Concept skos:Concept Code PR.PS-01.1

The organisation shall develop, document, and maintain a baseline configuration for its business critical systems.

Also known as

skos:altLabel

Baseline configuration management

Note

skos:note

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.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_PR_PS_01_1
All data (23 statements)

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

http://cyfun.data.gift/ontology#Requirement

type

The subject is an instance of a class.

Concept

An idea or notion; a unit of thought.

label

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.

http://cyfun.data.gift/ontology#requirementId

PR.PS-01.1

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p84

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p120

has broader

Relates a concept to a concept that is more general in meaning.

http://cyfun.data.gift/data/subcategory_PR.PS-01

note

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>

note

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.

note

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.

note

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.

notation

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

alternative label

skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.

Baseline configuration management

preferred label

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.

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_KeyMeasures

is in scheme

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

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_IMPORTANT

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

http://cyfun.data.gift/ontology#level

http://cyfun.data.gift/data/level_IMPORTANT

http://cyfun.data.gift/ontology#isKeyMeasure

1

triple count

The number of triples associated with the subject.

21

in dataset

Specifies the dataset the subject is part of.

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

Resultaten 1 - 23 of 23

References

Inverse links to the subject.