security-team

Performs threat modeling, incident response, compliance assessment, and vendor security review for early-stage companies.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill security-team-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-team
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/security-team
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill security-team-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Early-stage companies face security risks that live above any single code change — unrevoked access, unvetted vendors, unhardened cloud accounts, and no plan for the day something goes wrong. This Skill provides the proactive security function: threat modeling, incident response, compliance readiness, and identity/vendor/cloud risk management, grounded in the actual system rather than generic boilerplate. ## Core Features & Use Cases - Threat Modeling: STRIDE-based analysis of a system's real data flows and trust boundaries, producing prioritized findings handed to engineering as concrete requirements. - Incident Response: A practical playbook covering triage, containment, evidence preservation, confirmed-vs-suspected tracking, and blameless post-incident review, aligned with current NIST guidance. - Compliance & Audits: Gap analyses against SOC 2, ISO 27001, and OWASP's current Top 10, with prioritized remediation roadmaps. - Vendor & Access Risk: Pre-integration vendor due diligence, least-privilege onboarding/offboarding checklists, and cloud account hardening (MFA, root protection, billing anomaly alerts). - Use Case: Before integrating a new AI vendor that will touch customer data, run a vendor assessment covering actual data access scope, retention, DPA requirements, and a proceed/conditions/don't-integrate recommendation. ## Quick Start Ask the security team to threat-model your new feature or audit your cloud account security posture, for example: "Threat-model our patient data API before launch."

Frequently Asked Questions about security-team

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

FAQPage Schema
How do I threat-model a new feature before building it?

Use the /threat-model command with the feature name. It maps the system's data flows and trust boundaries, applies the STRIDE categories against real components, and prioritizes findings by likelihood and impact, handing concrete requirements to engineering.

What is the difference between SOC 2 and ISO 27001 for a startup?

SOC 2 is a flexible attestation against Trust Services Criteria, common for US-market SaaS, with Type II showing sustained operation. ISO 27001 builds a formal information security management system and suits international customers. The /comply command assesses readiness for either.

How should a small team respond to a security incident?

The /incident command activates a playbook: confirm and scope the incident, contain damage first, track facts as confirmed versus suspected, preserve evidence, and loop in legal immediately if personal data may be involved due to notification deadlines.

Does this replace a professional security audit or penetration test?

No. It assesses posture, builds gap analyses, and prepares remediation roadmaps, but actual SOC 2 or ISO 27001 certification requires a licensed external auditor, and serious incidents need a professional incident-response firm.

How do I check if a vendor is safe to integrate?

Use the /vendor command with the service name. It evaluates what data the vendor can actually access, where data is stored and retained, the vendor's certifications and track record, and whether a Data Processing Agreement is needed before connecting.