Concept skos:Concept Code PR.AA-02.2

The organisation shall ensure that unique credentials are used for each authenti- cated user, device, and process interacting with the organisation's critical systems. These credentials shall be verified, and the unique identifiers shall be captured during system interactions. Exceptions may be made for emergency access ("break- glass" procedures), provided such access is strictly controlled, logged, and reviewed.

Also known as

skos:altLabel

Unique credential enforcement

Note

skos:note

The goal of this control is to ensure that each user, device, and process interacting with critical systems is uniquely identifiable and authenticated. This supports accountability, traceability, and secure access, while allowing for controlled exceptions in emergencies. To achieve this goal, the organisation should:

  • Assign Unique Credentials Each user, device, and automated process should have its own unique credentials. Shared accounts should be avoided. All credentials should be verified before access is granted.
  • Implement Strong Authentication Multi-Factor Authentication (MFA – PR.AA-03.2) has to be used wherever feasible. Authentication mecha- nisms should be resistant to replay attacks and credential reuse. These practices align with ENISA’s Secure UserAuthentication Guidelines, which recommend layered and context-aware authentication for critical systems.
  • Enforce Credential Management Practices Password policies and credential rotation should be enforced. Credentials should be reviewed and updated regularly, especially after role changes or offboarding. This supports the principles outlined in ENISA’s NIS2 Technical Implementation Guidance, which emphasise secure identity lifecycle management.
  • ApplyAccess Control and Monitoring Access should follow the Principle of Least Privilege. Logs and audit trails should be continuously monitored to detect anomalies. Suspicious activity should be investigated promptly.
  • Control EmergencyAccess ("Break-Glass") Emergency access should be granted only through designated break-glass accounts.These accounts should be tightly controlled, time-limited, fully logged, and reviewed after use. Justification and approval should be required for each instance.
  • Promote UserAwareness and Training Personnel should be trained on the importance of using individual credentials and reporting suspicious access. Awareness should include the risks of credential sharing and misuse.
  • Ensure OT-Specific Feasibility In OTenvironments, unique credentials should be implemented in a waythat respects operational constraints and system limitations. Coordination with engineering teams may be required.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_PR_AA_02_2
