Concept skos:Concept Code ID.AM-08.2

Patches and security updates for Operating Systems and critical system compo- nents shall be installed.

Also known as

skos:altLabel

Patch and security update installation

Note

skos:note

The goal of this control is to ensure that operating systems and critical system components are kept secure and up-to-date by installing patches and security updates in a timely and controlled manner. To achieve this goal, the following should be considered:

  • Timely Updates Patches and security updates should be installed as soon as possible, especially for critical systems.
  • Industrial Systems Firmware updates for industrial assets (e.g. PLCs, HMIs) should be included in the patching process.
  • Centralised Management A Centralised patch management system should be used to automate and streamline patch deployment.
  • Testing Before Deployment
    • Patches should be tested in a controlled environment to avoid disruptions.
    • A test environment should closely mirror the production setup.
  • Phased Rollouts
    • Where appropriate, test groups, pilot users, and phased rollouts should be used.
    • A rollback procedure should be in place in case issues arise.
  • Trusted Sources Only
    • Patches should only be downloaded from verified, trusted sources.
    • Links in emails or advertisements should be avoided.
  • Minimal Software Footprint Only essential applications should be installed. These should be regularly patched and updated.
  • Safe Update Practices
    • Automatic updates should be enabled when connected to trusted networks.
    • Updates should not be performed over untrusted networks (e.g. public Wi-Fi).
  • Supported Software Only
    • Only vendor-supported and up-to-date software versions should be used.
    • End-of-life (EOL) software should be decommissioned as soon as possible.
  • Regular Checks If automatic updates are not possible, a regular schedule (e.g. monthly) should be set to manually check for and install updates.
  • Update Monitoring Tools Tools that notify about available updates should be configured to monitor all installed applications.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_AM_08_2
