STIGQter STIGQter: STIG Summary: McAfee MOVE AV Agentless 4.5 Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 11 Dec 2017:

The McAfee MOVE AV SVM settings policy must be configured to authenticate to the hypervisor/vCenter server with user name and password.

DISA Rule

SV-93213r1_rule

Vulnerability Number

V-78507

Group Title

MV45-SVM-200009

Rule Version

MV45-SVM-200009

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Access the McAfee ePO console.

Select Menu >> Policy >> Policy Catalog and then select "MOVE AntiVirus 4.5.0" from the Product list.

From the Category list, select "SVM Settings".

Select each configured SVM Settings policy.

Click "Show Advanced".

Under "SVM Configuration" (Agentless only), populate the "Username:" and "Password:" fields with a user/password combination that has authentication access to the hypervisor.

Click "Test connection settings".

Click "Save".

Check Contents

Access the McAfee ePO console.

Select Menu >> Policy >> Policy Catalog and then select "MOVE AntiVirus 4.5.0" from the Product list.

From the Category list, select "SVM Settings".

Select each configured SVM Settings policy.

Click "Show Advanced".

Under "SVM Configuration" (Agentless only), verify the "Username:" field is populated.

Note: The "Password:" field will appear to be blank. Since the "Username:" field cannot be populated and saved without a password, the "Password:" field requirement can be considered compliant provided the "Username:" field is validated as populated.

If the "Username:" field is not populated, this is a finding.

Vulnerability Number

V-78507

Documentable

False

Rule Version

MV45-SVM-200009

Severity Override Guidance

Access the McAfee ePO console.

Select Menu >> Policy >> Policy Catalog and then select "MOVE AntiVirus 4.5.0" from the Product list.

From the Category list, select "SVM Settings".

Select each configured SVM Settings policy.

Click "Show Advanced".

Under "SVM Configuration" (Agentless only), verify the "Username:" field is populated.

Note: The "Password:" field will appear to be blank. Since the "Username:" field cannot be populated and saved without a password, the "Password:" field requirement can be considered compliant provided the "Username:" field is validated as populated.

If the "Username:" field is not populated, this is a finding.

Check Content Reference

M

Target Key

3227

Comments