Records 401–800 — Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words
Records 401 to 800 of 2,022. Each links to its own page, which carries the source URL and the quoted line that states the value.
- AU-5(5)Provide an alternate audit logging capability in the event of a failure in primary audit logging capability that implements {{ insert: param, au-05.05_odp }}.
- AU-5aAlert {{ insert: param, au-05_odp.01 }} within {{ insert: param, au-05_odp.02 }} in the event of an audit logging process failure; and
- AU-5bTake the following additional actions: {{ insert: param, au-05_odp.03 }}.
- AU-6(1)Integrate audit record review, analysis, and reporting processes using {{ insert: param, au-06.01_odp }}.
- AU-6(3)Analyze and correlate audit records across different repositories to gain organization-wide situational awareness.
- AU-6(4)Provide and implement the capability to centrally review and analyze audit records from multiple components within the system.
- AU-6(5)Integrate analysis of audit records with analysis of {{ insert: param, au-06.05_odp.01 }} to further enhance the ability to identify inappropriate or unusual activity.
- AU-6(6)Correlate information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or
- AU-6(7)Specify the permitted actions for each {{ insert: param, au-06.07_odp }} associated with the review, analysis, and reporting of audit record information.
- AU-6(8)Perform a full text analysis of logged privileged commands in a physically distinct component or subsystem of the system, or other system that is dedicated to that analysis.
- AU-6(9)Correlate information from nontechnical sources with audit record information to enhance organization-wide situational awareness.
- AU-6aReview and analyze system audit records {{ insert: param, au-06_odp.01 }} for indications of {{ insert: param, au-06_odp.02 }} and the potential impact of the inappropriate or unus
- AU-6bReport findings to {{ insert: param, au-06_odp.03 }} ; and
- AU-6cAdjust the level of audit record review, analysis, and reporting within the system when there is a change in risk based on law enforcement information, intelligence information, or
- AU-7Provide and implement an audit record reduction and report generation capability that:
- AU-7(1)Provide and implement the capability to process, sort, and search audit records for events of interest based on the following content: {{ insert: param, au-07.01_odp }}.
- AU-7aSupports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents; and
- AU-7bDoes not alter the original content or time ordering of audit records.
- AU-8aUse internal system clocks to generate time stamps for audit records; and
- AU-8bRecord time stamps for audit records that meet {{ insert: param, au-08_odp }} and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Tim
- AU-9(1)Write audit trails to hardware-enforced, write-once media.
- AU-9(2)Store audit records {{ insert: param, au-09.02_odp }} in a repository that is part of a physically different system or system component than the system or component being audited.
- AU-9(3)Implement cryptographic mechanisms to protect the integrity of audit information and audit tools.
- AU-9(4)Authorize access to management of audit logging functionality to only {{ insert: param, au-09.04_odp }}.
- AU-9(5)Enforce dual authorization for {{ insert: param, au-09.05_odp.01 }} of {{ insert: param, au-09.05_odp.02 }}.
- AU-9(6)Authorize read-only access to audit information to {{ insert: param, au-09.06_odp }}.
- AU-9(7)Store audit information on a component running a different operating system than the system or component being audited.
- AU-9aProtect audit information and audit logging tools from unauthorized access, modification, and deletion; and
- AU-9bAlert {{ insert: param, au-09_odp }} upon detection of unauthorized access, modification, or deletion of audit information.
- AU-10Provide irrefutable evidence that an individual (or process acting on behalf of an individual) has performed {{ insert: param, au-10_odp }}.
- AU-10(1)(a)Bind the identity of the information producer with the information to {{ insert: param, au-10.01_odp }} ; and
- AU-10(1)(b)Provide the means for authorized individuals to determine the identity of the producer of the information.
- AU-10(2)(a)Validate the binding of the information producer identity to the information at {{ insert: param, au-10.02_odp.01 }} ; and
- AU-10(2)(b)Perform {{ insert: param, au-10.02_odp.02 }} in the event of a validation error.
- AU-10(3)Maintain reviewer or releaser credentials within the established chain of custody for information reviewed or released.
- AU-10(4)(a)Validate the binding of the information reviewer identity to the information at the transfer or release points prior to release or transfer between {{ insert: param, au-10.04_odp.0
- AU-10(4)(b)Perform {{ insert: param, au-10.04_odp.02 }} in the event of a validation error.
- AU-11Retain audit records for {{ insert: param, au-11_odp }} to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information rete
- AU-11(1)Employ {{ insert: param, au-11.01_odp }} to ensure that long-term audit records generated by the system can be retrieved.
- AU-12(1)Compile audit records from {{ insert: param, au-12.01_odp.01 }} into a system-wide (logical or physical) audit trail that is time-correlated to within {{ insert: param, au-12.01_od
- AU-12(2)Produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format.
- AU-12(3)Provide and implement the capability for {{ insert: param, au-12.03_odp.01 }} to change the logging to be performed on {{ insert: param, au-12.03_odp.02 }} based on {{ insert: para
- AU-12(4)Provide and implement the capability for auditing the parameters of user query events for data sets containing personally identifiable information.
- AU-12aProvide audit record generation capability for the event types the system is capable of auditing as defined in [AU-2a](#au-2_smt.a) on {{ insert: param, au-12_odp.01 }};
- AU-12bAllow {{ insert: param, au-12_odp.02 }} to select the event types that are to be logged by specific components of the system; and
- AU-12cGenerate audit records for the event types defined in [AU-2c](#au-2_smt.c) that include the audit record content defined in [AU-3](#au-3).
- AU-13(1)Monitor open-source information and information sites using {{ insert: param, au-13.01_odp }}.
- AU-13(2)Review the list of open-source information sites being monitored {{ insert: param, au-13.02_odp }}.
- AU-13(3)Employ discovery techniques, processes, and tools to determine if external entities are replicating organizational information in an unauthorized manner.
- AU-13aMonitor {{ insert: param, au-13_odp.01 }} {{ insert: param, au-13_odp.02 }} for evidence of unauthorized disclosure of organizational information; and
- AU-13bIf an information disclosure is discovered:
- AU-13b1Notify {{ insert: param, au-13_odp.03 }} ; and
- AU-13b2Take the following additional actions: {{ insert: param, au-13_odp.04 }}.
- AU-14(1)Initiate session audits automatically at system start-up.
- AU-14(3)Provide and implement the capability for authorized users to remotely view and hear content related to an established user session in real time.
- AU-14aProvide and implement the capability for {{ insert: param, au-14_odp.01 }} to {{ insert: param, au-14_odp.02 }} the content of a user session under {{ insert: param, au-14_odp.03 }
- AU-14bDevelop, integrate, and use session auditing activities in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, polici
- AU-16Employ {{ insert: param, au-16_odp.01 }} for coordinating {{ insert: param, au-16_odp.02 }} among external organizations when audit information is transmitted across organizational
- AU-16(1)Preserve the identity of individuals in cross-organizational audit trails.
- AU-16(2)Provide cross-organizational audit information to {{ insert: param, au-16.02_odp.01 }} based on {{ insert: param, au-16.02_odp.02 }}.
- AU-16(3)Implement {{ insert: param, au-16.03_odp }} to disassociate individuals from audit information transmitted across organizational boundaries.
- CA-1aDevelop, document, and disseminate to {{ insert: param, ca-1_prm_1 }}:
- CA-1a1{{ insert: param, ca-01_odp.03 }} assessment, authorization, and monitoring policy that:
- CA-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- CA-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- CA-1a2Procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and the associated assessment, authorization, and monitoring controls;
- CA-1bDesignate an {{ insert: param, ca-01_odp.04 }} to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures; a
- CA-1cReview and update the current assessment, authorization, and monitoring:
- CA-1c1Policy {{ insert: param, ca-01_odp.05 }} and following {{ insert: param, ca-01_odp.06 }} ; and
- CA-1c2Procedures {{ insert: param, ca-01_odp.07 }} and following {{ insert: param, ca-01_odp.08 }}.
- CA-2(1)Employ independent assessors or assessment teams to conduct control assessments.
- CA-2(2)Include as part of control assessments, {{ insert: param, ca-02.02_odp.01 }}, {{ insert: param, ca-02.02_odp.02 }}, {{ insert: param, ca-02.02_odp.03 }}.
- CA-2(3)Leverage the results of control assessments performed by {{ insert: param, ca-02.03_odp.01 }} on {{ insert: param, ca-02.03_odp.02 }} when the assessment meets {{ insert: param, ca
- CA-2aSelect the appropriate assessor or assessment team for the type of assessment to be conducted;
- CA-2bDevelop a control assessment plan that describes the scope of the assessment including:
- CA-2b1Controls and control enhancements under assessment;
- CA-2b2Assessment procedures to be used to determine control effectiveness; and
- CA-2b3Assessment environment, assessment team, and assessment roles and responsibilities;
- CA-2cEnsure the control assessment plan is reviewed and approved by the authorizing official or designated representative prior to conducting the assessment;
- CA-2dAssess the controls in the system and its environment of operation {{ insert: param, ca-02_odp.01 }} to determine the extent to which the controls are implemented correctly, operat
- CA-2eProduce a control assessment report that document the results of the assessment; and
- CA-2fProvide the results of the control assessment to {{ insert: param, ca-02_odp.02 }}.
- CA-3(6)Verify that individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting su
- CA-3(7)(a)Identify transitive (downstream) information exchanges with other systems through the systems identified in [CA-3a](#ca-3_smt.a) ; and
- CA-3(7)(b)Take measures to ensure that transitive (downstream) information exchanges cease when the controls on identified transitive (downstream) systems cannot be verified or validated.
- CA-3aApprove and manage the exchange of information between the system and other systems using {{ insert: param, ca-03_odp.01 }};
- CA-3bDocument, as part of each exchange agreement, the interface characteristics, security and privacy requirements, controls, and responsibilities for each system, and the impact level
- CA-3cReview and update the agreements {{ insert: param, ca-03_odp.03 }}.
- CA-5(1)Ensure the accuracy, currency, and availability of the plan of action and milestones for the system using {{ insert: param, ca-05.01_odp }}.
- CA-5aDevelop a plan of action and milestones for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assess
- CA-5bUpdate existing plan of action and milestones {{ insert: param, ca-05_odp }} based on the findings from control assessments, independent audits or reviews, and continuous monitorin
- CA-6(1)Employ a joint authorization process for the system that includes multiple authorizing officials from the same organization conducting the authorization.
- CA-6(2)Employ a joint authorization process for the system that includes multiple authorizing officials with at least one authorizing official from an organization external to the organiz
- CA-6aAssign a senior official as the authorizing official for the system;
- CA-6bAssign a senior official as the authorizing official for common controls available for inheritance by organizational systems;
- CA-6cEnsure that the authorizing official for the system, before commencing operations:
- CA-6c1Accepts the use of common controls inherited by the system; and
- CA-6c2Authorizes the system to operate;
- CA-6dEnsure that the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems;
- CA-6eUpdate the authorizations {{ insert: param, ca-06_odp }}.
- CA-7Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes:
- CA-7(1)Employ independent assessors or assessment teams to monitor the controls in the system on an ongoing basis.
- CA-7(3)Employ trend analyses to determine if control implementations, the frequency of continuous monitoring activities, and the types of activities used in the continuous monitoring proc
- CA-7(4)Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following:
- CA-7(4)(a)Effectiveness monitoring;
- CA-7(4)(b)Compliance monitoring; and
- CA-7(4)(c)Change monitoring.
- CA-7(5)Employ the following actions to validate that policies are established and implemented controls are operating in a consistent manner: {{ insert: param, ca-7.5_prm_1 }}.
- CA-7(6)Ensure the accuracy, currency, and availability of monitoring results for the system using {{ insert: param, ca-07.06_odp }}.
- CA-7aEstablishing the following system-level metrics to be monitored: {{ insert: param, ca-07_odp.01 }};
- CA-7bEstablishing {{ insert: param, ca-07_odp.02 }} for monitoring and {{ insert: param, ca-07_odp.03 }} for assessment of control effectiveness;
- CA-7cOngoing control assessments in accordance with the continuous monitoring strategy;
- CA-7dOngoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy;
- CA-7eCorrelation and analysis of information generated by control assessments and monitoring;
- CA-7fResponse actions to address results of the analysis of control assessment and monitoring information; and
- CA-7gReporting the security and privacy status of the system to {{ insert: param, ca-7_prm_4 }} {{ insert: param, ca-7_prm_5 }}.
- CA-8Conduct penetration testing {{ insert: param, ca-08_odp.01 }} on {{ insert: param, ca-08_odp.02 }}.
- CA-8(1)Employ an independent penetration testing agent or team to perform penetration testing on the system or system components.
- CA-8(2)Employ the following red-team exercises to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement: {{ insert: param
- CA-8(3)Employ a penetration testing process that includes {{ insert: param, ca-08.03_odp.01 }} {{ insert: param, ca-08.03_odp.02 }} attempts to bypass or circumvent controls associated wi
- CA-9(1)Perform security and privacy compliance checks on constituent system components prior to the establishment of the internal connection.
- CA-9aAuthorize internal connections of {{ insert: param, ca-09_odp.01 }} to the system;
- CA-9bDocument, for each internal connection, the interface characteristics, security and privacy requirements, and the nature of the information communicated;
- CA-9cTerminate internal system connections after {{ insert: param, ca-09_odp.02 }} ; and
- CA-9dReview {{ insert: param, ca-09_odp.03 }} the continued need for each internal connection.
- CM-1aDevelop, document, and disseminate to {{ insert: param, cm-1_prm_1 }}:
- CM-1a1{{ insert: param, cm-01_odp.03 }} configuration management policy that:
- CM-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- CM-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- CM-1a2Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls;
- CM-1bDesignate an {{ insert: param, cm-01_odp.04 }} to manage the development, documentation, and dissemination of the configuration management policy and procedures; and
- CM-1cReview and update the current configuration management:
- CM-1c1Policy {{ insert: param, cm-01_odp.05 }} and following {{ insert: param, cm-01_odp.06 }} ; and
- CM-1c2Procedures {{ insert: param, cm-01_odp.07 }} and following {{ insert: param, cm-01_odp.08 }}.
- CM-2(2)Maintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using {{ insert: param, cm-02.02_odp }}.
- CM-2(3)Retain {{ insert: param, cm-02.03_odp }} of previous versions of baseline configurations of the system to support rollback.
- CM-2(6)Maintain a baseline configuration for system development and test environments that is managed separately from the operational baseline configuration.
- CM-2(7)(a)Issue {{ insert: param, cm-02.07_odp.01 }} with {{ insert: param, cm-02.07_odp.02 }} to individuals traveling to locations that the organization deems to be of significant risk; an
- CM-2(7)(b)Apply the following controls to the systems or components when the individuals return from travel: {{ insert: param, cm-02.07_odp.03 }}.
- CM-2aDevelop, document, and maintain under configuration control, a current baseline configuration of the system; and
- CM-2bReview and update the baseline configuration of the system:
- CM-2b1{{ insert: param, cm-02_odp.01 }};
- CM-2b2When required due to {{ insert: param, cm-02_odp.02 }} ; and
- CM-2b3When system components are installed or upgraded.
- CM-3(1)Use {{ insert: param, cm-03.01_odp.01 }} to:
- CM-3(1)(a)Document proposed changes to the system;
- CM-3(1)(b)Notify {{ insert: param, cm-03.01_odp.02 }} of proposed changes to the system and request change approval;
- CM-3(1)(c)Highlight proposed changes to the system that have not been approved or disapproved within {{ insert: param, cm-03.01_odp.03 }};
- CM-3(1)(d)Prohibit changes to the system until designated approvals are received;
- CM-3(1)(e)Document all changes to the system; and
- CM-3(1)(f)Notify {{ insert: param, cm-03.01_odp.04 }} when approved changes to the system are completed.
- CM-3(2)Test, validate, and document changes to the system before finalizing the implementation of the changes.
- CM-3(3)Implement changes to the current system baseline and deploy the updated baseline across the installed base using {{ insert: param, cm-03.03_odp }}.
- CM-3(4)Require {{ insert: param, cm-3.4_prm_1 }} to be members of the {{ insert: param, cm-03.04_odp.03 }}.
- CM-3(5)Implement the following security responses automatically if baseline configurations are changed in an unauthorized manner: {{ insert: param, cm-03.05_odp }}.
- CM-3(6)Ensure that cryptographic mechanisms used to provide the following controls are under configuration management: {{ insert: param, cm-03.06_odp }}.
- CM-3(7)Review changes to the system {{ insert: param, cm-03.07_odp.01 }} or when {{ insert: param, cm-03.07_odp.02 }} to determine whether unauthorized changes have occurred.
- CM-3(8)Prevent or restrict changes to the configuration of the system under the following circumstances: {{ insert: param, cm-03.08_odp }}.
- CM-3aDetermine and document the types of changes to the system that are configuration-controlled;
- CM-3bReview proposed configuration-controlled changes to the system and approve or disapprove such changes with explicit consideration for security and privacy impact analyses;
- CM-3cDocument configuration change decisions associated with the system;
- CM-3dImplement approved configuration-controlled changes to the system;
- CM-3eRetain records of configuration-controlled changes to the system for {{ insert: param, cm-03_odp.01 }};
- CM-3fMonitor and review activities associated with configuration-controlled changes to the system; and
- CM-3gCoordinate and provide oversight for configuration change control activities through {{ insert: param, cm-03_odp.02 }} that convenes {{ insert: param, cm-03_odp.03 }}.
- CM-4Analyze changes to the system to determine potential security and privacy impacts prior to change implementation.
- CM-4(1)Analyze changes to the system in a separate test environment before implementation in an operational environment, looking for security and privacy impacts due to flaws, weaknesses,
- CM-4(2)After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and
- CM-5Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system.
- CM-5(1)(a)Enforce access restrictions using {{ insert: param, cm-05.01_odp }} ; and
- CM-5(1)(b)Automatically generate audit records of the enforcement actions.
- CM-5(4)Enforce dual authorization for implementing changes to {{ insert: param, cm-5.4_prm_1 }}.
- CM-5(5)(a)Limit privileges to change system components and system-related information within a production or operational environment; and
- CM-5(5)(b)Review and reevaluate privileges {{ insert: param, cm-5.5_prm_1 }}.
- CM-5(6)Limit privileges to change software resident within software libraries.
- CM-6(1)Manage, apply, and verify configuration settings for {{ insert: param, cm-06.01_odp.01 }} using {{ insert: param, cm-6.1_prm_2 }}.
- CM-6(2)Take the following actions in response to unauthorized changes to {{ insert: param, cm-06.02_odp.02 }}: {{ insert: param, cm-06.02_odp.01 }}.
- CM-6aEstablish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using {{ ins
- CM-6bImplement the configuration settings;
- CM-6cIdentify, document, and approve any deviations from established configuration settings for {{ insert: param, cm-06_odp.02 }} based on {{ insert: param, cm-06_odp.03 }} ; and
- CM-6dMonitor and control changes to the configuration settings in accordance with organizational policies and procedures.
- CM-7(1)(a)Review the system {{ insert: param, cm-07.01_odp.01 }} to identify unnecessary and/or nonsecure functions, ports, protocols, software, and services; and
- CM-7(1)(b)Disable or remove {{ insert: param, cm-7.1_prm_2 }}.
- CM-7(2)Prevent program execution in accordance with {{ insert: param, cm-07.02_odp.01 }}.
- CM-7(3)Ensure compliance with {{ insert: param, cm-07.03_odp }}.
- CM-7(4)(a)Identify {{ insert: param, cm-07.04_odp.01 }};
- CM-7(4)(b)Employ an allow-all, deny-by-exception policy to prohibit the execution of unauthorized software programs on the system; and
- CM-7(4)(c)Review and update the list of unauthorized software programs {{ insert: param, cm-07.04_odp.02 }}.
- CM-7(5)(a)Identify {{ insert: param, cm-07.05_odp.01 }};
- CM-7(5)(b)Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system; and
- CM-7(5)(c)Review and update the list of authorized software programs {{ insert: param, cm-07.05_odp.02 }}.
- CM-7(6)Require that the following user-installed software execute in a confined physical or virtual machine environment with limited privileges: {{ insert: param, cm-07.06_odp }}.
- CM-7(7)Allow execution of binary or machine-executable code only in confined physical or virtual machine environments and with the explicit approval of {{ insert: param, cm-07.07_odp }} w
- CM-7(7)(a)Obtained from sources with limited or no warranty; and/or
- CM-7(7)(b)Without the provision of source code.
- CM-7(8)(a)Prohibit the use of binary or machine-executable code from sources with limited or no warranty or without the provision of source code; and
- CM-7(8)(b)Allow exceptions only for compelling mission or operational requirements and with the approval of the authorizing official.
- CM-7(9)(a)Identify {{ insert: param, cm-07.09_odp.01 }};
- CM-7(9)(b)Prohibit the use or connection of unauthorized hardware components;
- CM-7(9)(c)Review and update the list of authorized hardware components {{ insert: param, cm-07.09_odp.02 }}.
- CM-7aConfigure the system to provide only {{ insert: param, cm-07_odp.01 }} ; and
- CM-7bProhibit or restrict the use of the following functions, ports, protocols, software, and/or services: {{ insert: param, cm-7_prm_2 }}.
- CM-8(1)Update the inventory of system components as part of component installations, removals, and system updates.
- CM-8(2)Maintain the currency, completeness, accuracy, and availability of the inventory of system components using {{ insert: param, cm-8.2_prm_1 }}.
- CM-8(3)(a)Detect the presence of unauthorized hardware, software, and firmware components within the system using {{ insert: param, cm-8.3_prm_1 }} {{ insert: param, cm-08.03_odp.04 }} ; and
- CM-8(3)(b)Take the following actions when unauthorized components are detected: {{ insert: param, cm-08.03_odp.05 }}.
- CM-8(4)Include in the system component inventory information, a means for identifying by {{ insert: param, cm-08.04_odp }} , individuals responsible and accountable for administering thos
- CM-8(6)Include assessed component configurations and any approved deviations to current deployed configurations in the system component inventory.
- CM-8(7)Provide a centralized repository for the inventory of system components.
- CM-8(8)Support the tracking of system components by geographic location using {{ insert: param, cm-08.08_odp }}.
- CM-8(9)(a)Assign system components to a system; and
- CM-8(9)(b)Receive an acknowledgement from {{ insert: param, cm-08.09_odp }} of this assignment.
- CM-8aDevelop and document an inventory of system components that:
- CM-8a1Accurately reflects the system;
- CM-8a2Includes all components within the system;
- CM-8a3Does not include duplicate accounting of components or components assigned to any other system;
- CM-8a4Is at the level of granularity deemed necessary for tracking and reporting; and
- CM-8a5Includes the following information to achieve system component accountability: {{ insert: param, cm-08_odp.01 }} ; and
- CM-8bReview and update the system component inventory {{ insert: param, cm-08_odp.02 }}.
- CM-9Develop, document, and implement a configuration management plan for the system that:
- CM-9(1)Assign responsibility for developing the configuration management process to organizational personnel that are not directly involved in system development.
- CM-9aAddresses roles, responsibilities, and configuration management processes and procedures;
- CM-9bEstablishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items;
- CM-9cDefines the configuration items for the system and places the configuration items under configuration management;
- CM-9dIs reviewed and approved by {{ insert: param, cm-09_odp }} ; and
- CM-9eProtects the configuration management plan from unauthorized disclosure and modification.
- CM-10(1)Establish the following restrictions on the use of open-source software: {{ insert: param, cm-10.01_odp }}.
- CM-10aUse software and associated documentation in accordance with contract agreements and copyright laws;
- CM-10bTrack the use of software and associated documentation protected by quantity licenses to control copying and distribution; and
- CM-10cControl and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduc
- CM-11(2)Allow user installation of software only with explicit privileged status.
- CM-11(3)Enforce and monitor compliance with software installation policies using {{ insert: param, cm-11.3_prm_1 }}.
- CM-11aEstablish {{ insert: param, cm-11_odp.01 }} governing the installation of software by users;
- CM-11bEnforce software installation policies through the following methods: {{ insert: param, cm-11_odp.02 }} ; and
- CM-11cMonitor policy compliance {{ insert: param, cm-11_odp.03 }}.
- CM-12(1)Use automated tools to identify {{ insert: param, cm-12.01_odp.01 }} on {{ insert: param, cm-12.01_odp.02 }} to ensure controls are in place to protect organizational information a
- CM-12aIdentify and document the location of {{ insert: param, cm-12_odp }} and the specific system components on which the information is processed and stored;
- CM-12bIdentify and document the users who have access to the system and system components where the information is processed and stored; and
- CM-12cDocument changes to the location (i.e., system or system components) where the information is processed and stored.
- CM-13Develop and document a map of system data actions.
- CM-14Prevent the installation of {{ insert: param, cm-14_prm_1 }} without verification that the component has been digitally signed using a certificate that is recognized and approved b
- CP-1aDevelop, document, and disseminate to {{ insert: param, cp-1_prm_1 }}:
- CP-1a1{{ insert: param, cp-01_odp.03 }} contingency planning policy that:
- CP-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- CP-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- CP-1a2Procedures to facilitate the implementation of the contingency planning policy and the associated contingency planning controls;
- CP-1bDesignate an {{ insert: param, cp-01_odp.04 }} to manage the development, documentation, and dissemination of the contingency planning policy and procedures; and
- CP-1cReview and update the current contingency planning:
- CP-1c1Policy {{ insert: param, cp-01_odp.05 }} and following {{ insert: param, cp-01_odp.06 }} ; and
- CP-1c2Procedures {{ insert: param, cp-01_odp.07 }} and following {{ insert: param, cp-01_odp.08 }}.
- CP-2(1)Coordinate contingency plan development with organizational elements responsible for related plans.
- CP-2(2)Conduct capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations.
- CP-2(3)Plan for the resumption of {{ insert: param, cp-02.03_odp.01 }} mission and business functions within {{ insert: param, cp-02.03_odp.02 }} of contingency plan activation.
- CP-2(5)Plan for the continuance of {{ insert: param, cp-02.05_odp }} mission and business functions with minimal or no loss of operational continuity and sustains that continuity until fu
- CP-2(6)Plan for the transfer of {{ insert: param, cp-02.06_odp }} mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational contin
- CP-2(7)Coordinate the contingency plan with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.
- CP-2(8)Identify critical system assets supporting {{ insert: param, cp-02.08_odp }} mission and business functions.
- CP-2aDevelop a contingency plan for the system that:
- CP-2a1Identifies essential mission and business functions and associated contingency requirements;
- CP-2a2Provides recovery objectives, restoration priorities, and metrics;
- CP-2a3Addresses contingency roles, responsibilities, assigned individuals with contact information;
- CP-2a4Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;
- CP-2a5Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented;
- CP-2a6Addresses the sharing of contingency information; and
- CP-2a7Is reviewed and approved by {{ insert: param, cp-2_prm_1 }};
- CP-2bDistribute copies of the contingency plan to {{ insert: param, cp-2_prm_2 }};
- CP-2cCoordinate contingency planning activities with incident handling activities;
- CP-2dReview the contingency plan for the system {{ insert: param, cp-02_odp.05 }};
- CP-2eUpdate the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution,
- CP-2fCommunicate contingency plan changes to {{ insert: param, cp-2_prm_4 }};
- CP-2gIncorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and
- CP-2hProtect the contingency plan from unauthorized disclosure and modification.
- CP-3(1)Incorporate simulated events into contingency training to facilitate effective response by personnel in crisis situations.
- CP-3(2)Employ mechanisms used in operations to provide a more thorough and realistic contingency training environment.
- CP-3aProvide contingency training to system users consistent with assigned roles and responsibilities:
- CP-3a1Within {{ insert: param, cp-03_odp.01 }} of assuming a contingency role or responsibility;
- CP-3a2When required by system changes; and
- CP-3a3{{ insert: param, cp-03_odp.02 }} thereafter; and
- CP-3bReview and update contingency training content {{ insert: param, cp-03_odp.03 }} and following {{ insert: param, cp-03_odp.04 }}.
- CP-4(1)Coordinate contingency plan testing with organizational elements responsible for related plans.
- CP-4(2)Test the contingency plan at the alternate processing site:
- CP-4(2)(a)To familiarize contingency personnel with the facility and available resources; and
- CP-4(2)(b)To evaluate the capabilities of the alternate processing site to support contingency operations.
- CP-4(3)Test the contingency plan using {{ insert: param, cp-04.03_odp }}.
- CP-4(4)Include a full recovery and reconstitution of the system to a known state as part of contingency plan testing.
- CP-4(5)Employ {{ insert: param, cp-04.05_odp.01 }} to {{ insert: param, cp-04.05_odp.02 }} to disrupt and adversely affect the system or system component.
- CP-4aTest the contingency plan for the system {{ insert: param, cp-04_odp.01 }} using the following tests to determine the effectiveness of the plan and the readiness to execute the pla
- CP-4bReview the contingency plan test results; and
- CP-4cInitiate corrective actions, if needed.
- CP-6(1)Identify an alternate storage site that is sufficiently separated from the primary storage site to reduce susceptibility to the same threats.
- CP-6(2)Configure the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives.
- CP-6(3)Identify potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outline explicit mitigation actions.
- CP-6aEstablish an alternate storage site, including necessary agreements to permit the storage and retrieval of system backup information; and
- CP-6bEnsure that the alternate storage site provides controls equivalent to that of the primary site.
- CP-7(1)Identify an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats.
- CP-7(2)Identify potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster and outlines explicit mitigation actions.
- CP-7(3)Develop alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives).
- CP-7(4)Prepare the alternate processing site so that the site can serve as the operational site supporting essential mission and business functions.
- CP-7(6)Plan and prepare for circumstances that preclude returning to the primary processing site.
- CP-7aEstablish an alternate processing site, including necessary agreements to permit the transfer and resumption of {{ insert: param, cp-07_odp.01 }} for essential mission and business
- CP-7bMake available at the alternate processing site, the equipment and supplies required to transfer and resume operations or put contracts in place to support delivery to the site wit
- CP-7cProvide controls at the alternate processing site that are equivalent to those at the primary site.
- CP-8Establish alternate telecommunications services, including necessary agreements to permit the resumption of {{ insert: param, cp-08_odp.01 }} for essential mission and business fun
- CP-8(1)(a)Develop primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery tim
- CP-8(1)(b)Request Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications
- CP-8(2)Obtain alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services.
- CP-8(3)Obtain alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats.
- CP-8(4)(a)Require primary and alternate telecommunications service providers to have contingency plans;
- CP-8(4)(b)Review provider contingency plans to ensure that the plans meet organizational contingency requirements; and
- CP-8(4)(c)Obtain evidence of contingency testing and training by providers {{ insert: param, cp-8.4_prm_1 }}.
- CP-8(5)Test alternate telecommunication services {{ insert: param, cp-08.05_odp }}.
- CP-9(1)Test backup information {{ insert: param, cp-9.1_prm_1 }} to verify media reliability and information integrity.
- CP-9(2)Use a sample of backup information in the restoration of selected system functions as part of contingency plan testing.
- CP-9(3)Store backup copies of {{ insert: param, cp-09.03_odp }} in a separate facility or in a fire rated container that is not collocated with the operational system.
- CP-9(5)Transfer system backup information to the alternate storage site {{ insert: param, cp-9.5_prm_1 }}.
- CP-9(6)Conduct system backup by maintaining a redundant secondary system that is not collocated with the primary system and that can be activated without loss of information or disruption
- CP-9(7)Enforce dual authorization for the deletion or destruction of {{ insert: param, cp-09.07_odp }}.
- CP-9(8)Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of {{ insert: param, cp-09.08_odp }}.
- CP-9aConduct backups of user-level information contained in {{ insert: param, cp-09_odp.01 }} {{ insert: param, cp-09_odp.02 }};
- CP-9bConduct backups of system-level information contained in the system {{ insert: param, cp-09_odp.03 }};
- CP-9cConduct backups of system documentation, including security- and privacy-related documentation {{ insert: param, cp-09_odp.04 }} ; and
- CP-9dProtect the confidentiality, integrity, and availability of backup information.
- CP-10Provide for the recovery and reconstitution of the system to a known state within {{ insert: param, cp-10_prm_1 }} after a disruption, compromise, or failure.
- CP-10(2)Implement transaction recovery for systems that are transaction-based.
- CP-10(3)Addressed through tailoring.
- CP-10(4)Provide the capability to restore system components within {{ insert: param, cp-10.04_odp }} from configuration-controlled and integrity-protected information representing a known,
- CP-10(6)Protect system components used for recovery and reconstitution.
- CP-11Provide the capability to employ {{ insert: param, cp-11_odp }} in support of maintaining continuity of operations.
- CP-12When {{ insert: param, cp-12_odp.02 }} are detected, enter a safe mode of operation with {{ insert: param, cp-12_odp.01 }}.
- CP-13Employ {{ insert: param, cp-13_odp.01 }} for satisfying {{ insert: param, cp-13_odp.02 }} when the primary means of implementing the security function is unavailable or compromised
- IA-1aDevelop, document, and disseminate to {{ insert: param, ia-1_prm_1 }}:
- IA-1a1{{ insert: param, ia-01_odp.03 }} identification and authentication policy that:
- IA-1a1(a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- IA-1a1(b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- IA-1a2Procedures to facilitate the implementation of the identification and authentication policy and the associated identification and authentication controls;
- IA-1bDesignate an {{ insert: param, ia-01_odp.04 }} to manage the development, documentation, and dissemination of the identification and authentication policy and procedures; and
- IA-1cReview and update the current identification and authentication:
- IA-1c1Policy {{ insert: param, ia-01_odp.05 }} and following {{ insert: param, ia-01_odp.06 }} ; and
- IA-1c2Procedures {{ insert: param, ia-01_odp.07 }} and following {{ insert: param, ia-01_odp.08 }}.
- IA-2Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.
- IA-2(1)Implement multi-factor authentication for access to privileged accounts.
- IA-2(2)Implement multi-factor authentication for access to non-privileged accounts.
- IA-2(5)When shared accounts or authenticators are employed, require users to be individually authenticated before granting access to the shared accounts or resources.
- IA-2(6)Implement multi-factor authentication for {{ insert: param, ia-02.06_odp.01 }} access to {{ insert: param, ia-02.06_odp.02 }} such that:
- IA-2(6)(a)One of the factors is provided by a device separate from the system gaining access; and
- IA-2(6)(b)The device meets {{ insert: param, ia-02.06_odp.03 }}.
- IA-2(8)Implement replay-resistant authentication mechanisms for access to {{ insert: param, ia-02.08_odp }}.
- IA-2(10)Provide a single sign-on capability for {{ insert: param, ia-02.10_odp }}.
- IA-2(12)Accept and electronically verify Personal Identity Verification-compliant credentials.
- IA-2(13)Implement the following out-of-band authentication mechanisms under {{ insert: param, ia-02.13_odp.02 }}: {{ insert: param, ia-02.13_odp.01 }}.
- IA-3Uniquely identify and authenticate {{ insert: param, ia-03_odp.01 }} before establishing a {{ insert: param, ia-03_odp.02 }} connection.
- IA-3(1)Authenticate {{ insert: param, ia-03.01_odp.01 }} before establishing {{ insert: param, ia-03.01_odp.02 }} connection using bidirectional authentication that is cryptographically b
- IA-3(3)(a)Where addresses are allocated dynamically, standardize dynamic address allocation lease information and the lease duration assigned to devices in accordance with {{ insert: param,
- IA-3(3)(b)Audit lease information when assigned to a device.
- IA-3(4)Handle device identification and authentication based on attestation by {{ insert: param, ia-03.04_odp }}.
- IA-4Manage system identifiers by:
- IA-4(1)Prohibit the use of system account identifiers that are the same as public identifiers for individual accounts.
- IA-4(4)Manage individual identifiers by uniquely identifying each individual as {{ insert: param, ia-04.04_odp }}.
- IA-4(5)Manage individual identifiers dynamically in accordance with {{ insert: param, ia-04.05_odp }}.
- IA-4(6)Coordinate with the following external organizations for cross-organization management of identifiers: {{ insert: param, ia-04.06_odp }}.
- IA-4(8)Generate pairwise pseudonymous identifiers.
- IA-4(9)Maintain the attributes for each uniquely identified individual, device, or service in {{ insert: param, ia-04.09_odp }}.
- IA-4aReceiving authorization from {{ insert: param, ia-04_odp.01 }} to assign an individual, group, role, service, or device identifier;
- IA-4bSelecting an identifier that identifies an individual, group, role, service, or device;
- IA-4cAssigning the identifier to the intended individual, group, role, service, or device; and
- IA-4dPreventing reuse of identifiers for {{ insert: param, ia-04_odp.02 }}.
- IA-5Manage system authenticators by:
- IA-5(1)For password-based authentication:
- IA-5(1)(a)Maintain a list of commonly-used, expected, or compromised passwords and update the list {{ insert: param, ia-05.01_odp.01 }} and when organizational passwords are suspected to hav
- IA-5(1)(b)Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a);
- IA-5(1)(c)Transmit passwords only over cryptographically-protected channels;
- IA-5(1)(d)Store passwords using an approved salted key derivation function, preferably using a keyed hash;
- IA-5(1)(e)Require immediate selection of a new password upon account recovery;
- IA-5(1)(f)Allow user selection of long passwords and passphrases, including spaces and all printable characters;
- IA-5(1)(g)Employ automated tools to assist the user in selecting strong password authenticators; and
- IA-5(1)(h)Enforce the following composition and complexity rules: {{ insert: param, ia-05.01_odp.02 }}.
- IA-5(2)(a)For public key-based authentication:
- IA-5(2)(a)(1)Enforce authorized access to the corresponding private key; and
- IA-5(2)(a)(2)Map the authenticated identity to the account of the individual or group; and
- IA-5(2)(b)When public key infrastructure (PKI) is used:
- IA-5(2)(b)(1)Validate certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; and
- IA-5(2)(b)(2)Implement a local cache of revocation data to support path discovery and validation.
- IA-5(5)Require developers and installers of system components to provide unique authenticators or change default authenticators prior to delivery and installation.
- IA-5(6)Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access.
- IA-5(7)Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage.
- IA-5(8)Implement {{ insert: param, ia-05.08_odp }} to manage the risk of compromise due to individuals having accounts on multiple systems.
- IA-5(9)Use the following external organizations to federate credentials: {{ insert: param, ia-05.09_odp }}.
- IA-5(10)Bind identities and authenticators dynamically using the following rules: {{ insert: param, ia-05.10_odp }}.
- IA-5(12)For biometric-based authentication, employ mechanisms that satisfy the following biometric quality requirements {{ insert: param, ia-05.12_odp }}.
- IA-5(13)Prohibit the use of cached authenticators after {{ insert: param, ia-05.13_odp }}.
- IA-5(14)For PKI-based authentication, employ an organization-wide methodology for managing the content of PKI trust stores installed across all platforms, including networks, operating sys
- IA-5(15)Use only General Services Administration-approved products and services for identity, credential, and access management.
- IA-5(16)Require that the issuance of {{ insert: param, ia-05.16_odp.01 }} be conducted {{ insert: param, ia-05.16_odp.02 }} before {{ insert: param, ia-05.16_odp.03 }} with authorization b
- IA-5(17)Employ presentation attack detection mechanisms for biometric-based authentication.
- IA-5(18)(a)Employ {{ insert: param, ia-05.18_odp.01 }} to generate and manage passwords; and
- IA-5(18)(b)Protect the passwords using {{ insert: param, ia-05.18_odp.02 }}.
- IA-5aVerifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator;
- IA-5bEstablishing initial authenticator content for any authenticators issued by the organization;
- IA-5cEnsuring that authenticators have sufficient strength of mechanism for their intended use;
- IA-5dEstablishing and implementing administrative procedures for initial authenticator distribution, for lost or compromised or damaged authenticators, and for revoking authenticators;
← records 1–400 · 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 801 on →