Product · Automated remediation
Fix issues the moment they land
Coming soon. AI-generated patches, approval workflows, automatic pull requests, and verification are planned. The examples below describe that workflow; the demos use sample data.
Security tools are good at finding problems and bad at closing them. Findings pile up faster than teams can fix them, and blanket auto-fixing is too risky to trust. RingZero's planned approach is configurable, human-in-the-loop remediation: the agent proposes — and can apply — fixes, but your org decides how much autonomy it gets, per severity, per project, and per oversight mode. The right issues get fixed fast; risky changes still get a human's eyes.
Three oversight modes, one dial
- Auto-apply — the agent applies the fix and verifies it. Still gated by your severity threshold; every apply is logged with its rationale.
- Approve-each — the agent prepares the fix; a human approves or rejects each one. Nothing changes without an explicit approval event.
- Watch-only — the agent notifies and never modifies code. For the services where "automated" should mean "informed", not "changed".
A severity threshold decides what the automation acts on at all — findings below it are recorded and skipped, not silently dropped — and prioritized projects jump the queue. Per-project overrides mean your payments service can run watch-only while everything else auto-applies low-risk fixes.
From finding to closed
Findings arrive from AI penetration tests, supply chain scans, and MCP config scans, and enter one pipeline: prioritize, propose a fix with AI context, then route by mode. Applied fixes are verified — built and tested, reverted and flagged if verification fails — and closing a finding updates your security score and severity counts live, so the feedback loop is visible.
Automation you can audit
Every step emits an audit entry: actor (agent or human), action, finding, fix, rationale,
timestamp. When an auditor asks "who changed this and why", the answer is a record, not a
reconstruction. The same approval pipeline handles code fixes and config fixes (like a
.mcp.json diff from an MCP finding), so there is one trail to review.
Watch the triage feed route findings live in the interactive demo, or see the approve-a-diff flow in the security workspace demo.
Frequently asked questions
Will RingZero change my code without asking?
Automated code changes are not available today. The planned workflow offers auto-apply, approve-each, and watch-only modes with project settings. The demo changes sample state only.
What will a proposed fix look like?
The preview shows a before/after diff alongside the finding, severity, and rationale. Generating patches and opening real pull requests are coming soon.
What is planned after a fix is applied?
The proposed workflow builds and tests a change, records the outcome, and reverts or flags a failed verification. Production verification and automatic rollback are not implemented yet.
Will remediation have an audit trail?
The planned trail records proposed, approved, applied, watched, and skipped actions with an actor, finding, rationale, and timestamp. The current demo illustrates those events with sample data.
Can I limit automation by severity or project?
The demo previews severity thresholds, project priorities, and oversight modes. Persisted policies and the production automation behind those controls are coming soon.