Security-sensitive items under governance review
Security Exception Register
Exceptions should be explicit, time-bounded, justified, and reviewable.
| Exception | Reason | Review Date | Owner / Required Action |
|---|---|---|---|
| Temporary admin for reporting service account | Needed for data refresh troubleshooting during source migration | May 06 | Reporting owner / remove or renew with evidence |
| MFA exception for one field device workflow | Legacy operational process not yet moved to compliant pattern | May 11 | Service owner / provide remediation timeline |
| Vendor diagnostic access to remote access platform | Needed for active incident evidence and remediation support | May 02 | Infrastructure lead / close immediately after bridge ends |
| External Teams sharing approval exception | Short-term collaboration need with named business sponsor | May 15 | Collaboration owner / confirm expiration and access list |
Privileged Access Review
Elevated access should be reviewed like live operational risk, not passive paperwork.
Infrastructure Admin
7 active grants across remote access, endpoint, and server tools.
Web / Publish Admin
3 active grants for scheduled publishing and emergency rollback coverage.
Data / Reporting Elevated Access
2 temporary admin cases tied to migration and troubleshooting work.
Vendor Diagnostic Access
2 external elevated grants connected to contract-backed support cases.
Current Review Timeline
Security governance works best when due dates are hard to ignore.
Close or renew vendor diagnostic access created for remote access incident support.
Review all infrastructure admin grants tied to patch-window operations.
Security owner reviews legacy MFA exception remediation plan with service owner.