Continuous monitoring

GRC platforms such as Vanta and Drata connect to the systems where controls actually live — AWS, Google Workspace, Okta, GitHub, your MDM — and run automated tests against each on a recurring cycle, often hourly or daily. Each test encodes a control expectation: every laptop encrypted, every repo requiring review, every user behind MFA. Passing tests double as evidence collection, since the platform records proof continuously; failing tests become alerts with a specific system and resource attached.

Monitoring is superb at technical drift and blind to everything that lives outside an API: vendor risk reviews, security training completion, tabletop exercises, exception write-ups. Those controls still need a human cadence, which is why a dashboard full of green checks is necessary but not sufficient.

The subtler failure mode is alert decay. Monitoring only tells you something broke — someone still has to triage the alert, fix the resource, and mark it closed, and unattended dashboards rot into hundreds of ignored failures within a quarter. Keeping the loop closed is the operator half of the system: it is the mechanism behind continuous compliance, and it is exactly the work a Managed Vanta engagement takes off your team.

Auditors like platform-generated test results because they are timestamped, tamper-resistant, and cover the full period rather than a hand-picked sample. A year of green checks becomes a substantial slice of your evidence package, shrinking the manual portion of the PBC list. The inverse also holds: a monitoring history full of long-lived red gives the auditor a documented record of every week a control sat broken.