security-review-owasp-choosing-and-using-security-questions

Identify account takeover risks in security-question flows across authentication and recovery reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps security reviewers evaluate security-question flows for weaknesses that can lead to account takeover, identity confusion, or privilege escalation.

Core Features & Use Cases

  • Reviews enrollment, recovery, reset, and step-up paths for weak identity proof and fallback bypasses.
  • Traces identity and authorization context across services, headers, background jobs, and delegated actions.
  • Flags missing rate limits, notifications, audit trails, and safe failure handling in high-risk account flows.
  • Use it to assess a login recovery design, a self-service profile change flow, or a service-to-service trust boundary that relies on user identity claims.

Quick Start

Use this skill to review the attached security-question recovery flow and report any confirmed account takeover or trust-propagation weaknesses.

Frequently Asked Questions about security-review-owasp-choosing-and-using-security-questions

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

FAQPage Schema
How do I review authentication recovery flows for account takeover risks?

To review authentication recovery flows for account takeover risks, trace identity and authorization context across services, verify rate limits and audit trails, and separate confirmed issues from review gaps in security-question and step-up paths.

What security weaknesses exist in account recovery and step-up authentication flows?

Security weaknesses in account recovery and step-up authentication flows include weak identity proof, fallback bypasses, missing notifications, and inadequate rate limits that allow attackers to compromise trust boundaries and escalate privileges.

How do I trace trust boundaries across service-to-service authentication paths?

Trace trust boundaries across service-to-service authentication paths by evaluating user identity claims, background jobs, and delegated actions to ensure authorization context is preserved and verified across all privilege boundaries.

Can I assess self-service profile change flows for identity confusion vulnerabilities?

You can assess self-service profile change flows for identity confusion vulnerabilities by analyzing the identity proof mechanisms, verifying authorization context propagation, and checking for missing operational controls like audit trails.

What are the limitations of relying on security questions for account recovery?

Limitations of relying on security questions for account recovery include susceptibility to weak identity proof, fallback bypasses across trust boundaries, and missing rate limits that enable automated takeover attempts if safe failure handling is absent.