Overview
This guide provides instructions to onboard your AWS infrastructure to Netskope DSPM (also known as Netskope One DSPM) using AWS CloudFormation. This automated method deploys the necessary IAM roles for DSPM to discover and scan your data stores.
This process has been updated to use more granular, feature-based IAM permissions. The CloudFormation templates are now provided in YAML format (replacing the previous JSON format) to improve readability and include inline comments explaining each permission’s purpose.
Template Permission Summary
The CloudFormation template is dynamically generated based on the capabilities you select in the Netskope UI. This section explains what permissions the template will automatically create in your AWS environment.
| Permission Type | Policies & Permissions | Purpose |
|---|---|---|
| Base Permissions (Always Included) | • IAMReadOnlyAccess (Managed Policy)• AWSOrganizationsReadOnlyAccess (Managed Policy, Org only)• Trust Policy for Netskope & EC2 | Provides basic read-only access and allows Netskope to assume the role. |
| Optional Permissions (Based on Capabilities) | • If "Ingest Tags" is enabled: - tag:GetResources (Custom Permission)• If "Auto-Discover New Data Stores" is enabled: - 5 Managed Policies (S3, Redshift, RDS, EC2, DynamoDB ReadOnly) - 3 Custom Policies (EFS, Redshift Credentials, Athena/Glue) • If "Scan EBS/EFS and Auto-Discover Unmanaged Data Stores" is enabled: - 7 custom EC2 policies for creating and deleting temporary scan environments. • If "Authorize Data Store Snapshots Access" is enabled: - All permissions from "Unmanaged Data Stores" - 8 Custom RDS & KMS Policies for scanning snapshots. • If Enable AWS Inventory is enabled: - s3:PutInventoryConfiguration (Custom Permission). Required when Enable AWS Inventory is toggled on. Allows DSPM to configure S3 Inventory on customer buckets to store metadata in a dedicated inventory bucket. The inventory bucket is server-side encrypted using AWS S3 Managed Keys (SSE-S3). | Adds specific permissions for each feature you select in the UI. |
Instructions for Infrastructure Connection
Follow the steps below to onboard your AWS infrastructure into the Netskope DSPM application. Depending on your setup, choose either the Individual AWS Account or AWS Organization section to proceed.
This workflow starts in Netskope DSPM, continues with actions in the AWS Console, and ends back in DSPM to complete the setup.
-
In the Netskope DSPM Console:
-
Go to Administration > Infrastructure Connections.
-
Click Add Infrastructure > Select AWS > Add Account.
-
Select Capabilities tab > Adjust the toggles based on your discovery and classification needs:
Toggle Description Details Auto-Discover New Accounts (Org) Applies only to AWS Organizations.
Netskope DSPM automatically detects accounts that join your organization (or the selected OU) after onboarding, and the Netskope role is deployed to them automatically.Auto-Discover New Data Stores Lets DSPM automatically detect new data stores as they are created. Scan EBS/EFS and Auto-Discover Unmanaged Data Stores Finds data stores on disk volumes.
This is off by default due to potential performance impact on large environments.Ingest Tags Pulls AWS tags from each connected data store for filtering and policy use. Authorize Data Store Snapshots Access Adds required IAM permissions to the CloudFormation or Terraform templates for snapshot-based onboarding. These templates are created in the next step. Enable AWS Inventory Toggle this option to allow DSPM to use the native AWS S3 Inventory feature for S3 data stores. When enabled, DSPM stores bucket metadata in a dedicated inventory bucket instead of making individual API calls to fetch file metadata. This significantly reduces API costs for large buckets.
Note: This toggle is disabled by default because it requires additional AWS permissions. When enabled at the infrastructure level, the Use S3 Inventory option becomes available when connecting individual S3 data stores. For more details, see Connect AWS S3 to DSPM. -
Select CloudFormation > Fill in the following values > Click Next.
-
Click Launch Template
This will open the AWS Console in a new browser tab.
-
Don’t close this window and leave it on the Add Infrastructure modal to return to it later.
-
-
In the AWS Console:
-
The CloudFormation Create stack wizard will open. The template URL and parameters (like
DaseraRoleNameandExternalID) are pre-populated. -
Review the parameters > Click Next.
-
On the Configure stack options page, click Next.
-
On the Review page, scroll to the bottom and check the box: “I acknowledge that AWS CloudFormation might create IAM resources.“
-
Click Create stack
-
Wait for the stack status to change to
CREATE_COMPLETE.
-
-
In the Netskope Console:
-
Return to the Netskope DSPM browser tab you left open.
-
Click Save.

