Skip to content

Access, Audit, and Data Protection Plan

This plan stages the identity, access, audit, encryption, privacy, and retention content needed for AC, IA, AU, SC, MP, and PT families. These controls are closely linked because the system must know who acted, what they could access, what data was involved, and how the record is protected.

Identity and Authentication

AreaTarget PracticeEvidence
Workforce identityFederated SSO with MFA.IdP policy export
Privileged identityPhishing-resistant MFA for production administrators.Authenticator policy and enrollment export
Customer identity[FILL IN: Better-Auth, OIDC, IdP, or other]Auth architecture and test evidence
Service accountsNamed, least-privilege, rotated, and owner-assigned.Service account inventory
Break-glassTime-limited, logged, reviewed after use.Break-glass event record
Stale accountsDetected and removed on a schedule.Access review evidence

Access Reviews

ScopeCadenceReviewerEvidence
Production administratorsMonthly or quarterlySecurity and Platform EngineeringAccess review issue
GitHub organization and repositoriesQuarterlySecurityTeam and permission export
Kubernetes RBACQuarterlyPlatform EngineeringRBAC export
Database privileged accessQuarterlyPlatform EngineeringRole and grant export
Secret manager accessQuarterlySecurityAccess export
Break-glass accountsAfter each use and quarterlySecurityEvent review

Authorization Rules

RuleImplementationEvidence
Least privilegeRoles grant only needed permissions.Role matrix
Separation of dutiesAuthor cannot be sole approver for production change.Pull request approval history
Server-side enforcementProtected actions check authorization on the server.Tests and code review
Administrative actionsAdmin actions emit audit events.Audit event samples
Data accessSensitive data access is authorized, logged, and minimized.Access tests and audit logs

Audit Event Schema

FieldDescriptionRequired
event_idUnique event identifier.Yes
event_timeTimestamp in UTC.Yes
actor_idUser or service account.Yes
actor_typeUser, service, system, or administrator.Yes
actionAction performed.Yes
target_typeObject type affected.Yes
target_idObject identifier.Conditional
resultSuccess, failure, denied, or error.Yes
source_ipSource address where available.Conditional
correlation_idTrace or request identifier.Yes
reasonReason for denial, change, or administrative action.Conditional

Audit Events To Capture

EventSupportsNotes
Login success and failureAU-2, IA-2, AC-7Include source and result.
MFA enrollment or resetIA-2, IA-5, AU-2Treat reset as sensitive.
Role or permission changeAC-2, AC-6, AU-2Include actor and approver.
Data exportAC-3, AU-2, PT-3Include scope and target.
Administrative configuration changeCM-3, AU-2Include before or after reference where safe.
Secret rotationSC-12, IA-5, AU-2Do not log secret values.
DeploymentCM-3, CM-4, AU-2Link commit, artifact, and environment.
Break-glass useAC-2, AC-6, AU-6Requires follow-up review.

Data Protection

AreaTarget PracticeEvidence
Encryption in transitTLS 1.2 or higher, target TLS 1.3 where supported.TLS configuration and scan
Internal trafficmTLS or network segmentation where practical.Service mesh or network policy evidence
Encryption at restDatabase, object, volume, and backup encryption.Provider and configuration export
Key managementKMS or HSM-backed keys with rotation.Key policy and rotation evidence
Secret managementSecret manager with access logs and rotation.Secret inventory and access logs
FIPS validationConfirm FIPS 140-3 module status for federal boundary.Vendor certificate or inherited control evidence

Privacy and Retention

Data ClassCollection PurposeRetentionDeletion MethodOwner
Account dataAuthentication and authorization[FILL IN][FILL IN]Security
Application recordsService delivery[FILL IN][FILL IN]Application Engineering
Audit logsSecurity accountability[FILL IN][FILL IN]Operations
Backup dataRecovery[FILL IN][FILL IN]Operations
Support dataSupport and troubleshooting[FILL IN][FILL IN]Customer Success or Operations

Required Decisions

  • Select identity provider and assurance level.
  • Define privileged MFA requirement.
  • Define role matrix.
  • Define audit event schema.
  • Choose audit log store and retention period.
  • Confirm encryption and FIPS validation posture.
  • Complete data inventory and retention schedule.
  • Define deletion and export procedures.