Finding investigation
Amazon Detective helps investigate security findings and suspicious activity to understand their root cause. Its behavior graphA linked set of analyzed data from one or more AWS accounts. connects activity and resources over time.
How it works
- Detective collects core data from CloudTrail logs, VPC Flow Logs, which describe network flows, and GuardDuty findings. It uses independent event streams without using existing logging configurations.
- Detective analyzes the data and builds a behavior graph, a linked view of resource activity and interactions.
- Investigators explore the timeline and resource relationships to understand a finding. Finding groupsA collection of related findings and entities associated with a potential security event. bring related findings and entities together.
- A graph administrator can invite other AWS accounts to contribute data. Investigators can move from a GuardDuty finding in GuardDuty or Security Hub CSPM into Detective.
Exam cues
- If the question says investigate the context and root cause of a GuardDuty finding, think Detective, because it connects activity and resources over time.
- If the question says find potentially malicious activity in AWS logs, think GuardDuty, because it analyzes logs for threats; use Detective to investigate findings.
- If the question says investigate related findings and entities together, think finding groups, because they bring them together for investigation.
- If the question says investigate activity across accounts, think a behavior graph, because an administrator can invite member accounts to contribute data.
Remember
- Core sources include CloudTrail, VPC Flow Logs and GuardDuty findings for accounts enrolled in GuardDuty.
- Detective uses independent CloudTrail and VPC flow log streams without using existing logging configurations.
Trap: Detective investigates findings; GuardDuty identifies potentially malicious activity. They are complementary, not interchangeable.
Detective uses CloudTrail events from graph accounts.
Detective uses VPC flow log events from independent streams.
Detective ingests GuardDuty findings for enrolled accounts and links activity over time.
From the AWS docs (10)
- Amazon Detective helps investigate security findings and suspicious activity to identify their root cause.
- Detective core sources include CloudTrail logs, VPC Flow Logs and GuardDuty findings for accounts enrolled in GuardDuty.
- Detective uses independent streams of CloudTrail and VPC flow log events without using existing logging configurations.
- AWS security findings is an optional source package that ingests Security Hub CSPM findings into Detective.
- The AWS security findings package is enabled by default for new behavior graphs created after May 16, 2023.
- Detective uses event data and machine learning to create an interactive view of resource behavior and interactions over time.
- Detective finding groups bring related findings and entities together for investigation.
- A Detective behavior graph can link analyzed data from one or more AWS accounts; an administrator can invite member accounts to contribute.
- Detective integrates with GuardDuty and Security Hub CSPM so an investigator can pivot from a GuardDuty finding to Detective.
- GuardDuty analyzes AWS logs using threat intelligence and machine learning to identify potentially malicious activity.
Investigation sources and history
Amazon Detective provides historical event data and source packages for investigation. Detective Investigation analyzes IAM users and roles for indicators of compromise, or signs of malicious activity.
How it works
- The core sources include CloudTrail logs, VPC Flow Logs and GuardDuty findings for accounts enrolled in GuardDuty.
- EKS audit logs require a separate source packageA group of data sources that Detective uses for a behavior graph. enabled for the behavior graphA linked set of analyzed data from one or more AWS accounts..
- Detective provides access to historical event data. Detective Investigation analyzes IAM users and roles for indicators of compromise. History | Detective Investigation
Exam cues
- If the question says investigate an IAM user or role for indicators of compromise, think Detective Investigation, because it analyzes those identities.
- If the question says include EKS audit logs in a behavior graph, think of enabling their source package, because they are separate from the core sources.
- If the question asks how far back event data is available, think up to one year, because that is the historical data Detective provides.
Remember
- Detective provides access to up to one year of historical event data.
- GuardDuty findings are a core source for accounts enrolled in GuardDuty. EKS audit logs require a separate source package.
Trap: EKS audit logs are not part of the core source package. Enable their separate package for the behavior graph.
From the AWS docs (4)
- Detective provides access to up to one year of historical event data.
- Detective core sources include CloudTrail logs, VPC Flow Logs and GuardDuty findings for accounts enrolled in GuardDuty.
- EKS audit logs are a source package that must be enabled for the behavior graph.
- Detective Investigation analyzes IAM users and roles for indicators of compromise.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 7 cards as a list
Which service helps investigate the root cause of a GuardDuty finding?
Amazon Detective. It connects activity over time in a behavior graph using core sources including CloudTrail, VPC Flow Logs and GuardDuty findings.
A security team needs to investigate related findings and affected resources together. What Amazon Detective feature helps?
Finding groups. They bring related findings and entities together for investigation.
A security team needs Amazon Detective to investigate suspicious activity across multiple AWS accounts. What can connect their data?
A behavior graph. An administrator can invite member accounts to contribute data.
Must a team configure its existing CloudTrail trail or VPC Flow Logs for Amazon Detective to consume its core event streams?
No. Detective uses independent streams and does not use existing logging configurations.
How much historical event data can Amazon Detective make available?
Up to one year.
Are Amazon EKS audit logs always included in the Amazon Detective core source package?
No. EKS audit logs are a separate source package that must be enabled.
What does Amazon Detective Investigation analyze for indicators of compromise?
IAM users and roles.