# Privilege Escalation

Privilege escalation is the acquisition of permissions beyond an identity’s intended authorization, often by exploiting excessive permissions, trust relationships, or control over privileged workloads.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/privilege-escalation

> In cloud environments, an identity can gain unintended access without exploiting a software vulnerability: legitimate administrative APIs can become escalation paths when permissions are combined incorrectly. Preventing and investigating escalation requires evaluating effective authorization, identifying indirect paths to privileged identities, and correcting the permissions or trust relationships that enable them.

Practice exams covering Privilege Escalation: [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty).

## 6 key aspects of Privilege Escalation

Privilege-escalation control combines analysis of indirect access paths, protected authorization administration, audit evidence, and verified remediation.

1. **Indirect authorization paths**: Assess what an identity can cause another identity or workload to do, not just its direct resource access. Deployment permissions, policy editing, and role passing can combine into capabilities that no single permission makes obvious.
2. **Effective-permission analysis**: Evaluate identity policies, resource policies, trust policies, conditions, and applicable permission ceilings together. A policy attachment alone does not describe all the permissions available to a principal.
3. **Protected privilege administration**: Restrict who can edit policies, change trust relationships, attach privileged roles, or remove permission boundaries. Keep ordinary workload administration separate from authorization administration wherever practical.
4. **Evidence-driven investigation**: Correlate unexpected access with audit events for policy changes, role assumptions, and workload modifications. Identify the original principal and the full sequence of actions that produced the elevated capability.
5. **Analyzer findings with context**: Use automated access analysis to identify unintended sharing, unused permissions, and policy concerns. Confirm findings against approved access requirements, and do not treat a clean report as proof that every escalation path is absent.
6. **Complete containment and verification**: Remove the enabling authorization path and address existing credentials, sessions, and persistence. Test that the prohibited path fails while approved operational workflows continue to work.

## Cloud services for Privilege Escalation

IAM defines identities and authorization relationships, while IAM Access Analyzer highlights supported access exposures, policy concerns, and unused permissions. CloudTrail supplies API evidence for reconstructing how an identity changed authorization or deployed a privileged workload. AWS Config adds supported configuration history and compliance evaluations, helping correlate suspicious activity with resource changes. AWS Organizations supplies account-level permission guardrails through service control policies. Together, these services support prevention, investigation, and remediation, but no single finding or policy establishes that all escalation paths are closed. Engineers must evaluate combined permissions, review approved trust relationships, address active sessions, and test the corrected authorization behavior.

- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records API activity used to reconstruct authorization changes and role usage. Investigators should inspect deployment events containing role references because iam:PassRole does not produce a separate API event, and configure relevant data events when resource-access evidence is required.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Service control policies constrain permissions available to covered principals in member accounts and can block sensitive authorization changes. They do not grant access, do not constrain the management account, and do not apply to service-linked roles.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config records supported resource configurations and evaluates configured compliance rules. Configuration history can help identify when an authorization-related resource changed, while rules can flag selected risky configurations rather than prove the absence of escalation.

## Privilege Escalation exam questions

Real practice exam questions on Privilege Escalation, with the correct answer and its explanation.

### Question 1 (SCS-C03)

**Question:**

A company runs a scheduled AWS Glue job that loads its Python script from s3://data-processing-assets/production/daily.py. The job's execution role can read confidential records that application support personnel are not authorized to read. Only the AWS Glue service can assume the execution role.

