Deploying Netskope One DSPM sidecars on AWS EC2 via Terraform

Deploying Netskope One DSPM sidecars on AWS EC2 via Terraform

Overview

The Netskope One DSPM application requires seamless connectivity to scan your data stores. However, as per common security practices, businesses tend to deny proper firewall egress between their internal networks and external applications. Such limitations impact the operational use of Netskope One DSPM and reduce the full return value of your subscription.

To overcome this, Netskope One DSPM provides a flexible collection architecture consisting of one or many sidecars you can deploy alongside your data stores. These sidecars collect necessary metadata and transfer it to the Netskope One DSPM application. Within this central management console, you can take action on insights from across all data stores regardless of where they are hosted.

Prerequisites

Before beginning, the Netskope One DSPM sidecar AMI needs to be shared with your organization. To request this AMI, please contact your CSM and supply:

• Your AWS account number; and
• The AWS region where you will deploy the Netskope One DSPM instance (which we require in order to share the image).
  In addition:

You will need a Netskope One DSPM-hosted tenant to receive the sidecar-collected metadata. Ensure that you validate the latest version of the required toolsets by running the following commands at your terminal prompt:

terraform --version (Ver 1.3.2 or higher)
aws --version (Ver 2.8.2 or higher)
git --version (Ver 2.38.x or higher)

Architecture

Netskope One DSPM provides a flexible collection architecture, consisting of one or many sidecars you deploy alongside the main application. These sidecars connect to data stores to runs scans, uploading the results to the Netskope One DSPM application.

A single sidecar can scan multiple data stores in its installation environment. Typically, you will deploy one sidecar per individual environment (e.g. VNet, VPC, etc.), however you may choose to install multiple sidecars for additional scalability and redundancy. The Netskope One DSPM application automatically load balances scans across healthy sidecars in each sidecar pool.

Register Sidecar

To set up the relationship between your sidecars and Netskope One DSPM-hosted tenant, you will provide the sidecars with unique authentication tokens generated within our Sidecar Administration UI.

If you already have an existing sidecar pool token to use, you can skip this section. Otherwise, follow these instructions to acquire a new token.

1. Log into the Netskope One DSPM application.
2. Navigate to the Platform Settings > Sidecar menu to display the Sidecar Administration screen.
3. Click the Add Sidecar Pool button.
4. The Add Sidecar Pool modal is displayed.
5. On the Details tab, complete the following field:

Field	Value
Name	Any friendly value to describe the sidecar pool.

6. Click the Save button.
7. Click the Copy button at the bottom of the Sidecar Authentication Token modal to save the generated token to your clipboard.

8. Click the “x” button to exit the modal.

Since you haven’t yet associated this token with a sidecar, the sidecar pool will appear only when you click the Show Inactive Sidecars icon in the upper right, with empty Version and Status columns for now.

The above-generated token will be used for each individual sidecar within the sidecar pool.

Setting up the AWS Configuration

1. At the terminal prompt or command shell type aws configure and provide the inputs as below:

AWS Access Key ID :
AWS Secret Access Key :
Default region name [us-west-2]:
Default output format [json]:

Note: Your AWS CLI should be referenced in the PATH variable

2. Copy the following URL in your browser window to download the requisite Terraform scripts:

https://netskope-dspm-release.s3.us-west-2.amazonaws.com/terraform/aws-sidecarFromAMI.zip

3. Extract the Netskope One DSPM Terraform scripts in your local system folder which will create a folder with two sub folders deploy and modules.

Running the Terraform Script

Navigate to the sidecar_instance_only folder created from the extraction above.

From that directory, run the following command to initiate your Terraform environment successfully:

terraform init

To validate that you have all the pre-requisites configuration details available for the installation, run the following command:

terraform plan

When prompted, enter the following variables:

Parameter	Value
ami_id	AMI ID of the Netskope One DSPM sidecar image shared with your organization. This value can be found in your AMI Catalog in the My AMIs section. Clear all filters and filter by Owner = “Shared With Me”.
host_security_group_ids	Your own AWS security groups that you wish to associate. Use [ ] and double-quotes to surround the groups. Please ensure the security groups belong to the same network as the subnet you will launch the Netskope One DSPM sidecar, otherwise deployment will fail.
host_subnet_id	This is the subnet to launch the Netskope One DSPM sidecar. This will determine the VPC and availability zone of the sidecar.
key_name	Name of the SSH key you wish to install on the sidecar. Installing patches and security updates requires an admin to connect to the sidecar via SSH. If this is pre-configured you can select the same from the drop down list; otherwise, please configure a new key pair within the AWS EC2 Console.
dasera_host	Your tenant URL minus the protocol. For example, if your tenant is accessed using https://example.dspm.goskope.com, your value will be example.dspm.goskope.com.
instance_type	The EC2 instance type you wish to deploy for the sidecar. Netskope’s standard recommendation is to use m5.2xlarge unless advised differently by your account team.
sidecar_token	An existing sidecar token, or a new one generated in the Register Sidecar section above.

