threat-model-assessment
NewConduct systematic security threat model assessments by analyzing code against countermeasurement requirements and generating compliance documentation with optional JIRA integration
Summary
This skill automates threat model assessments by analyzing codebases against security requirements like OWASP, GDPR, CIS Controls, and NIST.
- It generates compliance documentation and optionally creates JIRA tickets for identified risks, helping developers integrate security into their workflow without manual overhead.
Install & Usage
/plugin marketplace add <org/repo>Add the configuration to /plugin install threat-model-assessment@<marketplace>
/pluginUse Cases
Usage Examples
/threat-model-assessment analyze ./src --framework owasp --output report.md
Run a threat model assessment on the current project against GDPR and create JIRA tickets for each finding.
Check this Kubernetes deployment for CIS Controls compliance and summarize the results.
Security Audits
Frequently Asked Questions
What is threat-model-assessment?
This skill automates threat model assessments by analyzing codebases against security requirements like OWASP, GDPR, CIS Controls, and NIST. It generates compliance documentation and optionally creates JIRA tickets for identified risks, helping developers integrate security into their workflow without manual overhead.
How to install threat-model-assessment?
To install threat-model-assessment: add a marketplace (/plugin marketplace add <org/repo>), then add the config to /plugin install threat-model-assessment@<marketplace>. Finally, /plugin in Claude Code.
What is threat-model-assessment best for?
threat-model-assessment is a plugin categorized under General. It is designed for: security, documentation, threat-modeling, compliance, owasp, gdpr, cis-controls, nist. Created by Roland HuÃ.
What can I use threat-model-assessment for?
threat-model-assessment is useful for: Analyze a new microservice codebase for OWASP Top 10 vulnerabilities and generate a threat model report.; Assess an existing application against GDPR data protection requirements and document compliance gaps.; Review infrastructure-as-code templates for CIS Controls compliance and produce a remediation checklist.; Integrate threat modeling into CI/CD by scanning pull requests for security regressions and auto-creating JIRA issues.; Generate a NIST SP 800-53 compliance documentation package for a cloud-native application.; Audit third-party library usage against known vulnerabilities and update the threat model accordingly..