dgul2tor
Similar to what Stripe did for payments, I think the solution lies in abstracting away implementation details for secure architectures that need to commonly be built from the ground up. To name a few concrete components of a secure SaaS application that can be abstracted:
- end to end encryption (for p2p file transfer and for teams)
- multi-tenancy in data architectures
- secure data stores (with row/column, and even element level obfuscation of sensitive/PII data): obfuscation would be dynamic and highly configurable through an ACL style interface
- data severability: the ability for customers of an application to delete (or broadly, govern) their data should they feel at risk
In summary, a highly secure, scalable, and governable data backend for application developers to use instead of building their own. All accessible through an API which can be used a la carte.
Would love to get some thoughts on this approach from the community? What do you think?
PS. If you’d like to chat directly, get in touch through https://cipherflow.co
For the developer: get software to market faster without needing to build things like encryption key and certificate management systems, secure storage with element-level ACLS, multi-tenant backend, etc.
For the customer: have fine-grained control over who accesses your data and severability controls if needed.
I'd love to get feedback and learn about your potential use cases - please reach out through the site if you're interested!