DoD Compliance · STIG

VMW vRealize Operations Manager 6.x PostgreSQL Security Technical Implementation Guide

V1R2 · · 2.5 years ago · Released 25 Oct 2023 · 69 rules

Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Digest of Updates vs. V1R1 · 28 Sep 2018 +69 −69

Comparison against the immediately-prior release (V1R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Added rules 69

V-239772 Medium The vROps PostgreSQL DB must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.
V-239773 Medium The vROps PostgreSQL DB must provide audit record generation for DoD-defined auditable events within all DBMS/database components.
V-239774 Medium The vROps PostgreSQL DB must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
V-239775 Medium The vROps PostgreSQL DB must be able to generate audit records when privileges/permissions are retrieved.
V-239776 Medium The vROps PostgreSQL DB must initiate session auditing upon startup.
V-239777 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish what type of events occurred.
V-239778 Medium The vROps PostgreSQL DB must produce audit records containing time stamps to establish when the events occurred.
V-239779 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish where the events occurred.
V-239780 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the sources (origins) of the events.
V-239781 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
V-239782 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
V-239783 Medium The vROps PostgreSQL DB must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
V-239784 Low The vROps PostgreSQL DB must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records.
V-239785 Medium The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized read access.
V-239786 Medium The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized modification.
V-239787 Medium The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized deletion.
V-239788 Medium The vROps PostgreSQL DB must protect its audit features from unauthorized access.
V-239789 Medium The vROps PostgreSQL DB must protect its audit configuration from unauthorized modification.
V-239790 Medium The vROps PostgreSQL DB must protect its audit features from unauthorized removal.
V-239791 Medium vROps PostgreSQL DB objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by vROps PostgreSQL DB principals authorized for ownership.
V-239792 Medium The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the vROps PostgreSQL DB, etc.) must be restricted to authorized users.
V-239793 Medium Default demonstration and sample databases, database objects, and applications must be removed.
V-239794 Medium The vROps PostgreSQL DB must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
V-239795 Medium The vROps PostgreSQL DB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
V-239796 Medium If passwords are used for authentication, the vROps PostgreSQL DB must store only hashed, salted representations of passwords.
V-239797 Medium If passwords are used for authentication, the vROps PostgreSQL DB must transmit only encrypted representations of passwords.
V-239798 High The vROps PostgreSQL DB must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
V-239799 Medium In the event of a system failure, the vROps PostgreSQL DB must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
V-239800 Medium The vROps PostgreSQL DB must isolate security functions from non-security functions.
V-239801 Medium vROps PostgreSQL DB contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.
V-239802 Medium The vROps PostgreSQL DB must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.
V-239803 Medium The vROps PostgreSQL DB must utilize centralized management of the content captured in audit records generated by all components of the DBMS.
V-239804 Medium The vROps PostgreSQL DB must provide centralized configuration of the content to be captured in audit records generated by all components of the DBMS.
V-239805 Medium The vROps PostgreSQL DB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.
V-239806 Medium The vROps PostgreSQL DB must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts.
V-239807 Medium The vROps PostgreSQL DB must record time stamps, in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT).
V-239808 Medium The vROps PostgreSQL DB must generate time stamps, for audit records and application data, with a minimum granularity of one second.
V-239809 Medium The vROps PostgreSQL DB must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).
V-239810 Medium The vROps PostgreSQL DB must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.
V-239811 Medium When invalid inputs are received, the vROps PostgreSQL DB must behave in a predictable and documented manner that reflects organizational and system objectives.
V-239812 High Security-relevant software updates to the vROps PostgreSQL DB must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
V-239813 Medium The vROps PostgreSQL DB must be able to generate audit records when security objects are accessed.
V-239814 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to access security objects occur.
V-239815 Medium The vROps PostgreSQL DB must generate audit records when privileges/permissions are added.
V-239816 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to add privileges/permissions occur.
V-239817 Medium The vROps PostgreSQL DB must generate audit records when privileges/permissions are modified.
V-239818 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
V-239819 Medium The vROps PostgreSQL DB must generate audit records when security objects are modified.
V-239820 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify security objects occur.
V-239821 Medium The vROps PostgreSQL DB must generate audit records when privileges/permissions are deleted.
V-239822 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
V-239823 Medium The vROps PostgreSQL DB must generate audit records when security objects are deleted.
V-239824 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete security objects occur.
V-239825 Medium The vROps PostgreSQL DB must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.
V-239826 Medium The vROps PostgreSQL DB must generate audit records when successful logons or connections occur.
V-239827 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful logons or connection attempts occur.
V-239828 Medium The vROps PostgreSQL DB must generate audit records for all privileged activities or other system-level access.
V-239829 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.
V-239830 Medium The vROps PostgreSQL DB must generate audit records showing starting and ending time for user access to the database(s).
V-239831 Medium The vROps PostgreSQL DB must generate audit records when concurrent logons/connections by the same user from different workstations occur.
V-239832 Medium The vROps PostgreSQL DB must be able to generate audit records when successful accesses to objects occur.
V-239833 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful accesses to objects occur.
V-239834 Medium The vROps PostgreSQL DB must generate audit records for all direct access to the database(s).
V-239835 High The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures.
V-239836 High The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes.
V-239837 High The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.
V-239838 Medium The vROps PostgreSQL DB must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.
V-239839 Medium The vROps PostgreSQL DB must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs.
V-258458 High The version of vRealize Operations Manager 6.x PostgreSQL running on the system must be a supported version.

Removed rules 69

