Menu

Drift Is the Audit Finding: Detecting Network Configuration Drift Across Clouds Before an Auditor Does
📰

Drift Is the Audit Finding: Detecting Network Configuration Drift Across Clouds Before an Auditor Does

DEV Community: security·OneLifeVibe·about 13 hours ago
#OlKIkdEs
#devtosecurity#devto#dev#cloud#drift
Reading 0:00
15s threshold

Every multi-cloud estate has two networks. One lives in code: the route tables, security groups, firewall rules, DNS zones, and interconnect settings declared in Terraform, Pulumi, or a pile of reviewed change tickets. The other lives in the clouds themselves, and it changes a little every week. Someone opens a port during an incident and forgets to close it. A console fix solves an outage and never makes it back into code. A vendor adds a route during a maintenance window. None of it feels like a security event at the time. Months later, in a SOC 2 observation window, it becomes one: the estate cannot show that the network running today is the network that was approved.

Drift is rarely dramatic. That is exactly why it survives. The work is not finding one bad rule.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.