Security controls for
incident operations.
SSO, SCIM, MFA, RBAC, audit logs, and API controls for teams that need incident response without loose access controls.
Platform controls for security-conscious teams
The incident workflow is operationally critical. Access, identity, and auditability need to be first-class.
SAML SSO
Connect identity providers such as Microsoft, Okta, Google, or custom SAML for controlled workspace access.
SCIM provisioning
Automate user provisioning and deactivation so incident access follows your source of truth.
MFA enforcement
Require multi-factor authentication for organization members when stricter access control matters.
RBAC
Control who can manage incidents, integrations, billing, organization settings, and platform resources.
Audit logs
Track actor, resource, request, IP, user agent, auth method, API key, and service account metadata.
API access controls
Use API keys and service accounts for non-human access while keeping activity visible and governed.
How controls fit together
Centralize identity
Use SSO, SCIM, and MFA so user access follows your organization policy.
Limit sensitive actions
Use roles and permissions for organization settings, integrations, incidents, APIs, and billing.
Keep an audit trail
Track human and machine activity so operational changes are reviewable later.
Frequently asked questions
Bring incident response into your access-control model.
Use platform controls for the people and systems that touch incidents.