8.4 Generate Supporting Evidence [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 8.4 Generate Supporting Evidence ======

[[dido:02-crusible:08-compliance-and-authorization-operations:start|Go to 8. Compliance Operations]]

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] generates [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance|Compliance]] [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] Artifacts from the applicable compliance activities and results.

The generated Evidence supports review of the assessed subject, the selected compliance criteria, and the results produced by the Compliance Assessment.

Evidence generation does not independently establish compliance, approve an exception, accept risk, grant Operational Approval, or issue an Authority to Operate.

===== Identify the Evidence Subject =====

Crucible associates each generated Evidence Artifact with the subject to which the Evidence applies.

The Evidence subject can include:

  * A Machine Image
  * A Container Image
  * An Infrastructure Configuration
  * An Infrastructure Environment
  * A deployed resource
  * Another subject evaluated through an applicable Compliance Assessment

The subject remains identifiable so an authorized reviewer can determine which artifact, resource, environment, or revision the Evidence describes.

===== Identify the Supporting Assessment =====

The generated Evidence remains associated with the compliance activity that produced it.

The association can identify:

  * The assessment subject
  * The subject revision
  * The selected Compliance Baseline
  * The applicable compliance criteria
  * The assessment provider
  * The provider revision
  * The assessment result
  * The assessment time

The Evidence does not apply automatically to another subject or revision.

===== Generate Compliance Evidence Artifacts =====

Crucible generates Compliance Evidence Artifacts from the applicable assessment inputs and results.

A Compliance Evidence Artifact can contain or reference:

  * The assessed subject
  * The selected Compliance Baseline
  * The applicable compliance criterion
  * The observed condition
  * The assessment result
  * The assessment provider
  * Supporting provider output
  * Relevant assessment metadata
  * The relationship between the Evidence and the assessed subject

The applicable requirement does not prescribe one Evidence format, schema, repository, or presentation technology.

===== Generate Security Control Traceability Matrix Evidence =====

Crucible generates Evidence supporting Security Control Traceability Matrix activities.

The Evidence can relate:

  * A security control
  * The assessed subject
  * The applicable compliance criterion
  * The assessment result
  * The supporting Compliance Evidence Artifact

The responsible organization determines how the Evidence contributes to its Security Control Traceability Matrix.

Crucible does not independently determine that a security control is fully implemented, inherited, accepted, or approved.

===== Generate Risk Management Framework Evidence =====

Crucible generates Evidence supporting Risk Management Framework activities.

The Evidence can support review of:

  * The assessed subject
  * Applicable security controls
  * Compliance Assessment results
  * Identified deficiencies
  * Supporting Compliance Evidence Artifacts

The responsible organization determines how the Evidence applies within its Risk Management Framework process.

Crucible does not select the organization’s risk response, approve a remediation plan, or accept residual risk.

===== Generate Authority to Operate Evidence =====

Crucible generates Evidence supporting Authority to Operate activities.

The Evidence can provide information used by authorized personnel to evaluate:

  * The assessed subject
  * Applicable compliance criteria
  * Security-control implementation
  * Assessment results
  * Identified deficiencies
  * Supporting Compliance Evidence Artifacts

Crucible supports the authorization process by generating Evidence. Crucible does not grant, deny, renew, suspend, or revoke an Authority to Operate.

===== Maintain Evidence Associations During Generation =====

During generation, Crucible maintains the relationship among:

  * The Evidence Artifact
  * The assessed subject
  * The applicable criterion or security control
  * The Compliance Assessment
  * The assessment result
  * The authorization-supporting activity

These associations allow an authorized reviewer to determine what the Evidence describes and why Crucible generated it.

This capability does not establish a general requirement to preserve, retain, archive, or retrieve the generated Evidence after its production.

===== Evidence-Generation Result =====

The Evidence-generation result identifies:

  * The generated Compliance Evidence Artifacts
  * The subjects associated with the Evidence
  * The applicable Compliance Assessments
  * The selected compliance criteria
  * The related security controls, when applicable
  * The authorization-supporting activity
  * The Evidence-generation status
  * Any Evidence that could not be generated

The generated Evidence becomes available to the applicable review, Security Control Traceability Matrix, Risk Management Framework, or Authority to Operate activity.

===== Requirements Addressed =====

^ Requirement ^ Statement ^
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-004:start]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-004:start#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-009:fr-comp-009a]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-009:fr-comp-009a#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-009:fr-comp-009b]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-009:fr-comp-009b#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-009:fr-comp-009c]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-009:fr-comp-009c#Statement&noheader&nofooter&noeditbtn}} |

The linked leaf requirement pages remain the canonical sources.

===== Notes for Editors =====

The approved requirements establish Evidence generation and authorization-supporting Evidence. They do not establish Evidence preservation, retention, archival storage, or retrieval.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>