/architecting-security

name: architecting-security
description: Design comprehensive security architectures using defense-in-depth, zero trust principles, threat modeling (STRIDE, PASTA), and control frameworks (NIST CSF, CIS Controls, ISO 27001). Use when designing security for new systems, auditing existing architectures, or establishing security governance programs.

Security Architecture

Design and implement comprehensive security architectures that protect systems, data, and users through layered defense strategies, zero trust principles, and risk-based security controls.

Purpose

Security architecture provides the strategic foundation for building resilient, compliant, and trustworthy systems. This skill guides the design of defense-in-depth layers, zero trust implementations, threat modeling methodologies, and mapping to control frameworks (NIST CSF, CIS Controls, ISO 27001).

Unlike tactical security skills (configuring firewalls, implementing authentication, scanning vulnerabilities), security architecture focuses on strategic planning, comprehensive defense strategies, and governance frameworks.

When to Use This Skill

Use security architecture when:

• Designing security for greenfield systems (new applications, cloud migrations)
• Conducting security audits or risk assessments of existing systems
• Implementing zero trust architecture across enterprise environments
• Establishing security governance programs and compliance frameworks
• Threat modeling applications, APIs, or microservices architectures
• Selecting and mapping security controls to regulatory requirements (SOC 2, HIPAA, PCI DSS)
• Designing cloud security architectures (AWS, GCP, Azure multi-account strategies)
• Addressing supply chain security (SLSA framework, SBOM implementation)

Core Security Architecture Principles

1. Defense in Depth

Implement multiple independent layers of security controls so that if one layer fails, others continue to protect critical assets.

**9 Defense Layers (2025 Model):**

1. **Physical Security:** Data center access, environmental controls, hardware security modules (HSMs) 2. **Network Perimeter:** Next-gen firewalls (NGFW), DDoS protection, web application firewalls (WAF) 3. **Network Segmentation:** VLANs, VPCs, security groups, micro-segmentation 4. **Endpoint Protection:** EDR, antivirus, device encryption, patch management 5. **Application Layer:** Secure coding, WAF, API security, SAST/DAST scanning 6. **Data Layer:** Encryption (at-rest, in-transit, in-use), DLP, backup/recovery 7. **Identity & Access Management:** MFA, SSO, RBAC/ABAC, privileged access management (PAM) 8. **Behavioral Analytics:** UEBA, ML-based anomaly detection, threat intelligence 9. **Security Operations:** SIEM, SOAR, incident response, continuous monitoring

**Key Principle:** Each layer provides independent protection. Failure of one layer does not compromise the entire system.

For detailed layer-by-layer implementation patterns, see `references/defense-in-depth.md`.

2. Zero Trust Architecture

Implement "never trust, always verify" principles where every access request is authenticated, authorized, and continuously validated.

**Core Zero Trust Principles:**

1. **Continuous Verification:** Authenticate and authorize every access request (no implicit trust) 2. **Least Privilege Access:** Grant minimal permissions required, use just-in-time (JIT) access 3. **Assume Breach:** Design systems expecting compromise, limit blast radius 4. **Explicit Verification:** Verify user identity (MFA), device health, application integrity, context (location, time, behavior) 5. **Micro-Segmentation:** Divide networks into small isolated zones, control east-west traffic

**Zero Trust Architecture Components:**

• **Policy Engine:** Centralized authorization decision point (allow/deny)
• **Identity Provider (IdP):** User/machine identity verification (Azure AD, Okta)
• **Device Posture Service:** Device health checks (MDM, EDR integration)
• **Context/Risk Engine:** Behavioral analytics, location, time, threat intelligence
• **Policy Enforcement Points:** Gateways enforcing decisions (ZTNA, API gateways)

For zero trust implementation roadmap and reference architecture, see `references/zero-trust-architecture.md`.

3. Threat Modeling

Systematically identify, prioritize, and mitigate security threats through structured methodologies.

**Primary Methodologies:**

| Methodology | Purpose | Complexity | Best For | |-------------|---------|------------|----------| | **STRIDE** | Threat identification | Low | Development teams, quick threat analysis | | **PASTA** | Risk-centric analysis | High | Enterprise risk management | | **DREAD** | Risk scoring | Low | Prioritizing existing threats | | **Attack Trees** | Visual threat analysis | Medium | Security architecture reviews |

**STRIDE Threat Categories:**

• **S**poofing: Attacker impersonates another user/system (Mitigation: MFA, certificate validation)
• **T**ampering: Unauthorized data modification (Mitigation: Encryption, digital signatures)
• **R**epudiation: User denies action without proof (Mitigation: Audit logs, non-repudiation)
• **I**nformation Disclosure: Confidential data exposure (Mitigation: Encryption, access controls, DLP)
• **D**enial of Service: System unavailability (Mitigation: Rate limiting, DDoS protection, redundancy)
• **E**levation of Privilege: Gaining higher privileges (Mitigation: Least privilege, input validation, patching)

**STRIDE Application Process:**

1. Model the system using data flow diagrams (DFDs) 2. Identify threats by applying STRIDE to each component/data flow 3. Document threats with STRIDE categories 4. Prioritize threats using DREAD scoring or business impact 5. Design mitigation controls

For detailed threat modeling methodologies, PASTA process, DREAD scoring, and attack trees, see `references/threat-modeling.md`. For threat modeling examples, see `examples/threat-models/`.

Security Control Frameworks

M