auth-sec

Map authentication and authorization test scope for web and API targets.

1.6k|204|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/yaklang/hack-skills --skill auth-sec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-sec
Source: https://github.com/yaklang/hack-skills/tree/main/skills/auth-sec
Command: npx skills add https://github.com/yaklang/hack-skills --skill auth-sec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a concise routing and decision layer for authentication and authorization testing so practitioners can quickly determine which deeper auth topics to run next. It eliminates guesswork when targets expose mixed authentication mechanisms (login flows, sessions, tokens, SSO) and when it's unclear whether issues are authentication, authorization, or protocol misconfiguration.

Core Features & Use Cases

  • Decision Router: Helps triage whether to start with login/session testing, object-level authorization, token analysis (JWT/OAuth), or SSO/OIDC/SAML reviews.
  • Skill Map Linking: Direct links to focused skills for Auth Bypass, IDOR/BOLA, JWT/OAuth attacks, CSRF, CORS, and SAML assertion analysis.
  • Recommended Flow: Walks through confirming the auth model, verifying session boundaries, checking object permissions, then drilling into tokens and protocol details.
  • Use Case: During reconnaissance of a web app that includes both credentialed login and an SSO federation, use this router to pick the correct downstream tests and avoid wasted effort.

Quick Start

Classify the target authentication model and recommend whether to prioritize login/session testing, object authorization checks, token/protocol audits, or SSO assessments.

Frequently Asked Questions about auth-sec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine if a web app vulnerability is an authentication or authorization issue?

Map the target application's authentication and authorization test scope to classify whether issues reside in login flows, session management, object authorization, tokens, or SSO. This decision routing isolates the exact vulnerability category.

What is the best way to start testing JWT and OAuth token security?

The best way to start testing JWT and OAuth token security is to first confirm the target's authentication model and verify session boundaries. You then route to focused token analysis skills to drill into protocol misconfigurations and assertion vulnerabilities.

How do I prioritize IDOR and BOLA tests during API reconnaissance?

Prioritize IDOR and BOLA tests during API reconnaissance by first confirming the authentication model and verifying session boundaries. You then check object permissions and user-role access patterns to determine whether object-level authorization issues exist.

Can I use this approach for SSO and SAML federation security assessments?

Yes, you can use this approach for SSO and SAML federation security assessments. The routing layer evaluates SSO federation targets to determine if issues are protocol misconfigurations or authentication flaws, recommending targeted downstream SSO assessments.

When should I test for CORS and CSRF vulnerabilities in web applications?

Test for CORS and CSRF vulnerabilities in web applications after confirming the authentication model and verifying session boundaries. This ensures you accurately identify protocol misconfigurations related to session handling and cross-origin requests.