> Enterprise-level security: Single Sign-On (SSO), Data backup and recovery, Role-based permissions, Secure hosting, AES encryption
Ok but that’s “consumer level” for SaaS.
For Enterprise, you need to prove to me that a malicious insider at your organization can not access the enterprise’s data. Dealing with insiders and RBAC models is particularly interesting when offering search.
You need to provide full access and full change audits trails.
You need to provide a business continuity plan, as noted in a sibling comment.
You can make a more trusted claim by getting your solution HIPAA certified. If you are compliant for storing personal medical information, you’re basically there for “enterprise-level security”.
[0] - https://www.hhs.gov/hipaa/for-professionals/covered-entities...
TL;DR - Put them on the list, but don't let them burden you from making money.
Thanks for providing extra technical detail. However, I'm more curious with what's happening on the backend.
As far as I can tell, the your differentiation from something like MS Sharepoint or DropBox is an integrated OCR to extract keywords, and Artificial Intelligence to help filter (or "screen" as your landing pages call it). Is there more to your special sauce that I have overlooked?
Also, where are you storing customers' data? Amazon S3? In house servers? Are you using something like ElasticSearch or did you build your own search engine?
Sharepoint is of course very powerful. And that means you typically need a project to make it work. Shelf works out of the box, is opinionated and let's you get started with minimal to no configuration setup.
Yes, we use Amazon S3 for content uploaded to Shelf (encrypted of course) and we utilize ElasticSearch as well.
You don't need to answer. It's okay. I'm largely asking because I've been thinking about writing an series of essays on the subject of security and one of the topics I have taken some notes about is searching encrypted data.
If the index isn't secure, it kind of defeats the idea of encryption - someone need only make off with the index and be able to draw some conclusions. More so if it's relational.
There are different ways that some go about this, one is the hash with individual words with a unique salt and search for the hashes, but that has its own set of problems, like the ability to eliminate words like 'the' and 'it' from search queries. Well, at least computationally easy.
So, it's purely for my own curiosity that I ask. I imagine it might be doable to load it into RAM, the whole DB - if it's small enough or you have enough RAM, and then do the searches there in an encrypted environment?
I am not so concerned with exfiltration by 'hackers' so much as I'm concerned with exfiltration by employees. Should I get to writing the essays, that's going to be a central theme - protecting data from rogue employees with the increased use of cloud services in today's business environment.
Again, I'd not want you to feel obligated to release anything proprietary or anything that would compromise your security.
Been working on helping solve this this issue for quite a while now keeping things in more of a closed circle of beta users until recently. Why? Because we wanted to build a well rounded product based on customer feedback before opening this thing up.
Anyway, so far we've built Shelf primarily on a NodeJs stack making heavy use of microservices and recently more and more Lambdas with (and sometimes without) the Serverless framework. And we built a web clipper as browser extension for Chrome and Firefox to make it easier to clip and share web content.
Would love to get your feedback on if and how you experience the pain point. Of course feedback on the product itself would be great, too, if you want to give it a spin.