auth-sec
yaklang/hack-skills
Entry point router for authentication, authorization, sessions, and identity protocol testing.
What is auth-sec?
This is a routing skill that helps you categorize and prioritize authentication and authorization testing. Use it first when you encounter login flows, sessions, JWT, OAuth, CORS, CSRF, or object authorization issues to decide which deeper auth skill to apply next.
- Routes authentication issues to specialized skills (login bypass, token attacks, OAuth misconfiguration, SAML, CSRF, CORS)
- Helps distinguish between authentication flaws, object authorization (IDOR), and protocol-level weaknesses
- Provides a recommended testing flow: confirm auth model → check object/function authorization → test tokens and cross-origin → handle enterprise federation
- Maps seven related auth security domains with links to dedicated skills
How to install auth-sec
npx skills add https://github.com/yaklang/hack-skills --skill auth-secHow to use auth-sec
- 1.Identify the authentication mechanism in the target (login, JWT, OAuth, SAML, sessions, etc.)
- 2.Confirm whether the issue is authentication (who you are), authorization (what you can do), or protocol-level (token/cross-origin)
- 3.Use the Skill Map to select the appropriate deeper skill: authbypass, IDOR, JWT/OAuth, OAuth/OIDC, CSRF, CORS, or SAML
- 4.Follow the Recommended Flow: auth model → object authorization → tokens/cross-origin → enterprise federation if applicable
Use cases
- You discover a login mechanism and need to decide whether to test bypass, brute-force, or 2FA weaknesses
- An API returns user data and you need to determine if it's an authentication bypass or object authorization (IDOR) flaw
- You find a JWT or OAuth token and need to choose between algorithm confusion, key trust, or misconfiguration testing
- A web app has cross-origin requests and you need to assess CORS vs. CSRF vs. SameSite cookie issues
- An enterprise app uses SSO and you need to route to OAuth/OIDC or SAML assertion testing
- Security testers and penetration testers starting auth assessments
- Developers building login and authorization systems
- API security auditors deciding which auth flaw category applies
auth-sec FAQ
Use this router first if you're unsure whether the issue is authentication bypass, object authorization, token manipulation, or cross-origin misconfiguration. It helps you avoid testing the wrong category and ensures you follow a logical testing sequence.
Authentication verifies who you are (login, sessions, tokens). Authorization checks what you can do (object permissions, function access). This skill helps you test both in the right order.
This is a routing and decision-making skill. It points you to seven specialized skills that contain the actual testing techniques and exploits for each auth category.
Follow the Recommended Flow: confirm the auth model first, then check object authorization, then move to token and cross-origin details. You may need to apply multiple specialized skills in sequence.
Full instructions (SKILL.md)
Source of truth, from yaklang/hack-skills.
name: auth-sec description: >- Entry P1 category router for authentication and authorization. Use when testing login flows, sessions, object authorization, JWT, OAuth, CORS, CSRF, and enterprise SSO weaknesses before any deeper auth topic skill.
Authentication and Authorization Router
This is the routing entry point for authentication, sessions, and authorization boundaries.
Use it to decide whether the issue is mainly login mechanics, object-level authorization, browser trust boundaries, or identity protocols such as OAuth/JWT/SAML before going deeper.
When to Use
- The target includes login, registration, password reset, 2FA, sessions, JWT, OAuth, or SSO
- You suspect object authorization flaws, cross-tenant access, cross-origin reads, CSRF, or protocol misconfiguration
- You need to decide whether to test authentication or authorization first
Skill Map
- Authentication Bypass: login bypass, password reset, 2FA, enumeration, brute-force protections
- IDOR Broken Object Authorization: IDOR, BOLA, BFLA, missing object permissions
- JWT OAuth Token Attacks: algorithm confusion, key trust issues, claim abuse, token forgery
- OAuth OIDC Misconfiguration: redirect URI, state, nonce, PKCE, account binding
- CSRF Cross Site Request Forgery: CSRF tokens, SameSite, JSON CSRF, login CSRF
- CORS Cross Origin Misconfiguration: reflected Origin, credentialed cross-origin reads, allowlist bypass
- SAML SSO Assertion Attacks: assertion wrapping, signature validation, audience, ACS boundaries
Recommended Flow
- First confirm the authentication model and session boundaries
- Then confirm object-level and function-level authorization
- Then move to token, cross-origin, and protocol details
- If enterprise federation exists, continue with OAuth, OIDC, or SAML topics
Related Categories
- api-sec
- Default credentials, username variants, wordlist sizing, and port focus are consolidated in authbypass-authentication-flaws
Related skills
More from yaklang/hack-skills and the wider catalog.
authbypass-authentication-flaws
Authentication bypass testing playbook for login flows, password reset, MFA, and token flaws.
binary-protection-bypass
Identify and bypass ASLR, PIE, NX, canary, RELRO, FORTIFY_SOURCE, CET, and MTE protections in ELF binaries.
browser-exploitation-v8
V8 and Chrome browser exploitation: JIT type confusion, sandbox bypass, and renderer RCE techniques.
business-logic-vuln
Router for business logic vulnerabilities including race conditions, workflow abuse, and state-machine flaws.
business-logic-vulnerabilities
Identify business logic flaws: race conditions, price manipulation, workflow bypasses, and state machine attacks invisible to scanners.
classical-cipher-analysis
Identify and break classical ciphers using frequency analysis, Kasiski examination, and cryptanalysis techniques.