If you’re using AWS WAF as a web application firewall, you can ship its alerts to your Logz.io Cloud SIEM.
Configure AWS WAF to enrich observability
The first thing you’ll need is to add a rule to your AWS WAF to send all HTTP request logs.
- Open your AWS WAF admin console. Go to your web ACLs screen and select the relevant Region.
- Select an ACL that you can add your own rules to.
- In the ACL screen, open the Rules tab, add your own rule, and fill in the details:
- Rule type - Select Regular Rule.
- Use the OR separator.
- Next, create a statement with the following fields:
- Inspect: HTTP method
- Match type: Starts with string
- String to match: GET
- Add additional statements, separated by OR for every HTTP method you would like to monitor. At the very least, we recommend monitoring GET and POST methods.
- Then - Select the Count action.
- Save the rule.
- Adjust the rule’s hierarchy, if relevant. If the ACL has other rules, it is recommended that this rule be as high in the hierarchy as possible, taking the other rules’ logic into consideration.
Configure AWS WAF to send logs to an S3 Bucket
You’ll first need to make sure all your logs are being written to an S3 bucket.
- In your AWS WAF console, go to your web ACLs screen. Select the web ACL you would like to send logs from.
- Set the web ACL to send its logs to an S3 bucket.
Configure Logz.io to read AWS WAF logs from an S3 Bucket
You’ll want to configure the S3 Bucket to allow Logz.io to periodically read log files from the appropriate bucket.
Before you begin, you’ll need:
- A user with permissions to list the buckets on the relevant S3 Bucket.
- Permission to Get from all the paths under the bucket name.
If you run into issues, you can reference the guide for troubleshooting user permissions.