# Vulnerability Assessment

Vulnerability assessment is the systematic identification, evaluation, and prioritization of security weaknesses in systems, software, and configurations.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/vulnerability-assessment

> A vulnerability assessment determines which weaknesses exist, which resources they affect, and how urgently they need attention. In cloud environments, recurring assessments help engineers address vulnerable dependencies, exposed workloads, and insecure configurations as deployments and threat information change.

Practice exams covering Vulnerability Assessment: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Vulnerability Assessment

Effective vulnerability assessment combines verified coverage, suitable inspection methods, contextual prioritization, recurring scans, and validated remediation.

1. **Explicit scope and verified coverage**: Inventory the resources, accounts, Regions, and workload types that require assessment. Monitor unsupported resources, permission failures, and stale scans so missing coverage is not mistaken for a clean result.
2. **Workload-appropriate inspection**: Use inspection methods suited to virtual machines, container images, and serverless packages. Include both operating-system packages and application dependencies where the assessment tool supports them.
3. **Risk-based prioritization**: Combine vulnerability severity with exposure, exploitability, asset importance, and business impact. Use this context to establish remediation deadlines rather than treating every finding with the same severity as equally urgent.
4. **Continuous reassessment**: Reassess after deployments, dependency updates, and changes to vulnerability intelligence. Track scan freshness because unchanged software can become newly vulnerable when a weakness is disclosed.
5. **Verified remediation**: Patch, rebuild, replace, or otherwise mitigate affected workloads, then reassess the deployed resources. Record time-limited exceptions when immediate remediation is not possible.
6. **Complementary security controls**: Use network restrictions to reduce exposure and runtime detection to identify suspicious behavior. Neither control substitutes for identifying and correcting vulnerable software.

## Cloud services for Vulnerability Assessment

Amazon Inspector supplies vulnerability findings for supported compute workloads, including enhanced image scanning integrated with Amazon ECR. ECR holds the images that teams rebuild and redeploy when vulnerable packages are found. AWS Systems Manager supports agent-based EC2 inventory collection and can help apply operating-system patches through Patch Manager. Amazon GuardDuty adds behavioral threat detection, including runtime monitoring for supported EC2 and container workloads. Together, these services support a workflow of assessment, prioritization, remediation, verification, and threat monitoring. Engineers must still verify coverage, assign owners, and ensure corrected artifacts actually replace affected workloads.

- **[Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector)**: Assesses supported EC2 instances, ECR container images, and Lambda functions for vulnerabilities, with coverage depending on workload and scan type. It produces findings for remediation and can identify supported EC2 network-reachability issues; it does not patch workloads or block attacks.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: Complements vulnerability assessment with threat detection rather than serving as a general known-vulnerability scanner. Runtime Monitoring analyzes runtime activity on supported EC2 and container workloads, while Lambda Protection analyzes Lambda network activity.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Supports agent-based Inspector EC2 scanning through SSM Agent and software inventory collection for supported managed instances. Systems Manager Patch Manager can help remediate operating-system package vulnerabilities, but patch execution and assessment remain distinct activities.

## Vulnerability Assessment exam questions

Real practice exam questions on Vulnerability Assessment, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company runs Amazon EC2 instances across several VPC subnets. Before a security review, the company needs an automated assessment that identifies instances with SSH ports reachable from the internet through their current network configurations. The assessment must work even if no connection attempts have occurred and must not change existing traffic rules. Which solution best meets these requirements?

**Correct answer:** Enable Amazon Inspector scanning for EC2 instances and review its network reachability findings.

**Explanation:** Amazon Inspector assesses EC2 network reachability by analyzing network configurations, including security groups, network ACLs, routes, and gateways. It can report internet-reachable SSH ports without observing connection attempts or changing traffic rules.

### Question 2 (MLA-C02 (beta))

**Question:**

An ML team is preparing to release a custom inference container stored in Amazon ECR. Amazon Inspector reports a HIGH-severity vulnerability in an operating-system package inherited from the container's base image. The finding identifies the installed package version and a fixed version. The application source-code security checks pass.

The platform team updates the base image's existing tag to reference a new image that contains the fixed package. However, a new assessment of the previously built inference image still reports the vulnerability. The release has not been deployed.

Which action should the ML engineer take to remediate the release candidate and verify the result?

