You might want to enable security for a particular application if an application has security needs that are different from those required by other applications on the machine. For instance, you might decide to use machine-wide settings for your applications that require a low level of security, but set a higher level of security for a particular application.
Keep in mind the fact that the application-wide settings that you set in the registry using Dcomcnfg.exe can be overridden if a client calls CoSetProxyBlanket to set security for a particular interface proxy. Or, if a client or server (or both) call CoInitializeSecurity to set security for a process, the settings in the registry will be ignored and the parameters specified to CoInitializeSecurity will be used instead.
When enabling security for an application, there are several settings that may need to be modified. These include authentication level, location, launch permissions, access permissions, and identity. For step-by-step procedures, see the following topics: