A privileged account has elevated permissions that allow administrative or high-impact actions beyond those available to regular accounts. It may manage access rules, change system configurations, install software, create or delete accounts, disable security controls, or access sensitive data. section 8.5 section 10.4.4
Because one compromised privileged account can affect many users and critical resources, organizations treat it as a high-risk identity. Access should have a valid business reason, require strong protection, and remain limited to the permissions and time needed for a task. section 8.6 section 10.4.4
Practical safeguards for privileged accounts include:
- Use just-in-time access so elevated privileges are granted temporarily and revoked when the task ends. section 8.6
- Grant only the permissions required for the specific task, and review continuing access to limit privilege creep. section 8.6 section 10.4.4
- Protect PAM access with additional authentication and closely control who can request or approve elevated access. section 8.6 section 10.4.4
- Record the reason, approved permissions, approver, duration, and actions performed during privileged access. section 10.4.4
- Monitor activity for compliance, investigations, and suspicious behavior, while recognizing that authorized accounts can still cause significant harm if compromised. section 10.4.3 section 10.4.4
A compromised administrator account
An attacker with a regular account may be limited to that account’s files. A compromised domain administrator account could create users, delete accounts, disable security controls, or reach sensitive resources. A hospital can reduce this risk by recording who accessed medical records, when, why, which permissions were approved, and what actions followed. section 8.6 section 10.4.4
|
Account Type
|
Description
|
|
User Accounts
|
Used by individuals to interact with systems or
applications.
They range from basic access accounts to those with more
privileges.
|
|
Privileged Accounts
|
Elevated administrative access, such as system
configurations or critical data.
Require strict security to prevent misuse or unauthorized
access.
|
|
Guest Accounts
|
Temporary accounts with minimal privileges, used for
short-term access.
Must be managed carefully to avoid unauthorized use or
privilege escalation.
|
|
Shared Accounts
|
Generic accounts used by multiple users, posing
accountability risks.
Organizations often discourage their use or implement
delegation mechanisms for better security.
|
|
Service Accounts
|
Non-human accounts used for system-to-system or
application communication.
Operating in the background.
|
Compare privileged accounts with user, guest, shared, and service accounts to distinguish elevated administrative access from other account roles. section 8.5
