Concept skos:Concept Code ID.RA-01.5

Vulnerability scanning shall not adversely impact system functions.

Also known as

skos:altLabel

Non-disruptive vulnerability scanning

Note

skos:note

The goal of this control is to ensure that vulnerability scanning does not disrupt or degrade the performance of business-critical systems, particularly in Operational Technology (OT) environments where system stability and availability are critical. To achieve this goal, the organisation should:

  • Schedule Scans During Low-Usage Periods Scans should be performed during off-peak hours or planned maintenance windows to minimise operational impact.
  • Use Non-Intrusive Scanning Tools Tools should be selected based on their ability to scan without overloading system resources or interfering with real-time operations.
  • Test in Staging Environments First Scans should be trialled in non-production environments to identify potential issues before deployment in live systems.
  • Apply Incremental Scanning Scanning should be broken down into smaller, manageable segments to reduce system load and avoid over- whelming critical components.
  • Monitor System Performance During Scans System behaviour should be actively monitored during scanning to detect and respond to any performance degradation or anomalies. Distinction from ID.RA-01.4 (CyFun Essential) WhileID.RA-01.4focusesontestingactivitiessuchaspenetrationandloadtesting,whicharetypicallyplanned, infrequent, and often conducted in controlled environments, ID.RA-01.5 addresses the safe execution of vulnerability scanning, which is more frequent, often automated, and must be carefully managed to avoid unintended disruptions in live OT systems.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_RA_01_5
All data (21 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.

ID.RA-01.5: Vulnerability scanning shall not adversely impact system functions.

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

ID.RA-01.5

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p65

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p47

has broader

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

http://cyfun.data.gift/data/subcategory_ID.RA-01

note

A general note, for any purpose.

The goal of this control is to ensure that vulnerability scanning does not disrupt or degrade the performance of business-critical systems, particularly in Operational Technology (OT) environments where system stability and availability are critical. To achieve this goal, the organisation should: - Schedule Scans During Low-Usage Periods Scans should be performed during off-peak hours or planned maintenance windows to minimise operational impact. - Use Non-Intrusive Scanning Tools Tools should be selected based on their ability to scan without overloading system resources or interfering with real-time operations. - Test in Staging Environments First Scans should be trialled in non-production environments to identify potential issues before deployment in live systems. - Apply Incremental Scanning Scanning should be broken down into smaller, manageable segments to reduce system load and avoid over- whelming critical components. - Monitor System Performance During Scans System behaviour should be actively monitored during scanning to detect and respond to any performance degradation or anomalies. Distinction from ID.RA-01.4 (CyFun Essential) WhileID.RA-01.4focusesontestingactivitiessuchaspenetrationandloadtesting,whicharetypicallyplanned, infrequent, and often conducted in controlled environments, ID.RA-01.5 addresses the safe execution of vulnerability scanning, which is more frequent, often automated, and must be carefully managed to avoid unintended disruptions in live OT systems.

note

A general note, for any purpose.

The goal of this control is to ensure that vulnerability scanning does not disrupt or degrade the performance of business-critical systems, particularly in Operational Technology (OT) environments where system stability and availability are critical. To achieve this goal, the organisation should: • Schedule Scans During Low-Usage Periods Scans should be performed during off-peak hours or planned maintenance windows to minimise operational impact. • Use Non-Intrusive Scanning Tools Tools should be selected based on their ability to scan without overloading system resources or interfering with real-time operations. • Test in Staging Environments First Scans should be trialled in non-production environments to identify potential issues before deployment in live systems. • Apply Incremental Scanning Scanning should be broken down into smaller, manageable segments to reduce system load and avoid over- whelming critical components. • Monitor System Performance During Scans System behaviour should be actively monitored during scanning to detect and respond to any performance degradation or anomalies. Distinction from ID.RA-01.4 (CyFun Essential) WhileID.RA-01.4focusesontestingactivitiessuchaspenetrationandloadtesting,whicharetypicallyplanned, infrequent, and often conducted in controlled environments, ID.RA-01.5 addresses the safe execution of vulnerability scanning, which is more frequent, often automated, and must be carefully managed to avoid unintended disruptions in live OT systems.

note

A general note, for any purpose.

The goal of this control is to ensure that vulnerability scanning does not disrupt or degrade the performance of business-critical systems, particularly in Operational Technology (OT) environments where system stability and availability are critical. To achieve this goal, the organisation should: - Schedule Scans During Low-Usage Periods Scans should be performed during off-peak hours or planned maintenance windows to minimise operational impact. - Use Non-Intrusive Scanning Tools Tools should be selected based on their ability to scan without overloading system resources or interfering with real-time operations. - Test in Staging Environments First Scans should be trialled in non-production environments to identify potential issues before deployment in live systems. - Apply Incremental Scanning Scanning should be broken down into smaller, manageable segments to reduce system load and avoid over- whelming critical components. - Monitor System Performance During Scans System behaviour should be actively monitored during scanning to detect and respond to any performance degradation or anomalies. Distinction from ID.RA-01.4 (CyFun Essential) WhileID.RA-01.4focusesontestingactivitiessuchaspenetrationandloadtesting,whicharetypicallyplanned, infrequent, and often conducted in controlled environments, ID.RA-01.5 addresses the safe execution of vulnerability scanning, which is more frequent, often automated, and must be carefully managed to avoid unintended disruptions in live OT systems.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that vulnerability scanning does not disrupt or degrade the performance of business-critical systems, particularly in Operational Technology (OT) environments where system stability and availability are critical. To achieve this goal, the organisation should:</p><ul><li>Schedule Scans During Low-Usage Periods Scans should be performed during off-peak hours or planned maintenance windows to minimise operational impact.</li><li>Use Non-Intrusive Scanning Tools Tools should be selected based on their ability to scan without overloading system resources or interfering with real-time operations.</li><li>Test in Staging Environments First Scans should be trialled in non-production environments to identify potential issues before deployment in live systems.</li><li>Apply Incremental Scanning Scanning should be broken down into smaller, manageable segments to reduce system load and avoid over- whelming critical components.</li><li>Monitor System Performance During Scans System behaviour should be actively monitored during scanning to detect and respond to any performance degradation or anomalies. Distinction from ID.RA-01.4 (CyFun Essential) WhileID.RA-01.4focusesontestingactivitiessuchaspenetrationandloadtesting,whicharetypicallyplanned, infrequent, and often conducted in controlled environments, ID.RA-01.5 addresses the safe execution of vulnerability scanning, which is more frequent, often automated, and must be carefully managed to avoid unintended disruptions in live OT systems.</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.

ID.RA-01.5

alternative label

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

Non-disruptive vulnerability scanning

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.

Vulnerability scanning shall not adversely impact system functions.

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_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

triple count

The number of triples associated with the subject.

19

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 21 of 21

References

Inverse links to the subject.