NIST 800-53 REV 5 • SYSTEM AND SERVICES ACQUISITION

SA-8(22)Accountability and Traceability

Implement the security design principle of accountability and traceability in {{ insert: param, sa-8.22_prm_1 }}.

CMMC Practice Mapping

No direct CMMC mapping

NIST 800-171 Mapping

No direct NIST 800-171 mapping

Related Controls

Supplemental Guidance

The principle of accountability and traceability states that it is possible to trace security-relevant actions (i.e., subject-object interactions) to the entity on whose behalf the action is being taken. The principle of accountability and traceability requires a trustworthy infrastructure that can record details about actions that affect system security (e.g., an audit subsystem). To record the details about actions, the system is able to uniquely identify the entity on whose behalf the action is being carried out and also record the relevant sequence of actions that are carried out. The accountability policy also requires that audit trail itself be protected from unauthorized access and modification. The principle of least privilege assists in tracing the actions to particular entities, as it increases the granularity of accountability. Associating specific actions with system entities, and ultimately with users, and making the audit trail secure against unauthorized access and modifications provide non-repudiation because once an action is recorded, it is not possible to change the audit trail. Another important function that accountability and traceability serves is in the routine and forensic analysis of events associated with the violation of security policy. Analysis of audit logs may provide additional information that may be helpful in determining the path or component that allowed the violation of the security policy and the actions of individuals associated with the violation of the security policy.

Practitioner Notes

Accountability and traceability means that every action in the system can be attributed to a specific individual and traced through the system's audit trail. No action should be anonymous.

Example 1: Eliminate shared accounts and require individual authentication for all system access. Even for emergency or break-glass accounts, log which individual used the shared credential by requiring a sign-out process that records the user's identity alongside the shared account usage.

Example 2: In Azure AD, enable Sign-in Logs and Audit Logs with retention in Microsoft Sentinel or Log Analytics. Every authentication event, role assignment, application access, and configuration change is attributed to a specific identity with timestamps and source metadata. Set retention to at least one year.