security-requirement-extraction

Generate security requirements, user stories, and test cases from STRIDE threat models using Python templates and mappings.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/nonputtipong/Oryn --skill security-requirement-extraction-nonputtipong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-requirement-extraction
Source: https://github.com/nonputtipong/Oryn/tree/main/.agent/skills/security-requirement-extraction
Command: npx skills add https://github.com/nonputtipong/Oryn --skill security-requirement-extraction-nonputtipong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the translation of identified security threats into actionable security requirements, user stories, and test cases, streamlining the security design and development process.

Core Features & Use Cases

  • Threat-to-Requirement Mapping: Automatically generates security requirements based on threat models (e.g., STRIDE).
  • User Story Generation: Creates security-focused user stories from requirements.
  • Test Case Creation: Develops initial test cases and acceptance criteria for requirements.
  • Compliance Mapping: Assists in mapping requirements to common compliance frameworks.
  • Use Case: After a threat modeling session identifies a "Tampering" threat against user data, this Skill can generate requirements like "Validate all input to user data storage" and "Implement integrity checks for user data," along with corresponding user stories and test cases.

Quick Start

Use the security-requirement-extraction skill to generate security requirements from the provided threat model data.

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 security requirements from a STRIDE threat model?

To generate security requirements from a STRIDE threat model, provide your threat data and business context to automatically derive actionable security controls, user stories, and test cases using defined templates.

Can I automatically create security user stories and test cases from identified threats?

Yes, you can automatically create security user stories and test cases from identified threats by translating the threat model into structured security requirements and corresponding acceptance criteria.

Does this approach support compliance mapping for generated security requirements?

Yes, this approach supports compliance mapping by assisting in mapping the generated security requirements directly to common compliance frameworks alongside your security architecture documentation.

What is the best way to translate a threat like tampering into actionable security controls?

The best way to translate a tampering threat into actionable security controls is to use automated threat-to-requirement mapping, which generates specific validations and integrity checks from your threat data.

Do I need Python to derive security requirements from threat modeling data?

Yes, you need Python to derive security requirements from threat modeling data, as the translation of threats into structured security controls and test cases is implemented via Python scripts.