Runtime Workload Monitoring
Introduction
Controlling risks in the value stream is the first level of software process compliance. Also, it is crucial to have a monitoring process in place to identify unknown or non-compliant workloads in production.
Implementation of this control
We maintain a full forensic history of all container runtimes, lambda functions, and S3 buckets using Flarekit environments.
Unauthorized or non-compliant workloads are recorded and trigger alerts in our Slack channels, ensuring prompt action and compliance.
Last updated