Federated ID is an enterprise-managed account where all identity profiles—as well as all associated assets—are provided by the customer’s Single Sign-On (SSO) identity management system and are created, owned, controlled by the customers’ IT infrastructure. Adobe integrates with most SAML2.0 compliant identity providers. Adobe IDs and Enterprise IDs both leverage the SHA-256 hash algorithm in combination with password salts and a large number of hash iterations. Adobe continually monitors Adobe-hosted accounts for unusual or anomalous account activity and evaluates this information to help quickly mitigate threats to their security. For Federated ID accounts, Adobe does not manage the users’ passwords. More information about Adobe’s identity management services can be found in the Adobe Identity Management Services security overview. Data Governance in Experience Platform Access Control Adobe Experience Platform customers can use a robust set of access control capabilities to manage access to resources and workflows. Role-based access control ensures that only authorized users can access data. Using the access control feature, Experience Platform customers can manage data usage and prevent data leakage, helping ensure regulatory compliance. Administrators benefit from a centralized administration interface to seamlessly manage permissions required for users to access sandboxes and specific workflows, including data ingestion, data modeling, data management, profile management, identity management, and destinations. Sandboxes In Adobe Experience Platform, customer data is contained within sandboxes, or virtual partitions within a single Experience Platform instance. These sandboxes are shared across Experience Platform services and applications and provide operational and data isolation to support market, brand, or initiative-focused marketing and digital experience operations. Adobe provides two types of sandboxes to support software development lifecycle requirements: development and production. Experience Platform supports multiple production and development sandboxes, with each sandbox maintaining its own independent library of Experience Platform resources, including schemas, datasets, and profiles. Content and actions taken within any given sandbox are confined only to that sandbox and do not affect any other sandboxes. For more information about Adobe Experience Platform data governance, please see the Adobe Experience Platform Data Governance white paper. 7