reverse-skills-max: initial public release (restored, redacted, hardened)
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
# Cloud Metadata Path Checklist
|
||||
|
||||
## First Pass
|
||||
|
||||
- Metadata endpoint, hop limit, required headers, session token requirements, link-local route, workload identity binding
|
||||
- Reaching surface: local process, pod, container, proxy, SSRF, sidecar, or host namespace
|
||||
- Downstream trust: role assumption, cloud API, cluster API, secret access, or signed identity use
|
||||
|
||||
## Chain To Reconstruct
|
||||
|
||||
1. Reachable path to metadata established
|
||||
2. Metadata response or token obtained
|
||||
3. Usable identity or credential material extracted
|
||||
4. Downstream API or trust edge accepts it
|
||||
5. Resulting privilege or artifact confirmed
|
||||
|
||||
## Evidence To Keep Together
|
||||
|
||||
- Reachability side: route, headers, namespace, container, SSRF primitive, or proxy path
|
||||
- Identity side: role name, token claims, expiration, audience, issuer, account or project binding
|
||||
- Acceptance side: API action, resource access, secret read, or spawned workload effect
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
- Proving metadata access without proving a useful credential was actually issued
|
||||
- Proving token issuance without showing which downstream API accepts it
|
||||
- Mixing node identity and workload identity without showing which one actually drove the privilege edge
|
||||
Reference in New Issue
Block a user