Overview
Netskope DSPM supports scanning Azure SQL Server data stores. Follow these instructions to set up your Azure SQL Server database and configure its connection to Netskope DSPM.
Authenticate Data Store
There are two methods for authenticating Azure SQL Server data stores: Snapshot Scan or Netskope DSPM-specific credentials.
Using Snapshot Scan
Snapshot Scans are quicker and simpler, spinning up a secure copy of the data store for Netskope DSPM to scan without needing to create Netskope DSPM-specific credentials. This copy exists only within your Netskope DSPM instance, and Netskope DSPM does not store any associated data. It’s encrypted and then immediately spun down, so no lingering data copies exist. Please note that spinning up the data store copy can cause the scan to take several hours.
The following features are not supported when authenticating via Snapshot:
- Privilege Analysis
- Database selection
- Sample data collection
Ensure you’ve enabled data store Snapshots access during Azure Infrastructure onboarding. For already onboarded accounts, you must manually add the following permissions in the Azure console.
"Microsoft.Sql/servers/write", "Microsoft.Sql/servers/delete", "Microsoft.Sql/servers/firewallRules/write", "Microsoft.Sql/servers/databases/read", "Microsoft.Sql/servers/databases/write", "Microsoft.Sql/servers/databases/delete"
Once connected, data classification in the data store runs via Snapshot, which appears on the Data Store Inventory page as a small layered square note icon to the right of the hyperlinked data store name.
You can later edit the data store and toggle off Snapshots, at which point Netskope DSPM-specific credentials will be required to authenticate the data store.
Using Netskope DSPM-Specific Credentials
Authenticating the data store via Netskope DSPM-specific credentials requires additional configuration steps within Azure and may involve additional administrative support, as outlined below. This type of authentication enables access to all supported capabilities within Netskope DSPM.
Create Netskope DSPM Service Account
Begin by configuring a service account which will be dedicated to Netskope DSPM’s use.
- As a DB administrator, log into your SQL database.
- Create the Netskope DSPM-specific SQL user by executing the following commands in the mentioned order:
| Command | Outcome | Notes |
|---|---|---|
CREATE LOGIN 'dasera_user' WITH PASSWORD ='dasera_password'; | Creates the Netskope DSPM-specific DB user, which will be dedicated to Netskope DSPM’s use as a service account. | Substitute dasera_user and dasera_password with your own preferred values. You will need this information later when configuring Netskope DSPM. Note: We recommend using Netskope DSPM as the username and password of your choice. You will need this information later when configuring Netskope DSPM. |
USE "database name"; CREATE USER dasera FOR LOGIN 'dasera_user'; ALTER ROLE db_datareader ADD MEMBER dasera; | Grants read-only access to the Netskope DSPM-specific DB user in each MySQL database you want to scan. The CREATE USER command enables the previously-created LOGIN to access the database. The built-in db_datareader role grants read-only access to all schemas and tables (including system tables) on the active database. | Substitute “database name” with each MySQL DB you wish to scan with the Netskope DSPM Application. |
Retrieve Connection Information
In addition to configuring a service account, Netskope DSPM will also require additional information in order to communicate with your SQL database. Please follow the steps below to identify the connection values for later use within Netskope DSPM.
| Highlight Color | Corresponding Netskope DSPM Value | Example |
|---|---|---|
| Red | Data Store Endpoint |  |
Connect Your Data Store
Step 1: Provide Credentials
Follow these steps to configure the connection:
-
Go to Data Stores > Data Store Inventory.
-
Click CONNECT A DATA STORE in the upper right.
Tip: Alternatively, if the data store was already found by auto-discovery, go to the Discovered tab and click Connect in the Actions column.
-
In the Connect a Data Store window, click the data store icon you wish to connect.
-
In the Provide Credentials section, complete the following fields:
| Field | Value |
|---|---|
| Azure Account Name | Select one of the Azure Accounts defined within the Infrastructure Section screen. The field will default if there is just one Azure account configured. |
| Data Store Identifier | Friendly name to describe this Data Store. Your value is displayed in other Netskope DSPM screens such as Policy Management and Classification Management. |
| Data Store Endpoint | Enter the corresponding value from the Retrieve Connection Information step above, plus the port number. Example: Netskope DSPM-azure-mysql-test.mysql.database.azure.com:3306. 3306 is the default MySQL port number. If you are using a custom port number, be sure to substitute it here. |
| Scan Frequency | Controls how often your Data Store is reviewed for changes, Netskope DSPM’s recommended frequency is defaulted, which you can override (if desired). |
| Sidecar Pool | If you will use sidecars to monitor this data store, select a sidecar pool with network visibility to said data store. This field is displayed when there is at least one defined sidecar pool. To learn more, please visit our Sidecar Administration article. |
Step 2: Scanning Infrastructure
- Click Next.
- When the Select Capabilities tab appears, complete the following fields:
- Assign a Data Owner (Optional): Select one or more users responsible for this data store.
- Which databases should Netskope DSPM scan?: Select the specific data stores and schemas to monitor, if applicable.
- Features: Select the features you want to enable.
| Capability | Supported for Azure SQL Server via Netskope DSPM-specific Credentials | Supported for Azure SQL Server via Snapshot Scan |
|---|---|---|
| Discovery | Yes (always-on) | Yes |
| Privilege Analysis | Yes | No |
| Shadow Data Analysis | Yes | No |
| Classification | Yes | Yes |
| Data-In-Use Monitoring | No | No |
| Automation | Yes (always-on) | Yes |
Step 3: Review and Save
- Click Save.
- When the Review tab appears, the system validates your configuration. If there are any issues, follow the on-screen instructions to fix them.
- Click Save to finalize the connection.