architecting-security

Name: architecting-security
Author: ancoleman

55installs59forks

How to install architecting-security?

ancoleman/ai-design-components/architecting-security

$npx -y skills add ancoleman/ai-design-components --skill architecting-security

Installs into the current project.

Summary

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 se

Files · 1

View on GitHub

SKILL.md

1	# Security Architecture
2
3	Design and implement comprehensive security architectures that protect systems, data, and users through layered defense strategies, zero trust principles, and risk-based security controls.
4
5	## Purpose
6
7	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).
8
9	Unlike tactical security skills (configuring firewalls, implementing authentication, scanning vulnerabilities), security architecture focuses on strategic planning, comprehensive defense strategies, and governance frameworks.
10
11	## When to Use This Skill
12
13	Use security architecture when:
14
15	- Designing security for greenfield systems (new applications, cloud migrations)
16	- Conducting security audits or risk assessments of existing systems
17	- Implementing zero trust architecture across enterprise environments
18	- Establishing security governance programs and compliance frameworks
19	- Threat modeling applications, APIs, or microservices architectures
20	- Selecting and mapping security controls to regulatory requirements (SOC 2, HIPAA, PCI DSS)
21	- Designing cloud security architectures (AWS, GCP, Azure multi-account strategies)
22	- Addressing supply chain security (SLSA framework, SBOM implementation)
23
24	## Core Security Architecture Principles
25
26	### 1. Defense in Depth
27
28	Implement multiple independent layers of security controls so that if one layer fails, others continue to protect critical assets.
29
30	9 Defense Layers (2025 Model):
31
32	1. Physical Security: Data center access, environmental controls, hardware security modules (HSMs)
33	2. Network Perimeter: Next-gen firewalls (NGFW), DDoS protection, web application firewalls (WAF)
34	3. Network Segmentation: VLANs, VPCs, security groups, micro-segmentation
35	4. Endpoint Protection: EDR, antivirus, device encryption, patch management
36	5. Application Layer: Secure coding, WAF, API security, SAST/DAST scanning
37	6. Data Layer: Encryption (at-rest, in-transit, in-use), DLP, backup/recovery
38	7. Identity & Access Management: MFA, SSO, RBAC/ABAC, privileged access management (PAM)
39	8. Behavioral Analytics: UEBA, ML-based anomaly detection, threat intelligence
40	9. Security Operations: SIEM, SOAR, incident response, continuous monitoring
41
42	Key Principle: Each layer provides independent protection. Failure of one layer does not compromise the entire system.
43
44	For detailed layer-by-layer implementation patterns, see `references/defense-in-depth.md`.
45
46	### 2. Zero Trust Architecture
47
48	Implement "never trust, always verify" principles where every access request is authenticated, authorized, and continuously validated.
49
50	Core Zero Trust Principles:
51
52	1. Continuous Verification: Authenticate and authorize every access request (no implicit trust)
53	2. Least Privilege Access: Grant minimal permissions required, use just-in-time (JIT) access
54	3. Assume Breach: Design systems expecting compromise, limit blast radius
55	4. Explicit Verification: Verify user identity (MFA), device health, application integrity, context (location, time, behavior)
56	5. Micro-Segmentation: Divide networks into small isolated zones, control east-west traffic
57
58	Zero Trust Architecture Components:
59
60	- Policy Engine: Centralized authorization decision point (allow/deny)
61	- Identity Provider (IdP): User/machine identity verification (Azure AD, Okta)
62	- Device Posture Service: Device health checks (MDM, EDR integration)
63	- Context/Risk Engine: Behavioral analytics, location, time, threat intelligence
64	- Policy Enforcement Points: Gateways enforcing decisions (ZTNA, API gateways)
65
66	For zero trust implementation roadmap and reference architecture, see `references/zero-trust-architecture.md`.
67
68	### 3. Threat Modeling
69
70	Systematically identify, prioritize, and mitigate security threats through structured methodologies.
71
72	Primary Methodologies:
73
74	\| Methodology \| Purpose \| Complexity \| Best For \|
75	\|-------------\|---------\|------------\|----------\|
76	\| STRIDE \| Threat identification \| Low \| Development teams, quick threat analysis \|
77	\| PASTA \| Risk-centric analysis \| High \| Enterprise risk management \|
78	\| DREAD \| Risk scoring \| Low \| Prioritizing existing threats \|
79	\| Attack Trees \| Visual threat analysis \| Medium \| Security architecture reviews \|
80
81	STRIDE Threat Categories:
82
83	- Spoofing: Attacker impersonates another user/system (Mitigation: MFA, certificate validation)
84	- Tampering: Unau

