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-08.10: The organisation shall verify security controls following maintenance or repairs/ patching, and take action as appropriate. |
|
ID.AM-08.10 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p61 |
|
|
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 security controls remain effective after maintenance, repairs, or patch- ing activities. In OT environments, even small configuration changes can have significant safety or operational consequences, making post-maintenance verification critical. To achieve this goal, the organisation should: - Verify Security Controls: After maintenance, systems should be assessed to confirm that no changes have weakened security. This includes checking configurations, access permissions, and other security-relevant settings. - Update Records: Any changes made during maintenance should be documented, including updates to security controls or the implementation of new measures. - Report Issues: If security concerns are identified during verification, findings should be communicated to relevant stakeholders, to ensure awareness and coordinated response. - Take Corrective Action: If controls are found to be inadequate or compromised, corrective actions should be taken. This may include reconfiguring settings, applying additional patches, or strengthening existing controls. - Ensure Conformance and Compliance: All verification and corrective actions should conform to internal procedures and comply with applicable laws, regulations, and industry standards. |
|
A general note, for any purpose. |
The goal of this control is to ensure that security controls remain effective after maintenance, repairs, or patch- ing activities. In OT environments, even small configuration changes can have significant safety or operational consequences, making post-maintenance verification critical. To achieve this goal, the organisation should: • Verify Security Controls: After maintenance, systems should be assessed to confirm that no changes have weakened security. This includes checking configurations, access permissions, and other security-relevant settings. • Update Records: Any changes made during maintenance should be documented, including updates to security controls or the implementation of new measures. • Report Issues: If security concerns are identified during verification, findings should be communicated to relevant stakeholders, to ensure awareness and coordinated response. • Take Corrective Action: If controls are found to be inadequate or compromised, corrective actions should be taken. This may include reconfiguring settings, applying additional patches, or strengthening existing controls. • Ensure Conformance and Compliance: All verification and corrective actions should conform to internal procedures and comply with applicable laws, regulations, and industry standards. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that security controls remain effective after maintenance, repairs, or patch- ing activities. In OT environments, even small configuration changes can have significant safety or operational consequences, making post-maintenance verification critical. To achieve this goal, the organisation should:</p><ul><li>Verify Security Controls: After maintenance, systems should be assessed to confirm that no changes have weakened security. This includes checking configurations, access permissions, and other security-relevant settings.</li><li>Update Records: Any changes made during maintenance should be documented, including updates to security controls or the implementation of new measures.</li><li>Report Issues: If security concerns are identified during verification, findings should be communicated to relevant stakeholders, to ensure awareness and coordinated response.</li><li>Take Corrective Action: If controls are found to be inadequate or compromised, corrective actions should be taken. This may include reconfiguring settings, applying additional patches, or strengthening existing controls.</li><li>Ensure Conformance and Compliance: All verification and corrective actions should conform to internal procedures and comply with applicable laws, regulations, and industry standards.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that security controls remain effective after maintenance, repairs, or patch- ing activities. In OT environments, even small configuration changes can have significant safety or operational consequences, making post-maintenance verification critical. To achieve this goal, the organisation should: - Verify Security Controls: After maintenance, systems should be assessed to confirm that no changes have weakened security. This includes checking configurations, access permissions, and other security-relevant settings. - Update Records: Any changes made during maintenance should be documented, including updates to security controls or the implementation of new measures. - Report Issues: If security concerns are identified during verification, findings should be communicated to relevant stakeholders, to ensure awareness and coordinated response. - Take Corrective Action: If controls are found to be inadequate or compromised, corrective actions should be taken. This may include reconfiguring settings, applying additional patches, or strengthening existing controls. - Ensure Conformance and Compliance: All verification and corrective actions should conform to internal procedures and comply with applicable laws, regulations, and industry standards. |
|
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-08.10 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Post-maintenance security verification |
|
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 shall verify security controls following maintenance or repairs/ patching, and take action as appropriate. |
|
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. |
|
|
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. |
|
|
1 |
|
|
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