Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:s:security_plane [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:s:security_plane [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Security Plane ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Security Plane is an architectural plane that coordinates security controls and security-related information across system components, services, environments, | ||
| + | |||
| + | The Security Plane may coordinate capabilities such as: | ||
| + | |||
| + | * Identity management | ||
| + | * Authentication | ||
| + | * Authorization | ||
| + | * Access control | ||
| + | * Credential management | ||
| + | * Cryptographic key management | ||
| + | * Secrets management | ||
| + | * Security policy enforcement | ||
| + | * Security configuration | ||
| + | * Security monitoring | ||
| + | * Security event recording | ||
| + | * Vulnerability management | ||
| + | * Compliance evaluation | ||
| + | * Security Evidence collection | ||
| + | * Incident response | ||
| + | |||
| + | The Security Plane may interact with: | ||
| + | |||
| + | * Control-plane components | ||
| + | * Data-plane components | ||
| + | * Management-plane components | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * Operational services | ||
| + | * External security services | ||
| + | |||
| + | The Security Plane differs from an individual security control: | ||
| + | |||
| + | * A security control performs or enforces a bounded security function | ||
| + | * The Security Plane coordinates security concerns and controls across architectural elements | ||
| + | |||
| + | The Security Plane also differs from a [[public: | ||
| + | |||
| + | * A Security Baseline establishes an approved reference for required security characteristics | ||
| + | * The Security Plane coordinates the capabilities that apply, enforce, observe, or evaluate security characteristics | ||
| + | |||
| + | A Security Plane may be logically distinct without being implemented as a separate physical subsystem. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | The Security Plane may provide centralized, | ||
| + | |||
| + | An architectural element may participate in more than one plane. For example, a deployment service may perform deployment operations within a management or control plane while using the Security Plane for authorization, | ||
| + | |||
| + | The Security Plane does not imply that security responsibilities belong only to components assigned to that plane. Every architectural element remains responsible for satisfying its applicable security requirements. | ||
| + | |||
| + | The term does not prescribe a particular security architecture, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | The Security Plane authenticates a CI/CD Pipeline, authorizes access to an identified Infrastructure Configuration, | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||