Safeguard Loop
The continuous detect, prioritize, fix and verify cycle across scanning, AutoTriage, Griffin AI and remediation.
Safeguard Loop
Safeguard Loop is the name for the continuous cycle Safeguard runs on your software: detect issues, prioritize them, fix them, verify the fix, and repeat. It is not a separate engine. It is how the capabilities below work together.
The stages
| Stage | Capability | What it does |
|---|---|---|
| Detect / Prevent | Package Firewall | Evaluates dependencies at install time and can allow, warn, block, or quarantine typosquats, dependency confusion, and known-malicious packages before they land. A quarantined package is re-evaluated and released once its verdict clears. |
| Prioritize | AutoTriage | Deduplicates overlapping findings across scanners into a single correlated view. |
| Prioritize / Recommend | Griffin AI | Safeguard's security model prioritizes findings by reachability, exploitability, context, and business impact, and generates remediation: upgrade recommendations, dependency conflict resolution, breaking-change analysis, and pull requests. |
| Fix | Auto-Fix (AI Remediate) | Griffin-powered analysis, solution generation, impact assessment, pull request creation, and validation for vulnerable dependencies, across single, bulk, and page-level remediation. |
| Fix / Verify | Self-Healing Containers | Runs its own Detect, Plan, Rebuild, Promote loop for container images. |
Following one issue
A vulnerable dependency is found by scanning, deduplicated by AutoTriage, given a Griffin AI fix, and turned into a pull request by Auto-Fix. Follow it through each engine's own view: the correlated finding, the recommendation, and the pull request status.