Client: SentinelEdge · SaaS & B2B Software · US cloud security SaaS (130 staff)
Faster Alert Triage for a Security Platform
TechSupport Team helped SentinelEdge tune production alerts and triage for its cloud security platform. Over five months, client Jira Service Management records show triage time falling from 18 to 3 minutes. The client’s security lead approved alert rule changes.
Client and engagement facts
- Client
- SentinelEdge
- Industry
- SaaS & B2B Software
- Business context
- US cloud security SaaS (130 staff)
- Delivery model
- Alert triage and runbook engineering
- Application
- Cloud security monitoring and triage
- Supplied geography
- US
- Company size in source
- 130 staff
Related services: DevOps support
Application stack and tools
Application stack
- Python
- Elastic
- AWS
- SIEM
Tools used
- Jira Service Management
- PagerDuty
- Datadog
- client SIEM
Why Support Was Needed
Duplicate rules and stale conditions sent too many alerts to analysts. The team reviewed the rules against observed incident patterns and documented a clear action for each retained class.
Technical Work
- Removed 600 noisy rules over the first two months under the client’s rule approval process.
- Rebuilt triage runbooks around 40 observed incident patterns.
- Added measures for the client to review triage work.
Representative Incident
One removed rule left a 12-minute coverage gap. The team restored the rule with tighter conditions and recorded the change in the incident register.
Results and how they were measured
| Metric | Baseline | Result | Units | Measurement window | Source and scope |
|---|---|---|---|---|---|
| Triage time | 18 min | 3 min | min | 5 months | Client JSM |
| False-positive escalation | 41% | 12% | % | 5 months | Client PagerDuty |
| Detect-to-notify | 25 min | 6 min | min | 5 months | Client Datadog |
Evidence and Limitations
The five-month comparison excludes a SIEM vendor outage. The triage and notification measures describe the client’s incident workflow.
Alert Rule Approval
TechSupport Team proposed and documented the rules. SentinelEdge’s security lead approved each change.
Scope a Similar Engagement
Share the alert classes that consume investigation time and the review process for changing rules. Request a support plan or explore DevOps support.
Get a technical support plan
Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.
- We reply by email.
- We agree a call about the roles, your stack and the hours.
- If there is a fit, we propose engineers after an assessment.