Overview
Netskope One DSPM supports scanning self-managed Oracle Data Stores. Follow these instructions to setup your Oracle database and configure its connection to Netskope One DSPM.
Create a Netskope One DSPM Service Account
Begin by configuring an Oracle service account which will be dedicated to Netskope One DSPM’s use.
The following steps may require the assistance of your local database administrator.
- As an administrator, log into your Oracle database.
- Create the Netskope One DSPM-specific user by executing the following commands in order:
| Command | Outcome |
|---|---|
CREATE USER dasera_user IDENTIFIED BY "dasera_password"; | Creates the Netskope One DSPM-specific user. Note: Substitute dasera_user & dasera_password with your own preferred values. |
GRANT CONNECT, RESOURCE TO dasera_user; | Permits the Netskope One DSPM-specific user to connect to the Oracle database. |
GRANT SELECT ANY TABLE TO dasera_user; | Grants the initial necessary Netskope One DSPM-specific user permissions to power capabilities within the Netskope One DSPM platform. |
GRANT select_catalog_role TO dasera_user; | Grants the remaining necessary Netskope One DSPM-specific user permissions. |
You can alternatively authenticate this data store using AWS Secrets Manager instead of a username and password.
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 |
|---|---|
| Data Store Identifier | Friendly name to describe this Data Store. Your value is displayed in other Netskope One DSPM screens such as Policy Management and Classification Management. |
| Data Store Endpoint | Enter a single string of the following values separated by colons: – Database server address – Server listening port number – Database name For example, for an server address like oracle.example.io and database like production, you would enter oracle.example.io:1521:production. Note: 1521 is the default Oracle port number. If you are using a custom port number, be sure to substitute it here. |
| Authentication Method | Select AWS Secrets Manager or Username / Password authentication. |
| Secret ARN | If using AWS Secrets Manager authentication, enter Secret ARN obtained from AWS Secrets Manager. |
| Database Username | Enter the corresponding value from the Create Service Account step above. |
| Password | Enter the corresponding value from the Create Service Account step above. |
| Scan Frequency | Controlling how often your Data Store is reviewed for changes, Netskope One 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.
| Feature | Supported for Oracle? |
|---|---|
| Discovery | No |
| Configuration Analysis | No |
| Privilege Analysis | Yes |
| Shadow Data Analysis | Yes |
| Classification | Yes |
| Data In Use Monitoring | No |
| Automation | Yes (always-on) |
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.