EvidenceSheet
NIST SP 800-53 Rev 5 · AC - Access Control

AC-16 Security and Privacy Attributes

a. Provide the means to associate organization-defined types of security and privacy attributes with organization-defined security and privacy attribute values for information in storage, in process, and/or in transmission; b. Ensure that the attribute associations are made and retained with the information; c. Establish the following permitted security and privacy attributes from the attributes defined in AC-16a for organization-defined systems: organization-defined security and privacy attributes; d. Determine the following permitted attribute values or ranges for each of the established attributes: organization-defined attribute values or ranges for established attributes; e. Audit changes to attributes; and f. Review organization-defined security and privacy attributes for applicability organization-defined frequency.

Source: NIST SP 800-53 Rev 5, AC-16. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

8
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • System audit records · Identity provider / directory
  • Test of Organizational capability supporting and maintaining the association of security and privacy attributes to information in storage, in process, and in transmission · Identity provider / directory

governing documentDocuments that govern the control

  • Access control policy · Policy repository / GRC workspace
  • Procedures addressing the association of security and privacy attributes to information in storage, in process, and in transmission · Policy repository / GRC workspace
  • System design documentation · Policy repository / GRC workspace
  • System configuration settings and associated documentation · Policy repository / GRC workspace
  • System security plan · Policy repository / GRC workspace
  • Privacy plan · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

AC-14 Permitted Actions Without Identification or Authentication · AC-16(1) Security and Privacy Attributes | Dynamic Attribute Association