Skip to content

Access Control & SSO

Enterprise tier. AI SIEM adds role-based access control (RBAC) and single sign-on (SSO) so a team shares one deployment with permissions scoped to each person's job. On lower tiers there are no roles — every user you create signs in with full (admin-equivalent) access — so role setup is an enterprise-only concern.

Roles

Editor permissions come from Cognito group membership. Three roles ship:

  • admin — full access: configure detection and sources, approve and run remediation, manage users.
  • analyst — investigate and update threats: acknowledge, assign/claim, add notes, generate playbooks.
  • viewer — read-only dashboard and threat list.

Access is never elevated implicitly: a user who belongs to no group signs in as a read-only viewer, so you explicitly grant admin to the first person who needs to configure the system, and add everyone else as admin / analyst / viewer per person. Role assignment is managed with the groups helper — run groups init once to create the three groups, then add users to a group. Those commands ship in the helper-scripts bundle; see getting started for the exact steps.

How roles show up across the product:

  • Threat assignment — admins assign to anyone, analysts claim their own, viewers cannot assign. See analyst queues.
  • Remediation — only admins approve or run remediations. See response and remediation.
  • Rule editing — any role can follow a link to view the rule that fired a threat, but editing a rule requires admin or analyst. See custom detection rules.
  • Audit — every assignment, status change, and configuration change is recorded with the actor's role. See audit trail.

Single sign-on

Configure SAML or OIDC identity providers so users sign in with your existing IdP (Okta, Azure AD, and other SAML/OIDC providers). SSO is set up with the sso helper (setup-saml / setup-oidc, plus info to print the Cognito ACS URL, entity ID, and redirect URL you register with the IdP). The helper ships in the helper-scripts bundle — download it from Guides & Downloads.

Login and MFA

The editor is served over HTTPS through an ALB with Cognito login. Because sign-in is handled by Cognito, MFA (TOTP authenticator apps) is available on every tier that includes the editor — not an enterprise-only feature — and it is user-controlled: you choose whether to turn it on. Enforcement is set at deploy with the EditorMfa stack parameter:

  • OFF — no MFA.
  • OPTIONAL — each user enrolls their own authenticator.
  • ON — MFA required for all users (org-wide enforcement).

See the deploy parameters in getting started.