7.4 Privileged Access to Databases

When users access a database with privileged credentials, the chances for data loss or sensitive information misuse go up. The administrators need to ensure that the connection to the database is secure and the database credentials are not misused. Privileged Account Manager provides the database monitoring feature where administrators can protect the database by controlling and monitoring the activities of the users who connect to the database.

In addition, Privileged Account Manager allows you to assign the risk to a specific query or a table in the database. Based on the risk configuration, you can identify any suspicious activities in the database and disconnect the session or block the respective user from accessing the database.

Privileged Account Manager enables you to control and monitor database accesses by granting access to the database as follows:

  • Database Access Through Credential Checkout:

    This method enables you to provide privileged access to the database using the credentials checked out from Privileged Account Manager. In this method, the privileged account credentials are reset after every check-in to avoid misuse of credentials.

    NOTE:Credential check out is not supported when Privileged Account Manager is installed on a Windows server as a manager.

  • Database Access Through Privileged Account Manager Proxy:

    Using this method, you can allow users to access the database through Privileged Account Manager proxy where Privileged Account Manager monitors the activities performed on the database.

  • SSO to the Database:

    Using this method, you can allow users to SSO to a database session and monitor the activities performed on the database. For more information about configuring privileged SSO to database, see Configuring RemoteApp Mode Using Command Control.

Based on the information in the following table, you can choose the appropriate database access method:

Method

Keystroke Audit

Command Audit

Video Capture

Command Risk & Automatic Session Disconnect

Manual Disconnect

Database Access Through Privileged Account Manager Proxy

✗

✓

✗

✓

✓

Database Credential Checkout

✗

✗

✗

✗

✗

Privileged SSO to Database

✓

✗

✓

✗

✓

7.4.1 Database Access Through Credential Checkout

Credential Checkout for databases allows you to provide elevated access to a database and monitor user actions on the database. This feature is supported only on Linux environments.

7.4.2 Configuring Credential Checkout for Oracle Database

To enable credential checkout for Oracle, perform the following:

  1. Download and install the Oracle database client:

    1. Download and install the Oracle database client by using the instantclient-basic-linux.x64-x.x.zip package.

      NOTE:You can download the Oracle database client from the Instant Client at http://www.oracle.com/technetwork/indexes/downloads/index.html#database. All the files that you retrieve through the Oracle client zip/ tar file should be saved in /lib64 for 64-bit machine and /lib for 32-bit machine.

    2. Create a symbolic link libclntsh.so for the libclntsh.so.xx.x file in /lib64 or /lib.

      For example, for libclntsh.so.12.1 create a symbolic link libclntsh.so (libclntsh.so -> libclntsh.so.12.1).

  2. Configure the Oracle client library path in Privileged Account Manager:

    1. On the home page of the Privileged Account Manager administration console, click Hosts.

    2. On the middle pane, select the Privileged Account Manager host.

    3. On the right pane, click Packages.

    4. Select the dbaudit package.

    5. On the left pane, click Settings.

    6. In the Oracle Client Library Path field, specify the path where oracle client is installed. By default the path is /lib64 for a 64-bit machine or /lib for a 32-bit machine.

      This library must be installed on a Privileged Account Manager server.

  3. Add the database server details as a resource and add the privileged account of the database server. To add database resource and its credentials, click Credential Vault > Database > Database Type and click + next to the Resources. For more information about the resource configuration fields, see the contextual help.

  4. You can either create database permissions using Access Control. For more information, see Create Database Monitoring Permissions Using Access Control. OR

  5. You can also create a database rule using Command Control:

    1. On the home page of the console, click Command Control.

    2. In the Command control pane, click Rules.

    3. In the details pane, click Add Rule.

    4. Specify a name for the database rule, then click Finish.

    5. To configure the rule, select the rule, then in the details pane, click Modify.

      Configure only the following:

      Run User: Select Everyone from dropdown list.

      Run Host: Specify the name of the Database resource created above.

      Authorize: Select Yes, then select Stop from the drop-down list.

    6. Click Finish. The settings you have defined for the rule are displayed in the console.

  6. Add database password check out command to the rule:

    1. On the middle pane, click the Commands icon.

    2. For database password check out rule, From the drop down list of commands, drag the Oracle DB Password Check Out command and drop it to the database rule

7.4.3 Checking Out Database Credentials

Privileged Account Manager (PAM) allows users to checkout the database credentials in the following ways:

  • Credential Checkout from the user console

  • Checkout credentials using API tokens.

  • Checkout credentials using REST API.

    To view the REST API documentation:

    1. In the new administration or user console, click the logged in user on the top-right corner.

    2. Click REST API.

      The REST API document opens in a new tab.

7.4.4 Configuring Credential Checkout for Other Databases

To enable credential checkout for databases, such as Microsoft SQL Server, MySQL, PostgreSQL, MariaDB, Sybase, and IBM Db2 perform the following:

Create Database Monitoring Permissions Using Access Control

Create a database monitoring permissions using Access Control:

  1. On the home page of the console, click Access Control.

  2. In the Access Control pane, create resource pool for database users by clicking Create.

    1. In the General page enter the name, description and select the Database type for which you want to create the resource pool. Example: Microsoft SQL.

    2. Click Next

    3. Click +Add to select Microsoft SQL database. The resources are populated from the resources configured in the Credential Vault. If you have not done configure it at this point to view and select the appropriate resources.

    4. Click Create. You can view the newly created resource pool using Access Control > Resource Pools.

  3. Create user role of database users for database monitoring.

    1. To create this role, go to Access Control > User Roles > Create > General – specify the fields name and description. Click Next.

    2. In the Included Members page, click Add and select Database users. Click Add to select the users you want to add.

  4. Create an assignment.

    1. To configure the assignment, select the Access Control > Assignment, click Create Assignment.

    2. From the Resource Pools page, select the database you want to create the assignment for. Example: My SQL.

    3. Click Select.

    4. Select the User Role. Example: DB Users.

    5. Add a Description.

    6. Add Permissions. Example: My SQL Database Access and set the following fields

      • Time Restrictions: All Days (24 hours), Specify time range starting and ending. If you want custom setting use custom days.

      • Access and Monitoring Options page: Move the slider to the right if you want to disable Session Capture, by default this option is set to enable.

      • Customization page: add the customized scripts.

    7. Click Finish.

  5. You are redirected to the Assignments page, Click Create. Assignment created successfully message is displayed.

For more information about creating Resource Pools, User Roles, and Assignments, see Access Control. For more information about Database connectors, see Adding Database Connectors Using Access Control.

Create Database Monitoring Permissions Using Command Control

  1. In the agent that has the dbaudit module, perform the following:

    1. Install the ODBC (Open Database Connectivity) package that is unixODBC rpm package which is part of the OS distribution.

    2. Create the Symbolic links for ODBC Libraries in /lib64 or in /usr/lib64 as explained below:

      1. Create a link libodbc.so for libodbc.so.x.x.x

      2. Create a link libodbcinst.so for libodbcinst.so.x.x.x

    3. Install the supporting ODBC driver of the respective database. This ODBC driver is available as part of the database provider’s server distribution.

      For Microsoft SQL Server, choose the drivers as follows:

      1. Microsoft SQL Driver is supported only on Linux 64-bit.

      2. Free TDS Driver is supported on Linux 32 bit and 64-bit.

    4. Configure the database driver in ODBC by using odbcinst.ini file.

    5. Configure Data Source Name (DSN) of the database in the odbc.ini file.

      For more information about how to configuring odbcinst.ini and odbc.ini files, see the Knowledge Base Article.

      NOTE:To enable password change for a Linux IBM Db2 database, refer to the IBM Db2 documentation. For more information on setting up ODBC application connectivity on Linux using the IBM Data Server Driver, refer to the IBM Support pages.

  2. In the Privileged Account Manager administration console:

    1. Set the ODBC library path:

      1. On the home page of the Privileged Account Manager administration console, click Hosts.

        On the middle pane, select the Privileged Account Manager host.

        On the right pane, click Packages.

      2. Select the dbaudit package.

      3. On the left pane, click Settings.

      4. In the ODBC Library Path field, specify the path where the symbolic links are created.

      You can use the appropriate policy template to automatically create a resource and rule for databases. This resource and rule can be customized as required. To create the resource and rule manually, continue with the following steps.

    2. Add the database server details as a resource and add the privileged account of the database server. To add database resource and its credentials, click Credential Vault > Database > Database Type and click + next to the Resources. For more information about the resource configuration fields, see the contextual help.

    3. Create a database rule:

      1. On the home page of the console, click Command Control.

      2. In the Command control pane, click Rules.

      3. In the details pane, click Add.

      4. Specify a name for the database rule, then click Add.

      5. To configure the rule, select the rule, click edit icon in the details pane and configure the following:

        Run User: Select Everyone from the drop-down list.

        Run Host: Specify the name of the Database resource created above.

        Authorize: Select Yes, then select Stop from the drop-down list.

      6. Click Modify. The settings you have defined for the rule are displayed in the console.

    4. To add database password check out command to the rule, perform the following:

      1. In the middle pane, click the Commands icon.

      2. From the drop-down list of commands, drag the appropriate database command and drop it to the database rule.

