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.1: Logs shall be maintained, documented, and monitored. |
|
PR.PS-04.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p86 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p35 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p124 |
|
|
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 logs are consistentlymaintained, documented, and monitored to support visibility, accountability, and early detection of anomalies or threats. To support this goal, the organisation should: • Enable Logging Across Systems All operating systems, applications, services (including cloud-based), and securitytools (e.g. firewalls, antivirus) should be configured to generate log records. • Include a Variety of Log Types Logs should include, where applicable: audit logs, event logs, application logs, securitylogs, system logs, and maintenance logs. • Protect Log Data Logs should be protected from unauthorised access using encryption and access controls. • Back Up and Retain Logs Log backups should be performed regularly and retained for a predefined period, based on business needs or regulatory requirements. • Review Logs forAnomalies Logs should be reviewed to detect unusual patterns or behaviours, such as repeated malware detections or excessive access to non-business websites. • Define Retention Periods Retention periods for logs should be clearly defined. Sector-specific requirements should be taken into account. • Support Monitoring and Accountability Monitoring should be in place to provide visibility into system activity and support effective auditing and incident response. • Include OT Systems Logging practices should extend to OT environments, including industrial control systems, where logs can help detect operational anomalies or unauthorised access attempts. |
|
A general note, for any purpose. |
The goal of this control is to ensure that logs are consistentlymaintained, documented, and monitored to support visibility, accountability, and early detection of anomalies or threats. To support this goal, the organisation should: - Enable Logging Across Systems All operating systems, applications, services (including cloud-based), and securitytools (e.g. firewalls, antivirus) should be configured to generate log records. - Include a Variety of Log Types Logs should include, where applicable: audit logs, event logs, application logs, securitylogs, system logs, and maintenance logs. - Protect Log Data Logs should be protected from unauthorised access using encryption and access controls. - Back Up and Retain Logs Log backups should be performed regularly and retained for a predefined period, based on business needs or regulatory requirements. - Review Logs forAnomalies Logs should be reviewed to detect unusual patterns or behaviours, such as repeated malware detections or excessive access to non-business websites. - Define Retention Periods Retention periods for logs should be clearly defined. Sector-specific requirements should be taken into account. - Support Monitoring and Accountability Monitoring should be in place to provide visibility into system activity and support effective auditing and incident response. - Include OT Systems Logging practices should extend to OT environments, including industrial control systems, where logs can help detect operational anomalies or unauthorised access attempts. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that logs are consistentlymaintained, documented, and monitored to support visibility, accountability, and early detection of anomalies or threats. To support this goal, the organisation should:</p><ul><li>Enable Logging Across Systems All operating systems, applications, services (including cloud-based), and securitytools (e.g. firewalls, antivirus) should be configured to generate log records.</li><li>Include a Variety of Log Types Logs should include, where applicable: audit logs, event logs, application logs, securitylogs, system logs, and maintenance logs.</li><li>Protect Log Data Logs should be protected from unauthorised access using encryption and access controls.</li><li>Back Up and Retain Logs Log backups should be performed regularly and retained for a predefined period, based on business needs or regulatory requirements.</li><li>Review Logs forAnomalies Logs should be reviewed to detect unusual patterns or behaviours, such as repeated malware detections or excessive access to non-business websites.</li><li>Define Retention Periods Retention periods for logs should be clearly defined. Sector-specific requirements should be taken into account.</li><li>Support Monitoring and Accountability Monitoring should be in place to provide visibility into system activity and support effective auditing and incident response.</li><li>Include OT Systems Logging practices should extend to OT environments, including industrial control systems, where logs can help detect operational anomalies or unauthorised access attempts.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that logs are consistentlymaintained, documented, and monitored to support visibility, accountability, and early detection of anomalies or threats. To support this goal, the organisation should: - Enable Logging Across Systems All operating systems, applications, services (including cloud-based), and securitytools (e.g. firewalls, antivirus) should be configured to generate log records. - Include a Variety of Log Types Logs should include, where applicable: audit logs, event logs, application logs, securitylogs, system logs, and maintenance logs. - Protect Log Data Logs should be protected from unauthorised access using encryption and access controls. - Back Up and Retain Logs Log backups should be performed regularly and retained for a predefined period, based on business needs or regulatory requirements. - Review Logs forAnomalies Logs should be reviewed to detect unusual patterns or behaviours, such as repeated malware detections or excessive access to non-business websites. - Define Retention Periods Retention periods for logs should be clearly defined. Sector-specific requirements should be taken into account. - Support Monitoring and Accountability Monitoring should be in place to provide visibility into system activity and support effective auditing and incident response. - Include OT Systems Logging practices should extend to OT environments, including industrial control systems, where logs can help detect operational anomalies or unauthorised access attempts. |
|
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.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Log maintenance and monitoring |
|
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. |
Logs shall be maintained, documented, and monitored. |
|
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. |
|
|
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. |
|
|
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. |
|
|
1 |
|
|
The number of triples associated with the subject. |
23 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 25 of 25
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1