Skip to main content

Monitor for regressions

Set up monitoring on a project to catch security regressions: cases where a fixed vulnerability turns exploitable a second time.

Prerequisites​

  • A plan that includes monitoring (Pro or Enterprise)
  • An AISafe account with the manager role or higher
  • A Project with at least one verified black-box target
  • At least one completed black-box or white-box assessment on the project with a confirmed finding that carries a proof-of-concept or reproduction steps

What is a regression?​

A regression occurs when a fixed finding turns exploitable once more. This can happen when:

  • A fix is reverted or circumvented by a subsequent code change
  • A dependency update reintroduces a vulnerability patched in a prior release
  • An infrastructure change exposes an attack vector mitigated in a prior release

Monitoring catches these, so you do not have to wait for the next scheduled scan or a real attacker to discover them.

Step 1: Open the project​

  1. Navigate to Projects in the AISafe dashboard.
  2. Open the project you want to monitor.

Step 2: Enable monitoring​

  1. Open the project's Monitoring tab.
  2. Toggle Enable monitoring.
  3. Set the interval between runs, from 1 to 90 days (the default is 7).
  4. Save the monitoring settings.

You do not choose findings one by one. AISafe monitors every qualifying finding, up to 50 per project, and the panel lists them. See Which findings are monitored.

Step 3: Set up regression alerts​

To receive a notification when AISafe detects a regression:

  1. Connect Slack and enable monitoring regression notifications.
  2. Or configure an outbound webhook in your dashboard so the monitoring.regression event reaches your own tooling.

After AISafe detects a regression, it:

  1. Changes the finding to not fixed.
  2. Raises a monitoring.regression event.
  3. Posts a Slack notification (if configured).
  4. Fires any matching outbound webhook subscriptions you have set up.

Step 4: Respond to regressions​

After you receive a regression alert:

  1. Open the finding in AISafe to see the regression details. The finding keeps the code you already use in tickets and exports.
  2. Investigate the cause: check recent code changes, dependency updates, or infrastructure changes.
  3. Fix the regression. The next monitoring run re-tests the finding and sets it back to fixed once the issue no longer reproduces.

If a target is not verified​

Monitoring tests the project's black-box targets, so every one of them must be verified for your organization (see Domain ownership). Turning monitoring on is refused while a target is unverified, and the message names the hosts. If a target stops being verified, for example after you add a new host to the project, monitoring pauses instead of failing every check, and it resumes on its own once every target is verified again.

If your plan changes​

If your plan stops including monitoring, monitoring is paused and shows Paused by plan. Its run history stays readable, nothing runs or is charged, and it resumes on its own when you upgrade. See Credits & billing.

Next steps​