Sit back, relax, switch on Atlas for Enterprise, and let us make your business more secure. Learn how to enable security features such as LDAP in minutes. Quickly analyze your data with popular analytics tools using the BI Connector. That's right folks, we can speak SQL too!

1. MongoDB
Atlas For Your Enterprise
Kip Iwakiri - Technical Services Engineer

2. Kip Iwakiri
Technical Services Engineer @ MongoDB
Table Tennis Aspirant

3. About Me

4. A Quick Show of Hands
Deployed an enterprise database cluster with:
● TLS
● LDAP authentication
● LDAP authorization
● Encryption at Rest with KMIP Key Management
● Encrypted Backups
● Analytics Integration

5. So… I got this letter today
To Whom It May Concern,
???
Our analytics team needs a database to run some numbers and do analysis stuff.
Please configure the following before 10:40 AM on Feb 12nd (or else):
Highly Available, 3 Node, MongoDB Replica Set
TLS for all connections
LDAP authentication and authorization for 30,000 users
Database Auditing - ONLY authentication attempts must be logged
Encryption at Rest using our AWS KMS credentials
MySQL Shell Connectivity

6. With MongoDB Atlas:
YOU CAN DO IT!

7. Checklist:
Highly Available, 3 Node, MongoDB Replica Set
TLS for all connections
LDAP authentication and authorization for 30,000 users
Database Auditing - ONLY authentication attempts must be logged
Encryption at Rest using our AWS KMS credentials
MySQL Shell Connectivity

8. 3 Node Replica Set w/TLS

9. Checklist:
Highly Available, 3 Node, MongoDB Replica Set
TLS for all connections
LDAP authentication and authorization for 30,000 users
Database Auditing - ONLY authentication attempts must be logged
Encryption at Rest using our AWS KMS credentials
MySQL Shell Connectivity

10. LDAP Auth - Requirements
Authentication
1. Server Hostname
2. Server Port
3. Bind User Credentials
4. (Optional) CA Certificate for LDAP Server
5. (Optional) LDAP Query for Mapping
Authorization
1. An attribute to match to MongoDB Roles
2. An LDAP query to find these attributes

11. CN=Kip,DC=LDAP,DC=MongoDB,DC=COM
LDAP Authentication
Bind DN
Bind Password
User DN
User Password
BIND SUCCESS - Bind User
BIND SUCCESS - Client User
MongoDB Authorization
User @ $external

12. LDAP Authentication - LIVE
To Whom It May Concern,
Hope all is going well!
(For your sake)
Time is ticking!
- Management

13. LDAP Authorization
memberOf: CN=Admin, DC=LDAP, DC=MongoDB, DC=COM
memberOf: CN=Table, DC=LDAP, DC=MongoDB, DC=COM
memberOf: CN=Tennis, DC=LDAP, DC=MongoDB, DC=COM
And MORE!
MongoDB Authorization
Roles @ admin
Bind DN
Bind Password
User DN
User Password
BIND SUCCESS - Bind User
BIND SUCCESS - Client User
CN=Kip,DC=LDAP,DC=MongoDB,DC=COM

14. Checklist:
Highly Available, 3 Node, MongoDB Replica Set
TLS for all connections
LDAP authentication and authorization for 30,000 users
Database Auditing - ONLY authentication attempts must be logged
Encryption at Rest using our AWS KMS credentials
MySQL Shell Connectivity

15. Database Auditing

16. Database Auditing - Got ‘em!
GOING LIVE
2018/09/26

17. Checklist:
Highly Available, 3 Node, MongoDB Replica Set
TLS for all connections
LDAP authentication and authorization for 30,000 users
Database Auditing - ONLY authentication attempts must be logged
Encryption at Rest using our AWS KMS credentials
MySQL Shell Connectivity

18. Fort MongoDB Features
● TLS
● Database Auditing
● SSO via LDAP
● Wooden Palisades
Encryption at Rest

19. Amazon KMS
1. IAM User
a. DescribeKey
b. Encrypt
c. Decrypt
2. Access Key
3. Access Secret
4. Region key will reside
5. AWS Customer Master Key (CMK)
Encryption at Rest - Requirements

20. Encryption at Rest - Requirements
Amazon KMS
1. IAM User
a. DescribeKey
b. Encrypt
c. Decrypt
2. Access Key
3. Access Secret
4. Region key will reside
5. AWS Customer Master Key (CMK)
Azure Key Vault
1. The Tenant ID (or Directory ID) for an Active Directory tenant.
2. The Client ID (or Application ID) w/ non-expired application
Password
3. The Resource Group name
a. Must have Owner Role in Resource Group
4. The Subscription ID and Key Vault Name of an Azure Key Vault.
5. The Key Vault must have the following Access Policies:
a. Key Management Operations
i. GET
ii. LIST
b. Cryptographic Operations
i. ENCRYPT
ii. DECRYPT
6. The Key Identifier for a key in the specified Azure Key Vault.

21. Checklist:
Highly Available, 3 Node, MongoDB Replica Set
TLS for all connections
LDAP authentication and authorization for 30,000 users
Database Auditing - ONLY authentication attempts must be logged
Encryption at Rest using our AWS KMS credentials
MySQL Shell Connectivity

22. BI-Connector

23. Checklist:
Highly Available, 3 Node, MongoDB Replica Set
TLS for all connections
LDAP authentication and authorization for 30,000 users
Database Auditing - ONLY authentication attempts must be logged
Encryption at Rest using our AWS KMS credentials
MySQL Shell Connectivity

24. One More Message
To Whom It May Concern,
Thank you for setting up our MongoDB cluster on Atlas! We didn’t
think it was possible but here we are.
We’ll get you next time.
Regards,
- Management

25. With MongoDB Atlas:
YOU CAN DO IT!

26. Thank You!
Kip Iwakiri - Technical Services Engineer
Any feedback would be greatly appreciated!

27. Questions?
Kip Iwakiri - Technical Services Engineer
Any feedback would be greatly appreciated!

28. So Sassy!