+SA-10 Developer Configuration Management
---+SA-10(01) Software and Firmware Integrity Verification
---+SA-10(02) Alternative Configuration Management Processes
---+SA-10(03) Hardware Integrity Verification
---+SA-10(04) Trusted Generation
---+SA-10(05) Mapping Integrity for Version Control
---+SA-10(06) Trusted Distribution
---+SA-10(07) Security and Privacy Representatives

SA-10 Developer Configuration Management

Control

Require the developer of the system, system component, or system service to:
  1. Perform configuration management during system, component, or service [Selection(one-or-more): design; development; implementation; operation; disposal];
  2. Document, manage, and control the integrity of changes to [Assignement: configuration items];
  3. Implement only organization-approved changes to the system, component, or service;
  4. Document approved changes to the system, component, or service and the potential security and privacy impacts of such changes; and
  5. Track security flaws and flaw resolution within the system, component, or service and report findings to [Assignement: personnel].

Discussion

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

  1. the developer of the system, system component, or system service is required to perform configuration management during system, component, or service [Selection(one-or-more): design; development; implementation; operation; disposal];
    1. the developer of the system, system component, or system service is required to document the integrity of changes to [Assignement: configuration items];
    2. the developer of the system, system component, or system service is required to manage the integrity of changes to [Assignement: configuration items];
    3. the developer of the system, system component, or system service is required to control the integrity of changes to [Assignement: configuration items];
  3. the developer of the system, system component, or system service is required to implement only organization-approved changes to the system, component, or service;
    1. the developer of the system, system component, or system service is required to document approved changes to the system, component, or service;
    2. the developer of the system, system component, or system service is required to document the potential security impacts of approved changes;
    3. the developer of the system, system component, or system service is required to document the potential privacy impacts of approved changes;
    1. the developer of the system, system component, or system service is required to track security flaws within the system, component, or service;
    2. the developer of the system, system component, or system service is required to track security flaw resolutions within the system, component, or service;
    3. the developer of the system, system component, or system service is required to report findings to [Assignement: personnel].

Assessment Method

Examine

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 other relevant documents or records

Interview

Organizational personnel with system and service acquisition responsibilities organizational personnel with information security responsibilities organizational personnel with configuration management responsibilities system developers

1. Ħarsa ġenerali

SA-10(01) Software and Firmware Integrity Verification

Control

Require the developer of the system, system component, or system service to enable integrity verification of software and firmware components.

Discussion

Software and firmware integrity verification allows organizations to detect unauthorized changes to software and firmware components using developer-provided tools, techniques, and mechanisms. The integrity checking mechanisms can also address counterfeiting of software and firmware components. Organizations verify the integrity of software and firmware components, for example, through secure one-way hashes provided by developers. Delivered software and firmware components also include any updates to such components.

Assessment Objective

the developer of the system, system component, or system service is required to enable integrity verification of software and firmware components.

Assessment Method

Examine

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 software and firmware integrity verification records system change authorization records change control records configuration management records system security plan supply chain risk management plan other relevant documents or records

Interview

Organizational personnel with system and service acquisition responsibilities organizational personnel with information security responsibilities organizational personnel with configuration management responsibilities system developers organizational personnel with supply chain risk management responsibilities
SA-10(02) Alternative Configuration Management Processes

Control

Provide an alternate configuration management process using organizational personnel in the absence of a dedicated developer configuration management team.

Discussion

Alternate configuration management processes may be required when organizations use commercial off-the-shelf information technology products. Alternate configuration management processes include organizational personnel who review and approve proposed changes to systems, system components, and system services and conduct security and privacy impact analyses prior to the implementation of changes to systems, components, or services.

Assessment Objective

an alternate configuration management process has been provided using organizational personnel in the absence of a dedicated developer configuration management team.

Assessment Method

Examine

System and services acquisition policy system and services acquisition procedures configuration management policy configuration management plan solicitation documentation acquisition documentation service level agreements acquisition contracts for the system, system component, or system service system developer configuration management plan security impact analyses privacy impact analyses privacy impact assessment privacy risk assessment documentation system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with acquisition responsibilities organizational personnel with information security and privacy responsibilities organizational personnel with configuration management responsibilities system developers
SA-10(03) Hardware Integrity Verification

Control

Require the developer of the system, system component, or system service to enable integrity verification of hardware components.

Discussion

Hardware integrity verification allows organizations to detect unauthorized changes to hardware components using developer-provided tools, techniques, methods, and mechanisms. Organizations may verify the integrity of hardware components with hard-to-copy labels, verifiable serial numbers provided by developers, and by requiring the use of anti-tamper technologies. Delivered hardware components also include hardware and firmware updates to such components.

