IT OPS

Control-config drift detection against a screenshot baseline

On a daily cadence, recaptures security-config dashboards, compares each against its approved baseline image.

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily drift-check schedule fires
  • ActionRecapture config dashboard screenshotBrowserbase
  • ActionCompare capture to approved baselineOpenAI
  • LogicBranch on drift detected vs. unchanged
  • ActionOpen drift incident for on-callPagerDutyPagerDuty
  • OutputArchive capture to S3 audit trailAWS S3

What it does

Guards against silent config drift between audits. Each day it recaptures the security-configuration screens (encryption, retention, firewall rules), compares each new screenshot to the approved baseline using an image-and-text comparison, and raises an incident when a control no longer matches its sanctioned state.

When to use it

When a control passing at audit time isn't enough and you need continuous assurance that someone didn't quietly disable MFA enforcement or change a retention setting between review cycles.

How it works

  1. 1A daily schedule fires.
  2. 2Browserbase recaptures each monitored config dashboard.
  3. 3An OpenAI step compares the new capture and extracted settings against the stored baseline and classifies whether the control drifted.
  4. 4A logic step branches: matched controls are logged quietly; drifted controls continue.
  5. 5PagerDuty opens an incident for the on-call compliance engineer with the before/after images.
  6. 6The new capture is archived to S3 for the audit trail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BrowserbaseHeadless browsers, sessions, replays.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Connect AWS S3Buckets, objects, signed URLs.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.