auth-authz

Audit authentication and authorization flows for login, session, and ownership controls.

83|8|Updated May 6, 2026
One-click install
npx skills add https://github.com/Q16G/aster --skill auth-authz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-authz
Source: https://github.com/Q16G/aster/tree/main/skills/code-audit/auth-authz
Command: npx skills add https://github.com/Q16G/aster --skill auth-authz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

认证授权子清单 — 逐项排查登录语义、Cookie/Session 鉴权、IDOR/ownership、会话安全。

Core Features & Use Cases

  • 提供固定检查项和子技能加载(如 business-logic-auth-review、session-security),在现有应用中系统化审计认证授权流程
  • 覆盖登录接口、管理接口、查询与 ownership、session/cookie 信任边界等关键领域,帮助发现授权与会话相关的安全隐患
  • 适用场景包括需要审计登录、会话管理、权限判断、资源归属检查的代码库与应用

Quick Start

Invoke the skill on a project’s authentication and authorization flow to audit login, session management, and ownership controls.

Frequently Asked Questions about auth-authz

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

FAQPage Schema
How do I audit authentication and authorization flows for IDOR and session leakage?

You audit authentication and authorization flows by applying fixed checklists to login endpoints, session lifecycles, and resource ownership validation to detect IDOR and session leakage. This process enforces systematic checks across access controls, credentials, tokens, and cookies.

What is IDOR ownership validation and when do I need to check for it in my codebase?

IDOR ownership validation verifies that users can only access resources they own. You need to check for it in codebases with user accounts and sessions to detect authorization misconfigurations where users might access other users' data through insecure query parameters.

How to review session management security for cookies and tokens in a web application?

Reviewing session management security involves auditing the session lifecycle and cookie trust boundaries to identify session leakage. You must read configuration files to verify credential storage, token generation, and session invalidation mechanisms across login endpoints.

Does this authorization auditing approach work with existing codebases that have complex business logic?

Yes, authorization auditing works with existing codebases by loading sub-skills like business-logic-auth-review and session-security. It supports systematic checks across login interfaces, management interfaces, and query ownership validation to uncover hidden security vulnerabilities.

What's the best way to detect authorization misconfigurations across login endpoints and access controls?

The best way to detect authorization misconfigurations is enforcing fixed checklists across login endpoints, session lifecycles, and access controls. This approach systematically validates resource ownership and session boundaries to uncover insecure direct object reference vulnerabilities.

Why should I run a security audit on session lifecycle and resource ownership before deployment?

Running a security audit on session lifecycle and resource ownership before deployment identifies session leakage and access control failures early. It validates trust boundaries and prevents unauthorized data access by enforcing strict checks on credentials and cookies.