

Repeat previous steps but this time use the name AppPool2. Input the Name ' AppPool1' and then press OK as shown: Select the task on the right titled Add Application Pool. To do so, launch the IIS Manager:Ĭlick Start, and type ' INetMgr.exe' and press Enter (if prompted, select Continue to elevate your permissions).Ĭlick the + button beside the name of your machine in the Connections section. In this step, we create two new application pools that we isolate from one another. The default provider Rsa_WAS has been successfully changed. In the command window navigate to where you saved your setProvider.exe and run the following command:.In this step, we use the setProvider.exe application created earlier to change the provider to iisWasKey and then use the IIS Manager to change the passwords: The default value for this is RsaProtectedConfigurationProvider. Type=",System.Configuration,ĬspProviderName="" useMachineContainer="true" useOAEP="false"īy default, whenever a property is encrypted, IIS uses the defaultProvider for encryption defined in nfig. UseMachineProtection="true" keyEntropy="" name="DataProtectionConfigurationProvider" UseMachineContainer="true" useOAEP="false" name="RsaProtectedConfigurationProvider"
#PASSWORD ENCRYPTION WINDOWS#
Open your %SystemRoot%\Microsoft.NET\Framework\v7\config\nfig using Windows Notepad and verify the lines to the section are present for the new provider: ke圜ontainerName="NetFrameworkConfigurationKey" cspProviderName="" Verify that these changes occurred correctly. In the command window navigate to where you saved your createProvider.exe and run the following command:ĬreateProvider.exe iisWasKey RsaKeyForWAS Rsa_WAS.Restrict NTFS file system permissions on the key files so only SYSTEM and Administrators have access.Configure each of these application pools to run under different identities and encrypt their passwords using the iisWasKey.This key will be used to encrypt every application pool's passwords. Create a new RSA key (iisWasKey) that only LOCALSYSTEM and Administrators have access to.IIS has a process called WAS that runs under the context of LOCALSYSTEM and is the only process that needs access to the application pool passwords. Net user /add AnonymousAccount1 password3

#PASSWORD ENCRYPTION CODE#
To help simplify this process, two pieces of sample code are provided that: An example of this data is the anonymous user account password. Worker process isolation, on the other hand, entails protecting data that the application pool identity needs to access. An example of this data is the application pool passwords. Application pool isolation entails protecting data that WAS (the IIS local system process) needs to access. This document provides an overview of the steps required for setting both application pool and worker process isolation for IIS 7.0 and above servers.
