SC-05: Compliance Audit
| Field | Value |
|---|---|
| Scenario ID | PER-005-SC-05 |
| Context / Trigger | The company’s quarterly compliance review is approaching. David must produce an audit report demonstrating that all user access to the ATOMx platform is governed, auditable, and consistent with the organization’s security policies. The auditor will review: who has access, what roles they hold, how they authenticate, and whether any access changes were unauthorized. |
Narrative
David opens the organization admin dashboard and navigates to the audit and compliance section. He generates a user access report showing all current users, their roles, authentication method, last login timestamp, and account status [UERQ-SYS-1935].
He then generates an audit log export [UERQ-SYS-1994] covering the past quarter, filtered to: user provisioning events (invitations sent, accepted, declined), role changes (assignments and removals), authentication events (successful logins, failed attempts, MFA challenges), deactivation and offboarding events, and organization configuration changes (SSO settings, SCIM configuration, domain claims).
David reviews the log for anomalies: he identifies one user whose role was changed from Pilot/Operator to Fleet Manager — he confirms this was an authorized promotion with a corresponding change request ticket. He identifies two failed login attempts from an IP address outside the corporate network — he confirms these were a pilot attempting to log in from a personal device before being directed to use the corporate VPN.
He packages the audit report and log export for the compliance auditor. The auditor can independently verify that every user with platform access was provisioned through a controlled mechanism [UERQ-SYS-1988], that no self-claimed memberships exist, and that all role assignments correspond to approved business needs.
David notes that the audit data is scoped to his organization [UERQ-SYS-1608] — he cannot see other organizations’ audit records, and they cannot see his. The retention policy is configured to the company’s 7-year requirement [UERQ-SYS-1968].
Traceability
| Linked End Goals | Generate an audit report of all user provisioning, role changes, and access events for quarterly compliance review. |
| Linked Capabilities | Profile Data Management (UERQ-SYS-1935), Audit Log Retention (UERQ-SYS-1968), Audit Log Export and SIEM Integration (UERQ-SYS-1994), Audit Data Access Control — Authority Scope (UERQ-SYS-1608), Controlled User Provisioning (UERQ-SYS-1988). |
| Safety Relevance | Yes: the audit process validates the integrity of the organization’s access controls. If the audit reveals unauthorized access or ungoverned role assignments, those represent unmitigated safety risks — an unqualified user with Authorizer role could have approved or denied flight authorizations without proper oversight. |