Differences

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

--- public:99_annexes:annex-b-terms-and-definitions:a:accreditation_boundary [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1
+++ public:99_annexes:annex-b-terms-and-definitions:a:accreditation_boundary [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== Accreditation Boundary ======
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+An Accreditation Boundary identifies the systems, components, services, information, interfaces, infrastructure, processes, personnel roles, and operating environments included within an [[public:99_annexes:annex-b-terms-and-definitions:a:accreditation|Accreditation]].
+The boundary establishes the scope of the applicable requirements, controls, assessments, risks, and supporting [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. It also distinguishes included elements from external systems, services, organizations, and dependencies.
+An Accreditation Boundary may contain internal subdivisions, trust boundaries, deployment environments, or responsibility boundaries. Those subdivisions remain part of the Accreditation Boundary when the accreditation includes them.
+For an [[public:99_annexes:annex-b-terms-and-definitions:a:accredited_software_factory|Accredited Software Factory]], the boundary identifies the factory components and operational processes covered by the applicable [[public:99_annexes:annex-b-terms-and-definitions:o:operational_approval|Operational Approval]].
+===== Definition =====
+//defined scope of the systems, components, services, information, interfaces, infrastructure, processes, personnel roles, and operating environments included within an [[public:99_annexes:annex-b-terms-and-definitions:a:accreditation|accreditation]]//
+===== Source =====
+Generalised from security-accreditation, authorization-boundary, conformity-assessment, and risk-management usage and specialized for the Crucible architecture and operational model.
+===== Note =====
+An Accreditation Boundary defines the scope of an accreditation rather than a physical boundary alone. The boundary may include distributed components, external services under defined agreements, connected environments, and disconnected environments.
+A dependency located outside the Accreditation Boundary may still affect the risks, controls, or evidence associated with the accredited entity.
+===== Example =====
+The Accreditation Boundary for a Software Factory includes source-control services, build services, hardened build workers, dependency repositories, artifact repositories, compliance services, deployment automation, administrative processes, and approved interfaces to external infrastructure providers.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>