Assessment Objective

the developer of the system, system component, or system service is required to enable integrity verification of hardware components.

Assessment Method

Examine

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 hardware integrity verification records system security plan supply chain risk management plan other relevant documents or records

Interview

Organizational personnel with system and service acquisition responsibilities organizational personnel with information security responsibilities organizational personnel with configuration management responsibilities system developers organizational personnel with supply chain risk management responsibilities
SA-10(04) Trusted Generation

Control

Require the developer of the system, system component, or system service to employ tools for comparing newly generated versions of security-relevant hardware descriptions, source code, and object code with previous versions.

Discussion

The trusted generation of descriptions, source code, and object code addresses authorized changes to hardware, software, and firmware components between versions during development. The focus is on the efficacy of the configuration management process by the developer to ensure that newly generated versions of security-relevant hardware descriptions, source code, and object code continue to enforce the security policy for the system, system component, or system service. In contrast, [SA-10(1)](#sa-10.1) and [SA-10(3)](#sa-10.3) allow organizations to detect unauthorized changes to hardware, software, and firmware components using tools, techniques, or mechanisms provided by developers.

Assessment Objective

  1. the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions;
  2. the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of source code with previous versions;
  3. the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of object code with previous versions.

Assessment Method

Examine

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 change control records configuration management records configuration control audit records system security plan other relevant documents or records

Interview
SA-10(05) Mapping Integrity for Version Control

Control

Require the developer of the system, system component, or system service to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.

Discussion

Mapping integrity for version control addresses changes to hardware, software, and firmware components during both initial development and system development life cycle updates. Maintaining the integrity between the master copies of security-relevant hardware, software, and firmware (including designs, hardware drawings, source code) and the equivalent data in master copies in operational environments is essential to ensuring the availability of organizational systems that support critical mission and business functions.

Assessment Objective

the developer of the system, system component, or system service is required to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.

Assessment Method

Examine

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 change control records configuration management records version control change/update records integrity verification records between master copies of security-relevant hardware, software, and firmware (including designs and source code) system security plan other relevant documents or records

Interview

Organizational personnel with system and service acquisition responsibilities organizational personnel with information security responsibilities organizational personnel with configuration management responsibilities system developers
SA-10(06) Trusted Distribution

Control

Require the developer of the system, system component, or system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.

Discussion

The trusted distribution of security-relevant hardware, software, and firmware updates help to ensure that the updates are correct representations of the master copies maintained by the developer and have not been tampered with during distribution.

Assessment Objective

the developer of the system, system component, or system service is required to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.

Assessment Method

Examine

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 change control records configuration management records system security plan other relevant documents or records

Interview

Organizational personnel with system and service acquisition responsibilities organizational personnel with information security responsibilities organizational personnel with configuration management responsibilities system developers
SA-10(07) Security and Privacy Representatives

Control

Require [Assignement: organization-defined security and privacy representatives] to be included in the [Assignement: organization-defined configuration change management and control process].

Discussion

Information security and privacy representatives can include system security officers, senior agency information security officers, senior agency officials for privacy, and system privacy officers. Representation by personnel with information security and privacy expertise is important because changes to system configurations can have unintended side effects, some of which may be security- or privacy-relevant. Detecting such changes early in the process can help avoid unintended, negative consequences that could ultimately affect the security and privacy posture of systems. The configuration change management and control process in this control enhancement refers to the change management and control process defined by organizations in [SA-10b](#sa-10_smt.b).

Assessment Objective

  1. [Assignement: security representatives] are required to be included in the [Assignement: configuration change management and control processes];
  2. [Assignement: privacy representatives] are required to be included in the [Assignement: configuration change management and control processes].

Assessment Method

Examine

System and services acquisition policy system and services acquisition procedures configuration management policy configuration management plan solicitation documentation requiring representatives for security and privacy acquisition documentation service level agreements acquisition contracts for the system, system component, or system service system developer configuration management plan change control records configuration management records system security plan other relevant documents or records

Interview

Organizational personnel with system and service acquisition responsibilities organizational personnel with information security and privacy responsibilities organizational personnel with configuration management responsibilities system developers

1.1 Referenzi

1.2 Rekwiżiti identifikati

1.3 Regolamenti relatati

2. Rekwiżiti identifikati

Rekwiżiti

3. Regolamenti relatati

Regolamenti

Kwistjonijiet marbuta

Links
is blocked by SA-10 Developer Configuration Management – Assessment Procedure
is blocked by Developer Configuration Management