03.17.04E Provenance

Statement

Document, monitor, and maintain valid provenance of the following systems, system components, and associated CUI: {{ insert: param, A.03.17.04E.ODP.01 }}.

Guidance

Every system and system component has a point of origin and may be changed throughout its existence. Provenance is the chronology of the origin, development, ownership, location, and changes to a system or system component and associated data. It may also include personnel and processes used to interact with or make modifications to the system, component, or associated data. Organizations have methods to document, monitor, and maintain valid provenance baselines for systems, system components, and related data. These actions help track, assess, and document any changes to the provenance, including changes in supply chain elements or configuration, and help ensure non-repudiation of provenance information and the provenance change records. This requirement does not enhance a specific requirement in SP 800-171 but can be used to strengthen the protection of CUI associated with critical programs or high value assets.

Statement

• (includes detect) Reduce risk due to ignorance of threat events and possible replicated or similar threat events in the same or similar environments.

  • Reduce likelihood of impact.

  • The adversary loses the advantage of stealth as defenders are better prepared by developing and sharing threat intelligence.

Assessment objective

valid provenance is documented for {{ insert: param, A.03.17.04E.ODP.01 }}.

Assessment objective

valid provenance is monitored for {{ insert: param, A.03.17.04E.ODP.01 }}.

Assessment objective

valid provenance is maintained for {{ insert: param, A.03.17.04E.ODP.01 }}.

Assessment method

• Supply chain risk management policy supply chain risk management procedures supply chain risk management plan documentation of critical systems, critical system components, and associated data documentation showing the history of ownership, custody, and location of and changes to critical systems or critical system components system architecture inter-organizational agreements and procedures contracts system security plan other relevant documents or records

Assessment method

• Organizational personnel with acquisition responsibilities organizational personnel with information security responsibilities organizational personnel with supply chain risk management responsibilities

Assessment method

• Organizational processes for identifying the provenance of critical systems and critical system components mechanisms used to document, monitor, or maintain provenance

1. Overview

1.1 References

1.2 Identified Requirements

1.3 Related Regulations

2. Identified Requirements

3. Related Regulations

Linked Issues

• NIST -

  https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final