-
Your AWS account infrastructure is now connected, and Netskope DSPM can start discovering accounts and data stores for analysis.
Before you start:
- Sign in to the AWS organization’s management account.
- Enable trusted access for CloudFormation StackSets in AWS Organizations (AWS Organizations > Settings). If trusted access is not enabled, the role cannot be deployed to member accounts.
Follow this workflow to onboard an entire AWS Organization or specific Organizational Units (OUs).
-
In the Netskope DSPM Console:
-
Go to Administration > Infrastructure Connections.
-
Click Add Infrastructure > Select AWS > Add Organization.
-
Select Capabilities tab > Adjust the toggles based on your discovery and classification needs:
Toggle Description Details Auto-Discover New Accounts (Org) Applies only to AWS Organizations.
Netskope DSPM automatically detects accounts that join your organization (or the selected OU) after onboarding, and the Netskope role is deployed to them automatically.Auto-Discover New Data Stores Lets DSPM automatically detect new data stores as they are created. Scan EBS/EFS and Auto-Discover Unmanaged Data Stores Finds data stores on disk volumes.
This is off by default due to potential performance impact on large environments.Ingest Tags Pulls AWS tags from each connected data store for filtering and policy use. Authorize Data Store Snapshots Access Adds required IAM permissions to the CloudFormation or Terraform templates for snapshot-based onboarding. These templates are created in the next step. Enable AWS Inventory Toggle this option to allow DSPM to use the native AWS S3 Inventory feature for S3 data stores. When enabled, DSPM stores bucket metadata in a dedicated inventory bucket instead of making individual API calls to fetch file metadata. This significantly reduces API costs for large buckets.
Note: This toggle is disabled by default because it requires additional AWS permissions. When enabled at the infrastructure level, the Use S3 Inventory option becomes available when connecting individual S3 data stores. For more details, see Connect AWS S3 to DSPM. -
Select CloudFormation > Fill in the values below > Click Next.
-
Click Launch Template. The AWS Management Console opens in a new browser tab.
-
Keep this browser tab open on the Add Infrastructure modal to return to it later.
-
-
In the AWS Console:
-
Log in to the AWS Management Account for your organization.
-
Review the parameters > Click Next.
-
On the Configure stack options page, click Next.
-
On the Review page, scroll to the bottom and check the box: “I acknowledge that AWS CloudFormation might create IAM resources.”
-
Click Create stack.
-
Wait until the stack status reaches
CREATE_COMPLETE.This single stack creates the Netskope role in the management account and automatically deploys it to every member account under the selected organization root or OU. You do not need to create a StackSet or deploy a separate stack manually.
-
-
In the Netskope Console:
-
Return to the Netskope DSPM browser tab you left open.
-
Click Save.
Your AWS Organization infrastructure is now connected, and Netskope DSPM can start discovering accounts and data stores across your organization for analysis.
Already connected an AWS Organization?
If you onboarded your AWS Organization prior to this update, the Netskope role exists only in the management account, and member accounts are not updated automatically.
To enable scanning across all member accounts without role collision, choose one of the following options:
– Option A (Update the existing stack): In the AWS Console, select your original onboarding stack, choose Update, and upload or paste the new template. CloudFormation adds the StackSet to the existing stack without role collision because the role already belongs to that stack.
– Option B (Delete and recreate): In the AWS Console, delete the original stack first (which removes the old role), then return to Netskope DSPM and click Launch Template to create the stack fresh.
-
Troubleshooting
- Error: “Cannot ingest AWS tags due to missing permissions.”
- Cause: The “Ingest Tags” capability was not selected during the initial onboarding.
- Fix: Re-launch the template from Netskope DSPM with Ingest Tags enabled and update your CloudFormation stack.
- Cause: The “Ingest Tags” capability was not selected during the initial onboarding.
- Error: “Netskope encountered an error while scanning… Missing required AWS permissions: ec2:DeleteSnapshot”
- Cause: The “Scan EBS/EFS and Auto-Discover Unmanaged Data Stores” capability was not selected.
- Fix: Re-launch the template with this feature enabled and update your CloudFormation stack.
- Cause: The “Scan EBS/EFS and Auto-Discover Unmanaged Data Stores” capability was not selected.
- Error: “KMS decryption failed for RDS snapshot”
- Cause: The “Authorize Data Store Snapshots Access” capability was not selected.
- Fix: Re-launch the template with this feature enabled and update your CloudFormation stack.
- Cause: The “Authorize Data Store Snapshots Access” capability was not selected.
- Member accounts are not scanned or data stores are not discovered:
- Cause 1: The organization was onboarded prior to the member account role deployment update, so the Netskope role exists only in the management account.
- Fix 1: Re-run the onboarding workflow from Netskope DSPM using the current CloudFormation template. The updated template automatically deploys the role across the management account and all member accounts in a single stack.
- Cause 2: Trusted access for CloudFormation StackSets is disabled in AWS Organizations, or the stack was not launched from the management account.
- Fix 2: In the AWS Management Account, go to AWS Organizations > Settings and enable trusted access for CloudFormation StackSets. Then update or recreate the CloudFormation stack.
- Cause 3: A new member account joined the organization after onboarding, but automatic deployment was not active.
- Fix 3: In Netskope DSPM, ensure Auto-Discover New Accounts (Org) is enabled. In the AWS Management Account, verify that automatic deployment is enabled on the underlying StackSet so the role is deployed to accounts added later.
- Cause 1: The organization was onboarded prior to the member account role deployment update, so the Netskope role exists only in the management account.
- Session timed out or expired before clicking Save in Netskope DSPM:
- Cause: The browser session in Netskope DSPM timed out while waiting for the CloudFormation stack creation in the AWS Console.
- Fix: Once the CloudFormation stack status is
CREATE_COMPLETE, complete the connection without re-running the template:- Log back into Netskope DSPM and go to Administration > Infrastructure Connections.
- Click Add Infrastructure > Select AWS > Add Organization (or Add Account if onboarding an individual account).
- Select Manually Configured.
- Enter your Organization Name (or Account Name) and click Next.
- In the AWS Console, go to IAM > Roles, find the role your stack created (defaults to
Netskope_Role), and copy its Role ARN. - Paste the Role ARN into the Summary Info field in Netskope DSPM.
- Click Save.
- Fix: Once the CloudFormation stack status is
- Cause: The browser session in Netskope DSPM timed out while waiting for the CloudFormation stack creation in the AWS Console.
Next Steps
Now that your AWS infrastructure is connected, if you enabled Auto-Discover New Data Stores, you can proceed to the Data Stores Inventory to view your discovered resources.



