View a markdown version of this page

FND05-BP08 Employ vulnerability and patch management controls - AWS Well-Architected Framework

FND05-BP08 Employ vulnerability and patch management controls

Establish centralized vulnerability and patch management so your organization can identify, assess, and remediate security weaknesses consistently across workloads. A shared foundation reduces duplicated effort and creates clear accountability.

Desired outcome:

  • You have established centralized capabilities for vulnerability management that include standardized tools, processes, and policies for scanning, patch management, and security monitoring.

  • You have clear governance structures in place for security control implementation, exception management, and compliance reporting.

  • Your automated systems continuously monitor the security posture across all workloads, with centralized dashboards providing real-time visibility into risks and their remediation status.

  • Teams across your organization understand how to use these foundational services and can address workload-specific security requirements.

Common anti-patterns:

  • Letting each team implement their own vulnerability management tools and processes, leading to inconsistent security coverage and duplicated effort.

  • Implementing centralized tools without providing clear guidance, support, or training for workload teams to use them.

  • Enforcing rigid security controls without a defined exception process, causing teams to create workarounds.

  • Focusing solely on tool deployment without establishing supporting processes, policies, and governance structures, and setting policies without input from workload teams.

  • Rolling out foundational security services without considering different workload requirements (for example, development and production environments) and treating all workloads with the same security requirements regardless of data sensitivity.

  • Deploying multiple overlapping security scanning tools that create alert fatigue, without establishing clear ownership and processes for remediation.

Benefits of establishing this best practice:

  • Consistent security controls and processes across the organization provide full vulnerability management coverage and standardized security practices.

  • Foundational services and processes that workload teams can consume reduce duplication of effort, so teams can focus on their core objectives while meeting security standards.

  • Centralized security tooling and processes remove redundant tool deployments and reduce operational overhead across workload teams.

  • Standardized vulnerability management practices and automated monitoring provide consistent and reliable security coverage across all workloads.

  • Well-defined policies, processes, and accountability for security control implementation and exception management are established across the organization.

Level of risk exposed if this best practice is not established: High

Implementation guidance

Before cloud technologies, establishing a strong vulnerability management foundation across an enterprise was challenging because of diverse systems, inconsistent tooling, and limited visibility. Organizations faced siloed security efforts and the heavy manual effort associated with deploying and maintaining security infrastructure. The cloud now supports centralized management, automated scanning, and scalable security services that can be consistently applied across diverse workloads.

A unified vulnerability management foundation provides standardized tools, processes, and policies for the entire organization. Where possible, adopt immutable infrastructure to reduce risk exposure and simplify patch management. Deploy new instances with the latest updates and retire the old ones instead of patching in place. Use EC2 Image Builder to build and maintain pre-patched machine images.

Use Amazon Inspector to assess vulnerabilities in EC2 instances, container images, and Lambda functions. For systems that require in-place patching, configure AWS Systems Manager Patch Manager centrally to manage patches across compute resources.

Use AWS Organizations and service control policies to enforce security standards across accounts, including policies that require approved, up-to-date AMIs. AWS Security Hub CSPM shows security alerts and compliance status across accounts and routes its findings automatically to AWS Security Hub CSPM. Security Hub CSPM correlates them with findings from Amazon Inspector and other services to produce exposure findings that prioritize the most critical risks. AWS recommends enabling both services.

Integrating these services with broader organizational monitoring and ticketing systems enables tracking and remediation of identified vulnerabilities. Balance centralized controls with workload team autonomy. While the foundation provides standardized tools and processes, it should also allow flexibility to address unique workload requirements, and clear processes for exception management help the centralized foundation accommodate diverse compliance requirements across different business units or geographical regions.

Pair the tools that discover vulnerabilities with governance that defines severity thresholds, remediation SLAs, escalation paths, and the exception management process. Send findings into the tools teams already use (ticketing, change management, and chat) so remediation fits their existing workflows. Automate responses where judgment is not required, such as blocking deployment of container images with critical vulnerabilities. Route the rest to the appropriate owners with enough context to act.

Implementation steps

  1. Prioritize immutable infrastructure: Start by adopting an immutable infrastructure approach where possible, deploying workloads in verified known-good states rather than patching in place. Use EC2 Image Builder to create and maintain pipelines for building standardized AMIs and container images. See Create an image pipeline. This approach substantially reduces the need for ongoing patch management and provides consistent, tested environments across your organization.

  2. Implement automated vulnerability scanning: Configure Amazon Inspector to automatically scan your compute resources, including Amazon EC2 instances, container images in Amazon ECR repositories, and AWS Lambda functions. See Getting started with Amazon Inspector. Amazon Inspector provides enhanced container image scanning that supersedes basic Amazon ECR image scanning with deeper vulnerability analysis and continual monitoring, so Inspector is the preferred choice when both are available. Centralize findings in AWS Security Hub CSPM, and use AWS Systems Manager Inventory to maintain an inventory of resources that require scanning.

  3. Assess patch management requirements and constraints: Before implementing patch management processes, assess requirements across different workload types. Identify systems that require in-place patching compared with those that can adopt immutable infrastructure patterns. Document regulatory and compliance requirements that dictate patch timelines, and understand operational constraints such as maintenance windows and change control processes. Review AWS Systems Manager Patch Manager capabilities and determine which operating systems and applications in your environment are supported.

  4. Establish centralized patch management: For resources that require in-place patching, use AWS Systems Manager Patch Manager to define organization-wide patch baselines. See Working with custom patch baselines. Configure Systems Manager Maintenance Windows to schedule patching during approved windows. Set up automated patch compliance reporting. Implement automated rollback procedures using Systems Manager Automation runbooks for failed patches. Create emergency patch deployment procedures for zero-day vulnerabilities.

  5. Create an exception management process: Develop standardized exception request templates specifically for vulnerability management exceptions (delayed patching, scan exclusions). Define clear approval workflows based on risk levels, with stricter requirements for production environments. Use AWS Organizations to track and enforce exception policies through SCPs. Implement automated exception tracking through AWS Security Hub CSPM custom insights, and set up regular reviews of granted exceptions.

  6. Establish vulnerability monitoring and reporting: Centralize security findings in AWS Security Hub CSPM from various sources including Amazon Inspector, Amazon GuardDuty, and AWS Systems Manager Patch Manager. Create custom Security Hub CSPM insights for vulnerability trending and aging. Enable AWS Security Hub CSPM alongside Security Hub CSPM so vulnerability findings are correlated with threat and posture signals to generate exposure findings that identify the most critical risks. Apply risk-based prioritization that goes beyond raw severity scores. Take into account whether systems are internet-facing, the presence of compensating controls, and the business criticality of affected workloads. Use Security Hub CSPM finding attributes and custom actions to enrich findings with this environmental context. Configure Amazon EventBridge rules to automate responses to critical vulnerabilities. See Automated response and remediation. Integrate with third-party ticketing systems for automated remediation tracking.

Resources

Related best practices:

Related documents:

Related videos:

Related examples:

Related services: