MS SQL Server 2008 Security

Anonymous security secures the initiating service when it sends messages to an untrusted database.
Anonymous security would not protect the target service from receiving messages from the Orders database. In this scenario, the application uses the Server Broker service to send messages to the Orders database. Any messages sent from the application over the network to the Orders database will be encrypted when the conversation uses Anonymous security. In this scenario, the initiating service needs to identify the recipient of the work order, but the target service does not need to verify the identity of the initiating service. Therefore, the initiating service should run as a member of the fixed database role public in the Orders database.

You should configure the AuthenticationTypes setting to RSWindowsKerberos in the RSReportServer.config file to ensure that all client applications and third-party Web browsers use Kerberos authentication. In the RSReportServer.config file, you have the option to set the following AuthenticationTypes settings:RSWindowsNegotiate - Allows both Kerberos and NTLM authentication. RSWindowsKerberos - Used if you have applications that only use Kerberos authentication. RSWindowsNTLM - Used if
you have applications cannot use Kerberos authentication.

Users who have accounts in the Windows domain or Active Directory can be authenticated with Kerberos authentication or NTLM authentication with Windows Authentication. Users who have accounts created only on the SQL server, called SQL logins, can also be authenticated.Mixed Mode is used to provide backward
compatibility for legacy clients. In this scenario, Novell NetWare clients will be authenticating to the SQL server, not Windows clients. Novell Netware, Linux, UNIX, and other operating system clients can connect to SQL Server 2008 by creating a SQL login for the users that need to connect. The SQL login is native only
to the SQL server on which it is created, and cannot be used in Active Directory domains. If the client has the same network layer protocol bound to its network adapter as the SQL server and is running the same network library or SQL Server Network Configuration protocol, the client can connect with a valid SQL Server login account. For example, a NetWare client that has TCP/IP bound to its network adapter and is running the shared protocol network library or SQL Server Network Configuration protocol can connect to a SQL server that has TCP/IP bound to its network adapter and is running the shared protocol network library or SQL Server Network Configuration protocol.