Dynamic account groups are associated with rules engines that run when pertinent objects are created or changed. For example:
- Whenever you add or change an asset account, all applicable rules are reevaluated against that asset account.
- Whenever you change an asset account rule, the rule is reevaluated against all asset accounts within the scope of that rule. In other words, the rule is reevaluated against all asset accounts for grouping and the asset accounts within the designated partitions for tagging.
You can create a dynamic account group without any rules; however, no accounts will be added to this dynamic account group until you have added a rule.
In large environments, there is a possibility that the user interface may return before all of the rules have been reevaluated and you may not see the results you were expecting. If this happens, wait a few minutes and Refresh the screen to view the results.
Related topic:
Adding a dynamic account group
There are three ways a password or SSH key can change while a user has it checked out.
- An Asset Administrator manually changes the password or SSH key. See: Checking, changing, or setting an account password or Checking, changing, or setting an SSH key.
- A profile was scheduled to automatically change the password or SSH key. See: Change Password or Change SSH Key settings.
- A policy allows both simultaneous access and requires that the password or SSH key change when a user checks it in.
If the password or SSH key changes while a user has it checked out, and the current request is still valid, the user can select either Copy or Show Password or Show SSH Key again to obtain the new password.
Safeguard for Privileged Passwords requires port availability for various system operations.
Port details
Safeguard network port details are in the following table.
Table 288: Safeguard ports
|
|
MGMT |
TCP |
HTTPS used for a secure first-time configuration of the appliance. The IP address is a fixed address that cannot be changed. It is available in case the primary interface becomes unavailable.
Typically used: TCP/443 and IP address: 192.168.1.105 |
| Base operation |
25 |
TCP |
SMTP: Simple Mail Transfer |
| Base operation |
53 |
TCP / UDP |
DNS (Domain Name Server) |
|
Base operation |
123 |
|
NTP time synchronization |
|
Base operation |
88 |
UDP |
For communication with Active Directory, Safeguard uses port 88 (for example, Kerbos authorization against Active Directory). |
|
Base operation:
AD Asset and Account Discovery, password check and change |
389 |
TCP/UDP |
LDAP used for Active Directory Asset Discovery and Directory Accounts Discovery. The standard global catalog port, 3268 (LDAP), must be open on the firewall for every Windows global catalog server in the environment and SPP Appliance to communicate for directory management tasks (for example, adding a directory account, a directory user account, or a directory user group). LDAP uses port 389 for unencrypted connections. For more information, see the Microsoft publication How the Global Catalog Works.
For basic functionality when changing an OS account password, the following ports are required:
- Windows Active Directory: TCP/389 and TCP/445
- Windows, Windows Desktop: TCP/445
Also see:
|
|
Base operation (password and SSH key check and change) |
445 |
TCP SMB |
NetLogon Service (NP-In) is used to perform:
- Password check and changes for Windows Active Directory
- Password and SSH key check and changes for Windows, Windows Desktop.
Also see port 389 and Preparing Windows systems |
| LDAPS |
636 |
|
Supported for non-AD LDAP providers. The default LDAPS port is 636. Port 636 needs to be open to use LDAPS for non-AD LDAP providers. |
|
WMI |
135
(49152-
65535
Windows) |
TCP |
The firewall must be configured to allow Windows Management Instrumentation (WMI) for computer name and other lookups. WMI is also required if SPP performs any of the functions listed below on any Windows machine (whether it be a dependent system or a normal target platform):
- Managing service account passwords
- Managing scheduled task passwords
- Restarting a service
- Using Account Discovery on the target
WMI / DCOM from DPA will need access to TCP/135 to initiate communication on the target. The conversation continues on a random negotiated port. On Windows 7 and Windows 2008 (and above) this is in the range: 49152 - 65535.
To limit the ports used by WMI/DCOM, refer to these Microsoft articles:
For Windows Active Directory, if using Account Discovery or Auto Discovery CLDAP ping UDP/389 is also required. See:
|
|
WMI |
49152-65535 |
|
See port 135 |
|
SPP/SPS internal communications |
8649 |
TCP |
Used for the SPP/SPS internal communications when SPS is linked with SPP.
- SPS to SPP:
- SPS completes the link by talking to SPP on port 8649.
- SPS authenticates a new session and acquires the password from SPP by talking on port 8649.
- SPS queries SPP for cluster information and the appliance version.
- SPP to SPS:
- SPP queries SPS for cluster information and node roles.
- SPP pushes SSH host keys to SPS when a session is initiated.
- SPP queries SPS for session playback, follow mode, and session termination.
In SPS, the nodes require UDP ports 500 and 4500 and TCP 8649. For the latest detail, see the SPS Administration Guide, Enabling cluster management. |
|
Firewall |
655 |
TCP / UDP (X0) |
TINC (655) is open for secure VPN communication between appliances in a clustered high-availability configuration. TINC perfers UDP and uses TCP if UDP is unreliable. See KB article 232671.
To enroll an appliance into a cluster, the appliance must communicate over port 655 UDP/TCP and port 443 TCP, and must have IPv4 or IPv6 network addresses (not mixed). See:
|
|
Firewall and Client and Web browser points |
443 |
TCP
(X0) |
HTTPS over TLS/SSL (443/TCP) permits inbound requests (for client/Web/API access). Used to initially log on to the appliance to join the cluster member. Users must have access to the cluster X0 ports on port 443.
To enroll an appliance into a cluster, the appliance must communicate over port 655 UDP/TCP and port 443 TCP, and must have IPv4 or IPv6 network addresses (not mixed). See:
The port is used to prepare VMware ESXi host. See:
|
|
Global catalog |
3268 |
|
The LDAP standard global catalog port for Active Directory. The standard global catalog port, 3268 (LDAP), must be open on the firewall for every Windows global catalog server in the environment and SPP Appliance to communicate for directory management tasks (for example, adding a directory account, a directory user account, or a directory user group). LDAP uses port 389 for unencrypted connections. For more information, see the Microsoft publication How the Global Catalog Works. Also see:
There are no services listening for this port on a member/server workstation (local configuration). |
|
Kiosk |
DB9 |
SERIAL |
To connect to the Safeguard Kiosk. See KB article 233584. |
|
Radius server |
1812 |
|
Default port number that a Radius server uses to listen for authentication requests. See Adding identity and authentication providers. |
|
SonicWALL SMA or CMS appliance |
8443 |
TCP/ UDP |
For SonicWALL SMA or CMS appliance. See information related to authenticating an asset, Password (local service account desktop client) . |
|
SQL server |
1433 |
|
The port on which the SQL server will be listening for connections. See information related to authenticating an asset, Password (local service account desktop client) . |
|
Telnet |
23 |
TCP |
Telnet |
Platform ports
ACF2 – 23
ACF2 LDAP – 389
AIX – 22
AWS – 443
Cent OS – 22
Cisco Pix – 22
Debian – 22
IDRAC – 22
ESXi - 443 default
F5 - 22 default
Fortinet – 22 default
Free BSD – 22
HP iLO
IBM i – 23
JunOS – 22
MongoDB - https://docs.mongodb.com/manual/reference/default-mongodb-port/
MySQL – 3306
Oracle – 1521
Oracle Linux – 1521
OSX – 22
Other – port is not supported for the platform
Other Managed - port is not supported for the platform
Linux – 22
Pan OS – 22
PostgreSQL – 5432 default
RACF – 23
RACF LDAP – 389
RHEL – 22
SAP Hana – 39013 default
SAP Netweaver – 3300
Solaris – 22
SoniOS – 22
SonicWall SMA – 22
SQL – 1433
SUSE – 22
SyBase – 5002
Top Secret – 23
Top Secret LDAP – 389
Ubuntu – 22
Windows (various depanding on OS type) – 135/389/445 and maybe dynamic ports
Archiving
Archiving uses uses SFTP/SCP and CIFS.
- SFTP/SCP: 22 TCP (X0). See the Port details table, appliance port 22 for X0.
- CIFS: Uses UDP ports 137 and 138 and TCP ports 139 and 445.
Backup
Same as Archiving.
External Authentication
Federation – Port 443
Secondary Auth – Radius Port 1812
Starling - Port 443
External Integration
SNMP – Port 162 UDP
SMTP - Port 25 TCP Simple Mail Transfer
SysLog – 514 UDP
External Integration for Password and SSH key Workflow
Approval Anywhere - 443
Ticketing – ServiceNow 443
Ticketing - Remedy 1433 (communicates to the SQL server directly)
Other
NTP – port 123 UDP
Directories – Ports 389 LDAP and 3268 global catalog
Safeguard for Privileged Passwords version 2.7 was simplified to allow for a separation of duties based only on identity management, asset management, access policy configuration, and appliance maintenance. In the migration to version 2.7 or later, greater flexibility is realized through these high-level assignments:
- Directories are migrated to assets.
- Accounts include both directory accounts and asset accounts.
- Each directory is assigned its own partition in the migration to version 2.7 or later.
The following information details the changes from version 2.6 to version 2.7 or later. The same information is generally true if you are upgrading from version 2.1 forward to version 2.7 or later.
Before you migrate
- Make sure you back up before migrating to version 2.7 or later.
-
Be sure you have data you want to migrate and perform general clean up. For example, if you have entities that are not needed, remove them before migrating.
-
Complete as many outstanding Access Requests as possible. This is especially important for Active Directory Access Requests because any outstanding Active Directory Access Requests will need to be recreated after the migration since they cannot be resubmitted.
- Save all necessary version 2.6 logs. Directory log history prior to the migration to version 2.7 or later is not available after the migration. Details follow.
- Before the migration to version 2.7 or later, Directory Administrators, Asset Administrators, and Auditors can see audit log history for each of the directories, regardless of who created or changed them.
- The migration takes Directories and turns them into directory assets. All associated relationships with directories are also migrated to the new directory assets. The Directory Administrator role is removed and users with Directory Administrator permission are assigned as a partition owners for directories that are migrated to assets.
- After the migration to version 2.7 or later, the Asset Administrator can see the directory asset whose audit log history starts on the day of the migration. Events prior to migration are not available.
- We recommend two clients:
- A version 2.6 client to connect to older appliances
-
A new version 2.7 or later client to get the new features of Directory Assets and Discovery
This recommendation is made because a new client uses v3 endpoints. A version 2.6 appliance doesn't know how to respond to v3 calls. An new client pointed to an old appliance will get an error when trying to connect. You will see this message: The Safeguard desktop application is not compatible with this appliance. Please contact your administrator.
What to expect
The following lists entity changes you will note in the migration to version 2.7. or later.
Directories are migrated to Assets
-
Directories are migrated to assets with the appropriate platform assignment.
- Directories are still synced with Safeguard.
- Migrated directory assets reflect any account dependencies with Windows services and task on other assets.
-
You can select whether a directory asset manages the forest or a subset of the forest. Multiple assets can be assigned against the same forest.
-
Every migrated directory has Managed Forest selected so the administrator can create a directory to manage a domain or part of a domain. As assets, directories can be shared and all domains in a forest can be managed from one instance of a domain. Navigate to Administrative Tools | Asset | Management tab | Managed Forest check box.
-
Every migrated directory asset has Available for discovery across all partitions selected so the asset is available for asset and account aiscovery jobs beyond partition boundaries. Any partition that exists is able to use this directory asset. Navigation: Administrative Tools | Asset | Management tab | Available for discovery across all partitions check box.
- Discovery detail grids will identify migrated directory assets with a Partition value of Import.
-
Each migrated directory asset is assigned to its own partition and includes the Account Discovery jobs, the check and change schedules, account password rules, password sync groups, and related functions.
- To view the Account Discovery job assigned as the results of migration, navigate to Administrative Tools | Asset. Select the directory asset then Edit. Then navigate to | Account Discovery tab to see the selected Account Discovery job for the partition. If no schdule is selected, this message displays: No Account Discovery Chosen.
- Directory tags are migrated into the appropriate partition tag. To copy a tag to a new partition, change the description then copy the tag.
Administrative Tools | Directories removed and Discovery added
When Safeguard for Privileged Sessions version 2.7 is installed, directories, discovery jobs, and other related entities automatically migrate to the appropriate associations. The Administrative Tools | Directories selection is gone, and Administrative Tools | Discovery has been added. Functionality is reorganized and streamlined for better data control.
Discovery
- During migration, existing partition account discovery jobs are separated by platform type, for example, Unix, Windows, or Directory. As a result, you will see discovery jobs with the same name and a different prefix which denotes the platform. For example, you may see:
Each discovery job is assigned the appropriate asset and settings that apply to the platform.
You can rename or delete jobs, as needed. Navigate to: Administrative Tools | Discovery.
Account changes
- Accounts include directory accounts and asset accounts.
- Directory accounts are migrated into accounts and are assigned to the appropriate asset.
- Accounts identify the dependent assets.
-
Every migrated account has Available for use across all partitions selected. For example, if you create an asset service account with this check box selected, the service account could be used from anywhere.
Navigate to Administrative Tools | Account | Management tab | Available for use across all partitions check box.
- You cannot add the same account to multiple partitions from the same domain.
-
You can select a directory account and view the assets that have dependency on the directory account.
Navigate to Administrative Tools | Accounts | Dependent Assets.
Dynamic account group changes
The rules for dynamic asset groups and dynamic account groups include attributes for directory assets.
NOTE: Dynamic asset groups rule attributes do not include attributes for directory accounts. A directory cannot be the target of an asset group because you can not get an RDP or SSH session to them. Dynamic asset groups are for Security Policy Administrator control and directories are not included in policies.
Identity and authentication provider migration
A directory identity provider is managed by creating a directory asset which points to the same directory. The directory identity provider can be created and, optionally, put under management or not.
During migration from earlier versions of Safeguard for Privileged Passwords, if there are Active Directory users and user groups, SPP determines if Active Directory should be the identity provider or not. To see the result of the migration:
- Navigate to Administrative Tools | Settings.
- Select the directory then the General tab.
- Scroll down to Available Domains for Identity and Authentication to view the domains selected for the directory. Directory groups require the forest root domain to be visible and available for identity and authentication set on Administrative Tools | Settings | External Integration | Identity and Authentication. For more information, see Available Domains for Identity and Authentication (for Active Directory).
After the initial migration to version 2.6, add the identity provider.
Entitlements and access request policies
- Entitlement access request policies are migrated. If the access configuration for the asset-based session asset is a directory and you are using the version 2.6 desktop client, the name of the directory account may be blank since version 2.6 understood only one assignment and version 2.7 or later handles multiple assignments. To verify this, navigate to the Entitlements | Access Request Policy | Access Config tab. For directory accounts, the Asset-Based Session Access is correctly identified as a Directory Account, however, the directory account name is blank.
Management
Directories can be subdivided so administrators can be assigned to manage portions of a directory. For example, Admin A may only manage objects in the Finance organizational unit (OU) of the directory, and Admin B may only manage objects in the Engineering OU of the directory. This is possible via the settings on Assets including the asset Name, Domain Name, and whether to Manage Forest. This way, multiple assets can govern the same domain.
Directory accounts can be service accounts to other assets to run windows services/tasks on assets to keep password changes in sync.
Administrator role changes
- The Directory Administrator role is removed, and users with Directory Administrator permission are assigned as partition owners for directories that are migrated to assets. This role does not include the ability to manage identity providers.
- An Authorizer Administrator can now add an Active Directory forest only for identity to use as an unprivileged service account for connection.
- An Asset Administrator can now:
- Use service accounts to manage Active Directory. The service accounts can have limited permissions within a single domain.
- Use multiple service accounts for managing the same Active Directory domain with different limited permissions within the domain. For example, the administrator can add the domain as a managed asset multiple times with different service accounts.
- Use a service account from Active Directory to manage an asset from a different partition so that the administrator does not have to add that Active Directory to each of the administrator’s partitions.
- Set up a dependent system for a service running as an Active Directory account that isn’t in the administrator’s partition. This avoids having to add the Active Directory asset or the account to the partition.
- Add Active Directory for authentication to Safeguard for Privileged Passwords without managing any of the accounts in Active Directory.
- Set up multiple assets for the same domain.
