Configuring the SQL Server database for AppScan® Enterprise

The AppScan® Enterprise Server configuration needs information about SQL Server. Configure the SQL Server first to save time during the AppScan® configuration. If you upgrade SQL Server to a newer version, follow these instructions as well.

Important:
SQL Server account and password best practices

To ensure security and prevent connection issues, follow these guidelines when configuring your SQL Server account for AppScan Enterprise.

  • Don't use the default 'sa' account

    The default SQL Server system administrator (sa) login must not be used for AppScan Enterprise. Using the 'sa' account is a significant security risk because information about this account is public and its permissions can't be modified. Attempting to use the 'sa' principal will result in a connection error (Source: Cannot use the special principal 'sa'). Instead, create a dedicated SQL Server login with the appropriate permissions for AppScan Enterprise.

  • Manage password expiration

    Ensure that the password for the SQL Server account you use isn't expired and isn't set to expire. A connection can fail if the user password has expired, preventing the Configuration Wizard from completing successfully. If your organization's security policy requires password rotation, you must manually update the password in AppScan Enterprise after it has been changed in SQL Server. For more information, see Resetting Service Account Password in AppScan Enterprise through the ASE AdminUtil tool.

SQL Server properties

To define server properties:

  1. Right-click the server name and select Properties > Security.
  2. In the Server Authentication section, choose Windows™ Authentication mode or SQL Server and Windows Authentication mode and click OK.
Note:
If your environment uses a named SQL Server instance for the AppScan Enterprise database, make sure that TCP/IP is enabled in the SQL Server configuration manager, and restart the SQL services for SQL Server and SQL Server browser. For example, if you specify the instance name as:SQL Server or Server\Instance name: <sql_server_host>\<sql_server_instance> instead of SQL Server or Server\Instance name: <sql_server_host>.

Database driver fallback

AppScan Enterprise 10.12.0 and later supports the Microsoft OLE DB Driver 19 for SQL Server. Database connection management uses a fallback hierarchy based on the driver availability and the Transport Layer Security (TLS) configuration of the host environment.

AppScan attempts to connect using this driver hierarchy:

  1. MS OLE DB Driver 19: The system prioritizes and attempts to connect using the Driver 19 first.
  2. MS OLE DB Driver 18: If Driver 19 is missing, the system falls back to Driver 18.
  3. SQL Server Native Client: If neither OLE DB driver is available, the system uses the Native Client (the standard operational default if TLS 1.2 or higher is active).
  4. Legacy SQL OLE DB Driver: If all modern drivers are missing, the system falls back to this legacy driver.
    Note:
    The system enforces this legacy driver automatically if TLS 1.1 or lower is active).

Encrypting a SQL Server database with EFS

If your configuration uses Microsoft SQL Server Standard Edition, and you plan to encrypt your AppScan Enterprise databases, then this procedure needs to be performed before you install AppScan Enterprise.