Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:99_annexes:annex-b-terms-and-definitions:a:accreditation [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:a:accreditation [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Accreditation ======
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Accreditation establishes formal recognition that a defined system, service, facility, organization, or operational capability satisfies specified criteria within a defined scope and operating context.
 +
 +An accreditation process evaluates applicable requirements, implemented controls, identified risks, assessment results, operating procedures, and supporting [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. The resulting determination applies to the defined [[public:99_annexes:annex-b-terms-and-definitions:a:accreditation_boundary|Accreditation Boundary]].
 +
 +An [[public:99_annexes:annex-b-terms-and-definitions:a:authorizing_authority|Authorizing Authority]] uses the accreditation determination and supporting evidence when issuing an [[public:99_annexes:annex-b-terms-and-definitions:o:operational_approval|Operational Approval]].
 +
 +Accreditation differs from compliance. Compliance identifies conformity with specified requirements or criteria. Accreditation records formal recognition by an authorized body within a defined scope and context.
 +
 +===== Definition =====
 +
 +//formal recognition that a defined entity satisfies specified criteria within a defined scope and operating context//
 +
 +===== Source =====
 +
 +Generalised from conformity assessment, security accreditation, and risk management usage, and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +Accreditation applies only to the entity, boundary, configuration, criteria, and operational context identified in the accreditation decision.
 +
 +A change to the approved boundary, configuration, implemented controls, operating processes, or operational context may affect the continued applicability of the accreditation.
 +
 +===== Example =====
 +
 +An Authorizing Authority reviews the controls, risks, assessment results, operating procedures, and evidence of compliance associated with a defined Software Factory. The resulting accreditation records formal recognition that the factory satisfies the specified criteria within its approved Accreditation Boundary.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>