Security Architecture
Security architecture defines layered defenses (network, application, data, IAM) and the integration of policies, standards, and technologies to protect assets and support risk management.
A comprehensive security architecture establishes governance, risk management, and engineering practices to protect information assets across people, processes, and technology. It spans governance and policy, reference models, and a technical stack across multiple layers: governance/policy layer; network security; application security; data security; identity and access management; endpoint and cloud security; and supply chain security. Effective architectures map controls to recognized standards (e.g., NIST SP 800-53, ISO/IEC 27001, ISO/IEC 27002, NIST SP 800-160, CSA CCM; SABSA; TOGAF) and integrate security into the software development lifecycle (secure SDLC) and threat modeling (e.g., STRIDE, PASTA). They emphasize a risk-based approach, least privilege, and defense-in-depth, with clear ownership, measurement, and continuous improvement through monitoring (SIEM, EDR, IAM analytics) and governance reviews. Architecture artifacts include reference diagrams, policy mappings, control catalogs, data classification schemes, and an ongoing program to adapt to evolving threats and regulatory requirements. Education and awareness, supply chain risk management, and incident response integration complete the architecture, ensuring alignment with business objectives and regulatory posture.
graph LR
Center["Security Architecture"]:::main
Rel_computer_architecture["computer-architecture"]:::related -.-> Center
click Rel_computer_architecture "/terms/computer-architecture"
Rel_security_automation["security-automation"]:::related -.-> Center
click Rel_security_automation "/terms/security-automation"
Rel_hardware_security["hardware-security"]:::related -.-> Center
click Rel_hardware_security "/terms/hardware-security"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 Explain Like I'm 5
Generated ELI5 content
🤓 Expert Deep Dive
Generated expert content
❓ Frequently Asked Questions
What is the purpose of a security architecture?
To provide a risk-based blueprint for selecting and implementing security controls that protect critical assets while enabling business operations, governed by policy and continuous improvement.
What frameworks or standards guide security architecture?
Common references include NIST SP 800-53, ISO/IEC 27001/27002, NIST SP 800-160, SABSA, TOGAF, and threat modeling practices (STRIDE, MITRE ATT&CK).
What are typical layers or components?
Governance/policy, network security, application security, data security, identity and access management, endpoint/cloud security, and supply chain security.
How does security architecture relate to risk management?
It translates risk-based requirements into concrete controls, aligns with risk appetite, and enables measurable security outcomes.
What is Zero Trust in this context?
A model that requires verification and least-privilege access for every resource, irrespective of location or network perimeter.