- Newest
- Most votes
- Most comments
NIST alignment with logs is all about giving clarity and point blank info about the events. As you have mentioned, the volume of VPC flowlogs and cloud trail are huge for a SIEM system to consume. This dilutes the info and increases the cost of SIEM. In most cases (I assume same here) customers read data from the S3 buckets or cloudwatch via API which is huge and time consuming.
A suggestion here is to filter and upload only the significant events to SIEM. Can be a lambda which runs periodically and uploads the small delta to SIEM or colud also be athena that reads the VPC logs and exports the precise findings to SIEM for analysis.
Example filters for VPC flowlogs: REJECT logs Repeated repeated logs filter vulnerable port traffic
Example filters for CloudTrail Filter critical events like. SPOT fleet creation, user creation, resource creation in an unused region, key rotations etc.
Hope this helps.
Relevant content
- asked 2 years ago
- asked 9 years ago
- asked 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago