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. |
PR.DS-01.1: The organisation shall implement software, firmware, and information integrity checks to detect unauthorised changes to its critical system components during storage, transport, start-up and when determined necessary. |
|
PR.DS-01.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p78 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p109 |
|
|
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 the integrity and trustworthiness of critical system components, such as software, firmware, and configuration data, by detecting unauthorised modifications that could compromise operational safety, reliability, or security across all lifecycle stages, including storage, transport, and start-up. To effectively protect the integrity of data-at-rest, the organisation should implement a layered set of controls designed to detect and prevent unauthorised changes to stored data, software, and system components. The following practices should be considered: - Apply Cryptographic Integrity Mechanisms - Usecryptographichashes(e.g.,SHA-256),digitalsignatures,orothercryptographicmechanisms(e.g.message authentication codes (MACs)) to verify the integrity of stored data and critical files. - Integrity values should be generated at the time of storage and verified before access or execution. - Implement Automated Integrity Monitoring - Deploy file integrity monitoring (FIM) tools to continuously track changes to critical system files, configura- tions, and applications. - Alerts should be generated foranyunauthorised orunexpected modifications, and logs should be retained for audit and investigation. - Validate Software and Firmware Integrity - Ensure that software and firmware stored on systems are validated using signature verification or secure boot mechanisms before execution. - Integrity validation should be part of the system start-up process and enforced through technical controls. - Enforce Change Control and Access Restrictions - Limitwrite access to critical data and system components through role-based access controls (RBAC) and least privilege principles. - All changes to data-at-rest should be subject to formal change management procedures and logged for traceability. - Protect Integrity of Backups - Backups should include integrity verification mechanisms (e.g. checksums or digital signatures) to ensure they have not been tampered with. - Regular test restorations should be performed to confirm the integrity and usability of backup data. |
|
A general note, for any purpose. |
The goal of this control is to ensure the integrity and trustworthiness of critical system components, such as software, firmware, and configuration data, by detecting unauthorised modifications that could compromise operational safety, reliability, or security across all lifecycle stages, including storage, transport, and start-up. To effectively protect the integrity of data-at-rest, the organisation should implement a layered set of controls designed to detect and prevent unauthorised changes to stored data, software, and system components. The following practices should be considered: • Apply Cryptographic Integrity Mechanisms o Usecryptographichashes(e.g.,SHA-256),digitalsignatures,orothercryptographicmechanisms(e.g.message authentication codes (MACs)) to verify the integrity of stored data and critical files. o Integrity values should be generated at the time of storage and verified before access or execution. • Implement Automated Integrity Monitoring o Deploy file integrity monitoring (FIM) tools to continuously track changes to critical system files, configura- tions, and applications. o Alerts should be generated foranyunauthorised orunexpected modifications, and logs should be retained for audit and investigation. • Validate Software and Firmware Integrity o Ensure that software and firmware stored on systems are validated using signature verification or secure boot mechanisms before execution. o Integrity validation should be part of the system start-up process and enforced through technical controls. • Enforce Change Control and Access Restrictions o Limitwrite access to critical data and system components through role-based access controls (RBAC) and least privilege principles. o All changes to data-at-rest should be subject to formal change management procedures and logged for traceability. • Protect Integrity of Backups o Backups should include integrity verification mechanisms (e.g. checksums or digital signatures) to ensure they have not been tampered with. o Regular test restorations should be performed to confirm the integrity and usability of backup data. |
|
A general note, for any purpose. |
The goal of this control is to ensure the integrity and trustworthiness of critical system components, such as software, firmware, and configuration data, by detecting unauthorised modifications that could compromise operational safety, reliability, or security across all lifecycle stages, including storage, transport, and start-up. To effectively protect the integrity of data-at-rest, the organisation should implement a layered set of controls designed to detect and prevent unauthorised changes to stored data, software, and system components. The following practices should be considered: - Apply Cryptographic Integrity Mechanisms - Usecryptographichashes(e.g.,SHA-256),digitalsignatures,orothercryptographicmechanisms(e.g.message authentication codes (MACs)) to verify the integrity of stored data and critical files. - Integrity values should be generated at the time of storage and verified before access or execution. - Implement Automated Integrity Monitoring - Deploy file integrity monitoring (FIM) tools to continuously track changes to critical system files, configura- tions, and applications. - Alerts should be generated foranyunauthorised orunexpected modifications, and logs should be retained for audit and investigation. - Validate Software and Firmware Integrity - Ensure that software and firmware stored on systems are validated using signature verification or secure boot mechanisms before execution. - Integrity validation should be part of the system start-up process and enforced through technical controls. - Enforce Change Control and Access Restrictions - Limitwrite access to critical data and system components through role-based access controls (RBAC) and least privilege principles. - All changes to data-at-rest should be subject to formal change management procedures and logged for traceability. - Protect Integrity of Backups - Backups should include integrity verification mechanisms (e.g. checksums or digital signatures) to ensure they have not been tampered with. - Regular test restorations should be performed to confirm the integrity and usability of backup data. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure the integrity and trustworthiness of critical system components, such as software, firmware, and configuration data, by detecting unauthorised modifications that could compromise operational safety, reliability, or security across all lifecycle stages, including storage, transport, and start-up. To effectively protect the integrity of data-at-rest, the organisation should implement a layered set of controls designed to detect and prevent unauthorised changes to stored data, software, and system components. The following practices should be considered:</p><ul><li>Apply Cryptographic Integrity Mechanisms<ul><li>Usecryptographichashes(e.g.,SHA-256),digitalsignatures,orothercryptographicmechanisms(e.g.message authentication codes (MACs)) to verify the integrity of stored data and critical files.</li><li>Integrity values should be generated at the time of storage and verified before access or execution.</li></ul></li><li>Implement Automated Integrity Monitoring<ul><li>Deploy file integrity monitoring (FIM) tools to continuously track changes to critical system files, configura- tions, and applications.</li><li>Alerts should be generated foranyunauthorised orunexpected modifications, and logs should be retained for audit and investigation.</li></ul></li><li>Validate Software and Firmware Integrity<ul><li>Ensure that software and firmware stored on systems are validated using signature verification or secure boot mechanisms before execution.</li><li>Integrity validation should be part of the system start-up process and enforced through technical controls.</li></ul></li><li>Enforce Change Control and Access Restrictions<ul><li>Limitwrite access to critical data and system components through role-based access controls (RBAC) and least privilege principles.</li><li>All changes to data-at-rest should be subject to formal change management procedures and logged for traceability.</li></ul></li><li>Protect Integrity of Backups<ul><li>Backups should include integrity verification mechanisms (e.g. checksums or digital signatures) to ensure they have not been tampered with.</li><li>Regular test restorations should be performed to confirm the integrity and usability of backup data.</li></ul></li></ul></div> |
|
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. |
PR.DS-01.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Software and firmware integrity checks |
|
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 implement software, firmware, and information integrity checks to detect unauthorised changes to its critical system components during storage, transport, start-up and when determined necessary. |
|
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