7.4.5 Checking Out Database Credentials

Privileged Account Manager (PAM) allows users to checkout the database credentials in the following ways:

  • Credential Checkout from the user console

  • Checkout credentials using API tokens.

    For more information about AAPM, see Application to Application Password Management.

  • Checkout credentials using REST API.

    To view the REST API documentation:

    1. In the new administration or user console, click the logged in user on the top-right corner.

    2. Click REST API.

      The REST API document opens in a new tab.

7.4.6 Database Access Through Privileged Account Manager Proxy

You can use this feature to protect a database by controlling and monitoring the activities of the users who connect to the database through database connector. A database connector acts as a proxy between the user’s database client and the database server. This Privileged Account Manager proxy IP address and port number must be communicated to the user to whom you are providing access.

Figure 7-2 Database Connector

After you provide database access through Privileged Account Manager proxy, you can allow the user to log into the database using:

  • Their own database credentials.

  • Credentials checked out from Privileged Account Manager.

    In this method, you are enhancing the database security by allowing Privileged Account Manager to manage database credentials.

For configuring the database access through Privileged Account Manager proxy to monitor the database activities, perform the following:

Prerequisite

  • Direct access from database client to the database server should be blocked.

    The database server should only accept the data transfer through the Privileged Account Manager server.

  • If the database is connected over SSL to the Oracle database, import Privileged Account Manager certificate to the database client’s wallet.

  • If the database is connected over SSL to the Microsoft SQL server, import Privileged Account Manager certificate to the database client.

  • If the database is connected over SSL to Microsoft SQL server, ensure that the Microsoft SQL server supports TLS 1.2.

Adding Database Connectors Using Access Control

You can add the database connections which creating resource.

  1. Click Credential Vault > Database > Add New.

  2. Click + next to Resources.

  3. Specify the following information:

    General Setting

    Name: Specify the name of the database. This name is used along with the Credential to authenticate. If you do not provide the correct domain name, user authentication fails.

    Connection Details

    Connect String: You can specify the string that will reset the password in the database and check in the password.

    Connect As: Select SYSDBA. If you want Privileged Account Manager to perform the password check in process then, to check the connection to the database server, click Test Connection or select Default.

    Password Change on Check In:

    Based on the following selection the password of the application will be changed automatically every time a credential is checked in.

    • Never: You can use this option if you do not want to change the password after every credential check-in.

    • Delegate to Identity Manager: If you want to delegate the password check-in process to Identity Manager, select Delegate to Identity manager. On selecting this option, the IDM (Identity Manager) driver for Privileged Account Manager takes care of generating random password and synchronizing the password to IDM. The PAM IDM driver checks in the new password to PAM. IDM takes care of synchronizing password on the database through the respective database driver. For more information, refer the Driver Implementation guide on the PAM documentation page. Although the latest IDM driver version is 4.8.x, ensure that you use 4.5.x version of the IDM driver package, as 4.5.x version is currently supported with Privileged Account Manager.

      NOTE:Before you delegate password check-in to Identity Manager ensure that both the Privileged Account Manager IDM driver and database driver are operational.

    • Internal: Use this option, if you want Privileged Account Manager to manage password change.

      Select the appropriate Password Policy that must be used when Privileged Account Manager generates a new password. By default Default Password Policy is selected. You can either modify the default password policy or create a new password policy.

    • Proxy Connector Setting

    • Database IP Address: Specify the IP address or the Host Name of the Database.

    • Database Port: Specify the Database port number.

    • Connection Protocol: Select TCP or TCPS.

    • Database SSL Version: In case you have selected TCPS, specify if it is Any Database SSL version, or the specific one from the dropdown list.

    • DBAudit Servers: You can either select All or Selected server. Specify the proxy port.

