Performing Privilege Escalation Assessment
Overview
Cybersecurity skill for performing privilege escalation assessment. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing privilege escalation assessment"
"Performs privilege escalation assessments on compromised Linux and Windows syste"
After gaining initial low-privilege access during a penetration test to demonstrate full system compromise
Assessing the security hardening of Linux and Windows servers against local privilege escalation attacks
Evaluating whether endpoint detection and response (EDR) tools detect common privilege escalation techniques
Testing the effectiveness of least-privilege policies and application whitelisting on endpoints
Validating that container breakout and VM escape controls are properly configured
Do not use without written authorization, against production systems where exploitation could cause downtime, or for deploying kernel exploits on systems without prior approval and rollback capability.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Low-privilege shell access (reverse shell, SSH, RDP) to the target system obtained through authorized means
- Privilege escalation enumeration scripts: linPEAS (Linux), winPEAS (Windows), Linux Smart Enumeration (LSE)
- Compiled kernel exploits for common CVEs or access to compilation tools on the target
- GTFOBins reference for Linux SUID/sudo binary abuse and LOLBAS reference for Windows living-off-the-land binaries
- Precompiled post-exploitation binaries for the target architecture if compilation is not available on the target
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for privilege escalation assessment operations.
- Prepare Environment — Set up tools, access, and data sources required for privilege escalation assessment.
- Execute Core Workflow — Perform the privilege escalation assessment operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Design — Define interface, identify patterns, plan implementation
- Implement — Write code following existing conventions, add tests
- Verify — Run tests, check integration, validate behavior
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-privilege-escalation-assessment3description: Use when performs privilege escalation assessments on compromised Linux and Windows systems to identify paths from low-privilege access to root or SYSTEM-level control. The tester enumerates misconfigurations, vulnerable services, kernel exploits, SUID binaries, unquoted service paths, and credential stores to demonstrate the full impact of an initial compromise. Use when working with performing privilege escalation assessment.4license: Apache-2.05---67# Performing Privilege Escalation Assessment89## Overview1011Cybersecurity skill for performing privilege escalation assessment. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing privilege escalation assessment"16- "Performs privilege escalation assessments on compromised Linux and Windows syste"171819- After gaining initial low-privilege access during a penetration test to demonstrate full system compromise20- Assessing the security hardening of Linux and Windows servers against local privilege escalation attacks21- Evaluating whether endpoint detection and response (EDR) tools detect common privilege escalation techniques22- Testing the effectiveness of least-privilege policies and application whitelisting on endpoints23- Validating that container breakout and VM escape controls are properly configured2425**Do not use** without written authorization, against production systems where exploitation could cause downtime, or for deploying kernel exploits on systems without prior approval and rollback capability.262728## When NOT to Use2930- When you lack proper authorization for testing31- For production systems without change management32- When the task requires legal or compliance expertise beyond technical scope333435## Prerequisites3637- Low-privilege shell access (reverse shell, SSH, RDP) to the target system obtained through authorized means38- Privilege escalation enumeration scripts: linPEAS (Linux), winPEAS (Windows), Linux Smart Enumeration (LSE)39- Compiled kernel exploits for common CVEs or access to compilation tools on the target40- GTFOBins reference for Linux SUID/sudo binary abuse and LOLBAS reference for Windows living-off-the-land binaries41- Precompiled post-exploitation binaries for the target architecture if compilation is not available on the target4243## Workflow4445```python46# Example: IOC detection47import re4849IOC_PATTERNS = {50 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",51 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",52 "hash_md5": r"\b[a-f0-9]{32}\b",53 "hash_sha256": r"\b[a-f0-9]{64}\b",54}5556def extract_iocs(text: str) -> dict:57 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}58```59601. **Plan Operations** — Define objectives, scope, and success criteria for privilege escalation assessment operations.612. **Prepare Environment** — Set up tools, access, and data sources required for privilege escalation assessment.623. **Execute Core Workflow** — Perform the privilege escalation assessment operations following established procedures.634. **Validate Results** — Verify that results meet quality standards and objectives.645. **Report Findings** — Document results, observations, and recommendations.656. **Follow Up** — Track remediation actions and verify fixes where applicable.6667## Tools6869- **Analysis Platform** — Data processing and visualization70- **Collaboration Tools** — Team coordination and knowledge sharing717273## Process74751. **Design** — Define interface, identify patterns, plan implementation761. **Implement** — Write code following existing conventions, add tests771. **Verify** — Run tests, check integration, validate behavior7879## Verification8081- [ ] All privilege escalation assessment procedures executed completely and documented82- [ ] Findings validated against multiple data sources83- [ ] False positives identified and filtered84- [ ] Results documented with evidence and timestamps85- [ ] Recommendations provided with risk-based prioritization8687## Anti-Rationalization Table8889| Rationalization | Reality |90|---|---|91| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |92| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |93| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |