Source
Platform reliability, security & compliance — found from sitemap — Rootly
Checked for Rootly on 6 Nov 2026
- Page
- https://rootly.com/incident-response/security-incident-management
- Checked
- 6 Nov 2026, 04:47 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:74cd9509a5f14ae88ed4f094e50cfbac8ca8ff997d7806b28fa4896ca9f5bc33
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Private incidents Report an error
“A private incident adds incident-level access on top of role-based access control. Users see it only if their role grants private-incident read access or if a responder adds them. You can mark an incident private when you declare it in Slack.”
-
Access management Report an error
“Add or remove people with /rootly access or the Manage Access dialog in Slack or on the web. Rootly attempts to invite added users to the incident channel, and its “remove unauthenticated users” option removes anyone without private-incident permission.”
-
Security incident types Report an error
“Incident types such as “Security Event” can drive workflow conditions, so a security incident notifies the security team, attaches the right playbook and starts its own retrospective process.”
-
Splunk alert source Report an error
“Splunk is an alert source, and any detection tool that can send an HTTP request can use the generic webhook alert source. Expel is listed on Rootly integrations for managed detection and response alerts.”
-
Custom incident roles Report an error
“Define security-specific incident roles such as security lead or legal counsel, and assign them from Slack or the web.”
-
Incident timeline Report an error
“The incident timeline records events, decisions and status changes. If you declare after detection, update the incident timestamps so the record matches when you became aware.”
-
Jira followups Report an error
“Create remediation action items in Jira so they stay visible after the incident closes.”
-
SOC 2 audit records Report an error
“For audit evidence, see audit-ready incident records for SOC 2.”
-
Slack declaration Report an error
“You can mark an incident private when you declare it in Slack.”
-
Role based access control Report an error
“A private incident adds incident-level access on top of role-based access control.”
Scores citing this record
- The Engineering Manager Incident response, status pages & post-incident review
- The ICT Risk Officer Incident response, status pages & post-incident review
- The IT Operations Manager Incident response, status pages & post-incident review
- The MSP NOC Lead Incident response, status pages & post-incident review
- The MSP NOC Lead Platform reliability, security & compliance
- The Skeptic Incident response, status pages & post-incident review
- The SRE Lead Incident response, status pages & post-incident review