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. |
DE.CM-06.1: External service provider activities and services shall be secured and monitored to find potentially adverse events. |
|
DE.CM-06.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p151 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p101 |
|
|
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 activities performed by external service providers, whether remote or onsite, are securely managed and continuously monitored. This helps detect any unusual or harmful actions that could affect the organisation’s systems, data, or services. The achieve this goal, the following should be considered: • External providers mayinclude contractors, cloud servicevendors, ITsupport teams, software developers, and other third parties involved in system maintenance, development, or security. • Monitoring should focus on: o Access and login activity, including how and when external users connect to systems. o Data transfers and network traffic, to detect unusual or unauthorised movement of information. o System changes, such as software updates or configuration adjustments made by external parties. • All remote and onsite activities by external providers should be logged and reviewed to identify unauthorised actions or risky behaviour. • Cloud services and internet providers should be monitored for unexpected behaviour or performance issues that could indicate a security problem. • A centralised logging system should be used to collect and analyse data from all external services. • Anysecurityincidents involving external providers — such as malware infections, phishing attempts, orunau- thorised access — should be detected early, reported quickly, and addressed effectively. |
|
A general note, for any purpose. |
The goal of this control is to ensure that activities performed by external service providers, whether remote or onsite, are securely managed and continuously monitored. This helps detect any unusual or harmful actions that could affect the organisation’s systems, data, or services. The achieve this goal, the following should be considered: - External providers mayinclude contractors, cloud servicevendors, ITsupport teams, software developers, and other third parties involved in system maintenance, development, or security. - Monitoring should focus on: - Access and login activity, including how and when external users connect to systems. - Data transfers and network traffic, to detect unusual or unauthorised movement of information. - System changes, such as software updates or configuration adjustments made by external parties. - All remote and onsite activities by external providers should be logged and reviewed to identify unauthorised actions or risky behaviour. - Cloud services and internet providers should be monitored for unexpected behaviour or performance issues that could indicate a security problem. - A centralised logging system should be used to collect and analyse data from all external services. - Anysecurityincidents involving external providers — such as malware infections, phishing attempts, orunau- thorised access — should be detected early, reported quickly, and addressed effectively. |
|
A general note, for any purpose. |
The goal of this control is to ensure that activities performed by external service providers, whether remote or onsite, are securely managed and continuously monitored. This helps detect any unusual or harmful actions that could affect the organisation’s systems, data, or services. The achieve this goal, the following should be considered: - External providers mayinclude contractors, cloud servicevendors, ITsupport teams, software developers, and other third parties involved in system maintenance, development, or security. - Monitoring should focus on: - Access and login activity, including how and when external users connect to systems. - Data transfers and network traffic, to detect unusual or unauthorised movement of information. - System changes, such as software updates or configuration adjustments made by external parties. - All remote and onsite activities by external providers should be logged and reviewed to identify unauthorised actions or risky behaviour. - Cloud services and internet providers should be monitored for unexpected behaviour or performance issues that could indicate a security problem. - A centralised logging system should be used to collect and analyse data from all external services. - Anysecurityincidents involving external providers — such as malware infections, phishing attempts, orunau- thorised access — should be detected early, reported quickly, and addressed effectively. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that activities performed by external service providers, whether remote or onsite, are securely managed and continuously monitored. This helps detect any unusual or harmful actions that could affect the organisation’s systems, data, or services. The achieve this goal, the following should be considered:</p><ul><li>External providers mayinclude contractors, cloud servicevendors, ITsupport teams, software developers, and other third parties involved in system maintenance, development, or security.</li><li>Monitoring should focus on:<ul><li>Access and login activity, including how and when external users connect to systems.</li><li>Data transfers and network traffic, to detect unusual or unauthorised movement of information.</li><li>System changes, such as software updates or configuration adjustments made by external parties.</li></ul></li><li>All remote and onsite activities by external providers should be logged and reviewed to identify unauthorised actions or risky behaviour.</li><li>Cloud services and internet providers should be monitored for unexpected behaviour or performance issues that could indicate a security problem.</li><li>A centralised logging system should be used to collect and analyse data from all external services.</li><li>Anysecurityincidents involving external providers — such as malware infections, phishing attempts, orunau- thorised access — should be detected early, reported quickly, and addressed effectively.</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. |
DE.CM-06.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
External service provider 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. |
External service provider activities and services shall be secured and monitored to find potentially adverse events. |
|
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