Accenture MDR Quick Start Guide for MongoDB Atlas

This quick start guide will help Accenture MDR customers configure MongoDB Atlas to allow log collection from the Log Collection Platform (LCP).

The document includes the following topics:

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal.

Port Requirements

Table 1-1: Port requirements for LCP communication.

Source

Destination

Port

Description

LCP

MongoDB Cloud

TCP/443

Default Port

Configuring MongoDB Atlas

Pre-requisites:

Grant Programmatic Access to a Project - You need to have ProjectOwner Access to perform and provide below Access:

Below list of steps needs to be carried out for MongoDB configuration

Setup Auditing in MongoDB Atlas

  1. Login to your Atlas project.

  2. In the Security section of the left navigation, click Advanced.

  3. Toggle the button next to Database Auditing to On.

  4. Confirm that you want to audit authentication failures.

NOTE: By default, Atlas logs the failed authentication attempts of both known and unknown users in the audit log of the primary node.

  1. Select the database users, Atlas roles, and LDAP groups whose actions you want to audit in Select users and roles.

NOTE: Please enable all the filters.

  1. Select the event actions that you want to audit in Select actions to audit.

  1. Click Save.

Create an API Key for a Project

  1. Navigate to the Access Manager page for your organization.
    a) If it is not already displayed, select your desired organization from the Organizations menu in the navigation bar.

    b) Click Access Manager in the sidebar, or click Access Manager in the navigation bar, then click your organization.

  2. Click Create API Key.

  3. Enter the API Key Information.
    a) Enter a Description.

    b) In the Organization Permissions menu, select the new role or roles for the API key.

  1. Click Next.

  2. Copy and save the Public Key. The public key acts as the username when making API requests.

  3. Copy and save the Private Key. The private key acts as the password when making API requests.

  1. Add an API Access List Entry.
    a) Click Add Access list Entry.

    b) Enter an <LCP_IP address> or CIDR block from which you want Atlas to accept API requests for this API Key. You can also click Use Current IP Address if the host you are using to access Atlas will also make API requests using this API Key.
    c) Click Save.

  2. Click Done.

Create an API Key in an Organization

  1. Navigate to the Access Manager page for your organization.
    a) If it is not already displayed, select your desired organization from the Organizations menu in the navigation bar.

    b) Click Access Manager in the sidebar, or click Access Manager in the navigation bar, then click your organization.

  2. Click Create API Key.

  3. Enter the API Key Information.
    a) Enter a Description.

    b) In the Organization Permissions menu, select the new role or roles for the API key.

  4. Click Next.

  5. Copy and save the Public Key. The public key acts as the username when making API requests.

  6. Copy and save the Private Key. The private key acts as the password when making API requests.

  1. Add an API Access List Entry.
    a) Click Add Access list Entry.

    b) Enter an <LCP_IP address>from which you want Atlas to accept API requests for this API Key. You can also click Use Current IP Address if the host you are using to access Atlas will also make API requests using this API Key.
    c) Click Save.

  2. Click Done.

Invite an Organization API Key to a Project:

  1. Navigate to the Access Manager page for your project.
    a) If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.

    b) Select your desired project from the list of projects in the Projects page.
    c) Click the vertical ellipsis () next to your project name in the upper left corner and select Project Settings.
    d) Click Access Manager in the navigation bar, then click your project.

  2. Click the API Keys tab.

  3. Add the API Key to the project.
    a) Click Invite to Project.

    b) Type the public key into the field.
    c) In the Project Permissions menu, select the new role or roles for the API key.

  4. Click Invite to Project.

GRANT the Project role

  1. Navigate to the Access Manager page for your project.
    a) If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.

    b) Select your desired project from the list of projects in the Projects page.
    c) Click the vertical ellipsis () next to your project name in the upper left corner and select Project Settings.
    d) Click Access Manager in the navigation bar, then click your project.

  2. Click the API Keys tab.

  3. Add the API Key to the project.
    a) Click Invite to Project.

    b) Type the public key into the field.
    c) In the Project Permissions menu, select the new role or roles for the API key.

  1. Click Invite to Project.

LCP Configuration Parameters 

Table 1-2: The MongoDB Atlas event collector (API - 5073) properties to be configured by MDR are shown in the table.

Property

Default Value

Description

URL

MongoDB Cloud

URL to connect the MongoDB cloud.

Public Key

<Custom Value>

Get these values from above device configuration steps and mention in the Pre-Installation Questionnaire (PIQ).

Private Key

<Custom Value>

Get these values from above device configuration steps and mention in the Pre-Installation Questionnaire (PIQ).

 

Legal Notice

Copyright © 2021 Accenture. All rights reserved.

Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.