Support personnel use a SupportOperator IAM role. Its only S3 write permission allows s3:PutObject on arn:aws:s3:::data-processing-assets/*. Support personnel must continue uploading diagnostic files under staging/, but they do not need to modify production scripts. They have no IAM write permissions, iam:PassRole permission, or permissions to modify or start Glue jobs.

An investigation confirms that a support operator replaced daily.py with code that read confidential records during the next scheduled run. A security engineer stops the job, restores the approved script, and confirms that no job executions remain active. No other policies grant SupportOperator write access to the bucket, and support personnel cannot modify their own permissions.

Which change will prevent recurrence while preserving the scheduled job's required data access and the support team's diagnostic uploads?

**Correct answer:** Replace SupportOperator's bucket-wide s3:PutObject Allow with an Allow scoped to arn:aws:s3:::data-processing-assets/staging/*.

**Explanation:** The operator escalated privileges indirectly by controlling code that executes under a more privileged role. Restricting the only write grant to staging/ prevents replacement of the production script while preserving diagnostic uploads and the Glue job's required permissions.

### Question 2 (DOP-C02)

**Question:**

A company delegates application administration to a development team through a TeamProvisioner IAM role. The role's identity policy and centrally managed permissions boundary allow sts:AssumeRole on all roles in the account. The boundary otherwise limits access to development resources. Developers cannot modify IAM policies, permissions boundaries, or role trust policies.

During a security test, a developer assumes TeamProvisioner and then successfully assumes SecurityOperations, a role outside the /team-runtime/ path. SecurityOperations trusts TeamProvisioner and has permissions to read production secrets. The developer uses the new credentials to retrieve a production secret, even though TeamProvisioner's boundary does not allow that operation.

Developers must retain permission to assume application roles under /team-runtime/. Those application roles have centrally enforced permissions boundaries that developers cannot change. SecurityOperations must retain its existing permissions for administrative workflows. The security team wants to close the escalation path by changing only TeamProvisioner's permissions boundary.

Which change meets these requirements?

**Correct answer:** Add an explicit deny for sts:AssumeRole to TeamProvisioner's permissions boundary with NotResource set to arn:aws:iam::<account-id>:role/team-runtime/*.

**Explanation:** The explicit deny prevents TeamProvisioner from assuming any role outside the approved path, including SecurityOperations, despite the existing broad allows. It does not deny assumption of roles under /team-runtime/, so authorized application-role assumption remains available. SecurityOperations itself is unchanged.

## Practice Privilege Escalation in a full exam

Questions on Privilege Escalation in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 7 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 4 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 1 question

## What is Privilege Escalation

Privilege escalation occurs when a user, application, or service gains capabilities beyond its intended authorization. In cloud systems, this often involves valid API calls rather than an operating-system exploit. A developer who cannot directly read sensitive data might nevertheless be able to modify a workload that runs under an identity authorized to read it. The security question is therefore not only what the developer can access now, but also what permissions the developer can acquire or exercise indirectly.

Evaluate effective authorization across identity policies, resource policies, role trust policies, session restrictions, organizational controls, and relevant conditions. Authentication establishes who is making a request; authorization determines whether that request is allowed. Successful authentication, including multifactor authentication, does not make an excessively permissive authorization policy safe. Likewise, an identity with no administrator policy can still have an escalation path through a small combination of powerful permissions.

For example, an AWS identity allowed to change a managed IAM policy and make a new policy version the default could expand its own access if that policy controls its permissions. Another identity might combine iam:PassRole with permission to create and invoke a function using a more privileged execution role. Passing a role does not itself provide the caller with the role’s credentials, but controlling code that executes under that role can expose its capabilities. Investigate the complete chain, including the role’s trust policy, the caller’s deployment permissions, and the workload’s reachable resources.

Role assumption is another important path. A broadly written trust policy can let an unintended principal obtain a privileged session, subject to the applicable authorization requirements. Cross-account access is not automatically privilege escalation: it may be an intentional delegation. It becomes a security problem when the effective access exceeds the approved scope. Similarly, legitimate, approved temporary elevation is different from unintended elevation, although both require careful restrictions and auditing.

Start an investigation by identifying the principal, the unexpected action, the affected resource, and the authorization changes preceding the event. Review policy attachments, policy versions, group membership, trust relationships, resource policies, permissions boundaries, and organizational policies. Use audit records to reconstruct policy changes, role assumptions, and workload modifications. In AWS, iam:PassRole is a permission check rather than a standalone API call, so investigate the service API operation that received the role instead of expecting a separate PassRole event.

AWS IAM Access Analyzer helps identify resource access outside a configured zone of trust, validate policies, and find unused access through the corresponding analyzer capabilities. Findings require interpretation: an external-access finding can represent approved sharing, while the absence of a finding does not prove that no escalation chain exists. Policy validation checks policy structure and security concerns; it is not a complete assessment of every possible combination of permissions and workload behavior.

Correct the enabling permissions rather than merely removing the final administrator policy. Restrict role passing to approved role ARNs and services, separate workload deployment from privileged identity administration, and protect policy and boundary changes. Permissions boundaries limit identity-based permissions but do not grant access; some direct resource-policy grants have different evaluation behavior, so boundaries are not a universal ceiling. AWS Organizations service control policies establish guardrails for covered principals in member accounts, but they also do not grant permissions and have documented exclusions.

Containment may require disabling compromised credentials, revoking applicable role sessions, removing persistence, and correcting resource policies as well as identity policies. Changing a role’s trust policy prevents newly authorized assumptions but does not automatically invalidate sessions already issued. After remediation, test both prohibited escalation paths and legitimate workflows. Narrow permissions reduce risk but increase policy maintenance and troubleshooting effort; controlled elevation, automated policy checks, and monitored emergency access help balance operational needs with enforceable authorization boundaries.

## Learn Privilege Escalation in lessons

3 short lessons on Privilege Escalation in 3 certification courses.

- DEA-C01: Privilege Escalation: escalation-resistant permissions (Premium), https://app.blowstack.com/lessons/privilege-escalation-escalation-resistant-permissions-dea-c01
- SCS-C03: Privilege Escalation: indirect authorization paths (Premium), https://app.blowstack.com/lessons/privilege-escalation-indirect-authorization-paths-scs-c03
- DOP-C02: Privilege Escalation: Guarding Delegated IAM Administration (Premium), https://app.blowstack.com/lessons/privilege-escalation-guarding-delegated-iam-administration-dop-c02