**Correct answer:** Pull the patched base image, rebuild the inference image without reusing the old base layers, and push the new image. Confirm that the assessment of the new image digest no longer reports the affected package version.

**Explanation:** Container images retain the layers used when they were built. Rebuilding with the patched base incorporates the corrected package. Assessing the resulting image digest verifies that the release artifact, rather than just its base-image tag, has been remediated.

### Question 3 (SAP-C03)

**Question:**

A company runs an Amazon ECS service on AWS Fargate. Its task definitions reference container images in a private Amazon ECR repository by digest. Amazon Inspector enhanced scanning identifies a CRITICAL vulnerability in a Java dependency bundled in the production image.

A remediation pipeline updates the dependency, rebuilds the image, and pushes a new digest. Assessment of the new image completes without the vulnerability. However, the pipeline reports that remediation failed because it still finds the original CRITICAL finding in the repository. The original image must remain available for 180 days for forensic analysis, and its findings must not be suppressed. Production tasks are still running the original digest.

The company needs the pipeline to remediate the production workload and produce evidence that the vulnerable dependency is no longer deployed. Which solution meets these requirements?

**Correct answer:** Register a new task definition referencing the corrected digest and update the ECS service. Verify that replacement completes and that all running service tasks use the corrected digest. Associate their digests with completed Inspector assessments showing that the vulnerability is absent, while retaining the original image and its findings.

**Explanation:** Remediation requires replacing the vulnerable running containers, not merely publishing a corrected image. Correlating the digests actually running in ECS with their completed assessments provides workload-specific evidence. The retained original image can legitimately continue to have an active finding without indicating that the corrected production workload remains vulnerable.

### Question 4 (SCS-C03)

**Question:**

A company uses Amazon Inspector to assess supported Linux EC2 instances. The security team creates suppression rules for selected CRITICAL package vulnerabilities that have approved, temporary risk exceptions. Compensating network controls are in place, but the affected packages have not been updated. Inspector continues to scan the instances successfully.

An audit dashboard retrieves only ACTIVE Inspector findings and now reports zero outstanding CRITICAL vulnerabilities. The company must correct the dashboard without removing the suppression rules or returning accepted findings to the operational remediation queue. The dashboard must distinguish unresolved vulnerabilities with approved exceptions from verified remediation and identify resources that lack a current assessment.

Which solution meets these requirements?

**Correct answer:** Retrieve ACTIVE and SUPPRESSED findings and correlate them with the approved exception records. Report excepted vulnerabilities separately from remediation, validate remediation against current assessment evidence, and use coverage and scan freshness to identify assessment gaps.

**Explanation:** Suppression changes how findings are presented; it does not remove the vulnerable packages or stop assessment. Including suppressed findings preserves visibility into unresolved vulnerabilities while leaving the operational queue unchanged. Exception records distinguish accepted risk, current assessment evidence supports remediation claims, and coverage information exposes unassessed or stale resources.

### Question 5 (DOP-C02)

**Question:**

A company continuously scans its Amazon EC2 fleet for software vulnerabilities. An existing Amazon EventBridge rule forwards Amazon Inspector finding events with status ACTIVE to an incident-management system.

The security team approves a temporary risk exception for one specific CVE, but only on instances tagged Environment=development. Findings covered by the exception must no longer appear in the default active-findings view or trigger new incidents. Auditors must still be able to retrieve these findings. All instances must remain continuously scanned, and findings for other CVEs or for instances without the development tag must remain unaffected.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Create an Amazon Inspector suppression rule that matches both the specific vulnerability ID and the resource tag Environment=development. Retain the existing EventBridge rule.

**Explanation:** A suppression rule automatically changes matching findings to SUPPRESSED without disabling resource scanning. Combining the vulnerability ID and resource-tag criteria limits the exception to the approved scope. Suppressed findings remain available for audit but are excluded from the default active-findings view and do not generate active-finding notifications through the existing rule.

## Practice Vulnerability Assessment in a full exam

Questions on Vulnerability Assessment in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 8 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 7 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 7 questions
- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 4 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 3 questions

## What is Vulnerability Assessment

Vulnerability assessment examines assets for security weaknesses and evaluates their potential impact. Findings can include software packages affected by published Common Vulnerabilities and Exposures identifiers, unsupported components, or configurations that expose a workload to unnecessary access. The objective is actionable evidence: identify the affected resource, explain the weakness, determine its relevance, and recommend remediation or a documented mitigation.

