StackShield + PagerDuty: Critical Laravel Security Incident Alerts
Create PagerDuty incidents automatically when StackShield detects critical security issues in your Laravel application.
Connect StackShield to PagerDuty to escalate critical security findings into your incident management workflow. When a scan detects a critical issue such as an exposed .env file, an accessible debug page, or a publicly reachable Telescope dashboard, StackShield can automatically create a PagerDuty incident that pages the on-call engineer. This ensures that the most dangerous security misconfigurations trigger an immediate response rather than sitting in a notification channel until someone notices.
Features
- Automatic PagerDuty incident creation for critical and high-severity security findings
- Configurable severity mapping so StackShield finding severities align with your PagerDuty urgency levels
- Incident details include finding description, affected URL, severity, and a link to the remediation guide
- Auto-resolve incidents in PagerDuty when StackShield confirms the issue has been fixed in a subsequent scan
Setup Guide
-
1
Create a PagerDuty Integration Key
In PagerDuty, go to the service you want to receive StackShield alerts on. Add a new integration using the Events API v2 and copy the integration key (routing key).
-
2
Configure PagerDuty in StackShield
In your StackShield dashboard, go to Settings, then Notifications. Select PagerDuty as a notification channel and paste the integration key. Choose which severity levels should create PagerDuty incidents (typically critical and high only).
-
3
Set Up Severity Mapping
Map StackShield severity levels to PagerDuty urgency. For example, map critical findings to PagerDuty critical alerts (which page immediately) and high findings to PagerDuty warnings (which follow your escalation policy).
-
4
Test the Integration
Send a test alert from StackShield to verify that a PagerDuty incident is created correctly. Check that the incident includes the expected details and triggers the right escalation policy.
Ideal Use Case
PagerDuty integration is designed for production-critical Laravel applications where security issues demand immediate attention from an on-call engineer. This is essential for SaaS platforms handling customer data, fintech applications processing transactions, and healthcare systems with compliance requirements. By routing only critical findings to PagerDuty and using Slack or email for lower-severity issues, you avoid alert fatigue while ensuring the most dangerous misconfigurations get an immediate response.
Frequently Asked Questions
Will I get paged for every scan?
No. PagerDuty incidents are only created when new critical or high-severity findings are detected (based on your configuration). Repeated scans that find the same known issue will not create duplicate incidents.
Does StackShield auto-resolve PagerDuty incidents?
Yes. When a subsequent scan confirms that a previously detected issue has been fixed, StackShield sends a resolve event to PagerDuty to automatically close the incident.
Can I use this with PagerDuty service-level rules?
Yes. Since StackShield creates standard PagerDuty events via the Events API v2, all of your existing PagerDuty service rules, escalation policies, and schedules apply to StackShield alerts.
Related Integrations
Opsgenie
Route StackShield security alerts through Opsgenie for on-call management, escalation policies, and incident tracking.
Slack
Get instant Slack notifications when StackShield detects security issues in your Laravel app. Channel-based alerts keep your entire team informed.
Webhooks
Push StackShield scan results to any HTTP endpoint via webhooks. Build custom workflows, feed dashboards, or trigger automated remediation.
Try StackShield Free for 14 Days
Start monitoring your Laravel application security in minutes. No installation required.
Start Free Trial