Governance
Governance is Furl’s system for controlling whether a remediation runs automatically or requires human approval. It’s a layered evaluation that balances organizational policy with individual preferences, and it can only tighten controls — never loosen them.
How governance works
Section titled “How governance works”When a strategy execution is about to be created, the governance evaluator runs a two-layer check.
Layer 1: Organization rules
Section titled “Layer 1: Organization rules”Org-wide policies set by administrators:
| Rule | Effect |
|---|---|
| Global pause | All remediations blocked across the org |
| Blackout windows | No remediations during specified time periods (e.g., change freeze) |
| Confidence threshold | Strategies below a confidence score threshold require approval |
| Autonomy rules | Conditional rules (e.g., “auto-execute critical findings, require approval for low”) |
Layer 2: Owner preference (autonomy)
Section titled “Layer 2: Owner preference (autonomy)”Every endpoint has an owner, and every person has a personal autonomy preference that controls how much automation Furl applies to devices they own.
| Preference | Meaning |
|---|---|
| Org default | Follow whatever Layer 1 decided |
| Auto-execute | Allow automatic remediation (Layer 1 can still block) |
| Require approval | Always require approval, regardless of Layer 1 |
Key principle: can only tighten
Section titled “Key principle: can only tighten”Each layer can make the decision more restrictive, but never less:
- Org says auto-execute + person says require approval = require approval
- Org says require approval + person says auto-execute = require approval
- Org says auto-execute + person says auto-execute = auto-execute
Governance outcomes
Section titled “Governance outcomes”| Outcome | What happens |
|---|---|
| Auto-execute | The strategy proceeds immediately |
| Require approval | An execution is created with pending_approval status; the end user is notified |
| Blocked | A global pause or blackout window is active; the execution is deferred |
The approval experience
Section titled “The approval experience”When governance requires approval, the endpoint owner sees the pending remediation in the end-user portal with three options:
- Approve — the remediation proceeds.
- Reject — the remediation is cancelled (with an optional reason).
- Defer — “remind me later”; Furl re-notifies after a delay.
If no action is taken before the severity-based deadline, the request is escalated to administrators.
Related
Section titled “Related”- Strategy Executions — governance determines execution status
- Confidence Score — governance can gate on confidence threshold
- Remediation Scopes — scopes trigger the pipeline that evaluates governance