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-01.4: The organisation shall implement technical safeguards to enforce a policy of ‘deny-all’ and ‘permit-by-exception’ so that only authorised software programmes are executed. |
|
PR.PS-01.4 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p122 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that only explicitly authorised software is allowed to run, reducing the risk of unauthorised or malicious programs affecting critical systems. To achieve this goal, the organisation should consider the following:</p><ul><li>Implement application whitelisting to allow only approved software to execute.</li><li>Use group policies to enforce application control rules across systems.</li><li>Apply Software Restriction Policies (SRP) or similar mechanisms to block unauthorised software based on file path, hash, or digital signature.</li><li>Enforce role-based access control (RBAC) to ensure only authorised users can run specific applications.</li><li>Configure Java Security Manager to restrict which classes and methods can execute in Java-based envi- ronments.</li><li>Use configuration management tools to maintain consistent enforcement of authorised software across all systems.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that only explicitly authorised software is allowed to run, reducing the risk of unauthorised or malicious programs affecting critical systems. To achieve this goal, the organisation should consider the following: - Implement application whitelisting to allow only approved software to execute. - Use group policies to enforce application control rules across systems. - Apply Software Restriction Policies (SRP) or similar mechanisms to block unauthorised software based on file path, hash, or digital signature. - Enforce role-based access control (RBAC) to ensure only authorised users can run specific applications. - Configure Java Security Manager to restrict which classes and methods can execute in Java-based envi- ronments. - Use configuration management tools to maintain consistent enforcement of authorised software across all systems. |
|
A general note, for any purpose. |
The goal of this control is to ensure that only explicitly authorised software is allowed to run, reducing the risk of unauthorised or malicious programs affecting critical systems. To achieve this goal, the organisation should consider the following: - Implement application whitelisting to allow only approved software to execute. - Use group policies to enforce application control rules across systems. - Apply Software Restriction Policies (SRP) or similar mechanisms to block unauthorised software based on file path, hash, or digital signature. - Enforce role-based access control (RBAC) to ensure only authorised users can run specific applications. - Configure Java Security Manager to restrict which classes and methods can execute in Java-based envi- ronments. - Use configuration management tools to maintain consistent enforcement of authorised software across all systems. |
|
A general note, for any purpose. |
The goal of this control is to ensure that only explicitly authorised software is allowed to run, reducing the risk of unauthorised or malicious programs affecting critical systems. To achieve this goal, the organisation should consider the following: • Implement application whitelisting to allow only approved software to execute. • Use group policies to enforce application control rules across systems. • Apply Software Restriction Policies (SRP) or similar mechanisms to block unauthorised software based on file path, hash, or digital signature. • Enforce role-based access control (RBAC) to ensure only authorised users can run specific applications. • Configure Java Security Manager to restrict which classes and methods can execute in Java-based envi- ronments. • Use configuration management tools to maintain consistent enforcement of authorised software across all systems. |
|
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-01.4 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Software execution whitelisting |
|
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 implement technical safeguards to enforce a policy of ‘deny-all’ and ‘permit-by-exception’ so that only authorised software programmes are executed. |
|
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