People who liked this also viewed

6 picks

Type

architecting-security

55installs59forks

View on GitHub

How to install architecting-security?

ancoleman/ai-design-components/architecting-security

$npx -y skills add ancoleman/ai-design-components --skill architecting-security

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Security Architecture
2
3	Design and implement comprehensive security architectures that protect systems, data, and users through layered defense strategies, zero trust principles, and risk-based security controls.
4
5	## Purpose
6
7	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).
8
9	Unlike tactical security skills (configuring firewalls, implementing authentication, scanning vulnerabilities), security architecture focuses on strategic planning, comprehensive defense strategies, and governance frameworks.
10
11	## When to Use This Skill
12
13	Use security architecture when:
14
15	- Designing security for greenfield systems (new applications, cloud migrations)
16	- Conducting security audits or risk assessments of existing systems
17	- Implementing zero trust architecture across enterprise environments
18	- Establishing security governance programs and compliance frameworks
19	- Threat modeling applications, APIs, or microservices architectures
20	- Selecting and mapping security controls to regulatory requirements (SOC 2, HIPAA, PCI DSS)
21	- Designing cloud security architectures (AWS, GCP, Azure multi-account strategies)
22	- Addressing supply chain security (SLSA framework, SBOM implementation)
23
24	## Core Security Architecture Principles
25
26	### 1. Defense in Depth
27
28	Implement multiple independent layers of security controls so that if one layer fails, others continue to protect critical assets.
29
30	9 Defense Layers (2025 Model):
31
32	1. Physical Security: Data center access, environmental controls, hardware security modules (HSMs)
33	2. Network Perimeter: Next-gen firewalls (NGFW), DDoS protection, web application firewalls (WAF)
34	3. Network Segmentation: VLANs, VPCs, security groups, micro-segmentation
35	4. Endpoint Protection: EDR, antivirus, device encryption, patch management
36	5. Application Layer: Secure coding, WAF, API security, SAST/DAST scanning
37	6. Data Layer: Encryption (at-rest, in-transit, in-use), DLP, backup/recovery
38	7. Identity & Access Management: MFA, SSO, RBAC/ABAC, privileged access management (PAM)
39	8. Behavioral Analytics: UEBA, ML-based anomaly detection, threat intelligence
40	9. Security Operations: SIEM, SOAR, incident response, continuous monitoring
41
42	Key Principle: Each layer provides independent protection. Failure of one layer does not compromise the entire system.
43
44	For detailed layer-by-layer implementation patterns, see `references/defense-in-depth.md`.
45
46	### 2. Zero Trust Architecture
47
48	Implement "never trust, always verify" principles where every access request is authenticated, authorized, and continuously validated.
49
50	Core Zero Trust Principles:
51
52	1. Continuous Verification: Authenticate and authorize every access request (no implicit trust)
53	2. Least Privilege Access: Grant minimal permissions required, use just-in-time (JIT) access
54	3. Assume Breach: Design systems expecting compromise, limit blast radius
55	4. Explicit Verification: Verify user identity (MFA), device health, application integrity, context (location, time, behavior)
56	5. Micro-Segmentation: Divide networks into small isolated zones, control east-west traffic
57
58	Zero Trust Architecture Components:
59
60	- Policy Engine: Centralized authorization decision point (allow/deny)
61	- Identity Provider (IdP): User/machine identity verification (Azure AD, Okta)
62	- Device Posture Service: Device health checks (MDM, EDR integration)
63	- Context/Risk Engine: Behavioral analytics, location, time, threat intelligence
64	- Policy Enforcement Points: Gateways enforcing decisions (ZTNA, API gateways)
65
66	For zero trust implementation roadmap and reference architecture, see `references/zero-trust-architecture.md`.
67
68	### 3. Threat Modeling
69
70	Systematically identify, prioritize, and mitigate security threats through structured methodologies.
71
72	Primary Methodologies:
73
74	\| Methodology \| Purpose \| Complexity \| Best For \|
75	\|-------------\|---------\|------------\|----------\|
76	\| STRIDE \| Threat identification \| Low \| Development teams, quick threat analysis \|
77	\| PASTA \| Risk-centric analysis \| High \| Enterprise risk management \|
78	\| DREAD \| Risk scoring \| Low \| Prioritizing existing threats \|
79	\| Attack Trees \| Visual threat analysis \| Medium \| Security architecture reviews \|
80
81	STRIDE Threat Categories:
82
83	- Spoofing: Attacker impersonates another user/system (Mitigation: MFA, certificate validation)
84	- Tampering: Unau

People who liked this also viewed

6 picks

Type