Skip to content

Lesson 05 — Enterprise Vulnerability & Compliance Project & Module Review

Learning Path

☁️ Phase 02 – AWS Cloud Security

📘 Module 09 – Vulnerability & Compliance Management


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

  • Build an enterprise vulnerability management programme.
  • Perform an organisation-wide compliance assessment.
  • Identify and prioritise security risks.
  • Implement automated remediation processes.
  • Produce executive security and compliance reports.
  • Demonstrate the day-to-day responsibilities of a Cloud Security Engineer.

📚 Lesson Information

Estimated Time: 5 Hours

Difficulty: Advanced

Prerequisites: Lessons 01–04

Hands-on Project: Yes


CloudNova Technologies is preparing for its annual external security audit.

The organisation operates:

  • 60 AWS Accounts
  • 1,500 Amazon EC2 Instances
  • 500 Amazon ECR Repositories
  • 800 AWS Lambda Functions
  • 10,000 Amazon S3 Buckets
  • Hundreds of IAM Roles
  • Multi-Region AWS Infrastructure

The audit requires compliance with:

  • CIS AWS Foundations Benchmark
  • AWS Foundational Security Best Practices
  • PCI DSS
  • ISO 27001

Recent assessments reveal:

  • Critical EC2 vulnerabilities
  • Public Amazon S3 buckets
  • Sensitive customer data stored without proper classification
  • Excessive IAM permissions
  • Missing security patches
  • Non-compliant Security Groups
  • Configuration drift
  • Outdated container images

The CISO asks one final question before the audit begins.

“Can we prove that our AWS environment is continuously monitored, compliant and capable of responding quickly to newly discovered vulnerabilities?”

As the Cloud Security Engineer, your task is to perform a complete enterprise vulnerability assessment, prioritise risks, implement remediation and produce executive-level compliance reports.


Throughout this capstone project you will implement:

  • Amazon Inspector
  • AWS Systems Manager Patch Manager
  • IAM Access Analyzer
  • Amazon Macie
  • AWS Config
  • AWS Config Rules
  • Conformance Packs
  • AWS Security Hub

This project combines everything learned throughout Module 09.


AWS Organizations
┌─────────────────────┼─────────────────────┐
│ │ │
Production Development Shared Services
│ │ │
Amazon Inspector Inspector Inspector
│ │ │
AWS Systems Manager Patch Manager
IAM Access Analyzer
Amazon Macie
AWS Config
Security Hub
CloudWatch / EventBridge
SOC Team
Executive Dashboard

Create an inventory of:

  • Amazon EC2
  • Amazon EBS
  • Amazon RDS
  • Amazon S3
  • Amazon ECR
  • AWS Lambda
  • IAM Roles
  • VPC Resources

Classify assets according to:

  • Business Criticality
  • Internet Exposure
  • Data Classification
  • Compliance Requirements

Deliverable:

Enterprise Asset Inventory.


Enable Amazon Inspector.

Review:

  • EC2 Findings
  • Container Image Findings
  • Lambda Findings
  • Critical CVEs
  • High-Risk Packages

Prioritise findings based on:

  • CVSS Score
  • Business Impact
  • Internet Exposure
  • Exploit Availability

Deliverable:

Enterprise Vulnerability Report.


Configure AWS Systems Manager Patch Manager.

Create:

  • Patch Baselines
  • Maintenance Windows
  • Patch Groups

Validate:

  • Patch Compliance
  • Missing Updates
  • Successful Patch Installation

Deliverable:

Patch Management Plan.


Phase 04 — Identity & Data Security Review

Section titled “Phase 04 — Identity & Data Security Review”

Review IAM Access Analyzer findings.

Investigate:

  • Public Resources
  • Cross-Account Access
  • External Principals
  • Broad IAM Policies

Enable Amazon Macie.

Review:

  • Sensitive Data Discovery
  • PII Findings
  • Public Buckets
  • Missing Encryption

