AC-16(7) Security and Privacy Attributes | Consistent Attribute Interpretation
Provide a consistent interpretation of security and privacy attributes transmitted between distributed system components.
Source: NIST SP 800-53 Rev 5, AC-16(7). 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.
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
- Test of Mechanisms implementing access enforcement and information flow enforcement functions · Identity provider / directory
periodic reviewEvidence produced at each review
- System audit records · Identity provider / directory
governing documentDocuments that govern the control
- Access control policies and procedures · Policy repository / GRC workspace
- Procedures addressing consistent interpretation of security and privacy attributes transmitted between distributed system components · Policy repository / GRC workspace
- Procedures addressing access enforcement · Policy repository / GRC workspace
- Procedures addressing information flow enforcement · 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 access control policy · Policy repository / GRC workspace
First move
Common gaps auditors find
- Distributed components interpret the same security and privacy attributes differently
- No common attribute definitions are shared across distributed components exchanging attributed information
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 sheetAC-16(6) Security and Privacy Attributes | Maintenance of Attribute Association · AC-16(8) Security and Privacy Attributes | Association Techniques and Technologies