To initiate the Terraform installation run the following command from the deploy/instance_and_roles folder:

terraform apply

The script will begin and perform the following actions:

1. Prompt you to input. Provide the same set of 6 configuration details in sequence as listed in the table above.
2. Check for errors. In the event an error occurs, follow the on-screen instructions for correcting & resuming.
3. Outputs a resource modification list. To learn more about the resources created by the script, please expand the section below.
4. Prompt you to confirm before executing. To confirm you must type yes.

Apply complete! Resources: 1 added, 0 changed, 1 destroyed.

Outputs:

ids = "i-0dc55679d6d318d76"
ssh_ip = [
"XXX.XXX.XXX.XXX",
]

Resources Created

In the console output, the following resources are listed:

Resource Type	Resource Name
AWS::EC2::Instance	netskope-dspm-sidecar

When using Netskope’s recommendation instance type, each sidecar instance is deployed as a m5.2xlarge EC2 instance (equaling 8CPU/32GB).

Validate Sidecar Connection

When deploying sidecar, you’ll need to ensure that the sidecar has the ability to reach your tenant. Take the following steps to verify the connectivity from the sidecar.

1. SSH to the sidecar
2. Run the following commands, substituting [TENANT] with your tenant name:

curl [TENANT].dspm.goskope.com/api/pulse

A successful response will resemble the following:

{"version":"10.0.0.311","build_target":"prod","deployment_type":"saas"}%

Once a sidecar is running, you can now validate it is properly communicating with your Netskope One DSPM application.

1. Log into the Netskope One DSPM application.
2. Navigate to the Platform Settings > Sidecar screen.
3. For the sidecar(s) in question, validate that the Version column is populated and its matching Status indicator is green. 

It may take a few minutes for newly-running sidecars to communicate with the Netskope One DSPM application. If both values have not updated after 20 minutes, double-check that you configured your sidecars correctly and update the pool token, if necessary.

Rotating Sidecar Tokens

These instructions apply if your security practice requires regularly rotating security tokens, or if your sidecar is failing to communicate with the Netskope One DSPM application due to an invalid token. These steps will be repeated for each individual sidecar within the sidecar pool.

Generate New Token in Netskope One DSPM

1. Log into the Netskope One DSPM application.
2. Navigate to Platform Settings > Sidecar to open the Sidecar Administration screen.
3. For the sidecar pool registration whose token you wish to rotate, click the Generate New Token icon.
4. Generate New Token modal is displayed. Read then click Confirm.
5. Click Copy at the bottom of the Generate New Token modal to save the generated token to your clipboard.
6. Close modal.

Apply New Token in AWS

1. Log into the AWS EC2 Console. The EC2 dashboard is displayed.
2. In the left menu, navigate to the Instances > Instances screen. The Instances dashboard is displayed.
3. In the list of instances, click the Instance ID hyperlink corresponding to the Netskope One DSPM sidecar requiring the token update. The Instance Summary screen is displayed.
4. Click the Connect button. The Connect to instance screen is displayed.
5. Provide ubuntu as the user name and press the Connect button below to start a SSH session to the sidecar.

6. The AWS CLI is displayed.
7. Enter the command cat /etc/netskopeconf to display details of the Netskope One DSPM application tied to this sidecar along with its current token:
8. Enter the command sudo vi /etc/netskopeconf to open the sidecar’s configuration file.
9. Search for the SIDECAR_TOKEN parameter and replace its current value with the new token.
10. Save your changes and exit the vi editor.
11. To validate that the sidecar is using the new token, enter the command cat /etc/netskopeconf and validate that the SIDECAR_TOKEN parameter is using the new token.
12. Once confirmed, restart the sidecar by entering the command sudo reboot.

At this point, the SSH console will disconnect. Return to the AWS EC2 Console and verify that the sidecar reboot is complete.

Upgrading Sidecars

You may need to occasionally upgrade your sidecars so they remain compatible with your Netskope One DSPM application instance or tenant.

Your account team will provide you the location for a patch file in AWS S3. Using that value, run the following command from the sidecar’s CLI (substitute <patch_address> with the provided AWS S3 location).

wget <patch address> && patch

This upgrade process may take a couple minutes.