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-01.4: Mechanisms for detecting the presence of unauthorised hardware and firmware components within the organisation’s ICT/OT environment shall be identified. |
|
ID.AM-01.4 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p47 |
|
|
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 proactively identify unauthorised hardware and firmware components within ICT and OT environments, thereby enabling timely response and reducing the risk of compromise or operational disruption. To achieve this goal: - Automate Where Feasible Detection mechanisms should be automated where safe and technically possible, especially in complex or high-risk environments. - Continuously Monitor Networks Networks should be continuously monitored to detect new or unauthorised hardware and firmware com- ponents. Detected changes should trigger automatic updates to the asset inventory. - Establish a Response Process A defined process should exist to regularly review and address unauthorised components. - For unauthorised hardware, refer to ID.AM-01.3 - For unauthorised firmware, refer to ID.AM-02.4 - Include OT-Specific Considerations Detection methods in OTenvironments should account forsafety, availability, andvendor-specific constraints when identifying unauthorised components. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to proactively identify unauthorised hardware and firmware components within ICT and OT environments, thereby enabling timely response and reducing the risk of compromise or operational disruption. To achieve this goal:</p><ul><li>Automate Where Feasible Detection mechanisms should be automated where safe and technically possible, especially in complex or high-risk environments.</li><li>Continuously Monitor Networks Networks should be continuously monitored to detect new or unauthorised hardware and firmware com- ponents. Detected changes should trigger automatic updates to the asset inventory.</li><li>Establish a Response Process A defined process should exist to regularly review and address unauthorised components.<ul><li>For unauthorised hardware, refer to ID.AM-01.3</li><li>For unauthorised firmware, refer to ID.AM-02.4</li></ul></li><li>Include OT-Specific Considerations Detection methods in OTenvironments should account forsafety, availability, andvendor-specific constraints when identifying unauthorised components.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to proactively identify unauthorised hardware and firmware components within ICT and OT environments, thereby enabling timely response and reducing the risk of compromise or operational disruption. To achieve this goal: • Automate Where Feasible Detection mechanisms should be automated where safe and technically possible, especially in complex or high-risk environments. • Continuously Monitor Networks Networks should be continuously monitored to detect new or unauthorised hardware and firmware com- ponents. Detected changes should trigger automatic updates to the asset inventory. • Establish a Response Process A defined process should exist to regularly review and address unauthorised components. o For unauthorised hardware, refer to ID.AM-01.3 o For unauthorised firmware, refer to ID.AM-02.4 • Include OT-Specific Considerations Detection methods in OTenvironments should account forsafety, availability, andvendor-specific constraints when identifying unauthorised components. |
|
A general note, for any purpose. |
The goal of this control is to proactively identify unauthorised hardware and firmware components within ICT and OT environments, thereby enabling timely response and reducing the risk of compromise or operational disruption. To achieve this goal: - Automate Where Feasible Detection mechanisms should be automated where safe and technically possible, especially in complex or high-risk environments. - Continuously Monitor Networks Networks should be continuously monitored to detect new or unauthorised hardware and firmware com- ponents. Detected changes should trigger automatic updates to the asset inventory. - Establish a Response Process A defined process should exist to regularly review and address unauthorised components. - For unauthorised hardware, refer to ID.AM-01.3 - For unauthorised firmware, refer to ID.AM-02.4 - Include OT-Specific Considerations Detection methods in OTenvironments should account forsafety, availability, andvendor-specific constraints when identifying unauthorised components. |
|
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-01.4 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Unauthorised hardware detection mechanisms |
|
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. |
Mechanisms for detecting the presence of unauthorised hardware and firmware components within the organisation’s ICT/OT environment shall be identified. |
|
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