How to Secure MongoDB Data Access with Views
Rate this article
Sometimes, MongoDB collections contain sensitive information that require access control. Using the Role-Based Access Control (RBAC) provided by MongoDB, it's easy to restrict access to this collection.
But what if you want to share your collection to a wider audience without exposing sensitive data?
For example, it could be interesting to share your collections with the marketing team for analytics purposes without sharing personal identifiable information (PII) or data you prefer to keep private, like employee salaries.
It's possible to achieve this result with MongoDB views combined with the MongoDB RBAC, and this is what we are going to explore in this blog post.
You'll need either:
- A MongoDB cluster with authentication activated (which is somewhat recommended in production!).
- A MongoDB Atlas cluster.
I'll assume you already have an admin user on your cluster with full authorizations or at least a user that can create views, custom roles. and users. If you are in Atlas, you can create this user in the
Database Access tab or use the MongoDB Shell, like this:
In this example, I'll pretend to have an
employees collection with sensitive data:Now I want to share this collection to a wider audience, but I don’t want to share the social security numbers and salaries.
Note that I'm not doing
{$project: {ssn: 0, salary: 0}} because every field except these two would appear in the view.
It works today, but maybe tomorrow, I'll add a credit_card field in some documents. It would then appear instantly in the view.Let's confirm that the view works:
Results:
Depending on your schema design and how you want to filter the fields, it could be easier to use $unset instead of $project. You can learn more in the Practical MongoDB Aggregations Book. But again,
$unset will just remove the specified fields without filtering new fields that could be added in the future.Now that we have our view, we can share this with restricted access rights. In MongoDB, we need to create a custom role to achieve this.
Here are the command lines if you are not in Atlas.
Then we can create the user:
If you are in Atlas, database access is managed directly in the Atlas website in the
Database Access tab. You can also use the Atlas CLI if you feel like it.
Then you need to create a custom role.
Note: In Step 2, I only selected the Collection Actions > Query and Write Actions > find option.
Now that your role is created, head back to the
Database Users tab and create a user with this custom role.
Now that our user is created, we can confirm that this new restricted user doesn't have access to the underlying collection but has access to the view.
In this blog post, you learned how to share your MongoDB collections to a wider audience — even the most critical ones — without exposing sensitive data.
Note that views can use the indexes from the source collection so your restricted user can leverage those for more advanced queries.
You could also choose to add an extra
$match stage before your $project stage to filter entire documents from ever appearing in the view. You can see an example in the Practical MongoDB Aggregations Book. And don't forget to support the $match with an index!Rate this article