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_baseline [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:s:security_baseline [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Security Baseline ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Security Baseline is a specialization of [[public: | ||
| + | |||
| + | The general concept of Baseline provides the controlled reference against which a subject can be compared, evaluated, changed, or restored. | ||
| + | |||
| + | A Security Baseline applies that concept to the security characteristics of a subject such as: | ||
| + | |||
| + | * An [[public: | ||
| + | * A [[public: | ||
| + | * An operating system | ||
| + | * A network | ||
| + | * A platform | ||
| + | * A software component | ||
| + | * A service | ||
| + | * A device | ||
| + | * An [[public: | ||
| + | |||
| + | A Security Baseline may identify: | ||
| + | |||
| + | * Required security controls | ||
| + | * Required configuration values | ||
| + | * Permitted services and protocols | ||
| + | * Prohibited services and protocols | ||
| + | * Identity and access settings | ||
| + | * Authentication requirements | ||
| + | * Authorization requirements | ||
| + | * Cryptographic requirements | ||
| + | * Logging and monitoring requirements | ||
| + | * Vulnerability-management settings | ||
| + | * Network-security settings | ||
| + | * Data-protection settings | ||
| + | * Applicable constraints | ||
| + | * Applicable [[public: | ||
| + | |||
| + | A Security Baseline differs from a security policy: | ||
| + | |||
| + | * A security policy establishes governing security rules and objectives | ||
| + | * A Security Baseline establishes a controlled reference containing the security characteristics used to realize or evaluate those rules and objectives | ||
| + | |||
| + | A Security Baseline also differs from an observed security state: | ||
| + | |||
| + | * The Security Baseline identifies the approved reference state | ||
| + | * The observed security state identifies the security characteristics present in the evaluated subject | ||
| + | |||
| + | Comparing the observed security state with the Security Baseline may identify a [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Security Baseline may derive from: | ||
| + | |||
| + | * Laws | ||
| + | * Regulations | ||
| + | * Standards | ||
| + | * Organizational policies | ||
| + | * Contractual obligations | ||
| + | * Threat assessments | ||
| + | * Risk assessments | ||
| + | * Platform-security guidance | ||
| + | * Operational requirements | ||
| + | |||
| + | A Security Baseline should have an identifiable revision so an evaluator can determine which reference applies to a particular assessment, deployment, or operational state. | ||
| + | |||
| + | Approval of a Security Baseline does not establish that every subject conforms to it. Conformance requires comparison of the subject with the applicable Security Baseline. | ||
| + | |||
| + | The term does not require a particular security framework, assessment method, configuration format, repository, tool, or implementation technology. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Security Baseline for a [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||