TABLE OF CONTENTS Security must be maintained at every level in an enterprise solution. Each of these three major SQL Server 2005 services (Reporting, Analysis, and Integration) handles security differently in terms of authenticating user accounts, authorizing access to various processing and rendering components, and connecting to the underlying data store. After reading this chapter, you will have gained the essential knowledge to protect your systems and data from unauthorized access.
For Reporting Services, we ll cover role-based security and how to secure reporting resources and define tasks that a user may perform. We ll also cover other techniques for securing reports, including data filtering and data hiding.
For Analysis Services, we ll review how Analysis Services applications are secured. For Integration Services, we ll review how Integration Services packages are secured using package-level properties, database roles, operating system permissions, and digital signatures.
You ll also learn that the default security settings can work well under certain circumstances, but there s never one single best way for all situations and that understanding the fundamentals is critical to designing a customized solution for your specific environment.
Properly securing Reporting, Analysis, and Integration Services requires careful attention to all of the SQL Server security best practices (as described in this book), in addition to standard information technology systems best practice.
Keep in mind the great importance and legal obligation of strong security. Whether it s intellectual property, personal financial data, or protected health information, there is no second chance to make it right after
