Guard Center
Findings tell you what went wrong yesterday. Guards stop it happening again tomorrow, and turning one straight to "block" is how you break a release on a Friday.
Guard Center is built around that fear. Every policy starts by watching, and only blocks once you trust it.
Two families of policy
Every policy belongs to one family, fixed when you create it.
| Family | When it acts | Examples |
|---|---|---|
| Assurance | Evaluates resources Dwaar already knows, from their findings, settings and scans, and marks each one compliant or non-compliant. | A pull request, a promotion, Kubernetes admission, an agent release, a vendor review. |
| Runtime | Acts on live events reported by a guard, and logs or blocks each one. | A request, a tool call, a process, an install. |
A policy's controls only run at checkpoints of its family.
Dwaar evaluates assurance policies itself today, from your findings, scans, settings posture and vendor reviews. See Assurance policies. Runtime policies need a guard at the moment something happens, so their controls show as Needs a guard until one is installed.
Three modes
| Mode | On a failure |
|---|---|
| Observe | Nothing visible happens to the resource. The policy shows which resources are non-compliant. You are measuring. |
| Audit | The failure becomes an event, and the people who follow it are notified. |
| Enforce | As audit. For an assurance policy, that is all enforce does today: Dwaar does not change anything outside itself. |
The right rollout is observe, then audit, then enforce. Turn on Ask to enforce after clean days and Dwaar tells you when a policy in audit has gone that many days without a failure. It never enforces on its own: a person with permission to enforce promotes it.
Some actions are destructive and are never a default: auto_remediate, reconcile, revoke and kill. Choose them deliberately.
The tabs
- Policies lists your policies, with the scope of each, its mode and its compliance.
- Events lists the controls failing on your resources, open first. See Events and exceptions.
- Controls lists every control a policy can use, per resource type.
- Rego imports brings in Open Policy Agent policies. See Import Rego policies.
- Exceptions holds the agreed departures from a policy, waiting for approval or active until they end.
- Live guards shows the enforcement points and whether each is healthy.
- Settings configures guard behavior per resource type.
Try this next
Open the Code baseline policy, which every tenant starts with in observe, and read which resources it finds non-compliant. When the list looks right, move it to audit and read Events and exceptions before anyone else gets notified.