Adding Database Connectors Using Command Control

You can add the database connectors for any required agent which has the dbaudit module to connect to the supported database. You can add any number of database connectors to an agent listed on the Database Connectors page.

Adding Database Connector for Oracle

  1. On the home page of the console, click Hosts.

  2. In the left pane, click Database Connectors.

    The Database Connectors page displays all the agents that have dbaudit package installed with the list of connectors.

  3. Click Add on the bar for the required agent.

    If you have already added a connector, you can modify it as required by clicking the required connector field.

  4. Specify the following:

    • Type: Select Oracle from the drop-down menu.

    • DB Proxy Port: Specify the port on which the Privileged Account Manager accepts the connection from database clients to connect to a specific database server. Privileged Account Manager maps this port number to a specific database that has a specific DB address and DB Port.

    • DB Server Address: Specify the IP address or host name of the Oracle database.

    • DB Server Port: Specify the port number of the Oracle database.

    • Connection Protocol: Select TCP for non-SSL connection or TCPS for an SSL connection.

    • DB SSL Version: Specify the SSL version used on the Oracle database server.

    NOTE:

    • To use SSL, import the Privileged Account Manager certificate to the database client’s wallet.

    • If you are using Oracle 11.x or earlier versions of Oracle for an SSL connection, Privileged Account Manager supports only the TLS1V0 SSL version.

    • If you are using Oracle 12.x, Privileged Account Manager supports the TLS1V0, TLS1V1 and TLS1V2 versions.

  5. Click Save.

    When you save the configuration, the agents containing the dbaudit package restarts.

Adding Database Connector for Microsoft SQL Server

For Microsoft SQL Server database you can add a Microsoft SQL Server database connector using the port number or using the Microsoft SQL Server instance.

Adding Database Connector Using Port Number

  1. On the home page of the console, click Hosts.

  2. In the left pane, click Database Connectors.

    The Database Connectors page displays all the agents that have dbaudit package installed with the list of connectors.

  3. Click Add on the bar for the required agent.

    If you have already added a connector, you can modify it as per requirement by clicking the required connector field.

  4. Specify the following:

    • Type: Select Microsoft SQL Sever from the dropdown menu.

    • Use with Instance: The Use with Instance checkbox is selected by default. Uncheck this to configure the connector with the database port number.

    • DB Proxy Port: Specify the port number on which the Privileged Account Manager accepts the connection from database clients to connect to a specific database server. Privileged Account Manager maps this port number to a specific database that has a specific DB address and DB Port.

    • DB Server Address: Specify the IP address or host name of the Microsoft SQL server.

    • DB Server Port: Specify the port number of the Microsoft SQL server.

    • Network Packet Size: The default value is 4096. You can enter any value within the range 512 to 16000.

      NOTE:You need to enter the same value as specified here in the client, while connecting through this connector.

Adding Microsoft SQL Server Connector Using Named Instance

  1. (Optional) If you know the Microsoft SQL Server instance name, perform the following:

    1. On the home page of the console, click Hosts.

    2. In the left pane, click Database Connectors.

      The Database Connectors page displays all the agents that have dbaudit package installed with the list of connectors.

    3. Click Add for the required agent.

    4. Specify the following:

      • Type: Select Microsoft SQL Sever from the dropdown menu.

      • Use with Instance: The Use with Instance checkbox is selected by default.

      • DB Proxy Port: Specify the port number on which the Privileged Account Manager accepts the connection from database clients to connect to a specific database server. Privileged Account Manager maps this port number to a specific database that has a specific DB address and DB Port.

      • DB Server Address: Specify the IP address or host name of the Microsoft SQL server.

      • Instance Name: Enter the Database Instance name and click Fetch Details.

        NOTE:The SQL Server Browser service should be enabled in the SQL Server for which the instances are being fetched.

      • DB Server Port: Specify the port number of the Microsoft SQL server.

      • Dynamic Port: Click the Dynamic Port checkbox if a dynamic port is set for the configured server.

      • Network Packet Size: The default value is 4096. You can enter any value within the range 512 to 16000.

        NOTE:You need to enter the same value as specified here in the client, while connecting through this connector.

  2. (Optional) If you do not know the Microsoft SQL Server instance name, you can search and fetch the instance as follows:

    1. On the home page of the console, click Hosts.

    2. In the left pane, click Database Connectors.

      The Database Connectors page displays all the agents that have dbaudit package installed with the list of connectors.

    3. Click Microsoft SQL Server Instances.The Microsoft SQL Server Instances window is displayed.

    4. Enter the host name or the IP for which you want to fetch the instances and click Fetch.

      NOTE:The SQL Server Browser service should be enabled in the SQL Server for which the instances are being fetched.

    5. Select the desired instance and click Ok.

      NOTE:Click the Dynamic Port checkbox if a dynamic port is set for the configured server.

    6. Click Save.

