Share
Embed
Transcript
98 slides
-
#MDBlocal Kenneth White Security Principal TORONTO New encryption capabilities in
MongoDB 4.2: A deep dive into protecting sensitive workloads -
New encryption capabilities in MongoDB 4.2: A deep dive into
protecting sensitive workloads -
New encryption capabilities in MongoDB 4.2: A deep dive into
protecting sensitive workloads Agenda -
New encryption capabilities in MongoDB 4.2: A deep dive into
protecting sensitive workloads Agenda • A brief history of database security • Trust models: server vs. client • Encrypting data-in-use • Hands on deep dive • Q&A -
A brief history of database security Evolution • access controls
• passwords • plaintext > hashing > key derivation • bearer tokens • NTLM, Kerberos tickets, LDAP/S, SCRAM, web session • multi-factor auth • LCD fobs / SMS / 2FA apps / FIDO-U2F / WebAuthn / mobile enclaves • federated RBAC -
A brief history of database security Evolution • network •
(plaintext) native wire protocols • SSL encryption • TLS • TLS w/ PFS -
A brief history of database security Evolution • storage •
plaintext / raw filesystem • encrypted -
A brief history of database security Evolution • storage •
volume-level / full disk encryption (FDE) • BitLocker, DMCrypt, FileVault, encrypted EBS • file-level encryption • whole database • per-database (WiredTiger ESE) • tablespace • database-level encryption • column / field -
A brief history of database security These are all important
defenses, but… -
A brief history of database security Against whom/what are we
defending? • “hackers”? -
A brief history of database security Against whom/what are we
defending? • “hackers”? • criminal blackhats? • competitors? • activists? • unknown actors? -
A brief history of database security Against whom/what are we
defending? • “hackers”? • criminal blackhats? • competitors? • activists? • unknown actors? • insiders? -
A brief history of database security Against whom/what are we
defending? • “hackers”? • criminal blackhats? • competitors? • activists? • unknown actors? • insiders? • admins? -
A brief history of database security Every sector of the
global economy has been impacted. -
A brief history of database security Every sector of the
global economy has been impacted • enterprise • consumer tech • retail • government • healthcare • finance … -
A brief history of database security Major shifts in regulatory
& privacy climate -
A brief history of database security Major shifts in regulatory
& privacy climate • GDPR • HIPAA • PCI DSS • NIST/FISMA • Consumer protection • State & provincial -
A brief history of database security System architect & developer
security challenges -
A brief history of database security System architect & developer
security challenges Meeting legal/regulatory obligations • Controls • Audit/attestation -
A brief history of database security System architect & developer
security challenges Meeting legal/regulatory obligations • Controls • Audit/attestation Defending real-world attacks • First Principles: C/I/A • Separation of duties • Access control • Identifying & protecting sensitive data -
A brief history of database security System architects & develop
security challenges Meeting legal/regulatory obligations • Controls • Audit/attestation Defending real-world attacks • First Principles: C/I/A • Separation of duties • Access control • Identifying & protecting sensitive data -
Trust models: server vs. client What is the source of
trust? • Traditionally, DB encryption has relied on server-side trust -
Trust models: server vs. client What is the source of
trust? • Traditionally, DB encryption has relied on server-side trust • This has implications, many not so obvious -
Trust models: server vs. client What is the source of
trust? • Traditionally, DB encryption has relied on server-side trust • This has implications, many not so obvious • With a few caveats, the database operator typically has unrestricted technical access, including: • DBAs • system admins • hosting/infrastructure providers -
Trust models: server vs. client What is the source of
trust? • In a server-side encryption model, a leak or breach can be catastrophic -
Trust models: server vs. client What is the source of
trust? • In a server-side encryption model, a leak or breach can be catastrophic • This potentially includes: logs, backups, temp files, process memory… -
Trust models: server vs. client What is the source of
trust? • In a server-side encryption model, a leak or breach can be catastrophic • This potentially includes: logs, backups, temp files, process memory… • They who hold the keys controls the kingdom -
Trust models: server vs. client This is particularly important in
a cloud context, especially so when running highly sensitive workloads. -
Trust models: server vs. client A common pain for system
architects • Most notably in healthcare, finance, and consumer tech • The benefits of managed, easily expanded compute & cloud storage have often been considered out of reach because of data confidentiality & privacy concerns. -
Trust models: server vs. client The fundamental challenge is protecting
the confidentiality of data while it’s in use. -
Encrypting Data-in-Use Introducing MongoDB Client-Side Field Level Encryption • encryption
as a first-class citizen • modern, authenticated encryption algorithms • strong security guarantees • customer-managed keys • sensitive content is opaque to server & server operator -
Encrypting Data-in-Use Introducing MongoDB Client-Side Field-Level Encryption • major investment
• 2 years in the making • 18+ engineers spanning core server, query, security, cloud, drivers • targeting 12+ languages • all major hardware & operating system platforms • Linux, MacOS, Windows -
MongoDB Client-Side Field-Level Encryption Core design • CSFLE is enabled
in drivers & integrated into shell • All encryption/decryption is done in the driver, on the client • Drivers have expanded MQL awareness for automatic encryption • Individual fields within collections can be marked as encrypted • Keys can be used on a per-field or even per-document basis -
MongoDB Client-Side Field-Level Encryption Implementation • Extends existing JSON Schema
with new “encrypt” property • Schema validation extended client-side • Key management services natively integrated into drivers • KMS envelope encryption used to protect field data keys • Server only sees encrypted binary data (BinData subtype-6) -
MongoDB Client-Side Field-Level Encryption Cryptography • Multiple encryption options, including
deterministic search • Cloud key services are natively integrated • Modern authenticated encryption: AEAD AES-256 & HMAC-SHA512 • 2015 IETF draft: McGrew, Foley, Paterson • Abuse- & misuse-resistant derived HMACs w/ deterministic IVs • Native OS libraries used for crypto primitives -
MongoDB Client-Side Field-Level Encryption Cryptography • Raw key material never
persisted to disk (in-memory only) • Stored field keys protected by strong symmetric encryption • Field wrapping keys secured in HSM-backed external KMS • Key service master key rotation: scheduled or on-demand • Core constructions are Post-Quantum secure • Engaged with expert cryptography teams on design & security properties, and conducted independent security assessments -
View from application { firstName: "Pat", lastName: "Lee", ssn: "901-01-0001",
email: "[email protected]", mobile: "+1-212-555-1234", medRecNum: 235498 } -
View from application View from database (admin, server, DB logs,
process memory) { firstName: "Pat", lastName: "Lee", ssn: "901-01-0001", email: "[email protected]", mobile: "+1-212-555-1234", medRecNum: 235498 } -
{ firstName: "Pat", lastName: "Lee", ssn: "901-01-0001", email: "[email protected]", mobile:
"+1-212-555-1234", medRecNum: 235498 } { firstName: "Pat", lastName: "Lee", ssn: "r6EaUcgZ4lGw…", email: "K4b5U3TlcIXh…", mobile: "oR72CW4Wf5Ej…", medRecNum: 235498 } View from application View from database (admin, server, DB logs, process memory) -
Client-Side Field Level Encryption Step by Step Step 1:
Identify fields to encrypt -
Identify fields to encrypt { "medRecNum" : 235498, "firstName" :
"Pat", "lastName" : "Lee", "ssn" : "901-01-0001", "mobile" : "212-555-1234", "email" : "[email protected]" } -
Client-Side Field Level Encryption Step by Step Step 1:
Identify fields to encrypt Step 2: Set JSON data types & key(s) for encrypted fields -
"test.patients" : { "bsonType" : "object", "properties" : { "ssn"
: { "encrypt" : { "bsonType" : "string", "keyId" : [ myKey ], "algorithm" : encryption_mode, } } } } -
Client-Side Field Level Encryption Step by Step Step 1:
Identify fields to encrypt Step 2: Set JSON data types & key(s) for encrypted fields Step 3: Create a new Mongo session with encryption options -
var keystore = db.getCollection("__keystore") var clientSideFLEOptions = { "kmsProviders" :
{ "aws" : { "accessKeyId" : env.KMSKID , "secretAccessKey" : env.KMSKEY } }, "schemas" : { patientSchema } , "keyVaultCollection" : keystore } encryptedSession = new Mongo( "localhost", clientSideFLEOptions ) -
Client-Side Field Level Encryption Step by Step Step 1:
Identify fields to encrypt Step 2: Set JSON data types & key(s) for encrypted fields Step 3: Create a new Mongo session with encryption options Step 4: Run your queries. -
db.patients.insert({ "medRecNum" : 235498, "firstName" : "Pat", "lastName" : "Lee",
"ssn" : "901-01-0001", "mobile" : "212-555-1234", "email" : "[email protected]" }); ... db.patients.find({ "ssn": "901-01-1234" }); -
Client-Side Field Level Encryption Step by Step Step 1:
Identify fields to encrypt Step 2: Set JSON data types & key(s) for encrypted fields Step 3: Create a new mongo session with encryption options Step 4: Run your queries. (That’s it) -
Example: Direct query on an encrypted field encryptedDb.patients.find({"ssn": "901-01-0001" })
encryptedDb.patients.find({ "ssn": BinData(6,"ASV2YBzOhUY…" )}) -
Auto-decryption for clients holding a valid key: { "medRecNum" :
235498, "firstName" : "Pat", "lastName" : "Lee", "ssn" : "901-01-0001", "mobile" : "212-555-1234", "email" : "[email protected]" } -
View to a DBA: { "medRecNum" : 235498, "firstName" :
"Pat", "lastName" : "Lee", "ssn" : BinData(6,"ASV2YBzOhUZZu643i7Y..."), "mobile" : "212-555-1234", "email" : "[email protected]" } -
View to a client lacking a valid key: { "medRecNum"
: 235498, "firstName" : "Pat", "lastName" : "Lee", "ssn" : BinData(6,"ASV2YBzOhUZZu643i7Y..."), "mobile" : "212-555-1234", "email" : "[email protected]" } -
View to database, server memory, logs, backups: { "medRecNum" :
235498, "firstName" : "Pat", "lastName" : "Lee", "ssn" : BinData(6,"ASV2YBzOhUZZu643i7Y..."), "mobile" : "212-555-1234", "email" : "[email protected]" } -
{ "firstName" : "Pat", "lastName" : "Lee", "medRecNum" : 235498,
"ssn" : BinData(6,"ASV2YBzOhUZZu643i7Y..."), "mobile" : "212-555-1234", "email" : "[email protected]" } View to legacy clients: { "medRecNum" : 235498, "firstName" : "Pat", "lastName" : "Lee", "ssn" : BinData(6,"ASV2YBzOhUZZu643i7Y..."), "mobile" : "212-555-1234", "email" : "[email protected]" } -
Subdocuments & embedded fields supported { "_id": 923452345, "name": "John
Doe", "ssn": "555-55-5555, "addresses": { "home": { "street": "123 secret way", "state": "NV", "zip": "89429" } } } -
Subdocuments & embedded fields supported { "_id": 923452345, "name": "John
Doe", "ssn": "9+4/J%|]yr4t^(M", "addresses": "cEfgjCW,WqK+vB4V&fX1{G4XI*oi?OmQA7kT9>,}1vo SG!5\cJkl0?6ckTmL*9TmZ^[x`2gRkCYpP)~Ol5dpBz" } -
Subdocuments & embedded fields supported { "_id": 923452345, "name": "John
Doe", "ssn": "9+4/J%|]yr4t^(M", "addresses": { "home": { "street": "8u^,%k78`[l9*AqMM", "state": "NV", "zip": "89429" } } } -
Sorts, range, and reference queries schema design { "firstName": ")2~Y8cJQuM",
"lastName": "u?n<EzK9,G#agvq@", "DOB": 1978, "location": { "city": "u^fj,%k78*)qV", "state": "NV", }, "ssn": "9+4/J%|]yr4t^(M", "payerID": 62501, "medicalCode": "89K", "accountBalance": 4000.34 } -
MongoDB Client-Side Field-Level Encryption Recap • Run anywhere: Atlas, self-managed
cloud, GovCloud, local • Targeting all supported drivers on all supported platforms • Encrypt at the collection-, field-, or document-level • Search on encrypted fields • Subdocuments, objects and aggregation pipeline support • Multiple enforcement options (client-side, server-side, or both) • Backwards compatible with existing admin & cluster tools -
MongoDB Client-Side Field-Level Encryption Roadmap • Beta preview now –
Java, Node.js, C# .Net, Python, Go • Server support on Atlas 4.2 clusters now • Shell update in flight • Additional language beta previews in coming weeks • 3rd party cryptography reviews & security assessments complete -
#MDBlocal Kenneth White Security Principal TORONTO New encryption capabilities in
MongoDB 4.2: A deep dive into protecting sensitive workloads