Concept skos:Concept Code PR.AA-05.1

Access permissions, rights, and authorisations shall be defined, managed, enforced and reviewed.

Also known as

skos:altLabel

Access permissions management

Note

skos:note

The goal of this control is to ensure that access permissions, rights, and authorisations are clearly defined, properly managed, consistently enforced, and regularly reviewed to protect systems and data from unauthor- ised access. To achieve this goal, the following should be considered:

  • Access Definition and Management
    • Access lists for systems (e.g. files, servers, software, databases) should be created and reviewed regularly.
    • Reviews should be supported by tools such as Active Directory analysis.
    • Permission management procedures should be documented and updated as needed.
  • Access Review and Revocation
    • Logical and physical access rights should be reviewed periodicallyandwheneverroles change orindividuals leave the organisation.
    • Unnecessary privileges should be revoked immediately.
  • UserAccount Practices
    • Each user, including contractors, should have a separate account to ensure accountability.
    • Where technically feasible, appropriate authentication measures should be applied.
    • Guest accounts should be restricted to minimum required privileges (e.g. internet access only).
    • Single Sign-On (SSO) should be used where appropriate.
  • Authorisation Criteria Authorisation decisions should consider characteristics such as geolocation, time of access, and the security posture of the requesting device.
  • OT-Specific Considerations
    • In environments where individual accounts are not technically feasible — such as shared access to PLCs or HMIs, access should be limited to essential functions only, and enforced through secure methods like a jump server or HMI front-end that logs activity, restricts access by role or time, and adds an extra authentication layer (e.g. badge or PIN).
    • Authentication methods should align with the capabilities of OT systems.
    • Access to OT systems should be logged and monitored where possible.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_PR_AA_05_1
All data (25 statements)

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

http://cyfun.data.gift/ontology#Requirement

type

The subject is an instance of a class.

Concept

An idea or notion; a unit of thought.

label

A human-readable name for the subject.

PR.AA-05.1: Access permissions, rights, and authorisations shall be defined, managed, enforced and reviewed.

http://cyfun.data.gift/ontology#requirementId

PR.AA-05.1

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p28

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p66

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p93

has broader

Relates a concept to a concept that is more general in meaning.

http://cyfun.data.gift/data/subcategory_PR.AA-05

note

A general note, for any purpose.

