Source
Security / trust page — Rootly
Checked for Rootly on 6 Nov 2026
- Page
- https://rootly.com/security
- Checked
- 6 Nov 2026, 04:45 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:9a38497552bfae3dceea0b154cc6fee73195efbf96049fb7935a5d6f670df428
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Rbac scope Report an error
“Granular RBAC across incident roles, services, teams, and components. Control exactly who sees what—across every stage of a sensitive investigation.”
-
Private incidents default Report an error
“Private incidents are invisible to the rest of the org by default. Access is invite-only, access-controlled end-to-end, and never something somebody accidentally stumbles into.”
-
Audit logging Report an error
“Every action, decision, and escalation is logged to a single incident record in real time—no reconstruction required when regulators come calling. Access logs included: who was granted entry, when, and when it was revoked.”
-
Count Report an error
“100+ integrations—SIEMs, SORARs, identity providers, on-prem systems—so your response process doesn't depend on swapping tools out.”
-
Rbac attributes Report an error
“Control exactly who sees and performs what actions across every stage of a sensitive investigation—by role, team, service, component, severity, and incident type.”
-
Just in time access Report an error
“Grant just-in-time access when an incident fires, revoke it automatically when it closes, and extend those permissions to connected docs without a single manual step.”
-
Severity permissions Report an error
“Permission to set incident severity values Whether severity can be set when creating an incident, or based on its current severity.”
-
Dual slack channels Report an error
“Run security incidents across two parallel Slack channels—one for technical response, one for legal and business—where incident updates flow one way but sensitive discussions never cross over.”
-
Isolated tenants Report an error
“If your InfoSec team needs full separation, Rootly supports isolated tenants so operations are entirely independent from the rest of the organization.”
-
Audit log UI sections Report an error
“Timeline Communications Tasks Follow-ups Status page Retrospective”
-
Supported severities Report an error
“SEV 0 SEV 1 SEV 2 SEV 3 SEV 4”
2 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Engineering Manager Integrations, API & administration
- The ICT Risk Officer Integrations, API & administration
- The MSP NOC Lead Integrations, API & administration
- The Skeptic Integrations, API & administration
- The SRE Lead Integrations, API & administration