All data (19 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-02.2: The organisation shall ensure that unique credentials are used for each authenti- cated user, device, and process interacting with the organisation's critical systems. These credentials shall be verified, and the unique identifiers shall be captured during system interactions. Exceptions may be made for emergency access ("break- glass" procedures), provided such access is strictly controlled, logged, and reviewed.

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

PR.AA-02.2

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p87

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to ensure that each user, device, and process interacting with critical systems is uniquely identifiable and authenticated. This supports accountability, traceability, and secure access, while allowing for controlled exceptions in emergencies. To achieve this goal, the organisation should: - Assign Unique Credentials Each user, device, and automated process should have its own unique credentials. Shared accounts should be avoided. All credentials should be verified before access is granted. - Implement Strong Authentication Multi-Factor Authentication (MFA – PR.AA-03.2) has to be used wherever feasible. Authentication mecha- nisms should be resistant to replay attacks and credential reuse. These practices align with ENISA’s Secure UserAuthentication Guidelines, which recommend layered and context-aware authentication for critical systems. - Enforce Credential Management Practices Password policies and credential rotation should be enforced. Credentials should be reviewed and updated regularly, especially after role changes or offboarding. This supports the principles outlined in ENISA’s NIS2 Technical Implementation Guidance, which emphasise secure identity lifecycle management. - ApplyAccess Control and Monitoring Access should follow the Principle of Least Privilege. Logs and audit trails should be continuously monitored to detect anomalies. Suspicious activity should be investigated promptly. - Control EmergencyAccess ("Break-Glass") Emergency access should be granted only through designated break-glass accounts.These accounts should be tightly controlled, time-limited, fully logged, and reviewed after use. Justification and approval should be required for each instance. - Promote UserAwareness and Training Personnel should be trained on the importance of using individual credentials and reporting suspicious access. Awareness should include the risks of credential sharing and misuse. - Ensure OT-Specific Feasibility In OTenvironments, unique credentials should be implemented in a waythat respects operational constraints and system limitations. Coordination with engineering teams may be required.

note

A general note, for any purpose.

The goal of this control is to ensure that each user, device, and process interacting with critical systems is uniquely identifiable and authenticated. This supports accountability, traceability, and secure access, while allowing for controlled exceptions in emergencies. To achieve this goal, the organisation should: • Assign Unique Credentials Each user, device, and automated process should have its own unique credentials. Shared accounts should be avoided. All credentials should be verified before access is granted. • Implement Strong Authentication Multi-Factor Authentication (MFA – PR.AA-03.2) has to be used wherever feasible. Authentication mecha- nisms should be resistant to replay attacks and credential reuse. These practices align with ENISA’s Secure UserAuthentication Guidelines, which recommend layered and context-aware authentication for critical systems. • Enforce Credential Management Practices Password policies and credential rotation should be enforced. Credentials should be reviewed and updated regularly, especially after role changes or offboarding. This supports the principles outlined in ENISA’s NIS2 Technical Implementation Guidance, which emphasise secure identity lifecycle management. • ApplyAccess Control and Monitoring Access should follow the Principle of Least Privilege. Logs and audit trails should be continuously monitored to detect anomalies. Suspicious activity should be investigated promptly. • Control EmergencyAccess ("Break-Glass") Emergency access should be granted only through designated break-glass accounts.These accounts should be tightly controlled, time-limited, fully logged, and reviewed after use. Justification and approval should be required for each instance. • Promote UserAwareness and Training Personnel should be trained on the importance of using individual credentials and reporting suspicious access. Awareness should include the risks of credential sharing and misuse. • Ensure OT-Specific Feasibility In OTenvironments, unique credentials should be implemented in a waythat respects operational constraints and system limitations. Coordination with engineering teams may be required.

note

A general note, for any purpose.

The goal of this control is to ensure that each user, device, and process interacting with critical systems is uniquely identifiable and authenticated. This supports accountability, traceability, and secure access, while allowing for controlled exceptions in emergencies. To achieve this goal, the organisation should: - Assign Unique Credentials Each user, device, and automated process should have its own unique credentials. Shared accounts should be avoided. All credentials should be verified before access is granted. - Implement Strong Authentication Multi-Factor Authentication (MFA – PR.AA-03.2) has to be used wherever feasible. Authentication mecha- nisms should be resistant to replay attacks and credential reuse. These practices align with ENISA’s Secure UserAuthentication Guidelines, which recommend layered and context-aware authentication for critical systems. - Enforce Credential Management Practices Password policies and credential rotation should be enforced. Credentials should be reviewed and updated regularly, especially after role changes or offboarding. This supports the principles outlined in ENISA’s NIS2 Technical Implementation Guidance, which emphasise secure identity lifecycle management. - ApplyAccess Control and Monitoring Access should follow the Principle of Least Privilege. Logs and audit trails should be continuously monitored to detect anomalies. Suspicious activity should be investigated promptly. - Control EmergencyAccess ("Break-Glass") Emergency access should be granted only through designated break-glass accounts.These accounts should be tightly controlled, time-limited, fully logged, and reviewed after use. Justification and approval should be required for each instance. - Promote UserAwareness and Training Personnel should be trained on the importance of using individual credentials and reporting suspicious access. Awareness should include the risks of credential sharing and misuse. - Ensure OT-Specific Feasibility In OTenvironments, unique credentials should be implemented in a waythat respects operational constraints and system limitations. Coordination with engineering teams may be required.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that each user, device, and process interacting with critical systems is uniquely identifiable and authenticated. This supports accountability, traceability, and secure access, while allowing for controlled exceptions in emergencies. To achieve this goal, the organisation should:</p><ul><li>Assign Unique Credentials Each user, device, and automated process should have its own unique credentials. Shared accounts should be avoided. All credentials should be verified before access is granted.</li><li>Implement Strong Authentication Multi-Factor Authentication (MFA – PR.AA-03.2) has to be used wherever feasible. Authentication mecha- nisms should be resistant to replay attacks and credential reuse. These practices align with ENISA’s Secure UserAuthentication Guidelines, which recommend layered and context-aware authentication for critical systems.</li><li>Enforce Credential Management Practices Password policies and credential rotation should be enforced. Credentials should be reviewed and updated regularly, especially after role changes or offboarding. This supports the principles outlined in ENISA’s NIS2 Technical Implementation Guidance, which emphasise secure identity lifecycle management.</li><li>ApplyAccess Control and Monitoring Access should follow the Principle of Least Privilege. Logs and audit trails should be continuously monitored to detect anomalies. Suspicious activity should be investigated promptly.</li><li>Control EmergencyAccess ("Break-Glass") Emergency access should be granted only through designated break-glass accounts.These accounts should be tightly controlled, time-limited, fully logged, and reviewed after use. Justification and approval should be required for each instance.</li><li>Promote UserAwareness and Training Personnel should be trained on the importance of using individual credentials and reporting suspicious access. Awareness should include the risks of credential sharing and misuse.</li><li>Ensure OT-Specific Feasibility In OTenvironments, unique credentials should be implemented in a waythat respects operational constraints and system limitations. Coordination with engineering teams may be required.</li></ul></div>

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-02.2

alternative label

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

Unique credential enforcement

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.

The organisation shall ensure that unique credentials are used for each authenti- cated user, device, and process interacting with the organisation's critical systems. These credentials shall be verified, and the unique identifiers shall be captured during system interactions. Exceptions may be made for emergency access ("break- glass" procedures), provided such access is strictly controlled, logged, 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_IMPORTANT_to_ESSENTIAL

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_ESSENTIAL

triple count

The number of triples associated with the subject.

17

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 19 of 19

References

Inverse links to the subject.