Get up to speed on the new security features in "Denali", the next version of SQL Server. Disclose the new permissions, roles and encryption added to Denali. You'll discover some commonly overlooked practices in securing your SQL Server databases. Learn about physical security, passwords, privileges and roles, and preventative best practices. I'll demonstrate auditing and .Net code samples to use on your applications to prevent vulnerabilities.

1. 101: Intro to Security

3. .Net Developer VB.Net and C#

4. www.extofer.com

6. Write Secure Code

7. Auditing

8. Roles

9. Best Practices

10. Passwords

11. Physical Security

12. Security Patches

13. Network Security

15. Manipulating people to gather data

16. Not using technical cracking tools or techniques

17. SQL Injection

18. Vulnerable to any RDBMS, not just MS SQL Server

19. Attacker post SQL commands via front end applications

22. DDL Triggers

23. Use Stored Procedures

24. Use Parameters

25. Customize Error Messages

26. Avoid errors returning securable names

28. User Defined Audit – applications write customer events to audit logs

29. Filtering – filter unwanted events

31. Database Roles and Server Roles

32. Server Level Roles

33. sysadmin, bulkadmin, securityadmin, dbcreator

34. “Denali” User Defined Server Roles

35. Allow creation of new Server Roles

37. Active Directory Integration

38. Supports Groups

40. Legacy or Hard Coded Referenced Logins

41. Non Windows Clients

44. ASP.Net encrypt web.config

45. Encrypt password in your code

46. Strong Passwords

47. 8 to 10 minimum characters

48. Leak speak or special characters (i.e s = 5 or 3 = E)

49. SQLPing checks for default passwords

51. Restrict access to unauthorized individuals

53. Test updates or hotfixes immediately on non-production servers

55. Don’t surf the Web on the server

56. Only enable required protocols

59. Server Operations

60. Database Actions

61. Audit Specifications

62. Server Audit Specification

63. Audit Failed Login Attempts