How we handle GDPR data-subject requests on a deadline
Legal
A daily sweep checks resources against policy for public buckets, untagged resources, and over-broad roles, files findings, and proposes remediation as a reviewed change rather than applying it.
Infrastructure drifts out of compliance quietly. A bucket gets made public for a one-off, a resource ships without its tags, a role picks up a permission it no longer needs. Each change is small and reasonable in the moment, but they accumulate, and nobody notices until an audit or an incident surfaces them all at once. By then reconstructing when each drift happened is hard.
We handle this by checking the infrastructure against policy every day, so drift surfaces the day it appears. This writes up how we run that on Kortix — the connections, the steps, and the guardrails — so you can set up the same sweep.
The common approaches each have limits. A quarterly manual audit finds drift late and in bulk, when the context is hardest to recover. A fixed rules engine catches the checks it was configured for and nothing beyond them. And auto-remediation that fixes drift on its own can break a service that depended on the very configuration it "corrected."
We wanted the infrastructure checked against policy daily, with findings filed where the team already works and fixes proposed as reviewed changes rather than applied silently.
On Kortix, a daily schedule triggers an agent. Each sweep runs in its own isolated session — a cloud sandbox — with scoped, read access to AWS and the audit logs. The agent checks resources against policy — public buckets, untagged resources, over-broad roles — and files what it finds to Slack. Remediation is proposed as a reviewed change, never applied automatically.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the compliance-sweep skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily compliance monitoring agent in this workspace.
Create the agent agents/compliance-monitoring.md. Its job is to check AWS against our compliance policy and propose fixes as change requests. It may use the AWS and Slack connectors. It only reads AWS.
Create the skill skills/compliance-sweep/SKILL.md with these rules:
Add a cron trigger daily-compliance-sweep to kortix.yaml. It runs the compliance-monitoring agent every day at 06:00 UTC with the prompt "Load the compliance-sweep skill, run one complete sweep, and post the findings to #security."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect AWS with read-only access and Slack. Credentials are brokered server-side and never enter the agent's machine.
Checks buckets, tags and IAM roles, and reads audit logs.
Posts findings with their audit trail and proposed fixes.
Tracks each finding as a ticket for its owner.
Merge the change request, then start a session with the compliance-monitoring agent and send this prompt. Review the change requests it opens before you let the schedule take over.
Run one compliance sweep on AWS. Read only.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 06:00 UTC, each run in a new session on its own cloud computer. To change the time, edit the cron line, or open
Triggers in the workspace.
triggers:- slug: daily-compliance-sweep name: Daily compliance sweep on: cron: "0 0 6 * * *" run: agent: compliance-monitoring prompt: Load the compliance-sweep skill, run one complete sweep, and post the findings to #security.The agent only reads AWS. Each fix arrives as a change request with the diagnosis and the proposed change. A person reviews it, merges it and applies it. Nothing changes in AWS without that review.
Each run ends with one message in the channel. This is what a run looks like in the session:
Found 3 findings: 1 newly public bucket, 1 resource without the owner tag, and 1 role with a wildcard grant. CloudTrail shows when each one changed and who changed it. 3 change requests with the proposed fixes wait for review.
Once it works, paste any of these into the same session.
Extend the policy to flag security groups that allow 0.0.0.0/0 on any port other than 443, in every region I list.
Every Monday, post the count of open findings by type to #security, and list the change requests that still wait for review.
Each month, write a dated summary of every finding and its fix to memory/compliance-evidence.md for audit review.
Giving an agent a standing view of the infrastructure is a trust question. The relevant controls on Kortix:
The drift that used to surface in bulk at audit time now arrives as small daily findings in Slack, each with a proposed fix a person reviews before it's applied. The team reviews a change instead of reconstructing months of drift, and the infrastructure stays close to policy.