agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/cross-account/SKILL.md

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.

The file

Files
SKILL.md

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-matrix from personas and corpus routes.
  • Quick test: replay-route on a single high-value route.
  • Full scan: replay-corpus across all routes and all persona pairs.
  • Object-level: object-swap to test IDOR on object references.
  • Tenant-level: tenant-swap to test cross-tenant access.

Available Workflows

WorkflowPurpose
build-matrixConstruct authorization matrix from personas and route catalog.
replay-corpusReplay every corpus route as every persona persona pair.
replay-routeTest a single route across all persona pairs.
object-swapSwap object IDs between personas and replay.
tenant-swapTest cross-tenant access behavior.
role-downgradeTest if downgraded users retain access.
anonymous-replayTest authenticated routes without credentials.
diff-responsesDiff replay results and flag unauthorized access.
evidence-packPackage 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)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.