Some work never fits in one run. Keeping an application free of vulnerable dependencies means scanning every night, fixing what can be fixed, waiting for a person to approve the change, checking that the fix really landed, and chasing the finding when nobody answers. A harness runs that whole process for you.
A harness is one template that says which bot handles each step in the life of a piece of work, where the work goes next, and what the limits are. The bots do the thinking. The harness does the moving, waiting, counting and remembering.
When to use a harness
Use a harness when the outcome spans many runs, tools and owners, and different pieces of work need different routes. For a fixed sequence of steps that runs the same way every time, a workflow is simpler. Choosing a workflow or a harness compares the two with examples.
| Team | A harness that... |
|---|---|
| AppSec | scans a repository nightly, fixes vulnerable packages in one pull request per change, waits for the merge and re-scans to prove the fix |
| SOC | groups user-reported phishing by campaign, triages it, contains and purges after approval, and watches sign-ins for 24 hours |
| GRC | collects evidence for every control that is due, reviews it against the control and sends gaps to the control owner |
| Identity | checks risky grants for real use, asks the owner, revokes with approval and confirms the access is gone |
| Cloud posture | fixes misconfigurations through infrastructure-as-code pull requests and re-checks the rule |
How a harness works
Here is one night of an AppSec harness:
- Work comes in. At 02:00 the scanner bot (an input) runs and records 28 findings as tasks in Guardian.
- Findings are grouped. The harness waits until the scan finishes, then bundles related findings into one group task, so one scan becomes one fix instead of 28.
- The fix stage runs. The fix bot gets the whole group, updates the packages, opens a pull request and reports a result for every finding.
- The task waits for the merge. The harness parks the task and listens to your repository. No bot runs, and nothing is spent, while it waits.
- The verify stage proves it. After the merge, a different bot re-scans and marks each finding fixed or not fixed. Fixed findings close; the rest go back for the next round.
- Stalls escalate. If nobody acts in time or the deadline passes, the task moves to an escalation stage that asks a person.
- Regressions reopen. If a closed finding is seen again within 30 days, its task reopens instead of a new one being created.
Every move is written to the task's timeline, and every real action, such as a pull request opened or a message sent, is recorded under What it did on the task.
The parts of a harness
| Part | What it is |
|---|---|
| Application | What the harness looks after, such as payments-api. Its tasks and bots belong to it. |
| Input | A bot that brings work in: a scheduled scanner, a webhook, or a list of what is due. It only records tasks; it never fixes anything. |
| Task | One piece of work, such as one finding or one alert. The same tasks you see in Guardian. |
| Group | Related findings bundled into one task, so they get one fix and one approval. |
| Stage | One step in a task's life, such as triage, fix, approve, verify or escalate. Each stage runs one bot. |
| Transition | A rule that moves the task on: "if the fix bot reports pr_opened, go to the merge stage". |
| Interrupt | A rule that can move a task from any stage: "if the deadline passes, escalate". |
| Reaction | A bot that runs on the side without moving the task, such as notifying an owner. |
| Limits and policy | How often a stage may repeat, how many bots run at once, a monthly budget, deadlines per severity, and which tools need a person's approval. |
| Memory | A memory space where the harness's bots keep notes, raw results and history. |
The full template format is in Harness templates.
Harness types
The type of a harness sets the limits of what its bots may ever do. An AppSec harness, for example, can never delete user accounts, whatever its bots are allowed elsewhere.
| Type | For |
|---|---|
appsec | Vulnerabilities in code, dependencies, containers and running applications |
soc | Alerts and incidents, such as reported phishing |
grc | Control evidence and compliance gaps |
iamops | Access reviews and identity hygiene |
cloud_posture | Cloud misconfigurations |
finops | Cost anomalies |
generic | Anything else |
Who builds a harness
You describe the outcome to Optimus, and Optimus builds the harness with you: it asks its questions in one go, writes a plan for you to approve, creates the bots, writes the template and tests it safely before you switch it on. Start from Build a harness on Guardian > Harnesses: pick a ready template or start from scratch, and Optimus opens with the request filled in. See Build a harness.
To run the same harness on many applications, save it as an org template; it is proposed on every matching application. See Roll a harness out with an org template.