security-requirement-extraction

Generates security requirements from threat models using Python templates and compliance mappings.

3|Updated Jan 18, 2026

Search Tags:#threat modeling #compliance #risk management #user stories #security automation #security requirements

Ready to run

npx skills add https://github.com/TheerasakPing/video-downloader-tauri --skill security-requirement-extraction-theerasakping

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-requirement-extraction
Source: https://github.com/TheerasakPing/video-downloader-tauri/tree/main/.crush/skills/security-requirement-extraction
Command: npx skills add https://github.com/TheerasakPing/video-downloader-tauri --skill security-requirement-extraction-theerasakping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of translating high-level threat models and business context into specific, actionable security requirements, bridging the gap between security analysis and development.

Core Features & Use Cases

Threat-to-Requirement Mapping: Automatically generates security requirements based on identified threats (e.g., STRIDE categories).
Requirement Categorization: Classifies requirements into functional, non-functional, and constraint types, and maps them to security domains.
Compliance Mapping: Links security requirements to relevant compliance frameworks like PCI-DSS, HIPAA, and GDPR.
Use Case: After a threat modeling session identifies a "Denial of Service" threat against the user authentication service, this Skill can generate requirements like "Implement rate limiting for the authentication API" and map it to relevant OWASP categories.

Quick Start

Use the security-requirement-extraction skill to generate security requirements from a list of threats.

Frequently Asked Questions about security-requirement-extraction

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

FAQPage Schema

How do I generate actionable security requirements from a threat model?▼

To generate security requirements from a threat model, you map identified threats like STRIDE categories to specific actionable controls. This process translates high-level security analysis into structured functional and non-functional requirements for development teams.

How do I map security requirements to compliance frameworks like PCI-DSS, HIPAA, and GDPR?▼

Security requirements mapping links derived security controls to relevant compliance frameworks like PCI-DSS, HIPAA, and GDPR. This ensures generated security user stories and test cases automatically align with necessary regulatory obligations.

Can I automate creating security user stories and test cases from identified threats?▼

Yes, you can automate creating security user stories and test cases from identified threats. By using Python templates and structured mappings, threat scenarios like Denial of Service are translated directly into actionable development tasks.

How are derived security requirements categorized for software engineering teams?▼

Derived security requirements are categorized into functional, non-functional, and constraint types. They are further structured into security domains using defined Python classes to clarify implementation scope for engineering teams.

What is the best way to turn STRIDE threat modeling results into development tasks?▼

The best way to turn STRIDE threat modeling results into development tasks is using security requirement extraction. This approach systematically converts threat categories into specific implementation rules like API rate limiting.

Do I need prior threat modeling results to extract security requirements?▼

Yes, you need prior threat modeling results and business context as input. The extraction process relies on identified threats to automatically derive and categorize the corresponding security requirements.