Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The vCenter Server for Windows must use unique service accounts when applications connect to vCenter.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-94777 | VCWN-65-000034 | SV-104607r1_rule | Medium |
| Description |
|---|
| In order to not violate non-repudiation (i.e., deny the authenticity of who is connecting to vCenter), when applications need to connect to vCenter they should use unique service accounts. |
| STIG | Date |
|---|---|
| VMware vSphere 6.5 vCenter Server for Windows Security Technical Implementation Guide | 2019-12-12 |
Details
| Check Text ( C-93969r1_chk ) |
|---|
| Verify that each external application that connects to vCenter has a unique service account dedicated to that application. For example there should be separate accounts for Log Insight, Operations Manager, or anything else that requires an account to access vCenter. If any application shares a service account that is used to connect to vCenter, this is a finding. |
| Fix Text (F-100897r1_fix) |
|---|
| For applications sharing service accounts create a new service account to assign to the application so that no application shares a service account with another. When standing up a new application that requires access to vCenter always create a new service account prior to installation and grant only the permissions needed for that application. |