Cloud assessments start with resource discovery and coverage validation. Engineers need to know which virtual machines, container images, functions, accounts, and Regions are included. A successful scan of one resource does not establish coverage for an entire environment. Unsupported operating systems, missing permissions, unavailable package inventories, and excluded repositories can create blind spots. Coverage status and scan freshness therefore matter alongside the number and severity of findings.

Different workload types require different inspection methods. Virtual machines can be assessed through software inventory collected by an agent or through supported agentless inspection. Container images should be scanned in a registry or build pipeline so vulnerable operating-system packages and application dependencies can be addressed before deployment. Serverless assessments examine supported function packages and dependencies; optional code analysis can identify additional code-level weaknesses. Provider management of the underlying infrastructure does not remove customer responsibility for application code and bundled dependencies.

On AWS, Amazon Inspector assesses supported Amazon EC2 instances, container images in Amazon ECR, and AWS Lambda functions. For example, an engineer can identify a vulnerable library in an ECR image, update the dependency or base image, rebuild the image, and replace running containers with the corrected version. Pushing a fixed image alone does not update containers that are already running. For Lambda ZIP deployments, the engineer must update affected dependencies or layers and deploy the corrected function package.

Network controls and vulnerability assessment solve different problems. A security group is a stateful traffic control associated with network interfaces, while a network ACL applies stateless allow and deny rules at a subnet boundary. Neither checks installed packages for known vulnerabilities. Restricting ingress can reduce exposure to a vulnerable service, but it does not remove the vulnerable component. Amazon Inspector can also identify supported EC2 network-reachability findings; it is not an inline firewall and does not block traffic.

Prioritization should combine technical severity with workload context. A high-severity issue on an internet-accessible production service can warrant faster action than the same issue on an isolated test instance. Consider exploit availability, reachable attack paths, data sensitivity, business impact, and available fixes. Validate findings where necessary, because package identification and vendor backported fixes can complicate interpretation. Exceptions should have an owner, justification, compensating controls, and an expiration date.

Assessment is not penetration testing, patch deployment, or proof that exploitation occurred. Amazon GuardDuty complements scanning by detecting suspicious activity; its Runtime Monitoring capability analyzes runtime events on supported EC2 and container workloads. GuardDuty Lambda Protection analyzes Lambda network activity rather than providing the same runtime-agent monitoring used for those workloads. A runtime threat finding may require incident response even when vulnerability scans report no known issue.

Effective assessment is continuous rather than a one-time audit. New deployments and newly published vulnerability intelligence can change results without an application code change. Balance scan costs, coverage, operational overhead, and potential disruption from active testing. Assign findings to owners, remediate through controlled changes, and reassess the deployed resources to verify closure. A clean result means no covered weaknesses were detected by that assessment, not that the workload is invulnerable.

## Learn Vulnerability Assessment in lessons

9 short lessons on Vulnerability Assessment in 5 certification courses.

- CLF-C02: Vulnerability Assessment: identifying weaknesses in VPC workloads (Premium), https://app.blowstack.com/lessons/vulnerability-assessment-identifying-weaknesses-in-vpc-workloads-clf-c02
- MLA-C02 (beta): Threat Modeling vs. Vulnerability Assessment (Premium), https://app.blowstack.com/lessons/threat-modeling-vs-vulnerability-assessment-mla-c02
- SAP-C03: Security Quality Gates vs Vulnerability Assessment (Premium), https://app.blowstack.com/lessons/security-quality-gates-vs-vulnerability-assessment-sap-c03
- SCS-C03: Runtime Threat Detection vs. Vulnerability Assessment (Premium), https://app.blowstack.com/lessons/runtime-threat-detection-vs-vulnerability-assessment-scs-c03
- DOP-C02: Vulnerability Assessment: assessment scope and coverage (Premium), https://app.blowstack.com/lessons/vulnerability-assessment-assessment-scope-and-coverage-dop-c02
- MLA-C02 (beta): Vulnerability Assessment: ML workload assessment lifecycle (Premium), https://app.blowstack.com/lessons/vulnerability-assessment-ml-workload-assessment-lifecycle-mla-c02