Deliverable:

Identity & Data Security Assessment.


Enable AWS Config.

Deploy:

  • AWS Config Rules
  • Conformance Packs

Review:

  • Configuration Drift
  • Non-Compliant Resources
  • Failed Controls

Enable AWS Security Hub.

Review:

  • Compliance Standards
  • Security Findings
  • Risk Dashboard

Deliverable:

Compliance Assessment Report.


Validate the following controls.

Security Control Status
Amazon Inspector Enabled
Patch Manager Configured
Patch Baselines Created
Maintenance Windows Configured
IAM Access Analyzer Enabled
Amazon Macie Enabled
AWS Config Enabled
Config Rules Deployed
Conformance Packs Applied
Security Hub Enabled
Compliance Standards Enabled

During the project, CloudNova identifies the following findings.

Critical CVE

Resource:

Production EC2

Expected Action

✅ Prioritise remediation.

✅ Patch immediately.


Public Amazon S3 Bucket

Expected Action

✅ Remove public access.

✅ Enable S3 Block Public Access.


IAM Role with AdministratorAccess

Expected Action

✅ Replace with least-privilege policy.


Customer PII Found

Detected by:

Amazon Macie

Expected Action

✅ Restrict access.

✅ Enable encryption.


Unencrypted EBS Volume

Expected Action

✅ Create encrypted replacement volume.


Security Group Allows 0.0.0.0/0 on Port 22

Expected Action

✅ Restrict SSH access.


For every finding determine:

  • Severity
  • Business Impact
  • Root Cause
  • Recommended Fix
  • Responsible Team
  • Expected Completion Date
  • Validation Method

Document your investigation.


Prepare the following enterprise documentation.


Include:

  • Critical Findings
  • High Findings
  • Medium Findings
  • Risk Ratings
  • Recommended Actions

Summarise:

  • Overall Compliance Score
  • Failed Controls
  • Security Standards
  • Audit Readiness

Include:

  • Missing Patches
  • Patch Success Rate
  • Maintenance Schedule
  • Outstanding Issues

Document:

  • Excessive IAM Permissions
  • Cross-Account Access
  • Public Resources
  • Access Review Results

Include:

  • Sensitive Data Locations
  • Macie Findings
  • Encryption Status
  • Data Classification

Present:

  • Total Findings
  • Critical Findings
  • Compliance Percentage
  • Patch Compliance
  • High-Risk Assets
  • MTTR (Mean Time to Remediate)
  • Risk Trend

Enable:

  • Amazon Inspector
  • Patch Manager

Review:

  • Vulnerabilities
  • Patch Compliance

Enable:

  • IAM Access Analyzer

Review:

  • Public Resources
  • External Access
  • IAM Roles

Enable:

  • Amazon Macie

Review:

  • Sensitive Data Discovery
  • PII Findings
  • Bucket Classification

Deploy:

  • AWS Config
  • Config Rules
  • Conformance Packs

Review compliance.


Enable:

  • AWS Security Hub

Review:

  • Overall Security Score
  • Compliance Dashboard
  • Critical Findings

Prepare an Executive Security Report including:

  • Current Risk Level
  • Compliance Status
  • Priority Vulnerabilities
  • Remediation Plan
  • Executive Recommendations

Terminal window
aws inspector2 list-findings

Terminal window
aws ssm describe-patch-baselines

Terminal window
aws ssm describe-maintenance-windows

Terminal window
aws accessanalyzer list-findings \
--analyzer-name CloudNovaAnalyzer

Terminal window
aws macie2 list-findings

Terminal window
aws configservice describe-config-rules

Terminal window
aws securityhub get-findings

CloudNova standards include:

  • Maintain an accurate enterprise asset inventory.
  • Continuously scan workloads for vulnerabilities.
  • Prioritise remediation using business risk.
  • Test patches before production deployment.
  • Apply least-privilege principles.
  • Protect sensitive data using encryption and classification.
  • Continuously monitor configuration compliance.
  • Automate security reporting.
  • Review executive security dashboards weekly.
  • Integrate vulnerability management into CI/CD pipelines.

