FAQ
How often can it check?
You set the cadence when you configure monitoring on a project. It is whatever re-validation schedule you choose for the findings you selected.
What is a regression?
A regression is when a vulnerability you marked fixed becomes exploitable again. It can happen when a code change reverts a fix, a dependency update reintroduces a patched vulnerability, or an infrastructure change exposes a mitigated attack vector.
Does monitoring cost credits?
Endpoint monitoring re-validates existing findings. It is a background validation of what you already found, not a full assessment. Get exact billing terms from Credits and billing.
How do I get alerted?
AISafe raises a notification when it detects a regression. You can connect Slack to receive the notification there, and you see the alert in the dashboard.
How does monitoring compare to a scheduled scan?
Monitoring re-validates the proofs-of-concept of known findings. A scheduled scan runs a full assessment that hunts for new vulnerabilities across your codebase. Monitoring keeps you current on what you know; scheduled scans catch drift and new issues. Many teams use both.
What happens when a finding regresses?
AISafe raises a regression event. The finding's status reverts to open (or AISafe creates a new finding, depending on your configuration). You then investigate the cause — recent code changes, dependency updates, or infrastructure changes — and fix the regression.
Does monitoring re-test every finding?
No. You choose which findings to monitor, for example all critical and high findings. You set this when you configure monitoring on the project.
Can monitoring find brand-new vulnerabilities?
No. Monitoring re-validates findings you already have. To find new vulnerabilities, run a new Black-Box Pentest or set up scheduled scans.