Arkinu
AWS service comparison

Amazon Detective vs AWS Security Hub: differences and when to use each

Amazon Detective
AWS Security Hub

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 Detective

Security investigation service that automatically collects AWS CloudTrail logs and VPC Flow Logs, along with Amazon GuardDuty findings, and organizes them into a behavior graph. It helps you find the root cause of a finding or of suspicious activity.

Exam phrases that point here

  • «investigate the root cause of a GuardDuty finding»

    Amazon Detective organizes logs and findings into a behavior graph so an analyst can see what happened around the finding and since when.

    When not: Detective does not detect threats on its own: if the scenario asks to detect them, it points to Amazon GuardDuty. If it asks for a central view of findings from several services, to AWS Security Hub.

  • «visualize interactions between users, resources, and IP addresses over time»

    Detective's behavior graph relates accounts, users, roles, instances, and IPs, and offers ready-made visualizations to explore that activity.

    When not: If all that is needed is an auditable record of who made each API call, that is AWS CloudTrail. If the ask is to query the raw logs with SQL, think of Amazon Athena.

  • «determine whether the credentials of an IAM user or role were compromised»

    Detective's automated investigations review IAM users and roles for signs of compromise, such as sign-ins from impossible locations or from known malicious IPs.

    When not: If what you are looking for is overly permissive policies or resources shared with external accounts, the tool is IAM Access Analyzer.

  • «group related findings to investigate them as a single incident»

    Detective's finding groups gather findings and resources tied to the same possible incident so they can be analyzed together.

    When not: If the requirement is for the detection itself to correlate several stages of an attack into a single finding, that is done by GuardDuty Extended Threat Detection; Detective is used afterward, to investigate.

  • «speed up security investigations without writing scripts or managing logs»

    Detective collects the data on its own and comes with the visualizations and analysis guidance already built, with no additional tools.

    When not: If the scenario asks to respond or remediate automatically, Detective does not do that: that is built with EventBridge, Lambda, or response tooling.

Often paired with

  • Amazon GuardDuty
  • AWS CloudTrail
Study Amazon Detective →

Security, Identity, and Compliance

AWS Security Hub

AWS Security Hub now has two parts. The unified Security Hub correlates signals from Amazon GuardDuty, Amazon Inspector, Amazon Macie, and Security Hub CSPM to prioritize and respond to the most critical risks in your AWS environment. AWS Security Hub CSPM, the previous Security Hub, checks your accounts against security standards and best practices and aggregates findings from AWS services and partner products.

Exam phrases that point here

  • «centralized view of security findings across multiple accounts and AWS services»

    AWS Security Hub collects the findings from GuardDuty, Inspector, Macie, and other services in an administrator account, so you can review and prioritize them in one place.

    When not: Security Hub does not replace the detectors: without GuardDuty, Inspector, or Macie there are no findings to collect. If the ask is to investigate the root cause of a finding, it points to Amazon Detective.

  • «continuously check accounts against the CIS AWS Foundations Benchmark or AWS Foundational Security Best Practices»

    Those standards checks are the core of Security Hub CSPM, which evaluates resources mostly with AWS Config rules and generates control findings with the result of each check.

    When not: If the ask is to create a custom standard that mixes security, operations, or cost checks, AWS Config conformance packs fit. If the ask is to set up a governed multi-account environment with guardrails, it is AWS Control Tower.

  • «security posture score against an industry standard»

    Security Hub CSPM calculates a score for each enabled standard and points out the controls that need attention.

    When not: A score of 100% does not guarantee passing an audit, because many controls cannot be checked automatically. AWS's own compliance reports are downloaded from AWS Artifact.

  • «prioritize risks by correlating vulnerabilities, configurations, and threats»

    The current Security Hub correlates signals from Security Hub CSPM, Inspector, GuardDuty, and Macie to show exposures and potential attack paths, instead of a flat list of findings.

    When not: Watch out for study materials: before the split, "Security Hub" was what is now called Security Hub CSPM. If the question talks about standards checks or aggregating partner findings, it refers to that part.

  • «aggregate security findings from multiple Regions into a single Region»

    Security Hub is regional, but it lets you designate an aggregation Region that collects the findings from the other Regions.

    When not: If it is only about GuardDuty findings, they can also be exported from each Region to the same S3 bucket. If the ask is for a single view of several services, Security Hub fits better.

Often paired with

  • Amazon GuardDuty
  • Amazon Inspector
  • Amazon Macie
  • AWS Config
Study AWS Security Hub →