Frameworks, guidance, and publications for practical security architecture

Architecture

What is Architecture

A concise introduction to enterprise architecture, enterprise security architecture, and the role architecture plays in creating secure, coherent systems.

What’s inside

01

Primary source material, summaries, and references kept together

02

Downloads and supporting artefacts surfaced close to the content

03

Long-form guidance laid out for practical reading rather than promotion

What is architecture, and what does a security architect do?

Enterprise Architecture (EA) is the strategic discipline that defines the structure and operation of an organisation’s technology landscape so it aligns with business goals. Enterprise Security Architecture (ESA) is the security-focused subset of that work: the principles, controls, patterns, and processes needed to protect information and enable resilient services.

Both are blueprints. They help organisations make decisions consistently, avoid fragmented delivery, and create systems that work together over time.

The difference between EA and ESA

Enterprise Architecture

Enterprise architecture looks across the whole operating model:

  • business capabilities
  • applications and services
  • data and information flows
  • infrastructure and platforms
  • governance and operating processes

Its job is to make sure those parts support strategic outcomes instead of drifting apart.

Enterprise Security Architecture

Enterprise security architecture takes the same whole-system view but applies a security lens. It defines:

  • security principles and standards
  • risk-based control patterns
  • trust boundaries and assurance expectations
  • how security should be embedded into projects and operations

The point is not to bolt security on at the end. It is to shape how services are designed from the beginning.

An architectural analogy

The easiest analogy is building architecture.

A building architect does not just choose the paint. They understand purpose, usage, constraints, structure, flow, safety, and long-term maintainability. Security architecture works the same way in digital environments. It is not one control or one tool. It is the coherent design of the full environment.

Why this matters

Without architecture, security work becomes reactive:

  • controls get added without a clear model
  • projects solve local problems but create enterprise inconsistency
  • operations inherit brittle systems
  • business change becomes harder and more expensive

Good architecture gives teams a shared structure for making better choices. It improves traceability from business need to design decision to control implementation.

In summary

Architecture is the discipline of intentional design. Security architecture makes that design trustworthy, resilient, and aligned with risk appetite. It is as much about enabling business outcomes as it is about protection.