Concept skos:Concept Code PR.AA-05.4

No one shall have administrative privileges for routine day-to-day tasks.

Also known as

skos:altLabel

Administrative privilege restriction

Note

skos:note

The goal of this control is to prevent the use of administrative privileges for routine, day-to-day tasks, thereby reducing the risk of misuse or exploitation by attackers. To ensure this goal is met, the organisation should consider the following:

  • Account Separation and Privilege Management
    • Administrative and general user accounts should be strictly separated.
    • Dedicated administrator accounts should be used only for system management and administrative tasks.
    • User accounts should not have administrative privileges.
  • Access Restrictions and Security Measures
    • Unique local administrator passwords should be created for each system.
    • Unused accounts should be promptly disabled.
    • Internet browsing from administrative accounts should be prohibited to reduce exposure to web-based threats.
  • OT-Specific Considerations
    • In OT environments, administrative access should be limited to essential personnel and functions.
    • Where shared access is necessary, secure access methods (e.g. jump servers, session logging) should be used to enforce accountability and reduce risk.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_PR_AA_05_4
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.4: No one shall have administrative privileges for routine day-to-day tasks.

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

PR.AA-05.4

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p30

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p68

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p95

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 prevent the use of administrative privileges for routine, day-to-day tasks, thereby reducing the risk of misuse or exploitation by attackers. To ensure this goal is met, the organisation should consider the following: • Account Separation and Privilege Management o Administrative and general user accounts should be strictly separated. o Dedicated administrator accounts should be used only for system management and administrative tasks. o User accounts should not have administrative privileges. • Access Restrictions and Security Measures o Unique local administrator passwords should be created for each system. o Unused accounts should be promptly disabled. o Internet browsing from administrative accounts should be prohibited to reduce exposure to web-based threats. • OT-Specific Considerations o In OT environments, administrative access should be limited to essential personnel and functions. o Where shared access is necessary, secure access methods (e.g. jump servers, session logging) should be used to enforce accountability and reduce risk.

note

A general note, for any purpose.

The goal of this control is to prevent the use of administrative privileges for routine, day-to-day tasks, thereby reducing the risk of misuse or exploitation by attackers. To ensure this goal is met, the organisation should consider the following: - Account Separation and Privilege Management - Administrative and general user accounts should be strictly separated. - Dedicated administrator accounts should be used only for system management and administrative tasks. - User accounts should not have administrative privileges. - Access Restrictions and Security Measures - Unique local administrator passwords should be created for each system. - Unused accounts should be promptly disabled. - Internet browsing from administrative accounts should be prohibited to reduce exposure to web-based threats. - OT-Specific Considerations - In OT environments, administrative access should be limited to essential personnel and functions. - Where shared access is necessary, secure access methods (e.g. jump servers, session logging) should be used to enforce accountability and reduce risk.

note

A general note, for any purpose.

The goal of this control is to prevent the use of administrative privileges for routine, day-to-day tasks, thereby reducing the risk of misuse or exploitation by attackers. To ensure this goal is met, the organisation should consider the following: - Account Separation and Privilege Management - Administrative and general user accounts should be strictly separated. - Dedicated administrator accounts should be used only for system management and administrative tasks. - User accounts should not have administrative privileges. - Access Restrictions and Security Measures - Unique local administrator passwords should be created for each system. - Unused accounts should be promptly disabled. - Internet browsing from administrative accounts should be prohibited to reduce exposure to web-based threats. - OT-Specific Considerations - In OT environments, administrative access should be limited to essential personnel and functions. - Where shared access is necessary, secure access methods (e.g. jump servers, session logging) should be used to enforce accountability and reduce risk.

note

A general note, for any purpose.

<div><p>The goal of this control is to prevent the use of administrative privileges for routine, day-to-day tasks, thereby reducing the risk of misuse or exploitation by attackers. To ensure this goal is met, the organisation should consider the following:</p><ul><li>Account Separation and Privilege Management<ul><li>Administrative and general user accounts should be strictly separated.</li><li>Dedicated administrator accounts should be used only for system management and administrative tasks.</li><li>User accounts should not have administrative privileges.</li></ul></li><li>Access Restrictions and Security Measures<ul><li>Unique local administrator passwords should be created for each system.</li><li>Unused accounts should be promptly disabled.</li><li>Internet browsing from administrative accounts should be prohibited to reduce exposure to web-based threats.</li></ul></li><li>OT-Specific Considerations<ul><li>In OT environments, administrative access should be limited to essential personnel and functions.</li><li>Where shared access is necessary, secure access methods (e.g. jump servers, session logging) should be used to enforce accountability and reduce risk.</li></ul></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-05.4

alternative label

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

Administrative privilege restriction

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.

No one shall have administrative privileges for routine day-to-day tasks.

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.