Before you create a loader connection, verify that security for your databases is adequate and it can prevent unauthorized access. Note the following security guidelines:
-
When you create a loader connection, you have the option to select which repositories are allowed to access the connection. This helps restrict user access to certain data sources.
-
If you are creating loader connections to SQL Server Open Database Connectivity (ODBC) data types on Windows systems, you can configure these connections for single sign-on that supports a user’s Windows system credentials. Also, a user accessing the connection (to create an entity in the Control Center, for example) must be authenticated to access the server machine on which the data source resides.
-
Integrate Trillium Discovery with CyberArk account security. See Configuring CyberArk Integration.
-
To increase security, create separate loader connections to point to different file and database locations.
For example, assume two data analysis teams work with delimited data sources stored on the same UNIX server. If you create two loader connections, one for each team, to point to the separate file locations, data access by the team members can be streamlined and effectively controlled. Team 1 members will have access to only that data that is relevant for the Team 1 and Team 2 members will have access to only that data that is relevant for the Team 2.