security-review-owasp-transaction-authorization

Analyze transaction authorization flows for security weaknesses against OWASP guidance.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-transaction-authorization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review-owasp-transaction-authorization
Source: https://github.com/sjinks/ai-owasp-skillset/tree/main/.github/skills/security-review-owasp-transaction-authorization
Command: npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-transaction-authorization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers assess transaction authorization flows for weak identity proof, broken trust propagation, recovery bypasses, and privilege escalation risks.

Core Features & Use Cases

  • Security Review Guidance: Evaluates code, configuration, tests, and documentation for account takeover, identity confusion, and authorization failures.
  • Flow and Trust Boundary Analysis: Traces credentials, session-adjacent steps, step-up checks, and service-to-service identity context end to end.
  • Finding Prioritization: Focuses on confirmed weaknesses with concrete evidence and separates them from review gaps when controls are not visible.
  • Use Case: A reviewer can inspect authentication, recovery, and delegated action workflows to determine whether an attacker could impersonate another user or bypass a critical authorization step.

Quick Start

Ask this skill to review the relevant transaction authorization flow, component, or file set and return confirmed findings with evidence, review gaps, passed checks, and an overall assessment.

Frequently Asked Questions about security-review-owasp-transaction-authorization

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

FAQPage Schema
How do I review transaction authorization flows for account takeover and privilege escalation risks?

To review transaction authorization flows for account takeover and privilege escalation risks, analyze identity proof, authorization decisions, and failure handling against OWASP guidance. This process evaluates code, configuration, tests, and documentation to identify weak trust propagation and recovery bypass vulnerabilities.

What is trust boundary analysis in security review and how does it prevent identity confusion?

Trust boundary analysis in security review traces credentials, session-adjacent steps, and service-to-service identity context end to end to prevent identity confusion. It evaluates step-up checks and trust propagation across authentication and delegated action workflows to detect authorization bypasses.

How do I perform an evidence-based security review of authentication and recovery workflows?

Perform an evidence-based security review of authentication and recovery workflows by inspecting code, configuration, and operational controls for confirmed weaknesses. Separate concrete findings with evidence from review gaps where controls are not visible during the authorization decision evaluation.

Does this security review approach work for step-up authentication and delegated action scenarios?

Yes, this security review approach works for step-up authentication and delegated action scenarios by evaluating trust propagation and identity proof across trust boundaries. It assesses whether an attacker could impersonate another user or bypass critical authorization steps in these workflows.

What is the best way to prioritize security findings when reviewing transaction authorization mechanisms?

The best way to prioritize security findings when reviewing transaction authorization mechanisms is to focus on confirmed weaknesses with concrete evidence. Separate these critical findings from review gaps where controls are not visible, and document passed checks for overall assessment clarity.

When should I not rely on a transaction authorization security review?

You should not rely solely on a transaction authorization security review when operational controls or configuration details are not visible. In such cases, the review yields review gaps rather than confirmed findings, requiring additional evidence gathering for complete privilege escalation and account takeover assessment.