QuestionQ23

VerifiedSection 4: Advanced Marketo Governance

Refer to the case study.

The Unicorn Marketing Operations team maintains five custom integrations that push and pull data between Adobe Marketo Engage and other third-party systems. All five of these custom integrations currently rely on the same API user and the same custom Launchpoint service.

What should be the primary security concern for Unicorn?

Explanation

Because all five integrations authenticate through one shared API user and Launchpoint service, they all use identical client ID and client secret credentials. This means the credentials cannot be isolated, monitored, or revoked on a per-integration basis: if the shared secret is compromised or needs to be rotated/revoked, every integration is impacted simultaneously, and there is no way to disable access for a single misbehaving or compromised integration without breaking the other four. Marketo's REST API authentication and custom services documentation recommends creating a dedicated API-only user (and corresponding unique client credentials) per integration precisely to avoid this kind of shared-credential exposure and to enable independent access control, auditing, and revocation.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!