Amazon GuardDuty
cloud · amazonaws.com
Watched for drift — classified from the API's own spec; not yet a gate-proven pack.
<p>Amazon GuardDuty is a continuous security monitoring service that analyzes and processes the following data sources: VPC flow logs, Amazon Web Services CloudTrail management event logs, CloudTrail S3 data event logs, EKS audit logs, DNS logs, and Amazon EBS volume data. It uses threat intelligence feeds, such as lists of malicious IPs and domains, and machine learning to identify unexpected, potentially unauthorized, and malicious activity within your Amazon Web Services environment. This can include issues like escalations of privileges, uses of exposed credentials, or communication with malicious IPs, domains, or presence of malware on your Amazon EC2 instances and container workloads. For example, GuardDuty can detect compromised EC2 instances and container workloads serving malware, or mining bitcoin. </p> <p>GuardDuty also monitors Amazon Web Services account access behavior for signs of compromise, such as unauthorized infrastructure deployments like EC2 instances deployed in a Region that has never been used, or unusual API calls like a password policy change to reduce password strength. </p> <p>GuardDuty informs you about the status of your Amazon Web Services environment by producing security findings that you can view in the GuardDuty console or through Amazon EventBridge. For more information, see the <i> <a href="https://docs.aws.amazon.com/guardduty/latest/ug/what-is-guardduty.html">Amazon GuardDuty User Guide</a> </i>. </p>
Install
watched · not yet packagednpx verifyport add amazonaws-com-guardduty --lang python npx verifyport add amazonaws-com-guardduty --lang go npx verifyport add amazonaws-com-guardduty --lang node Agent trust (law 4)
the agent verdict →Usable, but spec-monitored only — not behaviorally proven yet.
Behavioral replay
No live replays yet — this connector is spec-monitored. Behavioral proof arrives with credentialed, read-only replay.
Drift timeline
No drift recorded yet — the spec has held its shape.
Spec history
- 16h ago 67 tools CLEAN:67 residual 0%