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.IR-01.7: The organisation shall ensure that development and test environments are strictly separated from the production environment, particularly in ICS/OT systems where any crossover could compromise safety, endanger health, or disrupt essential operations. |
|
PR.IR-01.7 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p137 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
The goal of this control is to prevent unintended disruptions, safetyrisks, orsecuritybreaches byensuring that development and testing activities do not interfere with live operational systems. In OT environments, such as Industrial Control Systems (ICS), even minor crossovers between test and pro- duction can lead to unsafe conditions, process interruptions, or exposure of sensitive configurations. Strict separation helps maintain system integrity, supports change control, and reduces the risk of accidental or malicious actions affecting critical operations. To achieve this goal, the following should be considered: - Strict Environment Separation Development and testing activities should be conducted in environments that are physically or logically separated from the production environment. This is especially critical in ICS/OT settings, where operational safety and reliability must not be compromised. - Pre-Deployment Testing Anychange intended for the ICTor OTenvironment should first be tested in a non-production environment. This allows for the evaluation of potential impacts and necessary adjustments before deployment. - Realistic Test Environments Test environments should closely replicate the production environment in terms of configuration, architec- ture, and data flow, to ensure accurate testing outcomes. - Secure Development Practices Cybersecurity features should be integrated and tested as early as possible in the development lifecycle, following secure development lifecycle (SDLC) principles. |
|
A general note, for any purpose. |
The goal of this control is to prevent unintended disruptions, safetyrisks, orsecuritybreaches byensuring that development and testing activities do not interfere with live operational systems. In OT environments, such as Industrial Control Systems (ICS), even minor crossovers between test and pro- duction can lead to unsafe conditions, process interruptions, or exposure of sensitive configurations. Strict separation helps maintain system integrity, supports change control, and reduces the risk of accidental or malicious actions affecting critical operations. To achieve this goal, the following should be considered: - Strict Environment Separation Development and testing activities should be conducted in environments that are physically or logically separated from the production environment. This is especially critical in ICS/OT settings, where operational safety and reliability must not be compromised. - Pre-Deployment Testing Anychange intended for the ICTor OTenvironment should first be tested in a non-production environment. This allows for the evaluation of potential impacts and necessary adjustments before deployment. - Realistic Test Environments Test environments should closely replicate the production environment in terms of configuration, architec- ture, and data flow, to ensure accurate testing outcomes. - Secure Development Practices Cybersecurity features should be integrated and tested as early as possible in the development lifecycle, following secure development lifecycle (SDLC) principles. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to prevent unintended disruptions, safetyrisks, orsecuritybreaches byensuring that development and testing activities do not interfere with live operational systems. In OT environments, such as Industrial Control Systems (ICS), even minor crossovers between test and pro- duction can lead to unsafe conditions, process interruptions, or exposure of sensitive configurations. Strict separation helps maintain system integrity, supports change control, and reduces the risk of accidental or malicious actions affecting critical operations. To achieve this goal, the following should be considered:</p><ul><li>Strict Environment Separation Development and testing activities should be conducted in environments that are physically or logically separated from the production environment. This is especially critical in ICS/OT settings, where operational safety and reliability must not be compromised.</li><li>Pre-Deployment Testing Anychange intended for the ICTor OTenvironment should first be tested in a non-production environment. This allows for the evaluation of potential impacts and necessary adjustments before deployment.</li><li>Realistic Test Environments Test environments should closely replicate the production environment in terms of configuration, architec- ture, and data flow, to ensure accurate testing outcomes.</li><li>Secure Development Practices Cybersecurity features should be integrated and tested as early as possible in the development lifecycle, following secure development lifecycle (SDLC) principles.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to prevent unintended disruptions, safetyrisks, orsecuritybreaches byensuring that development and testing activities do not interfere with live operational systems. In OT environments, such as Industrial Control Systems (ICS), even minor crossovers between test and pro- duction can lead to unsafe conditions, process interruptions, or exposure of sensitive configurations. Strict separation helps maintain system integrity, supports change control, and reduces the risk of accidental or malicious actions affecting critical operations. To achieve this goal, the following should be considered: • Strict Environment Separation Development and testing activities should be conducted in environments that are physically or logically separated from the production environment. This is especially critical in ICS/OT settings, where operational safety and reliability must not be compromised. • Pre-Deployment Testing Anychange intended for the ICTor OTenvironment should first be tested in a non-production environment. This allows for the evaluation of potential impacts and necessary adjustments before deployment. • Realistic Test Environments Test environments should closely replicate the production environment in terms of configuration, architec- ture, and data flow, to ensure accurate testing outcomes. • Secure Development Practices Cybersecurity features should be integrated and tested as early as possible in the development lifecycle, following secure development lifecycle (SDLC) principles. |
|
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.7 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Environment separation (dev/test/prod) |
|
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 ensure that development and test environments are strictly separated from the production environment, particularly in ICS/OT systems where any crossover could compromise safety, endanger health, or disrupt essential operations. |
|
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_IMPORTANT_to_ESSENTIAL |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
17 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 19 of 19
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1