❌ Treating vulnerability scanning as a quarterly activity.

❌ Delaying remediation of Internet-facing systems.

❌ Ignoring excessive IAM permissions.

❌ Storing confidential information without encryption.

❌ Deploying infrastructure without Config Rules.

❌ Ignoring Security Hub findings.

❌ Performing compliance reviews only before audits.


CloudNova is preparing for an international audit covering ISO 27001, PCI DSS and SOC 2.

Design a complete enterprise vulnerability and compliance programme that:

  1. Continuously scans EC2, ECR and Lambda workloads.
  2. Automates operating system patching.
  3. Detects public and cross-account resource exposure.
  4. Discovers sensitive customer information.
  5. Continuously monitors AWS resource compliance.
  6. Produces executive dashboards for leadership.
  7. Integrates all findings into Security Hub.
  8. Supports future growth across multiple AWS Regions and AWS Organizations.

Prepare the following documents:

  • Enterprise Security Architecture
  • Asset Inventory
  • Vulnerability Assessment Report
  • Patch Management Plan
  • Identity & Access Review
  • Data Classification Report
  • Compliance Dashboard
  • Executive Risk Report
  • Remediation Roadmap

Congratulations!

You have completed Module 09 – Vulnerability & Compliance Management.

You can now:

✅ Build enterprise vulnerability management programmes

✅ Perform continuous EC2, Lambda and container vulnerability assessments

✅ Automate patch management

✅ Identify excessive IAM permissions

✅ Discover sensitive information stored in Amazon S3

✅ Continuously monitor AWS compliance

✅ Build executive security dashboards

✅ Prepare organisations for enterprise security audits


  1. What is the purpose of Amazon Inspector?
  2. How does Patch Manager improve enterprise security?
  3. What does IAM Access Analyzer detect?
  4. What type of information can Amazon Macie discover?
  5. Why is AWS Config important for compliance?
  6. What is configuration drift?
  7. How does AWS Security Hub improve visibility?
  8. Why should organisations prioritise vulnerabilities based on business impact?
  9. How do these AWS services work together to improve security posture?
  10. Why is continuous compliance monitoring more effective than periodic security assessments?

After completing this module, you should understand:

  • Vulnerability management is an ongoing process that combines continuous discovery, risk assessment, remediation and validation.
  • Amazon Inspector and AWS Systems Manager Patch Manager help identify and remediate software vulnerabilities across EC2 instances, container images and Lambda functions.
  • IAM Access Analyzer and Amazon Macie strengthen identity governance and data protection by detecting unintended access and sensitive data exposure.
  • AWS Config and AWS Security Hub provide continuous compliance monitoring and a centralised view of security findings across AWS accounts.
  • Enterprise Cloud Security Engineers must not only secure cloud infrastructure but also demonstrate compliance, reduce organisational risk and communicate security posture effectively to technical teams, auditors and executive leadership.

Excellent work!

You have successfully completed Module 09 – Vulnerability & Compliance Management.

You now have the knowledge and practical skills to assess, prioritise, remediate and continuously monitor security risks across enterprise AWS environments using AWS-native security services.


➡️ Module 10 — Backup, Disaster Recovery & Business Continuity

In the next module, you will learn how to:

  • Design resilient backup strategies using AWS Backup
  • Protect workloads against accidental deletion and ransomware
  • Implement cross-Region and cross-account backups
  • Design Disaster Recovery (DR) architectures
  • Calculate RPO (Recovery Point Objective) and RTO (Recovery Time Objective)
  • Build Business Continuity Plans (BCP)
  • Test backup restoration and disaster recovery procedures

You will move from protecting and monitoring cloud workloads to ensuring business resilience and rapid recovery, a critical responsibility for every Cloud Security Engineer.