Export (0) Print
Expand All

Setting Client Application Process Security

Client applications that call WMI interfaces can control the security levels of their processes. All WMI applications access WMI through COM, and you can call the COM function CoInitializeSecurity to set security for your processes. Applications that make asynchronous calls to WMI and applications that register as event consumers set security levels on the call into WMI.

If you do not make an explicit call to CoInitializeSecurity, COM calls it implicitly with values from the registry. However, the registry values may have lower settings for impersonation and authentication that do not provide the security required for WMI. For more information, see Setting the Default Process Security Level Using C++.

Asynchronous access to WMI is not recommended. An asynchronous callback allows a non-authenticated user to provide data to the sink. This poses security risks to your scripts and applications. To eliminate the risks, use semisynchronous or synchronous communication, or perform proper access checks in your client application. For more information, see Calling a Method.

Calls to any of the WMI proxies (IWbemServices, IEnumWbemClassObject,IWbemCallResult, or IWbemRefresher) use an out-of-process pointer. For more information about the defaults and recommendations, see Setting the Security on IWbemServices and Other Proxies.

The following procedure describes the steps you must perform to set the security for WMI on your application process.

Aa393609.wedge(en-us,VS.85).gifTo set security for WMI on your application process

  1. Determine the security levels required for the Windows operating systems on which your client application runs.
  2. Call the COM CoInitializeSecurity function to set the default security for the process in which the client application runs. This declares how much security other applications require to access the process in which your application runs.
  3. If you need to change the security on an individual proxy, for example on another call to IWbemServices, call CoSetProxyBlanket.
  4. If you need to control remote hardware or a system object that requires more privilege, use the AdjustTokenPrivileges function to enable the necessary privileges. Note that you cannot enable a privilege that the process does not already have assigned to it. For more information, see Checking Access to Private Objects.

For further information about setting the default process security level, see Setting the Default Process Security Level Using C++ and Setting the Default Process Security Level Using VBScript.

 

 

Show:
© 2014 Microsoft