What changed in VMware vRealize Operations Manager 6.x SLES STIG V2R2V2R2 changes

VMware vRealize Operations Manager 6.x SLES STIG V2R2 (2023-10-25) replaced V2R1 (2021-07-23): 15 checks added, 14 removed. It has 212 checks, against 211 in V2R1.

V2R2 checklistV2R1 checklist Compare V2R1 and V2R2 in STIG Compare

  • 15 added
  • 14 removed
  • 0 updated

Added in V2R2 (15)

  • V-258448CAT IThe version of vRealize Operations Manager 6.x SLES running on the system must be a supported version.
  • V-258512CAT IIAny publicly accessible connection to the SLES for vRealize must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
  • V-258513CAT IIThe SLES for vRealize audit system must be configured to audit all administrative, privileged, and security actions.
  • V-258514CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through adjtimex.
  • V-258515CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through settimeofday.
  • V-258516CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through stime.
  • V-258517CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through clock_settime.
  • V-258518CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through /etc/localtime.
  • V-258519CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter the system through sethostname.
  • V-258520CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter the system through setdomainname.
  • V-258521CAT IIThe SLES for vRealize must be configured to audit all attempts to alter the system through sched_setparam.
  • V-258522CAT IIThe SLES for vRealize must be configured to audit all attempts to alter the system through sched_setscheduler.
  • V-258523CAT IIThe SLES for vRealize must be configured to audit all attempts to alter /var/log/faillog.
  • V-258524CAT IIThe SLES for vRealize must be configured to audit all attempts to alter /var/log/lastlog.
  • V-258525CAT IIThe SLES for vRealize must be configured to audit all attempts to alter /var/log/tallylog.

Removed since V2R1 (14)

  • V-239461CAT IIThe SLES for vRealize audit system must be configured to audit all administrative, privileged, and security actions.
  • V-239462CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through adjtimex.
  • V-239463CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through settimeofday.
  • V-239464CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through stime.
  • V-239465CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through clock_settime.
  • V-239466CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter system time through /etc/localtime.
  • V-239467CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter the system through sethostname.
  • V-239468CAT IIThe SLES for vRealize audit system must be configured to audit all attempts to alter the system through setdomainname.
  • V-239469CAT IIThe SLES for vRealize must be configured to audit all attempts to alter the system through sched_setparam.
  • V-239470CAT IIThe SLES for vRealize must be configured to audit all attempts to alter the system through sched_setscheduler.
  • V-239471CAT IIThe SLES for vRealize must be configured to audit all attempts to alter /var/log/faillog.
  • V-239472CAT IIThe SLES for vRealize must be configured to audit all attempts to alter /var/log/lastlog.
  • V-239473CAT IIThe SLES for vRealize must be configured to audit all attempts to alter /var/log/tallylog.
  • V-239574CAT IIAny publicly accessible connection to the SLES for vRealize must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V2R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.