Skip to content

Managed Services Provider Set up

Are you managing SecureCloudDB for several different clients? The following guide will help you effectively configure sandbox environments for your customers and allow them to do any limited management and audits that they require while you ensure that their infrastructure is maintained and protected.

Creating an Organization for a client

Begin by creating an organization for your client(s). You can add users that should have access by email to the organization creation wizard on step 2 or continue to the next section after you are done creating the organization.

For example, if you manage customers Bank A, Bank B, and Bank C, your organizations page would look similar to the page below after creating each client organization:

Invite members to an organization

Click on the organization that you would like to add a new member to. Using the side menu, navigate to the Settings > Members page. From there, click on the blue circle with a plus sign in the center to add a new member.

On the following page, input the email address of the user you would like to invite for the organization and click Add. Continuing the previous example, for the client organization Bank A, we would want to add all the members required from the Bank A team and possibly one member from the MSP's engineering team to only the Bank A organization:

Once you are finished adding all the required members of the client's team and yours accordingly, it is time to connect the client's data.

Connecting your client's cloud account(s)

Begin connecting one cloud account or multiple by creating an asset discovery in the organization designated for the client. This will allow you to build an inventory of the client's databases and backups and generate some of the foundational security reports.

Next, setup database access so that audits of user's accessing your customer's databases can be completed. This will unlock the remainder of the foundational security reports which includes user assessment and audit coverage.

Finally, configure database activity monitoring to identify anomalous behavior in real-time.

Note

This will need to be done for every client organization. Configuring an asset discovery, database access, or DAM configuration for organization Bank A does not allow the members of Bank B or Bank C to see the data stored in Bank A unless they are added to the Bank A member list by email.