11.07.2015 Views

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

508 Part IV: Securing Your Network, Host <strong>and</strong> <strong>Application</strong>●●●●●●PortsUnused ports are closed at the firewall, but it is required that servers behind thefirewall also block or restrict ports based on their usage. For a dedicated SQLServer, block all ports except for the necessary SQL Server port <strong>and</strong> the portsrequired for authentication.RegistrySQL Server maintains a number of security-related settings, including theconfigured authentication mode in the registry. Restrict <strong>and</strong> control access to theregistry to prevent the unauthorized update of configuration settings, for example,to loosen security on the database server.Auditing <strong>and</strong> LoggingAuditing is a vital aid in identifying intruders, attacks in progress, <strong>and</strong> to diagnoseattack footprints. Configure a minimum level of auditing for the database serverusing a combination of Windows <strong>and</strong> SQL Server auditing features.SQL Server <strong>Security</strong>A number of SQL Server security settings can be controlled through EnterpriseManager. These include the authentication mode, auditing level, <strong>and</strong> the accountsused to run the SQL Server service. For improved security, you should useWindows authentication. You should also enable SQL Server logon auditing <strong>and</strong>ensure that the SQL Server service runs using a least privileged account.SQL Server Logins, Users, <strong>and</strong> RolesSQL Server 2000 manages access control using logins, databases, users, <strong>and</strong> roles.Users (<strong>and</strong> applications) are granted access to SQL Server by way of a SQL serverlogin. The login is associated with a database user <strong>and</strong> the database user is placedin one or more roles. The permissions granted to the role determine the tables thelogin can access <strong>and</strong> the types of operations the login can perform. This approachis used to create least privileged database accounts that have the minimum set ofpermissions necessary to allow them to perform their legitimate functionality.SQL Server Database ObjectsThe ability to access SQL Server database objects, such as built-in storedprocedures, extended stored procedures <strong>and</strong> cmdExec jobs, should be reviewed.Also, any sample databases should be deleted.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!