Concept skos:Concept Code PR.IR-01.3

To ensure operational stability and security, the organisation shall, without exception, identify, document, and control connections between components of its critical systems.

Also known as

skos:altLabel

Critical system connection control

Note

skos:note

The goal of this control is to maintain operational stability and security by ensuring that all connections between components of critical systems are known, documented, and actively managed. In OTenvironments, undocumented or uncontrolled connections — whether physical, wireless, or logical — can introduce vulnerabilities, disrupt processes, or bypass safety mechanisms. To effectively manage and secure network connections between system components, the following practices should be considered:

  • Configuration Management Organisations should implement configuration management processes to ensure that all changes to network connections are documented, reviewed, and approved. Configuration files and logs should be kept current and securely maintained.
  • Access Controls Strict access controls should be enforced to ensure that only authorised personnel can modify network configurations. Role-Based Access Control (RBAC) should be used to restrict access based on job responsi- bilities and operational needs.
  • RegularAudits Regular audits should be conducted to verify that all documented connections remain accurate and that no unauthorisedchangeshaveoccurred.Auditresultsshouldbeusedtoupdatedocumentationandstrengthen controls.
  • Link to Asset Management (ID.AM) Connections between system components should be documented under ID.AM (Asset Management) and controlled under this requirement (PR.IR-01.3) to ensure consistency, traceability, and enforceability across the organisation’s cybersecurity architecture.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_PR_IR_01_3
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.IR-01.3: To ensure operational stability and security, the organisation shall, without exception, identify, document, and control connections between components of its critical systems.

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

PR.IR-01.3

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p132

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p91

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to maintain operational stability and security by ensuring that all connections between components of critical systems are known, documented, and actively managed. In OTenvironments, undocumented or uncontrolled connections — whether physical, wireless, or logical — can introduce vulnerabilities, disrupt processes, or bypass safety mechanisms. To effectively manage and secure network connections between system components, the following practices should be considered: • Configuration Management Organisations should implement configuration management processes to ensure that all changes to network connections are documented, reviewed, and approved. Configuration files and logs should be kept current and securely maintained. • Access Controls Strict access controls should be enforced to ensure that only authorised personnel can modify network configurations. Role-Based Access Control (RBAC) should be used to restrict access based on job responsi- bilities and operational needs. • RegularAudits Regular audits should be conducted to verify that all documented connections remain accurate and that no unauthorisedchangeshaveoccurred.Auditresultsshouldbeusedtoupdatedocumentationandstrengthen controls. • Link to Asset Management (ID.AM) Connections between system components should be documented under ID.AM (Asset Management) and controlled under this requirement (PR.IR-01.3) to ensure consistency, traceability, and enforceability across the organisation’s cybersecurity architecture.

note

A general note, for any purpose.

The goal of this control is to maintain operational stability and security by ensuring that all connections between components of critical systems are known, documented, and actively managed. In OTenvironments, undocumented or uncontrolled connections — whether physical, wireless, or logical — can introduce vulnerabilities, disrupt processes, or bypass safety mechanisms. To effectively manage and secure network connections between system components, the following practices should be considered: - Configuration Management Organisations should implement configuration management processes to ensure that all changes to network connections are documented, reviewed, and approved. Configuration files and logs should be kept current and securely maintained. - Access Controls Strict access controls should be enforced to ensure that only authorised personnel can modify network configurations. Role-Based Access Control (RBAC) should be used to restrict access based on job responsi- bilities and operational needs. - RegularAudits Regular audits should be conducted to verify that all documented connections remain accurate and that no unauthorisedchangeshaveoccurred.Auditresultsshouldbeusedtoupdatedocumentationandstrengthen controls. - Link to Asset Management (ID.AM) Connections between system components should be documented under ID.AM (Asset Management) and controlled under this requirement (PR.IR-01.3) to ensure consistency, traceability, and enforceability across the organisation’s cybersecurity architecture.

note

A general note, for any purpose.

The goal of this control is to maintain operational stability and security by ensuring that all connections between components of critical systems are known, documented, and actively managed. In OTenvironments, undocumented or uncontrolled connections — whether physical, wireless, or logical — can introduce vulnerabilities, disrupt processes, or bypass safety mechanisms. To effectively manage and secure network connections between system components, the following practices should be considered: - Configuration Management Organisations should implement configuration management processes to ensure that all changes to network connections are documented, reviewed, and approved. Configuration files and logs should be kept current and securely maintained. - Access Controls Strict access controls should be enforced to ensure that only authorised personnel can modify network configurations. Role-Based Access Control (RBAC) should be used to restrict access based on job responsi- bilities and operational needs. - RegularAudits Regular audits should be conducted to verify that all documented connections remain accurate and that no unauthorisedchangeshaveoccurred.Auditresultsshouldbeusedtoupdatedocumentationandstrengthen controls. - Link to Asset Management (ID.AM) Connections between system components should be documented under ID.AM (Asset Management) and controlled under this requirement (PR.IR-01.3) to ensure consistency, traceability, and enforceability across the organisation’s cybersecurity architecture.

note

A general note, for any purpose.

<div><p>The goal of this control is to maintain operational stability and security by ensuring that all connections between components of critical systems are known, documented, and actively managed. In OTenvironments, undocumented or uncontrolled connections — whether physical, wireless, or logical — can introduce vulnerabilities, disrupt processes, or bypass safety mechanisms. To effectively manage and secure network connections between system components, the following practices should be considered:</p><ul><li>Configuration Management Organisations should implement configuration management processes to ensure that all changes to network connections are documented, reviewed, and approved. Configuration files and logs should be kept current and securely maintained.</li><li>Access Controls Strict access controls should be enforced to ensure that only authorised personnel can modify network configurations. Role-Based Access Control (RBAC) should be used to restrict access based on job responsi- bilities and operational needs.</li><li>RegularAudits Regular audits should be conducted to verify that all documented connections remain accurate and that no unauthorisedchangeshaveoccurred.Auditresultsshouldbeusedtoupdatedocumentationandstrengthen controls.</li><li>Link to Asset Management (ID.AM) Connections between system components should be documented under ID.AM (Asset Management) and controlled under this requirement (PR.IR-01.3) to ensure consistency, traceability, and enforceability across the organisation’s cybersecurity architecture.</li></ul></div>

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.IR-01.3

alternative label

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

Critical system connection control

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.

To ensure operational stability and security, the organisation shall, without exception, identify, document, and control connections between components of its 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.