2,022 records
What does a named security control actually require, in the publisher's own words?
2,022 records, one fact each. Every value is transcribed from the source that states it and carries the sentence it was taken from: 9 sources across 2 sites, last checked 2026-11-15, due for re-check by 2026-12-15. Every record has a page of its own, quoting the line that states it.
Cite as: Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words, referencesource.org/security-compliance-controls/, checked 2026-11-15.
About this data
Every control in NIST SP 800-53 Rev 5 and every paragraph of the HIPAA Security Rule, cut one provision at a time, each with the publisher's own words as the record's quote. One record is one obligation: a control with five lettered statements becomes five records, keyed the way the publisher cites them (SC-28, SC-28(1), AC-2a, 164.312(a)(2)(iv)), so a reader or an agent that has been handed a control number gets that control's text and nothing else. Answers 'what does NIST SP 800-53 SC-28 require', 'what does HIPAA 164.312(a)(2)(iv) actually say about encryption', 'which published controls cover audit logging', and 'what is the organization-defined parameter in AC-12'. The hard part is not finding the documents — NIST publishes the catalogue as machine-readable OSCAL and the eCFR publishes the rule as XML — it is that both are published as whole documents, so a coding assistant asked to implement 'SC-28' either reads a 1,200-page catalogue or guesses. This dataset is the retrieval layer: provision in, the publisher's sentence out. It does not say how to implement anything; the control's own text is the whole of what is published here. NIST's machine-readable text leaves a placeholder where a value is the organisation's to decide ('Protect the {{ insert: param, sc-28_odp.01 }} of ...'), so every record that carries one also carries the same sentence with each placeholder resolved from the catalogue's own parameter labels and kept in square brackets — '[Selection (one or more): confidentiality; integrity]' — which is how NIST's own HTML rendering reads, and which is a sentence a person or a coding assistant can actually use. The verbatim text, placeholders and all, stays on the record as the evidence. SOC 2, ISO 27001 and PCI DSS are deliberately absent: that text is copyrighted and may not be republished.
The data
| Citation | Framework | Control | Control title | What it requires, verbatim | Element | Family | What it requires, with its parameters named | Organization-defined values |
|---|---|---|---|---|---|---|---|---|
| 164.302 | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.302 | Applicability | A covered entity or business associate must comply with the applicable standards, implementation specifications, and requirements of this subpart with respect to electronic protected health information of a covered entity. | ||||
| 164.306(a) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (a) General requirements. Covered entities and business associates must do the following: | (a) | |||
| 164.306(a)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (1) Ensure the confidentiality, integrity, and availability of all electronic protected health information the covered entity or business associate creates, receives, maintains, or transmits. | (1) | |||
| 164.306(a)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (2) Protect against any reasonably anticipated threats or hazards to the security or integrity of such information. | (2) | |||
| 164.306(a)(3) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (3) Protect against any reasonably anticipated uses or disclosures of such information that are not permitted or required under subpart E of this part. | (3) | |||
| 164.306(a)(4) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (4) Ensure compliance with this subpart by its workforce. | (4) | |||
| 164.306(b) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (b) Flexibility of approach. (1) Covered entities and business associates may use any security measures that allow the covered entity or business associate to reasonably and appropriately implement the standards and implementation specifications as specified in this subpart. | (b) | |||
| 164.306(b)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (2) In deciding which security measures to use, a covered entity or business associate must take into account the following factors: | (2) | |||
| 164.306(b)(2)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (i) The size, complexity, and capabilities of the covered entity or business associate. | (i) | |||
| 164.306(b)(2)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (ii) The covered entity's or the business associate's technical infrastructure, hardware, and software security capabilities. | (ii) | |||
| 164.306(b)(2)(iii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (iii) The costs of security measures. | (iii) | |||
| 164.306(b)(2)(iv) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (iv) The probability and criticality of potential risks to electronic protected health information. | (iv) | |||
| 164.306(c) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (c) Standards. A covered entity or business associate must comply with the applicable standards as provided in this section and in §§ 164.308, 164.310, 164.312, 164.314 and 164.316 with respect to all electronic protected health information. | (c) | |||
| 164.306(d) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (d) Implementation specifications. In this subpart: | (d) | |||
| 164.306(d)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (1) Implementation specifications are required or addressable. If an implementation specification is required, the word “Required” appears in parentheses after the title of the implementation specification. If an implementation specification is addressable, the word “Addressable” appears in parentheses after the title of the implementation specification. | (1) | |||
| 164.306(d)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (2) When a standard adopted in § 164.308, § 164.310, § 164.312, § 164.314, or § 164.316 includes required implementation specifications, a covered entity or business associate must implement the implementation specifications. | (2) | |||
| 164.306(d)(3) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (3) When a standard adopted in § 164.308, § 164.310, § 164.312, § 164.314, or § 164.316 includes addressable implementation specifications, a covered entity or business associate must— | (3) | |||
| 164.306(d)(3)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (i) Assess whether each implementation specification is a reasonable and appropriate safeguard in its environment, when analyzed with reference to the likely contribution to protecting electronic protected health information; and | (i) | |||
| 164.306(d)(3)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (ii) As applicable to the covered entity or business associate— | (ii) | |||
| 164.306(d)(3)(ii)(A) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (A) Implement the implementation specification if reasonable and appropriate; or | (A) | |||
| 164.306(d)(3)(ii)(B) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (B) If implementing the implementation specification is not reasonable and appropriate— | (B) | |||
| 164.306(e) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.306 | Security standards: General rules | (e) Maintenance. A covered entity or business associate must review and modify the security measures implemented under this subpart as needed to continue provision of reasonable and appropriate protection of electronic protected health information, and update documentation of such security measures in accordance with § 164.316(b)(2)(iii). | (e) | |||
| 164.308(a) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (a) A covered entity or business associate must, in accordance with § 164.306: | (a) | |||
| 164.308(a)(1)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (1)(i) Standard: Security management process. Implement policies and procedures to prevent, detect, contain, and correct security violations. | (i) | |||
| 164.308(a)(1)(ii)(A) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (A) Risk analysis (Required). Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate. | (A) | |||
| 164.308(a)(1)(ii)(B) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (B) Risk management (Required). Implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level to comply with § 164.306(a). | (B) | |||
| 164.308(a)(1)(ii)(C) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (C) Sanction policy (Required). Apply appropriate sanctions against workforce members who fail to comply with the security policies and procedures of the covered entity or business associate. | (C) | |||
| 164.308(a)(1)(ii)(D) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (D) Information system activity review (Required). Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports. | (D) | |||
| 164.308(a)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (2) Standard: Assigned security responsibility. Identify the security official who is responsible for the development and implementation of the policies and procedures required by this subpart for the covered entity or business associate. | (2) | |||
| 164.308(a)(3)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (3)(i) Standard: Workforce security. Implement policies and procedures to ensure that all members of its workforce have appropriate access to electronic protected health information, as provided under paragraph (a)(4) of this section, and to prevent those workforce members who do not have access under paragraph (a)(4) of this section from obtaining access to electronic protected health information. | (i) | |||
| 164.308(a)(3)(ii)(A) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (A) Authorization and/or supervision (Addressable). Implement procedures for the authorization and/or supervision of workforce members who work with electronic protected health information or in locations where it might be accessed. | (A) | |||
| 164.308(a)(3)(ii)(B) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (B) Workforce clearance procedure (Addressable). Implement procedures to determine that the access of a workforce member to electronic protected health information is appropriate. | (B) | |||
| 164.308(a)(3)(ii)(C) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (C) Termination procedures (Addressable). Implement procedures for terminating access to electronic protected health information when the employment of, or other arrangement with, a workforce member ends or as required by determinations made as specified in paragraph (a)(3)(ii)(B) of this section. | (C) | |||
| 164.308(a)(4)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (4)(i) Standard: Information access management. Implement policies and procedures for authorizing access to electronic protected health information that are consistent with the applicable requirements of subpart E of this part. | (i) | |||
| 164.308(a)(4)(ii)(A) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (A) Isolating health care clearinghouse functions (Required). If a health care clearinghouse is part of a larger organization, the clearinghouse must implement policies and procedures that protect the electronic protected health information of the clearinghouse from unauthorized access by the larger organization. | (A) | |||
| 164.308(a)(4)(ii)(B) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (B) Access authorization (Addressable). Implement policies and procedures for granting access to electronic protected health information, for example, through access to a workstation, transaction, program, process, or other mechanism. | (B) | |||
| 164.308(a)(4)(ii)(C) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (C) Access establishment and modification (Addressable). Implement policies and procedures that, based upon the covered entity's or the business associate's access authorization policies, establish, document, review, and modify a user's right of access to a workstation, transaction, program, or process. | (C) | |||
| 164.308(a)(5)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (5)(i) Standard: Security awareness and training. Implement a security awareness and training program for all members of its workforce (including management). | (i) | |||
| 164.308(a)(5)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (ii) Implementation specifications. Implement: | (ii) | |||
| 164.308(a)(5)(ii)(A) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (A) Security reminders (Addressable). Periodic security updates. | (A) | |||
| 164.308(a)(5)(ii)(B) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (B) Protection from malicious software (Addressable). Procedures for guarding against, detecting, and reporting malicious software. | (B) | |||
| 164.308(a)(5)(ii)(C) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (C) Log-in monitoring (Addressable). Procedures for monitoring log-in attempts and reporting discrepancies. | (C) | |||
| 164.308(a)(5)(ii)(D) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (D) Password management (Addressable). Procedures for creating, changing, and safeguarding passwords. | (D) | |||
| 164.308(a)(6)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (6)(i) Standard: Security incident procedures. Implement policies and procedures to address security incidents. | (i) | |||
| 164.308(a)(6)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (ii) Implementation specification: Response and reporting (Required). Identify and respond to suspected or known security incidents; mitigate, to the extent practicable, harmful effects of security incidents that are known to the covered entity or business associate; and document security incidents and their outcomes. | (ii) | |||
| 164.308(a)(7)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (7)(i) Standard: Contingency plan. Establish (and implement as needed) policies and procedures for responding to an emergency or other occurrence (for example, fire, vandalism, system failure, and natural disaster) that damages systems that contain electronic protected health information. | (i) | |||
| 164.308(a)(7)(ii)(A) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (A) Data backup plan (Required). Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information. | (A) | |||
| 164.308(a)(7)(ii)(B) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (B) Disaster recovery plan (Required). Establish (and implement as needed) procedures to restore any loss of data. | (B) | |||
| 164.308(a)(7)(ii)(C) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (C) Emergency mode operation plan (Required). Establish (and implement as needed) procedures to enable continuation of critical business processes for protection of the security of electronic protected health information while operating in emergency mode. | (C) | |||
| 164.308(a)(7)(ii)(D) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (D) Testing and revision procedures (Addressable). Implement procedures for periodic testing and revision of contingency plans. | (D) | |||
| 164.308(a)(7)(ii)(E) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (E) Applications and data criticality analysis (Addressable). Assess the relative criticality of specific applications and data in support of other contingency plan components. | (E) | |||
| 164.308(a)(8) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (8) Standard: Evaluation. Perform a periodic technical and nontechnical evaluation, based initially upon the standards implemented under this rule and, subsequently, in response to environmental or operational changes affecting the security of electronic protected health information, that establishes the extent to which a covered entity's or business associate's security policies and procedures meet the requirements of this subpart. | (8) | |||
| 164.308(b)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (b)(1) Business associate contracts and other arrangements. A covered entity may permit a business associate to create, receive, maintain, or transmit electronic protected health information on the covered entity's behalf only if the covered entity obtains satisfactory assurances, in accordance with § 164.314(a), that the business associate will appropriately safeguard the information. A covered entity is not required to obtain such satisfactory assurances from a business associate that is a subcontractor. | (1) | |||
| 164.308(b)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (2) A business associate may permit a business associate that is a subcontractor to create, receive, maintain, or transmit electronic protected health information on its behalf only if the business associate obtains satisfactory assurances, in accordance with § 164.314(a), that the subcontractor will appropriately safeguard the information. | (2) | |||
| 164.308(b)(3) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.308 | Administrative safeguards | (3) Implementation specifications: Written contract or other arrangement (Required). Document the satisfactory assurances required by paragraph (b)(1) or (b)(2) of this section through a written contract or other arrangement with the business associate that meets the applicable requirements of § 164.314(a). | (3) | |||
| 164.310 | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | A covered entity or business associate must, in accordance with § 164.306: | ||||
| 164.310(a)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (a)(1) Standard: Facility access controls. Implement policies and procedures to limit physical access to its electronic information systems and the facility or facilities in which they are housed, while ensuring that properly authorized access is allowed. | (1) | |||
| 164.310(a)(2)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (i) Contingency operations (Addressable). Establish (and implement as needed) procedures that allow facility access in support of restoration of lost data under the disaster recovery plan and emergency mode operations plan in the event of an emergency. | (i) | |||
| 164.310(a)(2)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (ii) Facility security plan (Addressable). Implement policies and procedures to safeguard the facility and the equipment therein from unauthorized physical access, tampering, and theft. | (ii) | |||
| 164.310(a)(2)(iii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (iii) Access control and validation procedures (Addressable). Implement procedures to control and validate a person's access to facilities based on their role or function, including visitor control, and control of access to software programs for testing and revision. | (iii) | |||
| 164.310(a)(2)(iv) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (iv) Maintenance records (Addressable). Implement policies and procedures to document repairs and modifications to the physical components of a facility which are related to security (for example, hardware, walls, doors, and locks). | (iv) | |||
| 164.310(b) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (b) Standard: Workstation use. Implement policies and procedures that specify the proper functions to be performed, the manner in which those functions are to be performed, and the physical attributes of the surroundings of a specific workstation or class of workstation that can access electronic protected health information. | (b) | |||
| 164.310(c) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (c) Standard: Workstation security. Implement physical safeguards for all workstations that access electronic protected health information, to restrict access to authorized users. | (c) | |||
| 164.310(d)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (d)(1) Standard: Device and media controls. Implement policies and procedures that govern the receipt and removal of hardware and electronic media that contain electronic protected health information into and out of a facility, and the movement of these items within the facility. | (1) | |||
| 164.310(d)(2)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (i) Disposal (Required). Implement policies and procedures to address the final disposition of electronic protected health information, and/or the hardware or electronic media on which it is stored. | (i) | |||
| 164.310(d)(2)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (ii) Media re-use (Required). Implement procedures for removal of electronic protected health information from electronic media before the media are made available for re-use. | (ii) | |||
| 164.310(d)(2)(iii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (iii) Accountability (Addressable). Maintain a record of the movements of hardware and electronic media and any person responsible therefore. | (iii) | |||
| 164.310(d)(2)(iv) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.310 | Physical safeguards | (iv) Data backup and storage (Addressable). Create a retrievable, exact copy of electronic protected health information, when needed, before movement of equipment. | (iv) | |||
| 164.312 | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | A covered entity or business associate must, in accordance with § 164.306: | ||||
| 164.312(a)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (a)(1) Standard: Access control. Implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to those persons or software programs that have been granted access rights as specified in § 164.308(a)(4). | (1) | |||
| 164.312(a)(2)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (i) Unique user identification (Required). Assign a unique name and/or number for identifying and tracking user identity. | (i) | |||
| 164.312(a)(2)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (ii) Emergency access procedure (Required). Establish (and implement as needed) procedures for obtaining necessary electronic protected health information during an emergency. | (ii) | |||
| 164.312(a)(2)(iii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (iii) Automatic logoff (Addressable). Implement electronic procedures that terminate an electronic session after a predetermined time of inactivity. | (iii) | |||
| 164.312(a)(2)(iv) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (iv) Encryption and decryption (Addressable). Implement a mechanism to encrypt and decrypt electronic protected health information. | (iv) | |||
| 164.312(b) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (b) Standard: Audit controls. Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information. | (b) | |||
| 164.312(c)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (c)(1) Standard: Integrity. Implement policies and procedures to protect electronic protected health information from improper alteration or destruction. | (1) | |||
| 164.312(c)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (2) Implementation specification: Mechanism to authenticate electronic protected health information (Addressable). Implement electronic mechanisms to corroborate that electronic protected health information has not been altered or destroyed in an unauthorized manner. | (2) | |||
| 164.312(d) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (d) Standard: Person or entity authentication. Implement procedures to verify that a person or entity seeking access to electronic protected health information is the one claimed. | (d) | |||
| 164.312(e)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (e)(1) Standard: Transmission security. Implement technical security measures to guard against unauthorized access to electronic protected health information that is being transmitted over an electronic communications network. | (1) | |||
| 164.312(e)(2)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (i) Integrity controls (Addressable). Implement security measures to ensure that electronically transmitted electronic protected health information is not improperly modified without detection until disposed of. | (i) | |||
| 164.312(e)(2)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.312 | Technical safeguards | (ii) Encryption (Addressable). Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate. | (ii) | |||
| 164.314(a)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (a)(1) Standard: Business associate contracts or other arrangements. The contract or other arrangement required by § 164.308(b)(3) must meet the requirements of paragraph (a)(2)(i), (a)(2)(ii), or (a)(2)(iii) of this section, as applicable. | (1) | |||
| 164.314(a)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (2) Implementation specifications (Required)—(i) Business associate contracts. The contract must provide that the business associate will— | (2) | |||
| 164.314(a)(2)(A) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (A) Comply with the applicable requirements of this subpart; | (A) | |||
| 164.314(a)(2)(A)(B) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (B) In accordance with § 164.308(b)(2), ensure that any subcontractors that create, receive, maintain, or transmit electronic protected health information on behalf of the business associate agree to comply with the applicable requirements of this subpart by entering into a contract or other arrangement that complies with this section; and | (B) | |||
| 164.314(a)(2)(A)(C) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (C) Report to the covered entity any security incident of which it becomes aware, including breaches of unsecured protected health information as required by § 164.410. | (C) | |||
| 164.314(a)(2)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (ii) Other arrangements. The covered entity is in compliance with paragraph (a)(1) of this section if it has another arrangement in place that meets the requirements of § 164.504(e)(3). | (ii) | |||
| 164.314(a)(2)(iii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (iii) Business associate contracts with subcontractors. The requirements of paragraphs (a)(2)(i) and (a)(2)(ii) of this section apply to the contract or other arrangement between a business associate and a subcontractor required by § 164.308(b)(4) in the same manner as such requirements apply to contracts or other arrangements between a covered entity and business associate. | (iii) | |||
| 164.314(b)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (b)(1) Standard: Requirements for group health plans. Except when the only electronic protected health information disclosed to a plan sponsor is disclosed pursuant to § 164.504(f)(1)(ii) or (iii), or as authorized under § 164.508, a group health plan must ensure that its plan documents provide that the plan sponsor will reasonably and appropriately safeguard electronic protected health information created, received, maintained, or transmitted to or by the plan sponsor on behalf of the group health plan. | (1) | |||
| 164.314(b)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (2) Implementation specifications (Required). The plan documents of the group health plan must be amended to incorporate provisions to require the plan sponsor to— | (2) | |||
| 164.314(b)(2)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (i) Implement administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of the electronic protected health information that it creates, receives, maintains, or transmits on behalf of the group health plan; | (i) | |||
| 164.314(b)(2)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (ii) Ensure that the adequate separation required by § 164.504(f)(2)(iii) is supported by reasonable and appropriate security measures; | (ii) | |||
| 164.314(b)(2)(iii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (iii) Ensure that any agent to whom it provides this information agrees to implement reasonable and appropriate security measures to protect the information; and | (iii) | |||
| 164.314(b)(2)(iv) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.314 | Organizational requirements | (iv) Report to the group health plan any security incident of which it becomes aware. | (iv) | |||
| 164.316 | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.316 | Policies and procedures and documentation requirements | A covered entity or business associate must, in accordance with § 164.306: | ||||
| 164.316(a) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.316 | Policies and procedures and documentation requirements | (a) Standard: Policies and procedures. Implement reasonable and appropriate policies and procedures to comply with the standards, implementation specifications, or other requirements of this subpart, taking into account those factors specified in § 164.306(b)(2)(i), (ii), (iii), and (iv). This standard is not to be construed to permit or excuse an action that violates any other standard, implementation specification, or other requirements of this subpart. A covered entity or business associate may change its policies and procedures at any time, provided that the changes are documented and are implemented in accordance with this subpart. | (a) | |||
| 164.316(b)(1) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.316 | Policies and procedures and documentation requirements | (b)(1) Standard: Documentation. (i) Maintain the policies and procedures implemented to comply with this subpart in written (which may be electronic) form; and | (1) | |||
| 164.316(b)(1)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.316 | Policies and procedures and documentation requirements | (ii) If an action, activity or assessment is required by this subpart to be documented, maintain a written (which may be electronic) record of the action, activity, or assessment. | (ii) | |||
| 164.316(b)(2)(i) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.316 | Policies and procedures and documentation requirements | (i) Time limit (Required). Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later. | (i) | |||
| 164.316(b)(2)(ii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.316 | Policies and procedures and documentation requirements | (ii) Availability (Required). Make documentation available to those persons responsible for implementing the procedures to which the documentation pertains. | (ii) | |||
| 164.316(b)(2)(iii) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.316 | Policies and procedures and documentation requirements | (iii) Updates (Required). Review documentation periodically, and update as needed, in response to environmental or operational changes affecting the security of the electronic protected health information. | (iii) | |||
| 164.318(a) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.318 | Compliance dates for the initial implementation of the security standards | (a) Health plan. (1) A health plan that is not a small health plan must comply with the applicable requirements of this subpart no later than April 20, 2005. | (a) | |||
| 164.318(a)(2) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.318 | Compliance dates for the initial implementation of the security standards | (2) A small health plan must comply with the applicable requirements of this subpart no later than April 20, 2006. | (2) | |||
| 164.318(b) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.318 | Compliance dates for the initial implementation of the security standards | (b) Health care clearinghouse. A health care clearinghouse must comply with the applicable requirements of this subpart no later than April 20, 2005. | (b) | |||
| 164.318(c) | HIPAA Security Rule (45 CFR part 164, subpart C) | 164.318 | Compliance dates for the initial implementation of the security standards | (c) Health care provider. A covered health care provider must comply with the applicable requirements of this subpart no later than April 20, 2005. | (c) | |||
| AC-1a | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | Develop, document, and disseminate to {{ insert: param, ac-1_prm_1 }}: | a. | Access Control | Develop, document, and disseminate to [Assignment: organization-defined organization-defined personnel or roles]: | organization-defined personnel or roles |
| AC-1a1 | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | {{ insert: param, ac-01_odp.03 }} access control policy that: | 1. | Access Control | [Selection (one or more): organization-level; mission/business process-level; system-level] access control policy that: | organization-level or mission/business process-level or system-level |
| AC-1a1(a) | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and | (a) | Access Control | ||
| AC-1a1(b) | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and | (b) | Access Control | ||
| AC-1a2 | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | Procedures to facilitate the implementation of the access control policy and the associated access controls; | 2. | Access Control | ||
| AC-1b | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | Designate an {{ insert: param, ac-01_odp.04 }} to manage the development, documentation, and dissemination of the access control policy and procedures; and | b. | Access Control | Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the access control policy and procedures; and | official |
| AC-1c | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | Review and update the current access control: | c. | Access Control | ||
| AC-1c1 | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | Policy {{ insert: param, ac-01_odp.05 }} and following {{ insert: param, ac-01_odp.06 }} ; and | 1. | Access Control | Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events] ; and | frequency; events |
| AC-1c2 | NIST SP 800-53 Rev 5.2.0 | AC-1 | Policy and Procedures | Procedures {{ insert: param, ac-01_odp.07 }} and following {{ insert: param, ac-01_odp.08 }}. | 2. | Access Control | Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | frequency; events |
| AC-2(1) | NIST SP 800-53 Rev 5.2.0 | AC-2(1) | Automated System Account Management | Support the management of system accounts using {{ insert: param, ac-02.01_odp }}. | Access Control | Support the management of system accounts using [Assignment: organization-defined automated mechanisms]. | automated mechanisms | |
| AC-2(2) | NIST SP 800-53 Rev 5.2.0 | AC-2(2) | Automated Temporary and Emergency Account Management | Automatically {{ insert: param, ac-02.02_odp.01 }} temporary and emergency accounts after {{ insert: param, ac-02.02_odp.02 }}. | Access Control | Automatically [Selection: remove; disable] temporary and emergency accounts after [Assignment: organization-defined time period]. | remove or disable; time period | |
| AC-2(3) | NIST SP 800-53 Rev 5.2.0 | AC-2(3) | Disable Accounts | Disable accounts within {{ insert: param, ac-02.03_odp.01 }} when the accounts: | Access Control | Disable accounts within [Assignment: organization-defined time period] when the accounts: | time period | |
| AC-2(3)(a) | NIST SP 800-53 Rev 5.2.0 | AC-2(3) | Disable Accounts | Have expired; | (a) | Access Control | ||
| AC-2(3)(b) | NIST SP 800-53 Rev 5.2.0 | AC-2(3) | Disable Accounts | Are no longer associated with a user or individual; | (b) | Access Control | ||
| AC-2(3)(c) | NIST SP 800-53 Rev 5.2.0 | AC-2(3) | Disable Accounts | Are in violation of organizational policy; or | (c) | Access Control | ||
| AC-2(3)(d) | NIST SP 800-53 Rev 5.2.0 | AC-2(3) | Disable Accounts | Have been inactive for {{ insert: param, ac-02.03_odp.02 }}. | (d) | Access Control | Have been inactive for [Assignment: organization-defined time period]. | time period |
| AC-2(4) | NIST SP 800-53 Rev 5.2.0 | AC-2(4) | Automated Audit Actions | Automatically audit account creation, modification, enabling, disabling, and removal actions. | Access Control | |||
| AC-2(5) | NIST SP 800-53 Rev 5.2.0 | AC-2(5) | Inactivity Logout | Require that users log out when {{ insert: param, ac-02.05_odp }}. | Access Control | Require that users log out when [Assignment: organization-defined time period of expected inactivity or description of when to log out]. | time period of expected inactivity or description of when to log out | |
| AC-2(6) | NIST SP 800-53 Rev 5.2.0 | AC-2(6) | Dynamic Privilege Management | Implement {{ insert: param, ac-02.06_odp }}. | Access Control | Implement [Assignment: organization-defined dynamic privilege management capabilities]. | dynamic privilege management capabilities | |
| AC-2(7)(a) | NIST SP 800-53 Rev 5.2.0 | AC-2(7) | Privileged User Accounts | Establish and administer privileged user accounts in accordance with {{ insert: param, ac-02.07_odp }}; | (a) | Access Control | Establish and administer privileged user accounts in accordance with [Selection: a role-based access scheme; an attribute-based access scheme]; | a role-based access scheme or an attribute-based access scheme |
| AC-2(7)(b) | NIST SP 800-53 Rev 5.2.0 | AC-2(7) | Privileged User Accounts | Monitor privileged role or attribute assignments; | (b) | Access Control | ||
| AC-2(7)(c) | NIST SP 800-53 Rev 5.2.0 | AC-2(7) | Privileged User Accounts | Monitor changes to roles or attributes; and | (c) | Access Control | ||
| AC-2(7)(d) | NIST SP 800-53 Rev 5.2.0 | AC-2(7) | Privileged User Accounts | Revoke access when privileged role or attribute assignments are no longer appropriate. | (d) | Access Control | ||
| AC-2(8) | NIST SP 800-53 Rev 5.2.0 | AC-2(8) | Dynamic Account Management | Create, activate, manage, and deactivate {{ insert: param, ac-02.08_odp }} dynamically. | Access Control | Create, activate, manage, and deactivate [Assignment: organization-defined system accounts] dynamically. | system accounts | |
| AC-2(9) | NIST SP 800-53 Rev 5.2.0 | AC-2(9) | Restrictions on Use of Shared and Group Accounts | Only permit the use of shared and group accounts that meet {{ insert: param, ac-02.09_odp }}. | Access Control | Only permit the use of shared and group accounts that meet [Assignment: organization-defined conditions]. | conditions | |
| AC-2(11) | NIST SP 800-53 Rev 5.2.0 | AC-2(11) | Usage Conditions | Enforce {{ insert: param, ac-02.11_odp.01 }} for {{ insert: param, ac-02.11_odp.02 }}. | Access Control | Enforce [Assignment: organization-defined circumstances and/or usage conditions] for [Assignment: organization-defined system accounts]. | circumstances and/or usage conditions; system accounts | |
| AC-2(12)(a) | NIST SP 800-53 Rev 5.2.0 | AC-2(12) | Account Monitoring for Atypical Usage | Monitor system accounts for {{ insert: param, ac-02.12_odp.01 }} ; and | (a) | Access Control | Monitor system accounts for [Assignment: organization-defined atypical usage] ; and | atypical usage |
| AC-2(12)(b) | NIST SP 800-53 Rev 5.2.0 | AC-2(12) | Account Monitoring for Atypical Usage | Report atypical usage of system accounts to {{ insert: param, ac-02.12_odp.02 }}. | (b) | Access Control | Report atypical usage of system accounts to [Assignment: organization-defined personnel or roles]. | personnel or roles |
| AC-2(13) | NIST SP 800-53 Rev 5.2.0 | AC-2(13) | Disable Accounts for High-risk Individuals | Disable accounts of individuals within {{ insert: param, ac-02.13_odp.01 }} of discovery of {{ insert: param, ac-02.13_odp.02 }}. | Access Control | Disable accounts of individuals within [Assignment: organization-defined time period] of discovery of [Assignment: organization-defined significant risks]. | time period; significant risks | |
| AC-2a | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Define and document the types of accounts allowed and specifically prohibited for use within the system; | a. | Access Control | ||
| AC-2b | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Assign account managers; | b. | Access Control | ||
| AC-2c | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Require {{ insert: param, ac-02_odp.01 }} for group and role membership; | c. | Access Control | Require [Assignment: organization-defined prerequisites and criteria] for group and role membership; | prerequisites and criteria |
| AC-2d1 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Authorized users of the system; | 1. | Access Control | ||
| AC-2d2 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Group and role membership; and | 2. | Access Control | ||
| AC-2d3 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Access authorizations (i.e., privileges) and {{ insert: param, ac-02_odp.02 }} for each account; | 3. | Access Control | Access authorizations (i.e., privileges) and [Assignment: organization-defined attributes (as required)] for each account; | attributes (as required) |
| AC-2e | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Require approvals by {{ insert: param, ac-02_odp.03 }} for requests to create accounts; | e. | Access Control | Require approvals by [Assignment: organization-defined personnel or roles] for requests to create accounts; | personnel or roles |
| AC-2f | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Create, enable, modify, disable, and remove accounts in accordance with {{ insert: param, ac-02_odp.04 }}; | f. | Access Control | Create, enable, modify, disable, and remove accounts in accordance with [Assignment: organization-defined policy, procedures, prerequisites, and criteria]; | policy, procedures, prerequisites, and criteria |
| AC-2g | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Monitor the use of accounts; | g. | Access Control | ||
| AC-2h | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Notify account managers and {{ insert: param, ac-02_odp.05 }} within: | h. | Access Control | Notify account managers and [Assignment: organization-defined personnel or roles] within: | personnel or roles |
| AC-2h1 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | {{ insert: param, ac-02_odp.06 }} when accounts are no longer required; | 1. | Access Control | [Assignment: organization-defined time period] when accounts are no longer required; | time period |
| AC-2h2 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | {{ insert: param, ac-02_odp.07 }} when users are terminated or transferred; and | 2. | Access Control | [Assignment: organization-defined time period] when users are terminated or transferred; and | time period |
| AC-2h3 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | {{ insert: param, ac-02_odp.08 }} when system usage or need-to-know changes for an individual; | 3. | Access Control | [Assignment: organization-defined time period] when system usage or need-to-know changes for an individual; | time period |
| AC-2i | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Authorize access to the system based on: | i. | Access Control | ||
| AC-2i1 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | A valid access authorization; | 1. | Access Control | ||
| AC-2i2 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Intended system usage; and | 2. | Access Control | ||
| AC-2i3 | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | {{ insert: param, ac-02_odp.09 }}; | 3. | Access Control | [Assignment: organization-defined attributes (as required)]; | attributes (as required) |
| AC-2j | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Review accounts for compliance with account management requirements {{ insert: param, ac-02_odp.10 }}; | j. | Access Control | Review accounts for compliance with account management requirements [Assignment: organization-defined frequency]; | frequency |
| AC-2k | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and | k. | Access Control | ||
| AC-2l | NIST SP 800-53 Rev 5.2.0 | AC-2 | Account Management | Align account management processes with personnel termination and transfer processes. | l. | Access Control | ||
| AC-3 | NIST SP 800-53 Rev 5.2.0 | AC-3 | Access Enforcement | Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. | Access Control | |||
| AC-3(2) | NIST SP 800-53 Rev 5.2.0 | AC-3(2) | Dual Authorization | Enforce dual authorization for {{ insert: param, ac-03.02_odp }}. | Access Control | Enforce dual authorization for [Assignment: organization-defined privileged commands and/or other actions]. | privileged commands and/or other actions | |
| AC-3(3) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Enforce {{ insert: param, ac-3.3_prm_1 }} over the set of covered subjects and objects specified in the policy, and where the policy: | Access Control | Enforce [Assignment: organization-defined organization-defined mandatory access control policy] over the set of covered subjects and objects specified in the policy, and where the policy: | organization-defined mandatory access control policy | |
| AC-3(3)(a) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Is uniformly enforced across the covered subjects and objects within the system; | (a) | Access Control | ||
| AC-3(3)(b) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Specifies that a subject that has been granted access to information is constrained from doing any of the following; | (b) | Access Control | ||
| AC-3(3)(b)(1) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Passing the information to unauthorized subjects or objects; | (1) | Access Control | ||
| AC-3(3)(b)(2) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Granting its privileges to other subjects; | (2) | Access Control | ||
| AC-3(3)(b)(3) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Changing one or more security attributes (specified by the policy) on subjects, objects, the system, or system components; | (3) | Access Control | ||
| AC-3(3)(b)(4) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Choosing the security attributes and attribute values (specified by the policy) to be associated with newly created or modified objects; and | (4) | Access Control | ||
| AC-3(3)(b)(5) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Changing the rules governing access control; and | (5) | Access Control | ||
| AC-3(3)(c) | NIST SP 800-53 Rev 5.2.0 | AC-3(3) | Mandatory Access Control | Specifies that {{ insert: param, ac-03.03_odp.03 }} may explicitly be granted {{ insert: param, ac-03.03_odp.04 }} such that they are not limited by any defined subset (or all) of the above constraints. | (c) | Access Control | Specifies that [Assignment: organization-defined subjects] may explicitly be granted [Assignment: organization-defined privileges] such that they are not limited by any defined subset (or all) of the above constraints. | subjects; privileges |
| AC-3(4) | NIST SP 800-53 Rev 5.2.0 | AC-3(4) | Discretionary Access Control | Enforce {{ insert: param, ac-3.4_prm_1 }} over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following: | Access Control | Enforce [Assignment: organization-defined organization-defined discretionary access control policy] over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following: | organization-defined discretionary access control policy | |
| AC-3(4)(a) | NIST SP 800-53 Rev 5.2.0 | AC-3(4) | Discretionary Access Control | Pass the information to any other subjects or objects; | (a) | Access Control | ||
| AC-3(4)(b) | NIST SP 800-53 Rev 5.2.0 | AC-3(4) | Discretionary Access Control | Grant its privileges to other subjects; | (b) | Access Control | ||
| AC-3(4)(c) | NIST SP 800-53 Rev 5.2.0 | AC-3(4) | Discretionary Access Control | Change security attributes on subjects, objects, the system, or the system’s components; | (c) | Access Control | ||
| AC-3(4)(d) | NIST SP 800-53 Rev 5.2.0 | AC-3(4) | Discretionary Access Control | Choose the security attributes to be associated with newly created or revised objects; or | (d) | Access Control | ||
| AC-3(4)(e) | NIST SP 800-53 Rev 5.2.0 | AC-3(4) | Discretionary Access Control | Change the rules governing access control. | (e) | Access Control | ||
| AC-3(5) | NIST SP 800-53 Rev 5.2.0 | AC-3(5) | Security-relevant Information | Prevent access to {{ insert: param, ac-03.05_odp }} except during secure, non-operable system states. | Access Control | Prevent access to [Assignment: organization-defined security-relevant information] except during secure, non-operable system states. | security-relevant information | |
| AC-3(7) | NIST SP 800-53 Rev 5.2.0 | AC-3(7) | Role-based Access Control | Enforce a role-based access control policy over defined subjects and objects and control access based upon {{ insert: param, ac-3.7_prm_1 }}. | Access Control | Enforce a role-based access control policy over defined subjects and objects and control access based upon [Assignment: organization-defined organization-defined roles and users authorized to assume such roles]. | organization-defined roles and users authorized to assume such roles | |
| AC-3(8) | NIST SP 800-53 Rev 5.2.0 | AC-3(8) | Revocation of Access Authorizations | Enforce the revocation of access authorizations resulting from changes to the security attributes of subjects and objects based on {{ insert: param, ac-03.08_odp }}. | Access Control | Enforce the revocation of access authorizations resulting from changes to the security attributes of subjects and objects based on [Assignment: organization-defined rules]. | rules | |
| AC-3(9) | NIST SP 800-53 Rev 5.2.0 | AC-3(9) | Controlled Release | Release information outside of the system only if: | Access Control | |||
| AC-3(9)(a) | NIST SP 800-53 Rev 5.2.0 | AC-3(9) | Controlled Release | The receiving {{ insert: param, ac-03.09_odp.01 }} provides {{ insert: param, ac-03.09_odp.02 }} ; and | (a) | Access Control | The receiving [Assignment: organization-defined system or system component] provides [Assignment: organization-defined controls] ; and | system or system component; controls |
| AC-3(9)(b) | NIST SP 800-53 Rev 5.2.0 | AC-3(9) | Controlled Release | {{ insert: param, ac-03.09_odp.03 }} are used to validate the appropriateness of the information designated for release. | (b) | Access Control | [Assignment: organization-defined controls] are used to validate the appropriateness of the information designated for release. | controls |
| AC-3(10) | NIST SP 800-53 Rev 5.2.0 | AC-3(10) | Audited Override of Access Control Mechanisms | Employ an audited override of automated access control mechanisms under {{ insert: param, ac-03.10_odp.01 }} by {{ insert: param, ac-03.10_odp.02 }}. | Access Control | Employ an audited override of automated access control mechanisms under [Assignment: organization-defined conditions] by [Assignment: organization-defined roles]. | conditions; roles | |
| AC-3(11) | NIST SP 800-53 Rev 5.2.0 | AC-3(11) | Restrict Access to Specific Information Types | Restrict access to data repositories containing {{ insert: param, ac-03.11_odp }}. | Access Control | Restrict access to data repositories containing [Assignment: organization-defined information types]. | information types | |
| AC-3(12)(a) | NIST SP 800-53 Rev 5.2.0 | AC-3(12) | Assert and Enforce Application Access | Require applications to assert, as part of the installation process, the access needed to the following system applications and functions: {{ insert: param, ac-03.12_odp }}; | (a) | Access Control | Require applications to assert, as part of the installation process, the access needed to the following system applications and functions: [Assignment: organization-defined system applications and functions]; | system applications and functions |
| AC-3(12)(b) | NIST SP 800-53 Rev 5.2.0 | AC-3(12) | Assert and Enforce Application Access | Provide an enforcement mechanism to prevent unauthorized access; and | (b) | Access Control | ||
| AC-3(12)(c) | NIST SP 800-53 Rev 5.2.0 | AC-3(12) | Assert and Enforce Application Access | Approve access changes after initial installation of the application. | (c) | Access Control | ||
| AC-3(13) | NIST SP 800-53 Rev 5.2.0 | AC-3(13) | Attribute-based Access Control | Enforce attribute-based access control policy over defined subjects and objects and control access based upon {{ insert: param, ac-03.13_odp }}. | Access Control | Enforce attribute-based access control policy over defined subjects and objects and control access based upon [Assignment: organization-defined attributes]. | attributes | |
| AC-3(14) | NIST SP 800-53 Rev 5.2.0 | AC-3(14) | Individual Access | Provide {{ insert: param, ac-03.14_odp.01 }} to enable individuals to have access to the following elements of their personally identifiable information: {{ insert: param, ac-03.14_odp.02 }}. | Access Control | Provide [Assignment: organization-defined mechanisms] to enable individuals to have access to the following elements of their personally identifiable information: [Assignment: organization-defined elements]. | mechanisms; elements | |
| AC-3(15)(a) | NIST SP 800-53 Rev 5.2.0 | AC-3(15) | Discretionary and Mandatory Access Control | Enforce {{ insert: param, ac-3.15_prm_1 }} over the set of covered subjects and objects specified in the policy; and | (a) | Access Control | Enforce [Assignment: organization-defined organization-defined mandatory access control policy] over the set of covered subjects and objects specified in the policy; and | organization-defined mandatory access control policy |
| AC-3(15)(b) | NIST SP 800-53 Rev 5.2.0 | AC-3(15) | Discretionary and Mandatory Access Control | Enforce {{ insert: param, ac-3.15_prm_2 }} over the set of covered subjects and objects specified in the policy. | (b) | Access Control | Enforce [Assignment: organization-defined organization-defined discretionary access control policy] over the set of covered subjects and objects specified in the policy. | organization-defined discretionary access control policy |
| AC-4 | NIST SP 800-53 Rev 5.2.0 | AC-4 | Information Flow Enforcement | Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on {{ insert: param, ac-04_odp }}. | Access Control | Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on [Assignment: organization-defined information flow control policies]. | information flow control policies | |
| AC-4(1) | NIST SP 800-53 Rev 5.2.0 | AC-4(1) | Object Security and Privacy Attributes | Use {{ insert: param, ac-4.1_prm_1 }} associated with {{ insert: param, ac-4.1_prm_2 }} to enforce {{ insert: param, ac-04.01_odp.09 }} as a basis for flow control decisions. | Access Control | Use [Assignment: organization-defined organization-defined security and privacy attributes] associated with [Assignment: organization-defined organization-defined information, source, and destination objects] to enforce [Assignment: organization-defined information flow control policies] as a basis for flow control decisions. | organization-defined security and privacy attributes; organization-defined information, source, and destination objects; information flow control policies | |
| AC-4(2) | NIST SP 800-53 Rev 5.2.0 | AC-4(2) | Processing Domains | Use protected processing domains to enforce {{ insert: param, ac-04.02_odp }} as a basis for flow control decisions. | Access Control | Use protected processing domains to enforce [Assignment: organization-defined information flow control policies] as a basis for flow control decisions. | information flow control policies | |
| AC-4(3) | NIST SP 800-53 Rev 5.2.0 | AC-4(3) | Dynamic Information Flow Control | Enforce {{ insert: param, ac-04.03_odp }}. | Access Control | Enforce [Assignment: organization-defined information flow control policies]. | information flow control policies | |
| AC-4(4) | NIST SP 800-53 Rev 5.2.0 | AC-4(4) | Flow Control of Encrypted Information | Prevent encrypted information from bypassing {{ insert: param, ac-04.04_odp.01 }} by {{ insert: param, ac-04.04_odp.02 }}. | Access Control | Prevent encrypted information from bypassing [Assignment: organization-defined information flow control mechanisms] by [Selection (one or more): decrypting the information; blocking the flow of the encrypted information; terminating communications sessions attempting to pass encrypted information; [Assignment: organization-defined organization-defined procedure or method]]. | information flow control mechanisms; decrypting the information or blocking the flow of the encrypted information or terminating communications sessions attempting to pass encrypted information or [Assignment: organization-defined organization-defined procedure or method] | |
| AC-4(5) | NIST SP 800-53 Rev 5.2.0 | AC-4(5) | Embedded Data Types | Enforce {{ insert: param, ac-04.05_odp }} on embedding data types within other data types. | Access Control | Enforce [Assignment: organization-defined limitations] on embedding data types within other data types. | limitations | |
| AC-4(6) | NIST SP 800-53 Rev 5.2.0 | AC-4(6) | Metadata | Enforce information flow control based on {{ insert: param, ac-04.06_odp }}. | Access Control | Enforce information flow control based on [Assignment: organization-defined metadata]. | metadata | |
| AC-4(7) | NIST SP 800-53 Rev 5.2.0 | AC-4(7) | One-way Flow Mechanisms | Enforce one-way information flows through hardware-based flow control mechanisms. | Access Control | |||
| AC-4(8)(a) | NIST SP 800-53 Rev 5.2.0 | AC-4(8) | Security and Privacy Policy Filters | Enforce information flow control using {{ insert: param, ac-4.8_prm_1 }} as a basis for flow control decisions for {{ insert: param, ac-4.8_prm_2 }} ; and | (a) | Access Control | Enforce information flow control using [Assignment: organization-defined organization-defined security or privacy policy filters] as a basis for flow control decisions for [Assignment: organization-defined organization-defined information flows] ; and | organization-defined security or privacy policy filters; organization-defined information flows |
| AC-4(8)(b) | NIST SP 800-53 Rev 5.2.0 | AC-4(8) | Security and Privacy Policy Filters | {{ insert: param, ac-04.08_odp.05 }} data after a filter processing failure in accordance with {{ insert: param, ac-4.8_prm_4 }}. | (b) | Access Control | [Selection (one or more): block; strip; modify; quarantine] data after a filter processing failure in accordance with [Assignment: organization-defined organization-defined security or privacy policy]. | block or strip or modify or quarantine; organization-defined security or privacy policy |
| AC-4(9) | NIST SP 800-53 Rev 5.2.0 | AC-4(9) | Human Reviews | Enforce the use of human reviews for {{ insert: param, ac-04.09_odp.01 }} under the following conditions: {{ insert: param, ac-04.09_odp.02 }}. | Access Control | Enforce the use of human reviews for [Assignment: organization-defined information flows] under the following conditions: [Assignment: organization-defined conditions]. | information flows; conditions | |
| AC-4(10) | NIST SP 800-53 Rev 5.2.0 | AC-4(10) | Enable and Disable Security or Privacy Policy Filters | Provide the capability for privileged administrators to enable and disable {{ insert: param, ac-4.10_prm_1 }} under the following conditions: {{ insert: param, ac-4.10_prm_2 }}. | Access Control | Provide the capability for privileged administrators to enable and disable [Assignment: organization-defined organization-defined security or privacy policy filters] under the following conditions: [Assignment: organization-defined organization-defined conditions]. | organization-defined security or privacy policy filters; organization-defined conditions | |
| AC-4(11) | NIST SP 800-53 Rev 5.2.0 | AC-4(11) | Configuration of Security or Privacy Policy Filters | Provide the capability for privileged administrators to configure {{ insert: param, ac-4.11_prm_1 }} to support different security or privacy policies. | Access Control | Provide the capability for privileged administrators to configure [Assignment: organization-defined organization-defined security or privacy policy filters] to support different security or privacy policies. | organization-defined security or privacy policy filters | |
| AC-4(12) | NIST SP 800-53 Rev 5.2.0 | AC-4(12) | Data Type Identifiers | When transferring information between different security domains, use {{ insert: param, ac-04.12_odp }} to validate data essential for information flow decisions. | Access Control | When transferring information between different security domains, use [Assignment: organization-defined data type identifiers] to validate data essential for information flow decisions. | data type identifiers | |
| AC-4(13) | NIST SP 800-53 Rev 5.2.0 | AC-4(13) | Decomposition into Policy-relevant Subcomponents | When transferring information between different security domains, decompose information into {{ insert: param, ac-04.13_odp }} for submission to policy enforcement mechanisms. | Access Control | When transferring information between different security domains, decompose information into [Assignment: organization-defined policy-relevant subcomponents] for submission to policy enforcement mechanisms. | policy-relevant subcomponents | |
| AC-4(14) | NIST SP 800-53 Rev 5.2.0 | AC-4(14) | Security or Privacy Policy Filter Constraints | When transferring information between different security domains, implement {{ insert: param, ac-4.14_prm_1 }} requiring fully enumerated formats that restrict data structure and content. | Access Control | When transferring information between different security domains, implement [Assignment: organization-defined organization-defined security or privacy policy filters] requiring fully enumerated formats that restrict data structure and content. | organization-defined security or privacy policy filters | |
| AC-4(15) | NIST SP 800-53 Rev 5.2.0 | AC-4(15) | Detection of Unsanctioned Information | When transferring information between different security domains, examine the information for the presence of {{ insert: param, ac-04.15_odp.01 }} and prohibit the transfer of such information in accordance with the {{ insert: param, ac-4.15_prm_2 }}. | Access Control | When transferring information between different security domains, examine the information for the presence of [Assignment: organization-defined unsanctioned information] and prohibit the transfer of such information in accordance with the [Assignment: organization-defined organization-defined security or privacy policy]. | unsanctioned information; organization-defined security or privacy policy | |
| AC-4(17) | NIST SP 800-53 Rev 5.2.0 | AC-4(17) | Domain Authentication | Uniquely identify and authenticate source and destination points by {{ insert: param, ac-04.17_odp }} for information transfer. | Access Control | Uniquely identify and authenticate source and destination points by [Selection (one or more): organization, system, application, service, individual] for information transfer. | organization, system, application, service, individual | |
| AC-4(19) | NIST SP 800-53 Rev 5.2.0 | AC-4(19) | Validation of Metadata | When transferring information between different security domains, implement {{ insert: param, ac-4.19_prm_1 }} on metadata. | Access Control | When transferring information between different security domains, implement [Assignment: organization-defined organization-defined security or privacy policy filters] on metadata. | organization-defined security or privacy policy filters | |
| AC-4(20) | NIST SP 800-53 Rev 5.2.0 | AC-4(20) | Approved Solutions | Employ {{ insert: param, ac-04.20_odp.01 }} to control the flow of {{ insert: param, ac-04.20_odp.02 }} across security domains. | Access Control | Employ [Assignment: organization-defined solutions in approved configurations] to control the flow of [Assignment: organization-defined information] across security domains. | solutions in approved configurations; information | |
| AC-4(21) | NIST SP 800-53 Rev 5.2.0 | AC-4(21) | Physical or Logical Separation of Information Flows | Separate information flows logically or physically using {{ insert: param, ac-4.21_prm_1 }} to accomplish {{ insert: param, ac-04.21_odp.03 }}. | Access Control | Separate information flows logically or physically using [Assignment: organization-defined organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization-defined required separations]. | organization-defined mechanisms and/or techniques; required separations | |
| AC-4(22) | NIST SP 800-53 Rev 5.2.0 | AC-4(22) | Access Only | Provide access from a single device to computing platforms, applications, or data residing in multiple different security domains, while preventing information flow between the different security domains. | Access Control | |||
| AC-4(23) | NIST SP 800-53 Rev 5.2.0 | AC-4(23) | Modify Non-releasable Information | When transferring information between different security domains, modify non-releasable information by implementing {{ insert: param, ac-04.23_odp }}. | Access Control | When transferring information between different security domains, modify non-releasable information by implementing [Assignment: organization-defined modification action]. | modification action | |
| AC-4(24) | NIST SP 800-53 Rev 5.2.0 | AC-4(24) | Internal Normalized Format | When transferring information between different security domains, parse incoming data into an internal normalized format and regenerate the data to be consistent with its intended specification. | Access Control | |||
| AC-4(25) | NIST SP 800-53 Rev 5.2.0 | AC-4(25) | Data Sanitization | When transferring information between different security domains, sanitize data to minimize {{ insert: param, ac-04.25_odp.01 }} in accordance with {{ insert: param, ac-04.25_odp.02 }}. | Access Control | When transferring information between different security domains, sanitize data to minimize [Selection (one or more): delivery of malicious content, command and control of malicious code, malicious code augmentation, and steganography-encoded data; spillage of sensitive information] in accordance with [Assignment: organization-defined policy]. | delivery of malicious content, command and control of malicious code, malicious code augmentation, and steganography-encoded data or spillage of sensitive information; policy | |
| AC-4(26) | NIST SP 800-53 Rev 5.2.0 | AC-4(26) | Audit Filtering Actions | When transferring information between different security domains, record and audit content filtering actions and results for the information being filtered. | Access Control | |||
| AC-4(27) | NIST SP 800-53 Rev 5.2.0 | AC-4(27) | Redundant/Independent Filtering Mechanisms | When transferring information between different security domains, implement content filtering solutions that provide redundant and independent filtering mechanisms for each data type. | Access Control | |||
| AC-4(28) | NIST SP 800-53 Rev 5.2.0 | AC-4(28) | Linear Filter Pipelines | When transferring information between different security domains, implement a linear content filter pipeline that is enforced with discretionary and mandatory access controls. | Access Control | |||
| AC-4(29) | NIST SP 800-53 Rev 5.2.0 | AC-4(29) | Filter Orchestration Engines | When transferring information between different security domains, employ content filter orchestration engines to ensure that: | Access Control | |||
| AC-4(29)(a) | NIST SP 800-53 Rev 5.2.0 | AC-4(29) | Filter Orchestration Engines | Content filtering mechanisms successfully complete execution without errors; and | (a) | Access Control | ||
| AC-4(29)(b) | NIST SP 800-53 Rev 5.2.0 | AC-4(29) | Filter Orchestration Engines | Content filtering actions occur in the correct order and comply with {{ insert: param, ac-04.29_odp }}. | (b) | Access Control | Content filtering actions occur in the correct order and comply with [Assignment: organization-defined policy]. | policy |
| AC-4(30) | NIST SP 800-53 Rev 5.2.0 | AC-4(30) | Filter Mechanisms Using Multiple Processes | When transferring information between different security domains, implement content filtering mechanisms using multiple processes. | Access Control | |||
| AC-4(31) | NIST SP 800-53 Rev 5.2.0 | AC-4(31) | Failed Content Transfer Prevention | When transferring information between different security domains, prevent the transfer of failed content to the receiving domain. | Access Control | |||
| AC-4(32) | NIST SP 800-53 Rev 5.2.0 | AC-4(32) | Process Requirements for Information Transfer | When transferring information between different security domains, the process that transfers information between filter pipelines: | Access Control | |||
| AC-4(32)(a) | NIST SP 800-53 Rev 5.2.0 | AC-4(32) | Process Requirements for Information Transfer | Does not filter message content; | (a) | Access Control | ||
| AC-4(32)(b) | NIST SP 800-53 Rev 5.2.0 | AC-4(32) | Process Requirements for Information Transfer | Validates filtering metadata; | (b) | Access Control | ||
| AC-4(32)(c) | NIST SP 800-53 Rev 5.2.0 | AC-4(32) | Process Requirements for Information Transfer | Ensures the content associated with the filtering metadata has successfully completed filtering; and | (c) | Access Control | ||
| AC-4(32)(d) | NIST SP 800-53 Rev 5.2.0 | AC-4(32) | Process Requirements for Information Transfer | Transfers the content to the destination filter pipeline. | (d) | Access Control | ||
| AC-5a | NIST SP 800-53 Rev 5.2.0 | AC-5 | Separation of Duties | Identify and document {{ insert: param, ac-05_odp }} ; and | a. | Access Control | Identify and document [Assignment: organization-defined duties of individuals] ; and | duties of individuals |
| AC-5b | NIST SP 800-53 Rev 5.2.0 | AC-5 | Separation of Duties | Define system access authorizations to support separation of duties. | b. | Access Control | ||
| AC-6 | NIST SP 800-53 Rev 5.2.0 | AC-6 | Least Privilege | Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks. | Access Control | |||
| AC-6(1) | NIST SP 800-53 Rev 5.2.0 | AC-6(1) | Authorize Access to Security Functions | Authorize access for {{ insert: param, ac-06.01_odp.01 }} to: | Access Control | Authorize access for [Assignment: organization-defined individuals and roles] to: | individuals and roles | |
| AC-6(1)(a) | NIST SP 800-53 Rev 5.2.0 | AC-6(1) | Authorize Access to Security Functions | {{ insert: param, ac-6.1_prm_2 }} ; and | (a) | Access Control | [Assignment: organization-defined organization-defined security functions (deployed in hardware, software, and firmware)] ; and | organization-defined security functions (deployed in hardware, software, and firmware) |
| AC-6(1)(b) | NIST SP 800-53 Rev 5.2.0 | AC-6(1) | Authorize Access to Security Functions | {{ insert: param, ac-06.01_odp.05 }}. | (b) | Access Control | [Assignment: organization-defined security-relevant information]. | security-relevant information |
| AC-6(2) | NIST SP 800-53 Rev 5.2.0 | AC-6(2) | Non-privileged Access for Nonsecurity Functions | Require that users of system accounts (or roles) with access to {{ insert: param, ac-06.02_odp }} use non-privileged accounts or roles, when accessing nonsecurity functions. | Access Control | Require that users of system accounts (or roles) with access to [Assignment: organization-defined security functions or security-relevant information] use non-privileged accounts or roles, when accessing nonsecurity functions. | security functions or security-relevant information | |
| AC-6(3) | NIST SP 800-53 Rev 5.2.0 | AC-6(3) | Network Access to Privileged Commands | Authorize network access to {{ insert: param, ac-06.03_odp.01 }} only for {{ insert: param, ac-06.03_odp.02 }} and document the rationale for such access in the security plan for the system. | Access Control | Authorize network access to [Assignment: organization-defined privileged commands] only for [Assignment: organization-defined compelling operational needs] and document the rationale for such access in the security plan for the system. | privileged commands; compelling operational needs | |
| AC-6(4) | NIST SP 800-53 Rev 5.2.0 | AC-6(4) | Separate Processing Domains | Provide separate processing domains to enable finer-grained allocation of user privileges. | Access Control | |||
| AC-6(5) | NIST SP 800-53 Rev 5.2.0 | AC-6(5) | Privileged Accounts | Restrict privileged accounts on the system to {{ insert: param, ac-06.05_odp }}. | Access Control | Restrict privileged accounts on the system to [Assignment: organization-defined personnel or roles]. | personnel or roles | |
| AC-6(6) | NIST SP 800-53 Rev 5.2.0 | AC-6(6) | Privileged Access by Non-organizational Users | Prohibit privileged access to the system by non-organizational users. | Access Control | |||
| AC-6(7)(a) | NIST SP 800-53 Rev 5.2.0 | AC-6(7) | Review of User Privileges | Review {{ insert: param, ac-06.07_odp.01 }} the privileges assigned to {{ insert: param, ac-06.07_odp.02 }} to validate the need for such privileges; and | (a) | Access Control | Review [Assignment: organization-defined frequency] the privileges assigned to [Assignment: organization-defined roles and classes] to validate the need for such privileges; and | frequency; roles and classes |
| AC-6(7)(b) | NIST SP 800-53 Rev 5.2.0 | AC-6(7) | Review of User Privileges | Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs. | (b) | Access Control | ||
| AC-6(8) | NIST SP 800-53 Rev 5.2.0 | AC-6(8) | Privilege Levels for Code Execution | Prevent the following software from executing at higher privilege levels than users executing the software: {{ insert: param, ac-06.08_odp }}. | Access Control | Prevent the following software from executing at higher privilege levels than users executing the software: [Assignment: organization-defined software]. | software | |
| AC-6(9) | NIST SP 800-53 Rev 5.2.0 | AC-6(9) | Log Use of Privileged Functions | Log the execution of privileged functions. | Access Control | |||
| AC-6(10) | NIST SP 800-53 Rev 5.2.0 | AC-6(10) | Prohibit Non-privileged Users from Executing Privileged Functions | Prevent non-privileged users from executing privileged functions. | Access Control | |||
| AC-7(2) | NIST SP 800-53 Rev 5.2.0 | AC-7(2) | Purge or Wipe Mobile Device | Purge or wipe information from {{ insert: param, ac-07.02_odp.01 }} based on {{ insert: param, ac-07.02_odp.02 }} after {{ insert: param, ac-07.02_odp.03 }} consecutive, unsuccessful device logon attempts. | Access Control | Purge or wipe information from [Assignment: organization-defined mobile devices] based on [Assignment: organization-defined purging or wiping requirements and techniques] after [Assignment: organization-defined number] consecutive, unsuccessful device logon attempts. | mobile devices; purging or wiping requirements and techniques; number | |
| AC-7(3) | NIST SP 800-53 Rev 5.2.0 | AC-7(3) | Biometric Attempt Limiting | Limit the number of unsuccessful biometric logon attempts to {{ insert: param, ac-07.03_odp }}. | Access Control | Limit the number of unsuccessful biometric logon attempts to [Assignment: organization-defined number]. | number | |
| AC-7(4)(a) | NIST SP 800-53 Rev 5.2.0 | AC-7(4) | Use of Alternate Authentication Factor | Allow the use of {{ insert: param, ac-07.04_odp.01 }} that are different from the primary authentication factors after the number of organization-defined consecutive invalid logon attempts have been exceeded; and | (a) | Access Control | Allow the use of [Assignment: organization-defined authentication factors] that are different from the primary authentication factors after the number of organization-defined consecutive invalid logon attempts have been exceeded; and | authentication factors |
| AC-7(4)(b) | NIST SP 800-53 Rev 5.2.0 | AC-7(4) | Use of Alternate Authentication Factor | Enforce a limit of {{ insert: param, ac-07.04_odp.02 }} consecutive invalid logon attempts through use of the alternative factors by a user during a {{ insert: param, ac-07.04_odp.03 }}. | (b) | Access Control | Enforce a limit of [Assignment: organization-defined number] consecutive invalid logon attempts through use of the alternative factors by a user during a [Assignment: organization-defined time period]. | number; time period |
| AC-7a | NIST SP 800-53 Rev 5.2.0 | AC-7 | Unsuccessful Logon Attempts | Enforce a limit of {{ insert: param, ac-07_odp.01 }} consecutive invalid logon attempts by a user during a {{ insert: param, ac-07_odp.02 }} ; and | a. | Access Control | Enforce a limit of [Assignment: organization-defined number] consecutive invalid logon attempts by a user during a [Assignment: organization-defined time period] ; and | number; time period |
| AC-7b | NIST SP 800-53 Rev 5.2.0 | AC-7 | Unsuccessful Logon Attempts | Automatically {{ insert: param, ac-07_odp.03 }} when the maximum number of unsuccessful attempts is exceeded. | b. | Access Control | Automatically [Selection (one or more): lock the account or node for [Assignment: organization-defined time period]; lock the account or node until released by an administrator; delay next logon prompt per [Assignment: organization-defined delay algorithm]; notify system administrator; take other [Assignment: organization-defined action]] when the maximum number of unsuccessful attempts is exceeded. | lock the account or node for [Assignment: organization-defined time period] or lock the account or node until released by an administrator or delay next logon prompt per [Assignment: organization-defined delay algorithm] or notify system administrator or take other [Assignment: organization-defined action] |
| AC-8a | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | Display {{ insert: param, ac-08_odp.01 }} to users before granting access to the system that provides privacy and security notices consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and state that: | a. | Access Control | Display [Assignment: organization-defined system use notification] to users before granting access to the system that provides privacy and security notices consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and state that: | system use notification |
| AC-8a1 | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | Users are accessing a U.S. Government system; | 1. | Access Control | ||
| AC-8a2 | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | System usage may be monitored, recorded, and subject to audit; | 2. | Access Control | ||
| AC-8a3 | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | Unauthorized use of the system is prohibited and subject to criminal and civil penalties; and | 3. | Access Control | ||
| AC-8a4 | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | Use of the system indicates consent to monitoring and recording; | 4. | Access Control | ||
| AC-8b | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | Retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system; and | b. | Access Control | ||
| AC-8c | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | For publicly accessible systems: | c. | Access Control | ||
| AC-8c1 | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | Display system use information {{ insert: param, ac-08_odp.02 }} , before granting further access to the publicly accessible system; | 1. | Access Control | Display system use information [Assignment: organization-defined conditions] , before granting further access to the publicly accessible system; | conditions |
| AC-8c2 | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | Display references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and | 2. | Access Control | ||
| AC-8c3 | NIST SP 800-53 Rev 5.2.0 | AC-8 | System Use Notification | Include a description of the authorized uses of the system. | 3. | Access Control | ||
| AC-9 | NIST SP 800-53 Rev 5.2.0 | AC-9 | Previous Logon Notification | Notify the user, upon successful logon to the system, of the date and time of the last logon. | Access Control | |||
| AC-9(1) | NIST SP 800-53 Rev 5.2.0 | AC-9(1) | Unsuccessful Logons | Notify the user, upon successful logon, of the number of unsuccessful logon attempts since the last successful logon. | Access Control | |||
| AC-9(2) | NIST SP 800-53 Rev 5.2.0 | AC-9(2) | Successful and Unsuccessful Logons | Notify the user, upon successful logon, of the number of {{ insert: param, ac-09.02_odp.01 }} during {{ insert: param, ac-09.02_odp.02 }}. | Access Control | Notify the user, upon successful logon, of the number of [Selection: successful logons; unsuccessful logon attempts; both] during [Assignment: organization-defined time period]. | successful logons or unsuccessful logon attempts or both; time period | |
| AC-9(3) | NIST SP 800-53 Rev 5.2.0 | AC-9(3) | Notification of Account Changes | Notify the user, upon successful logon, of changes to {{ insert: param, ac-09.03_odp.01 }} during {{ insert: param, ac-09.03_odp.02 }}. | Access Control | Notify the user, upon successful logon, of changes to [Assignment: organization-defined security-related characteristics or parameters] during [Assignment: organization-defined time period]. | security-related characteristics or parameters; time period | |
| AC-9(4) | NIST SP 800-53 Rev 5.2.0 | AC-9(4) | Additional Logon Information | Notify the user, upon successful logon, of the following additional information: {{ insert: param, ac-09.04_odp }}. | Access Control | Notify the user, upon successful logon, of the following additional information: [Assignment: organization-defined additional information]. | additional information | |
| AC-10 | NIST SP 800-53 Rev 5.2.0 | AC-10 | Concurrent Session Control | Limit the number of concurrent sessions for each {{ insert: param, ac-10_odp.01 }} to {{ insert: param, ac-10_odp.02 }}. | Access Control | Limit the number of concurrent sessions for each [Assignment: organization-defined account and/or account types] to [Assignment: organization-defined number]. | account and/or account types; number | |
| AC-11(1) | NIST SP 800-53 Rev 5.2.0 | AC-11(1) | Pattern-hiding Displays | Conceal, via the device lock, information previously visible on the display with a publicly viewable image. | Access Control | |||
| AC-11a | NIST SP 800-53 Rev 5.2.0 | AC-11 | Device Lock | Prevent further access to the system by {{ insert: param, ac-11_odp.01 }} ; and | a. | Access Control | Prevent further access to the system by [Selection (one or more): initiating a device lock after [Assignment: organization-defined time period] of inactivity; requiring the user to initiate a device lock before leaving the system unattended] ; and | initiating a device lock after [Assignment: organization-defined time period] of inactivity or requiring the user to initiate a device lock before leaving the system unattended |
| AC-11b | NIST SP 800-53 Rev 5.2.0 | AC-11 | Device Lock | Retain the device lock until the user reestablishes access using established identification and authentication procedures. | b. | Access Control | ||
| AC-12 | NIST SP 800-53 Rev 5.2.0 | AC-12 | Session Termination | Automatically terminate a user session after {{ insert: param, ac-12_odp }}. | Access Control | Automatically terminate a user session after [Assignment: organization-defined conditions or trigger events]. | conditions or trigger events | |
| AC-12(1) | NIST SP 800-53 Rev 5.2.0 | AC-12(1) | User-initiated Logouts | Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to {{ insert: param, ac-12.01_odp }}. | Access Control | Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to [Assignment: organization-defined information resources]. | information resources | |
| AC-12(2) | NIST SP 800-53 Rev 5.2.0 | AC-12(2) | Termination Message | Display an explicit logout message to users indicating the termination of authenticated communications sessions. | Access Control | |||
| AC-12(3) | NIST SP 800-53 Rev 5.2.0 | AC-12(3) | Timeout Warning Message | Display an explicit message to users indicating that the session will end in {{ insert: param, ac-12.03_odp }}. | Access Control | Display an explicit message to users indicating that the session will end in [Assignment: organization-defined time]. | time | |
| AC-14a | NIST SP 800-53 Rev 5.2.0 | AC-14 | Permitted Actions Without Identification or Authentication | Identify {{ insert: param, ac-14_odp }} that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and | a. | Access Control | Identify [Assignment: organization-defined user actions] that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and | user actions |
| AC-14b | NIST SP 800-53 Rev 5.2.0 | AC-14 | Permitted Actions Without Identification or Authentication | Document and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication. | b. | Access Control | ||
| AC-16(1) | NIST SP 800-53 Rev 5.2.0 | AC-16(1) | Dynamic Attribute Association | Dynamically associate security and privacy attributes with {{ insert: param, ac-16.1_prm_1 }} in accordance with the following security and privacy policies as information is created and combined: {{ insert: param, ac-16.1_prm_2 }}. | Access Control | Dynamically associate security and privacy attributes with [Assignment: organization-defined organization-defined subjects and objects] in accordance with the following security and privacy policies as information is created and combined: [Assignment: organization-defined organization-defined security and privacy policies]. | organization-defined subjects and objects; organization-defined security and privacy policies | |
| AC-16(2) | NIST SP 800-53 Rev 5.2.0 | AC-16(2) | Attribute Value Changes by Authorized Individuals | Provide authorized individuals (or processes acting on behalf of individuals) the capability to define or change the value of associated security and privacy attributes. | Access Control | |||
| AC-16(3) | NIST SP 800-53 Rev 5.2.0 | AC-16(3) | Maintenance of Attribute Associations by System | Maintain the association and integrity of {{ insert: param, ac-16.3_prm_1 }} to {{ insert: param, ac-16.3_prm_2 }}. | Access Control | Maintain the association and integrity of [Assignment: organization-defined organization-defined security and privacy attributes] to [Assignment: organization-defined organization-defined subjects and objects]. | organization-defined security and privacy attributes; organization-defined subjects and objects | |
| AC-16(4) | NIST SP 800-53 Rev 5.2.0 | AC-16(4) | Association of Attributes by Authorized Individuals | Provide the capability to associate {{ insert: param, ac-16.4_prm_1 }} with {{ insert: param, ac-16.4_prm_2 }} by authorized individuals (or processes acting on behalf of individuals). | Access Control | Provide the capability to associate [Assignment: organization-defined organization-defined security and privacy attributes] with [Assignment: organization-defined organization-defined subjects and objects] by authorized individuals (or processes acting on behalf of individuals). | organization-defined security and privacy attributes; organization-defined subjects and objects | |
| AC-16(5) | NIST SP 800-53 Rev 5.2.0 | AC-16(5) | Attribute Displays on Objects to Be Output | Display security and privacy attributes in human-readable form on each object that the system transmits to output devices to identify {{ insert: param, ac-16.05_odp.01 }} using {{ insert: param, ac-16.05_odp.02 }}. | Access Control | Display security and privacy attributes in human-readable form on each object that the system transmits to output devices to identify [Assignment: organization-defined instructions] using [Assignment: organization-defined naming conventions]. | instructions; naming conventions | |
| AC-16(6) | NIST SP 800-53 Rev 5.2.0 | AC-16(6) | Maintenance of Attribute Association | Require personnel to associate and maintain the association of {{ insert: param, ac-16.6_prm_1 }} with {{ insert: param, ac-16.6_prm_2 }} in accordance with {{ insert: param, ac-16.6_prm_3 }}. | Access Control | Require personnel to associate and maintain the association of [Assignment: organization-defined organization-defined security and privacy attributes] with [Assignment: organization-defined organization-defined subjects and objects] in accordance with [Assignment: organization-defined organization-defined security and privacy policies]. | organization-defined security and privacy attributes; organization-defined subjects and objects; organization-defined security and privacy policies | |
| AC-16(7) | NIST SP 800-53 Rev 5.2.0 | AC-16(7) | Consistent Attribute Interpretation | Provide a consistent interpretation of security and privacy attributes transmitted between distributed system components. | Access Control | |||
| AC-16(8) | NIST SP 800-53 Rev 5.2.0 | AC-16(8) | Association Techniques and Technologies | Implement {{ insert: param, ac-16.8_prm_1 }} in associating security and privacy attributes to information. | Access Control | Implement [Assignment: organization-defined organization-defined techniques and technologies] in associating security and privacy attributes to information. | organization-defined techniques and technologies | |
| AC-16(9) | NIST SP 800-53 Rev 5.2.0 | AC-16(9) | Attribute Reassignment — Regrading Mechanisms | Change security and privacy attributes associated with information only via regrading mechanisms validated using {{ insert: param, ac-16.9_prm_1 }}. | Access Control | Change security and privacy attributes associated with information only via regrading mechanisms validated using [Assignment: organization-defined organization-defined techniques or procedures]. | organization-defined techniques or procedures | |
| AC-16(10) | NIST SP 800-53 Rev 5.2.0 | AC-16(10) | Attribute Configuration by Authorized Individuals | Provide authorized individuals the capability to define or change the type and value of security and privacy attributes available for association with subjects and objects. | Access Control | |||
| AC-16a | NIST SP 800-53 Rev 5.2.0 | AC-16 | Security and Privacy Attributes | Provide the means to associate {{ insert: param, ac-16_prm_1 }} with {{ insert: param, ac-16_prm_2 }} for information in storage, in process, and/or in transmission; | a. | Access Control | Provide the means to associate [Assignment: organization-defined organization-defined types of security and privacy attributes] with [Assignment: organization-defined organization-defined security and privacy attribute values] for information in storage, in process, and/or in transmission; | organization-defined types of security and privacy attributes; organization-defined security and privacy attribute values |
| AC-16b | NIST SP 800-53 Rev 5.2.0 | AC-16 | Security and Privacy Attributes | Ensure that the attribute associations are made and retained with the information; | b. | Access Control | ||
| AC-16c | NIST SP 800-53 Rev 5.2.0 | AC-16 | Security and Privacy Attributes | Establish the following permitted security and privacy attributes from the attributes defined in [AC-16a](#ac-16_smt.a) for {{ insert: param, ac-16_prm_3 }}: {{ insert: param, ac-16_prm_4 }}; | c. | Access Control | Establish the following permitted security and privacy attributes from the attributes defined in [AC-16a](#ac-16_smt.a) for [Assignment: organization-defined organization-defined systems]: [Assignment: organization-defined organization-defined security and privacy attributes]; | organization-defined systems; organization-defined security and privacy attributes |
| AC-16d | NIST SP 800-53 Rev 5.2.0 | AC-16 | Security and Privacy Attributes | Determine the following permitted attribute values or ranges for each of the established attributes: {{ insert: param, ac-16_odp.09 }}; | d. | Access Control | Determine the following permitted attribute values or ranges for each of the established attributes: [Assignment: organization-defined attribute values or ranges]; | attribute values or ranges |
| AC-16e | NIST SP 800-53 Rev 5.2.0 | AC-16 | Security and Privacy Attributes | Audit changes to attributes; and | e. | Access Control | ||
| AC-16f | NIST SP 800-53 Rev 5.2.0 | AC-16 | Security and Privacy Attributes | Review {{ insert: param, ac-16_prm_6 }} for applicability {{ insert: param, ac-16_prm_7 }}. | f. | Access Control | Review [Assignment: organization-defined organization-defined security and privacy attributes] for applicability [Assignment: organization-defined organization-defined frequency]. | organization-defined security and privacy attributes; organization-defined frequency |
| AC-17(1) | NIST SP 800-53 Rev 5.2.0 | AC-17(1) | Monitoring and Control | Employ automated mechanisms to monitor and control remote access methods. | Access Control | |||
| AC-17(2) | NIST SP 800-53 Rev 5.2.0 | AC-17(2) | Protection of Confidentiality and Integrity Using Encryption | Implement cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions. | Access Control | |||
| AC-17(3) | NIST SP 800-53 Rev 5.2.0 | AC-17(3) | Managed Access Control Points | Route remote accesses through authorized and managed network access control points. | Access Control | |||
| AC-17(4)(a) | NIST SP 800-53 Rev 5.2.0 | AC-17(4) | Privileged Commands and Access | Authorize the execution of privileged commands and access to security-relevant information via remote access only in a format that provides assessable evidence and for the following needs: {{ insert: param, ac-17.4_prm_1 }} ; and | (a) | Access Control | Authorize the execution of privileged commands and access to security-relevant information via remote access only in a format that provides assessable evidence and for the following needs: [Assignment: organization-defined organization-defined needs] ; and | organization-defined needs |
| AC-17(4)(b) | NIST SP 800-53 Rev 5.2.0 | AC-17(4) | Privileged Commands and Access | Document the rationale for remote access in the security plan for the system. | (b) | Access Control | ||
| AC-17(6) | NIST SP 800-53 Rev 5.2.0 | AC-17(6) | Protection of Mechanism Information | Protect information about remote access mechanisms from unauthorized use and disclosure. | Access Control | |||
| AC-17(9) | NIST SP 800-53 Rev 5.2.0 | AC-17(9) | Disconnect or Disable Access | Provide the capability to disconnect or disable remote access to the system within {{ insert: param, ac-17.09_odp }}. | Access Control | Provide the capability to disconnect or disable remote access to the system within [Assignment: organization-defined time period]. | time period | |
| AC-17(10) | NIST SP 800-53 Rev 5.2.0 | AC-17(10) | Authenticate Remote Commands | Implement {{ insert: param, ac-17.10_odp.01 }} to authenticate {{ insert: param, ac-17.10_odp.02 }}. | Access Control | Implement [Assignment: organization-defined mechanisms] to authenticate [Assignment: organization-defined remote commands]. | mechanisms; remote commands | |
| AC-17a | NIST SP 800-53 Rev 5.2.0 | AC-17 | Remote Access | Establish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and | a. | Access Control | ||
| AC-17b | NIST SP 800-53 Rev 5.2.0 | AC-17 | Remote Access | Authorize each type of remote access to the system prior to allowing such connections. | b. | Access Control | ||
| AC-18(1) | NIST SP 800-53 Rev 5.2.0 | AC-18(1) | Authentication and Encryption | Protect wireless access to the system using authentication of {{ insert: param, ac-18.01_odp }} and encryption. | Access Control | Protect wireless access to the system using authentication of [Selection (one or more): users; devices] and encryption. | users or devices | |
| AC-18(3) | NIST SP 800-53 Rev 5.2.0 | AC-18(3) | Disable Wireless Networking | Disable, when not intended for use, wireless networking capabilities embedded within system components prior to issuance and deployment. | Access Control | |||
| AC-18(4) | NIST SP 800-53 Rev 5.2.0 | AC-18(4) | Restrict Configurations by Users | Identify and explicitly authorize users allowed to independently configure wireless networking capabilities. | Access Control | |||
| AC-18(5) | NIST SP 800-53 Rev 5.2.0 | AC-18(5) | Antennas and Transmission Power Levels | Select radio antennas and calibrate transmission power levels to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries. | Access Control | |||
| AC-18a | NIST SP 800-53 Rev 5.2.0 | AC-18 | Wireless Access | Establish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and | a. | Access Control | ||
| AC-18b | NIST SP 800-53 Rev 5.2.0 | AC-18 | Wireless Access | Authorize each type of wireless access to the system prior to allowing such connections. | b. | Access Control | ||
| AC-19(4)(a) | NIST SP 800-53 Rev 5.2.0 | AC-19(4) | Restrictions for Classified Information | Prohibit the use of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official; and | (a) | Access Control | ||
| AC-19(4)(b) | NIST SP 800-53 Rev 5.2.0 | AC-19(4) | Restrictions for Classified Information | Enforce the following restrictions on individuals permitted by the authorizing official to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information: | (b) | Access Control | ||
| AC-19(4)(b)(1) | NIST SP 800-53 Rev 5.2.0 | AC-19(4) | Restrictions for Classified Information | Connection of unclassified mobile devices to classified systems is prohibited; | (1) | Access Control | ||
| AC-19(4)(b)(2) | NIST SP 800-53 Rev 5.2.0 | AC-19(4) | Restrictions for Classified Information | Connection of unclassified mobile devices to unclassified systems requires approval from the authorizing official; | (2) | Access Control | ||
| AC-19(4)(b)(3) | NIST SP 800-53 Rev 5.2.0 | AC-19(4) | Restrictions for Classified Information | Use of internal or external modems or wireless interfaces within the unclassified mobile devices is prohibited; and | (3) | Access Control | ||
| AC-19(4)(b)(4) | NIST SP 800-53 Rev 5.2.0 | AC-19(4) | Restrictions for Classified Information | Unclassified mobile devices and the information stored on those devices are subject to random reviews and inspections by {{ insert: param, ac-19.04_odp.01 }} , and if classified information is found, the incident handling policy is followed. | (4) | Access Control | Unclassified mobile devices and the information stored on those devices are subject to random reviews and inspections by [Assignment: organization-defined security officials] , and if classified information is found, the incident handling policy is followed. | security officials |
| AC-19(4)(c) | NIST SP 800-53 Rev 5.2.0 | AC-19(4) | Restrictions for Classified Information | Restrict the connection of classified mobile devices to classified systems in accordance with {{ insert: param, ac-19.04_odp.02 }}. | (c) | Access Control | Restrict the connection of classified mobile devices to classified systems in accordance with [Assignment: organization-defined security policies]. | security policies |
| AC-19(5) | NIST SP 800-53 Rev 5.2.0 | AC-19(5) | Full Device or Container-based Encryption | Employ {{ insert: param, ac-19.05_odp.01 }} to protect the confidentiality and integrity of information on {{ insert: param, ac-19.05_odp.02 }}. | Access Control | Employ [Selection: full-device encryption; container-based encryption] to protect the confidentiality and integrity of information on [Assignment: organization-defined mobile devices]. | full-device encryption or container-based encryption; mobile devices | |
| AC-19a | NIST SP 800-53 Rev 5.2.0 | AC-19 | Access Control for Mobile Devices | Establish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas; and | a. | Access Control | ||
| AC-19b | NIST SP 800-53 Rev 5.2.0 | AC-19 | Access Control for Mobile Devices | Authorize the connection of mobile devices to organizational systems. | b. | Access Control | ||
| AC-20(1) | NIST SP 800-53 Rev 5.2.0 | AC-20(1) | Limits on Authorized Use | Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after: | Access Control | |||
| AC-20(1)(a) | NIST SP 800-53 Rev 5.2.0 | AC-20(1) | Limits on Authorized Use | Verification of the implementation of controls on the external system as specified in the organization’s security and privacy policies and security and privacy plans; or | (a) | Access Control | ||
| AC-20(1)(b) | NIST SP 800-53 Rev 5.2.0 | AC-20(1) | Limits on Authorized Use | Retention of approved system connection or processing agreements with the organizational entity hosting the external system. | (b) | Access Control | ||
| AC-20(2) | NIST SP 800-53 Rev 5.2.0 | AC-20(2) | Portable Storage Devices — Restricted Use | Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems using {{ insert: param, ac-20.02_odp }}. | Access Control | Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems using [Assignment: organization-defined restrictions]. | restrictions | |
| AC-20(3) | NIST SP 800-53 Rev 5.2.0 | AC-20(3) | Non-organizationally Owned Systems — Restricted Use | Restrict the use of non-organizationally owned systems or system components to process, store, or transmit organizational information using {{ insert: param, ac-20.03_odp }}. | Access Control | Restrict the use of non-organizationally owned systems or system components to process, store, or transmit organizational information using [Assignment: organization-defined restrictions]. | restrictions | |
| AC-20(4) | NIST SP 800-53 Rev 5.2.0 | AC-20(4) | Network Accessible Storage Devices — Prohibited Use | Prohibit the use of {{ insert: param, ac-20.04_odp }} in external systems. | Access Control | Prohibit the use of [Assignment: organization-defined network-accessible storage devices] in external systems. | network-accessible storage devices | |
| AC-20(5) | NIST SP 800-53 Rev 5.2.0 | AC-20(5) | Portable Storage Devices — Prohibited Use | Prohibit the use of organization-controlled portable storage devices by authorized individuals on external systems. | Access Control | |||
| AC-20a | NIST SP 800-53 Rev 5.2.0 | AC-20 | Use of External Systems | {{ insert: param, ac-20_odp.01 }} , consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to: | a. | Access Control | [Selection (one or more): establish [Assignment: organization-defined terms and conditions]; identify [Assignment: organization-defined controls asserted]] , consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to: | establish [Assignment: organization-defined terms and conditions] or identify [Assignment: organization-defined controls asserted] |
| AC-20a1 | NIST SP 800-53 Rev 5.2.0 | AC-20 | Use of External Systems | Access the system from external systems; and | 1. | Access Control | ||
| AC-20a2 | NIST SP 800-53 Rev 5.2.0 | AC-20 | Use of External Systems | Process, store, or transmit organization-controlled information using external systems; or | 2. | Access Control | ||
| AC-20b | NIST SP 800-53 Rev 5.2.0 | AC-20 | Use of External Systems | Prohibit the use of {{ insert: param, ac-20_odp.04 }}. | b. | Access Control | Prohibit the use of [Assignment: organization-defined prohibited types of external systems]. | prohibited types of external systems |
| AC-21(1) | NIST SP 800-53 Rev 5.2.0 | AC-21(1) | Automated Decision Support | Employ {{ insert: param, ac-21.01_odp }} to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared. | Access Control | Employ [Assignment: organization-defined automated mechanisms] to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared. | automated mechanisms | |
| AC-21(2) | NIST SP 800-53 Rev 5.2.0 | AC-21(2) | Information Search and Retrieval | Implement information search and retrieval services that enforce {{ insert: param, ac-21.02_odp }}. | Access Control | Implement information search and retrieval services that enforce [Assignment: organization-defined information-sharing restrictions]. | information-sharing restrictions | |
| AC-21a | NIST SP 800-53 Rev 5.2.0 | AC-21 | Information Sharing | Enable authorized users to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for {{ insert: param, ac-21_odp.01 }} ; and | a. | Access Control | Enable authorized users to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for [Assignment: organization-defined information-sharing circumstances] ; and | information-sharing circumstances |
| AC-21b | NIST SP 800-53 Rev 5.2.0 | AC-21 | Information Sharing | Employ {{ insert: param, ac-21_odp.02 }} to assist users in making information sharing and collaboration decisions. | b. | Access Control | Employ [Assignment: organization-defined automated mechanisms] to assist users in making information sharing and collaboration decisions. | automated mechanisms |
| AC-22a | NIST SP 800-53 Rev 5.2.0 | AC-22 | Publicly Accessible Content | Designate individuals authorized to make information publicly accessible; | a. | Access Control | ||
| AC-22b | NIST SP 800-53 Rev 5.2.0 | AC-22 | Publicly Accessible Content | Train authorized individuals to ensure that publicly accessible information does not contain nonpublic information; | b. | Access Control | ||
| AC-22c | NIST SP 800-53 Rev 5.2.0 | AC-22 | Publicly Accessible Content | Review the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included; and | c. | Access Control | ||
| AC-22d | NIST SP 800-53 Rev 5.2.0 | AC-22 | Publicly Accessible Content | Review the content on the publicly accessible system for nonpublic information {{ insert: param, ac-22_odp }} and remove such information, if discovered. | d. | Access Control | Review the content on the publicly accessible system for nonpublic information [Assignment: organization-defined frequency] and remove such information, if discovered. | frequency |
| AC-23 | NIST SP 800-53 Rev 5.2.0 | AC-23 | Data Mining Protection | Employ {{ insert: param, ac-23_odp.01 }} for {{ insert: param, ac-23_odp.02 }} to detect and protect against unauthorized data mining. | Access Control | Employ [Assignment: organization-defined techniques] for [Assignment: organization-defined data storage objects] to detect and protect against unauthorized data mining. | techniques; data storage objects | |
| AC-24 | NIST SP 800-53 Rev 5.2.0 | AC-24 | Access Control Decisions | {{ insert: param, ac-24_odp.01 }} to ensure {{ insert: param, ac-24_odp.02 }} are applied to each access request prior to access enforcement. | Access Control | [Selection (one or more): establish procedures; implement mechanisms] to ensure [Assignment: organization-defined access control decisions] are applied to each access request prior to access enforcement. | establish procedures or implement mechanisms; access control decisions | |
| AC-24(1) | NIST SP 800-53 Rev 5.2.0 | AC-24(1) | Transmit Access Authorization Information | Transmit {{ insert: param, ac-24.01_odp.01 }} using {{ insert: param, ac-24.01_odp.02 }} to {{ insert: param, ac-24.01_odp.03 }} that enforce access control decisions. | Access Control | Transmit [Assignment: organization-defined access authorization information] using [Assignment: organization-defined controls] to [Assignment: organization-defined systems] that enforce access control decisions. | access authorization information; controls; systems | |
| AC-24(2) | NIST SP 800-53 Rev 5.2.0 | AC-24(2) | No User or Process Identity | Enforce access control decisions based on {{ insert: param, ac-24.2_prm_1 }} that do not include the identity of the user or process acting on behalf of the user. | Access Control | Enforce access control decisions based on [Assignment: organization-defined organization-defined security or privacy attributes] that do not include the identity of the user or process acting on behalf of the user. | organization-defined security or privacy attributes | |
| AC-25 | NIST SP 800-53 Rev 5.2.0 | AC-25 | Reference Monitor | Implement a reference monitor for {{ insert: param, ac-25_odp }} that is tamperproof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured. | Access Control | Implement a reference monitor for [Assignment: organization-defined access control policies] that is tamperproof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured. | access control policies | |
| AT-1a | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | Develop, document, and disseminate to {{ insert: param, at-1_prm_1 }}: | a. | Awareness and Training | Develop, document, and disseminate to [Assignment: organization-defined organization-defined personnel or roles]: | organization-defined personnel or roles |
| AT-1a1 | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | {{ insert: param, at-01_odp.03 }} awareness and training policy that: | 1. | Awareness and Training | [Selection (one or more): organization-level; mission/business process-level; system-level] awareness and training policy that: | organization-level or mission/business process-level or system-level |
| AT-1a1(a) | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and | (a) | Awareness and Training | ||
| AT-1a1(b) | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and | (b) | Awareness and Training | ||
| AT-1a2 | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | Procedures to facilitate the implementation of the awareness and training policy and the associated awareness and training controls; | 2. | Awareness and Training | ||
| AT-1b | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | Designate an {{ insert: param, at-01_odp.04 }} to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and | b. | Awareness and Training | Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and | official |
| AT-1c | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | Review and update the current awareness and training: | c. | Awareness and Training | ||
| AT-1c1 | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | Policy {{ insert: param, at-01_odp.05 }} and following {{ insert: param, at-01_odp.06 }} ; and | 1. | Awareness and Training | Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events] ; and | frequency; events |
| AT-1c2 | NIST SP 800-53 Rev 5.2.0 | AT-1 | Policy and Procedures | Procedures {{ insert: param, at-01_odp.07 }} and following {{ insert: param, at-01_odp.08 }}. | 2. | Awareness and Training | Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | frequency; events |
| AT-2(1) | NIST SP 800-53 Rev 5.2.0 | AT-2(1) | Practical Exercises | Provide practical exercises in literacy training that simulate events and incidents. | Awareness and Training | |||
| AT-2(2) | NIST SP 800-53 Rev 5.2.0 | AT-2(2) | Insider Threat | Provide literacy training on recognizing and reporting potential indicators of insider threat. | Awareness and Training | |||
| AT-2(3) | NIST SP 800-53 Rev 5.2.0 | AT-2(3) | Social Engineering and Mining | Provide literacy training on recognizing and reporting potential and actual instances of social engineering and social mining. | Awareness and Training | |||
| AT-2(4) | NIST SP 800-53 Rev 5.2.0 | AT-2(4) | Suspicious Communications and Anomalous System Behavior | Provide literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using {{ insert: param, at-02.04_odp }}. | Awareness and Training | Provide literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using [Assignment: organization-defined indicators of malicious code]. | indicators of malicious code | |
| AT-2(5) | NIST SP 800-53 Rev 5.2.0 | AT-2(5) | Advanced Persistent Threat | Provide literacy training on the advanced persistent threat. | Awareness and Training | |||
| AT-2(6)(a) | NIST SP 800-53 Rev 5.2.0 | AT-2(6) | Cyber Threat Environment | Provide literacy training on the cyber threat environment; and | (a) | Awareness and Training | ||
| AT-2(6)(b) | NIST SP 800-53 Rev 5.2.0 | AT-2(6) | Cyber Threat Environment | Reflect current cyber threat information in system operations. | (b) | Awareness and Training | ||
| AT-2a | NIST SP 800-53 Rev 5.2.0 | AT-2 | Literacy Training and Awareness | Provide security and privacy literacy training to system users (including managers, senior executives, and contractors): | a. | Awareness and Training | ||
| AT-2a1 | NIST SP 800-53 Rev 5.2.0 | AT-2 | Literacy Training and Awareness | As part of initial training for new users and {{ insert: param, at-2_prm_1 }} thereafter; and | 1. | Awareness and Training | As part of initial training for new users and [Assignment: organization-defined organization-defined frequency] thereafter; and | organization-defined frequency |
| AT-2a2 | NIST SP 800-53 Rev 5.2.0 | AT-2 | Literacy Training and Awareness | When required by system changes or following {{ insert: param, at-2_prm_2 }}; | 2. | Awareness and Training | When required by system changes or following [Assignment: organization-defined organization-defined events]; | organization-defined events |
| AT-2b | NIST SP 800-53 Rev 5.2.0 | AT-2 | Literacy Training and Awareness | Employ the following techniques to increase the security and privacy awareness of system users {{ insert: param, at-02_odp.05 }}; | b. | Awareness and Training | Employ the following techniques to increase the security and privacy awareness of system users [Assignment: organization-defined awareness techniques]; | awareness techniques |
| AT-2c | NIST SP 800-53 Rev 5.2.0 | AT-2 | Literacy Training and Awareness | Update literacy training and awareness content {{ insert: param, at-02_odp.06 }} and following {{ insert: param, at-02_odp.07 }} ; and | c. | Awareness and Training | Update literacy training and awareness content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events] ; and | frequency; events |
| AT-2d | NIST SP 800-53 Rev 5.2.0 | AT-2 | Literacy Training and Awareness | Incorporate lessons learned from internal or external security incidents or breaches into literacy training and awareness techniques. | d. | Awareness and Training | ||
| AT-3(1) | NIST SP 800-53 Rev 5.2.0 | AT-3(1) | Environmental Controls | Provide {{ insert: param, at-03.01_odp.01 }} with initial and {{ insert: param, at-03.01_odp.02 }} training in the employment and operation of environmental controls. | Awareness and Training | Provide [Assignment: organization-defined personnel or roles] with initial and [Assignment: organization-defined frequency] training in the employment and operation of environmental controls. | personnel or roles; frequency | |
| AT-3(2) | NIST SP 800-53 Rev 5.2.0 | AT-3(2) | Physical Security Controls | Provide {{ insert: param, at-03.02_odp.01 }} with initial and {{ insert: param, at-03.02_odp.02 }} training in the employment and operation of physical security controls. | Awareness and Training | Provide [Assignment: organization-defined personnel or roles] with initial and [Assignment: organization-defined frequency] training in the employment and operation of physical security controls. | personnel or roles; frequency | |
| AT-3(3) | NIST SP 800-53 Rev 5.2.0 | AT-3(3) | Practical Exercises | Provide practical exercises in security and privacy training that reinforce training objectives. | Awareness and Training | |||
| AT-3(5) | NIST SP 800-53 Rev 5.2.0 | AT-3(5) | Processing Personally Identifiable Information | Provide {{ insert: param, at-03.05_odp.01 }} with initial and {{ insert: param, at-03.05_odp.02 }} training in the employment and operation of personally identifiable information processing and transparency controls. | Awareness and Training | Provide [Assignment: organization-defined personnel or roles] with initial and [Assignment: organization-defined frequency] training in the employment and operation of personally identifiable information processing and transparency controls. | personnel or roles; frequency | |
| AT-3a | NIST SP 800-53 Rev 5.2.0 | AT-3 | Role-based Training | Provide role-based security and privacy training to personnel with the following roles and responsibilities: {{ insert: param, at-3_prm_1 }}: | a. | Awareness and Training | Provide role-based security and privacy training to personnel with the following roles and responsibilities: [Assignment: organization-defined organization-defined roles and responsibilities]: | organization-defined roles and responsibilities |
| AT-3a1 | NIST SP 800-53 Rev 5.2.0 | AT-3 | Role-based Training | Before authorizing access to the system, information, or performing assigned duties, and {{ insert: param, at-03_odp.03 }} thereafter; and | 1. | Awareness and Training | Before authorizing access to the system, information, or performing assigned duties, and [Assignment: organization-defined frequency] thereafter; and | frequency |
| AT-3a2 | NIST SP 800-53 Rev 5.2.0 | AT-3 | Role-based Training | When required by system changes; | 2. | Awareness and Training | ||
| AT-3b | NIST SP 800-53 Rev 5.2.0 | AT-3 | Role-based Training | Update role-based training content {{ insert: param, at-03_odp.04 }} and following {{ insert: param, at-03_odp.05 }} ; and | b. | Awareness and Training | Update role-based training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events] ; and | frequency; events |
| AT-3c | NIST SP 800-53 Rev 5.2.0 | AT-3 | Role-based Training | Incorporate lessons learned from internal or external security incidents or breaches into role-based training. | c. | Awareness and Training | ||
| AT-4a | NIST SP 800-53 Rev 5.2.0 | AT-4 | Training Records | Document and monitor information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training; and | a. | Awareness and Training | ||
| AT-4b | NIST SP 800-53 Rev 5.2.0 | AT-4 | Training Records | Retain individual training records for {{ insert: param, at-04_odp }}. | b. | Awareness and Training | Retain individual training records for [Assignment: organization-defined time period]. | time period |
| AT-6 | NIST SP 800-53 Rev 5.2.0 | AT-6 | Training Feedback | Provide feedback on organizational training results to the following personnel {{ insert: param, at-06_odp.01 }}: {{ insert: param, at-06_odp.02 }}. | Awareness and Training | Provide feedback on organizational training results to the following personnel [Assignment: organization-defined frequency]: [Assignment: organization-defined personnel]. | frequency; personnel | |
| AU-1a | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | Develop, document, and disseminate to {{ insert: param, au-1_prm_1 }}: | a. | Audit and Accountability | Develop, document, and disseminate to [Assignment: organization-defined organization-defined personnel or roles]: | organization-defined personnel or roles |
| AU-1a1 | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | {{ insert: param, au-01_odp.03 }} audit and accountability policy that: | 1. | Audit and Accountability | [Selection (one or more): organization-level; mission/business process-level; system-level] audit and accountability policy that: | organization-level or mission/business process-level or system-level |
| AU-1a1(a) | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and | (a) | Audit and Accountability | ||
| AU-1a1(b) | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and | (b) | Audit and Accountability | ||
| AU-1a2 | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | Procedures to facilitate the implementation of the audit and accountability policy and the associated audit and accountability controls; | 2. | Audit and Accountability | ||
| AU-1b | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | Designate an {{ insert: param, au-01_odp.04 }} to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and | b. | Audit and Accountability | Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and | official |
| AU-1c | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | Review and update the current audit and accountability: | c. | Audit and Accountability | ||
| AU-1c1 | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | Policy {{ insert: param, au-01_odp.05 }} and following {{ insert: param, au-01_odp.06 }} ; and | 1. | Audit and Accountability | Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events] ; and | frequency; events |
| AU-1c2 | NIST SP 800-53 Rev 5.2.0 | AU-1 | Policy and Procedures | Procedures {{ insert: param, au-01_odp.07 }} and following {{ insert: param, au-01_odp.08 }}. | 2. | Audit and Accountability | Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. | frequency; events |
| AU-2a | NIST SP 800-53 Rev 5.2.0 | AU-2 | Event Logging | Identify the types of events that the system is capable of logging in support of the audit function: {{ insert: param, au-02_odp.01 }}; | a. | Audit and Accountability | Identify the types of events that the system is capable of logging in support of the audit function: [Assignment: organization-defined event types]; | event types |
| AU-2b | NIST SP 800-53 Rev 5.2.0 | AU-2 | Event Logging | Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged; | b. | Audit and Accountability | ||
| AU-2c | NIST SP 800-53 Rev 5.2.0 | AU-2 | Event Logging | Specify the following event types for logging within the system: {{ insert: param, au-2_prm_2 }}; | c. | Audit and Accountability | Specify the following event types for logging within the system: [Assignment: organization-defined organization-defined event types (subset of the event types defined in [AU-2a.](#au-2_smt.a)) along with the frequency of (or situation requiring) logging for each identified event type]; | organization-defined event types (subset of the event types defined in [AU-2a.](#au-2_smt.a)) along with the frequency of (or situation requiring) logging for each identified event type |
| AU-2d | NIST SP 800-53 Rev 5.2.0 | AU-2 | Event Logging | Provide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and | d. | Audit and Accountability | ||
| AU-2e | NIST SP 800-53 Rev 5.2.0 | AU-2 | Event Logging | Review and update the event types selected for logging {{ insert: param, au-02_odp.04 }}. | e. | Audit and Accountability | Review and update the event types selected for logging [Assignment: organization-defined frequency]. | frequency |
| AU-3 | NIST SP 800-53 Rev 5.2.0 | AU-3 | Content of Audit Records | Ensure that audit records contain information that establishes the following: | Audit and Accountability | |||
| AU-3(1) | NIST SP 800-53 Rev 5.2.0 | AU-3(1) | Additional Audit Information | Generate audit records containing the following additional information: {{ insert: param, au-03.01_odp }}. | Audit and Accountability | Generate audit records containing the following additional information: [Assignment: organization-defined additional information]. | additional information | |
| AU-3(3) | NIST SP 800-53 Rev 5.2.0 | AU-3(3) | Limit Personally Identifiable Information Elements | Limit personally identifiable information contained in audit records to the following elements identified in the privacy risk assessment: {{ insert: param, au-03.03_odp }}. | Audit and Accountability | Limit personally identifiable information contained in audit records to the following elements identified in the privacy risk assessment: [Assignment: organization-defined elements]. | elements | |
| AU-3a | NIST SP 800-53 Rev 5.2.0 | AU-3 | Content of Audit Records | What type of event occurred; | a. | Audit and Accountability | ||
| AU-3b | NIST SP 800-53 Rev 5.2.0 | AU-3 | Content of Audit Records | When the event occurred; | b. | Audit and Accountability | ||
| AU-3c | NIST SP 800-53 Rev 5.2.0 | AU-3 | Content of Audit Records | Where the event occurred; | c. | Audit and Accountability | ||
| AU-3d | NIST SP 800-53 Rev 5.2.0 | AU-3 | Content of Audit Records | Source of the event; | d. | Audit and Accountability | ||
| AU-3e | NIST SP 800-53 Rev 5.2.0 | AU-3 | Content of Audit Records | Outcome of the event; and | e. | Audit and Accountability | ||
| AU-3f | NIST SP 800-53 Rev 5.2.0 | AU-3 | Content of Audit Records | Identity of any individuals, subjects, or objects/entities associated with the event. | f. | Audit and Accountability | ||
| AU-4 | NIST SP 800-53 Rev 5.2.0 | AU-4 | Audit Log Storage Capacity | Allocate audit log storage capacity to accommodate {{ insert: param, au-04_odp }}. | Audit and Accountability | Allocate audit log storage capacity to accommodate [Assignment: organization-defined audit log retention requirements]. | audit log retention requirements | |
| AU-4(1) | NIST SP 800-53 Rev 5.2.0 | AU-4(1) | Transfer to Alternate Storage | Transfer audit logs {{ insert: param, au-04.01_odp }} to a different system, system component, or media other than the system or system component conducting the logging. | Audit and Accountability | Transfer audit logs [Assignment: organization-defined frequency] to a different system, system component, or media other than the system or system component conducting the logging. | frequency | |
| AU-5(1) | NIST SP 800-53 Rev 5.2.0 | AU-5(1) | Storage Capacity Warning | Provide a warning to {{ insert: param, au-05.01_odp.01 }} within {{ insert: param, au-05.01_odp.02 }} when allocated audit log storage volume reaches {{ insert: param, au-05.01_odp.03 }} of repository maximum audit log storage capacity. | Audit and Accountability | Provide a warning to [Assignment: organization-defined personnel, roles, and/or locations] within [Assignment: organization-defined time period] when allocated audit log storage volume reaches [Assignment: organization-defined percentage] of repository maximum audit log storage capacity. | personnel, roles, and/or locations; time period; percentage | |
| AU-5(2) | NIST SP 800-53 Rev 5.2.0 | AU-5(2) | Real-time Alerts | Provide an alert within {{ insert: param, au-05.02_odp.01 }} to {{ insert: param, au-05.02_odp.02 }} when the following audit failure events occur: {{ insert: param, au-05.02_odp.03 }}. | Audit and Accountability | Provide an alert within [Assignment: organization-defined real-time period] to [Assignment: organization-defined personnel, roles, and/or locations] when the following audit failure events occur: [Assignment: organization-defined audit logging failure events requiring real-time alerts]. | real-time period; personnel, roles, and/or locations; audit logging failure events requiring real-time alerts | |
| AU-5(3) | NIST SP 800-53 Rev 5.2.0 | AU-5(3) | Configurable Traffic Volume Thresholds | Enforce configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity and {{ insert: param, au-05.03_odp }} network traffic above those thresholds. | Audit and Accountability | Enforce configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity and [Selection (one or more): reject; delay] network traffic above those thresholds. | reject or delay | |
| AU-5(4) | NIST SP 800-53 Rev 5.2.0 | AU-5(4) | Shutdown on Failure | Invoke a {{ insert: param, au-05.04_odp.01 }} in the event of {{ insert: param, au-05.04_odp.02 }} , unless an alternate audit logging capability exists. | Audit and Accountability | Invoke a [Selection (one or more): full system shutdown; partial system shutdown; degraded operational mode with limited mission or business functionality available] in the event of [Assignment: organization-defined audit logging failures] , unless an alternate audit logging capability exists. | full system shutdown or partial system shutdown or degraded operational mode with limited mission or business functionality available; audit logging failures |
Showing the first 400 of 2,022 records. Every record has its own page, with its source and the quoted line that states it; these list the rest.
- Records 1–400164.302 … AU-5(4)
- Records 401–800AU-5(5) … IA-5d
- Records 801–1,200IA-5e … PM-14a1
- Records 1,201–1,600PM-14a2 … SA-17
- Records 1,601–2,000SA-17(1) … SR-3b
- Records 2,001–2,022SR-3c … SR-12
Where this came from
Every record above links the page it was taken from and quotes the sentence that states it. These are the 9 sources this dataset was assembled from.
- ecfr.govhttps://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.302
- ecfr.govhttps://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306
- ecfr.govhttps://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.308
- ecfr.govhttps://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.310
- ecfr.govhttps://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.312
- ecfr.govhttps://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.314
- ecfr.govhttps://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.316
- ecfr.govhttps://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.318
- raw.githubusercontent.comhttps://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json
Machine-readable
- data.jsonThe whole dataset — every record with its source URL and source quote.
- Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
- data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
- How this is made and checkedWhat "verified against source" does and does not mean.
Set your AI assistant up to use this
Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.
{
"mcpServers": {
"referencesource": {
"type": "http",
"url": "https://referencesource.org/mcp"
}
}
}Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project
Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:
When a question needs "Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `security-compliance-controls`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.What each tool does, and the servers built over single registers: Connect your AI assistant.