MongoDB Security
summary
Nearly 440,000 mongod servers are shown wide open on the internet with 600 TB exposed, and many breaches trace to default settings left unchanged. Defaults matter: older mongod binds to 0.0.0.0 (pre‑2.4), 2.6+ binds to 127.0.0.1, default port 27017, REST on port 1000 disabled by default, and Community builds before 3.0 lack SSL. Secure layers include firewall/IPTables or VPC, strict file ownership and perms, and a replicated keyfile 1KB 600 perms; enabling auth forces restarts and careful user/key rollout.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:54Security...
- 1:18Slashdot 08/15/2015
- 1:50Why you should care
- 3:34Is MongoDB insecure?
- 4:54General guidelines
- 6:14Firewall
- 7:51bind_ip setting
- 8:45Ports
- 9:33HTTP Interface
- 10:09REST Interface
- 10:27SSL/TLS
- 11:31Agenda
- 12:36File Permissions
- 14:07Encryption
- 15:25Enable client access control
- 17:32Localhost exception
- 19:39Other option
- 20:14Create an admin user
- 23:02Roles
- 24:44Create app users
- 25:30Key files
- 27:24Sharded clusters - 2
related talks
15mMongoDB Security: Making Things Secure by Default
31mMongoDB: Advantages of an Open Source NoSQL Database
54mNoSQL Shouldn’t Mean NoSecurity
01h 08mMongoDB First Steps
58mAuthentication and Authorization in MongoDB
37mThe State of MongoDB, Its Open Source Community, and Where Percona Is Going With It
33mKey Management for Data-at-Rest Encryption in Percona Server for MongoDB
35mNoSQL Is Not NoVulnerable