Arkinu
AWS service comparison

Amazon GuardDuty vs Amazon Inspector: differences and when to use each

Amazon GuardDuty
Amazon Inspector

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Security, Identity, and Compliance

Amazon GuardDuty

Threat detection service that continuously analyzes sources such as AWS CloudTrail events, VPC Flow Logs, and DNS logs. It uses threat intelligence and machine learning to detect suspicious activity, such as compromised credentials or unauthorized cryptocurrency mining.

Exam phrases that point here

  • «detect malicious activity or unauthorized behavior in AWS accounts»

    GuardDuty is the threat detection service: it continuously monitors the activity of accounts and workloads and generates a finding when it sees something suspicious.

    When not: If the ask is to investigate the root cause of a finding that has already been detected, it points to Amazon Detective. If you are looking for software vulnerabilities, to Amazon Inspector; if you are looking for sensitive data in S3, to Amazon Macie.

  • «analyze CloudTrail events, VPC Flow Logs, and DNS logs to identify threats»

    Those are exactly GuardDuty's foundational sources, which it reads on its own without you having to enable or store them.

    When not: If the requirement is to retain or audit who made each API call, that is AWS CloudTrail. If the ask is to query the logs by hand, think of query tools such as Amazon Athena, not GuardDuty.

  • «intelligent threat detection without deploying agents or additional software»

    GuardDuty's basic protection is enabled in the console and starts analyzing with no sensors, appliances, or changes to resources.

    When not: The exception is Runtime Monitoring, which does use an agent. And if the scenario asks to block traffic inline, GuardDuty is not enough: it detects, but the blocking is done by another service (for example, AWS Network Firewall or AWS WAF) or an automation.

  • «an EC2 instance is communicating with IP addresses associated with cryptocurrency mining»

    GuardDuty uses lists of malicious IPs and domains and behavior models to flag compromised instances, such as those talking to mining servers or attacker command-and-control servers.

    When not: GuardDuty reports the finding; isolating the instance or closing off access requires a response, often automated with Amazon EventBridge and AWS Lambda.

  • «detect malware in objects uploaded to an S3 bucket or in EBS volumes»

    GuardDuty Malware Protection scans new objects in S3 and copies of EBS volumes from suspicious instances, with no agents.

    When not: If what you are looking for in S3 is not malware but personal or confidential information, the service is Amazon Macie.

Often paired with

  • AWS CloudTrail
  • Amazon EventBridge
  • Amazon Detective
  • AWS Security Hub
Study Amazon GuardDuty →

Security, Identity, and Compliance

Amazon Inspector

Vulnerability management service that automatically discovers Amazon EC2 instances, container images in Amazon ECR, and AWS Lambda functions. It continuously scans them for software vulnerabilities and unintended network exposure.

Exam phrases that point here

  • «continuously assess EC2 instances for known software vulnerabilities (CVEs)»

    Amazon Inspector discovers the instances and rescans them only when their packages change or a new vulnerability that affects them is published.

    When not: Inspector finds the vulnerability; it does not install the patch. Patching at scale is AWS Systems Manager (Patch Manager). And if the scenario describes suspicious activity or a compromised instance, it points to Amazon GuardDuty.

  • «scan container images in Amazon ECR for vulnerabilities»

    Enhanced scanning for ECR is done by Inspector: it covers operating system and programming language packages and rescans images when new vulnerabilities appear.

    When not: If checking operating system packages when the image is pushed is enough, ECR's own basic scanning may be sufficient. For threats in containers that are already running, think of GuardDuty Runtime Monitoring.

  • «identify instances exposed to the internet through an unintended network path»

    Inspector also generates network reachability findings: it warns you when a compute resource has an open path that it should not have.

    When not: Inspector reports; it does not close the access. That is fixed in security groups, network ACLs, or route tables. If the question is about checking account configurations against standards, AWS Security Hub CSPM or AWS Config is a better fit.

  • «detect vulnerabilities in the dependencies of AWS Lambda functions»

    Inspector scans Lambda functions (the $LATEST version) and, if enabled, their code as well.

    When not: If the concern is a function that communicates with malicious servers, that is threat detection: GuardDuty Lambda Protection.

  • «block images with critical vulnerabilities in the CI/CD pipeline»

    Inspector has integrations with CI/CD tools that scan the image in a pipeline step and can stop the build based on the result.

    When not: If what needs to be checked is the configuration of the AWS account against CIS AWS Foundations, not the image or the operating system, the service is Security Hub CSPM.

Often paired with

  • Amazon EC2
  • Amazon ECR
  • AWS Lambda
  • AWS Security Hub
Study Amazon Inspector →