Direct links from the subject.
| Property | Value |
|---|---|
|
The subject is an instance of a class. |
|
|
The subject is an instance of a class. |
An idea or notion; a unit of thought. |
|
A human-readable name for the subject. |
PR.PS-01.1: The organisation shall develop, document, and maintain a baseline configuration for its business critical systems. |
|
PR.PS-01.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p84 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p120 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
<div><p>This control ensures that all business-critical systems operate in a known, secure, and approved state.Abaseline configuration defines the standard setup for these systems, helping to detect unauthorised changes, enforce security policies, and support consistent operations. To implement this control the following should be considered:</p><ul><li>Definition of what is Business-Critical Business-critical systems mayinclude IT, OT(OperationalTechnology), and potentiallyIoT(Internet ofThings) components — if they support essential business functions:<ul><li>IT systems are typically managed internally.</li><li>OT systems may include industrial control systems.</li><li>IoTsystems (e.g. sensors, smart devices) can be business-critical iftheirfailure disrupts operations orintro- duces security risks.</li></ul></li><li>Establish and Maintain Baseline Configurations For each business-critical system, the baseline should include:<ul><li>System components (e.g. approved software, hardware)</li><li>Operating system and application versions, including patch levels</li><li>Configuration settings and parameters</li><li>Network topology, showing how components are connected, including:<ul><li>External connections</li><li>Servers hosting sensitive data or functions</li><li>DNS and security services</li></ul></li><li>Logical placement of components within the system architecture</li></ul></li><li>Apply Security Principles<ul><li>Baselines should enforce the principle of least functionality — only necessary features and services should be enabled.</li><li>Default settings should be reviewed and adjusted to reduce security risks during installation or upgrades.</li></ul></li><li>Monitor and Update<ul><li>Continuously monitor systems for deviations from the approved baseline.</li><li>Update baselines when systems are patched, upgraded, or reconfigured.</li></ul></li><li>Cloud and Supplier-Managed Systems For systems managed by third parties (e.g. cloud services), ensure that baseline expectations are defined contractually and that suppliers provide visibility into configuration and change management.</li></ul></div> |
|
A general note, for any purpose. |
This control ensures that all business-critical systems operate in a known, secure, and approved state.Abaseline configuration defines the standard setup for these systems, helping to detect unauthorised changes, enforce security policies, and support consistent operations. To implement this control the following should be considered: • Definition of what is Business-Critical Business-critical systems mayinclude IT, OT(OperationalTechnology), and potentiallyIoT(Internet ofThings) components — if they support essential business functions: o IT systems are typically managed internally. o OT systems may include industrial control systems. o IoTsystems (e.g. sensors, smart devices) can be business-critical iftheirfailure disrupts operations orintro- duces security risks. • Establish and Maintain Baseline Configurations For each business-critical system, the baseline should include: o System components (e.g. approved software, hardware) o Operating system and application versions, including patch levels o Configuration settings and parameters o Network topology, showing how components are connected, including: - External connections - Servers hosting sensitive data or functions - DNS and security services o Logical placement of components within the system architecture • Apply Security Principles o Baselines should enforce the principle of least functionality — only necessary features and services should be enabled. o Default settings should be reviewed and adjusted to reduce security risks during installation or upgrades. • Monitor and Update o Continuously monitor systems for deviations from the approved baseline. o Update baselines when systems are patched, upgraded, or reconfigured. • Cloud and Supplier-Managed Systems For systems managed by third parties (e.g. cloud services), ensure that baseline expectations are defined contractually and that suppliers provide visibility into configuration and change management. |
|
A general note, for any purpose. |
This control ensures that all business-critical systems operate in a known, secure, and approved state.Abaseline configuration defines the standard setup for these systems, helping to detect unauthorised changes, enforce security policies, and support consistent operations. To implement this control the following should be considered: - Definition of what is Business-Critical Business-critical systems mayinclude IT, OT(OperationalTechnology), and potentiallyIoT(Internet ofThings) components — if they support essential business functions: - IT systems are typically managed internally. - OT systems may include industrial control systems. - IoTsystems (e.g. sensors, smart devices) can be business-critical iftheirfailure disrupts operations orintro- duces security risks. - Establish and Maintain Baseline Configurations For each business-critical system, the baseline should include: - System components (e.g. approved software, hardware) - Operating system and application versions, including patch levels - Configuration settings and parameters - Network topology, showing how components are connected, including: - External connections - Servers hosting sensitive data or functions - DNS and security services - Logical placement of components within the system architecture - Apply Security Principles - Baselines should enforce the principle of least functionality — only necessary features and services should be enabled. - Default settings should be reviewed and adjusted to reduce security risks during installation or upgrades. - Monitor and Update - Continuously monitor systems for deviations from the approved baseline. - Update baselines when systems are patched, upgraded, or reconfigured. - Cloud and Supplier-Managed Systems For systems managed by third parties (e.g. cloud services), ensure that baseline expectations are defined contractually and that suppliers provide visibility into configuration and change management. |
|
A general note, for any purpose. |
This control ensures that all business-critical systems operate in a known, secure, and approved state.Abaseline configuration defines the standard setup for these systems, helping to detect unauthorised changes, enforce security policies, and support consistent operations. To implement this control the following should be considered: - Definition of what is Business-Critical Business-critical systems mayinclude IT, OT(OperationalTechnology), and potentiallyIoT(Internet ofThings) components — if they support essential business functions: - IT systems are typically managed internally. - OT systems may include industrial control systems. - IoTsystems (e.g. sensors, smart devices) can be business-critical iftheirfailure disrupts operations orintro- duces security risks. - Establish and Maintain Baseline Configurations For each business-critical system, the baseline should include: - System components (e.g. approved software, hardware) - Operating system and application versions, including patch levels - Configuration settings and parameters - Network topology, showing how components are connected, including: - External connections - Servers hosting sensitive data or functions - DNS and security services - Logical placement of components within the system architecture - Apply Security Principles - Baselines should enforce the principle of least functionality — only necessary features and services should be enabled. - Default settings should be reviewed and adjusted to reduce security risks during installation or upgrades. - Monitor and Update - Continuously monitor systems for deviations from the approved baseline. - Update baselines when systems are patched, upgraded, or reconfigured. - Cloud and Supplier-Managed Systems For systems managed by third parties (e.g. cloud services), ensure that baseline expectations are defined contractually and that suppliers provide visibility into configuration and change management. |
|
A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme. |
PR.PS-01.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Baseline configuration management |
|
A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag. |
The organisation shall develop, document, and maintain a baseline configuration for its business critical systems. |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
http://cyfun.data.gift/data/CyFun2025_delta_BASIC_to_IMPORTANT |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
1 |
|
|
The number of triples associated with the subject. |
21 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 23 of 23
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1