This section focuses on describing the MSSQL-specific details of connection configuration. For a detailed description on configuring connections, see General connection settings.
This section focuses on describing the MSSQL-specific details of connection configuration. For a detailed description on configuring connections, see General connection settings.
The current version of One Identity Safeguard for Privileged Sessions (SPS) has the following limitations:
MSSQL server with TCP dynamic port settings is not supported.
You must specify a static TCP port for every instance in the SQL Server Configuration Manager you want to audit. By doing so, you can configure the access to multiple MSSQL instances with multiple connection policies and specify the instances with inband or fixed targets and ports. You can also create and assign different Credential Store policies to check out SQL users' passwords of the instances.
In the MSSQL client program, always specify the address with the port number of the SPS connection policy you want to connect to.
The available MSSQL channel types and their functionalities are described below. For details on configuring Channel Policies, see Creating and editing channel policies. For a list of supported client applications, see Supported protocols and client applications.
MSSQL: Enables you to use the MSSQL protocol. This channel must be enabled for MSSQL to work.
The available channel policy options are the following: From, Target, Time policy, Four-eyes, Record audit trail, Gateway groups, Remote groups, and Content policy. Note that the Gateway groups option is used only if the user performs inband authentication using one of the supported MSSQL authentication methods (see Authentication in MSSQL). To retrieve the groups of an authenticated user from an LDAP database, you must also set an LDAP Server in the Connection Policy (for MSSQL connections, One Identity Safeguard for Privileged Sessions (SPS) uses this server only to retrieve the group membership of authenticated users, you cannot authenticate the users to LDAP from SPS). For details on configuring these options, see Creating and editing channel policies.
When setting Target, note the following:
If the connection uses DNAT (NAT destination address), the target address of the original client will be compared to the Target parameter of the Channel policy, that is not necessarily equivalent with the server's address.
If the connection is redirected to a Fix address, the redirected address will be compared to the Target parameter of the Channel policy.
For the audited MSSQL connections, SPS(SPS) supports SQL Server Authentication.
SPS records the username used in the authentication process into the Username and Remote username fields of the connection database.
For authenticated sessions, SPS can perform group-based user authorization that allows you to finetune access to your servers and services: you can set the required group membership in the Channel policy of the MSSQL connection. Note that group-based authorization in MSSQL works only for authenticated sessions (for MSSQL connections, SPS uses this server only to retrieve the group membership of authenticated users, you cannot authenticate the users to LDAP from SPS). If a username is not available for the session, SPS will permit the connection even if the Remote groups field is set.
SPS does not store failed MSSQL authentication attempts in the connection database. This means that the Verdict field of the Search page will never contain CONN-AUTH-FAIL values for MSSQL connections.
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center