Change Triggers

Change triggers watch for changes in your infrastructure and automatically launch pentests when something changes — ensuring continuous security coverage.

Supported providers

Setting up a change trigger

1. Go to Settings > Change Triggers
2. Click New Trigger
3. Select a provider
4. Configure the connection details
5. Set the poll interval (5 min, 15 min, 30 min, or 1 hour) for polling-based providers
6. Enable the trigger

ServiceNow advanced filtering

For ServiceNow, you can filter which changes trigger pentests:

• Table: Change Requests, Incidents, or Problems
• Change types: Normal, Emergency, Standard
• Minimum priority: 1 (Critical) through 4 (All)
• Categories and assignment groups: Comma-separated lists
• Configuration items: Filter by specific CIs
• Custom SYSPARM query: Advanced ServiceNow query for fine-grained control

Webhook-based providers

For GitHub, GitLab, and Generic Webhook:

1. CodeWall provides a webhook URL
2. Configure your platform to send events to that URL
3. Optionally set a webhook secret for signature verification
4. CodeWall triggers a pentest when it receives a matching event

How it works

When a change is detected:

1. The trigger evaluates the change against your filters
2. If it matches, CodeWall launches a pentest using the associated test configuration
3. The test runs like any other pentest, producing findings and reports
4. Results are linked to the triggering change for traceability