security

Guide backend security engineering from threat modeling to incident response.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Emmraan/agent-skills --skill security-emmraan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/Emmraan/agent-skills/tree/main/skills/security
Command: npx skills add https://github.com/Emmraan/agent-skills --skill security-emmraan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework for designing, implementing, and maintaining robust security for backend systems, addressing the entire security lifecycle from threat modeling to ongoing operations.

Core Features & Use Cases

  • Threat Modeling: Systematically identify and mitigate security risks.
  • Application Security: Implement secure coding practices, input validation, and injection prevention.
  • Data Protection: Ensure data confidentiality, integrity, and compliance.
  • Infrastructure & Operations: Harden infrastructure, manage secrets, and plan for incident response.
  • Use Case: Design a secure architecture for a new microservice, including threat modeling, secure API design, data encryption, and access control policies.

Quick Start

Begin by defining the system's security context and identifying its critical assets.

Frequently Asked Questions about security

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

FAQPage Schema
How do I perform threat modeling for a new backend microservice?

Threat modeling for backend microservices involves systematically identifying and mitigating security risks to ensure controls are proportional to identified threats. You define the security context, identify critical assets, and apply a threat-driven methodology to integrate proportional security controls.

What is a threat-driven security methodology for backend systems?

A threat-driven security methodology ensures that application security, data protection, and infrastructure hardening controls are strictly proportional to identified risks. This approach integrates security controls directly into the backend engineering workflow rather than applying generic checklists.

How do I design secure APIs and ensure data protection for compliance?

Designing secure APIs and ensuring data protection requires implementing secure coding practices, input validation, and injection prevention. You establish data confidentiality, integrity, and compliance by integrating access control policies and encryption into the architecture.

Can I use this approach to harden backend infrastructure and manage secrets?

Yes, you can use this approach to harden backend infrastructure and manage secrets. It encompasses infrastructure hardening, secure secret management, and incident response planning as part of a comprehensive backend security engineering lifecycle.

What is the best way to integrate incident response into backend engineering?

The best way to integrate incident response into backend engineering is treating it as part of a comprehensive security lifecycle. Operations like incident response and infrastructure hardening are planned alongside application security and data protection during system design.

Do I need prior compliance definitions to start securing a backend architecture?

No, you do not need prior compliance definitions to start securing a backend architecture. You can begin by defining the system's security context and identifying its critical assets before systematically applying threat modeling and data protection controls.