A scheduled job reads an identity provider’s configuration each day, compares it with settings a person approved in Git, stores the result as locked audit evidence, and posts to a chat channel. Okta is the system it watches. The same pattern applies to any system with a read API.
A read-only credential makes GET requests to the vendor API. The responses are saved as one JSON snapshot.
Deeply nested rules reduce to one readable line each, with a trailing hash over the whole rule so any change shows.
The snapshot is checked against YAML baselines in Git. Each baseline setting ties to a policy statement, a control, and an approver.
The snapshot, its hash, the run record, and the baselines used go to a bucket with a locked retention policy.
A chat message lists each finding. A clean run posts one all-clear line, so a missing line shows that nothing ran.
- id: min-length description: Minimum password length policy: Password Policy, section 4.1 control: ACCESS-01 path: 'password_policies[name=Example Policy].settings.password.complexity.minLength' operator: gte expected: 14
The same inputs always produce the same answer. AI takes no part in deciding whether a result is clean, drifted, or an error.
A setting the script cannot find counts as drift, so a renamed or removed field raises a finding.
If the collection did not finish, the run reports an error and never a pass.
A baseline with no approver refuses to run, so a generated draft cannot take effect before a person reviews it.
The writing account can only create new objects, and retention blocks deletion until the audit period ends. Whoever changes a baseline cannot edit the evidence of a past run.
An auditor can download a run folder, check out the commit named in the run record, and reproduce the result without contacting the vendor.
Platforms offer prebuilt connectors and mapped tests. Their tests follow generic wording, and this job follows the exact wording of the policy. The two can run together, with the platform covering breadth and the monitor covering specific settings.
Terraform makes a system match a declaration, which requires write access. A read-only monitor can also verify changes that Terraform or a person makes.
A screenshot proves one moment. A daily snapshot with a hash proves the whole period.
The work started from a single policy statement and the API endpoint that holds the matching setting.
Three to five settings expressed the sentence, and a pull request approved them.
Each check ran against edited copies of real data. Every break produced a specific, readable finding.
The evidence bucket and chat message came after the comparison ran cleanly.
A setting outside the baselines changes without notice. The monitoring documentation lists coverage so the claim stays accurate.
A change can sit until the next run. The daily cadence sets the detection window.
Some settings have no read endpoint, and the check cannot see them.
Where a policy leaves a term undefined, the baseline can record what exists and cannot say whether it is right.