All pages
Powered by GitBook
1 of 9

Azure

Password Rotation in the Azure Environment

Overview

In this section, you will learn how to rotate user credentials within the Azure network environment across various target systems. Rotation works on the devices configured and attached to the Azure Active Directory (Azure AD) which can also be your default directory.

KeeperPAM can rotate the password for Azure AD users, service accounts, local admin users, local users, managed services, databases and more.

KeeperPAM Record Types

Configurations for the Azure Active Directory are defined in the PAM Configuration section of Keeper Secrets Manager.

Configurations for the Azure AD joined devices are defined in the PAM Directory, PAM Machine, and PAM Database record types. The credentials and user accounts are defined in PAM User records. The following table shows the supported Azure AD joined devices with Keeper Rotation and their corresponding PAM Record Type:

Azure AD Joined Device
Corresponding PAM Record Type

Azure AD Domain Services

PAM Directory

Virtual Machines

PAM Machine

Managed Databases

PAM Database

Prerequisites for Rotation

Prior to rotating user credentials within your Azure environment, you need to make sure you have the following information and configurations in place:

  1. All Azure AD joined devices that you want to use with Rotation need to be created and configured within your Azure Active Directory

  2. To successfully configure and setup Rotation within your Azure Network, the following values are needed for your PAM Configuration:

Field
Description

Client ID

The application/client id (UUID) of the Azure application

Client Secret

The client credentials secret for the Azure application

Subscription ID

The UUID of your subscription to use Azure services (i.e. Pay-As-You-GO)

Tenant ID

The UUID of the Azure Active Directory

  1. Make sure all the Azure services or Azure AD joined devices you plan on using for rotation have access to the Azure Active Directory.

  2. Create a custom role to allow application to access/perform actions on various Azure resources. For more information see the Azure Environment Setup document.

Setup Steps

At a high level, the following steps are needed to successfully rotate passwords on your Azure network:

  1. Create Shared Folders to hold the PAM records involved in rotation

  2. Create PAM Machine, PAM Database and PAM Directory records representing each resource

  3. Create PAM User records that contain the necessary account credentials for each resource

  4. Link the PAM User record to the PAM Resource record.

  5. Assign a Secrets Manager Application to all of the shared folders that hold the PAM records

  6. Install a Keeper Gateway and add it to the Secrets Manager application

  7. Create a PAM Configuration with the Azure environment setting

  8. Configure Rotation settings on the PAM User records

Use Cases:

  • Azure AD Users

  • Azure VM Local Users

  • Azure Managed Database

  • Azure App Secret

Loading...

Loading...

Azure Managed Database

Rotate Azure Managed Database credentials with Keeper

In this section, you will learn how to rotate DB User or Admin credentials on the following Azure Managed Databases:

  • Azure SQL

  • Azure MySQL

  • Azure MariaDB

  • Azure PostgreSQL

Loading...

Loading...

Loading...

Azure PostgreSQL - Single or Flexible Database

Rotating Admin/Regular Azure PostgreSQL Single or Flexible Database Users with Keeper

Overview

For Azure Managed PostgreSQL database, the Azure SDK will be used to rotate the password of Database Admin Accounts. To rotate the passwords of Regular Database Users, Keeper connects to the DB instance with the provided admin credentials and executes the necessary SQL statements to change the password.

Prerequisites

This guide assumes the following tasks have already taken place:

  • Your Keeper Gateway is able to communicate with the Azure Managed PostgreSQL database

1. Set up a PAM Database Record

The PAM Database record links to the admin credentials and necessary configurations to connect to the PostgreSQL Server on Azure. Keeper Rotation will use these provided configurations to rotate passwords of regular database user accounts in the Azure PostgreSQL Server instance. These provided admin credentials need to also have sufficient database permissions to successfully change the credentials of the database user accounts.

The following table lists all the required fields on the PAM Database Record:

Field
Description

Title

Keeper record title Ex: Azure PostgreSQL Admin

Hostname or IP Address

The Database Server name i.e testdb-psql.postgresql.database.azure.com

Port

Use SSL

Check to perform SSL verification before connecting, if your database has SSL configured

Administrative Credentials

PAM User admin account username that will perform rotation. If the Admin account in the DB user table is in a Host other than %, add the Host value to the user name as USERNAME@HOST

Connect Database

Optional database that will be used when connecting to the database server. For example, PostgreSQL requires a database and so this will default to template1.

Database ID

Name of the Azure Database Server i.e. testdb-psql

Database Type

postgresql or postgresql-flexible

Provider Group

Azure Resource group name

Provider Region

Azure Resource region i.e. East US

Note: Adding Provider Group, Provider Region, and Database ID will enable managing the PAM Database Record through the Azure SDK.

This PAM Database Record with the admin credential needs to be in a shared folder that is shared to the KSM application created in the pre-requisites. Only the KSM application needs access to this privileged account, it does not need to be shared with any users.

2. Set up PAM Configuration

Note: You can skip this step if you already have a PAM Configuration set up for this environment..

If you are creating a new PAM Configuration, login to the Keeper Vault and select "Secrets Manager", then select the "PAM Configurations" tab, and click on "New Configuration". The following table lists all the required fields on the PAM Configuration Record:

Field
Description

Title

Configuration name, example: Azure DB Configuration

Environment

Select: Azure Network

Gateway

Select the Gateway that is configured on the Keeper Secrets Manager application and has network access to your Azure PostgreSQL database from the pre-requisites

Application Folder

Select the Shared folder where the PAM Configuration will be stored. We recommend placing this in a shared folder with the PAM User records.

Azure ID

A unique ID for this instance of Azure. This is for your reference and can be anything, but its recommended to be kept short Ex: Azure-Prod

Client ID

The unique Application (client) ID assigned to your app by Azure AD when the application was registered

Client Secret

The client credentials secret for the Azure application

Subscription ID

The UUID that identifies your subscription (i.e. Pay-As-You-GO) to use Azure services.

Tenant ID

The UUID of the Azure Active Directory

3. Set up one or more PAM User records

Keeper Rotation will use the linked credentials in the PAM Database record to rotate the PAM User records on your Azure environment. The PAM User credential needs to be in a shared folder that is shared to the KSM application created in the prerequisites.

The following table lists all the required fields on the PAM User record:

Field
Description

Title

Keeper record title i.e. Azure PostgreSQL User1

Login

Case sensitive username of the account being rotated. If the user in the DB user table is in a Host other than %, add the Host value to the user name as USERNAME@SERVERNAME

Password

Account password is optional, rotation will set one if blank

Connect Database

Optional database that will be used when connecting to the database server. For example: PostgreSQL requires a database and so this will default to template1

4. Configure Rotation on the PAM User records

Select the PAM User record(s) from Step 3, edit the record and open the "Password Rotation Settings".

  • Select the desired schedule and password complexity.

  • The "Rotation Settings" should use the PAM Configuration setup previously.

  • The "Resource Credential" field should select the PAM Database credential setup from Step 1.

  • Upon saving, the rotation button will be enabled and available to rotate on demand, or via the selected schedule.

Any user with edit rights to a PAM User record has the ability to setup rotation for that record.

Loading...