Windows IIS Application Pools Password Management

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Windows IIS Application Pools Password Management

L5 Sessionator

I would like to understand the requirement for password management for IIS pools. I was going through below documents and it gives option to change the password of IIS pools. I know that we have IIS installed in PVWA but am assuming it is helpful for other teams too. Hence, I want to know if anyone has been able to work on this on past and how it went? I want to know where the password are stored in iis pools so that we can achieve benefit of managing the password?

Windows IIS Application Pools | CyberArk Docs

1 accepted solution

Accepted Solutions

L7 Applicator

CyberArk IIS Application Pool Password Management

Objective

Securely manage and rotate IIS Application Pool credentials using CyberArk, eliminating manual password management.

Architecture Overview

Components involved include CyberArk Vault, Central Policy Manager (CPM), PVWA, Credential Provider (AIM/CCP), and IIS Server.

Step 1: Identify IIS App Pool Identity

Open IIS Manager, navigate to Application Pools, and check Advanced Settings → Process Model → Identity.

Step 2: Onboard Account into CyberArk

Add the IIS service account in PVWA under Accounts with CPM management enabled.

Step 3: Configure Password Rotation

Assign appropriate platform and configure rotation frequency and complexity requirements.

Step 4: Install Credential Provider

Install CyberArk AIM or configure CCP for credential retrieval on IIS server.

Step 5: Create Application Identity (AppID)

Define AppID in PVWA and restrict access to IIS server.

Step 6: Grant Access

Provide Retrieve permissions to AppID for the IIS account.

Step 7: Update IIS App Pool Password

Use a PowerShell script or CPM plugin to update IIS credentials after rotation.

PowerShell Example

Set-ItemProperty IIS:\AppPools\MyAppPool -Name processModel -Value @{userName = "domain\user"; password = "<retrieved_password>"; identityType = 3}

Alternative: gMSA

Use Group Managed Service Accounts to eliminate password rotation requirements.

Validation Steps

Force password rotation and verify IIS app pool continues functioning.

Best Practices

Use least privilege, separate accounts, enable auditing, and prefer gMSA when possible.

 

View solution in original post

1 REPLY 1

L7 Applicator

CyberArk IIS Application Pool Password Management

Objective

Securely manage and rotate IIS Application Pool credentials using CyberArk, eliminating manual password management.

Architecture Overview

Components involved include CyberArk Vault, Central Policy Manager (CPM), PVWA, Credential Provider (AIM/CCP), and IIS Server.

Step 1: Identify IIS App Pool Identity

Open IIS Manager, navigate to Application Pools, and check Advanced Settings → Process Model → Identity.

Step 2: Onboard Account into CyberArk

Add the IIS service account in PVWA under Accounts with CPM management enabled.

Step 3: Configure Password Rotation

Assign appropriate platform and configure rotation frequency and complexity requirements.

Step 4: Install Credential Provider

Install CyberArk AIM or configure CCP for credential retrieval on IIS server.

Step 5: Create Application Identity (AppID)

Define AppID in PVWA and restrict access to IIS server.

Step 6: Grant Access

Provide Retrieve permissions to AppID for the IIS account.

Step 7: Update IIS App Pool Password

Use a PowerShell script or CPM plugin to update IIS credentials after rotation.

PowerShell Example

Set-ItemProperty IIS:\AppPools\MyAppPool -Name processModel -Value @{userName = "domain\user"; password = "<retrieved_password>"; identityType = 3}

Alternative: gMSA

Use Group Managed Service Accounts to eliminate password rotation requirements.

Validation Steps

Force password rotation and verify IIS app pool continues functioning.

Best Practices

Use least privilege, separate accounts, enable auditing, and prefer gMSA when possible.

 

  • 1 accepted solution
  • 43 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!