Configurable drift detection interval per building block definition
Florian Nowarre
As a platform engineer, I want to set how often drift detection runs for each building block definition.
## Problem
Drift detection currently runs once every 24 hours. For security-relevant resources like storage buckets or Key Vaults, that gap is too long. If someone changes such a resource by hand, for example in the Azure Portal, it can stay misconfigured for up to 24 hours
before meshStack notices. A storage bucket accidentally made public or a weakened Key Vault access policy can cause a serious security incident in that time.
## Proposed solution
- Let platform engineers set the drift detection interval on each building block definition, e.g. every 15 minutes, hourly or daily.
- Keep the current 24h interval as the default, so existing definitions behave the same.
- Optionally, allow a shorter interval for selected building blocks only, to keep load and cloud API costs under control.
## Value
- Misconfigurations on critical resources are found within minutes instead of hours.
- Platform teams can match the detection frequency to how critical each resource is.
- Helps meet compliance requirements that ask for timely detection of configuration changes, e.g. ISO 27001, BSI C5 and DORA.
Photo Viewer
View photos in a modal