Enterprise Metadata Management System  ·  View 21 of 22  ·  Assurance

Authorisation and Audit

One governance action end to end, proving that both permitted and denied outcomes are recorded.

Editable source SVG draw.io All views
Data Steward
Data Steward
Governance Console
Governance Console
API Gateway
API Gateway
Policy Decision Point
Policy Decision Point
Classification Service
Classification Service
Aspect Store
Aspect Store
Audit Log
Audit Log
Policy Enforcement
Policy Enforcement
1. set label Restricted
1. set label Restricted
2. PATCH classification
2. PATCH classification
3. authorise
3. authorise
4. role + domain + label
4. role + domain + label
5. deny, other domain
5. deny, other domain
6. permit
6. permit
7. apply label
7. apply label
8. write version + 1
8. write version + 1
9. actor, before, after
9. actor, before, after
10. sync tag
10. sync tag
11. applied at source
11. applied at source
12. denied attempt
12. denied attempt
13. 204 with new version
13. 204 with new version
Authorisation and Audit — Changing a Classification
Authorisation and Audit — Changing a Classification
Both outcomes are audited. The audit record is append-only and keeps the prior value, so a classification can always be explained after the fact.
Both outcomes are audited. The audit record is append-only and keeps the prior value, so a classification can always be explained after the fact.
v 1.0 · owner Security Architecture · date 2026-08
v 1.0 · owner Security Architecture · date 2026-08
Text is not SVG - cannot display

What this proves

  • Authorisation is a single decision point consulted by every service, not logic repeated per service.
  • Denials are audited as carefully as permissions. An audit trail that records only what succeeded cannot answer the question an investigation actually asks.
  • The prior value is retained on every write, so any classification can be explained months later without a restore.

Audit properties

  • Append-only, 7-year retention, held in a separate store with its own credentials and object-lock retention.
  • Every record carries actor, action, entity URN, before, after and correlation id.
  • Quarterly access review over the audit index; the review itself is audited.

Assumption

  • Immutability is enforced by storage-level object lock and separated credentials rather than by a ledger database. Confirm that this satisfies the internal audit standard before build.