Can Spirion Sensitive Data Platform be integrated with Microsoft Active Directory?

1. Authentication & Role-Based Access Control (RBAC)

Spirion supports integration with Active Directory for administrative and user access to the platform:

• Console Login: You can configure the Spirion console to enable administrators and auditors to log in using their standard Active Directory domain credentials via LDAP or SAML-based Single Sign-On (SSO).
• User Segmentation: Integration with AD allows for the segmentation of users and devices based on domain group membership, ensuring that only authorized personnel can view specific scan results or manage certain agent groups.

2. Asset Discovery & Management

One of the primary uses of AD integration is to automate the identification of endpoints (Assets) within your environment:

• Asset Import: You can sync Spirion with Active Directory to automatically populate the console with a list of computers, servers, and users.
• Dynamic Grouping: By leveraging AD organizational units (OUs), Spirion can automatically assign new machines to specific scan groups or policies as soon as they appear in the domain.
• Contextual Data: Future roadmap requirements (Phase 3 in some internal PRDs) focus on using AD to clarify "data flow" by linking sensitive data findings to the access controls and business processes defined in Active Directory.

3. Scan Credentials

The Spirion Agent relies on Active Directory for the permissions needed to perform deep scans:

• Service Accounts: You can use a dedicated AD Service Account to run the Spirion Agent or to provide the "impersonation" credentials required to scan remote file shares (SMB), SharePoint sites, or Exchange mailboxes.
• Domain Permissions: The integration allows the agent to distinguish between local accounts and domain accounts when reporting on file ownership or permissions associated with a sensitive data discovery.

4. Policy and Governance

Spirion aligns with hierarchical policy systems similar to Microsoft Group Policy (GPO). Administrators often use AD knowledge to:

• Targeting: Segment and target scans based on Active Directory account or device metadata.
• Access Control Mapping: Use AD permissions to identify which users have "Read/Write" access to locations where sensitive data has been discovered, helping prioritize remediation efforts.

Summary

While the specific level of integration can depend on your deployment model (SaaS vs. On-Prem), Active Directory is considered a core "Should Have" integration for Asset Creation, Credential Management, and Authentication within the Spirion ecosystem.