AC-4(20) Information Flow Enforcement | Approved Solutions
Employ organization-defined solutions in approved configurations to control the flow of organization-defined information across security domains.
Source: NIST SP 800-53 Rev 5, AC-4(20). 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
- Approved configuration baselines · Identity provider / directory
- Test of Mechanisms implementing 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
- Information flow enforcement policy · Policy repository / GRC workspace
- Information flow control policies · 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
- List of solutions in approved configurations · Policy repository / GRC workspace
- System security plan · Policy repository / GRC workspace
First move
Common gaps auditors find
- Cross-domain information flows use solutions that are not in approved configurations
- The approved solutions and the information they may carry across domains were never defined
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-4(19) Information Flow Enforcement | Validation of Metadata · AC-4(21) Information Flow Enforcement | Physical or Logical Separation of Information Flows