1 Sid Shetye CEO & Founder sid@crypteron.com 858-342-1617
The Problem – Data breaches 2 $$$ Compliance fines, Customer goodwill, Lawsuits, Lights out … Basically, anyone building connected apps should be concerned
Stages of a data breach 3 Lateral Data Reconnaissance Intrusion Persistence movement Exfiltration Industry focus and investments - Network breach ≠ Data beach - The perimeter is a losing battle - Fight where you can win: invest in SELF-PROTECTING core assets - Crypteron: Simplifies data security for developers - Crypteron: Post-breach, neutering controls in-place
Ecosystem and Crypteron 4 Cloud SaaS Apps Data store Internet Custom Enterprise Apps Customers Sensitive ‘Game Over’ Web/App Firewalls Data Server External File Server VPN Server Employee Hackers & Botnets Commercial off the shelf server apps Internal Employee Anti Virus Email Document Endpoint security etc. Server Server A platform-as-a-service that instantly enables pervasive Data always encrypted … except when being processed encryption, offering one-click data-breach response
The Crypteron Difference – minutes vs months/years 5 Security Features Crypteron Alternatives Encryption Custom code + 3rd party libraries Automatic Tamper Protection Custom code Automatic Key Storage Insecure or custom code + 3rd party appliances (off-site and multi-layered encryption) Automatic Insecure or single-layered SSL Key Distribution (multi-layered encryption) (vulnerable to Heartbleed etc.) Key Usage and Caching Access controls Automatic Custom code Audit Logs Key Revocations Key Rotations Secures all types of data Yes Custom code (SQL, NoSQL, Objects, Files, (unified platform) (Fragmented) Streams, etc.) Cloud Provider Flexibility Any public, private or hybrid cloud Cloud lock-in or custom code
Benefits - simpler compliance 6 Painful compliance covering Simple compliance by keeping most all building blocks infrastructure ‘out of scope’
7 1 min demo Secure. Productive. In minutes.
00:00:10 Step 1. Install SDK Timer
00:00:20 Step 2. Get API Key Timer
00:00:30 Step 3. Plug in the API Key Timer
Step 4. Tell what’s secure That’s it (really!) Once for the entire app. And Java users 00:01:00 skip this Timer
Step 5. Enjoy. Everything just works 00:01:00 Timer
Automatically decrypted when data is being processed 00:01:00 Timer
Basically, as simple as … 14 [Secure] @Secure … that’s smaller than a Tweet. Any developer can learn in seconds.
Don’t be left behind Let’s Get Started Today Still Have Questions…? Call: 1-(858) 342-1617 E-mail: sid@crypteron.com Documentation: crypteron.com/docs
More recommend