Adding Database Connector for Other Databases

Perform the following for adding the connectors for the databases MySQL, PostgreSQL, MariaDB, Sybase, and IBM Db2:

  1. On the home page of the console, click Hosts.

  2. In the left pane, click Database Connectors.

    The Database Connectors page displays all the agents that have dbaudit package installed with the list of connectors.

  3. Click Add on the bar for the required agent.

    If you have already added a connector, you can modify it as required by clicking the required connector field.

  4. Specify the following:

    • Type: Select the desired database from the drop-down menu.

    • DB Proxy Port: Specify the port number on which the Privileged Account Manager accepts the connection from database clients to connect to a specific database server. Privileged Account Manager maps this port number to a specific database that has a specific DB address and DB Port.

    • DB Server Address: Specify the IP address or host name of the database.

    • DB Server Port: Specify the port number of the database.

    • Connection Protocol: Select TCP for non-SSL connection and TLS for an SSL connection.

      This option is visible only for the databases for which you can choose the connection methods.

      Databases

      Connection Protocols

      Sybase

      You can choose TCP or TLS (SSL Connection) connection protocol.

      MySQL and MariaDB

      Privileged Account Manager dynamically selects the protocol based on the database client and database server configuration.

      PostgreSQL

      Privileged Account Manager supports only TCP protocol in this release.

      IBM Db2

      Privileged Account Manager supports only TCP protocol in this release.

    • Enable SHA Cipher Suites: This option allows Privileged Account Manager to use SHA cipher suites lower than SHA256 for communicating with database client and server.

      By default, this option is enabled because most of the third party database clients use SHA cipher suites for SSL communication.

  5. Click OK.

    When you save the configuration, the agents containing the dbaudit package restarts for the connector configurations to take effect.

Managing Database Connectors

You can remove or edit the database connectors for any required agent which has the dbaudit module to connect to the supported database.

Viewing Database Connectors

To view a database connector, perform the following:

  1. On the home page of the Administration console, click Hosts.

  2. In the middle pane, select the root domain, Hosts.

  3. In the left pane click Database Connectors.

    The Database Connectors page lists all the agents and its connectors on which dbaudit module is installed.

  4. (Conditional) If you can view only the agents, but not the connectors then you can click on the bar. The page expands the view and displays all the database connectors for the specific agent.

    It expands the view and all database connectors for the specific agent gets displayed.

  5. (Conditional) If you want to expand the view to display all the connectors for all the agents, click Expand All.

  6. (Conditional) If you want to collapse the view to display only the agents that contain the dbaudit package, click Collapse All.

If any agent that contains the dbaudit package is offline, Privileged Account Manager displays the agent with offline message on the database connectors page.

Removing Database Connectors

To remove a database connector, perform the following:

  1. On the home page of the Administration console, click Hosts.

  2. In the left pane, click Database Connectors.

    The Database Connectors page displays all the agents that have dbaudit package installed with the list of connectors.

  3. To delete a connector, click on the required connector for the required agent, then click Remove > Save.

Modifying Database Connectors for an Agent

You can add, remove, or modify the database connectors for any specific agent that has the dbaudit module.

To view, add, remove, or modify the database connector for a specific agent, perform the following:

  1. On the home page of the administration console, click Hosts.

  2. In the left pane, click Database Connectors.The Database Connectors page displays all the agents that have dbaudit package installed with the list of connectors.

  3. Click dbaudit package to display the Modify and Remove options.

  4. Click Modify to display the Modify Database Connector window.

    NOTE:For Microsoft SQL Server database connector, Database Address and Instance Name fields cannot be modified. The Instance Details will be displayed.

  5. Click Remove to delete an added connector.

    If you have already added a connector, you can modify it by clicking the required field.

Database Monitoring Using Access Control