The goal of this control is to ensure that access permissions, rights, and authorisations are clearly defined, properly managed, consistently enforced, and regularly reviewed to protect systems and data from unauthor- ised access. To achieve this goal, the following should be considered: • Access Definition and Management o Access lists for systems (e.g. files, servers, software, databases) should be created and reviewed regularly. o Reviews should be supported by tools such as Active Directory analysis. o Permission management procedures should be documented and updated as needed. • Access Review and Revocation o Logical and physical access rights should be reviewed periodicallyandwheneverroles change orindividuals leave the organisation. o Unnecessary privileges should be revoked immediately. • UserAccount Practices o Each user, including contractors, should have a separate account to ensure accountability. o Where technically feasible, appropriate authentication measures should be applied. o Guest accounts should be restricted to minimum required privileges (e.g. internet access only). o Single Sign-On (SSO) should be used where appropriate. • Authorisation Criteria Authorisation decisions should consider characteristics such as geolocation, time of access, and the security posture of the requesting device. • OT-Specific Considerations o In environments where individual accounts are not technically feasible — such as shared access to PLCs or HMIs, access should be limited to essential functions only, and enforced through secure methods like a jump server or HMI front-end that logs activity, restricts access by role or time, and adds an extra authentication layer (e.g. badge or PIN). o Authentication methods should align with the capabilities of OT systems. o Access to OT systems should be logged and monitored where possible.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that access permissions, rights, and authorisations are clearly defined, properly managed, consistently enforced, and regularly reviewed to protect systems and data from unauthor- ised access. To achieve this goal, the following should be considered:</p><ul><li>Access Definition and Management<ul><li>Access lists for systems (e.g. files, servers, software, databases) should be created and reviewed regularly.</li><li>Reviews should be supported by tools such as Active Directory analysis.</li><li>Permission management procedures should be documented and updated as needed.</li></ul></li><li>Access Review and Revocation<ul><li>Logical and physical access rights should be reviewed periodicallyandwheneverroles change orindividuals leave the organisation.</li><li>Unnecessary privileges should be revoked immediately.</li></ul></li><li>UserAccount Practices<ul><li>Each user, including contractors, should have a separate account to ensure accountability.</li><li>Where technically feasible, appropriate authentication measures should be applied.</li><li>Guest accounts should be restricted to minimum required privileges (e.g. internet access only).</li><li>Single Sign-On (SSO) should be used where appropriate.</li></ul></li><li>Authorisation Criteria Authorisation decisions should consider characteristics such as geolocation, time of access, and the security posture of the requesting device.</li><li>OT-Specific Considerations<ul><li>In environments where individual accounts are not technically feasible — such as shared access to PLCs or HMIs, access should be limited to essential functions only, and enforced through secure methods like a jump server or HMI front-end that logs activity, restricts access by role or time, and adds an extra authentication layer (e.g. badge or PIN).</li><li>Authentication methods should align with the capabilities of OT systems.</li><li>Access to OT systems should be logged and monitored where possible.</li></ul></li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that access permissions, rights, and authorisations are clearly defined, properly managed, consistently enforced, and regularly reviewed to protect systems and data from unauthor- ised access. To achieve this goal, the following should be considered: - Access Definition and Management - Access lists for systems (e.g. files, servers, software, databases) should be created and reviewed regularly. - Reviews should be supported by tools such as Active Directory analysis. - Permission management procedures should be documented and updated as needed. - Access Review and Revocation - Logical and physical access rights should be reviewed periodicallyandwheneverroles change orindividuals leave the organisation. - Unnecessary privileges should be revoked immediately. - UserAccount Practices - Each user, including contractors, should have a separate account to ensure accountability. - Where technically feasible, appropriate authentication measures should be applied. - Guest accounts should be restricted to minimum required privileges (e.g. internet access only). - Single Sign-On (SSO) should be used where appropriate. - Authorisation Criteria Authorisation decisions should consider characteristics such as geolocation, time of access, and the security posture of the requesting device. - OT-Specific Considerations - In environments where individual accounts are not technically feasible — such as shared access to PLCs or HMIs, access should be limited to essential functions only, and enforced through secure methods like a jump server or HMI front-end that logs activity, restricts access by role or time, and adds an extra authentication layer (e.g. badge or PIN). - Authentication methods should align with the capabilities of OT systems. - Access to OT systems should be logged and monitored where possible.

note

A general note, for any purpose.

The goal of this control is to ensure that access permissions, rights, and authorisations are clearly defined, properly managed, consistently enforced, and regularly reviewed to protect systems and data from unauthor- ised access. To achieve this goal, the following should be considered: - Access Definition and Management - Access lists for systems (e.g. files, servers, software, databases) should be created and reviewed regularly. - Reviews should be supported by tools such as Active Directory analysis. - Permission management procedures should be documented and updated as needed. - Access Review and Revocation - Logical and physical access rights should be reviewed periodicallyandwheneverroles change orindividuals leave the organisation. - Unnecessary privileges should be revoked immediately. - UserAccount Practices - Each user, including contractors, should have a separate account to ensure accountability. - Where technically feasible, appropriate authentication measures should be applied. - Guest accounts should be restricted to minimum required privileges (e.g. internet access only). - Single Sign-On (SSO) should be used where appropriate. - Authorisation Criteria Authorisation decisions should consider characteristics such as geolocation, time of access, and the security posture of the requesting device. - OT-Specific Considerations - In environments where individual accounts are not technically feasible — such as shared access to PLCs or HMIs, access should be limited to essential functions only, and enforced through secure methods like a jump server or HMI front-end that logs activity, restricts access by role or time, and adds an extra authentication layer (e.g. badge or PIN). - Authentication methods should align with the capabilities of OT systems. - Access to OT systems should be logged and monitored where possible.

notation

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.AA-05.1

alternative label

skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.

Access permissions management

preferred label

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.

Access permissions, rights, and authorisations shall be defined, managed, enforced and reviewed.

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_delta_BASIC

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_BASIC

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_KeyMeasures

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_IMPORTANT

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

http://cyfun.data.gift/ontology#level

http://cyfun.data.gift/data/level_BASIC

http://cyfun.data.gift/ontology#isKeyMeasure

1

triple count

The number of triples associated with the subject.

23

in dataset

Specifies the dataset the subject is part of.

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

Resultaten 1 - 25 of 25

References

Inverse links to the subject.