20.2 Required Database Permissions and Settings

Core Services uses the VigilEntService account to connect to the SQL Server computer on which the Secure Configuration Manager database is installed. The Secure Configuration Manager console uses either the VSMConsole or VigilEnt_Users account to read and write data from the Secure Configuration Manager database. Secure Configuration Manager creates these accounts during installation.

By default, the VigilEntService, VSMConsole, and VigilEnt_Users accounts are granted the VigilEnt User Access role in SQL Server. Secure Configuration Manager creates this role during installation. Use the Microsoft SQL Server Enterprise Manager tool to verify permissions.

Microsoft SQL Server automatically grants the sysadmin role to Windows user accounts that belong to the Administrators group.

Secure Configuration Manager supports both Windows authentication and mixed-mode authentication. You can choose to use SQL authentication when you log onto the Secure Configuration Manager console.

Depending on which authentication you configure Core Services to support, the Secure Configuration Manager console can accept different account credentials at logon. If Core Services is configured to support SQL authentication, the console can accept either the VSMConsole or the VigilEnt_Users account credentials. If Core Services supports Windows authentication, the console can accept the Windows credentials of the console user. For more information, see the Secure Configuration Manager Installation Guide.