Records 1–400 — Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words
Records 1 to 400 of 2,022. Each links to its own page, which carries the source URL and the quoted line that states the value.
- 164.302A covered entity or business associate must comply with the applicable standards, implementation specifications, and requirements of this subpart with respect to electronic protect
- 164.306(a)(a) General requirements. Covered entities and business associates must do the following:
- 164.306(a)(1)(1) Ensure the confidentiality, integrity, and availability of all electronic protected health information the covered entity or business associate creates, receives, maintains, or
- 164.306(a)(2)(2) Protect against any reasonably anticipated threats or hazards to the security or integrity of such information.
- 164.306(a)(3)(3) Protect against any reasonably anticipated uses or disclosures of such information that are not permitted or required under subpart E of this part.
- 164.306(a)(4)(4) Ensure compliance with this subpart by its workforce.
- 164.306(b)(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 approp
- 164.306(b)(2)(2) In deciding which security measures to use, a covered entity or business associate must take into account the following factors:
- 164.306(b)(2)(i)(i) The size, complexity, and capabilities of the covered entity or business associate.
- 164.306(b)(2)(ii)(ii) The covered entity's or the business associate's technical infrastructure, hardware, and software security capabilities.
- 164.306(b)(2)(iii)(iii) The costs of security measures.
- 164.306(b)(2)(iv)(iv) The probability and criticality of potential risks to electronic protected health information.
- 164.306(c)(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
- 164.306(d)(d) Implementation specifications. In this subpart:
- 164.306(d)(1)(1) Implementation specifications are required or addressable. If an implementation specification is required, the word “Required” appears in parentheses after the title of the imp
- 164.306(d)(2)(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
- 164.306(d)(3)(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 m
- 164.306(d)(3)(i)(i) Assess whether each implementation specification is a reasonable and appropriate safeguard in its environment, when analyzed with reference to the likely contribution to protec
- 164.306(d)(3)(ii)(ii) As applicable to the covered entity or business associate—
- 164.306(d)(3)(ii)(A)(A) Implement the implementation specification if reasonable and appropriate; or
- 164.306(d)(3)(ii)(B)(B) If implementing the implementation specification is not reasonable and appropriate—
- 164.306(e)(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 an
- 164.308(a)(a) A covered entity or business associate must, in accordance with § 164.306:
- 164.308(a)(1)(i)(1)(i) Standard: Security management process. Implement policies and procedures to prevent, detect, contain, and correct security violations.
- 164.308(a)(1)(ii)(A)(A) Risk analysis (Required). Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electron
- 164.308(a)(1)(ii)(B)(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).
- 164.308(a)(1)(ii)(C)(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
- 164.308(a)(1)(ii)(D)(D) Information system activity review (Required). Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security
- 164.308(a)(2)(2) Standard: Assigned security responsibility. Identify the security official who is responsible for the development and implementation of the policies and procedures required by
- 164.308(a)(3)(i)(3)(i) Standard: Workforce security. Implement policies and procedures to ensure that all members of its workforce have appropriate access to electronic protected health informatio
- 164.308(a)(3)(ii)(A)(A) Authorization and/or supervision (Addressable). Implement procedures for the authorization and/or supervision of workforce members who work with electronic protected health inf
- 164.308(a)(3)(ii)(B)(B) Workforce clearance procedure (Addressable). Implement procedures to determine that the access of a workforce member to electronic protected health information is appropriate.
- 164.308(a)(3)(ii)(C)(C) Termination procedures (Addressable). Implement procedures for terminating access to electronic protected health information when the employment of, or other arrangement with,
- 164.308(a)(4)(i)(4)(i) Standard: Information access management. Implement policies and procedures for authorizing access to electronic protected health information that are consistent with the app
- 164.308(a)(4)(ii)(A)(A) Isolating health care clearinghouse functions (Required). If a health care clearinghouse is part of a larger organization, the clearinghouse must implement policies and procedu
- 164.308(a)(4)(ii)(B)(B) Access authorization (Addressable). Implement policies and procedures for granting access to electronic protected health information, for example, through access to a workstati
- 164.308(a)(4)(ii)(C)(C) Access establishment and modification (Addressable). Implement policies and procedures that, based upon the covered entity's or the business associate's access authorization po
- 164.308(a)(5)(i)(5)(i) Standard: Security awareness and training. Implement a security awareness and training program for all members of its workforce (including management).
- 164.308(a)(5)(ii)(ii) Implementation specifications. Implement:
- 164.308(a)(5)(ii)(A)(A) Security reminders (Addressable). Periodic security updates.
- 164.308(a)(5)(ii)(B)(B) Protection from malicious software (Addressable). Procedures for guarding against, detecting, and reporting malicious software.
- 164.308(a)(5)(ii)(C)(C) Log-in monitoring (Addressable). Procedures for monitoring log-in attempts and reporting discrepancies.
- 164.308(a)(5)(ii)(D)(D) Password management (Addressable). Procedures for creating, changing, and safeguarding passwords.
- 164.308(a)(6)(i)(6)(i) Standard: Security incident procedures. Implement policies and procedures to address security incidents.
- 164.308(a)(6)(ii)(ii) Implementation specification: Response and reporting (Required). Identify and respond to suspected or known security incidents; mitigate, to the extent practicable, harmful ef
- 164.308(a)(7)(i)(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, sys
- 164.308(a)(7)(ii)(A)(A) Data backup plan (Required). Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information.
- 164.308(a)(7)(ii)(B)(B) Disaster recovery plan (Required). Establish (and implement as needed) procedures to restore any loss of data.
- 164.308(a)(7)(ii)(C)(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
- 164.308(a)(7)(ii)(D)(D) Testing and revision procedures (Addressable). Implement procedures for periodic testing and revision of contingency plans.
- 164.308(a)(7)(ii)(E)(E) Applications and data criticality analysis (Addressable). Assess the relative criticality of specific applications and data in support of other contingency plan components.
- 164.308(a)(8)(8) Standard: Evaluation. Perform a periodic technical and nontechnical evaluation, based initially upon the standards implemented under this rule and, subsequently, in response to
- 164.308(b)(1)(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 i
- 164.308(b)(2)(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 onl
- 164.308(b)(3)(3) Implementation specifications: Written contract or other arrangement (Required). Document the satisfactory assurances required by paragraph (b)(1) or (b)(2) of this section thr
- 164.310A covered entity or business associate must, in accordance with § 164.306:
- 164.310(a)(1)(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
- 164.310(a)(2)(i)(i) Contingency operations (Addressable). Establish (and implement as needed) procedures that allow facility access in support of restoration of lost data under the disaster recove
- 164.310(a)(2)(ii)(ii) Facility security plan (Addressable). Implement policies and procedures to safeguard the facility and the equipment therein from unauthorized physical access, tampering, and t
- 164.310(a)(2)(iii)(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, includin
- 164.310(a)(2)(iv)(iv) Maintenance records (Addressable). Implement policies and procedures to document repairs and modifications to the physical components of a facility which are related to securi
- 164.310(b)(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
- 164.310(c)(c) Standard: Workstation security. Implement physical safeguards for all workstations that access electronic protected health information, to restrict access to authorized users.
- 164.310(d)(1)(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
- 164.310(d)(2)(i)(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 w
- 164.310(d)(2)(ii)(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.
- 164.310(d)(2)(iii)(iii) Accountability (Addressable). Maintain a record of the movements of hardware and electronic media and any person responsible therefore.
- 164.310(d)(2)(iv)(iv) Data backup and storage (Addressable). Create a retrievable, exact copy of electronic protected health information, when needed, before movement of equipment.
- 164.312A covered entity or business associate must, in accordance with § 164.306:
- 164.312(a)(1)(a)(1) Standard: Access control. Implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow acces
- 164.312(a)(2)(i)(i) Unique user identification (Required). Assign a unique name and/or number for identifying and tracking user identity.
- 164.312(a)(2)(ii)(ii) Emergency access procedure (Required). Establish (and implement as needed) procedures for obtaining necessary electronic protected health information during an emergency.
- 164.312(a)(2)(iii)(iii) Automatic logoff (Addressable). Implement electronic procedures that terminate an electronic session after a predetermined time of inactivity.
- 164.312(a)(2)(iv)(iv) Encryption and decryption (Addressable). Implement a mechanism to encrypt and decrypt electronic protected health information.
- 164.312(b)(b) Standard: Audit controls. Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic prot
- 164.312(c)(1)(c)(1) Standard: Integrity. Implement policies and procedures to protect electronic protected health information from improper alteration or destruction.
- 164.312(c)(2)(2) Implementation specification: Mechanism to authenticate electronic protected health information (Addressable). Implement electronic mechanisms to corroborate that electronic pr
- 164.312(d)(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.
- 164.312(e)(1)(e)(1) Standard: Transmission security. Implement technical security measures to guard against unauthorized access to electronic protected health information that is being transmit
- 164.312(e)(2)(i)(i) Integrity controls (Addressable). Implement security measures to ensure that electronically transmitted electronic protected health information is not improperly modified witho
- 164.312(e)(2)(ii)(ii) Encryption (Addressable). Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate.
- 164.314(a)(1)(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)
- 164.314(a)(2)(2) Implementation specifications (Required)—(i) Business associate contracts. The contract must provide that the business associate will—
- 164.314(a)(2)(A)(A) Comply with the applicable requirements of this subpart;
- 164.314(a)(2)(A)(B)(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
- 164.314(a)(2)(A)(C)(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.
- 164.314(a)(2)(ii)(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
- 164.314(a)(2)(iii)(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
- 164.314(b)(1)(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)
- 164.314(b)(2)(2) Implementation specifications (Required). The plan documents of the group health plan must be amended to incorporate provisions to require the plan sponsor to—
- 164.314(b)(2)(i)(i) Implement administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of the electronic protec
- 164.314(b)(2)(ii)(ii) Ensure that the adequate separation required by § 164.504(f)(2)(iii) is supported by reasonable and appropriate security measures;
- 164.314(b)(2)(iii)(iii) Ensure that any agent to whom it provides this information agrees to implement reasonable and appropriate security measures to protect the information; and
- 164.314(b)(2)(iv)(iv) Report to the group health plan any security incident of which it becomes aware.
- 164.316A covered entity or business associate must, in accordance with § 164.306:
- 164.316(a)(a) Standard: Policies and procedures. Implement reasonable and appropriate policies and procedures to comply with the standards, implementation specifications, or other requiremen
- 164.316(b)(1)(b)(1) Standard: Documentation. (i) Maintain the policies and procedures implemented to comply with this subpart in written (which may be electronic) form; and
- 164.316(b)(1)(ii)(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.
- 164.316(b)(2)(i)(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, w
- 164.316(b)(2)(ii)(ii) Availability (Required). Make documentation available to those persons responsible for implementing the procedures to which the documentation pertains.
- 164.316(b)(2)(iii)(iii) Updates (Required). Review documentation periodically, and update as needed, in response to environmental or operational changes affecting the security of the electronic prot
- 164.318(a)(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.
- 164.318(a)(2)(2) A small health plan must comply with the applicable requirements of this subpart no later than April 20, 2006.
- 164.318(b)(b) Health care clearinghouse. A health care clearinghouse must comply with the applicable requirements of this subpart no later than April 20, 2005.
- 164.318(c)(c) Health care provider. A covered health care provider must comply with the applicable requirements of this subpart no later than April 20, 2005.
- AC-1aDevelop, document, and disseminate to {{ insert: param, ac-1_prm_1 }}:
- AC-1a1{{ insert: param, ac-01_odp.03 }} access control policy that:
- AC-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- AC-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- AC-1a2Procedures to facilitate the implementation of the access control policy and the associated access controls;
- AC-1bDesignate an {{ insert: param, ac-01_odp.04 }} to manage the development, documentation, and dissemination of the access control policy and procedures; and
- AC-1cReview and update the current access control:
- AC-1c1Policy {{ insert: param, ac-01_odp.05 }} and following {{ insert: param, ac-01_odp.06 }} ; and
- AC-1c2Procedures {{ insert: param, ac-01_odp.07 }} and following {{ insert: param, ac-01_odp.08 }}.
- AC-2(1)Support the management of system accounts using {{ insert: param, ac-02.01_odp }}.
- AC-2(2)Automatically {{ insert: param, ac-02.02_odp.01 }} temporary and emergency accounts after {{ insert: param, ac-02.02_odp.02 }}.
- AC-2(3)Disable accounts within {{ insert: param, ac-02.03_odp.01 }} when the accounts:
- AC-2(3)(a)Have expired;
- AC-2(3)(b)Are no longer associated with a user or individual;
- AC-2(3)(c)Are in violation of organizational policy; or
- AC-2(3)(d)Have been inactive for {{ insert: param, ac-02.03_odp.02 }}.
- AC-2(4)Automatically audit account creation, modification, enabling, disabling, and removal actions.
- AC-2(5)Require that users log out when {{ insert: param, ac-02.05_odp }}.
- AC-2(6)Implement {{ insert: param, ac-02.06_odp }}.
- AC-2(7)(a)Establish and administer privileged user accounts in accordance with {{ insert: param, ac-02.07_odp }};
- AC-2(7)(b)Monitor privileged role or attribute assignments;
- AC-2(7)(c)Monitor changes to roles or attributes; and
- AC-2(7)(d)Revoke access when privileged role or attribute assignments are no longer appropriate.
- AC-2(8)Create, activate, manage, and deactivate {{ insert: param, ac-02.08_odp }} dynamically.
- AC-2(9)Only permit the use of shared and group accounts that meet {{ insert: param, ac-02.09_odp }}.
- AC-2(11)Enforce {{ insert: param, ac-02.11_odp.01 }} for {{ insert: param, ac-02.11_odp.02 }}.
- AC-2(12)(a)Monitor system accounts for {{ insert: param, ac-02.12_odp.01 }} ; and
- AC-2(12)(b)Report atypical usage of system accounts to {{ insert: param, ac-02.12_odp.02 }}.
- AC-2(13)Disable accounts of individuals within {{ insert: param, ac-02.13_odp.01 }} of discovery of {{ insert: param, ac-02.13_odp.02 }}.
- AC-2aDefine and document the types of accounts allowed and specifically prohibited for use within the system;
- AC-2bAssign account managers;
- AC-2cRequire {{ insert: param, ac-02_odp.01 }} for group and role membership;
- AC-2d1Authorized users of the system;
- AC-2d2Group and role membership; and
- AC-2d3Access authorizations (i.e., privileges) and {{ insert: param, ac-02_odp.02 }} for each account;
- AC-2eRequire approvals by {{ insert: param, ac-02_odp.03 }} for requests to create accounts;
- AC-2fCreate, enable, modify, disable, and remove accounts in accordance with {{ insert: param, ac-02_odp.04 }};
- AC-2gMonitor the use of accounts;
- AC-2hNotify account managers and {{ insert: param, ac-02_odp.05 }} within:
- AC-2h1{{ insert: param, ac-02_odp.06 }} when accounts are no longer required;
- AC-2h2{{ insert: param, ac-02_odp.07 }} when users are terminated or transferred; and
- AC-2h3{{ insert: param, ac-02_odp.08 }} when system usage or need-to-know changes for an individual;
- AC-2iAuthorize access to the system based on:
- AC-2i1A valid access authorization;
- AC-2i2Intended system usage; and
- AC-2i3{{ insert: param, ac-02_odp.09 }};
- AC-2jReview accounts for compliance with account management requirements {{ insert: param, ac-02_odp.10 }};
- AC-2kEstablish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and
- AC-2lAlign account management processes with personnel termination and transfer processes.
- AC-3Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
- AC-3(2)Enforce dual authorization for {{ insert: param, ac-03.02_odp }}.
- AC-3(3)Enforce {{ insert: param, ac-3.3_prm_1 }} over the set of covered subjects and objects specified in the policy, and where the policy:
- AC-3(3)(a)Is uniformly enforced across the covered subjects and objects within the system;
- AC-3(3)(b)Specifies that a subject that has been granted access to information is constrained from doing any of the following;
- AC-3(3)(b)(1)Passing the information to unauthorized subjects or objects;
- AC-3(3)(b)(2)Granting its privileges to other subjects;
- AC-3(3)(b)(3)Changing one or more security attributes (specified by the policy) on subjects, objects, the system, or system components;
- AC-3(3)(b)(4)Choosing the security attributes and attribute values (specified by the policy) to be associated with newly created or modified objects; and
- AC-3(3)(b)(5)Changing the rules governing access control; and
- AC-3(3)(c)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
- AC-3(4)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
- AC-3(4)(a)Pass the information to any other subjects or objects;
- AC-3(4)(b)Grant its privileges to other subjects;
- AC-3(4)(c)Change security attributes on subjects, objects, the system, or the system’s components;
- AC-3(4)(d)Choose the security attributes to be associated with newly created or revised objects; or
- AC-3(4)(e)Change the rules governing access control.
- AC-3(5)Prevent access to {{ insert: param, ac-03.05_odp }} except during secure, non-operable system states.
- AC-3(7)Enforce a role-based access control policy over defined subjects and objects and control access based upon {{ insert: param, ac-3.7_prm_1 }}.
- AC-3(8)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 }}.
- AC-3(9)Release information outside of the system only if:
- AC-3(9)(a)The receiving {{ insert: param, ac-03.09_odp.01 }} provides {{ insert: param, ac-03.09_odp.02 }} ; and
- AC-3(9)(b){{ insert: param, ac-03.09_odp.03 }} are used to validate the appropriateness of the information designated for release.
- AC-3(10)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 }}.
- AC-3(11)Restrict access to data repositories containing {{ insert: param, ac-03.11_odp }}.
- AC-3(12)(a)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 }};
- AC-3(12)(b)Provide an enforcement mechanism to prevent unauthorized access; and
- AC-3(12)(c)Approve access changes after initial installation of the application.
- AC-3(13)Enforce attribute-based access control policy over defined subjects and objects and control access based upon {{ insert: param, ac-03.13_odp }}.
- AC-3(14)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
- AC-3(15)(a)Enforce {{ insert: param, ac-3.15_prm_1 }} over the set of covered subjects and objects specified in the policy; and
- AC-3(15)(b)Enforce {{ insert: param, ac-3.15_prm_2 }} over the set of covered subjects and objects specified in the policy.
- AC-4Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on {{ insert: param, ac-04_odp }}.
- AC-4(1)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.
- AC-4(2)Use protected processing domains to enforce {{ insert: param, ac-04.02_odp }} as a basis for flow control decisions.
- AC-4(3)Enforce {{ insert: param, ac-04.03_odp }}.
- AC-4(4)Prevent encrypted information from bypassing {{ insert: param, ac-04.04_odp.01 }} by {{ insert: param, ac-04.04_odp.02 }}.
- AC-4(5)Enforce {{ insert: param, ac-04.05_odp }} on embedding data types within other data types.
- AC-4(6)Enforce information flow control based on {{ insert: param, ac-04.06_odp }}.
- AC-4(7)Enforce one-way information flows through hardware-based flow control mechanisms.
- AC-4(8)(a)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
- AC-4(8)(b){{ insert: param, ac-04.08_odp.05 }} data after a filter processing failure in accordance with {{ insert: param, ac-4.8_prm_4 }}.
- AC-4(9)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 }}.
- AC-4(10)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 }}.
- AC-4(11)Provide the capability for privileged administrators to configure {{ insert: param, ac-4.11_prm_1 }} to support different security or privacy policies.
- AC-4(12)When transferring information between different security domains, use {{ insert: param, ac-04.12_odp }} to validate data essential for information flow decisions.
- AC-4(13)When transferring information between different security domains, decompose information into {{ insert: param, ac-04.13_odp }} for submission to policy enforcement mechanisms.
- AC-4(14)When transferring information between different security domains, implement {{ insert: param, ac-4.14_prm_1 }} requiring fully enumerated formats that restrict data structure and c
- AC-4(15)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
- AC-4(17)Uniquely identify and authenticate source and destination points by {{ insert: param, ac-04.17_odp }} for information transfer.
- AC-4(19)When transferring information between different security domains, implement {{ insert: param, ac-4.19_prm_1 }} on metadata.
- AC-4(20)Employ {{ insert: param, ac-04.20_odp.01 }} to control the flow of {{ insert: param, ac-04.20_odp.02 }} across security domains.
- AC-4(21)Separate information flows logically or physically using {{ insert: param, ac-4.21_prm_1 }} to accomplish {{ insert: param, ac-04.21_odp.03 }}.
- AC-4(22)Provide access from a single device to computing platforms, applications, or data residing in multiple different security domains, while preventing information flow between the dif
- AC-4(23)When transferring information between different security domains, modify non-releasable information by implementing {{ insert: param, ac-04.23_odp }}.
- AC-4(24)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
- AC-4(25)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.0
- AC-4(26)When transferring information between different security domains, record and audit content filtering actions and results for the information being filtered.
- AC-4(27)When transferring information between different security domains, implement content filtering solutions that provide redundant and independent filtering mechanisms for each data ty
- AC-4(28)When transferring information between different security domains, implement a linear content filter pipeline that is enforced with discretionary and mandatory access controls.
- AC-4(29)When transferring information between different security domains, employ content filter orchestration engines to ensure that:
- AC-4(29)(a)Content filtering mechanisms successfully complete execution without errors; and
- AC-4(29)(b)Content filtering actions occur in the correct order and comply with {{ insert: param, ac-04.29_odp }}.
- AC-4(30)When transferring information between different security domains, implement content filtering mechanisms using multiple processes.
- AC-4(31)When transferring information between different security domains, prevent the transfer of failed content to the receiving domain.
- AC-4(32)When transferring information between different security domains, the process that transfers information between filter pipelines:
- AC-4(32)(a)Does not filter message content;
- AC-4(32)(b)Validates filtering metadata;
- AC-4(32)(c)Ensures the content associated with the filtering metadata has successfully completed filtering; and
- AC-4(32)(d)Transfers the content to the destination filter pipeline.
- AC-5aIdentify and document {{ insert: param, ac-05_odp }} ; and
- AC-5bDefine system access authorizations to support separation of duties.
- AC-6Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organization
- AC-6(1)Authorize access for {{ insert: param, ac-06.01_odp.01 }} to:
- AC-6(1)(a){{ insert: param, ac-6.1_prm_2 }} ; and
- AC-6(1)(b){{ insert: param, ac-06.01_odp.05 }}.
- AC-6(2)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.
- AC-6(3)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 t
- AC-6(4)Provide separate processing domains to enable finer-grained allocation of user privileges.
- AC-6(5)Restrict privileged accounts on the system to {{ insert: param, ac-06.05_odp }}.
- AC-6(6)Prohibit privileged access to the system by non-organizational users.
- AC-6(7)(a)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
- AC-6(7)(b)Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs.
- AC-6(8)Prevent the following software from executing at higher privilege levels than users executing the software: {{ insert: param, ac-06.08_odp }}.
- AC-6(9)Log the execution of privileged functions.
- AC-6(10)Prevent non-privileged users from executing privileged functions.
- AC-7(2)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, unsuccessf
- AC-7(3)Limit the number of unsuccessful biometric logon attempts to {{ insert: param, ac-07.03_odp }}.
- AC-7(4)(a)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
- AC-7(4)(b)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.
- AC-7aEnforce 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
- AC-7bAutomatically {{ insert: param, ac-07_odp.03 }} when the maximum number of unsuccessful attempts is exceeded.
- AC-8aDisplay {{ 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
- AC-8a1Users are accessing a U.S. Government system;
- AC-8a2System usage may be monitored, recorded, and subject to audit;
- AC-8a3Unauthorized use of the system is prohibited and subject to criminal and civil penalties; and
- AC-8a4Use of the system indicates consent to monitoring and recording;
- AC-8bRetain 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
- AC-8cFor publicly accessible systems:
- AC-8c1Display system use information {{ insert: param, ac-08_odp.02 }} , before granting further access to the publicly accessible system;
- AC-8c2Display references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and
- AC-8c3Include a description of the authorized uses of the system.
- AC-9Notify the user, upon successful logon to the system, of the date and time of the last logon.
- AC-9(1)Notify the user, upon successful logon, of the number of unsuccessful logon attempts since the last successful logon.
- AC-9(2)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 }}.
- AC-9(3)Notify the user, upon successful logon, of changes to {{ insert: param, ac-09.03_odp.01 }} during {{ insert: param, ac-09.03_odp.02 }}.
- AC-9(4)Notify the user, upon successful logon, of the following additional information: {{ insert: param, ac-09.04_odp }}.
- AC-10Limit the number of concurrent sessions for each {{ insert: param, ac-10_odp.01 }} to {{ insert: param, ac-10_odp.02 }}.
- AC-11(1)Conceal, via the device lock, information previously visible on the display with a publicly viewable image.
- AC-11aPrevent further access to the system by {{ insert: param, ac-11_odp.01 }} ; and
- AC-11bRetain the device lock until the user reestablishes access using established identification and authentication procedures.
- AC-12Automatically terminate a user session after {{ insert: param, ac-12_odp }}.
- AC-12(1)Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to {{ insert: param, ac-12.01_odp }}.
- AC-12(2)Display an explicit logout message to users indicating the termination of authenticated communications sessions.
- AC-12(3)Display an explicit message to users indicating that the session will end in {{ insert: param, ac-12.03_odp }}.
- AC-14aIdentify {{ insert: param, ac-14_odp }} that can be performed on the system without identification or authentication consistent with organizational mission and business functions;
- AC-14bDocument and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication.
- AC-16(1)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 creat
- AC-16(2)Provide authorized individuals (or processes acting on behalf of individuals) the capability to define or change the value of associated security and privacy attributes.
- AC-16(3)Maintain the association and integrity of {{ insert: param, ac-16.3_prm_1 }} to {{ insert: param, ac-16.3_prm_2 }}.
- AC-16(4)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 individua
- AC-16(5)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 {{
- AC-16(6)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
- AC-16(7)Provide a consistent interpretation of security and privacy attributes transmitted between distributed system components.
- AC-16(8)Implement {{ insert: param, ac-16.8_prm_1 }} in associating security and privacy attributes to information.
- AC-16(9)Change security and privacy attributes associated with information only via regrading mechanisms validated using {{ insert: param, ac-16.9_prm_1 }}.
- AC-16(10)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.
- AC-16aProvide 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;
- AC-16bEnsure that the attribute associations are made and retained with the information;
- AC-16cEstablish 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-1
- AC-16dDetermine the following permitted attribute values or ranges for each of the established attributes: {{ insert: param, ac-16_odp.09 }};
- AC-16eAudit changes to attributes; and
- AC-16fReview {{ insert: param, ac-16_prm_6 }} for applicability {{ insert: param, ac-16_prm_7 }}.
- AC-17(1)Employ automated mechanisms to monitor and control remote access methods.
- AC-17(2)Implement cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions.
- AC-17(3)Route remote accesses through authorized and managed network access control points.
- AC-17(4)(a)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 followin
- AC-17(4)(b)Document the rationale for remote access in the security plan for the system.
- AC-17(6)Protect information about remote access mechanisms from unauthorized use and disclosure.
- AC-17(9)Provide the capability to disconnect or disable remote access to the system within {{ insert: param, ac-17.09_odp }}.
- AC-17(10)Implement {{ insert: param, ac-17.10_odp.01 }} to authenticate {{ insert: param, ac-17.10_odp.02 }}.
- AC-17aEstablish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and
- AC-17bAuthorize each type of remote access to the system prior to allowing such connections.
- AC-18(1)Protect wireless access to the system using authentication of {{ insert: param, ac-18.01_odp }} and encryption.
- AC-18(3)Disable, when not intended for use, wireless networking capabilities embedded within system components prior to issuance and deployment.
- AC-18(4)Identify and explicitly authorize users allowed to independently configure wireless networking capabilities.
- AC-18(5)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
- AC-18aEstablish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and
- AC-18bAuthorize each type of wireless access to the system prior to allowing such connections.
- AC-19(4)(a)Prohibit the use of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information unless specifically permitted by the au
- AC-19(4)(b)Enforce the following restrictions on individuals permitted by the authorizing official to use unclassified mobile devices in facilities containing systems processing, storing, or
- AC-19(4)(b)(1)Connection of unclassified mobile devices to classified systems is prohibited;
- AC-19(4)(b)(2)Connection of unclassified mobile devices to unclassified systems requires approval from the authorizing official;
- AC-19(4)(b)(3)Use of internal or external modems or wireless interfaces within the unclassified mobile devices is prohibited; and
- AC-19(4)(b)(4)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 in
- AC-19(4)(c)Restrict the connection of classified mobile devices to classified systems in accordance with {{ insert: param, ac-19.04_odp.02 }}.
- AC-19(5)Employ {{ insert: param, ac-19.05_odp.01 }} to protect the confidentiality and integrity of information on {{ insert: param, ac-19.05_odp.02 }}.
- AC-19aEstablish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of c
- AC-19bAuthorize the connection of mobile devices to organizational systems.
- AC-20(1)Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after:
- AC-20(1)(a)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
- AC-20(1)(b)Retention of approved system connection or processing agreements with the organizational entity hosting the external system.
- AC-20(2)Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems using {{ insert: param, ac-20.02_odp }}.
- AC-20(3)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 }}.
- AC-20(4)Prohibit the use of {{ insert: param, ac-20.04_odp }} in external systems.
- AC-20(5)Prohibit the use of organization-controlled portable storage devices by authorized individuals on external systems.
- AC-20a{{ insert: param, ac-20_odp.01 }} , consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing au
- AC-20a1Access the system from external systems; and
- AC-20a2Process, store, or transmit organization-controlled information using external systems; or
- AC-20bProhibit the use of {{ insert: param, ac-20_odp.04 }}.
- AC-21(1)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
- AC-21(2)Implement information search and retrieval services that enforce {{ insert: param, ac-21.02_odp }}.
- AC-21aEnable 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
- AC-21bEmploy {{ insert: param, ac-21_odp.02 }} to assist users in making information sharing and collaboration decisions.
- AC-22aDesignate individuals authorized to make information publicly accessible;
- AC-22bTrain authorized individuals to ensure that publicly accessible information does not contain nonpublic information;
- AC-22cReview the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included; and
- AC-22dReview the content on the publicly accessible system for nonpublic information {{ insert: param, ac-22_odp }} and remove such information, if discovered.
- AC-23Employ {{ insert: param, ac-23_odp.01 }} for {{ insert: param, ac-23_odp.02 }} to detect and protect against unauthorized data mining.
- AC-24{{ insert: param, ac-24_odp.01 }} to ensure {{ insert: param, ac-24_odp.02 }} are applied to each access request prior to access enforcement.
- AC-24(1)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.
- AC-24(2)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.
- AC-25Implement 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 wh
- AT-1aDevelop, document, and disseminate to {{ insert: param, at-1_prm_1 }}:
- AT-1a1{{ insert: param, at-01_odp.03 }} awareness and training policy that:
- AT-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- AT-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- AT-1a2Procedures to facilitate the implementation of the awareness and training policy and the associated awareness and training controls;
- AT-1bDesignate an {{ insert: param, at-01_odp.04 }} to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and
- AT-1cReview and update the current awareness and training:
- AT-1c1Policy {{ insert: param, at-01_odp.05 }} and following {{ insert: param, at-01_odp.06 }} ; and
- AT-1c2Procedures {{ insert: param, at-01_odp.07 }} and following {{ insert: param, at-01_odp.08 }}.
- AT-2(1)Provide practical exercises in literacy training that simulate events and incidents.
- AT-2(2)Provide literacy training on recognizing and reporting potential indicators of insider threat.
- AT-2(3)Provide literacy training on recognizing and reporting potential and actual instances of social engineering and social mining.
- AT-2(4)Provide literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using {{ insert: param, at-02.04_odp }}.
- AT-2(5)Provide literacy training on the advanced persistent threat.
- AT-2(6)(a)Provide literacy training on the cyber threat environment; and
- AT-2(6)(b)Reflect current cyber threat information in system operations.
- AT-2aProvide security and privacy literacy training to system users (including managers, senior executives, and contractors):
- AT-2a1As part of initial training for new users and {{ insert: param, at-2_prm_1 }} thereafter; and
- AT-2a2When required by system changes or following {{ insert: param, at-2_prm_2 }};
- AT-2bEmploy the following techniques to increase the security and privacy awareness of system users {{ insert: param, at-02_odp.05 }};
- AT-2cUpdate literacy training and awareness content {{ insert: param, at-02_odp.06 }} and following {{ insert: param, at-02_odp.07 }} ; and
- AT-2dIncorporate lessons learned from internal or external security incidents or breaches into literacy training and awareness techniques.
- AT-3(1)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.
- AT-3(2)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.
- AT-3(3)Provide practical exercises in security and privacy training that reinforce training objectives.
- AT-3(5)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 p
- AT-3aProvide role-based security and privacy training to personnel with the following roles and responsibilities: {{ insert: param, at-3_prm_1 }}:
- AT-3a1Before authorizing access to the system, information, or performing assigned duties, and {{ insert: param, at-03_odp.03 }} thereafter; and
- AT-3a2When required by system changes;
- AT-3bUpdate role-based training content {{ insert: param, at-03_odp.04 }} and following {{ insert: param, at-03_odp.05 }} ; and
- AT-3cIncorporate lessons learned from internal or external security incidents or breaches into role-based training.
- AT-4aDocument and monitor information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training;
- AT-4bRetain individual training records for {{ insert: param, at-04_odp }}.
- AT-6Provide feedback on organizational training results to the following personnel {{ insert: param, at-06_odp.01 }}: {{ insert: param, at-06_odp.02 }}.
- AU-1aDevelop, document, and disseminate to {{ insert: param, au-1_prm_1 }}:
- AU-1a1{{ insert: param, au-01_odp.03 }} audit and accountability policy that:
- AU-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- AU-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- AU-1a2Procedures to facilitate the implementation of the audit and accountability policy and the associated audit and accountability controls;
- AU-1bDesignate an {{ insert: param, au-01_odp.04 }} to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and
- AU-1cReview and update the current audit and accountability:
- AU-1c1Policy {{ insert: param, au-01_odp.05 }} and following {{ insert: param, au-01_odp.06 }} ; and
- AU-1c2Procedures {{ insert: param, au-01_odp.07 }} and following {{ insert: param, au-01_odp.08 }}.
- AU-2aIdentify the types of events that the system is capable of logging in support of the audit function: {{ insert: param, au-02_odp.01 }};
- AU-2bCoordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged;
- AU-2cSpecify the following event types for logging within the system: {{ insert: param, au-2_prm_2 }};
- AU-2dProvide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and
- AU-2eReview and update the event types selected for logging {{ insert: param, au-02_odp.04 }}.
- AU-3Ensure that audit records contain information that establishes the following:
- AU-3(1)Generate audit records containing the following additional information: {{ insert: param, au-03.01_odp }}.
- AU-3(3)Limit personally identifiable information contained in audit records to the following elements identified in the privacy risk assessment: {{ insert: param, au-03.03_odp }}.
- AU-3aWhat type of event occurred;
- AU-3bWhen the event occurred;
- AU-3cWhere the event occurred;
- AU-3dSource of the event;
- AU-3eOutcome of the event; and
- AU-3fIdentity of any individuals, subjects, or objects/entities associated with the event.
- AU-4Allocate audit log storage capacity to accommodate {{ insert: param, au-04_odp }}.
- AU-4(1)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.
- AU-5(1)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
- AU-5(2)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.0
- AU-5(3)Enforce configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity and {{ insert: param, au-05.03_odp }} network traffic above th
- AU-5(4)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.
All of Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words · records 401 on →