Service accounts
A service account is the credential that Privilege Secure uses to connect to a resource, directory, or database and manage its accounts. Each resource, domain, database, and Microsoft Entra ID tenant uses one service account. This page lists what each platform needs and how to add one.
Open the list from Configuration > Service Accounts in the left navigation.
Service account requirements by platform
Each platform needs different permissions. The permissions are the minimum the service account must hold on the target. For the full list, see Target environments.
| Platform | Account the service account represents | Notes |
|---|---|---|
| Active Directory | A domain account in the Domain Administrators group of the target domains. | Set Domain and Username. |
| Windows | A domain account, or a local account in the local Administrators group on each server or desktop. | A server outside a domain can reject remote PowerShell. See Target environments. |
| Linux | A local account on each server, or a central domain account for hosts bridged to Active Directory. The account is root, or has delegated sudo permissions. | Authenticate with a password, an SSH certificate, or both. For a least-privilege account, see Creating a least privilege service account for Linux resources. |
| Cisco | An account with Level 15 Privileged EXEC access, or a lower-level account with an Enable Password that raises it to Privileged EXEC mode. | The form requires Enable Password for every Cisco service account. |
| Microsoft Entra ID | An app registration with Microsoft Graph application permissions and Entra roles. | Enter the application ID and secret. See Register an app in Microsoft Entra ID. |
| Microsoft SQL Server | An account with sysadmin privileges. | See the note on Windows logins that follows. |
| Oracle | An account with SYSDBA privileges. | |
| BSD | A local account on each host with sudo rights to run the user, group, and sudoers management commands, such as pw. This is effectively root access through sudo. | The Add form doesn't offer Elevation Command for BSD, so Privilege Secure runs the commands with sudo. |
| Palo Alto PAN-OS | A PAN-OS administrator account whose admin role profile enables the XML API for configuration, operational requests, and commit. | Privilege Secure reads and changes administrator accounts through the PAN-OS XML API over HTTPS, using the username and password of this account. |
If a Cisco device has both an enable secret and an enable password, enter the enable secret in Enable Password. Cisco IOS ignores the enable password when an enable secret is set. Privilege Secure sends enable and answers the password prompt with this value, and skips that step when the device goes straight to the privileged prompt.
Before 26.07.3, SQL Server actions for a domain user created a local SQL login. From 26.07.3, they create a Windows authentication login named DOMAIN\username, and the disable and role-change actions look the login up by that name. The service account setup doesn't change: it still needs sysadmin privileges.
Add a service account
- Select Configuration > Service Accounts.
- Click the + button above the list. The tooltip reads Add Service account.
- Enter a name in Enter Service Account Name, for example
svc-ad-sync. - Enter a Description.
- Select the Platform. The default is None Specified.
- Enter the Domain and Username*.
- Enter the Password*. Select the eye icon to show the value you typed.
- To check the credential out of a vault, select a Vault Connector. The list holds
<none>and one entry for each integration connector. - Click Save.
The account appears in the list. Select a name in the list to see and edit the details. Click Save to keep an edit, or Cancel to discard it.
Service account fields
| Field | Applies to | Description |
|---|---|---|
| Name | All | The name shown in the list. |
| Description | All | A description of the account. |
| Platform | All | None Specified, Active Directory, BSD, Cisco, Entra ID, Linux, Microsoft SQL Server, Oracle, or Palo Alto PanOS. |
| Domain | All except Entra ID | The domain of the account. |
| Username | All except Entra ID | The account name. |
| Password | All except Entra ID | The account password. |
| Vault Connector | All | The integration connector that supplies the credential. See Vault connectors. |
| App ID | Entra ID | The application (client) ID of the app registration. |
| App Secret | Entra ID | The client secret of the app registration. |
| Elevation Command | Linux | The command that raises the account's privileges on the host, such as sudo, pbrun, pmrun, or dzdo. |
| Authentication Method | Linux and Cisco | Password, SSH Certificate, or SSH Certificate and Password. |
| Private Key and SSH Passphrase | Linux and Cisco with an SSH certificate method | The key and passphrase for certificate authentication. |
| Enable Password | Cisco, required | Raises the account to Privileged EXEC mode. The account can be any Cisco user at privilege level 1 to 15. Release 26.07.1 and later support Cisco devices that are configured with both an enable secret and an enable password. |
| Address, Safe, and Folder | CyberArk vault connector | The CyberArk address, and the safe and folder that hold the login account. |
| Library | HashiCorp vault connector | The library that holds the login account. |
Delete a service account
Point to the account in the list and click the trash icon. Confirm the deletion.
Check which resources use the account first. Use Change Service Account on the Resources page to move them to another account.
Managed service accounts
Privilege Secure can also manage a service account. A chip on the account shows Service Account is Managed by Netwrix Privilege Secure. See Credentials.