Troubleshooting¶
Having issues with Parapet Security? This guide covers common problems and their solutions.
Common Issues¶
-
Alerts Not Arriving
Your SIEM is configured but alerts aren't appearing in Parapet Security.
-
Webhook Errors
Getting HTTP errors when your SIEM tries to send alerts.
-
Common Issues
Other frequently encountered problems and solutions.
Quick Diagnostics¶
Run through this checklist before diving deeper:
1. Check Service Status¶
Visit our status page: status.parapetsecurity.com
If there's an outage, you'll see it there.
2. Verify Your Token¶
- Go to Settings → Service Tokens
- Check that your token exists and isn't expired
- If in doubt, generate a new token
3. Test Webhook Connectivity¶
curl -X POST https://webhook-us.parapetsecurity.com/webhook/YOUR-TENANT-ID \
-H "Authorization: Bearer pst_YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"source": "test", "test": true}'
Expected response:
4. Check SIEM Configuration¶
- Is the webhook URL correct?
- Is the token included in the Authorization header?
- Is the SIEM generating alerts (check SIEM logs)?
Error Reference¶
HTTP Status Codes¶
| Code | Meaning | Solution |
|---|---|---|
202 | Success | Alert accepted - working correctly |
400 | Bad request | Check JSON syntax |
401 | Unauthorized | Token invalid or expired |
403 | Forbidden | Token revoked or wrong tenant |
404 | Not found | Check webhook URL |
413 | Payload too large | Alert exceeds 1MB limit |
429 | Rate limited | Slow down or upgrade plan |
500 | Server error | Retry, contact support if persists |
503 | Service unavailable | Temporary outage, retry |
Error Messages¶
| Message | Meaning | Solution |
|---|---|---|
invalid_token | Token not recognized | Check token value |
token_expired | Token past expiry | Generate new token |
tenant_not_found | Tenant ID invalid | Check webhook URL |
rate_limit_exceeded | Too many requests | Wait and retry |
invalid_json | Malformed JSON | Validate JSON syntax |
Getting Help¶
Before Contacting Support¶
Gather this information:
- Tenant ID (first 8 characters only)
- HTTP response code and body
- Timestamp of the issue
- SIEM platform and version
- Steps to reproduce
Contact Methods¶
| Method | Best For | Response Time |
|---|---|---|
| Non-urgent issues | 24-48 hours | |
| Slack | Quick questions | During business hours |
| Status page | Checking outages | Real-time |
- Email: support@parapetsecurity.com
- Slack: parapetsecurity.slack.com
- Status: status.parapetsecurity.com
Self-Service Resources¶
- SIEM Integration Guides - Platform-specific setup
- Getting Started - Initial configuration
- Notification Settings - Alert delivery
- Dashboard Guide - Using the interface