AC-3(3) Access Enforcement | Mandatory Access Control
Enforce organization-defined mandatory access control policy over the set of covered subjects and objects specified in the policy, and where the policy: (a) Is uniformly enforced across the covered subjects and objects within the system; (b) Specifies that a subject that has been granted access to information is constrained from doing any of the following; (1) Passing the information to unauthorized subjects or objects; (2) Granting its privileges to other subjects; (3) Changing one or more security attributes (specified by the policy) on subjects, objects, the system, or system components; (4) Choosing the security attributes and attribute values (specified by the policy) to be associated with newly created or modified objects; and (5) Changing the rules governing access control; and (c) Specifies that organization-defined subjects may explicitly be granted organization-defined privileges such that they are not limited by any defined subset (or all) of the above constraints.
Source: NIST SP 800-53 Rev 5, AC-3(3). 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
- List of subjects and objects (i.e., users and resources) requiring enforcement of mandatory access control policies · Identity provider / directory
- Test of Automated mechanisms implementing mandatory access control · Identity provider / directory
periodic reviewEvidence produced at each review
- System audit records · Identity provider / directory
governing documentDocuments that govern the control
- Access control policy · Policy repository / GRC workspace
- Mandatory access control policies · Policy repository / GRC workspace
- Procedures addressing access 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
First move
Common gaps auditors find
- No mandatory access control policy is defined, so subjects can pass information to unauthorized subjects or objects
- Mandatory access control is enforced on some components only, contrary to uniform enforcement under (a)
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-3(2) Access Enforcement | Dual Authorization · AC-3(4) Access Enforcement | Discretionary Access Control