Datasources
Datasources store information about your database or repository
such as the type of database, the location of the repository, or credentials
that might be associated with it. You must define a datasource in order to
use it with Guardium® applications.
Creating a datasource definition Guardium applications such as Vulnerability Assessment and classifier. A datasource can be created by using the Datasource Definitions tool or by creating and uploading a CSV file by using the Customer Uploads tool in the Guardium user interface. You can also create a datasource by using Guardium APIs. Creating a datasource group Guardium applications where you can specify a single datasource, such as security assessments, classification, and discovery scenarios. Create datasource groups from the Datasource Definitions page in the Guardium UI. Configuring your datasource Configuring custom properties for your datasources Working with existing datasources Reporting on datasources Defining a datasource using a service name Managing KDC definitions Managing datasource credentials with CyberArk Managing datasource credentials with AWS Secrets Manager Guardium system with the Amazon Web Services (AWS) Secrets Manager to securely store, manage, rotate, and retrieve credentials for your datasources that use the Amazon Relational Database Service (RDS).Managing datasource credentials with HashiCorp Guardium system with HashiCorp to securely store, manage, rotate, and retrieve credentials for all supported datasources.You can configure your Guardium system to authenticate to the HashiCorp vault by using a username and password with no Transport Layer Security (TLS), server-side authentication with TLS, or client-side authentication with TLS. If you use client-side authentication with TLS, you must create and import a client signed certificate on all your systems such as the central manager and managed units, if any.