Concept skos:Concept Code PR.DS-10.1

The organisation’s critical systems shall be protected against denial-of-service attacks or at least the effect of such attacks shall be limited.

Also known as

skos:altLabel

Denial-of-service protection

Note

skos:note

The goal of this control is to ensure that critical systems remain available and operational even when targeted by denial-of-service (DoS) attacks, which aim to overload or disrupt services. To achieve this goal, the organisation should:

  • Limit the impact of DoS attacks by:
    • Deploying boundary protection devices or services that filter malicious traffic.
    • Ensuring sufficient network capacity and redundancy to absorb traffic spikes.
  • Restrict the ability to launch DoS attacks by:
    • Limiting connectivity options to prevent unauthorised transmission over wired, wireless, or satellite links.
    • Enforcing resource usage limits to prevent system overload.
    • Applying strong authentication and authorisation to control access to critical functions.
  • Strengthen system resilience by:
    • Conducting regular security testing and audits to identify and address vulnerabilities.
    • Monitoring network traffic for anomalies that may indicate early signs of a DoS attempt.
  • OT-Specific Considerations In OT environments, where availability directly affects safety and production, even short disruptions can have severe consequences. DoS protections should be tailored to industrial protocols and legacy systems, ensuring that defences do not interfere with real-time operations.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_PR_DS_10_1
All data (19 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.DS-10.1: The organisation’s critical systems shall be protected against denial-of-service attacks or at least the effect of such attacks shall be limited.

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

PR.DS-10.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p115

has broader

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

http://cyfun.data.gift/data/subcategory_PR.DS-10

note

A general note, for any purpose.

The goal of this control is to ensure that critical systems remain available and operational even when targeted by denial-of-service (DoS) attacks, which aim to overload or disrupt services. To achieve this goal, the organisation should: • Limit the impact of DoS attacks by: o Deploying boundary protection devices or services that filter malicious traffic. o Ensuring sufficient network capacity and redundancy to absorb traffic spikes. • Restrict the ability to launch DoS attacks by: o Limiting connectivity options to prevent unauthorised transmission over wired, wireless, or satellite links. o Enforcing resource usage limits to prevent system overload. o Applying strong authentication and authorisation to control access to critical functions. • Strengthen system resilience by: o Conducting regular security testing and audits to identify and address vulnerabilities. o Monitoring network traffic for anomalies that may indicate early signs of a DoS attempt. • OT-Specific Considerations In OT environments, where availability directly affects safety and production, even short disruptions can have severe consequences. DoS protections should be tailored to industrial protocols and legacy systems, ensuring that defences do not interfere with real-time operations.

note

A general note, for any purpose.

The goal of this control is to ensure that critical systems remain available and operational even when targeted by denial-of-service (DoS) attacks, which aim to overload or disrupt services. To achieve this goal, the organisation should: - Limit the impact of DoS attacks by: - Deploying boundary protection devices or services that filter malicious traffic. - Ensuring sufficient network capacity and redundancy to absorb traffic spikes. - Restrict the ability to launch DoS attacks by: - Limiting connectivity options to prevent unauthorised transmission over wired, wireless, or satellite links. - Enforcing resource usage limits to prevent system overload. - Applying strong authentication and authorisation to control access to critical functions. - Strengthen system resilience by: - Conducting regular security testing and audits to identify and address vulnerabilities. - Monitoring network traffic for anomalies that may indicate early signs of a DoS attempt. - OT-Specific Considerations In OT environments, where availability directly affects safety and production, even short disruptions can have severe consequences. DoS protections should be tailored to industrial protocols and legacy systems, ensuring that defences do not interfere with real-time operations.

note

A general note, for any purpose.

The goal of this control is to ensure that critical systems remain available and operational even when targeted by denial-of-service (DoS) attacks, which aim to overload or disrupt services. To achieve this goal, the organisation should: - Limit the impact of DoS attacks by: - Deploying boundary protection devices or services that filter malicious traffic. - Ensuring sufficient network capacity and redundancy to absorb traffic spikes. - Restrict the ability to launch DoS attacks by: - Limiting connectivity options to prevent unauthorised transmission over wired, wireless, or satellite links. - Enforcing resource usage limits to prevent system overload. - Applying strong authentication and authorisation to control access to critical functions. - Strengthen system resilience by: - Conducting regular security testing and audits to identify and address vulnerabilities. - Monitoring network traffic for anomalies that may indicate early signs of a DoS attempt. - OT-Specific Considerations In OT environments, where availability directly affects safety and production, even short disruptions can have severe consequences. DoS protections should be tailored to industrial protocols and legacy systems, ensuring that defences do not interfere with real-time operations.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that critical systems remain available and operational even when targeted by denial-of-service (DoS) attacks, which aim to overload or disrupt services. To achieve this goal, the organisation should:</p><ul><li>Limit the impact of DoS attacks by:<ul><li>Deploying boundary protection devices or services that filter malicious traffic.</li><li>Ensuring sufficient network capacity and redundancy to absorb traffic spikes.</li></ul></li><li>Restrict the ability to launch DoS attacks by:<ul><li>Limiting connectivity options to prevent unauthorised transmission over wired, wireless, or satellite links.</li><li>Enforcing resource usage limits to prevent system overload.</li><li>Applying strong authentication and authorisation to control access to critical functions.</li></ul></li><li>Strengthen system resilience by:<ul><li>Conducting regular security testing and audits to identify and address vulnerabilities.</li><li>Monitoring network traffic for anomalies that may indicate early signs of a DoS attempt.</li></ul></li><li>OT-Specific Considerations In OT environments, where availability directly affects safety and production, even short disruptions can have severe consequences. DoS protections should be tailored to industrial protocols and legacy systems, ensuring that defences do not interfere with real-time operations.</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.DS-10.1

alternative label

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

Denial-of-service protection

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’s critical systems shall be protected against denial-of-service attacks or at least the effect of such attacks shall be limited.

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_IMPORTANT_to_ESSENTIAL

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_ESSENTIAL

triple count

The number of triples associated with the subject.

17

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 19 of 19

References

Inverse links to the subject.