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.5: The organisation shall only allow the use of removable media when absolutely necessary and shall put technical measures in place to block automatic execution of files from these devices. |
|
PR.DS-01.5 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p80 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p111 |
|
|
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 minimise the attack surface in operational and IT environments by strictly limiting the use of removable media and preventing automatic execution of potentially harmful files. To reduce the risk of malware infections and data leaks from removable media (e.g. USB sticks, external drives), the organisation should: - Allow Use Only When Necessary - The organisation should state in its policy that removable media should only be used when no safer alter- native is available (e.g., secure file transfer). - Technical tools should be used to limit access to USB ports or require approval before use. - Disable Autorun and Auto-Execution - All systems should be configured to disable autorun and autoplay features so that files on removable media do not run automatically. - This should help prevent malware from executing without user action. - Use Security Tools to Control Access - The organisation should use endpoint protection tools to: - Block or limit USB access. - Allow only approved devices. - Require administrator approval for new devices. - Monitor and Review Usage - The organisation should monitor removable media use by logging device connections through endpoint protection tools or operating system logs. In OT environments, manual logging or controlled access pro- cedures should be used. Logs should be reviewed regularly to detect unauthorised activity. - Example:Afinance team should use encrypted, company-approved USB drives to transfersensitive reports. These drives should be scanned before use, autorun should be disabled on all systems, and access should be logged and reviewed. Clarification of the difference with PR.DS-01.4 - PR.DS-01.4 focuses on setting rules and procedures for how removable media should be used (e.g., who can use them, encryption, physical protection). - PR.DS-01.5 focuses on the technical enforcement of those rules — how systems should be configured to reduce risk. |
|
A general note, for any purpose. |
The goal of this control is to minimise the attack surface in operational and IT environments by strictly limiting the use of removable media and preventing automatic execution of potentially harmful files. To reduce the risk of malware infections and data leaks from removable media (e.g. USB sticks, external drives), the organisation should: • Allow Use Only When Necessary o The organisation should state in its policy that removable media should only be used when no safer alter- native is available (e.g., secure file transfer). o Technical tools should be used to limit access to USB ports or require approval before use. • Disable Autorun and Auto-Execution o All systems should be configured to disable autorun and autoplay features so that files on removable media do not run automatically. o This should help prevent malware from executing without user action. • Use Security Tools to Control Access o The organisation should use endpoint protection tools to: - Block or limit USB access. - Allow only approved devices. - Require administrator approval for new devices. • Monitor and Review Usage o The organisation should monitor removable media use by logging device connections through endpoint protection tools or operating system logs. In OT environments, manual logging or controlled access pro- cedures should be used. Logs should be reviewed regularly to detect unauthorised activity. • Example:Afinance team should use encrypted, company-approved USB drives to transfersensitive reports. These drives should be scanned before use, autorun should be disabled on all systems, and access should be logged and reviewed. Clarification of the difference with PR.DS-01.4 • PR.DS-01.4 focuses on setting rules and procedures for how removable media should be used (e.g., who can use them, encryption, physical protection). • PR.DS-01.5 focuses on the technical enforcement of those rules — how systems should be configured to reduce risk. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to minimise the attack surface in operational and IT environments by strictly limiting the use of removable media and preventing automatic execution of potentially harmful files. To reduce the risk of malware infections and data leaks from removable media (e.g. USB sticks, external drives), the organisation should:</p><ul><li>Allow Use Only When Necessary<ul><li>The organisation should state in its policy that removable media should only be used when no safer alter- native is available (e.g., secure file transfer).</li><li>Technical tools should be used to limit access to USB ports or require approval before use.</li></ul></li><li>Disable Autorun and Auto-Execution<ul><li>All systems should be configured to disable autorun and autoplay features so that files on removable media do not run automatically.</li><li>This should help prevent malware from executing without user action.</li></ul></li><li>Use Security Tools to Control Access<ul><li>The organisation should use endpoint protection tools to:<ul><li>Block or limit USB access.</li><li>Allow only approved devices.</li><li>Require administrator approval for new devices.</li></ul></li></ul></li><li>Monitor and Review Usage<ul><li>The organisation should monitor removable media use by logging device connections through endpoint protection tools or operating system logs. In OT environments, manual logging or controlled access pro- cedures should be used. Logs should be reviewed regularly to detect unauthorised activity.</li></ul></li><li>Example:Afinance team should use encrypted, company-approved USB drives to transfersensitive reports. These drives should be scanned before use, autorun should be disabled on all systems, and access should be logged and reviewed. Clarification of the difference with PR.DS-01.4</li><li>PR.DS-01.4 focuses on setting rules and procedures for how removable media should be used (e.g., who can use them, encryption, physical protection).</li><li>PR.DS-01.5 focuses on the technical enforcement of those rules — how systems should be configured to reduce risk.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to minimise the attack surface in operational and IT environments by strictly limiting the use of removable media and preventing automatic execution of potentially harmful files. To reduce the risk of malware infections and data leaks from removable media (e.g. USB sticks, external drives), the organisation should: - Allow Use Only When Necessary - The organisation should state in its policy that removable media should only be used when no safer alter- native is available (e.g., secure file transfer). - Technical tools should be used to limit access to USB ports or require approval before use. - Disable Autorun and Auto-Execution - All systems should be configured to disable autorun and autoplay features so that files on removable media do not run automatically. - This should help prevent malware from executing without user action. - Use Security Tools to Control Access - The organisation should use endpoint protection tools to: - Block or limit USB access. - Allow only approved devices. - Require administrator approval for new devices. - Monitor and Review Usage - The organisation should monitor removable media use by logging device connections through endpoint protection tools or operating system logs. In OT environments, manual logging or controlled access pro- cedures should be used. Logs should be reviewed regularly to detect unauthorised activity. - Example:Afinance team should use encrypted, company-approved USB drives to transfersensitive reports. These drives should be scanned before use, autorun should be disabled on all systems, and access should be logged and reviewed. Clarification of the difference with PR.DS-01.4 - PR.DS-01.4 focuses on setting rules and procedures for how removable media should be used (e.g., who can use them, encryption, physical protection). - PR.DS-01.5 focuses on the technical enforcement of those rules — how systems should be configured to reduce risk. |
|
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.5 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Removable media restriction |
|
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 only allow the use of removable media when absolutely necessary and shall put technical measures in place to block automatic execution of files from these devices. |
|
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