security-review-owasp-identity-propagation-patterns

Review identity propagation and trust-boundary failures across authentication and service-to-service flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers detect identity confusion, recovery bypasses, weak challenge flows, and privilege escalation risks in systems that move identity across users, services, and sessions.

Core Features & Use Cases

  • End-to-end trust review: Trace how identity proof, credential handling, and authorization decisions flow through code, configuration, tests, and documentation.
  • Attack-path focus: Prioritize account takeover, broken trust propagation, unsafe fallback paths, and client-controlled claims or headers.
  • Review example: Use this Skill to assess a login, recovery, step-up, or service-to-service handoff and identify where an attacker could impersonate another user or gain unintended privileges.

Quick Start

Ask the skill to review the relevant identity flow, component, or files and return confirmed findings, review gaps, passed checks, and an overall assessment.

Frequently Asked Questions about security-review-owasp-identity-propagation-patterns

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

FAQPage Schema
How do I review identity propagation and trust boundary failures in authentication flows?

Identity propagation review traces how identity proof, credential handling, and authorization decisions flow across users, services, and sessions to detect trust boundary failures. It requires evidence-backed analysis of code, configuration, and tests to find impersonation risks.

What security checks are needed to prevent account takeover in session-adjacent and recovery flows?

Account takeover prevention checks assess weak challenge flows, unsafe fallback paths, and client-controlled claims in recovery and session-adjacent flows. The review confirms rate limiting, step-up enforcement, and logging are present to block privilege escalation.

How does trust boundary analysis work for service-to-service authentication and authorization?

Trust boundary analysis for service-to-service flows traces identity context and privilege decisions across components. It identifies broken trust propagation and client-controlled headers that could allow an attacker to gain unintended privileges across services.

Can I use an OWASP security review to find step-up authentication bypasses in my code?

An OWASP security review can find step-up authentication bypasses by analyzing evidence of credential handling, authorization, and step-up enforcement across code and operational controls. It flags unsafe fallback paths where attackers might impersonate users.

What is the best way to detect broken trust propagation and identity confusion across trust boundaries?

Detecting broken trust propagation requires tracing identity proof and authorization decisions across trust boundaries in code, configuration, and documentation. An evidence-backed review prioritizes attack paths like account takeover and client-controlled claims.

What limitations exist when reviewing identity propagation weaknesses without runtime evidence?

Reviewing identity propagation without runtime evidence limits analysis to code, configuration, tests, and documentation. The review cannot dynamically verify rate limiting or step-up enforcement, relying on static proof of credential handling and authorization controls.