Works with the AI Agents you already use
Identity Penetration Testing
Prove a privilege or tenant boundary can be crossed minimally, with authorization
$22
Identity Penetration Testing
Example session with this skill installed
Authorized identity boundary test. Objective: determine whether a standard user in Tenant A can access Tenant B's billing settings. Use controlled test identities only. Stop when the boundary is proven or refuted.
- Read your context and instructions
- Compiled the identity penetration testing
Identity Boundary Record
OBJECTIVE
Determine whether a controlled standard user from Tenant A can cross the tenant boundary into Tenant B's billing settings.
EXECUTION CLASSIFICATION
- Authorization: supplied for the synthetic scenario.
- Starting principal: controlled Tenant A standard user.
- Target boundary: Tenant B billing administration.
- Real external execution: none.
- Evidence status: SYNTHETIC / ILLUSTRATIVE.
START CONDITION
Tenant A standard user has a valid session and no administrative privileges.
BASELINE
The starting principal is expected to access only Tenant A resources.
BOUNDARY TEST
A minimal cross-tenant access attempt is modeled using Tenant B as the target context while preserving the Tenant A identity.
SYNTHETIC OUTCOME
The worked example demonstrates how the skill would classify whether the server-side authorization boundary rejects or permits the transition.
VERDICT
No real-world vulnerability is claimed from this demo. A live verdict requires observable evidence from an explicitly authorized target.
STOP CONDITION
Testing ends immediately once the named tenant boundary is proven or refuted.
EXCLUDED ACTIONS
No credential guessing, password spraying, phishing, attacks against real users, destructive account changes, or unrelated privilege exploration.
NEXT STEP
For real execution, provide explicit authorization, the controlled test identities, target environment, permitted actions, and the exact boundary to validate.
Connects securely to your tools. The creator never sees your data.
About this skill
An authorized, objective-driven identity penetration test that attempts the smallest boundary transition needed to prove a defined escalation objective from a known starting principal. It focuses on privilege escalation, cross-tenant access, session/token replay, and authorization-boundary failures while enforcing an explicit authorization gate and hard stop condition.
What it does
- Privilege-boundary testing from a defined starting identity or role.
- Cross-tenant isolation testing to determine whether one tenant can reach another tenant's protected resources or actions.
- Session and token boundary validation for replay, scope confusion, and unsafe privilege transitions.
- Horizontal and vertical authorization testing using controlled test identities.
- Minimal proof construction that stops as soon as the agreed escalation objective is demonstrated.
- Evidence-backed reporting that separates observed runtime evidence from hypotheses and missing inputs.
How it works
- Authorization and scope gate confirms the permitted target, identities, actions, and stop condition.
- Starting-principal definition establishes the exact user, role, tenant, or token from which testing begins.
- Baseline verification records what that principal is legitimately allowed to access.
- Boundary transition probes test the smallest relevant privilege, tenant, session, or token transition.
- Impact proofing records only the evidence required to establish whether the named boundary can be crossed.
- Hard stop ends active testing as soon as the agreed objective is proven or cannot be established within scope.
Boundaries
API-surface campaigns whose primary objective is API exploitation route to api-penetration-testing. Browser-oriented multi-vector intrusion objectives route to web-penetration-testing. Read-only authentication and authorization architecture review routes to identity-access-review. A single documented vulnerability that only needs exploitability confirmation routes to exploit-validation.
Credential stuffing, phishing, attacks against real users, destructive account actions, password spraying, and activity outside explicit authorization are excluded by design.
Why this beats prompting it yourself
Generic identity-security prompts can blur the difference between review and active penetration testing, expand into credential attacks, or keep testing after the required boundary has already been proven. This skill fixes the starting principal, target boundary, authorization scope, evidence requirements, and stop condition before active testing proceeds.
Validation
Routing boundary stress-tested in isolated Antigravity sessions — 5/5 high-risk negative cases kept identity-penetration-testing OFF with zero false triggers.
Use cases
- Prove whether a standard user can reach an administrator-only capability.
- Test whether one controlled tenant identity can cross into another tenant's protected resources.
- Validate a suspected unsafe session or token replay path.
- Demonstrate a horizontal or vertical authorization failure with the smallest sufficient proof.
- Verify whether an identity-boundary weakness produces the agreed impact without expanding the engagement.
Known limitations
Requires explicit user-supplied authorization, defined test identities, target scope, and engagement boundaries before active execution. Runtime findings require observable evidence from the authorized environment. Missing execution evidence remains BLOCKED or UNVERIFIED rather than being treated as a confirmed finding.
Part of JetFerrari Security Engineering.
Active identity testing requires explicit authorization, defined principals, target boundaries, and an agreed escalation or access objective. The skill does not perform credential stuffing, phishing, social engineering, or attacks against real users. Broader authentication and authorization review without an active intrusion objective belongs to identity access review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 25 days ago
Permissions
Project and target access are task-scoped. Active testing requires explicit user-supplied authorization, controlled test identities, and defined scope. Credentials or tokens must be supplied only for the authorized test environment. The skill does not harvest environment variables, perform credential stuffing, phish users, or modify unrelated project artifacts.