Improving Web Application Security: Threats and - CGISecurity

Chapter 18: Securing Your Database Server 533 To restrict cmdExec access to the sysadmin role1. Start SQL Server Enterprise Manager, expand the SQL Server Group, and thenexpand your SQL Server.2. Expand the Management node, right-click SQL Server Agent, and then clickProperties.The SQL Server Agent Properties dialog box is displayed.3. Click the Job System tab.4. At the bottom of the dialog, select the Only users with SysAdmin privileges canexecute CmdExec and ActiveScripting job steps check box.5. Click OK.Note This change may require you to supply a user name and password. If the SQL Server serviceaccount is least privileged user (as advocated earlier in this chapter), you will be prompted for theuser name and password of an administrator account that has privileges to modify the service.Snapshot of a Secure Database ServerWhen you have a snapshot view that shows the attributes of a secured SQL Serverdatabase server, you can quickly and easily compare settings with your own server.The settings shown in Table 18.5 are based on an analysis of SQL Server databaseservers that have proven to be very resilient to attack and demonstrate soundsecurity practices.Table 18.5 Snapshot of a Secure Database ServerComponent CharacteristicsPatches and Updates Latest service packs and patches are applied for Windows 2000 and SQLServerServicesNonessential services are disabled.The MSDTC is disabled if not used.The MSSearch service is disabled if not required.The SQLServerAgent service is disabled if not required.The MSSQLServerADHelper service is disabled if not required.ProtocolsUnnecessary protocols are removed or disabled.The following protocols are not enabled on the server: NetBIOS and SMB.The TCP/IP stack is hardened.(continued)