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. |
ID.AM-02.4: When unauthorised software is detected, it shall be quarantined for possible excep- tion handling, removed, or replaced, and the inventory shall be updated accordingly. |
|
ID.AM-02.4 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p49 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p35 |
|
|
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 internal network communications and data flows are clearly under- stood, properly documented, and kept up to date to support secure operations and informed decision-making across ICT and OT environments. To achieve this goal: • Establish Network Baselines Communication and data flows across wired, wireless, and cloud-based infrastructure (e.g. IaaS) should be mapped, documented, and authorised. Updates should be made when changes occur. • Document Technical Details Expected network ports, protocols, and services used between authorised systems should be recorded to support monitoring and troubleshooting. • Integrate with Configuration Management Configuration management processes should support the maintenance and validation of network flow documentation. • Ensure Resilient Documentation Network flow documentation should be stored securely and not solely on the network it describes. A pro- tected offline copy (e.g. encrypted external drive or hardcopy) should be maintained to ensure availability during outages or incidents. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that internal network communications and data flows are clearly under- stood, properly documented, and kept up to date to support secure operations and informed decision-making across ICT and OT environments. To achieve this goal:</p><ul><li>Establish Network Baselines Communication and data flows across wired, wireless, and cloud-based infrastructure (e.g. IaaS) should be mapped, documented, and authorised. Updates should be made when changes occur.</li><li>Document Technical Details Expected network ports, protocols, and services used between authorised systems should be recorded to support monitoring and troubleshooting.</li><li>Integrate with Configuration Management Configuration management processes should support the maintenance and validation of network flow documentation.</li><li>Ensure Resilient Documentation Network flow documentation should be stored securely and not solely on the network it describes. A pro- tected offline copy (e.g. encrypted external drive or hardcopy) should be maintained to ensure availability during outages or incidents.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that internal network communications and data flows are clearly under- stood, properly documented, and kept up to date to support secure operations and informed decision-making across ICT and OT environments. To achieve this goal: - Establish Network Baselines Communication and data flows across wired, wireless, and cloud-based infrastructure (e.g. IaaS) should be mapped, documented, and authorised. Updates should be made when changes occur. - Document Technical Details Expected network ports, protocols, and services used between authorised systems should be recorded to support monitoring and troubleshooting. - Integrate with Configuration Management Configuration management processes should support the maintenance and validation of network flow documentation. - Ensure Resilient Documentation Network flow documentation should be stored securely and not solely on the network it describes. A pro- tected offline copy (e.g. encrypted external drive or hardcopy) should be maintained to ensure availability during outages or incidents. |
|
A general note, for any purpose. |
The goal of this control is to ensure that internal network communications and data flows are clearly under- stood, properly documented, and kept up to date to support secure operations and informed decision-making across ICT and OT environments. To achieve this goal: - Establish Network Baselines Communication and data flows across wired, wireless, and cloud-based infrastructure (e.g. IaaS) should be mapped, documented, and authorised. Updates should be made when changes occur. - Document Technical Details Expected network ports, protocols, and services used between authorised systems should be recorded to support monitoring and troubleshooting. - Integrate with Configuration Management Configuration management processes should support the maintenance and validation of network flow documentation. - Ensure Resilient Documentation Network flow documentation should be stored securely and not solely on the network it describes. A pro- tected offline copy (e.g. encrypted external drive or hardcopy) should be maintained to ensure availability during outages or incidents. |
|
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.AM-02.4 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Unauthorised software handling |
|
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. |
When unauthorised software is detected, it shall be quarantined for possible excep- tion handling, removed, or replaced, and the inventory shall be updated accordingly. |
|
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_BASIC_to_IMPORTANT |
|
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. |
|
|
The number of triples associated with the subject. |
19 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 21 of 21
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1