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.5: The organisation shall ensure that authorised personnel can extend or enhance audit logging and monitoring capabilities when needed to support investigations or incident response. |
|
PR.PS-04.5 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p126 |
|
|
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 audit logging can be quickly adapted to provide deepervisibility during security incidents or investigations, without disrupting normal operations. To achieve this goal: - Audit logging systems should allow on-demand adjustments, such as increasing log detail, extending reten- tion, or expanding coverage. - Authorised personnel and conditions for enabling extended logging should be clearly defined. - Activation procedures should include approvals, documentation, and change tracking. - Logbook records should be reviewed regularly for accuracy and completeness across ICT and OT systems. - Policies should ensure extended logging is used only when justified and is properly recorded. - Technical capacity, escalation paths, and personnel availability should be pre-planned to support timely activation. |
|
A general note, for any purpose. |
The goal of this control is to ensure that audit logging can be quickly adapted to provide deepervisibility during security incidents or investigations, without disrupting normal operations. To achieve this goal: • Audit logging systems should allow on-demand adjustments, such as increasing log detail, extending reten- tion, or expanding coverage. • Authorised personnel and conditions for enabling extended logging should be clearly defined. • Activation procedures should include approvals, documentation, and change tracking. • Logbook records should be reviewed regularly for accuracy and completeness across ICT and OT systems. • Policies should ensure extended logging is used only when justified and is properly recorded. • Technical capacity, escalation paths, and personnel availability should be pre-planned to support timely activation. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that audit logging can be quickly adapted to provide deepervisibility during security incidents or investigations, without disrupting normal operations. To achieve this goal:</p><ul><li>Audit logging systems should allow on-demand adjustments, such as increasing log detail, extending reten- tion, or expanding coverage.</li><li>Authorised personnel and conditions for enabling extended logging should be clearly defined.</li><li>Activation procedures should include approvals, documentation, and change tracking.</li><li>Logbook records should be reviewed regularly for accuracy and completeness across ICT and OT systems.</li><li>Policies should ensure extended logging is used only when justified and is properly recorded.</li><li>Technical capacity, escalation paths, and personnel availability should be pre-planned to support timely activation.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that audit logging can be quickly adapted to provide deepervisibility during security incidents or investigations, without disrupting normal operations. To achieve this goal: - Audit logging systems should allow on-demand adjustments, such as increasing log detail, extending reten- tion, or expanding coverage. - Authorised personnel and conditions for enabling extended logging should be clearly defined. - Activation procedures should include approvals, documentation, and change tracking. - Logbook records should be reviewed regularly for accuracy and completeness across ICT and OT systems. - Policies should ensure extended logging is used only when justified and is properly recorded. - Technical capacity, escalation paths, and personnel availability should be pre-planned to support timely activation. |
|
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.5 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Enhanced audit logging capabilities |
|
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 authorised personnel can extend or enhance audit logging and monitoring capabilities when needed to support investigations or incident response. |
|
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