Overview
This article provides instructions for ongoing maintenance and lifecycle management of your OVA-deployed Netskope DSPM sidecars, including configuring SSL proxies post-deployment, rotating security tokens, and performing version upgrades.
Configure for an SSL Proxy Environment (Post-Deployment)
If your organization routes outbound traffic through an SSL proxy, you must perform the following steps to allow your sidecar to communicate with the Netskope DSPM platform.
- Use an SSH client to connect to the appliance’s IP address.
- Log in with the default credentials:
- Login:
netskope - Password:
netskope
- Login:
- Execute the setup script with sudo privileges:
sudo /opt/netskope/setup-sidecar.sh - Follow the on-screen prompts to confirm your configuration parameters ((Sidecar Configuration, Tenant Host Configuration, Authentication Configuration). The values you entered during the OVA deployment will be shown as defaults.
- For HTTPS Proxy Configuration (Optional), populate with a HTTPS address to force sidecar traffic thru your designated proxy.
- When prompted Are you sure to use these variables for Sidecar deployment? (Y/N):, type
yand press Enter to save the configuration.- The configuration will be stored in the
/opt/netskope/sidecar-config.envfile.
- The configuration will be stored in the
- Next, execute the following command with sudo privileges to delete specific safety markers:
sudo rm CLOUD_INIT_SUCCESS SIDECAR_DEPLOYED - After saving the configuration and deleting the safety markers, execute the bootstrap script:
sudo /opt/netskope/bootstrap.sh
When deployment is complete, your sidecar should immediately begin communicating via the designated proxy.
Rotating Sidecar Tokens
If you need to rotate your security credentials, you must generate a new token in the console and apply it to the appliance.
Step 1: Generate a New Sidecar Pool Token
- Log in to your Netskope DSPM instance.
- Go to Administration > Sidecar.
- For more details on managing sidecar pools, see DSPM Sidecar Administration Overview.
- For the sidecar pool whose token you wish to rotate, click the Generate New Token icon.
- Read the warning on the modal and click Confirm.
- Click Copy to save the generated token to your clipboard.
- Close the modal.
Step 2: Apply the New Token
- SSH into the sidecar virtual appliance.
- Re-run the configuration script:Bash
sudo /opt/netskope/setup-sidecar.sh - Enter the new Sidecar Pool Token when prompted and confirm the changes.
The script will automatically update the configuration and restart the necessary services.
Sidecar Upgrade
The recommended method for upgrading the sidecar appliance is to redeploy it using the latest available OVA file.
- Download the new version of the OVA from Netskope.
- Deploy it as a completely new virtual machine, following the deployment steps in Deploy DSPM Sidecars via OVA/OVF on VMware vSphere.
- Once the new sidecar is online and connected, you can safely decommission and delete the old virtual machine.

