Skip to main content

MongoDB Atlas proof types and permissions

Written by Hyperproof Support
Updated over 3 weeks ago

Hyperproof supports collecting proof from MongoDB Atlas.


πŸ“ Note

Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance in meeting the requirements to integrate with Hyperproof and collect the proof you need.


When you create a Hypersync between Hyperproof and MongoDB Atlas, you can automatically collect the following proof types:

MongoDB Atlas proof types and fields

Proof type

Fields

Testable

Backup Compliance Policies

Organization Name, Project Name, Policy Id, Authorized Email, State, Copy Protection, Encrypted, Restore Window Days, Frequency Interval, Frequency Type, Retention Unit, Retention Value

Yes

List of Users

Organization Name, Project Name, User Id, Username, Email, Organization/Group, Role

Yes


​

This Hypersync supports importing a user list for an access review. See Importing a list of application users with a Hypersync for more information.

Requirements

To connect to MongoDB Atlas and collect proof your MongoDB Atlas configuration must meet the following requirements.

Authentication

Authentication type: Custom
​

Custom authentication parameters: Client ID, Client Secret

In MongoDB Atlas create a service account under Org > Access Manager > Applications > Service Accounts. See the MongoDB Atlas documentation for more information.


πŸ“ Note

Save the Client ID and Client Secret for this account. They are required when configuring the Hypersync in Hyperproof.


Permissions

The service account must have Organization Owner permissions.

Additional documentation


πŸ“ Note

You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need.
​

Additionally, you can create multiple Hypersyncs for a single control or label.


Did this answer your question?