Amazon AWS
DEFEND can collect and analyse several types of AWS Logs. For most AWS services, these are collected from an S3 bucket within your AWS account, using IAM credentials. By default, the SOC will delete logs delivered to S3 once they have been collected.
Configuration Steps
The high-level steps for enabling the SOC to ingest the logs are:
- Create an S3 bucket in which to store logs
- Enable logging to S3 in the desired services.
- Set the S3 bucket prefix to the name of the S3 service as shown below.
- Create an IAM user called “foxtech-soc” or similar, with permissions to read and delete files from the S3 bucket.
- Provide Support with:
- AWS Access Key ID
- AWS Secret Access Key
- S3 Bucket Name
- Services being logged (from below)
AWS Services using Logging to S3
Cloudwatch Logs
CloudWatch Logs does not integrate pass logs to an S3 bucket, but instead they DEFEND will fetch the selected log groups you specify directly through the AWS APIs.
For DEFEND to process these:
- Create an IAM account through which to fetch the logs
- Grant the IAM account permissions to read the chosen CloudWatch log groups
- Provide Support with the list of log groups to be fetched. By default, we’ll fetch that log group from all regions.
Generally, we recommend enabling at a minimum CloudTrail and S3 Server Access Logs and VPC flow logs.