Concept skos:Concept Code PR.AA-01.5

The organisation’s critical systems shall be monitored for atypical use of system credentials. Credentials associated with significant risk shall be disabled.

Also known as

skos:altLabel

Atypical credential usage monitoring

Note

skos:note

The goal of this control is to detect and respond to abnormal or high-risk use of system credentials in critical systems, helping to prevent unauthorised access, insider threats, and credential-based attacks. To achieve this goal, the organisation should:

  • Detect Atypical Credential Use Systems should be monitored for deviations from normal credential usage patterns, such as unusual login times, access from unfamiliarlocations, use of unfamiliarsystems, simultaneous logins from distant locations, or sudden access to sensitive data.
  • Limit and Respond to Failed Login Attempts A threshold for failed login attempts should be enforced. Accounts should be locked automatically after repeated failures and remain inaccessible until a defined lockout period expires or an authorised adminis- trator resets them.
  • Manage Credential Lifecycles Credential issuance, usage, and revocation should be automated where possible. An up-to-date inventory of active credentials should be maintained, and unused or orphaned accounts should be regularly reviewed and disabled.
  • Monitor and Correlate Events Security Information and Event Management (SIEM) tools or equivalent solutions should be considered to detect anomalies and correlate events across systems. Behavioural baselining should be implemented to identify deviations from typical usage.
  • Disable High-Risk Credentials Automatically Credentials associated with confirmed or high-risk anomalous activity should be disabled immediately. Security teams should be notified for investigation and response. All actions should be logged for audit and forensic purposes.
  • Raise UserAwareness Users should be trained on secure credential practices and encouraged to report suspicious activity or anomalies in access behaviour.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_PR_AA_01_5
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-01.5: The organisation’s critical systems shall be monitored for atypical use of system credentials. Credentials associated with significant risk shall be disabled.

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

PR.AA-01.5

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p86

has broader

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

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

note

A general note, for any purpose.

<div><p>The goal of this control is to detect and respond to abnormal or high-risk use of system credentials in critical systems, helping to prevent unauthorised access, insider threats, and credential-based attacks. To achieve this goal, the organisation should:</p><ul><li>Detect Atypical Credential Use Systems should be monitored for deviations from normal credential usage patterns, such as unusual login times, access from unfamiliarlocations, use of unfamiliarsystems, simultaneous logins from distant locations, or sudden access to sensitive data.</li><li>Limit and Respond to Failed Login Attempts A threshold for failed login attempts should be enforced. Accounts should be locked automatically after repeated failures and remain inaccessible until a defined lockout period expires or an authorised adminis- trator resets them.</li><li>Manage Credential Lifecycles Credential issuance, usage, and revocation should be automated where possible. An up-to-date inventory of active credentials should be maintained, and unused or orphaned accounts should be regularly reviewed and disabled.</li><li>Monitor and Correlate Events Security Information and Event Management (SIEM) tools or equivalent solutions should be considered to detect anomalies and correlate events across systems. Behavioural baselining should be implemented to identify deviations from typical usage.</li><li>Disable High-Risk Credentials Automatically Credentials associated with confirmed or high-risk anomalous activity should be disabled immediately. Security teams should be notified for investigation and response. All actions should be logged for audit and forensic purposes.</li><li>Raise UserAwareness Users should be trained on secure credential practices and encouraged to report suspicious activity or anomalies in access behaviour.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to detect and respond to abnormal or high-risk use of system credentials in critical systems, helping to prevent unauthorised access, insider threats, and credential-based attacks. To achieve this goal, the organisation should: - Detect Atypical Credential Use Systems should be monitored for deviations from normal credential usage patterns, such as unusual login times, access from unfamiliarlocations, use of unfamiliarsystems, simultaneous logins from distant locations, or sudden access to sensitive data. - Limit and Respond to Failed Login Attempts A threshold for failed login attempts should be enforced. Accounts should be locked automatically after repeated failures and remain inaccessible until a defined lockout period expires or an authorised adminis- trator resets them. - Manage Credential Lifecycles Credential issuance, usage, and revocation should be automated where possible. An up-to-date inventory of active credentials should be maintained, and unused or orphaned accounts should be regularly reviewed and disabled. - Monitor and Correlate Events Security Information and Event Management (SIEM) tools or equivalent solutions should be considered to detect anomalies and correlate events across systems. Behavioural baselining should be implemented to identify deviations from typical usage. - Disable High-Risk Credentials Automatically Credentials associated with confirmed or high-risk anomalous activity should be disabled immediately. Security teams should be notified for investigation and response. All actions should be logged for audit and forensic purposes. - Raise UserAwareness Users should be trained on secure credential practices and encouraged to report suspicious activity or anomalies in access behaviour.

note

A general note, for any purpose.

The goal of this control is to detect and respond to abnormal or high-risk use of system credentials in critical systems, helping to prevent unauthorised access, insider threats, and credential-based attacks. To achieve this goal, the organisation should: - Detect Atypical Credential Use Systems should be monitored for deviations from normal credential usage patterns, such as unusual login times, access from unfamiliarlocations, use of unfamiliarsystems, simultaneous logins from distant locations, or sudden access to sensitive data. - Limit and Respond to Failed Login Attempts A threshold for failed login attempts should be enforced. Accounts should be locked automatically after repeated failures and remain inaccessible until a defined lockout period expires or an authorised adminis- trator resets them. - Manage Credential Lifecycles Credential issuance, usage, and revocation should be automated where possible. An up-to-date inventory of active credentials should be maintained, and unused or orphaned accounts should be regularly reviewed and disabled. - Monitor and Correlate Events Security Information and Event Management (SIEM) tools or equivalent solutions should be considered to detect anomalies and correlate events across systems. Behavioural baselining should be implemented to identify deviations from typical usage. - Disable High-Risk Credentials Automatically Credentials associated with confirmed or high-risk anomalous activity should be disabled immediately. Security teams should be notified for investigation and response. All actions should be logged for audit and forensic purposes. - Raise UserAwareness Users should be trained on secure credential practices and encouraged to report suspicious activity or anomalies in access behaviour.

note

A general note, for any purpose.

The goal of this control is to detect and respond to abnormal or high-risk use of system credentials in critical systems, helping to prevent unauthorised access, insider threats, and credential-based attacks. To achieve this goal, the organisation should: • Detect Atypical Credential Use Systems should be monitored for deviations from normal credential usage patterns, such as unusual login times, access from unfamiliarlocations, use of unfamiliarsystems, simultaneous logins from distant locations, or sudden access to sensitive data. • Limit and Respond to Failed Login Attempts A threshold for failed login attempts should be enforced. Accounts should be locked automatically after repeated failures and remain inaccessible until a defined lockout period expires or an authorised adminis- trator resets them. • Manage Credential Lifecycles Credential issuance, usage, and revocation should be automated where possible. An up-to-date inventory of active credentials should be maintained, and unused or orphaned accounts should be regularly reviewed and disabled. • Monitor and Correlate Events Security Information and Event Management (SIEM) tools or equivalent solutions should be considered to detect anomalies and correlate events across systems. Behavioural baselining should be implemented to identify deviations from typical usage. • Disable High-Risk Credentials Automatically Credentials associated with confirmed or high-risk anomalous activity should be disabled immediately. Security teams should be notified for investigation and response. All actions should be logged for audit and forensic purposes. • Raise UserAwareness Users should be trained on secure credential practices and encouraged to report suspicious activity or anomalies in access behaviour.

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

alternative label

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

Atypical credential usage monitoring

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’s critical systems shall be monitored for atypical use of system credentials. Credentials associated with significant risk shall be disabled.

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.