security-architecture

Generate a security control matrix mapping STRIDE threats to enforcement layers.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill security-architecture-shafibabar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-architecture
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/security-architecture
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill security-architecture-shafibabar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of designing secure software architectures by providing a structured, reviewable framework that maps threats to specific, verifiable controls.

Core Features & Use Cases

  • Security Control Matrix: Automatically generates a matrix mapping STRIDE threats to specific enforcement layers and controls.
  • Zero-Trust Implementation: Provides guidance on separating transport identity (mTLS) from authorization decisions (ABAC).
  • Automated Governance: Defines the triad of attestation producers, evidence stores, and control gates to ensure security is enforced in the CI/CD pipeline.

Quick Start

Use the security-architecture skill to generate a security control matrix for the current system design based on the existing threat model.

Frequently Asked Questions about security-architecture

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

FAQPage Schema
How do I design a zero-trust security architecture for my software system?

A STRIDE threat model maps spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege risks to specific enforcement layers. It generates a security control matrix to ensure verifiable security invariants and blast-radius containment.

How do I implement automated governance for security controls in a CI/CD pipeline?

Automated governance is implemented by defining a triad of attestation producers, evidence stores, and control gates. This enforces continuous control monitoring and verifies security invariants directly within the software deployment pipeline.

What is the best way to separate transport identity from authorization in secure systems?

The best way to separate transport identity from authorization is implementing zero-trust principles using mTLS for transport identity and ABAC for authorization decisions. This ensures continuous control monitoring and blast-radius containment.

Does defense-in-depth architecture work for continuous control monitoring?

Yes, defense-in-depth architecture supports continuous control monitoring by mapping STRIDE-based threats to automated governance components. It defines attestation producers, evidence stores, and control gates to enforce verifiable security invariants across the system.

When do I need a security control matrix during system design?

You need a security control matrix during the design phase to map STRIDE threats to specific enforcement layers and controls. It provides a structured framework for verifying security invariants and ensuring blast-radius containment in zero-trust systems.