Improving Web Application Security: Threats and - CGISecurity

732 Improving Web Application Security: Threats and CountermeasuresAuditing and LoggingCheck DescriptionAll failed Windows login attempts are logged.All failed actions are logged across the file system.SQL Server login auditing is enabled.Log files are relocated from the default location and secured with access control lists.Log files are configured with an appropriate size depending on the application securityrequirement.Where the database contents are highly sensitive or vital, Windows is set to Shut Downmode on overflow of the security logs.SQL Server SecurityCheck DescriptionSQL Server authentication is set to Windows only (if supported by the application).The SQL Server audit level is set to Failure or All.SQL Server runs using a least-privileged account.SQL Server Logins, Users, and RolesCheck DescriptionA strong sa password is used (for all accounts).SQL Server guest user accounts are removed.BUILTIN\Administrators server login is removed.Permissions are not granted for the public role.Members of sysadmin fixed server role are limited (ideally, no more than two users).Restricted database permissions are granted. Use of built-in roles, such as db_datareaderand db_datawriter, are avoided because they provide limited authorization granularity.Default permissions that are applied to SQL Server objects are not altered.