3 ms·

Show HN: Critsit – Incident Response After the Alert

1 points by ZECTBynmo 5y ago

ZECTBynmo 5y ago
This is the MVP of a startup I've been working on. The core idea is to create a real-time information/collaboration hub for incident response. One place for info, designated teams/roles/plans, and integrations with commonly used systems. There's still lots of work to be done, but I'd really love some feedback and direction from anyone interested. Thanks for checking it out!
ramimac 5y ago
Regardless of the tool itself, there is a huge trust barrier to overcome here as a hosted solution for inherently sensitive Incident Response related data. Looking at the site, there is nothing to indicate this would be viable for my organization from a security perspective. In terms of features/functionality, I could see some synergy with building in IR Tabletop/simulations.
- ZECTBynmo 5y ago
  That makes total sense, thanks for the feedback. Is there anything besides wide adoption that you think might help bridge the trust gap?
  - ramimac 5y ago
    It's a hard problem - and depends on your target market. That being said, in my experience most companies with the maturity to go hunting for a tool like this will also have established vendor security requirements. On a baseline "trust" level - having an identity associated with the project beyond a new "brand" can help bridge that gap, especially if there are folks with strong personal reputations attached. On the product side, https://www.enterpriseready.io/ https://www.enterpriseready.io/ does a good job breaking down expectations for SaaS (https://www.enterpriseready.io/features/product-security/ https://www.enterpriseready.io/features/product-security/). In the long term, you'll find many of the largest possible customers will demand an on-prem option, and/or some level of external attestation (e.g. a pentest, SOC2, etc.) I acknowledge this is a lot to throw at someone getting a product going, and don't want to be discouraging, but security products have an even larger expectation - especially because I expect your buyer and user personas to be security-centric

1 points by ZECTBynmo 5y ago

This is the MVP of a startup I've been working on. The core idea is to create a real-time information/collaboration hub for incident response. One place for info, designated teams/roles/plans, and integrations with commonly used systems. There's still lots of work to be done, but I'd really love some feedback and direction from anyone interested. Thanks for checking it out!

ramimac 5y ago

Regardless of the tool itself, there is a huge trust barrier to overcome here as a hosted solution for inherently sensitive Incident Response related data. Looking at the site, there is nothing to indicate this would be viable for my organization from a security perspective. In terms of features/functionality, I could see some synergy with building in IR Tabletop/simulations.

ZECTBynmo 5y ago
That makes total sense, thanks for the feedback. Is there anything besides wide adoption that you think might help bridge the trust gap?
- ramimac 5y ago
  It's a hard problem - and depends on your target market. That being said, in my experience most companies with the maturity to go hunting for a tool like this will also have established vendor security requirements. On a baseline "trust" level - having an identity associated with the project beyond a new "brand" can help bridge that gap, especially if there are folks with strong personal reputations attached. On the product side, https://www.enterpriseready.io/ https://www.enterpriseready.io/ does a good job breaking down expectations for SaaS (https://www.enterpriseready.io/features/product-security/ https://www.enterpriseready.io/features/product-security/). In the long term, you'll find many of the largest possible customers will demand an on-prem option, and/or some level of external attestation (e.g. a pentest, SOC2, etc.) I acknowledge this is a lot to throw at someone getting a product going, and don't want to be discouraging, but security products have an even larger expectation - especially because I expect your buyer and user personas to be security-centric