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.PS-04.4: The organisation shall ensure that audit processing failures on the organisation's systems generate alerts and trigger defined responses. |
|
PR.PS-04.4 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p125 |
|
|
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 any failure in audit logging, such as errors in log collection, processing, or storage, triggers alerts and predefined responses to maintain system integrity and traceability. To achieve this goal: - Audit failures should include software or hardware issues, broken logging mechanisms, or full storage. - Alerts should be automatically generated when such failures occur, and predefined actions should be trig- gered to address them. - Each audit log repository, whether on a server, firewall, or application, should be monitored individually and collectively. - System Logging Protocol (Syslog) servers or similar centralised logging solutions should be used to support reliable log collection and alerting. - Systems generating logs should be configured to capture detailed activity, access, and behaviour data to support zero-trust principles. - Audit logs should be continuously monitored to ensure availability, integrity, and sufficient storage capacity. |
|
A general note, for any purpose. |
The goal of this control is to ensure that any failure in audit logging, such as errors in log collection, processing, or storage, triggers alerts and predefined responses to maintain system integrity and traceability. To achieve this goal: • Audit failures should include software or hardware issues, broken logging mechanisms, or full storage. • Alerts should be automatically generated when such failures occur, and predefined actions should be trig- gered to address them. • Each audit log repository, whether on a server, firewall, or application, should be monitored individually and collectively. • System Logging Protocol (Syslog) servers or similar centralised logging solutions should be used to support reliable log collection and alerting. • Systems generating logs should be configured to capture detailed activity, access, and behaviour data to support zero-trust principles. • Audit logs should be continuously monitored to ensure availability, integrity, and sufficient storage capacity. |
|
A general note, for any purpose. |
The goal of this control is to ensure that any failure in audit logging, such as errors in log collection, processing, or storage, triggers alerts and predefined responses to maintain system integrity and traceability. To achieve this goal: - Audit failures should include software or hardware issues, broken logging mechanisms, or full storage. - Alerts should be automatically generated when such failures occur, and predefined actions should be trig- gered to address them. - Each audit log repository, whether on a server, firewall, or application, should be monitored individually and collectively. - System Logging Protocol (Syslog) servers or similar centralised logging solutions should be used to support reliable log collection and alerting. - Systems generating logs should be configured to capture detailed activity, access, and behaviour data to support zero-trust principles. - Audit logs should be continuously monitored to ensure availability, integrity, and sufficient storage capacity. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that any failure in audit logging, such as errors in log collection, processing, or storage, triggers alerts and predefined responses to maintain system integrity and traceability. To achieve this goal:</p><ul><li>Audit failures should include software or hardware issues, broken logging mechanisms, or full storage.</li><li>Alerts should be automatically generated when such failures occur, and predefined actions should be trig- gered to address them.</li><li>Each audit log repository, whether on a server, firewall, or application, should be monitored individually and collectively.</li><li>System Logging Protocol (Syslog) servers or similar centralised logging solutions should be used to support reliable log collection and alerting.</li><li>Systems generating logs should be configured to capture detailed activity, access, and behaviour data to support zero-trust principles.</li><li>Audit logs should be continuously monitored to ensure availability, integrity, and sufficient storage capacity.</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.PS-04.4 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Audit processing failure alerts |
|
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 ensure that audit processing failures on the organisation's systems generate alerts and trigger defined responses. |
|
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