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.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. |
|
PR.DS-10.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p115 |
|
|
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 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. |
|
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. |
|
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. |
|
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> |
|
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 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Denial-of-service protection |
|
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. |
|
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