SOC 2 Type II Certified

πŸ›‘οΈSOC 2 Type II Certified

We are ringing in 2022 with our SOC 2 Type II (2) certification!

We continue to be committed to our own privacy, governance, and security as our first priority to protect our customers.

How is this different from SOC 2 Type I?

  • Although SOC 2 Type I has it's benefits, it pales in comparison to SOC 2 Type 2.
  • A SOC 2 Type 2 requires companies to show an attestation of controls over a minimum 6 month period.
  • Whereas SOC 2 Type 1 is only an attestation of controls at a specific point in time.
  • SOC 2 Type 2 vendors continuously validate against tough security protocols and controls they remain compliant.

How did we achieved SOC 2 Type II

A large part of this success is with partnering with Secureframe, the best SOC 2 automation platform.

They integrate with our infrastructure and continuously scan and monitor our systems in addition to ensure any vendor we use is secure and compliant.

More details covered in our full customer case study with Secureframe.

Security @ Rootly

To learn more, please visit https://rootly.com/security where we highlight our security best practices. Everything from encryption to SSO.


🌝 New & Improved

  • πŸ†• Weihan Li joined our team as a Senior Software Engineer and will help accelerate our roadmap efforts and continue to ensure the platform is reliable
  • πŸ†• Added Slack command /incident status or /rootly status that allows you to pick from Mitigated and Resolved easier
  • πŸ†• Postmortem URL can be used as an incident variable
  • πŸ†• Action items can be assigned to teams and not just individuals, this is also supported in Workflows - Action Item as a condition if you want to filter Team A action item goes to Team A board
  • πŸ†• Pinned images and screenshots will show up in external timelines on Confluence and Google Docs
  • πŸ†• Search and pagination added to Invite Users from Slack modal
  • πŸ†• New Workflow Condition called Visibility that will let you trigger workflows based on whether an incident is private or public
  • πŸ†• New Workflow Task that allows you to create an incident independent of Slack automatically
  • πŸ†• Brand new coat of paint on our Slack Marketplace app as we continue to deepen our partnership
  • πŸ’… Private incidents are excluded from weekly email for all users regardless of admin privileges
  • πŸ’… All Slack integrations on Rootly by default ask users to connect their Slack account to make onboarding more seamless
  • πŸ’… Anywhere incident variables can be used we now link to a better resource for Slack markdown, more enhancements coming here soon
  • πŸ’… Manually running Workflows UI in Slack now says ⚑ Run instead of Submit
  • πŸ’… Improved carriage returns and spacing on status page events, in particular for long form updates
  • πŸ’… Improved status page styling, title, and added support for favicon
  • πŸ’… Slack integration page now includes references to Slack markdown for incident title
  • πŸ’… Removed /genius from Slack commands as it was replaced by Run Workflow option when an incident channel is created
  • πŸ› Fixed issue where PagerDuty list of users had an infinite scroll
  • πŸ› Fixed issue where there were inconsistent timezones on incident timeline
  • πŸ› Fixed issue where Opsgenie teams weren't importing
  • πŸ› Fixed UI issue where connecting to Slack account had a banner partially covering the connect button
  • πŸ› Fixed issue in Slack UI where duplicate emojis displayed
  • πŸ› Fixed issue where VictorOps occasionally did not page
  • πŸ› Fixed issue where scheduled maintenance timezone and system did not align correctly
  • πŸ› Fixed issue where occasionally manually clicking Run Workflow in Slack did not populate all workflows
  • πŸ› Fixed issue where occasionally editing or creating a Workflow did not work under specific conditions
  • πŸ› Fixed issue where alerts would ping old resolved incident channels


Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.
wave