V-88215 Medium The vROps PostgreSQL DB must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.
V-88217 Medium The vROps PostgreSQL DB must provide audit record generation for DoD-defined auditable events within all DBMS/database components.
V-88219 Medium The vROps PostgreSQL DB must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
V-88221 Medium The vROps PostgreSQL DB must be able to generate audit records when privileges/permissions are retrieved.
V-88223 Medium The vROps PostgreSQL DB must initiate session auditing upon startup.
V-88225 Medium The vROps PostgreSQL DB must provide authorized users to capture, record, and log all content related to a user session.
V-88227 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish what type of events occurred.
V-88229 Medium The vROps PostgreSQL DB must produce audit records containing time stamps to establish when the events occurred.
V-88231 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish where the events occurred.
V-88233 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the sources (origins) of the events.
V-88235 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
V-88237 Medium The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
V-88239 Medium The vROps PostgreSQL DB must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
V-88241 Low The vROps PostgreSQL DB must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records.
V-88243 Medium The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized read access.
V-88245 Medium The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized modification.
V-88247 Medium The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized deletion.
V-88249 Medium The vROps PostgreSQL DB must protect its audit features from unauthorized access.
V-88251 Medium The vROps PostgreSQL DB must protect its audit configuration from unauthorized modification.
V-88253 Medium The vROps PostgreSQL DB must protect its audit features from unauthorized removal.
V-88255 Medium vROps PostgreSQL DB objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by vROps PostgreSQL DB principals authorized for ownership.
V-88257 Medium The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the vROps PostgreSQL DB, etc.) must be restricted to authorized users.
V-88259 Medium Default demonstration and sample databases, database objects, and applications must be removed.
V-88261 Medium The vROps PostgreSQL DB must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
V-88263 Medium The vROps PostgreSQL DB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
V-88265 Medium If passwords are used for authentication, the vROps PostgreSQL DB must store only hashed, salted representations of passwords.
V-88267 Medium If passwords are used for authentication, the vROps PostgreSQL DB must transmit only encrypted representations of passwords.
V-88269 High The vROps PostgreSQL DB must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
V-88271 Medium In the event of a system failure, the vROps PostgreSQL DB must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
V-88273 Medium The vROps PostgreSQL DB must isolate security functions from non-security functions.
V-88275 Medium vROps PostgreSQL DB contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.
V-88277 Medium The vROps PostgreSQL DB must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.
V-88279 Medium The vROps PostgreSQL DB must utilize centralized management of the content captured in audit records generated by all components of the DBMS.
V-88281 Medium The vROps PostgreSQL DB must provide centralized configuration of the content to be captured in audit records generated by all components of the DBMS.
V-88283 Medium The vROps PostgreSQL DB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.
V-88285 Medium The vROps PostgreSQL DB must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts.
V-88287 Medium The vROps PostgreSQL DB must record time stamps, in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT).
V-88289 Medium The vROps PostgreSQL DB must generate time stamps, for audit records and application data, with a minimum granularity of one second.
V-88291 Medium The vROps PostgreSQL DB must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).
V-88293 Medium The vROps PostgreSQL DB must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.
V-88295 Medium When invalid inputs are received, the vROps PostgreSQL DB must behave in a predictable and documented manner that reflects organizational and system objectives.
V-88297 High Security-relevant software updates to the vROps PostgreSQL DB must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
V-88299 Medium The vROps PostgreSQL DB must be able to generate audit records when security objects are accessed.
V-88301 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to access security objects occur.
V-88303 Medium The vROps PostgreSQL DB must generate audit records when privileges/permissions are added.
V-88305 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to add privileges/permissions occur.
V-88307 Medium The vROps PostgreSQL DB must generate audit records when privileges/permissions are modified.
V-88309 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
V-88311 Medium The vROps PostgreSQL DB must generate audit records when security objects are modified.
V-88313 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify security objects occur.
V-88315 Medium The vROps PostgreSQL DB must generate audit records when privileges/permissions are deleted.
V-88317 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
V-88319 Medium The vROps PostgreSQL DB must generate audit records when security objects are deleted.
V-88321 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete security objects occur.
V-88323 Medium The vROps PostgreSQL DB must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.
V-88325 Medium The vROps PostgreSQL DB must generate audit records when successful logons or connections occur.
V-88327 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful logons or connection attempts occur.
V-88329 Medium The vROps PostgreSQL DB must generate audit records for all privileged activities or other system-level access.
V-88331 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.
V-88333 Medium The vROps PostgreSQL DB must generate audit records showing starting and ending time for user access to the database(s).
V-88335 Medium The vROps PostgreSQL DB must generate audit records when concurrent logons/connections by the same user from different workstations occur.
V-88337 Medium The vROps PostgreSQL DB must be able to generate audit records when successful accesses to objects occur.
V-88339 Medium The vROps PostgreSQL DB must generate audit records when unsuccessful accesses to objects occur.
V-88341 Medium The vROps PostgreSQL DB must generate audit records for all direct access to the database(s).
V-88343 High The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures.
V-88345 High The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes.
V-88347 High The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.
V-88349 Medium The vROps PostgreSQL DB must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.
V-88351 Medium The vROps PostgreSQL DB must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs.

Sort by

Expand all

The vROps PostgreSQL DB must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.

AC-10 - Medium - CCI-000054 - V-239772 - SV-239772r879511_rule

RMF Control

AC-10

Severity

CCI

CCI-000054

Version

VROM-PG-000005

Vuln IDs

V-239772
V-88215

Rule IDs

SV-239772r879511_rule
SV-98865

Database management includes the ability to control the number of users and user sessions utilizing a DBMS. Unlimited concurrent connections to the DBMS could allow a successful Denial of Service (DoS) attack by exhausting connection resources; and a system can also fail or be degraded by an overload of legitimate users. Limiting the number of concurrent sessions per user is helpful in reducing these risks. This requirement addresses concurrent session control for a single account. It does not address concurrent sessions by a single user via multiple system accounts; and it does not deal with the total number of sessions across all accounts. The capability to limit the number of concurrent sessions per user must be configured in or added to the DBMS (for example, by use of a logon trigger), when this is technically feasible. Note that it is not sufficient to limit sessions via a web server or application server alone, because legitimate users and adversaries can potentially connect to the DBMS by other means. The organization will need to define the maximum number of concurrent sessions by account type, by account, or a combination thereof. In deciding on the appropriate number, it is important to consider the work requirements of the various types of users. For example, 2 might be an acceptable limit for general users accessing the database via an application; but 10 might be too few for a database administrator using a database management GUI tool, where each query tab and navigation pane may count as a separate session. (Sessions may also be referred to as connections or logons, which for the purposes of this requirement are synonyms.)

Checks: C-43005r663691_chk

At the command prompt, execute the following command: # grep '^\s*max_connections\b' /storage/db/vcops/vpostgres/data/postgresql.conf If max_connections is not "210", this is a finding.

Fix: F-42964r663692_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET max_connections TO '210';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must provide audit record generation for DoD-defined auditable events within all DBMS/database components.

AU-12 - Medium - CCI-000169 - V-239773 - SV-239773r879559_rule

RMF Control

AU-12

Severity

CCI

CCI-000169

Version

VROM-PG-000025

Vuln IDs

V-239773
V-88217

Rule IDs

SV-239773r879559_rule
SV-98867

Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the DBMS (e.g., process, module). Certain specific application functionalities may be audited as well. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. DoD has defined the list of events for which the DBMS will provide an audit record generation capability as the following: (i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); (ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities, or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; and (iii) All account creation, modification, disabling, and termination actions. Organizations may define additional events requiring continuous or ad hoc auditing.

Checks: C-43006r663694_chk

At the command prompt, execute the following command: # grep '^\s*log_line_prefix\b' /storage/db/vcops/vpostgres/data/postgresql.conf If log_line_prefix is not set to "%m %d %u %r %p %l %c", this is a finding.

Fix: F-42965r663695_fix

At the command prompt, execute the following commands: # sed -i.bak "/log_line_prefix.*/ d" /storage/db/vcops/vpostgres/data/postgresql.conf # sed -i "$ a log_line_prefix = '%m %d %u %r %p %l %c'" /storage/db/vcops/vpostgres/data/postgresql.conf # su postgres postgres@vRealizeClusterNode:> cd /opt/vmware/vpostgres/current postgres@vRealizeClusterNode:> /opt/vmware/vpostgres/9.3/bin/pg_ctl restart -D /storage/db/vcops/vpostgres/data postgres@vRealizeClusterNode:> exit

The vROps PostgreSQL DB must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.

AU-12 - Medium - CCI-000171 - V-239774 - SV-239774r879560_rule

RMF Control

AU-12

Severity

CCI

CCI-000171

Version

VROM-PG-000030

Vuln IDs

V-239774
V-88219

Rule IDs

SV-239774r879560_rule
SV-98869

Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events. Suppression of auditing could permit an adversary to evade detection. Misconfigured audits can degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.

Checks: C-43007r663697_chk

At the command prompt, enter the following command: # ls -l /storage/db/vcops/vpostgres/data/*conf* If the permissions on any of the listed files are not "600" or more restrictive, this is a finding.

Fix: F-42966r663698_fix

At the command prompt, enter the following command: # chmod 600 <file> Note: Replace <file> with the file with incorrect permissions.

The vROps PostgreSQL DB must be able to generate audit records when privileges/permissions are retrieved.

AU-12 - Medium - CCI-000172 - V-239775 - SV-239775r879561_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000035

Vuln IDs

V-239775
V-88221

Rule IDs

SV-239775r879561_rule
SV-98871

Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically make such information available through views or functions. This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted.

Checks: C-43008r663700_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If log_statement is not set to "all", this is a finding.

Fix: F-42967r663701_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_statement TO 'all';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must initiate session auditing upon startup.

AU-14 - Medium - CCI-001464 - V-239776 - SV-239776r879562_rule

RMF Control

AU-14

Severity

CCI

CCI-001464

Version

VROM-PG-000045

Vuln IDs

V-239776
V-88223

Rule IDs

SV-239776r879562_rule
SV-98873

Session auditing is for use when a user's activities are under investigation. To be sure of capturing all activity during those periods when session auditing is in use, it needs to be in operation for the whole time the DBMS is running.

Checks: C-43009r663703_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If log_statement is not set to "all", this is a finding.

Fix: F-42968r663704_fix

The vROps PostgreSQL DB must produce audit records containing sufficient information to establish what type of events occurred.

AU-3 - Medium - CCI-000130 - V-239777 - SV-239777r879563_rule

RMF Control

AU-3

Severity

CCI

CCI-000130

Version

VROM-PG-000055

Vuln IDs

V-239777
V-88227

Rule IDs

SV-239777r879563_rule
SV-98877

Information system auditing capability is critical for accurate forensic analysis. Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit record content that may be necessary to satisfy the requirement of this policy includes, for example, time stamps, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application. Database software is capable of a range of actions on data stored within the database. It is important, for accurate forensic analysis, to know exactly what actions were performed. This requires specific information regarding the event type an audit record is referring to. If event type information is not recorded and stored with the audit record, the record itself is of very limited use.

Checks: C-43010r663706_chk

Fix: F-42969r663707_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_line_prefix TO '%m %d %u %r %p %l %c';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must produce audit records containing time stamps to establish when the events occurred.

AU-3 - Medium - CCI-000131 - V-239778 - SV-239778r879564_rule

RMF Control

AU-3

Severity

CCI

CCI-000131

Version

VROM-PG-000060

Vuln IDs

V-239778
V-88229

Rule IDs

SV-239778r879564_rule
SV-98879

Information system auditing capability is critical for accurate forensic analysis. Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know the date and time when events occurred. Associating the date and time with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application. Database software is capable of a range of actions on data stored within the database. It is important, for accurate forensic analysis, to know exactly when specific actions were performed. This requires the date and time an audit record is referring to. If date and time information is not recorded and stored with the audit record, the record itself is of very limited use.

Checks: C-43011r663709_chk

Fix: F-42970r663710_fix

The vROps PostgreSQL DB must produce audit records containing sufficient information to establish where the events occurred.

AU-3 - Medium - CCI-000132 - V-239779 - SV-239779r879565_rule

RMF Control

AU-3

Severity

CCI

CCI-000132

Version

VROM-PG-000065

Vuln IDs

V-239779
V-88231

Rule IDs

SV-239779r879565_rule
SV-98881

Information system auditing capability is critical for accurate forensic analysis. Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

Checks: C-43012r663712_chk

Fix: F-42971r663713_fix

The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the sources (origins) of the events.

AU-3 - Medium - CCI-000133 - V-239780 - SV-239780r879566_rule

RMF Control

AU-3

Severity

CCI

CCI-000133

Version

VROM-PG-000070

Vuln IDs

V-239780
V-88233

Rule IDs

SV-239780r879566_rule
SV-98883

Information system auditing capability is critical for accurate forensic analysis. Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. In addition to logging where events occur within the application, the application must also produce audit records that identify the application itself as the source of the event. Associating information about the source of the event within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

Checks: C-43013r663715_chk

Fix: F-42972r663716_fix

The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.

AU-3 - Medium - CCI-000134 - V-239781 - SV-239781r879567_rule

RMF Control

AU-3

Severity

CCI

CCI-000134

Version

VROM-PG-000075

Vuln IDs

V-239781
V-88235

Rule IDs

SV-239781r879567_rule
SV-98885

Information system auditing capability is critical for accurate forensic analysis. Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.

Checks: C-43014r663718_chk

Fix: F-42973r663719_fix

The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.

AU-3 - Medium - CCI-001487 - V-239782 - SV-239782r879568_rule

RMF Control

AU-3

Severity

CCI

CCI-001487

Version

VROM-PG-000080

Vuln IDs

V-239782
V-88237

Rule IDs

SV-239782r879568_rule
SV-98887

Information system auditing capability is critical for accurate forensic analysis. Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. Identifiers (if authenticated or otherwise known) include, but are not limited to, user database tables, primary key values, user names, or process identifiers.

Checks: C-43015r663721_chk

Fix: F-42974r663722_fix

The vROps PostgreSQL DB must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.

AU-3 - Medium - CCI-000135 - V-239783 - SV-239783r879569_rule

RMF Control

AU-3

Severity

CCI

CCI-000135

Version

VROM-PG-000085

Vuln IDs

V-239783
V-88239

Rule IDs

SV-239783r879569_rule
SV-98889

Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. To support analysis, some types of events will need information to be logged that exceeds the basic requirements of event type, time stamps, location, source, outcome, and user identity. If additional information is not available, it could negatively impact forensic investigations into user actions or other malicious events. The organization must determine what additional information is required for complete analysis of the audited events. The additional information required is dependent on the type of information (e.g., sensitivity of the data and the environment within which it resides). At a minimum, the organization must employ either full-text recording of privileged commands or the individual identities of group users, or both. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Examples of detailed information the organization may require in audit records are full-text recording of privileged commands or the individual identities of group account users.

Checks: C-43016r663724_chk

Fix: F-42975r663725_fix

The vROps PostgreSQL DB must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records.

AU-5 - Low - CCI-000140 - V-239784 - SV-239784r879571_rule

RMF Control

AU-5

Severity

CCI

CCI-000140

Version

VROM-PG-000095

Vuln IDs

V-239784
V-88241

Rule IDs

SV-239784r879571_rule
SV-98891

It is critical that when the DBMS is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. When availability is an overriding concern, approved actions in response to an audit failure are as follows: (i) If the failure was caused by the lack of audit record storage capacity, the DBMS must continue generating audit records, if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner. (ii) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the DBMS must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server. Systems where availability is paramount will most likely be MAC I; the final determination is the prerogative of the application owner, subject to Authorizing Official concurrence. In any case, sufficient auditing resources must be allocated to avoid audit data loss in all but the most extreme situations.

Checks: C-43017r663727_chk

At the command prompt, execute the following command: # grep '^\s*log_truncate_on_rotation\b' /storage/db/vcops/vpostgres/data/postgresql.conf If log_truncate_on_rotation is not set to "on", this is a finding.

Fix: F-42976r663728_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_truncate_on_rotation TO on;" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized read access.

AU-9 - Medium - CCI-000162 - V-239785 - SV-239785r879576_rule

RMF Control

AU-9

Severity

CCI

CCI-000162

Version

VROM-PG-000105

Vuln IDs

V-239785
V-88243

Rule IDs

SV-239785r879576_rule
SV-98893

If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In addition, access to audit records provides information an attacker could potentially use to his or her advantage. To ensure the veracity of audit data, the information system and/or the application must protect audit information from any and all unauthorized access. This includes read, write, copy, etc. This requirement can be achieved through multiple methods which will depend upon system architecture and design. Some commonly employed methods include ensuring log files enjoy the proper file system permissions utilizing file system protections and limiting log data location. Additionally, applications with user interfaces to audit records should not allow for the unfettered manipulation of or access to those records via the application. If the application provides access to the audit data, the application becomes accountable for ensuring that audit information is protected from unauthorized access. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.

Checks: C-43018r663730_chk

At the command prompt, enter the following command: # ls -l /storage/db/vcops/vpostgres/data/pg_log/*.log If the permissions on any log files are not "600", this is a finding.

Fix: F-42977r663731_fix

At the command prompt, enter the following command: # chmod 600 /storage/db/vcops/vpostgres/data/pg_log/<file_name> Replace <file_name> with files to be modified. At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_file_mode TO '0600';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized modification.

AU-9 - Medium - CCI-000163 - V-239786 - SV-239786r879577_rule

RMF Control

AU-9

Severity

CCI

CCI-000163

Version

VROM-PG-000110

Vuln IDs

V-239786
V-88245

Rule IDs

SV-239786r879577_rule
SV-98895

If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data the information system and/or the application must protect audit information from unauthorized modification. This requirement can be achieved through multiple methods that will depend upon system architecture and design. Some commonly employed methods include ensuring log files enjoy the proper file system permissions and limiting log data locations. Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights that the user enjoys in order to make access decisions regarding the modification of audit data. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. Modification of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.

Checks: C-43019r663733_chk

At the command prompt, enter the following command: # ls -l /storage/db/vcops/vpostgres/data/pg_log/*.log If the owner of any log files is not "postgres:users", this is a finding.

Fix: F-42978r663734_fix

At the command prompt, enter the following command: # chown postgres:users /storage/db/vcops/vpostgres/data/pg_log/<file_name> Replace <file_name> with files to be modified.

The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized deletion.

AU-9 - Medium - CCI-000164 - V-239787 - SV-239787r879578_rule

RMF Control

AU-9

Severity

CCI

CCI-000164

Version

VROM-PG-000115

Vuln IDs

V-239787
V-88247

Rule IDs

SV-239787r879578_rule
SV-98897

If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods which will depend upon system architecture and design. Some commonly employed methods include: ensuring log files enjoy the proper file system permissions utilizing file system protections; restricting access; and backing up log data to ensure log data is retained. Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit data. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. Deletion of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.

Checks: C-43020r663736_chk

At the command prompt, enter the following command: # ls -l /storage/db/vcops/vpostgres/data/pg_log/*.log If the group-owner of any log files is not "postgres:users", this is a finding.

Fix: F-42979r663737_fix

At the command prompt, enter the following command: # chown postgres:users /storage/db/vcops/vpostgres/data/pg_log/<file_name> Replace <file_name> with files to be modified.

The vROps PostgreSQL DB must protect its audit features from unauthorized access.

AU-9 - Medium - CCI-001493 - V-239788 - SV-239788r879579_rule

RMF Control

AU-9

Severity

CCI

CCI-001493

Version

VROM-PG-000120

Vuln IDs

V-239788
V-88249

Rule IDs

SV-239788r879579_rule
SV-98899

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, OS-provided audit tools, vendor-provided audit tools, and open source audit tools needed to successfully view and manipulate audit information system activity and records. If an attacker were to gain access to audit tools, he could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.

Checks: C-43021r663739_chk

At the command prompt, enter the following command: # ls -l /storage/db/vcops/vpostgres/data/*conf* /var/vmware/vpostgres/9.3/.pgpass If the permissions on any of the listed files are not "600", this is a finding.

Fix: F-42980r663740_fix

At the command prompt, enter the following command: # chmod 600 <file> Note: Replace <file> with the file with incorrect permissions.

The vROps PostgreSQL DB must protect its audit configuration from unauthorized modification.

AU-9 - Medium - CCI-001494 - V-239789 - SV-239789r879580_rule

RMF Control

AU-9

Severity

CCI

CCI-001494

Version

VROM-PG-000125

Vuln IDs

V-239789
V-88251

Rule IDs

SV-239789r879580_rule
SV-98901

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the modification of audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Checks: C-43022r663742_chk

At the command prompt, enter the following command: # ls -l /storage/db/vcops/vpostgres/data/*conf* /var/vmware/vpostgres/9.3/.pgpass If the owner of any configuration file is not "postgres:users", this is a finding.

Fix: F-42981r663743_fix

At the command prompt, enter the following command: # chown postgres:users <file_name> Replace <file_name> with files to be modified.

The vROps PostgreSQL DB must protect its audit features from unauthorized removal.

AU-9 - Medium - CCI-001495 - V-239790 - SV-239790r879581_rule

RMF Control

AU-9

Severity

CCI

CCI-001495

Version

VROM-PG-000130

Vuln IDs

V-239790
V-88253

Rule IDs

SV-239790r879581_rule
SV-98903

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Checks: C-43023r663745_chk

At the command prompt, enter the following command: # ls -l /storage/db/vcops/vpostgres/data/*conf* /var/vmware/vpostgres/9.3/.pgpass If the group-owner of any configuration file is not "postgres:users", this is a finding.

Fix: F-42982r663746_fix

At the command prompt, enter the following command: # chown postgres:users <file_name> Replace <file_name> with files to be modified.

vROps PostgreSQL DB objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by vROps PostgreSQL DB principals authorized for ownership.

CM-5 - Medium - CCI-001499 - V-239791 - SV-239791r879586_rule

RMF Control

CM-5

Severity

CCI

CCI-001499

Version

VROM-PG-000150

Vuln IDs

V-239791
V-88255

Rule IDs

SV-239791r879586_rule
SV-98905

Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and procedures can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions if they were the owner. If not properly managed, this can lead to privileged actions being taken by unauthorized individuals. Conversely, if critical tables or other objects rely on unauthorized owner accounts, these objects may be lost when an account is removed.

Checks: C-43024r663748_chk

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "\dp;" Review the Access Privileges column. If any tables have permissions to users other than "postgres", this is a finding.

Fix: F-42983r663749_fix

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER TABLE <tablename> OWNER TO postgres;" Replace <tablename> with the name of the table discovered during the check.

The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the vROps PostgreSQL DB, etc.) must be restricted to authorized users.

CM-5 - Medium - CCI-001499 - V-239792 - SV-239792r663895_rule

RMF Control

CM-5

Severity

CCI

CCI-001499

Version

VROM-PG-000155

Vuln IDs

V-239792
V-88257

Rule IDs

SV-239792r663895_rule
SV-98907

If the DBMS were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. Unmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.

Checks: C-43025r663751_chk

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "\du;" If the accounts other than "postgres" and "vc" have create privileges, this is a finding.

Fix: F-42984r663752_fix

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "REVOKE ALL PRIVILEGES FROM <user>;" Replace <user> with the account discovered during the check.

Default demonstration and sample databases, database objects, and applications must be removed.

CM-7 - Medium - CCI-000381 - V-239793 - SV-239793r879587_rule

RMF Control

CM-7

Severity

CCI

CCI-000381

Version

VROM-PG-000160

Vuln IDs

V-239793
V-88259

Rule IDs

SV-239793r879587_rule
SV-98909

Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. Examples include, but are not limited to, installing advertising software, demonstrations, or browser plugins not related to requirements or providing a wide array of functionality, not required for every mission, that cannot be disabled. DBMSs must adhere to the principles of least functionality by providing only essential capabilities. Demonstration and sample database objects and applications present publicly known attack points for malicious users. These demonstration and sample objects are meant to provide simple examples of coding specific functions and are not developed to prevent vulnerabilities from being introduced to the DBMS and host system.

Checks: C-43026r663896_chk

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT datname FROM pg_database WHERE datistemplate = false;" If the output is not the following lines, this is a finding: datname ---------- postgres VCDB (2 rows)

Fix: F-42985r663755_fix

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "DROP DATABASE IF EXISTS <name>;"

The vROps PostgreSQL DB must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

CM-7 - Medium - CCI-000382 - V-239794 - SV-239794r879588_rule

RMF Control

CM-7

Severity

CCI

CCI-000382

Version

VROM-PG-000180

Vuln IDs

V-239794
V-88261

Rule IDs

SV-239794r879588_rule
SV-98911

In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols/services on information systems. Applications are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the application must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. Database Management Systems using ports, protocols, and services deemed unsafe are open to attack through those ports, protocols, and services. This can allow unauthorized access to the database and through the database to other components of the information system.

Checks: C-43027r663898_chk

At the command prompt, execute the following command: # grep '^\s*port\b' /storage/db/vcops/vpostgres/data/postgresql.conf If the port is set to "5432", this is NOT a finding. If the port is not set to "5432" and if the ISSO does not have documentation of an approved variance for using a non-standard port, this is a finding.

Fix: F-42986r663758_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET port TO '5432';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

IA-2 - Medium - CCI-000764 - V-239795 - SV-239795r879589_rule

RMF Control

IA-2

Severity

CCI

CCI-000764

Version

VROM-PG-000185

Vuln IDs

V-239795
V-88263

Rule IDs

SV-239795r879589_rule
SV-98913

To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses, except the following: (i) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and (ii) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.

Checks: C-43028r663760_chk

At the command prompt, execute the following command to enter the psql prompt: # cat /storage/db/vcops/vpostgres/data/pg_hba.conf If any rows have "trust" specified for the "METHOD" column, this is a finding.

Fix: F-42987r663761_fix

Navigate to and open /storage/db/vcops/vpostgres/data/pg_hba.conf. Navigate to the user that has a method of "trust". Change the method to md5. A correct, typical line will look like the below: # TYPE DATABASE USER ADDRESS METHOD host all all 127.0.0.1/32 md5

If passwords are used for authentication, the vROps PostgreSQL DB must store only hashed, salted representations of passwords.

IA-5 - Medium - CCI-000196 - V-239796 - SV-239796r879608_rule

RMF Control

IA-5

Severity

CCI

CCI-000196

Version

VROM-PG-000190

Vuln IDs

V-239796
V-88265

Rule IDs

SV-239796r879608_rule
SV-98915

The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. In such cases, database passwords stored in clear text, using reversible encryption, or using unsalted hashes would be vulnerable to unauthorized disclosure. Database passwords must always be in the form of one-way, salted hashes when stored internally or externally to the DBMS.

Checks: C-43029r663763_chk

Fix: F-42988r663764_fix

If passwords are used for authentication, the vROps PostgreSQL DB must transmit only encrypted representations of passwords.

IA-5 - Medium - CCI-000197 - V-239797 - SV-239797r879609_rule

RMF Control

IA-5

Severity

CCI

CCI-000197

Version

VROM-PG-000195

Vuln IDs

V-239797
V-88267

Rule IDs

SV-239797r879609_rule
SV-98917

The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. In such cases, passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission. DBMS passwords sent in clear text format across the network are vulnerable to discovery by unauthorized users. Disclosure of passwords may easily lead to unauthorized access to the database.

Checks: C-43030r663766_chk

At the command prompt, execute the following command: # grep '^\s*ssl\b' /storage/db/vcops/vpostgres/data/postgresql.conf If ssl is not set to "on", this is a finding.

Fix: F-42989r663767_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET ssl TO 'on';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.

IA-7 - High - CCI-000803 - V-239798 - SV-239798r879616_rule

RMF Control

IA-7

Severity

CCI

CCI-000803

Version

VROM-PG-000220

Vuln IDs

V-239798
V-88269

Rule IDs

SV-239798r879616_rule
SV-98919

Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak algorithms can be easily broken and not validated cryptographic modules may not implement algorithms correctly. Unapproved cryptographic modules or algorithms should not be relied on for authentication, confidentiality, or integrity. Weak cryptography could allow an attacker to gain access to and modify data stored in the database as well as the administration settings of the DBMS. Applications, including DBMSs, utilizing cryptography are required to use approved NIST FIPS 140-2 validated cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The security functions validated as part of FIPS 140-2 for cryptographic modules are described in FIPS 140-2 Annex A. NSA Type-X (where X=1, 2, 3, 4) products are NSA-certified, hardware-based encryption modules.

Checks: C-43031r663769_chk

At the command prompt, execute the following command: # grep '^\s*ssl_ciphers\b' /storage/db/vcops/vpostgres/data/postgresql.conf If ssl_ciphers is not set to "FIPS: +3DES:!aNULL", this is a finding.

Fix: F-42990r663770_fix

At the command prompt, execute the following commands: # sed -i.bak "/ssl_ciphers\s.*/ d" /storage/db/vcops/vpostgres/data/postgresql.conf # sed -i "$ a ssl_ciphers = 'FIPS: +3DES:\!aNULL'" /storage/db/vcops/vpostgres/data/postgresql.conf # su postgres postgres@vRealizeClusterNode:> cd /opt/vmware/vpostgres/current postgres@vRealizeClusterNode:> /opt/vmware/vpostgres/9.3/bin/pg_ctl restart -D /storage/db/vcops/vpostgres/data postgres@vRealizeClusterNode:> exit

In the event of a system failure, the vROps PostgreSQL DB must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.

SC-24 - Medium - CCI-001665 - V-239799 - SV-239799r879641_rule

RMF Control

SC-24

Severity

CCI

CCI-001665

Version

VROM-PG-000255

Vuln IDs

V-239799
V-88271

Rule IDs

SV-239799r879641_rule
SV-98921

Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving information system state information helps to facilitate system restart and return to the operational mode of the organization with less disruption of mission/business processes. Since it is usually not possible to test this capability in a production environment, systems should either be validated in a testing environment or prior to installation. This requirement is usually a function of the design of the IDPS component. Compliance can be verified by acceptance/validation processes or vendor attestation.

Checks: C-43032r663900_chk

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT name, setting FROM pg_settings WHERE name IN ('fsync','full_page_writes','synchronous_commit');" If "fsync", "full_page_writes", and "synchronous_commit" are not set to "on", this is a finding. The command should return the below lines: name | setting ---------------------------+--------- fsync | on full_page_writes | on synchronous_commit | on (3 rows)

Fix: F-42991r663773_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET <name> TO 'on';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();" Note: Substitute <name> with the incorrectly set parameter.

The vROps PostgreSQL DB must isolate security functions from non-security functions.

SC-3 - Medium - CCI-001084 - V-239800 - SV-239800r879643_rule

RMF Control

SC-3

Severity

CCI

CCI-001084

Version

VROM-PG-000265

Vuln IDs

V-239800
V-88273

Rule IDs

SV-239800r879643_rule
SV-98923

An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Database Management Systems typically separate security functionality from non-security functionality via separate databases or schemas. Database objects or code implementing security functionality should not be commingled with objects or code implementing application logic. When security and non-security functionality are commingled, users who have access to non-security functionality may be able to access security functionality.

Checks: C-43033r663902_chk

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "\dp.*.;" Review the Access Privilege column for all Schemas listed as information_schema and pg_catalog. If access privilege is granted to any users other than "postgres", this is a finding.

Fix: F-42992r663776_fix

At the command prompt, execute the following command: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "REVOKE ALL PRIVILEGES ON <name> FROM <user>;" Replace <name> and <user> with the Access Privilege name and account, respectively, discovered during the check.

vROps PostgreSQL DB contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.

SC-4 - Medium - CCI-001090 - V-239801 - SV-239801r879649_rule

RMF Control

SC-4

Severity

CCI

CCI-001090

Version

VROM-PG-000270

Vuln IDs

V-239801
V-88275

Rule IDs

SV-239801r879649_rule
SV-98925

Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. Data used for the development and testing of applications often involves copying data from production. It is important that specific procedures exist for this process, to include the conditions under which such transfer may take place, where the copies may reside, and the rules for ensuring sensitive data are not exposed. Copies of sensitive data must not be misplaced or left in a temporary location without the proper controls.

Checks: C-43034r663904_chk

Obtain the site data-transfer policy from the ISSO. Review the policies and procedures used to ensure that all vROps data is being protected from unauthorized and unintended information transformation in accordance with site policy. If the site data-transfer policy is not followed, this is a finding.

Fix: F-42993r663779_fix

Modify any code used for moving data from production to development/test systems to comply with the organization-defined site data-transfer policy, and to ensure copies of production data are not left in unsecured locations.

The vROps PostgreSQL DB must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.

SI-11 - Medium - CCI-001314 - V-239802 - SV-239802r879656_rule

RMF Control

SI-11

Severity

CCI

CCI-001314

Version

VROM-PG-000305

Vuln IDs

V-239802
V-88277

Rule IDs

SV-239802r879656_rule
SV-98927

If the DBMS provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. Some default DBMS error messages can contain information that could aid an attacker in, among others things, identifying the database type, host address, or state of the database. Custom errors may contain sensitive customer information. It is important that detailed error messages be visible only to those who are authorized to view them; that general users receive only generalized acknowledgment that errors have occurred; and that these generalized messages appear only when relevant to the user's task. For example, a message along the lines of, "An error has occurred. Unable to save your changes. If this problem persists, please contact your help desk" would be relevant. A message such as "Warning: your transaction generated a large number of page splits" would likely not be relevant. Administrative users authorized to review detailed error messages typically are the ISSO, ISSM, SA and DBA. Other individuals or roles may be specified according to organization-specific needs, with DBA approval.

Checks: C-43035r663781_chk

At the command prompt, execute the following command: # ls -l /storage/db/vcops/vpostgres/data/serverlog If the file permissions are more permissive than "640", this is a finding.

Fix: F-42994r663782_fix

At the command prompt, enter the following command: chmod 640 /storage/db/vcops/vpostgres/data/serverlog

The vROps PostgreSQL DB must utilize centralized management of the content captured in audit records generated by all components of the DBMS.

AU-3 - Medium - CCI-001844 - V-239803 - SV-239803r879729_rule

RMF Control

AU-3

Severity

CCI

CCI-001844

Version

VROM-PG-000355

Vuln IDs

V-239803
V-88279

Rule IDs

SV-239803r879729_rule
SV-98929

Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.

Checks: C-43036r663784_chk

At the command prompt, execute the following command: # grep '^\s*logging_collector\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "logging_collector" is not set to "on", this is a finding.

Fix: F-42995r663785_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET logging_collector TO 'on';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must provide centralized configuration of the content to be captured in audit records generated by all components of the DBMS.

AU-3 - Medium - CCI-001844 - V-239804 - SV-239804r879729_rule

RMF Control

AU-3

Severity

CCI

CCI-001844

Version

VROM-PG-000360

Vuln IDs

V-239804
V-88281

Rule IDs

SV-239804r879729_rule
SV-98931

If the configuration of the DBMS's auditing is spread across multiple locations in the database management software, or across multiple commands, only loosely related, it is harder to use and takes longer to reconfigure in response to events. The DBMS must provide a unified tool for audit configuration.

Checks: C-43037r663787_chk

At the command prompt, execute the following command: # grep '^\s*logging_collector\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "logging_collector" is not set to "on", this is a finding.

Fix: F-42996r663788_fix

The vROps PostgreSQL DB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.

AU-5 - Medium - CCI-001855 - V-239805 - SV-239805r879732_rule

RMF Control

AU-5

Severity

CCI

CCI-001855

Version

VROM-PG-000370

Vuln IDs

V-239805
V-88283

Rule IDs

SV-239805r879732_rule
SV-98933

Organizations are required to use a central log management system, so, under normal conditions, the audit space allocated to the DBMS on its own server will not be an issue. However, space will still be required on the DBMS server for audit records in transit, and, under abnormal conditions, this could fill up. Since a requirement exists to halt processing upon audit failure, a service outage would result. If support personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. The appropriate support staff include, at a minimum, the ISSO and the DBA/SA.

Checks: C-43038r663790_chk

At the command prompt, execute the following command: # grep '^\s*syslog_facility\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "syslog_facility" is not set to "local0", this is a finding.

Fix: F-42997r663791_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET syslog_facility TO 'local0';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts.

AU-8 - Medium - CCI-001888 - V-239806 - SV-239806r663795_rule

RMF Control

AU-8

Severity

CCI

CCI-001888

Version

VROM-PG-000375

Vuln IDs

V-239806
V-88285

Rule IDs

SV-239806r663795_rule
SV-98935

It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. The appropriate support staff include, at a minimum, the ISSO and the DBA/SA. Alerts provide organizations with urgent messages. Real-time alerts provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less).

Checks: C-43039r663793_chk

At the command prompt, execute the following command: # grep '^\s*syslog_facility\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "syslog_facility" is not set to "local0", this is a finding.

Fix: F-42998r663794_fix

The vROps PostgreSQL DB must record time stamps, in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT).

AU-8 - Medium - CCI-001890 - V-239807 - SV-239807r879747_rule

RMF Control

AU-8

Severity

CCI

CCI-001890

Version

VROM-PG-000380

Vuln IDs

V-239807
V-88287

Rule IDs

SV-239807r879747_rule
SV-98937

If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the DBMS must include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Some DBMS products offer a data type called TIMESTAMP that is not a representation of date and time. Rather, it is a database state counter and does not correspond to calendar and clock time. This requirement does not refer to that meaning of TIMESTAMP.

Checks: C-43040r663796_chk

At the command prompt, execute the following command: # grep '^\s*log_timezone\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_timezone" is not set to "UTC", this is a finding.

Fix: F-42999r663797_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_timezone TO 'UTC';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must generate time stamps, for audit records and application data, with a minimum granularity of one second.

AU-8 - Medium - CCI-001889 - V-239808 - SV-239808r879748_rule

RMF Control

AU-8

Severity

CCI

CCI-001889

Version

VROM-PG-000385

Vuln IDs

V-239808
V-88289

Rule IDs

SV-239808r879748_rule
SV-98939

Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the DBMS must include date and time. Granularity of time measurements refers to the precision available in time stamp values. Granularity coarser than one second is not sufficient for audit trail purposes. Time stamp values are typically presented with three or more decimal places of seconds; however, the actual granularity may be coarser than the apparent precision. For example, SQL Server's GETDATE()/CURRENT_TMESTAMP values are presented to three decimal places, but the granularity is not one millisecond: it is about 1/300 of a second. Some DBMS products offer a data type called TIMESTAMP that is not a representation of date and time. Rather, it is a database state counter and does not correspond to calendar and clock time. This requirement does not refer to that meaning of TIMESTAMP.

Checks: C-43041r663799_chk

At the command prompt, execute the following command: # grep '^\s*log_line_prefix\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_line_prefix" is not set to "%m %d %u %r %p %l %c", this is a finding.

Fix: F-43000r663800_fix

The vROps PostgreSQL DB must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).

CM-5 - Medium - CCI-001813 - V-239809 - SV-239809r879753_rule

RMF Control

CM-5

Severity

CCI

CCI-001813

Version

VROM-PG-000395

Vuln IDs

V-239809
V-88291

Rule IDs

SV-239809r879753_rule
SV-98941

Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the information system can potentially have significant effects on the overall security of the system. Accordingly, only qualified and authorized individuals should be allowed to obtain access to system components for the purposes of initiating changes, including upgrades and modifications.

Checks: C-43042r663802_chk

Fix: F-43001r663803_fix

At the command prompt, enter the following command: # chmod 600 <file> Note: Replace <file> with the file with incorrect permissions.

The vROps PostgreSQL DB must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.

CM-7 - Medium - CCI-001762 - V-239810 - SV-239810r879756_rule

RMF Control

CM-7

Severity

CCI

CCI-001762

Version

VROM-PG-000405

Vuln IDs

V-239810
V-88293

Rule IDs

SV-239810r879756_rule
SV-98943

Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.

Checks: C-43043r855648_chk

Fix: F-43002r663806_fix

When invalid inputs are received, the vROps PostgreSQL DB must behave in a predictable and documented manner that reflects organizational and system objectives.

SI-10 - Medium - CCI-002754 - V-239811 - SV-239811r879818_rule

RMF Control

SI-10

Severity

CCI

CCI-002754

Version

VROM-PG-000455

Vuln IDs

V-239811
V-88295

Rule IDs

SV-239811r879818_rule
SV-98945

A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state. The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.

Checks: C-43044r663808_chk

At the command prompt, execute the following command: # grep '^\s*client_encoding\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "client_encoding" is not set to "UTF8", this is a finding.

Fix: F-43003r663809_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET client_encoding TO 'UTF8';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

Security-relevant software updates to the vROps PostgreSQL DB must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).

SI-2 - High - CCI-002605 - V-239812 - SV-239812r879827_rule

RMF Control

SI-2

Severity

CCI

CCI-002605

Version

VROM-PG-000465

Vuln IDs

V-239812
V-88297

Rule IDs

SV-239812r879827_rule
SV-98947

Security flaws with software applications, including database management systems, 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).

Checks: C-43045r855651_chk

Obtain supporting documentation from the ISSO. Review the policies and procedures used to ensure that all security-related upgrades are being installed within the configured time period directed by an authoritative source. If all security-related upgrades are not being installed within the configured time period directed by an authoritative source, this is a finding.

Fix: F-43004r663812_fix

Verify that patches and updates from an authoritative source are applied at least within 24 hours after they have been received and has been documented in the supporting documentation.

The vROps PostgreSQL DB must be able to generate audit records when security objects are accessed.

AU-12 - Medium - CCI-000172 - V-239813 - SV-239813r879863_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000470

Vuln IDs

V-239813
V-88299

Rule IDs

SV-239813r879863_rule
SV-98949

Changes to the security configuration must be tracked. This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE

Checks: C-43046r663814_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43005r663815_fix

The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to access security objects occur.

AU-12 - Medium - CCI-000172 - V-239814 - SV-239814r879863_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000475

Vuln IDs

V-239814
V-88301

Rule IDs

SV-239814r879863_rule
SV-98951

Checks: C-43047r663817_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43006r663818_fix

The vROps PostgreSQL DB must generate audit records when privileges/permissions are added.

AU-12 - Medium - CCI-000172 - V-239815 - SV-239815r879866_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000490

Vuln IDs

V-239815
V-88303

Rule IDs

SV-239815r879866_rule
SV-98953

Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of individuals' and groups' privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command.

Checks: C-43048r663820_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43007r663821_fix

The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to add privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-239816 - SV-239816r879866_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000495

Vuln IDs

V-239816
V-88305

Rule IDs

SV-239816r879866_rule
SV-98955

Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict individuals' and groups' privileges could go undetected. In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-43049r663823_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43008r663824_fix

The vROps PostgreSQL DB must generate audit records when privileges/permissions are modified.

AU-12 - Medium - CCI-000172 - V-239817 - SV-239817r879866_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000500

Vuln IDs

V-239817
V-88307

Rule IDs

SV-239817r879866_rule
SV-98957

Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of individuals' and groups' privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, modifying permissions is typically done via the GRANT, REVOKE, and DENY commands.

Checks: C-43050r663826_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43009r663827_fix

The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-239818 - SV-239818r879866_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000505

Vuln IDs

V-239818
V-88309

Rule IDs

SV-239818r879866_rule
SV-98959

Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict individuals' and groups' privileges could go undetected. In PostgreSQL environment, modifying permissions is typically done via the GRANT and REVOKE commands. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-43051r663829_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43010r663830_fix

The vROps PostgreSQL DB must generate audit records when security objects are modified.

AU-12 - Medium - CCI-000172 - V-239819 - SV-239819r879867_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000510

Vuln IDs

V-239819
V-88311

Rule IDs

SV-239819r879867_rule
SV-98961

Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative.

Checks: C-43052r663832_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43011r663833_fix

The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify security objects occur.

AU-12 - Medium - CCI-000172 - V-239820 - SV-239820r879867_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000515

Vuln IDs

V-239820
V-88313

Rule IDs

SV-239820r879867_rule
SV-98963

Checks: C-43053r663835_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43012r663836_fix

The vROps PostgreSQL DB must generate audit records when privileges/permissions are deleted.

AU-12 - Medium - CCI-000172 - V-239821 - SV-239821r879870_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000530

Vuln IDs

V-239821
V-88315

Rule IDs

SV-239821r879870_rule
SV-98965

Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of individuals' and groups' privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, deleting permissions is typically done via the REVOKE or DENY command.

Checks: C-43054r663838_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43013r663839_fix

The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-239822 - SV-239822r879870_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000535

Vuln IDs

V-239822
V-88317

Rule IDs

SV-239822r879870_rule
SV-98967

Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict individuals' and groups' privileges could go undetected. In an SQL environment, deleting permissions is typically done via the REVOKE or DENY command. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-43055r663841_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43014r663842_fix

The vROps PostgreSQL DB must generate audit records when security objects are deleted.

AU-12 - Medium - CCI-000172 - V-239823 - SV-239823r879872_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000540

Vuln IDs

V-239823
V-88319

Rule IDs

SV-239823r879872_rule
SV-98969

The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.

Checks: C-43056r663844_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43015r663845_fix

The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete security objects occur.

AU-12 - Medium - CCI-000172 - V-239824 - SV-239824r879872_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000545

Vuln IDs

V-239824
V-88321

Rule IDs

SV-239824r879872_rule
SV-98971

The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-43057r663847_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43016r663848_fix

The vROps PostgreSQL DB must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.

AU-12 - Medium - CCI-000172 - V-239825 - SV-239825r879873_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000550

Vuln IDs

V-239825
V-88323

Rule IDs

SV-239825r879873_rule
SV-98973

Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.

Checks: C-43058r663850_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43017r663851_fix

The vROps PostgreSQL DB must generate audit records when successful logons or connections occur.

AU-12 - Medium - CCI-000172 - V-239826 - SV-239826r879874_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000560

Vuln IDs

V-239826
V-88325

Rule IDs

SV-239826r879874_rule
SV-98975

For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.

Checks: C-43059r663853_chk

At the command prompt, execute the following command: # grep '^\s*log_connections\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_connections" is not set to "on", this is a finding.

Fix: F-43018r663854_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_connections TO 'on';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must generate audit records when unsuccessful logons or connection attempts occur.

AU-12 - Medium - CCI-000172 - V-239827 - SV-239827r879874_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000565

Vuln IDs

V-239827
V-88327

Rule IDs

SV-239827r879874_rule
SV-98977

For completeness of forensic analysis, it is necessary to track failed attempts to log on to the DBMS. While positive identification may not be possible in a case of failed authentication, as much information as possible about the incident must be captured.

Checks: C-43060r663856_chk

At the command prompt, execute the following command: # grep '^\s*log_min_messages\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_min_messages" is not set to "warning", this is a finding.

Fix: F-43019r663857_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_min_messages TO 'warning';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must generate audit records for all privileged activities or other system-level access.

AU-12 - Medium - CCI-000172 - V-239828 - SV-239828r879875_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000570

Vuln IDs

V-239828
V-88329

Rule IDs

SV-239828r879875_rule
SV-98979

Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. System documentation should include a definition of the functionality considered privileged. A privileged function in this context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to: CREATE ALTER DROP GRANT REVOKE DENY There may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples in SQL include: TRUNCATE TABLE; DELETE, or DELETE affecting more than n rows, for some n, or DELETE without a WHERE clause; UPDATE or UPDATE affecting more than n rows, for some n, or UPDATE without a WHERE clause; any SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal. Depending on the capabilities of the DBMS and the design of the database and associated applications, audit logging may be achieved by means of DBMS auditing features, database triggers, other mechanisms, or a combination of these. Note that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement itself, since the objective is to have a complete audit trail of all administrative activity.

Checks: C-43061r663859_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43020r663860_fix

The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.

AU-12 - Medium - CCI-000172 - V-239829 - SV-239829r879875_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000575

Vuln IDs

V-239829
V-88331

Rule IDs

SV-239829r879875_rule
SV-98981

Checks: C-43062r663862_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43021r663863_fix

The vROps PostgreSQL DB must generate audit records showing starting and ending time for user access to the database(s).

AU-12 - Medium - CCI-000172 - V-239830 - SV-239830r879876_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000580

Vuln IDs

V-239830
V-88333

Rule IDs

SV-239830r879876_rule
SV-98983

For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to the DBMS lasts. This can be achieved by recording disconnections, in addition to logons/connections, in the audit logs. Disconnection may be initiated by the user or forced by the system (as in a timeout) or result from a system or network failure. To the greatest extent possible, all disconnections must be logged.

Checks: C-43063r663865_chk

At the command prompt, execute the following command: # grep '^\s*log_connections\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_connections" is not set to "on", this is a finding.

Fix: F-43022r663866_fix

The vROps PostgreSQL DB must generate audit records when concurrent logons/connections by the same user from different workstations occur.

AU-12 - Medium - CCI-000172 - V-239831 - SV-239831r879877_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000585

Vuln IDs

V-239831
V-88335

Rule IDs

SV-239831r879877_rule
SV-98985

For completeness of forensic analysis, it is necessary to track who logs on to the DBMS. Concurrent connections by the same user from multiple workstations may be valid use of the system; or such connections may be due to improper circumvention of the requirement to use the CAC for authentication; or they may indicate unauthorized account sharing; or they may be because an account has been compromised. (If the fact of multiple, concurrent logons by a given user can be reliably reconstructed from the log entries for other events (logons/connections; voluntary and involuntary disconnections), then it is not mandatory to create additional log entries specifically for this.)

Checks: C-43064r663868_chk

At the command prompt, execute the following command: # grep '^\s*log_connections\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_connections" is not set to "on", this is a finding.

Fix: F-43023r663869_fix

The vROps PostgreSQL DB must be able to generate audit records when successful accesses to objects occur.

AU-12 - Medium - CCI-000172 - V-239832 - SV-239832r879878_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000590

Vuln IDs

V-239832
V-88337

Rule IDs

SV-239832r879878_rule
SV-98987

Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE

Checks: C-43065r663871_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43024r663872_fix

The vROps PostgreSQL DB must generate audit records when unsuccessful accesses to objects occur.

AU-12 - Medium - CCI-000172 - V-239833 - SV-239833r879878_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000595

Vuln IDs

V-239833
V-88339

Rule IDs

SV-239833r879878_rule
SV-98989

Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-43066r663874_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43025r663875_fix

The vROps PostgreSQL DB must generate audit records for all direct access to the database(s).

AU-12 - Medium - CCI-000172 - V-239834 - SV-239834r879879_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

VROM-PG-000600

Vuln IDs

V-239834
V-88341

Rule IDs

SV-239834r879879_rule
SV-98991

In this context, direct access is any query, command, or call to the DBMS that comes from any source other than the application(s) that it supports. Examples would be the command line or a database management utility program. The intent is to capture all activity from administrative and non-standard sources.

Checks: C-43067r663877_chk

At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "log_statement" is not set to "all", this is a finding.

Fix: F-43026r663878_fix

The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures.

SC-13 - High - CCI-002450 - V-239835 - SV-239835r879885_rule

RMF Control

SC-13

Severity

CCI

CCI-002450

Version

VROM-PG-000605

Vuln IDs

V-239835
V-88343

Rule IDs

SV-239835r879885_rule
SV-98993

Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. For detailed information, refer to NIST FIPS Publication 140-2, Security Requirements for Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

Checks: C-43068r663880_chk

At the command prompt, execute the following command: # grep '^\s*ssl_ciphers\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "ssl_ciphers" is not set to "FIPS: +3DES:!aNULL", this is a finding.

Fix: F-43027r663881_fix

The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes.

SC-13 - High - CCI-002450 - V-239836 - SV-239836r879885_rule

RMF Control

SC-13

Severity

CCI

CCI-002450

Version

VROM-PG-000610

Vuln IDs

V-239836
V-88345

Rule IDs

SV-239836r879885_rule
SV-98995

Checks: C-43069r663883_chk

Fix: F-43028r663884_fix

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET ssl_ciphers TO 'FIPS: +3DES:!aNULL';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.

SC-13 - High - CCI-002450 - V-239837 - SV-239837r879885_rule

RMF Control

SC-13

Severity

CCI

CCI-002450

Version

VROM-PG-000615

Vuln IDs

V-239837
V-88347

Rule IDs

SV-239837r879885_rule
SV-98997

Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. It is the responsibility of the data owner to assess the cryptography requirements in light of applicable federal laws, Executive Orders, directives, policies, regulations, and standards. For detailed information, refer to NIST FIPS Publication 140-2, Security Requirements for Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

Checks: C-43070r663886_chk

Fix: F-43029r663887_fix

The vROps PostgreSQL DB must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.

AU-4 - Medium - CCI-001851 - V-239838 - SV-239838r879886_rule

RMF Control

AU-4

Severity

CCI

CCI-001851

Version

VROM-PG-000620

Vuln IDs

V-239838
V-88349

Rule IDs

SV-239838r879886_rule
SV-98999

Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.

Checks: C-43071r663889_chk

At the command prompt, execute the following command: # grep '^\s*syslog_facility\b' /storage/db/vcops/vpostgres/data/postgresql.conf If "syslog_facility" is not set to "local0", this is a finding.

Fix: F-43030r663890_fix

The vROps PostgreSQL DB must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs.

CM-6 - Medium - CCI-000366 - V-239839 - SV-239839r879887_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

VROM-PG-000625

Vuln IDs

V-239839
V-88351

Rule IDs

SV-239839r879887_rule
SV-99001

Configuring the DBMS to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. In addition to this SRG, sources of guidance on security and information assurance exist. These include NSA configuration guides, CTOs, DTMs, and IAVMs. The DBMS must be configured in compliance with guidance from all such relevant sources.

Checks: C-43072r663910_chk

Obtain supporting documentation from the ISSO. Verify that this Security Technical Implementation Guide (STIG) is the most current STIG available for PostgreSQL on vROps. Assess all of the organization's vROps installations to ensure that they are fully compliant with the most current PostgreSQL STIG. If the PostgreSQL configuration is not compliant with the most current PostgreSQL STIG, this is a finding.

Fix: F-43031r663893_fix

Install the latest approved security-relevant software updates and document in the supporting documentation.

The version of vRealize Operations Manager 6.x PostgreSQL running on the system must be a supported version.

SI-2 - High - CCI-002605 - V-258458 - SV-258458r928895_rule

RMF Control

SI-2

Severity

CCI

CCI-002605

Version

VROM-PG-009999

Vuln IDs

V-258458

Rule IDs

SV-258458r928895_rule

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 used to install patches across the enclave and 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 used 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).

Checks: C-62198r928894_chk

vRealize Operations Manager 6.x PostgreSQL is no longer supported by the vendor. If the system is running vRealize Operations Manager 6.x PostgreSQL, this is a finding.

Fix: F-53958r798705_fix

Upgrade to a supported version.

Added rules 69

Removed rules 69

Checks: C-43005r663691_chk

Fix: F-42964r663692_fix

Generate Mitigation Statement:

Checks: C-43006r663694_chk

Fix: F-42965r663695_fix

Generate Mitigation Statement:

Checks: C-43007r663697_chk

Fix: F-42966r663698_fix

Generate Mitigation Statement:

Checks: C-43008r663700_chk

Fix: F-42967r663701_fix

Generate Mitigation Statement:

Checks: C-43009r663703_chk

Fix: F-42968r663704_fix

Generate Mitigation Statement:

Checks: C-43010r663706_chk

Fix: F-42969r663707_fix

Generate Mitigation Statement:

Checks: C-43011r663709_chk

Fix: F-42970r663710_fix

Generate Mitigation Statement:

Checks: C-43012r663712_chk

Fix: F-42971r663713_fix

Generate Mitigation Statement:

Checks: C-43013r663715_chk

Fix: F-42972r663716_fix

Generate Mitigation Statement:

Checks: C-43014r663718_chk

Fix: F-42973r663719_fix

Generate Mitigation Statement:

Checks: C-43015r663721_chk

Fix: F-42974r663722_fix

Generate Mitigation Statement:

Checks: C-43016r663724_chk

Fix: F-42975r663725_fix

Generate Mitigation Statement:

Checks: C-43017r663727_chk

Fix: F-42976r663728_fix

Generate Mitigation Statement:

Checks: C-43018r663730_chk

Fix: F-42977r663731_fix

Generate Mitigation Statement:

Checks: C-43019r663733_chk

Fix: F-42978r663734_fix

Generate Mitigation Statement:

Checks: C-43020r663736_chk

Fix: F-42979r663737_fix

Generate Mitigation Statement:

Checks: C-43021r663739_chk

Fix: F-42980r663740_fix

Generate Mitigation Statement:

Checks: C-43022r663742_chk

Fix: F-42981r663743_fix

Generate Mitigation Statement:

Checks: C-43023r663745_chk

Fix: F-42982r663746_fix

Generate Mitigation Statement:

Checks: C-43024r663748_chk

Fix: F-42983r663749_fix

Generate Mitigation Statement:

Checks: C-43025r663751_chk

Fix: F-42984r663752_fix

Generate Mitigation Statement:

Checks: C-43026r663896_chk

Fix: F-42985r663755_fix

Generate Mitigation Statement:

Checks: C-43027r663898_chk

Fix: F-42986r663758_fix

Generate Mitigation Statement:

Checks: C-43028r663760_chk

Fix: F-42987r663761_fix

Generate Mitigation Statement:

Checks: C-43029r663763_chk

Fix: F-42988r663764_fix

Generate Mitigation Statement:

Checks: C-43030r663766_chk

Fix: F-42989r663767_fix

Generate Mitigation Statement: