cyber defense toolkit
Professional cybersecurity reporting, threat modeling, and detection engineering with CVSS v4.0 validation.
$20
Works with the AI Agents you already use
cyber defense toolkit
Example session with this skill installed
I found an unauthenticated API endpoint that leaks user PII. Here is the request: GET /api/v1/users/123. Write a vulnerability report and calculate the CVSS score.
- Read your context and instructions
- Compiled the cyber defense toolkit
I have generated a vulnerability report for the unauthenticated API endpoint based on your findings. The CVSS score has been calculated using the v4.0 vector to ensure accuracy for your remediation team.
Vulnerability Research Report: Broken Access Control
| Field | Detail |
|---|---|
| Vulnerability | Unauthenticated PII Disclosure |
| Severity | High |
| CVSS v4.0 Score | 8.7 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N) |
| Affected Endpoint | GET /api/v1/users/{id} |
| MITRE ATT&CK | T1592 - Gather Victim Identity Information |
Executive Summary
A critical broken access control vulnerability was identified in the user management API. An attacker can access sensitive Personal Identifiable Information (PII) for any user by directly browsing to the endpoint without providing authentication tokens. This allows for large-scale data harvesting with minimal effort.
Technical Analysis
The endpoint /api/v1/users/ does not verify the presence or validity of a JSON Web Token (JWT) or session cookie before returning the user object.
Evidence: User was able to retrieve full profile data for ID 123 via a simple GET request in a private browser session.
- Impact: High. Disclosure of PII (email, phone, address) violates GDPR and internal privacy policies.
Remediation
- Implement Auth: Apply the
auth:requiredmiddleware to all routes under the/api/v1/users/prefix.
Identity Verification: Ensure the authenticated user ID matches the requested resource ID or possesses administrative privileges.
3. Logging: Enable audit logging for all PII access requests to monitor for past exploitation.
Next steps
- Verify the CVSS environmental metrics based on your specific network architecture.
- Review logs for the
/api/v1/users/endpoint from the last 90 days to check for anomalous volume. - Apply the recommended middleware to the staging environment for regression testing.
Connects securely to your tools. The creator never sees your data.
About this skill
Security reporting is a bottleneck for practitioners who would rather be hunting or fixing. This skill converts raw logs, pentest notes, and system diagrams into audit-ready defensive documentation. It automates the heavy lifting of report generation, threat modeling, and detection engineering while enforcing professional standards and framework accuracy.
What it does
- Vulnerability Reporting translates technical findings into pentest reports with precise CVSS v4.0 scoring and remediation steps.
- Incident Documentation generates playbooks, incident response plans, and post-incident reviews for breaches or ransomware events.
- Detection Engineering creates validated Sigma rules, Splunk SPL, KQL, or Elastic queries from log samples and threat intel.
- Threat Modeling performs STRIDE analysis on features or systems to identify architectural risks before deployment.
- Compliance Mapping aligns existing controls and evidence to ISO 27001, NIST CSF, PCI DSS, or CIS benchmarks.
How it works
- Select Workflow by identifying if the task is a report, a detection rule, a threat model, or a compliance map.
- Freshness Check verifies the latest versions of MITRE ATT&CK, NIST, or ISO frameworks to avoid stale IDs.
- Execute Template by populating standard assets with user-provided logs, notes, or code snippets.
- Validation runs Python scripts to calculate exact CVSS vectors and lint Sigma rule syntax for production readiness.
Frameworks & tools
This tool utilizes Python scripts for CVSS calculation and Sigma validation. It integrates with MITRE ATT&CK, NIST CSF, ISO 27001, PCI DSS, and common SIEM languages including KQL and SPL.
Why this beats prompting it yourself
Generic prompts often hallucinate CVSS scores or use outdated MITRE IDs that fail audits. This skill uses dedicated Python validators and a mandatory freshness check to ensure every technical claim is backed by current standards and provided evidence.
Use cases
- Convert a list of nmap and Nessus findings into a professional pentest report.
- Write a detection rule for a new TTP and validate its syntax automatically.
- Map a startup's security controls to NIST CSF for a potential enterprise client.
- Conduct a STRIDE threat model for a new cloud microservice architecture.
Known limitations
Does not generate malware, exploits, or phishing pages. Requires external verification for framework versions if web access is unavailable. All impact claims require user-provided evidence.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
No malware or exploit generation. Requires user-provided evidence for impact claims. Manual verification needed for framework versions if web access is restricted.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago