Skip to content

SSO and provisioning

Single sign-on

Base Operations supports enterprise single sign-on through Auth0, using SAML 2.0 and OpenID Connect (OIDC).

Supported identity providers include:

  • Microsoft Entra ID
  • Okta
  • Google Workspace
  • ADFS
  • Active Directory / LDAP
  • Other SAML- or OIDC-compatible providers

SAML and Okta integrations are currently configured. Other providers require setup specific to your organization, and confirmation that SSO is included in your subscription.

Once SSO is enabled, users authenticate through your existing identity infrastructure. No separate Base Operations credentials are required.

Username and password

If your organization does not use SSO, users can sign in with a username and password.

Multi-factor authentication

MFA is supported. It can be enforced at the platform level, or managed through your SSO provider if you would rather keep enforcement centralized.

What Base Operations needs to provision users

Name and email. That is the whole list.

Standard platform access does not require confidential client data, internal incident records, or sensitive business information. If your organization opts into BaseFusion, that involves a separate data-sharing agreement specific to internal incident feeds.

Security and compliance

Base Operations is SOC 2 compliant and hosted on AWS.

The Trust Center is publicly available for review at app.drata.com/trust.

Getting set up

SSO configuration is handled by your account team. Contact your Customer Success Manager to start, and they will coordinate with the technical team on your identity provider's requirements.