All data (25 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.2: Patches and security updates for Operating Systems and critical system compo- nents shall be installed.

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

ID.AM-08.2

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p19

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p56

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p40

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.

<div><p>The goal of this control is to ensure that operating systems and critical system components are kept secure and up-to-date by installing patches and security updates in a timely and controlled manner. To achieve this goal, the following should be considered:</p><ul><li>Timely Updates Patches and security updates should be installed as soon as possible, especially for critical systems.</li><li>Industrial Systems Firmware updates for industrial assets (e.g. PLCs, HMIs) should be included in the patching process.</li><li>Centralised Management A Centralised patch management system should be used to automate and streamline patch deployment.</li><li>Testing Before Deployment<ul><li>Patches should be tested in a controlled environment to avoid disruptions.</li><li>A test environment should closely mirror the production setup.</li></ul></li><li>Phased Rollouts<ul><li>Where appropriate, test groups, pilot users, and phased rollouts should be used.</li><li>A rollback procedure should be in place in case issues arise.</li></ul></li><li>Trusted Sources Only<ul><li>Patches should only be downloaded from verified, trusted sources.</li><li>Links in emails or advertisements should be avoided.</li></ul></li><li>Minimal Software Footprint Only essential applications should be installed. These should be regularly patched and updated.</li><li>Safe Update Practices<ul><li>Automatic updates should be enabled when connected to trusted networks.</li><li>Updates should not be performed over untrusted networks (e.g. public Wi-Fi).</li></ul></li><li>Supported Software Only<ul><li>Only vendor-supported and up-to-date software versions should be used.</li><li>End-of-life (EOL) software should be decommissioned as soon as possible.</li></ul></li><li>Regular Checks If automatic updates are not possible, a regular schedule (e.g. monthly) should be set to manually check for and install updates.</li><li>Update Monitoring Tools Tools that notify about available updates should be configured to monitor all installed applications.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that operating systems and critical system components are kept secure and up-to-date by installing patches and security updates in a timely and controlled manner. To achieve this goal, the following should be considered: - Timely Updates Patches and security updates should be installed as soon as possible, especially for critical systems. - Industrial Systems Firmware updates for industrial assets (e.g. PLCs, HMIs) should be included in the patching process. - Centralised Management A Centralised patch management system should be used to automate and streamline patch deployment. - Testing Before Deployment - Patches should be tested in a controlled environment to avoid disruptions. - A test environment should closely mirror the production setup. - Phased Rollouts - Where appropriate, test groups, pilot users, and phased rollouts should be used. - A rollback procedure should be in place in case issues arise. - Trusted Sources Only - Patches should only be downloaded from verified, trusted sources. - Links in emails or advertisements should be avoided. - Minimal Software Footprint Only essential applications should be installed. These should be regularly patched and updated. - Safe Update Practices - Automatic updates should be enabled when connected to trusted networks. - Updates should not be performed over untrusted networks (e.g. public Wi-Fi). - Supported Software Only - Only vendor-supported and up-to-date software versions should be used. - End-of-life (EOL) software should be decommissioned as soon as possible. - Regular Checks If automatic updates are not possible, a regular schedule (e.g. monthly) should be set to manually check for and install updates. - Update Monitoring Tools Tools that notify about available updates should be configured to monitor all installed applications.

note

A general note, for any purpose.

The goal of this control is to ensure that operating systems and critical system components are kept secure and up-to-date by installing patches and security updates in a timely and controlled manner. To achieve this goal, the following should be considered: • Timely Updates Patches and security updates should be installed as soon as possible, especially for critical systems. • Industrial Systems Firmware updates for industrial assets (e.g. PLCs, HMIs) should be included in the patching process. • Centralised Management A Centralised patch management system should be used to automate and streamline patch deployment. • Testing Before Deployment o Patches should be tested in a controlled environment to avoid disruptions. o A test environment should closely mirror the production setup. • Phased Rollouts o Where appropriate, test groups, pilot users, and phased rollouts should be used. o A rollback procedure should be in place in case issues arise. • Trusted Sources Only o Patches should only be downloaded from verified, trusted sources. o Links in emails or advertisements should be avoided. • Minimal Software Footprint Only essential applications should be installed. These should be regularly patched and updated. • Safe Update Practices o Automatic updates should be enabled when connected to trusted networks. o Updates should not be performed over untrusted networks (e.g. public Wi-Fi). • Supported Software Only o Only vendor-supported and up-to-date software versions should be used. o End-of-life (EOL) software should be decommissioned as soon as possible. • Regular Checks If automatic updates are not possible, a regular schedule (e.g. monthly) should be set to manually check for and install updates. • Update Monitoring Tools Tools that notify about available updates should be configured to monitor all installed applications.

note

A general note, for any purpose.

The goal of this control is to ensure that operating systems and critical system components are kept secure and up-to-date by installing patches and security updates in a timely and controlled manner. To achieve this goal, the following should be considered: - Timely Updates Patches and security updates should be installed as soon as possible, especially for critical systems. - Industrial Systems Firmware updates for industrial assets (e.g. PLCs, HMIs) should be included in the patching process. - Centralised Management A Centralised patch management system should be used to automate and streamline patch deployment. - Testing Before Deployment - Patches should be tested in a controlled environment to avoid disruptions. - A test environment should closely mirror the production setup. - Phased Rollouts - Where appropriate, test groups, pilot users, and phased rollouts should be used. - A rollback procedure should be in place in case issues arise. - Trusted Sources Only - Patches should only be downloaded from verified, trusted sources. - Links in emails or advertisements should be avoided. - Minimal Software Footprint Only essential applications should be installed. These should be regularly patched and updated. - Safe Update Practices - Automatic updates should be enabled when connected to trusted networks. - Updates should not be performed over untrusted networks (e.g. public Wi-Fi). - Supported Software Only - Only vendor-supported and up-to-date software versions should be used. - End-of-life (EOL) software should be decommissioned as soon as possible. - Regular Checks If automatic updates are not possible, a regular schedule (e.g. monthly) should be set to manually check for and install updates. - Update Monitoring Tools Tools that notify about available updates should be configured to monitor all installed applications.

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.2

alternative label

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

Patch and security update installation

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.

Patches and security updates for Operating Systems and critical system compo- nents shall be installed.

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_delta_BASIC

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_BASIC

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_IMPORTANT

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_BASIC

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

1

triple count

The number of triples associated with the subject.

23

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 25 of 25

References

Inverse links to the subject.