Develop, document, and disseminate to personnel or roles; one or more: organization-level; mission/business process-level; system-level; official; frequency; events: one or more: organization-level; mission/business process-level; system-level configuration management policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls; Designate an official to manage the development, documentation, and dissemination of the configuration management policy and procedures; and Review and update the current configuration management: Policy frequency and following events ; and Procedures frequency and following events.
Configuration management policy and procedures address the controls in the CM family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of configuration management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to configuration management policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
a configuration management policy is developed and documented; the configuration management policy is disseminated to personnel or roles; configuration management procedures to facilitate the implementation of the configuration management policy and associated configuration management controls are developed and documented; the configuration management procedures are disseminated to personnel or roles; the one or more: organization-level; mission/business process-level; system-level of the configuration management policy addresses purpose; the one or more: organization-level; mission/business process-level; system-level of the configuration management policy addresses scope; the one or more: organization-level; mission/business process-level; system-level of the configuration management policy addresses roles; the one or more: organization-level; mission/business process-level; system-level of the configuration management policy addresses responsibilities; the one or more: organization-level; mission/business process-level; system-level of the configuration management policy addresses management commitment; the one or more: organization-level; mission/business process-level; system-level of the configuration management policy addresses coordination among organizational entities; the one or more: organization-level; mission/business process-level; system-level of the configuration management policy addresses compliance; the configuration management policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines; the official is designated to manage the development, documentation, and dissemination of the configuration management policy and procedures; the current configuration management policy is reviewed and updated frequency; the current configuration management policy is reviewed and updated following events; the current configuration management procedures are reviewed and updated frequency; the current configuration management procedures are reviewed and updated following events.
No cross-framework mappings available