GuardDuty#
Client#
- class GuardDuty.Client#
A low-level client representing Amazon GuardDuty
Amazon GuardDuty is a continuous security monitoring service that analyzes and processes the following foundational data sources - VPC flow logs, Amazon Web Services CloudTrail management event logs, CloudTrail S3 data event logs, EKS audit logs, DNS logs, Amazon EBS volume data, runtime activity belonging to container workloads, such as Amazon EKS, Amazon ECS (including Amazon Web Services Fargate), and Amazon EC2 instances. 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.
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.
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 Amazon GuardDuty User Guide .
import boto3 client = boto3.client('guardduty')
These are the available methods:
- accept_administrator_invitation
- accept_invitation
- archive_findings
- can_paginate
- close
- create_detector
- create_filter
- create_ip_set
- create_malware_protection_plan
- create_members
- create_publishing_destination
- create_sample_findings
- create_threat_intel_set
- decline_invitations
- delete_detector
- delete_filter
- delete_invitations
- delete_ip_set
- delete_malware_protection_plan
- delete_members
- delete_publishing_destination
- delete_threat_intel_set
- describe_malware_scans
- describe_organization_configuration
- describe_publishing_destination
- disable_organization_admin_account
- disassociate_from_administrator_account
- disassociate_from_master_account
- disassociate_members
- enable_organization_admin_account
- get_administrator_account
- get_coverage_statistics
- get_detector
- get_filter
- get_findings
- get_findings_statistics
- get_invitations_count
- get_ip_set
- get_malware_protection_plan
- get_malware_scan_settings
- get_master_account
- get_member_detectors
- get_members
- get_organization_statistics
- get_paginator
- get_remaining_free_trial_days
- get_threat_intel_set
- get_usage_statistics
- get_waiter
- invite_members
- list_coverage
- list_detectors
- list_filters
- list_findings
- list_invitations
- list_ip_sets
- list_malware_protection_plans
- list_members
- list_organization_admin_accounts
- list_publishing_destinations
- list_tags_for_resource
- list_threat_intel_sets
- start_malware_scan
- start_monitoring_members
- stop_monitoring_members
- tag_resource
- unarchive_findings
- untag_resource
- update_detector
- update_filter
- update_findings_feedback
- update_ip_set
- update_malware_protection_plan
- update_malware_scan_settings
- update_member_detectors
- update_organization_configuration
- update_publishing_destination
- update_threat_intel_set
Paginators#
Paginators are available on a client instance via the get_paginator method. For more detailed instructions and examples on the usage of paginators, see the paginators user guide.
The available paginators are: