ESS Policy Auditor STIG Version Comparison
ESS Policy Auditor Security Technical Implementation Guide
There are 1 differences between versions v4 r7 (July 24, 2015) (the "left" version) and v5 r1 (Jan. 24, 2024) (the "right" version).
Check H30280 - PA was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.
(U) Policy Auditor has must have the current security patches installed.
(U) The Policy Auditor version can be found by examining the properties of the policy auditor agent for the selected machine. Determine the patch level of Policy Auditor. The Policy Auditor version must be the equivalent to, or greater than, the minimum mandated versions specified in USCYBERCOM TASKORD 14-0305. USCYBERCOM TASKORDS and OPORDS can be found on SIPR: https://www.cybercom.smil.mil. The Policy Auditor baseline versions can be found in the baseline documentation of the HBSS ESS section within the DoD DOD patch repository: https://patches.csd.disa.mil/Default.aspx. If the version is less than the minimum mandated version specified in USCYBERCOM TASKORD 14-0305, this is a finding.
Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period utilized must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
(U) Install the minimum mandated version specified in USCYBERCOM TASKORD 14-0305.