| Course Overview |
| Module Introduction |
| Navigation Overview |
| Lab Information |
| Designing a Server-Side Solution for SQL Server 2005 |
| Designing a Security Strategy |
| Module Introduction |
| Designing a Security Strategy for the Components of a Solution |
| Lesson Introduction |
| Considerations for Choosing Authentication Modes |
| The Process for Defining an Authorization Strategy |
| Guidelines for Designing Security for Reporting Services |
| Guidelines for Designing Security for Notification Services |
| Considerations for Designing Security for Integration Services |
| Considerations for Designing Security for Replication |
| Self Test |
| Designing Objects to Manage Application Access |
| Lesson Introduction |
| Guidelines for Using SQL Server 2005 Roles and Schemas |
| Considerations for Using the Code Execution Context |
| Guidelines for Using Stored Procedures |
| Guidelines for Using Views |
| Self Test |
| Creating an Auditing Strategy |
| Lesson Introduction |
| Guidelines for Designing an Auditing Strategy |
| Techniques for Storing Auditing Information |
| Choosing a Technique for Storing Auditing Information |
| Guidelines for Protecting Auditing Information |
| Self Test |
| Managing Multiple Development Teams by Using the Security Features |
| Lesson Introduction |
| The Common Challenges of Working with Multiple Development Teams |
| Guidelines for Managing Developer Access by Using Schemas |
| Guidelines for Auditing Development by Using DDL Triggers |
| Self Test |
| Lab: Designing a Security Strategy |
| Lesson Introduction |
| Scenario |
| Exercise: Evaluating the Security Trade-offs of SQL Server Services |
| Exercise: Designing a Security Strategy |
| Proposed Security Strategies: Solution A |
| Proposed Security Strategies: Solution B |
| Proposed Security Strategies: Solution C |
| Lab Review |
| Module Summary |
| Glossary |
| Module Introduction |