Imperva Data Activity Monitoring (DAM)
- 08 Mar 2022
- 1 Minute to read
-
Print
-
DarkLight
-
PDF
Imperva Data Activity Monitoring (DAM)
- Updated on 08 Mar 2022
- 1 Minute to read
-
Print
-
DarkLight
-
PDF
Imperva Data Activity Monitoring (DAM) defines and enforces data security and compliance policies across the cloud and on-premises including relational databases, mainframes, big data platforms, data warehouses, and enterprise file stores.
Parameters
- Imperva DAM Domain (required) - The hostname or IP Address of the Imperva DAM server. When using a hostname, it must be the FQDN (Fully Qualified Domain Name) of your Imperva DAM server.
- User Name and Password (required) - The credentials for a user account that has the Required Permissions to fetch assets.
- Verify SSL (required, default: False) - Verify the SSL certificate offered by the value supplied in Imperva DAM Domain. For more details, see SSL Trust & CA Settings.
- If enabled, the SSL certificate offered by the value supplied in Imperva DAM Domain will be verified against the CA database inside of Axonius. If the SSL certificate can not be validated against the CA database inside of Axonius, the connection will fail with an error.
- If disabled, the SSL certificate offered by the value supplied in Imperva DAM Domain will not be verified against the CA database inside of Axonius.
- HTTPS Proxy (optional, default: empty) - A proxy to use when connecting to the value supplied in Imperva DAM Domain.
- If supplied, Axonius will utilize the proxy when connecting to the value supplied in Imperva DAM Domain.
- If not supplied, Axonius will connect directly to the value supplied in Imperva DAM Domain.
- For details on the common adapter connection parameters and buttons, see Adding a New Adapter Connection.
Required Permissions
The value supplied in User Name must have read access to devices.
Such permission are required to access the data necessary to a given API resource. For more details, see Creating a SecureSphere User on Imperva documentation website.