Securing Notification Services
Maintaining security is a primary task for administering SQL Server 2005 Notification Services. You need to make sure that all applications and users have the permissions required to perform necessary work, but not excessive permissions that can undermine security. Also, you must make sure that unauthorized applications and users cannot read or modify instance and application data.
This section describes the accounts used to deploy, administer, and run instances of Notification Services, describes how to configure security, and documents the database roles used by Notification Services.
For an overview of the Notification Services security model and recommended security practices, see Security Considerations for Notification Services.
In This Section
| Topic | Description |
|---|---|
Provides an overview of the accounts needed to deploy, administer, and run an instance of Notification Services. |
|
Permissions Required to Deploy and Administer Notification Services |
Describes the permissions required to perform deployment and administration tasks. |
Configuring Windows Accounts for an Instance of Notification Services |
Lists the account types the Notification Services engine can run under, the benefits and drawbacks of these account types, and how to specify the account if using the NS$instanceName Microsoft Windows service as the engine. |
Configuring SQL Server Permissions for an Instance of Notification Services |
Describes the SQL Server permissions required by an instance of Notification Services. |
Describes the permissions required by subscription management applications and non-hosted event providers. |
|
Describes the need to secure source and operational files. |
|
Lists the database roles created by Notification Services, and describes the purpose of each role. |
See Also
Concepts
Security Considerations for Notification Services
Other Resources
Administering Notification Services