Create a database monitoring permissions using Access Control:

  1. On the home page of the console, click Access Control.

  2. In the Access Control pane, create resource pool for database users by clicking Create.

    1. In the General page enter the name, description and select the Database type for which you want to create the resource pool. Example: Microsoft SQL.

    2. Click Next

    3. Click +Add to select Microsoft SQL database. The resources are populated from the resources configured in the Credential Vault. If you have not done configure it at this point to view and select the appropriate resources.

    4. Click Create. You can view the newly created resource pool using Access Control > Resource Pools.

  3. Create user role of database users for database monitoring.

    1. To create this role, go to Access Control > User Roles > Create > General – specify the fields name and description. Click Next.

    2. In the Included Members page, click Add and select Database users. Click Add to select the users you want to add.

  4. Create an assignment.

    1. To configure the assignment, select the Access Control > Assignment, click Create Assignment.

    2. From the Resource Pools page, select the database you want to create the assignment for. Example: My SQL.

    3. Click Select.

    4. Select the User Role. Example: DB Users.

    5. Add a Description.

    6. Add Permissions. Example: My SQL Database Access and set the following fields

      • Time Restrictions: All Days (24 hours), Specify time range starting and ending. If you want custom setting use custom days.

      • Access and Monitoring Options page: Move the slider to the right if you want to disable Session Capture, by default this option is set to enable.

      • Customization page: add the customized scripts.

    7. Click Finish.

  5. You are redirected to the Assignments page, Click Create. Assignment created successfully message is displayed.

For more information about creating Resource Pools, User Roles, and Assignments, see Access Control.

Adding Rules for Database using Command Control

After adding the appropriate database connector, you must add rules to provide access to the database. You can add the database rule manually or by using the policy template.

  1. On the home page of the administration console, click Command Control.

  2. To add a rule and provide the access to supported databases, perform the following:

    1. (Conditional) To add the rules automatically using policy template, perform the following:

      1. In the Command control pane, click Rules.

      2. In the details pane, click Add Policy Template and then select the required policy from the drop-down list. For example, select Oracle DB Session to add rules for Oracle database.

      3. Click Import.

        When you click import a new rule is added and based on the type of policy selected, the appropriate command is also added to the rule. You can further edit the rule as required.

    2. (Conditional) To add the rules manually, perform the following:

      1. In the Command control pane, click Rules.

      2. In the details pane, click Add.

      3. Specify a name for the database rule, then click Add.

      4. To configure the rule, select the rule, click edit icon in the details pane.

        Configure only the following:

        Session Capture: Select On to capture the activities done by the user.

        Authorize: Select Yes, then select Stop from the drop-down list.

      5. Click Modify.

        The settings that are defined for the rule are displayed in the console.

      6. In the middle pane, click the Commands icon.

      7. From the list of commands, drag the required database command and drop it to the database rule.

        NOTE:In case the user needs to have restricted access for specific instances of Microsoft SQL Server, you can create custom commands and drag it to the database rule. For example, if you want to provide restricted access to user for one of the two instances, then you need to add <DBMSSQLAccess> InstanceName1 under Commands field when creating the custom command.

7.4.7 Viewing Database Activity

To view the activities of a database user, perform the following:

  1. In the Reports console, select the appropriate database command, such as DBOracleAccess command for Oracle database, DBMSSQLAccess command for Microsoft SQL Server database, and so on.

    Command control keystroke reports appears, which displays all the commands executed by the user on the database on that particular session.

  2. (Conditional) If Command Risk for database query/ table is defined in the Command Control console, based on the level of risk a color is displayed against a particular input.

    You can disconnect a session if the activity of a user is suspicious.

    NOTE:

    1. When a user logs in to any database server through Privileged Account Manager, the database session can contain multiple connections. If the user executes any suspicious query (for which auto-disconnect is configured in the Command Risk), Privileged Account Manager disconnects the connection on which the query is executed. The user can still use the existing session, or establish a new database session. If the suspicious query results in blocking the user (if Auto Block is also configured in the Command Risk), Privileged Account Manager will not allow any new session, or any new connections within the existing sessions.

    2. For any database, Privileged Account Manager disconnects a session if auto-disconnect is configured for a user. In case of such progressive session with multiple active connections, if the Privileged Account Manager terminates any connection, the remaining connections of the session won't be affected.