- Perform configuration management during system, component, or service [ Assignment: ];
- Document, manage, and control the integrity of changes to [ Assignment: configuration items ];
- 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 [ Assignment: personnel ].
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.\n\nThe 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.