Skip to content

Enterprise Security Architecture

Learning Path

πŸ“˜ Phase 1 – Overview


By the end of this lesson, you will be able to:

  • Understand Enterprise Security Architecture (ESA).
  • Learn how organisations design secure cloud environments.
  • Understand the principles of Defence in Depth and Zero Trust.
  • Identify the different layers of enterprise security.
  • Learn where Cloud Security Engineers fit within an enterprise architecture.
  • Understand how AWS security services work together to protect cloud workloads.

πŸ“š Lesson Information

Estimated Time: 2.5 Hours

Difficulty: Beginner

Prerequisites: Enterprise Cloud Architecture

Hands-on Lab: Yes

Assignment: Yes


Large organisations don’t rely on a single security product.

Instead, they build multiple security layers so that if one control fails, another continues protecting the business.

Enterprise Security Architecture is the blueprint that ensures people, processes, technology and cloud services work together to protect business assets.

A Cloud Security Engineer spends much of their time designing, implementing and improving this architecture.


Enterprise Security Architecture (ESA) is the structured design of security controls that protect an organisation’s:

  • People
  • Applications
  • Data
  • Networks
  • Cloud Infrastructure
  • Devices
  • Identities
  • Business Processes

It provides a consistent security framework across the entire organisation.

Think of it as the security blueprint for the company.


CloudNova Technologies operates:

  • Customer Portal
  • Internal HR Application
  • Finance Systems
  • Kubernetes Platform
  • AWS Production Environment
  • AWS Development Environment
  • Remote Workforce
  • Third-party SaaS Applications

Every system must work together securely.

Instead of securing each application independently, CloudNova creates one Enterprise Security Architecture that defines how security should be implemented across the business.


Security exists at multiple layers.

Users
β”‚
β–Ό
Identity Security
β”‚
β–Ό
Endpoint Security
β”‚
β–Ό
Network Security
β”‚
β–Ό
Application Security
β”‚
β–Ό
Platform Security
β”‚
β–Ό
Data Security
β”‚
β–Ό
Monitoring & Detection
β”‚
β–Ό
Incident Response
β”‚
β–Ό
Business Continuity

If one layer fails, another layer continues protecting the organisation.


Defence in Depth means using multiple security controls instead of relying on a single control.

Example:

A production web application might use:

  • MFA
  • IAM Policies
  • Security Groups
  • Network ACLs
  • AWS WAF
  • AWS Shield
  • Encryption
  • CloudTrail
  • GuardDuty
  • Security Hub

Even if one control is bypassed, others continue protecting the environment.


Traditional security assumed that anything inside the corporate network was trusted.

Zero Trust follows a different principle:

Never Trust. Always Verify.

Every request must be:

  • Authenticated
  • Authorised
  • Logged
  • Continuously evaluated

Examples:

  • MFA required for administrators.
  • Device health verification.
  • Least Privilege IAM.
  • Conditional access policies.
  • Continuous monitoring.

Zero Trust reduces the impact of compromised credentials.


Identity is the first security layer.

Controls include:

  • IAM
  • IAM Roles
  • IAM Policies
  • MFA
  • Identity Center (SSO)
  • Federation
  • Password Policies
  • Access Reviews

Identity determines who can access enterprise resources.


Network security protects communication between systems.

Typical controls include:

  • VPC
  • Subnets
  • Security Groups
  • Network ACLs
  • AWS Network Firewall
  • VPN
  • Transit Gateway
  • PrivateLink
  • Route Tables

The objective is to minimise unnecessary network exposure.


Enterprise workloads run on:

  • EC2
  • Containers
  • Kubernetes
  • Lambda

Security controls include:

  • Patch Management
  • Hardened Images
  • Endpoint Protection
  • Secure AMIs
  • Vulnerability Scanning
  • Runtime Monitoring

Data is the organisation’s most valuable asset.

Controls include:

  • Encryption
  • AWS KMS
  • S3 Bucket Policies
  • Backup
  • Versioning
  • Data Classification
  • Access Logging

Security Engineers focus on protecting data throughout its lifecycle.


Applications should be secure by design.

Controls include:

  • Secure Development Lifecycle (SDLC)
  • Static Code Analysis (SAST)
  • Dynamic Testing (DAST)
  • Dependency Scanning
  • Secrets Management
  • API Security
  • Input Validation

Security begins during software development.


Security architecture includes continuous monitoring.

AWS services include:

  • CloudTrail
  • CloudWatch
  • GuardDuty
  • Inspector
  • Security Hub
  • AWS Config
  • Detective

These services provide visibility into cloud activity and help detect threats.


Every architecture must include an incident response capability.

Preparation includes:

  • Incident Response Plan
  • Playbooks
  • Logging
  • Backup
  • Recovery Procedures
  • Communication Plan

The goal is to minimise business disruption.


Security architecture must ensure business resilience.

Key concepts:

  • High Availability
  • Fault Tolerance
  • Backup
  • Disaster Recovery
  • Multi-AZ Deployments
  • Multi-Region Architecture

Business continuity is as important as preventing attacks.


A simplified AWS enterprise security architecture:

Internet
β”‚
AWS Shield + AWS WAF
β”‚
Application Load Balancer
β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ β”‚
Public Subnet Public Subnet
β”‚ β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
Private Subnets
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ β”‚
EC2 / EKS Lambda
β”‚ β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
Database Tier
(Amazon RDS)
β”‚
AWS KMS Encryption
β”‚
Backup & Monitoring
β”‚
CloudTrail β€’ GuardDuty β€’ Config β€’ Security Hub

