Customer safeguards
- Start with observation and measure false positives before blocking traffic.
- Maintain explicit allow rules for required partners, monitors, and search crawlers.
- Use staged rollout and rollback criteria for every enforcement change.
- Keep defensive traffic controls separate from vulnerability assessment workflows.
Review cycle
- Confirm the workspace, scope, and product access before a sensitive action.
- Review the product result with the accountable customer owner.
- Record the decision and assign follow-up work.
- Verify the outcome before closing the task.
- Revisit policies, access, and notification paths when the environment changes.
Get support
When contacting support about Cerberus, include the workspace, affected workflow, approximate time, and any visible correlation identifier.