Access Control Testing
Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.
Install
/plugin marketplace add mn-youssef/security-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add mn-youssef/security-skills --skill access-control-testinggit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/access-control-testing ~/.claude/skills/access-control-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Access Control Testing (FIND/EXPLOIT — OWASP A01) ## Overview Verify that every object and every action enforces "is *this* caller allowed?" server-side. Broken access control is the most common and highest-impact real-world flaw — and the easiest to miss because the happy path works perfectly. **Core principle:** Authentication proves *who you are*; authorization proves *what you may do*. Test the second one on every object and every action — not just the UI-visible ones. ## Applies when / Skip when - **Applies when:** the app has authentication, multiple users, roles, or multi-tenant data — any resource or action that should be restricted. (Almost every non-trivial app.) - **Skip when:** the app is fully public/anonymous with no per-user or privileged data → N/A. - **If N/A:** report "access-control-testing: N/A — no auth/multi-user surface" and stop. Don't invent access boundaries that don't exist. ## ⚠️ Authorization Use test accounts you created on an app you own/are authorized to test. Two accounts (A and B) plus one admin/one low-priv account is the cleanest setup. ## The test matrix (run every cell) | | Read | Write/Update | Delete | Admin action | |---|---|---|---|---| | **As another user (horizontal)** | A reads B's object? | A edits B's? | A deletes B's? | — | | **As lower privilege (vertical)** | user hits admin read? | user hits admin write? | — | user invokes admin fn? |
Details
- Skill name
access-control-testing- Repository
- mn-youssef/security-skills
- Path
skills/access-control-testing/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Access Control Testing skill do?
Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.
How do I install the Access Control Testing skill?
Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Access Control Testing popular?
It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.
Related skills
Active Pentest
49mn-youssef/security-skills
Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.
API Security Testing
49mn-youssef/security-skills
Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.
Authentication Testing
49mn-youssef/security-skills
Use when testing login, sessions, password reset, OAuth/OIDC/SAML/SSO, MFA, and JWTs for weaknesses that lead to account takeover — credential attacks, session fixation, reset-token poisoning, MFA bypass, and token forgery. On apps you own or are authorized to test.
TDD Workflow
32joneqian/claude-skills-suite
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
Business Logic Testing
49mn-youssef/security-skills
Use when testing application-specific workflow and business-rule flaws that scanners cannot find — price/quantity/parameter tampering, workflow and state-machine bypass, race conditions and TOCTOU, replay, and abuse of coupons/refunds/limits. Requires understanding what the app is supposed to do.
Timovi QA Engineer
49theminimalcreator/timovi
QA Engineer for the Timovi project. Validates framework completeness and testability with Given/When/Then criteria, edge cases, and quality risks. Use when planning tests for the framework, defining acceptance criteria for pipeline phases, analyzing edge cases in state transitions, or reviewing framework quality.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.