Manage your Security Consoles

The Command Platform features a set of self-serve capabilities that allows Vulnerability Management (InsightVM) and Nexpose customers to manage and adjust license allocation and cloud connectivity for Security Consoles deployed in your environment.

Users with the Platform Admin role can access these controls from the Command Platform web interface by navigating to Subscription Management (available from your menu or your settings dropdown) and clicking on Vulnerability Management (InsightVM) or Nexpose under Active Subscriptions.

These Security Console controls allow you to:

• Add and pair new Security Consoles to the Command Platform
• Allocate assets to Security Consoles you have deployed
• Edit Security Console names
• Remove Security Consoles from your license

Change a console name

To change the name of a console:

1. Click the ellipsis (…) within the Security Console card.
2. Click Edit name.
3. Name your console.
4. Click Rename Console to save or Cancel if you do not wish to change the console name.

View console license keys

To view (and copy) the license key for a console:

1. Click the ellipsis (…) within the Security Console card.
2. Click View license key. The key for this console will display.

Allocate assets to consoles

To change the number of assets that are allocated to a console:

1. Click Allocate Assets.
2. Change the asset count within any of your consoles.

3. Click Save Allocations to allocate your assets. Each console license will be updated with the new asset allocations.

Add a console

You can add additional Security Consoles to your Vulnerability Management (InsightVM) or Nexpose subscription from the Manage Licenses tab.

To add a console:

1. Click the Add Console button. This will present a stepped workflow.
2. Select whether your console should be cloud connected or cloud restricted.
3. Click Next.
4. Name your console.
5. Assign an organization.

Cloud connected consoles

Cloud connected Security Consoles are meant to be paired to the Rapid7 Command Platform. An Vulnerability Management (InsightVM) license is required for this pairing to take place. The license instance must be linked to an organization within your customer Rapid7 account. You can use an existing organization if no Vulnerability Management (InsightVM) license already exists within that organization, or you can create a new organization and give it a name. The organization must also be associated with a Command Platform data storage region.

1. Click Next.
2. Allocate assets to your new console.
3. Click Create Console.

This will result in the creation of two separate licenses:

• A console license
• An Vulnerability Management (InsightVM) product license within the organization and data storage region previously chosen

A new Vulnerability Management (InsightVM) product license instance will appear within the allocated organization on the Command Platform Home page.

The new console will also appear under Manage Licenses in the Vulnerability Management (InsightVM) space of Subscription Management, but will indicate Pairing Pending. This means that the console still needs to be installed, activated, and paired with the Command Platform.

4. Click the Install and pair console option within the new console to complete the process. You will be presented with details on how to download and install your console software on your chosen host.
5. Click Copy. The key should be of the format:

XXXX-XXXX-XXXX-XXXX:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-{region}

This is a composite key which consists of two parts:

• XXXX-XXXX-XXXX-XXXX relates to the license key for the console
• xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-{region} relates to the organization and data region linked to the Vulnerability Management (InsightVM) product license instance that the console will pair to.

6. Log in to your console.
7. Paste the key into the console. The console will then automatically pair with the Vulnerability Management (InsightVM) cloud license instance.

Within Subscription Management, the Pairing Pending flag should be removed from your new console.

Cloud restricted consoles

When creating a new console that is not intended to be connected to the Command Platform, choose Cloud Restricted in the first step of the Add Console workflow.

1. Click Next.
2. Name your Console.
3. Click Next.
4. Allocate Assets to your Console.
5. Click Create Console.

Your new cloud restricted Console will appear.

6. Click View Set-up guide from within the new console card to complete the console download and installation process.
7. Copy your console license key.
8. Log in to your console and enter the key to activate the console.

Nexpose consoles

To add a new Nexpose console:

1. Click Add Console.
2. Name your Console.
3. Allocate Assets to your Console.
4. Click Create Console.

Your new Nexpose console will appear.

6. Click View Set-up guide from within the new console card to complete the console download and installation process.
7. Copy your console license key.
8. Log in to your console and enter the key to activate the console.

When to consult Rapid7 before adding a new console

Before adding a new console, it is critically important that you consult with Rapid7 first if any of the subscription scenarios detailed in this section apply to you.

Managed Vulnerability Management and Rapid7 Hosted Vulnerability Management (InsightVM)

If you subscribe to either of these offerings, do not add additional consoles from the Console Management user interface. Adding a new console yourself for these subscriptions is unnecessary. If you feel that you need to add a new console for your deployment, contact your Rapid7 Customer Success Advisor first to discuss the implications of doing so.

SIEM (InsightIDR) and Managed Detection & Response

If you are an SIEM (InsightIDR) subscriber, be aware that adding another Vulnerability Management (InsightVM) cloud-connected console will create a new organization for the new Vulnerability Management (InsightVM) cloud instance. This organization will be separate from the primary organization that your existing SIEM (InsightIDR) and Vulnerability Management (InsightVM) subscriptions (along with your primary Security Console) are attached to. As a consequence, any assets attached to the new organization (and thus, the new console) that are assessed by Insight Agents will not be visible to the SIEM (InsightIDR) subscription attached to your primary organization.

For the same reason, Managed Detection & Response (MDR) subscribers must not add additional consoles without informing Rapid7 beforehand. Doing so will impact the ability of the MDR team to have full visibility on the subscriber’s environment.

Cloud Risk Complete

The Vulnerability Management (InsightVM) and Cloud Security (InsightCloudSec) products that are part of Cloud Risk Complete are designed to work together. For this reason, the typical Cloud Risk Complete deployment houses both product instances in a single organization. Since setting up an additional cloud-connected Vulnerability Management (InsightVM) console creates a new organization for the secondary Vulnerability Management (InsightVM) cloud instance, contact your Rapid7 Customer Success Advisor first to discuss how this action affects your Cloud Risk Complete subscription.

Considerations for adding new consoles

If you are considering adding a new console, keep the following in mind:

1. Insight Agents are tied to one organization only and cannot be shared with another organization.
2. SIEM (InsightIDR) must be attached to the same organization as Vulnerability Management (InsightVM) for any Insight Agents to collect data for both offerings.
3. If you choose to add a secondary console, the assets attached to it must be logically separated from the in-scope environment your MDR subscription is intended to monitor.
   • See the MDR Scope of Service document for more information on what logical separation entails.
4. If you want to add additional organizations to your MDR scope of service, contact your Rapid7 Customer Success Advisor first about MDR Multi-Org or Multi-Instance.

Deleting a Console

If a console is no longer being used, you can delete it. This process will result in associated licenses being deactivated.

In the case of a cloud connected console, the console will also be unpaired from the Command Platform and the product instance will be removed from your Command Platform account.

Assets that were allocated to the console will be added back into the unallocated pool for your Vulnerability Management (InsightVM) subscription.

The process of removal of console software from your host will need to be performed separately.

To delete a console:

1. Click the ellipsis (…) within the Security Console card.
2. Click Delete console.
3. Click Delete console again to complete the action. The deletion process may take some time to complete.