Skip to main content
A trigger is whatever kicks off a pentest. Instead of running scans by hand every time, you set up a trigger once and let the platform decide when to run. Right now there’s one kind available, and two more on the way.

​
The three trigger types

1

Schedule trigger (available now)

The agent runs on a fixed cadence you pick. Daily, weekly, monthly, or custom if you need something the presets don’t cover. This is the default for most teams and it’s usually where you start.
2

Event-driven triggers (coming soon)

A scan fires when something security-relevant happens in your stack. A new CVE drops for a library you depend on, a new threat actor targets your industry, something interesting shows up in threat intelligence feeds. The platform watches and decides. Not available yet, but it’s coming.
3

Code change triggers (coming soon)

A scan fires when new code ships. You connect a repository, pick which branches to watch, and every deploy kicks off a targeted scan on the code that actually changed. Great for catching regressions before they reach your users. Also on the roadmap.

​
Setting up a schedule

When you pick Schedule, you get a frequency dropdown with four options: daily, weekly, monthly, and custom. Custom lets you set your own cadence when the presets don’t cover what you need. Weekly adds a second control where you pick which days of the week the scan should run on. You also choose a start time and a timezone. The agent kicks off at that time on every scheduled run. A typical scan runs for roughly six to twelve hours depending on your scan mode and how much surface area it’s covering, so pick a window where your traffic is light and your team isn’t planning any big deploys.