_nist/sp-800-53/sa/sa-10 · always-coding.co.uk

id: "SA-10" title: "Developer Configuration Management" family: "SA" family_name: "System and Services Acquisition" sort_id: "sa-10" priority: "P1" implementation_level: "organization" enhancements: - sa-10.1 - sa-10.2 - sa-10.3 - sa-10.4 - sa-10.5 - sa-10.6 - sa-10.7

Statement

Require the developer of the system, system component, or system service to:

Perform configuration management during system, component, or service {{ insert: param, sa-10_odp.01 }};

Document, manage, and control the integrity of changes to {{ insert: param, sa-10_odp.02 }};

Implement only organization-approved changes to the system, component, or service;

Document approved changes to the system, component, or service and the potential security and privacy impacts of such changes; and

Track security flaws and flaw resolution within the system, component, or service and report findings to {{ insert: param, sa-10_odp.03 }}.

Guidance

Organizations consider the quality and completeness of configuration management activities conducted by developers as direct evidence of applying effective security controls. Controls include protecting the master copies of material used to generate security-relevant portions of the system hardware, software, and firmware from unauthorized modification or destruction. Maintaining the integrity of changes to the system, system component, or system service requires strict configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes.

The configuration items that are placed under configuration management include the formal model; the functional, high-level, and low-level design specifications; other design data; implementation documentation; source code and hardware schematics; the current running version of the object code; tools for comparing new versions of security-relevant hardware descriptions and source code with previous versions; and test fixtures and documentation. Depending on the mission and business needs of organizations and the nature of the contractual relationships in place, developers may provide configuration management support during the operations and maintenance stage of the system development life cycle.

Assessment Objective: the developer of the system, system component, or system service is required to perform configuration management during system, component, or service {{ insert: param, sa-10_odp.01 }};

Assessment Objective: the developer of the system, system component, or system service is required to document the integrity of changes to {{ insert: param, sa-10_odp.02 }};

Assessment Objective: the developer of the system, system component, or system service is required to manage the integrity of changes to {{ insert: param, sa-10_odp.02 }};

Assessment Objective: the developer of the system, system component, or system service is required to control the integrity of changes to {{ insert: param, sa-10_odp.02 }};

Assessment Objective: the developer of the system, system component, or system service is required to implement only organization-approved changes to the system, component, or service;

Assessment Objective: the developer of the system, system component, or system service is required to document approved changes to the system, component, or service;

Assessment Objective: the developer of the system, system component, or system service is required to document the potential security impacts of approved changes;

Assessment Objective: the developer of the system, system component, or system service is required to document the potential privacy impacts of approved changes;

Assessment Objective: the developer of the system, system component, or system service is required to track security flaws within the system, component, or service;

Assessment Objective: the developer of the system, system component, or system service is required to track security flaw resolutions within the system, component, or service;

Assessment Objective: the developer of the system, system component, or system service is required to report findings to {{ insert: param, sa-10_odp.03 }}.

System and services acquisition policy

procedures addressing system developer configuration management

solicitation documentation

acquisition documentation

service level agreements

acquisition contracts for the system, system component, or system service

system developer configuration management plan

security flaw and flaw resolution tracking records

system change authorization records

change control records

configuration management records

system security plan