cross-account
Skill1 starsChanged 3 months agoMITView on GitHub
Persona credentials, session cookies, and auth headers are stored local-only under $OUTDIR/persona and are never committed (gitignore enforced); all evidence written by these workflows must redact/sanitize tokens, cookies, and bearer values before it is saved or shared.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
Files
Cross-Account Authorization Testing
Overview
Automate IDOR/BOLA/BFLA/tenant isolation testing by replaying captured requests across multiple authenticated personas and diffing the responses. Converts raw traffic into structured authorization experiments.
Quick Reference
- Skill: cross-account
- Version: 1.0.0
- Bounded Context: AuthorizationContext
- Required tools:
python3,curl,jq - Risk tier: intrusive (replays against target)
Workflow Selection
- Setup:
build-matrixfrom personas and corpus routes. - Quick test:
replay-routeon a single high-value route. - Full scan:
replay-corpusacross all routes and all persona pairs. - Object-level:
object-swapto test IDOR on object references. - Tenant-level:
tenant-swapto test cross-tenant access.
Available Workflows
| Workflow | Purpose |
build-matrix | Construct authorization matrix from personas and route catalog. |
replay-corpus | Replay every corpus route as every persona persona pair. |
replay-route | Test a single route across all persona pairs. |
object-swap | Swap object IDs between personas and replay. |
tenant-swap | Test cross-tenant access behavior. |
role-downgrade | Test if downgraded users retain access. |
anonymous-replay | Test authenticated routes without credentials. |
diff-responses | Diff replay results and flag unauthorized access. |
evidence-pack | Package confirmed finding with replay evidence. |
Evidence Required
- Baseline owner request and response.
- Attacker replay request and response.
- Diff showing status code, body field, or authorization discrepancy.
- Persona relationship (same tenant, different tenant, admin vs user).
Persona credentials, session cookies, and auth headers are stored local-only under $OUTDIR/persona and are never committed (gitignore enforced); all evidence written by these workflows must redact/sanitize tokens, cookies, and bearer values before it is saved or shared.
References
- OWASP WSTG-ATHZ-02 (Insecure Direct Object References)
- OWASP API1:2023 (Broken Object Level Authorization)
- OWASP API5:2023 (Broken Function Level Authorization)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

