This shows you the differences between two versions of the page.
| |
| dido:99_annexes:annex-b-terms-and-definitions:a:accredited_software_factory [2026/07/13 09:25] – created nick_dido | dido:99_annexes:annex-b-terms-and-definitions:a:accredited_software_factory [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ===== Source ===== | ===== Source ===== |
| |
| Generalised from software-factory, security-accreditation, and risk-management usage and specialised for the Crucible architecture and operational model. | Generalised from software-factory, security-accreditation, and risk-management usage and specialized for the Crucible architecture and operational model. |
| |
| ===== Note ===== | ===== Note ===== |
| Accreditation applies to the approved boundary, configuration, controls, operating processes, and operational context. Accreditation of the Software Factory does not automatically establish accreditation of every product produced by the factory or every environment into which a product is deployed. | Accreditation applies to the approved boundary, configuration, controls, operating processes, and operational context. Accreditation of the Software Factory does not automatically establish accreditation of every product produced by the factory or every environment into which a product is deployed. |
| |
| A Software Factory that implements security controls or produces compliance evidence does not become an Accredited Software Factory until an Authorising Authority issues the applicable Operational Approval. | A Software Factory that implements security controls or produces compliance evidence does not become an Accredited Software Factory until an Authorizing Authority issues the applicable Operational Approval. |
| |
| ===== Example ===== | ===== Example ===== |
| |
| An organisation uses Crucible to reproduce a Software Factory from pinned source repositories, hardened machine images, controlled infrastructure baselines, captured dependencies, and traceable evidence of compliance. An Authorising Authority evaluates the defined Accreditation Boundary and issues an Operational Approval for the factory. | An organization uses Crucible to reproduce a Software Factory from pinned source repositories, hardened machine images, controlled infrastructure baselines, captured dependencies, and traceable evidence of compliance. An Authorizing Authority evaluates the defined Accreditation Boundary and issues an Operational Approval for the factory. |
| |
| ---- | ---- |