Every layer has dedicated security controls.


πŸ‘¨β€πŸ’Ό Role of a Cloud Security Engineer

Section titled β€œπŸ‘¨β€πŸ’Ό Role of a Cloud Security Engineer”

A Cloud Security Engineer is responsible for:

  • Designing secure cloud architectures.
  • Reviewing IAM permissions.
  • Implementing encryption.
  • Managing Security Groups.
  • Monitoring security events.
  • Supporting incident response.
  • Conducting security reviews.
  • Performing compliance checks.
  • Advising development teams.
  • Improving security posture continuously.

Security Engineers work across every layer of the architecture.


CloudNova plans to launch a new customer-facing application.

The proposed architecture includes:

  • Public EC2 instance hosting both the web application and database.
  • Shared administrator account.
  • No MFA.
  • Public S3 bucket storing customer invoices.
  • No logging enabled.
  • No backups.
  • No monitoring.
  • No Web Application Firewall.
  • Database accessible from the internet.

As the Cloud Security Engineer:

  1. Identify every security weakness.
  2. Recommend architectural improvements.
  3. Which AWS services would you implement?
  4. How would Defence in Depth improve the design?
  5. How would Zero Trust principles change this architecture?

πŸ§ͺ Hands-on Exercise 1 β€” Explore AWS Security Services

Section titled β€œπŸ§ͺ Hands-on Exercise 1 β€” Explore AWS Security Services”

Navigate to:

AWS Console

Locate:

  • IAM
  • VPC
  • Security Groups
  • CloudTrail
  • GuardDuty
  • Security Hub
  • AWS Config
  • AWS WAF
  • AWS Shield
  • AWS Backup

Questions:

  • What role does each service play in the enterprise architecture?
  • Which layer does each service protect?

Complete the table below.

Security Layer AWS Service
Identity IAM
Network
Compute
Data
Monitoring
Backup
Threat Detection

Discuss your answers with your mentor or classmates.


πŸ§ͺ Hands-on Exercise 3 β€” Defence in Depth Review

Section titled β€œπŸ§ͺ Hands-on Exercise 3 β€” Defence in Depth Review”

For the following scenario, identify at least three security controls.

Scenario Controls
Public web application
Amazon RDS database
IAM Administrator
Customer data in S3

Questions:

  • Which control prevents attacks?
  • Which control detects attacks?
  • Which control supports recovery?

πŸ§ͺ Hands-on Exercise 4 β€” Zero Trust Assessment

Section titled β€œπŸ§ͺ Hands-on Exercise 4 β€” Zero Trust Assessment”

Review the following requirements.

  • Developer working remotely.
  • Accessing production AWS account.
  • Using personal laptop.
  • Wants AdministratorAccess.

Answer:

  • Should access be granted?
  • What additional controls are required?
  • How would you verify the user and device?
  • How would you apply Least Privilege?

πŸ§ͺ Hands-on Exercise 5 β€” Build Your Enterprise Security Architecture

Section titled β€œπŸ§ͺ Hands-on Exercise 5 β€” Build Your Enterprise Security Architecture”

Design a high-level architecture for CloudNova Technologies.

Include:

  • Users
  • IAM
  • VPC
  • Public Subnets
  • Private Subnets
  • Load Balancer
  • EC2
  • RDS
  • S3
  • KMS
  • CloudTrail
  • GuardDuty
  • Security Hub
  • AWS Backup
  • WAF
  • Shield

Draw the architecture using:

  • draw.io
  • Lucidchart
  • Excalidraw
  • Microsoft Visio

Label each security control and explain its purpose.


Answer the following questions:

  1. What is Enterprise Security Architecture?
  2. Why is Defence in Depth important?
  3. What is Zero Trust?
  4. Why is identity considered the new security perimeter?
  5. Which AWS services secure the network layer?
  6. Which AWS services help detect threats?
  7. What is the purpose of AWS Security Hub?
  8. Why is monitoring essential?
  9. How does Business Continuity support security?
  10. What are the key responsibilities of a Cloud Security Engineer?

Prepare an Enterprise Security Architecture Review for CloudNova Technologies.

Include:

  • Enterprise Security Architecture overview.
  • Defence in Depth strategy.
  • Zero Trust implementation.
  • Layer-by-layer security controls.
  • AWS security services used.
  • Security architecture diagram.
  • Recommendations for improving CloudNova’s security posture.

Length: 4–5 pages, including at least one architecture diagram.


After completing this lesson, you should understand:

  • Enterprise Security Architecture provides a structured approach to securing the organisation.
  • Security is implemented through multiple layers rather than a single control.
  • Defence in Depth ensures resilience if one control fails.
  • Zero Trust requires every request to be authenticated, authorised, and monitored.
  • AWS offers integrated services for identity, network, compute, data, monitoring, and incident response.
  • Cloud Security Engineers are responsible for designing, implementing, and continuously improving enterprise security architectures.

  • AWS Well-Architected Framework – Security Pillar
  • AWS Security Reference Architecture (AWS SRA)
  • AWS Prescriptive Guidance – Security
  • NIST Cybersecurity Framework (CSF) 2.0
  • NIST SP 800-207 – Zero Trust Architecture
  • CIS Controls v8
  • ISO/IEC 27001 & ISO/IEC 27002

➑️ Day in the Life of a Cloud Security Engineer