Concept skos:Concept Code ID.AM-08.10

The organisation shall verify security controls following maintenance or repairs/ patching, and take action as appropriate.

Also known as

skos:altLabel

Post-maintenance security verification

Note

skos:note

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.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_AM_08_10
All data (21 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.

ID.AM-08.10: The organisation shall verify security controls following maintenance or repairs/ patching, and take action as appropriate.

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

ID.AM-08.10

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p61

has broader

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

http://cyfun.data.gift/data/subcategory_ID.AM-08

note

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.

note

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.

note

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>

note

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.

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.

ID.AM-08.10

alternative label

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

Post-maintenance security verification

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 shall verify security controls following maintenance or repairs/ patching, and take action as appropriate.

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_KeyMeasures

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

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

1

triple count

The number of triples associated with the subject.

19

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 21 of 21

References

Inverse links to the subject.