Skip to content

Latest commit

 

History

History
90 lines (49 loc) · 4.87 KB

README.md

File metadata and controls

90 lines (49 loc) · 4.87 KB

Say Thanks!

Sleep Better With Content Encryption

Cryptography can secure data even when the database has left the company. Effective cryptography not only makes attackers life harder, it also provides sound sleep for management, OPs, and everybody else responsible for data.


You sweat, a wave of nausea hits you. In two hours you talk to your bosses-bosses-boss. Why? You have been hacked. You had all the fancy acronyms like SAST, DAST, SCA, WAF, SIEM, and several you are pretty sure the IT team just made up on the spot. You had a pentest. Twice! And still they managed to hack the application. YOUR application.

“I will make it”, you say to yourself, and prepare your slides.

[two very tense hours later]

The conference room is nice. Nicer than the ones you are used to know. Also colder. Much colder. Or so it seems.

"Yes, we have been hacked. The attackers dumped our customer database and took it with them.

The attackers even managed to modify customers payment data with the intent to order our products on other customers’ bill. To do so, they randomly swapped the payment data between customers and then ordered expensive products. That would have been quite ingenious, if it had worked: we would be swamped with wrongly assigned bills and it would take months to sort it all out and sieve out the actual malicious orders. By that time, all traces of the attackers would be cold and gone.

Luckily, we were prepared.

All PII in the customer records was encrypted in our application. Although the attackers managed to dump the whole database table, it contained only encrypted data with no hope of decryption. We could practically hear the sigh of relief of our DPO, when we told her.

The payment data was cryptographically linked to the customer. Whilst that did not prevent the manipulation of the database, all manipulated records were instantly detected by the now failing integrity check. We had to restore the table from backup, but not a single wrongly billed order was executed."

[later in the evening, with a good glass of wine]

"And this, my friend, was the moment I got an approving nod from my bosses-bosses-boss"


But there is another, equally important side: Microservices, Big Data, Machine Learning — these are the buzzwords that make a developers eye gleam. In reality these are often replaced by Integrating legacy systems, file based data exchange via ftp, and laws & compliance.

Encryption and other cryptographic measures can help bring together technology and the ugly side of business. Though they are not for the careless to implement. This slide deck will give you a very short introduction into the why and how of implementing cryptography into your applications.

You might even push snooze on your alarm clock when the next Heartbleed hits the news.

Where

Slides

Here are some example slides. The whole presentation (Keynote) can be found here. A pdf export is also available. You can view the slides in your browser.

Topic Slide

Disclaimer

Value of data

Why?

Why?

Data classification

Trust Anchors

Pattern 1/2

Pattern 2/2

Transparent Encryption 1

Transparent Encryption 2

Storing Keys

Algorithm Rollover

Login

Data Integrity

Access Control

LICENSE

CC BY-SA 4.0