EDB Postgres Advanced Server Security Technical Implementation Guide

Version

PPS9-00-001200

Vuln IDs

V-213567
V-68887

Rule IDs

SV-213567r508024_rule
SV-83491

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-14789r290013_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14787r290014_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-213568 - SV-213568r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-001300

Vuln IDs

V-213568
V-68889

Rule IDs

SV-213568r508024_rule
SV-83493

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. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-14790r290016_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14788r290017_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must initiate support of session auditing upon startup.

AU-14 - Medium - CCI-001464 - V-213569 - SV-213569r508024_rule

RMF Control

AU-14

Severity

M

CCI

CCI-001464

Version

PPS9-00-001400

Vuln IDs

V-213569
V-68891

Rule IDs

SV-213569r508024_rule
SV-83495

Session auditing is for use when a user's activities are under investigation. Typically, this DBMS capability would be used in conjunction with comparable monitoring of a user's online session, involving other software components such as operating systems, web servers and front-end user applications. The current requirement, however, deals specifically with the DBMS. To be sure of capturing all activity during those periods when session auditing is in use, database auditing needs to be in operation for the whole time the DBMS is running.

Checks: C-14791r290019_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14789r290020_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must produce audit records containing sufficient information to establish what type of events occurred.

AU-3 - Medium - CCI-000130 - V-213570 - SV-213570r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000130

Version

PPS9-00-001600

Vuln IDs

V-213570
V-68895

Rule IDs

SV-213570r508024_rule
SV-83499

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-14792r290022_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14790r290023_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must produce audit records containing time stamps to establish when the events occurred.

AU-3 - Medium - CCI-000131 - V-213571 - SV-213571r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000131

Version

PPS9-00-001700

Vuln IDs

V-213571
V-68897

Rule IDs

SV-213571r508024_rule
SV-83501

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-14793r290025_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14791r290026_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must produce audit records containing sufficient information to establish where the events occurred.

AU-3 - Medium - CCI-000132 - V-213572 - SV-213572r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000132

Version

PPS9-00-001800

Vuln IDs

V-213572
V-68899

Rule IDs

SV-213572r508024_rule
SV-83503

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-14794r290028_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14792r290029_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must produce audit records containing sufficient information to establish the sources (origins) of the events.

AU-3 - Medium - CCI-000133 - V-213573 - SV-213573r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000133

Version

PPS9-00-001900

Vuln IDs

V-213573
V-68901

Rule IDs

SV-213573r508024_rule
SV-83505

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-14795r290031_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14793r290032_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.

AU-3 - Medium - CCI-000134 - V-213574 - SV-213574r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000134

Version

PPS9-00-002000

Vuln IDs

V-213574
V-68903

Rule IDs

SV-213574r508024_rule
SV-83507

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-14796r290034_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14794r290035_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server 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-213575 - SV-213575r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-001487

Version

PPS9-00-002100

Vuln IDs

V-213575
V-68905

Rule IDs

SV-213575r508024_rule
SV-83509

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-14797r290037_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14795r290038_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server 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-213576 - SV-213576r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000135

Version

PPS9-00-002200

Vuln IDs

V-213576
V-68907

Rule IDs

SV-213576r508024_rule
SV-83511

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. In EnterpriseDB Postgres Plus Advanced Server, the edb_audit_tag can be used to record additional information. This tag can be set to different values by different sessions (connections), and can be set to new values any number of times. How to recognize the conditions for producing such audit data has to be determined and coded for as part of application and database design.

Checks: C-14798r290040_chk

Review the system documentation to identify what additional information the organization has determined necessary. Check application and database design, and existing audit records to verify that all organization-defined additional, more detailed information is in the audit records for audit events identified by type, location, or subject. If any additional information is defined and is not included in the audit records, this is a finding.

Fix: F-14796r290041_fix

Execute the following SQL to set additional detailed information for the audit records in the session: set edb_audit_tag = '<information>'; Replace <information> with a character string holding the additional data that must be captured. To set this in a trigger, an example is included below. Keep in mind that the edb_audit_tag is set for the life of the session, not just the life of the insert command: CREATE OR REPLACE FUNCTION add_audit_info() RETURNS trigger AS $BODY$ BEGIN SET edb_audit_tag = '<information>'; RETURN NEW; END; $BODY$ LANGUAGE plpgsql; CREATE TRIGGER add_audit_info_trigger BEFORE INSERT ON <table> FOR EACH ROW EXECUTE PROCEDURE add_audit_info();

b

The EDB Postgres Advanced Server must by default shut down upon audit failure, to include the unavailability of space for more audit log records; or must be configurable to shut down upon audit failure.

AU-5 - Medium - CCI-000140 - V-213577 - SV-213577r508024_rule

RMF Control

AU-5

Severity

M

CCI

CCI-000140

Version

PPS9-00-002300

Vuln IDs

V-213577
V-68909

Rule IDs

SV-213577r508024_rule
SV-83513

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 the need for system availability does not outweigh the need for a complete audit trail, the DBMS should shut down immediately, rolling back all in-flight transactions. Systems where audit trail completeness is paramount will most likely be at a lower MAC level than 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 a shutdown in all but the most extreme situations.

Checks: C-14799r290043_chk

If Postgres Enterprise Manager (PEM) is not installed and configured to shut down the database when the audit log is full, this is a finding.

Fix: F-14797r290044_fix

Install PEM and configure an alert to shut down the PPAS server when the audit log mount point is at 99 percent full. Refer to the Supplemental Procedures document, supplied with this STIG, for guidance on configuring alerts.

c

The EDB Postgres Advanced Server 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 - High - CCI-000140 - V-213578 - SV-213578r508024_rule

RMF Control

AU-5

Severity

H

CCI

CCI-000140

Version

PPS9-00-002400

Vuln IDs

V-213578
V-68911

Rule IDs

SV-213578r508024_rule
SV-83515

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-14800r290046_chk

If an externally managed and monitored partition or logical volume that can be grown dynamically is being used for logging, this is not a finding. If PPAS is auditing to a directory that is not being actively checked for availability of disk space, and if logrotate is not configured to rotate logs based on the size of the audit log directory with oldest logs being replaced by newest logs, this is a finding.

Fix: F-14798r290047_fix

Determine the max size of your audit log directory. For this fix, we will assume that the audit log directory has a max size of 100MB. Divide the max size of the directory by 10 to determine the size of your log files for rotation. Perform the following steps to ensure that the audit log directory is never more than 90% full and new logs always replace the oldest logs: 1) Add the following to the bottom of the /etc/logrotate.conf file: <postgresql data directory>/edb_audit/audit.csv { size 10M dateext dateformat .%Y-%m-%d.%s copytruncate rotate 8 } (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) 2) Create the file /etc/cron.hourly/logrotate with these contents: #!/bin/sh /usr/sbin/logrotate /etc/logrotate.conf EXITVALUE=$? if [ $EXITVALUE != 0 ]; then /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]" fi exit 0 3) Issue these SQL statements: ALTER SYSTEM SET edb_audit_filename = 'audit'; SELECT pg_reload_conf();

b

The audit information produced by the EDB Postgres Advanced Server must be protected from unauthorized read access.

AU-9 - Medium - CCI-000162 - V-213579 - SV-213579r508024_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000162

Version

PPS9-00-002600

Vuln IDs

V-213579
V-68913

Rule IDs

SV-213579r508024_rule
SV-83517

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-14801r290049_chk

Verify User ownership, Group ownership, and permissions on the “edb_audit” directory: > ls –ald <postgresql data directory>/edb_audit If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the directory is more permissive than 700, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14799r290050_fix

Run these commands: 1) "chown enterprisedb <postgresql data directory>/edb_audit" 2) "chgrp enterprisedb <postgresql data directory>/edb_audit" 3) "chmod 700 <postgresql data directory>/edb_audit" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

b

The audit information produced by the EDB Postgres Advanced Server must be protected from unauthorized modification.

AU-9 - Medium - CCI-000163 - V-213580 - SV-213580r508024_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000163

Version

PPS9-00-002700

Vuln IDs

V-213580
V-68915

Rule IDs

SV-213580r508024_rule
SV-83519

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-14802r290052_chk

Verify User ownership, Group ownership, and permissions on the “edb_audit” directory: > ls –ald <postgresql data directory>/edb_audit If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the directory is more permissive than 700, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14800r290053_fix

Run these commands: 1) "chown enterprisedb <postgresql data directory>/edb_audit" 2) "chgrp enterprisedb <postgresql data directory>/edb_audit" 3) "chmod 700 <postgresql data directory>/edb_audit" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

b

The audit information produced by the EDB Postgres Advanced Server must be protected from unauthorized deletion.

AU-9 - Medium - CCI-000164 - V-213581 - SV-213581r508024_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000164

Version

PPS9-00-002800

Vuln IDs

V-213581
V-68917

Rule IDs

SV-213581r508024_rule
SV-83521

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-14803r290055_chk

Verify User ownership, Group ownership, and permissions on the “edb_audit” directory: > ls –ald <postgresql data directory>/edb_audit If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the directory is more permissive than 700, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14801r290056_fix

Run these commands: 1) "chown enterprisedb <postgresql data directory>/edb_audit" 2) "chgrp enterprisedb <postgresql data directory>/edb_audit" 3) "chmod 700 <postgresql data directory>/edb_audit" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

b

The EDB Postgres Advanced Server must protect its audit features from unauthorized access.

AU-9 - Medium - CCI-001493 - V-213582 - SV-213582r508024_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001493

Version

PPS9-00-002900

Vuln IDs

V-213582
V-68919

Rule IDs

SV-213582r508024_rule
SV-83523

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-14804r290058_chk

Verify User ownership, Group ownership, and permissions on the “edb_audit” directory: > ls –ald <postgresql data directory>/edb_audit If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the directory is more permissive than 700, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14802r290059_fix

Run these commands: 1) "chown enterprisedb <postgresql data directory>/edb_audit" 2) "chgrp enterprisedb <postgresql data directory>/edb_audit" 3) "chmod 700 <postgresql data directory>/edb_audit" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

b

The EDB Postgres Advanced Server must protect its audit configuration from unauthorized modification.

AU-9 - Medium - CCI-001494 - V-213583 - SV-213583r508024_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001494

Version

PPS9-00-003000

Vuln IDs

V-213583
V-68921

Rule IDs

SV-213583r508024_rule
SV-83525

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-14805r290061_chk

Verify User ownership, Group ownership, and permissions on the “edb_audit” directory: > ls –ald <postgresql data directory>/edb_audit If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the directory is more permissive than 700, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14803r290062_fix

Run these commands: 1) "chown enterprisedb <postgresql data directory>/edb_audit" 2) "chgrp enterprisedb <postgresql data directory>/edb_audit" 3) "chmod 700 <postgresql data directory>/edb_audit" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

b

The EDB Postgres Advanced Server must protect its audit features from unauthorized removal.

AU-9 - Medium - CCI-001495 - V-213584 - SV-213584r508024_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001495

Version

PPS9-00-003100

Vuln IDs

V-213584
V-68923

Rule IDs

SV-213584r508024_rule
SV-83527

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-14806r290064_chk

Verify User ownership, Group ownership, and permissions on the “edb_audit” directory: > ls –ald <postgresql data directory>/edb_audit If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the directory is more permissive than 700, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14804r290065_fix

Run these commands: 1) "chown enterprisedb <postgresql data directory>/edb_audit" 2) "chgrp enterprisedb <postgresql data directory>/edb_audit" 3) "chmod 700 <postgresql data directory>/edb_audit" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

b

Software, applications, and configuration files that are part of, or related to, the Postgres Plus Advanced Server installation must be monitored to discover unauthorized changes.

CM-5 - Medium - CCI-001499 - V-213585 - SV-213585r508024_rule

RMF Control

CM-5

Severity

M

CCI

Version

PPS9-00-003200

Vuln IDs

V-213585
V-68925

Rule IDs

SV-213585r508024_rule
SV-83529

If the system were to allow any user to make changes to software libraries, 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. Monitoring is required for assurance that the protections are effective. Unmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.

Checks: C-14807r290067_chk

Review monitoring procedures and implementation evidence to verify monitoring of changes to database software libraries, related applications, and configuration files is done. Verify the list of files and directories being monitored is complete. If monitoring does not occur or is not complete, this is a finding.

Fix: F-14805r290068_fix

Implement procedures to monitor for unauthorized changes to DBMS software libraries, related software application libraries, and configuration files. If a third-party automated tool is not employed, an automated job that reports file information on the directories and files of interest and compares them to the baseline report for the same will meet the requirement. Use file hashes or checksums for comparisons, as file dates may be manipulated by malicious users.

b

EDB Postgres Advanced Server software modules, to include stored procedures, functions and triggers must be monitored to discover unauthorized changes.

CM-5 - Medium - CCI-001499 - V-213586 - SV-213586r508024_rule

RMF Control

CM-5

Severity

M

CCI

Version

PPS9-00-003210

Vuln IDs

V-213586
V-68927

Rule IDs

SV-213586r508024_rule
SV-83531

If the system were to allow any user to make changes to software libraries, 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. Monitoring is required for assurance that the protections are effective. Unmanaged changes that occur to the logic modules within the database can lead to unauthorized or compromised installations.

Checks: C-14808r290070_chk

Check the EDB Postgres configuration for a timed job that automatically checks all system and user-defined procedures, functions and triggers for being modified by running the following EDB Postgres query: select job, what from ALL_JOBS; (Alternatively, in Postgres Enterprise Manager, navigate to the "Jobs" node of the database and examine the job from there.) If a timed job or some other method is not implemented to check for Triggers being modified, this is a finding.

Fix: F-14806r290071_fix

Configure an EDB Postgres timed job that automatically checks all system and user-defined procedures, functions and triggers for being modified, and in the event of such changes informs the proper personnel for evaluation and possible action.

b

The EDB Postgres Advanced Server software installation account must be restricted to authorized users.

CM-5 - Medium - CCI-001499 - V-213587 - SV-213587r508024_rule

RMF Control

CM-5

Severity

M

CCI

Version

PPS9-00-003300

Vuln IDs

V-213587
V-68929

Rule IDs

SV-213587r508024_rule
SV-83533

When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can have significant effects on the overall security of the system. If the system were to allow any user to make changes to software libraries, 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 access to information system components for purposes of initiating changes, including upgrades and modifications. DBA and other privileged administrative or application owner accounts are granted privileges that allow actions that can have a great impact on database security and operation. It is especially important to grant privileged access to only those persons who are qualified and authorized to use them.

Checks: C-14809r290073_chk

Review procedures for controlling, granting access to, and tracking use of the DBMS software installation account. If access or use of this account is not restricted to the minimum number of personnel required or if unauthorized access to the account has been granted, this is a finding.

Fix: F-14807r290074_fix

Develop, document, and implement procedures to restrict and track use of the DBMS software installation account.

b

Database software, including EDB Postgres Advanced Server configuration files, must be stored in dedicated directories, separate from the host OS and other applications.

CM-5 - Medium - CCI-001499 - V-213588 - SV-213588r508024_rule

RMF Control

CM-5

Severity

M

CCI

Version

PPS9-00-003400

Vuln IDs

V-213588
V-68931

Rule IDs

SV-213588r508024_rule
SV-83535

When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system. Multiple applications can provide a cumulative negative effect. A vulnerability and subsequent exploit to one application can lead to an exploit of other applications sharing the same security context. For example, an exploit to a web server process that leads to unauthorized administrative access to host system directories can most likely lead to a compromise of all applications hosted by the same system. Database software not installed using dedicated directories both threatens and is threatened by other hosted applications. Access controls defined for one application may by default provide access to the other application's database objects or directories. Any method that provides any level of separation of security context assists in the protection between applications.

Checks: C-14810r290076_chk

Review the DBMS software library directory and note other root directories located on the same disk directory or any subdirectories. If any non-DBMS software directories exist on the disk directory, examine or investigate their use. If any of the directories are used by other applications, including third-party applications that use the DBMS, this is a finding. Only applications that are required for the functioning and administration, not use, of the DBMS should be located in the same disk directory as the DBMS software libraries. If other applications are located in the same directory as the DBMS, this is a finding.

Fix: F-14808r290077_fix

Install all applications on directories separate from the DBMS software library directory. Relocate any directories or reinstall other application software that currently shares the DBMS software library directory.

b

Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the EDB Postgres Advanced Server, etc.) must be owned by database/EDB Postgres Advanced Server principals authorized for ownership.

CM-5 - Medium - CCI-001499 - V-213589 - SV-213589r508024_rule

RMF Control

CM-5

Severity

M

CCI

Version

PPS9-00-003500

Vuln IDs

V-213589
V-68933

Rule IDs

SV-213589r508024_rule
SV-83537

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-14811r290079_chk

Review system documentation to identify accounts authorized to own database objects. Review accounts that own objects in the database(s) by running this SQL command: select * from sys.all_objects; If any database objects are found to be owned by users not authorized to own database objects, this is a finding.

Fix: F-14809r290080_fix

Assign ownership of authorized objects to authorized object owner accounts by running this SQL command for each object to be changed: ALTER <type> <object name> OWNER TO <new owner>; For example: ALTER TABLE my_table OWNER TO APP_USER;

b

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 EDB Postgres Advanced Server, etc.) must be restricted to authorized users.

CM-5 - Medium - CCI-001499 - V-213590 - SV-213590r508024_rule

RMF Control

CM-5

Severity

M

CCI

Version

PPS9-00-003600

Vuln IDs

V-213590
V-68935

Rule IDs

SV-213590r508024_rule
SV-83539

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-14812r290082_chk

Use psql to connect to the db as enterprisedb and run this command: \dp *.* If any unauthorized roles have unauthorized accesses, this is a finding. Definitions of the access privileges are defined here: http://www.postgresql.org/docs/current/static/sql-grant.html

Fix: F-14810r290083_fix

Revoke unauthorized privileges. The syntax is: REVOKE <privilege> ON <object> FROM <role>. Example: REVOKE INSERT ON a FROM PUBLIC; See PostgreSQL documentation for details.

b

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

CM-7 - Medium - CCI-000381 - V-213591 - SV-213591r508024_rule

RMF Control

CM-7

Severity

M

CCI

Version

PPS9-00-003700

Vuln IDs

V-213591
V-68937

Rule IDs

SV-213591r508024_rule
SV-83541

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-14813r290085_chk

Review vendor documentation and vendor websites for vendor-provided demonstration or sample databases, database applications, objects, and files. Review the DBMS to determine if any of the demonstration and sample databases, database applications, or files are installed in the database or are included with the DBMS application. If any are present in the database or are included with the DBMS application, this is a finding. Check for the existence of EDB Postgres sample databases: postgres and edb. Execute the following SQL as enterprisedb: SELECT datname FROM pg_database WHERE datistemplate = false; If any databases are listed here that are not used by the application, this is a finding.

Fix: F-14811r290086_fix

Remove any unused sample databases from the DBMS. To remove a database, execute the follow SQL: DROP DATABASE <database>;

b

Unused database components, EDB Postgres Advanced Server software, and database objects must be removed.

CM-7 - Medium - CCI-000381 - V-213592 - SV-213592r508024_rule

RMF Control

CM-7

Severity

M

CCI

Version

PPS9-00-003800

Vuln IDs

V-213592
V-68939

Rule IDs

SV-213592r508024_rule
SV-83543

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. DBMSs must adhere to the principles of least functionality by providing only essential capabilities.

Checks: C-14814r290088_chk

Review the list of components and features installed with the database. If unused components are installed and are not documented and authorized, this is a finding. RPM can also be used to check to see what is installed: yum list installed | grep ppas This returns EDB database packages that have been installed. If any packages displayed by this command are not being used, this is a finding.

Fix: F-14812r290089_fix

If any components are required for operation of applications that will be accessing the DBMS, include them in the system documentation. To uninstall and unused package (using ppas-odbc-devel-09.03.0400.02-1.rhel7.x86_64 as an example), execute the following command as root: yum erase -y ppas-odbc-devel-09.03.0400.02-1.rhel7.x86_64

b

Unused database components which are integrated in the EDB Postgres Advanced Server and cannot be uninstalled must be disabled.

CM-7 - Medium - CCI-000381 - V-213593 - SV-213593r508024_rule

RMF Control

CM-7

Severity

M

CCI

Version

PPS9-00-003900

Vuln IDs

V-213593
V-68941

Rule IDs

SV-213593r508024_rule
SV-83545

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. DBMSs must adhere to the principles of least functionality by providing only essential capabilities. Unused, unnecessary DBMS components increase the attack vector for the DBMS by introducing additional targets for attack. By minimizing the services and applications installed on the system, the number of potential vulnerabilities is reduced. Components of the system that are unused and cannot be uninstalled must be disabled. The techniques available for disabling components will vary by DBMS product, OS and the nature of the component and may include DBMS configuration settings, OS service settings, OS file access security, and DBMS user/group permissions.

Checks: C-14815r290091_chk

Run the following command as root: yum list installed | grep ppas If any packages are installed that are not needed, this is a finding.

Fix: F-14813r290092_fix

Review the EDB PPAS packages available in the installation guide here: http://www.enterprisedb.com/docs/en/9.5/instguide/Postgres_Plus_Advanced_Server_Installation_Guide.1.14.html# Uninstall any unneeded packages by running the following as root: yum erase -y <package-name> At a minimum, the ppas94-server-* packages are required, but other packages such as jdbc, postgis, pgpool and others may be required by applications that need the functionality provided in these additional packages

b

Access to external executables must be disabled or restricted.

CM-7 - Medium - CCI-000381 - V-213594 - SV-213594r508024_rule

RMF Control

CM-7

Severity

M

CCI

Version

PPS9-00-004000

Vuln IDs

V-213594
V-68943

Rule IDs

SV-213594r508024_rule
SV-83547

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 applications to provide, or install by default, functionality exceeding requirements or mission objectives. Applications must adhere to the principles of least functionality by providing only essential capabilities. DBMSs may spawn additional external processes to execute procedures that are defined in the DBMS but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than the DBMS and provide unauthorized access to the host system.

Checks: C-14816r290094_chk

Run the following command as root: yum list installed | grep ppas If any packages are installed that are not needed, this is a finding.

Fix: F-14814r290095_fix

Review the EDB PPAS packages available in the installation guide here: http://www.enterprisedb.com/docs/en/9.5/instguide/Postgres_Plus_Advanced_Server_Installation_Guide.1.14.html# Uninstall any unneeded packages by running the following as root: #> yum erase -y <package-name> At a minimum, the ppas94-server-* packages are required, but other packages such as jdbc, postgis, pgpool and others may be required by applications that need the functionality provided in these additional packages

b

The EDB Postgres Advanced Server 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-213595 - SV-213595r508024_rule

RMF Control

CM-7

Severity

M

CCI

CCI-000382

Version

PPS9-00-004100

Vuln IDs

V-213595
V-68945

Rule IDs

SV-213595r508024_rule
SV-83549

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-14817r290097_chk

Execute the following SQL as enterprisedb: SHOW port; SHOW listen_addresses; If the port or addresses are not approved, this is a finding.

Fix: F-14815r290098_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET port = <port>; ALTER SYSTEM SET listen_addresses = <comma separated addresses>; Execute the following operating system command as root: systemctl restart ppas-9.5.service

b

The EDB Postgres Advanced Server must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

IA-2 - Medium - CCI-000764 - V-213596 - SV-213596r508024_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000764

Version

PPS9-00-004200

Vuln IDs

V-213596
V-69091

Rule IDs

SV-213596r508024_rule
SV-83695

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-14818r290100_chk

Open "<postgresql data directory>/pg_hba.conf" in a viewer or editor. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) If any rows have "trust" specified for the "METHOD" column, this is a finding.

Fix: F-14816r290101_fix

Open "<postgresql data directory>/pg_hba.conf" in an editor. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) If any rows have "trust" specified for the "METHOD" column, delete the rows or change them to other authentication methods. Permitted methods in preferred order are: peer (local only), cert, ldap, sspi, pam, md5

b

If passwords are used for authentication, the EDB Postgres Advanced Server must store only hashed, salted representations of passwords.

IA-5 - Medium - CCI-000196 - V-213597 - SV-213597r508024_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000196

Version

PPS9-00-004300

Vuln IDs

V-213597
V-68947

Rule IDs

SV-213597r508024_rule
SV-83551

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-14819r290103_chk

Execute the following SQL as enterprisedb: SHOW password_encryption; If the value is not "on", this is a finding.

Fix: F-14817r290104_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET password_encryption = on; SELECT pg_reload_conf();

b

If passwords are used for authentication, the EDB Postgres Advanced Server must transmit only encrypted representations of passwords.

IA-5 - Medium - CCI-000197 - V-213598 - SV-213598r508024_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000197

Version

PPS9-00-004400

Vuln IDs

V-213598
V-68949

Rule IDs

SV-213598r508024_rule
SV-83553

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-14820r290106_chk

Open "<postgresql data directory>/pg_hba.conf" in a viewer or editor. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) If any rows have "password" specified for the "METHOD" column, this is a finding.

Fix: F-14818r290107_fix

Open "<postgresql data directory>/pg_hba.conf" in an editor. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) For any rows that have "password" specified for the "METHOD" column, change the value to "md5".

b

The EDB Postgres Advanced Server, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.

IA-5 - Medium - CCI-000185 - V-213599 - SV-213599r508024_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000185

Version

PPS9-00-004500

Vuln IDs

V-213599
V-68951

Rule IDs

SV-213599r508024_rule
SV-83555

The DoD standard for authentication is DoD-approved PKI certificates. A certificate’s certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate. Certification path validation includes checks such as certificate issuer trust, time validity and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses. Database Management Systems that do not validate certificates by performing RFC 5280-compliant certification path validation are in danger of accepting certificates that are invalid and/or counterfeit. This could allow unauthorized access to the database.

Checks: C-14821r290109_chk

Open "<postgresql data directory>/pg_hba.conf" in a viewer or editor. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) If any rows have TYPE of "hostssl" but do not include "clientcert=1" in the OPTIONS column at the end of the line, this is a finding.

Fix: F-14819r290110_fix

Open "<postgresql data directory>/pg_hba.conf" in an editor. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) For any rows that have TYPE of "hostssl", append "clientcert=1" in the OPTIONS column at the end of the line.

c

The EDB Postgres Advanced Server must enforce authorized access to all PKI private keys stored/utilized by the EDB Postgres Advanced Server.

IA-5 - High - CCI-000186 - V-213600 - SV-213600r508024_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000186

Version

PPS9-00-004600

Vuln IDs

V-213600
V-68953

Rule IDs

SV-213600r508024_rule
SV-83557

The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key. If the private key is stolen, an attacker can use the private key(s) to impersonate the certificate holder. In cases where the DBMS-stored private keys are used to authenticate the DBMS to the system’s clients, loss of the corresponding private keys would allow an attacker to successfully perform undetected man in the middle attacks against the DBMS system and its clients. Both the holder of a digital certificate and the issuing authority must take careful measures to protect the corresponding private key. Private keys should always be generated and protected in FIPS 140-2 validated cryptographic modules. All access to the private key(s) of the DBMS must be restricted to authorized and authenticated users. If unauthorized users have access to one or more of the DBMS's private keys, an attacker could gain access to the key(s) and use them to impersonate the database on the network or otherwise perform unauthorized actions.

Checks: C-14822r290112_chk

Verify User ownership, Group ownership, and permissions on the “server.key” file: > ls –alL <postgresql data directory>/server.key If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the file is more permissive than 600, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14820r290113_fix

Run these commands: 1) "chown enterprisedb <postgresql data directory>/server.key" 2) "chgrp enterprisedb <postgresql data directory>/server.key" 3) "chmod 600 <postgresql data directory>/server.key" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

c

Applications must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

IA-6 - High - CCI-000206 - V-213601 - SV-213601r508024_rule

RMF Control

IA-6

Severity

H

CCI

CCI-000206

Version

PPS9-00-004810

Vuln IDs

V-213601
V-68955

Rule IDs

SV-213601r508024_rule
SV-83559

To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. Obfuscation of user-provided information when typed into the system is a method used in addressing this risk. For example, displaying asterisks when a user types in a password or PIN, is an example of obscuring feedback of authentication information. Database applications may allow for entry of the account name and password as a visible parameter of the application execution command. This practice must be prohibited and disabled to prevent shoulder surfing. This calls for review of applications, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Checks: C-14823r290115_chk

Determine whether any applications that access the database allow for entry of the account name and password or PIN. If any do, determine whether these applications obfuscate authentication data. If they do not, this is a finding.

Fix: F-14821r290116_fix

Configure or modify applications to prohibit display of passwords in clear text.

c

When using command-line tools such as psql, users must use a logon method that does not expose the password.

IA-6 - High - CCI-000206 - V-213602 - SV-213602r508024_rule

RMF Control

IA-6

Severity

H

CCI

CCI-000206

Version

PPS9-00-004820

Vuln IDs

V-213602
V-68957

Rule IDs

SV-213602r508024_rule
SV-83561

To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. Obfuscation of user-provided information when typed into the system is a method used in addressing this risk. For example, displaying asterisks when a user types in a password or PIN, is an example of obscuring feedback of authentication information. This requirement is applicable when mixed-mode authentication is enabled. When this is the case, password-authenticated accounts can be created in and authenticated by SQL Server. Other STIG requirements prohibit the use of mixed-mode authentication except when justified and approved. This deals with the exceptions. Psql is part of any PostgreSQL installation. Other command-line tools may also exist. These tools can accept a plain-text password, but do offer alternative techniques. Since the typical user of these tools is a database administrator, the consequences of password compromise are particularly serious. Therefore, the use of plain-text passwords must be prohibited, as a matter of practice and procedure.

Checks: C-14824r290118_chk

For psql, which cannot be configured not to accept a plain-text password, and any other essential tool with the same limitation, verify that the system documentation explains the need for the tool, who uses it, and any relevant mitigations and that AO approval has been obtained. If not, this is a finding. Request evidence that all users of the tool are trained in the importance of using the "-P" option and not using the plain-text password option and in how to keep the password hidden and that they adhere to this practice. If not, this is a finding.

Fix: F-14822r290119_fix

For psql, which can accept a plain-text password, and any other essential tool with the same limitation: 1) Document the need for it, who uses it, and any relevant mitigations, and obtain AO approval. 2) Train all users of the tool in the importance of not using the plain-text password option and in how to keep the password hidden by using the "-P" option.

c

The EDB Postgres Advanced Server must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.

IA-7 - High - CCI-000803 - V-213603 - SV-213603r508024_rule

RMF Control

IA-7

Severity

H

CCI

CCI-000803

Version

PPS9-00-004900

Vuln IDs

V-213603
V-68959

Rule IDs

SV-213603r508024_rule
SV-83563

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-14825r290121_chk

If a FIPS-certified OpenSSL library is not installed and configured, this is a finding. Run this command to ensure that you are running RHEL: "cat /etc/redhat-release" Run this command to see the OpenSSL version: "openssl version" If "/etc/redhat-release" does not show a supported version of Red Hat Enterprise Linux or if the openssl version does not include "-fips" in the version, this is a finding.

Fix: F-14823r290122_fix

There is no known fix for a FIPS-compliant OpenSSL library on Microsoft Windows at this time. Configure RHEL OpenSSL as defined in section 9.1 of the RHEL OpenSSL FIPS Compliance documentation here: http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1758.pdf

b

The EDB Postgres Advanced Server must protect the confidentiality and integrity of all information at rest.

SC-28 - Medium - CCI-001199 - V-213604 - SV-213604r508024_rule

RMF Control

SC-28

Severity

M

CCI

CCI-001199

Version

PPS9-00-005700

Vuln IDs

V-213604
V-68961

Rule IDs

SV-213604r508024_rule
SV-83565

This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive) within an organizational information system. Applications and application users generate information throughout the course of their application use. User data generated, as well as application-specific configuration data, needs to be protected. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate. If the confidentiality and integrity of application data is not protected, the data will be open to compromise and unauthorized modification.

Checks: C-14826r290124_chk

If the application owner and Authorizing Official have determined that encryption of data at rest is NOT required, this is not a finding. Execute the following command as root: > df If the mounted filesystem where "<postgresql data directory>" exists is not located on an encrypted disk partition, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14824r290125_fix

Create an encrypted partition to host the "<postgresql data directory>" directory. This can be done at the OS level with a technology such as db-crypt or other encryption technologies provided by third-party tools. One option is to use LUKS as documented here: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Encryption.html (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

b

The EDB Postgres Advanced Server must isolate security functions from non-security functions.

SC-3 - Medium - CCI-001084 - V-213605 - SV-213605r508024_rule

RMF Control

SC-3

Severity

M

CCI

CCI-001084

Version

PPS9-00-005800

Vuln IDs

V-213605
V-68963

Rule IDs

SV-213605r508024_rule
SV-83567

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-14827r290127_chk

All PPAS built-in security packages are in the sys, pg_catalog, information_schema, and dbo schemas. If any application-specific packages have been added to these schemas, this is a finding.

Fix: F-14825r290128_fix

Remove all application-specific packages that were added to the sys, pg_catalog, information_schema, and dbo schemas.

b

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

SC-4 - Medium - CCI-001090 - V-213606 - SV-213606r508024_rule

RMF Control

SC-4

Severity

M

CCI

CCI-001090

Version

PPS9-00-005900

Vuln IDs

V-213606
V-68965

Rule IDs

SV-213606r508024_rule
SV-83569

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-14828r290130_chk

Review the procedures for the refreshing of development/test data from production. Review any scripts or code that exists for the movement of production data to development/test systems or to any other location or for any other purpose. Verify that copies of production data are not left in unprotected locations. If the code that exists for data movement does not comply with the organization-defined data transfer policy and/or fails to remove any copies of production data from unprotected locations, this is a finding.

Fix: F-14826r290131_fix

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

b

Access to database files must be limited to relevant processes and to authorized, administrative users.

SC-4 - Medium - CCI-001090 - V-213607 - SV-213607r508024_rule

RMF Control

SC-4

Severity

M

CCI

CCI-001090

Version

PPS9-00-006100

Vuln IDs

V-213607
V-68967

Rule IDs

SV-213607r508024_rule
SV-83571

Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. Permitting only DBMS processes and authorized, administrative users to have access to the files where the database resides helps ensure that those files are not shared inappropriately and are not open to backdoor access and manipulation.

Checks: C-14829r290133_chk

Verify User ownership, Group ownership, and permissions on the <postgressql data directory> directory: > ls –ald <postgresql data directory> If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the directory is more permissive than 700, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14827r290134_fix

Run these commands: 1) "chown enterprisedb <postgresql data directory>" 2) "chgrp enterprisedb <postgresql data directory>" 3) "chmod 700 <postgresql data directory>" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

b

The EDB Postgres Advanced Server must check the validity of all data inputs except those specifically identified by the organization.

SI-10 - Medium - CCI-001310 - V-213608 - SV-213608r508024_rule

RMF Control

SI-10

Severity

M

CCI

CCI-001310

Version

PPS9-00-006200

Vuln IDs

V-213608
V-68969

Rule IDs

SV-213608r508024_rule
SV-83573

Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application or information system compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database. Even when no such hijacking takes place, invalid input that gets recorded in the database, whether accidental or malicious, reduces the reliability and usability of the system. Available protections include data types, referential constraints, uniqueness constraints, range checking, and application-specific logic. Application-specific logic can be implemented within the database in stored procedures and triggers, where appropriate.

Checks: C-14830r290136_chk

Execute the following SQL as enterprisedb: SELECT * FROM sqlprotect.list_protected_users; If the database and user that handles user input is not listed or if sqlprotect.list_protected_users does not exist (meaning SQL/Protect is not installed), and an alternative means of reviewing for vulnerable code is not in use, this is a finding.

Fix: F-14828r290137_fix

Install and configure SQL/Protect as documented here: http://www.enterprisedb.com/docs/en/9.5/eeguide/Postgres_Plus_Enterprise_Edition_Guide.1.072.html# Alternatively, implement, document, and maintain another method of checking for the validity of inputs.

b

The EDB Postgres Advanced Server and associated applications must reserve the use of dynamic code execution for situations that require it.

SI-10 - Medium - CCI-001310 - V-213609 - SV-213609r508024_rule

RMF Control

SI-10

Severity

M

CCI

CCI-001310

Version

PPS9-00-006300

Vuln IDs

V-213609
V-68971

Rule IDs

SV-213609r508024_rule
SV-83575

With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being processed, either from inside knowledge or by observing system behavior in response to invalid inputs. When the attacker identifies scenarios where SQL queries are being assembled by application code (which may be within the database or separate from it) and executed dynamically, the attacker is then able to craft input strings that subvert the intent of the query. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database. The principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be utilized otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, pre-compiled stored procedures and functions (and triggers). This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Checks: C-14831r290139_chk

Execute the following SQL as enterprisedb: SELECT * FROM sqlprotect.list_protected_users; If the database and user that handles user input is not listed or if sqlprotect.list_protected_users does not exist (meaning SQL/Protect is not installed), and an alternative means of reviewing for vulnerable code is not in use, this is a finding.

Fix: F-14829r290140_fix

Install and configure SQL/Protect as documented here: http://www.enterprisedb.com/docs/en/9.5/eeguide/Postgres_Plus_Enterprise_Edition_Guide.1.072.html# Alternatively, implement, document, and maintain another method of checking for the validity of inputs.

b

The EDB Postgres Advanced Server and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.

SI-10 - Medium - CCI-001310 - V-213610 - SV-213610r508024_rule

RMF Control

SI-10

Severity

M

CCI

CCI-001310

Version

PPS9-00-006400

Vuln IDs

V-213610
V-68973

Rule IDs

SV-213610r508024_rule
SV-83577

With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being processed, either from inside knowledge or by observing system behavior in response to invalid inputs. When the attacker identifies scenarios where SQL queries are being assembled by application code (which may be within the database or separate from it) and executed dynamically, the attacker is then able to craft input strings that subvert the intent of the query. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database. The principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be utilized otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, pre-compiled stored procedures and functions (and triggers). When dynamic execution is necessary, ways to mitigate the risk include the following, which should be implemented both in the on-screen application and at the database level, in the stored procedures: -- Allow strings as input only when necessary. -- Rely on data typing to validate numbers, dates, etc. Do not accept invalid values. If substituting other values for them, think carefully about whether this could be subverted. -- Limit the size of input strings to what is truly necessary. -- If single quotes/apostrophes, double quotes, semicolons, equals signs, angle brackets, or square brackets will never be valid as input, reject them. -- If comment markers will never be valid as input, reject them. In SQL, these are -- or /* */ -- If HTML and XML tags, entities, comments, etc., will never be valid, reject them. -- If wildcards are present, reject them unless truly necessary. In SQL these are the underscore and the percentage sign, and the word ESCAPE is also a clue that wildcards are in use. -- If SQL key words, such as SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, ESCAPE, UNION, GRANT, REVOKE will never be valid, reject them. Use case-insensitive comparisons when searching for these. Bear in mind that some of these words, particularly Grant (as a person's name), could also be valid input. -- If there are range limits on the values that may be entered, enforce those limits. -- Institute procedures for inspection of programs for correct use of dynamic coding, by a party other than the developer. -- Conduct rigorous testing of program modules that use dynamic coding, searching for ways to subvert the intended use. -- Record the inspection and testing in the system documentation. -- Bear in mind that all this applies not only to screen input, but also to the values in an incoming message to a web service or to a stored procedure called by a software component that has not itself been hardened in these ways. Not only can the caller be subject to such vulnerabilities; it may itself be the attacker. This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Checks: C-14832r290142_chk

Execute the following SQL as enterprisedb: SELECT * FROM sqlprotect.list_protected_users; If the database and user that handles user input is not listed or if sqlprotect.list_protected_users does not exist (meaning SQL/Protect is not installed), and an alternative means of reviewing for vulnerable code is not in use, this is a finding.

Fix: F-14830r290143_fix

Install and configure SQL/Protect as documented here: http://www.enterprisedb.com/docs/en/9.5/eeguide/Postgres_Plus_Enterprise_Edition_Guide.1.072.html# Alternatively, implement, document, and maintain another method of checking for the validity of inputs.

b

The EDB Postgres Advanced Server must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.

SI-11 - Medium - CCI-001312 - V-213611 - SV-213611r508024_rule

RMF Control

SI-11

Severity

M

CCI

CCI-001312

Version

PPS9-00-006500

Vuln IDs

V-213611
V-68975

Rule IDs

SV-213611r508024_rule
SV-83579

Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromising the data and security of the system. The structure and content of error messages need to be carefully considered by the organization and development team. Databases can inadvertently provide a wealth of information to an attacker through improperly handled error messages. In addition to sensitive business or personal information, database errors can provide host names, IP addresses, user names, and other system information not required for troubleshooting but very useful to someone targeting the system. Carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers. This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Checks: C-14833r290145_chk

Check custom database code to verify that error messages do not contain information beyond what is needed for troubleshooting the issue. If custom database errors contain PII data, sensitive business data, or information useful for identifying the host system or database structure, this is a finding.

Fix: F-14831r290146_fix

Configure custom database code and associated application code not to divulge sensitive information or information useful for system identification in error messages.

b

The EDB Postgres Advanced Server must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.

SI-11 - Medium - CCI-001314 - V-213612 - SV-213612r508024_rule

RMF Control

SI-11

Severity

M

CCI

CCI-001314

Version

PPS9-00-006600

Vuln IDs

V-213612
V-68977

Rule IDs

SV-213612r508024_rule
SV-83581

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 appropriate approval. This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Checks: C-14834r290148_chk

Check custom database code to determine if detailed error messages are ever displayed to unauthorized individuals. If detailed error messages are displayed to individuals not authorized to view them, this is a finding.

Fix: F-14832r290149_fix

Configure custom database code and associated application code not to display detailed error messages to those not authorized to view them.

b

The EDB Postgres Advanced Server must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

AC-12 - Medium - CCI-002361 - V-213613 - SV-213613r508024_rule

RMF Control

AC-12

Severity

M

CCI

CCI-002361

Version

PPS9-00-006700

Vuln IDs

V-213613
V-68979

Rule IDs

SV-213613r508024_rule
SV-83583

This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination ends all processes associated with a user's logical session except those batch processes/jobs that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. This capability is typically reserved for specific cases where the system owner, data owner, or organization requires additional assurance.

Checks: C-14835r290151_chk

Review system documentation to obtain the organization's definition of circumstances requiring automatic session termination. If the documentation explicitly states that such termination is not required or is prohibited, this is not a finding. If the documentation requires automatic session termination but the DBMS is not configured via triggers, scripts, or other organization-defined manners to terminate sessions when required, this is a finding.

Fix: F-14833r290152_fix

Execute this SQL command in the places where the documentation requires automatic session termination: SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE usename = '<username>'

b

The EDB Postgres Advanced Server must associate organization-defined types of security labels having organization-defined security label values with information in storage.

AC-16 - Medium - CCI-002262 - V-213614 - SV-213614r508024_rule

RMF Control

AC-16

Severity

M

CCI

CCI-002262

Version

PPS9-00-006900

Vuln IDs

V-213614
V-68981

Rule IDs

SV-213614r508024_rule
SV-83585

Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.

Checks: C-14836r290154_chk

If security labeling is not required, this is not applicable (NA). If security labeling requirements have been specified, execute the following SQL as enterprisedb: SELECT * from ALL_POLICIES where OBJECT_NAME = '<table name>'; If a policy is not enabled for the table requiring security labeling, this is a finding.

Fix: F-14834r290155_fix

Create a row-level policy for all required tables as defined here: http://www.enterprisedb.com/docs/en/9.5/oracompat/Database_Compatibility_for_Oracle_Developers_Guide.1.201.html#pID0E0D5J0HA

b

The EDB Postgres Advanced Server must associate organization-defined types of security labels having organization-defined security label values with information in process.

AC-16 - Medium - CCI-002263 - V-213615 - SV-213615r508024_rule

RMF Control

AC-16

Severity

M

CCI

CCI-002263

Version

PPS9-00-007000

Vuln IDs

V-213615
V-68983

Rule IDs

SV-213615r508024_rule
SV-83587

Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.

Checks: C-14837r290157_chk

If security labeling is not required, this is not applicable (NA). If security labeling requirements have been specified, execute the following SQL as enterprisedb: SELECT * from ALL_POLICIES where OBJECT_NAME = '<table name>'; If a policy is not enabled for the table requiring security labeling, this is a finding.

Fix: F-14835r290158_fix

Create a row-level policy for all required tables as defined here: http://www.enterprisedb.com/docs/en/9.5/oracompat/Database_Compatibility_for_Oracle_Developers_Guide.1.201.html#pID0E0D5J0HA

b

The EDB Postgres Advanced Server must associate organization-defined types of security labels having organization-defined security label values with information in transmission.

AC-16 - Medium - CCI-002264 - V-213616 - SV-213616r508024_rule

RMF Control

AC-16

Severity

M

CCI

CCI-002264

Version

PPS9-00-007100

Vuln IDs

V-213616
V-68985

Rule IDs

SV-213616r508024_rule
SV-83589

Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.

Checks: C-14838r290160_chk

If security labeling is not required, this is not applicable (NA). If security labeling requirements have been specified, execute the following SQL as enterprisedb: SELECT * from ALL_POLICIES where OBJECT_NAME = '<table name>'; If a policy is not enabled for the table requiring security labeling, this is a finding.

Fix: F-14836r290161_fix

Create a row-level policy for all required tables as defined here: http://www.enterprisedb.com/docs/en/9.5/oracompat/Database_Compatibility_for_Oracle_Developers_Guide.1.201.html#pID0E0D5J0HA

b

The EDB Postgres Advanced Server must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.

AC-6 - Medium - CCI-002235 - V-213617 - SV-213617r508024_rule

RMF Control

AC-6

Severity

M

CCI

CCI-002235

Version

PPS9-00-007400

Vuln IDs

V-213617
V-68987

Rule IDs

SV-213617r508024_rule
SV-83591

Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. System documentation should include a definition of the functionality considered privileged. Depending on circumstances, privileged functions can include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. A privileged function in the DBMS/database 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 There may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples 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, the prevention of unauthorized use of privileged functions may be achieved by means of DBMS security features, database triggers, other mechanisms, or a combination of these.

Checks: C-14839r290163_chk

Review the system documentation to obtain the definition of the database/DBMS functionality considered privileged in the context of the system in question. If any functionality considered privileged has access privileges granted to non-privileged users, this is a finding.

Fix: F-14837r290164_fix

Revoke any privileges to privileged functionality by executing the REVOKE command as documented here: http://www.postgresql.org/docs/current/static/sql-revoke.html

b

Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.

AC-6 - Medium - CCI-002233 - V-213618 - SV-213618r508024_rule

RMF Control

AC-6

Severity

M

CCI

CCI-002233

Version

PPS9-00-007500

Vuln IDs

V-213618
V-68989

Rule IDs

SV-213618r508024_rule
SV-83593

In certain situations, to provide required functionality, a DBMS needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. Privilege elevation must be utilized only where necessary and protected from misuse. This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Checks: C-14840r290166_chk

Review the system documentation and source code of the application(s) using the database. If elevation of DBMS privileges is used but not documented, this is a finding. If elevation of DBMS privileges is documented but not implemented as described in the documentation, this is a finding. If the privilege-elevation logic can be invoked in ways other than intended, in contexts other than intended, or by subjects/principals other than intended, this is a finding. Execute the following SQL to find any SECURITY DEFINER functions (meaning they are executed as owner rather than invoker): select proname from pg_proc where prosecdef = true; If any of these functions should not be SECURITY DEFINER, this is a finding.

Fix: F-14838r290167_fix

Determine where, when, how, and by what principals/subjects elevated privilege is needed. Modify the system and the application(s) using the database to ensure privilege elevation is used only as required. To alter a function to use SECURITY INVOKER instead of SECURITY DEFINER, execute the following SQL: ALTER FUNCTION <function()> SECURITY INVOKER;

b

Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.

AC-6 - Medium - CCI-002233 - V-213619 - SV-213619r508024_rule

RMF Control

AC-6

Severity

M

CCI

CCI-002233

Version

PPS9-00-007510

Vuln IDs

V-213619
V-68991

Rule IDs

SV-213619r508024_rule
SV-83595

In certain situations, to provide required functionality, a DBMS needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. Privilege elevation must be utilized only where necessary and protected from misuse. This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Checks: C-14841r290169_chk

Review the system documentation and source code of the application(s) using the database. If elevation of DBMS privileges is used but not documented, this is a finding. If elevation of DBMS privileges is documented but not implemented as described in the documentation, this is a finding. If the privilege-elevation logic can be invoked in ways other than intended, in contexts other than intended, or by subjects/principals other than intended, this is a finding. Execute the following SQL to find any users with BYPASS RLS permissions: select rolname from pg_roles where rolbypassrls = true; If any of these users are not superusers that should bypass RLS, this is a finding.

Fix: F-14839r290170_fix

Determine where, when, how, and by what principals/subjects elevated privilege is needed. Modify the system and the application(s) using the database to ensure privilege elevation is used only as required. To alter a user to not allow bypassing RLS, execute the following SQL: ALTER USER <user> NOBYPASSRLS;

b

The EDB Postgres Advanced Server must utilize centralized management of the content captured in audit records generated by all components of the EDB Postgres Advanced Server.

AU-3 - Medium - CCI-001844 - V-213620 - SV-213620r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-001844

Version

PPS9-00-007700

Vuln IDs

V-213620
V-68993

Rule IDs

SV-213620r508024_rule
SV-83597

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-14842r290172_chk

If a centralized log collecting tool such as Postgres Enterprise Manager (PEM) is not installed and configured to automatically collect audit logs, this is a finding. Review the system documentation for a description of how audit records are off-loaded and how local audit log space is managed.

Fix: F-14840r290173_fix

Install a centralized log collecting tool and configure it as instructed in its documentation. If using PEM, find the instructions at http://www.enterprisedb.com/docs/en/6.0/pemgetstarted/toc.html

b

The EDB Postgres Advanced Server must provide centralized configuration of the content to be captured in audit records generated by all components of the EDB Postgres Advanced Server.

AU-3 - Medium - CCI-001844 - V-213621 - SV-213621r508024_rule

RMF Control

AU-3

Severity

M

CCI

CCI-001844

Version

PPS9-00-007800

Vuln IDs

V-213621
V-68995

Rule IDs

SV-213621r508024_rule
SV-83599

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-14843r290175_chk

If a unified tool for audit configuration such as PEM (Postgres Enterprise Manager) is not installed and configured to automatically collect audit logs, this is a finding. Review the system documentation for a description of how audit records are off-loaded and how local audit log space is managed.

Fix: F-14841r290176_fix

Install a centralized log collecting tool and configure it as instructed in its documentation. If using PEM, find the instructions at http://www.enterprisedb.com/docs/en/6.0/pemgetstarted/toc.html

b

The EDB Postgres Advanced Server must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.

AU-4 - Medium - CCI-001849 - V-213622 - SV-213622r508024_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001849

Version

PPS9-00-007900

Vuln IDs

V-213622
V-68997

Rule IDs

SV-213622r508024_rule
SV-83601

In order to ensure sufficient storage capacity for the audit logs, the DBMS must be able to allocate audit record storage capacity. Although another requirement (SRG-APP-000515-DB-000318) mandates that audit data be off-loaded to a centralized log management system, it remains necessary to provide space on the database server to serve as a buffer against outages and capacity limits of the off-loading mechanism. The task of allocating audit record storage capacity is usually performed during initial installation of the DBMS and is closely associated with the DBA and system administrator roles. The DBA or system administrator will usually coordinate the allocation of physical drive space with the application owner/installer and the application will prompt the installer to provide the capacity information, the physical location of the disk, or both. In determining the capacity requirements, consider such factors as: total number of users; expected number of concurrent users during busy periods; number and type of events being monitored; types and amounts of data being captured; the frequency/speed with which audit records are off-loaded to the central log management system; and any limitations that exist on the DBMS's ability to reuse the space formerly occupied by off-loaded records.

Checks: C-14844r290178_chk

Investigate whether there have been any incidents where the DBMS ran out of audit log space since the last time the space was allocated or other corrective measures were taken. If there have been, this is a finding.

Fix: F-14842r290179_fix

Allocate sufficient audit file space to "<postgresql data directory>/edb_audit" to support peak demand.

b

The EDB Postgres Advanced Server 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-213623 - SV-213623r508024_rule

RMF Control

AU-5

Severity

M

CCI

CCI-001855

Version

PPS9-00-008000

Vuln IDs

V-213623
V-68999

Rule IDs

SV-213623r508024_rule
SV-83603

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-14845r290181_chk

If Postgres Enterprise Manager (PEM) or another similar monitoring capability is not installed and configured to probe storage volume utilization of "<postgresql data directory>" and notify appropriate support staff upon storage volume utilization reaching 75 percent, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix: F-14843r290182_fix

Install PEM and configure a probe to monitor "<postgresql data directory>" and notify appropriate support staff upon storage volume utilization reaching 75 percent. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) Example steps for creating a probe are below, using the thin client (browser) PEM interface. Refer also to the Supplemental Procedures document, supplied with this STIG. Open the PEM web console in a browser - Log in - Click on the agent for the machine to be monitored - Select "Management | Probe Configuration" - Select "Disk Space" and set the check interval as you like - Select "Management | Alerting" - Name the definition "Audit Log Full" - Select Template "Disk Consumption Percentage" - Set Frequency, Comparison Operator, and Thresholds (1 minute, >, 95/96/97 for example) - Enter the Mount Point for where the audit log is - Click Notification tab - Click Email all alerts - Click "Execute Script" on Monitored Server - Enter script to showdown postgres, generally "service ppas-95 stop" - Click Add/Change to save, click "OK" to exit dialog box

b

The EDB Postgres Advanced Server must provide an immediate real-time alert to appropriate support staff of all audit log failures.

AU-5 - Medium - CCI-001858 - V-213624 - SV-213624r508024_rule

RMF Control

AU-5

Severity

M

CCI

CCI-001858

Version

PPS9-00-008100

Vuln IDs

V-213624
V-69001

Rule IDs

SV-213624r508024_rule
SV-83605

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. A failure of database auditing will result in either the database continuing to function without auditing or in a complete halt to database operations. When audit processing fails, appropriate personnel must be alerted immediately to avoid further downtime or unaudited transactions 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-14846r495386_chk

Review Postgres Enterprise Manager (PEM) alert settings, OS, or third-party logging software settings to determine whether a real-time alert will be sent to the appropriate personnel when auditing fails for any reason. If real-time alerts are not sent upon auditing failure, this is a finding.

Fix: F-14844r290185_fix

Install PEM and configure audit failure event alerting as documented here: http://www.enterprisedb.com/docs/en/5.0/pemgetstarted/PEM_Getting_Started_Guide.1.28.html An example for creating an alert that ensure the audit directory does not fill up is included below, using the thin client (browser) PEM interface. Refer also to the Supplemental Procedures document, supplied with this STIG. Open the PEM web console in a browser - Log in - Click on the agent for the machine to be monitored - Select "Management | Probe Configuration" - Select "Disk Space" and set the check interval as you like - Select "Management | Alerting" - Name the definition "Audit Log Full" - Select Template "Disk Consumption Percentage" - Set Frequency, Comparison Operator, and Thresholds (1 minute, >, 95/96/97 for example) - Enter the Mount Point for where the audit log is - Click Notification tab - Click Email all alerts - Click "Execute Script" on Monitored Server

b

The EDB Postgres Advanced Server must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.

CM-11 - Medium - CCI-001812 - V-213625 - SV-213625r508024_rule

RMF Control

CM-11

Severity

M

CCI

CCI-001812

Version

PPS9-00-008400

Vuln IDs

V-213625
V-69003

Rule IDs

SV-213625r508024_rule
SV-83607

Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceed the rights of a regular user. DBMS functionality and the nature and requirements of databases will vary; so while users are not permitted to install unapproved software, there may be instances where the organization allows the user to install approved software packages such as from an approved software repository. The requirements for production servers will be more restrictive than those used for development and research. The DBMS must enforce software installation by users based upon what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software whose pedigree with regard to being potentially malicious is unknown or suspect) by the organization. In the case of a database management system, this requirement covers stored procedures, functions, triggers, views, etc.

Checks: C-14847r290187_chk

If EDB Postgres supports only software development, experimentation, and/or developer-level testing (that is, excluding production systems, integration testing, stress testing, and user acceptance testing), this is not a finding. Review the EDB Postgres security settings with respect to non-administrative users' ability to create, alter, or replace logic modules, to include but not necessarily only stored procedures, functions, triggers, and views. These psql commands can help with showing existing permissions of databases and schemas: \l \dn+ If any such permissions exist and are not documented and approved, this is a finding.

Fix: F-14845r290188_fix

Document and obtain approval for any non-administrative users who require the ability to create, alter, or replace logic modules. Implement the approved permissions. Revoke (or deny) any unapproved permissions and remove any unauthorized role memberships.

b

The EDB Postgres Advanced Server must enforce access restrictions associated with changes to the configuration of the EDB Postgres Advanced Server or database(s).

CM-5 - Medium - CCI-001813 - V-213626 - SV-213626r508024_rule

RMF Control

CM-5

Severity

M

CCI

CCI-001813

Version

PPS9-00-008500

Vuln IDs

V-213626
V-69005

Rule IDs

SV-213626r508024_rule
SV-83609

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-14848r290190_chk

Review the security configuration of the EDB Postgres database(s). If unauthorized users can start the SQL Server Configuration Manager or SQL Server Management Studio, this is a finding. If EDB Postgres does not enforce access restrictions associated with changes to the configuration of the database(s), this is a finding. - - - - - To assist in conducting reviews of permissions, the following psql commands describe permissions of databases, schemas, and users: \l \dn+ \du Permissions of concern in this respect include the following, and possibly others: - any user with SUPERUSER privileges - any database or schema with "C" (create) or "w" (update) privileges that are not necessary

Fix: F-14846r290191_fix

Configure EDB PPAS to enforce access restrictions associated with changes to the configuration of the EDB Postgres database(s).

b

The EDB Postgres Advanced Server must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the EDB Postgres Advanced Server or database(s).

CM-5 - Medium - CCI-001814 - V-213627 - SV-213627r508024_rule

RMF Control

CM-5

Severity

M

CCI

CCI-001814

Version

PPS9-00-008600

Vuln IDs

V-213627
V-69007

Rule IDs

SV-213627r508024_rule
SV-83611

Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an audit trail would not be available for forensic investigation for after-the-fact actions. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.

Checks: C-14849r290193_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14847r290194_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server 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-213628 - SV-213628r508024_rule

RMF Control

CM-7

Severity

M

CCI

CCI-001762

Version

PPS9-00-008700

Vuln IDs

V-213628
V-69009

Rule IDs

SV-213628r508024_rule
SV-83613

Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats. A database cluster listens on a single port (usually 5444 for Postgres Plus Advanced Server). The Postgres Enterprise Manager (PEM) agents do not listen on ports, they only act as clients to the PEM server. The PEM server has two components (a repository which is a Postgres database) and a PHP application. The PHP application listens on a port configured in Apache, generally 8080 or 8443. The ports to check are: 1) The primary Postgres cluster port, 2) The PEM PHP port, and 3) The PEM Repository DB port. Generally 2 and 3 should be installed on an isolated management machine without access from anyone other than administrators.

Checks: C-14850r290196_chk

Review the network functions, ports, protocols, and services supported by the DBMS. If any protocol is prohibited by the PPSM guidance and is enabled, this is a finding. Open "<postgresql data directory>/pg_hba.conf" in a viewer. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) If any rows have a TYPE that is "host" or "hostnossl", this is a finding. Execute the following SQL as enterprisedb: SHOW port; If the displayed port is not allowed, this is a finding.

Fix: F-14848r290197_fix

Disable each prohibited network function, port, protocol, or service prohibited by the PPSM guidance. Open "<postgresql data directory>/pg_hba.conf" in an editor. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) Change the TYPE of any rows not starting with a "#" to be either "local" or "hostssl". The METHOD for the local rows should be "peer", which will authenticate based on the operating system name. The METHOD for the hostssl rows should be one of these (in preferred order): cert, ldap, sspi, pam, md5 Execute the following SQL as enterprisedb: ALTER SYSTEM SET port = <port>; Execute the following operating system command as root: systemctl restart ppas-9.5.service

b

The EDB Postgres Advanced Server must require users to re-authenticate when organization-defined circumstances or situations require re-authentication.

IA-11 - Medium - CCI-002038 - V-213629 - SV-213629r508024_rule

RMF Control

IA-11

Severity

M

CCI

CCI-002038

Version

PPS9-00-008800

Vuln IDs

V-213629
V-69011

Rule IDs

SV-213629r508024_rule
SV-83615

The DoD standard for authentication of an interactive user is the presentation of a Common Access Card (CAC) or other physical token bearing a valid, current, DoD-issued Public Key Infrastructure (PKI) certificate, coupled with a Personal Identification Number (PIN) to be entered by the user at the beginning of each session and whenever re-authentication is required. Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical the user re-authenticate. In addition to the re-authentication requirements associated with session locks, organizations may require re-authentication of individuals and/or devices in other situations, including (but not limited to) the following circumstances: (i) When authenticators change; (ii) When roles change; (iii) When security categories of information systems change; (iv) When the execution of privileged functions occurs; (v) After a fixed period of time; or (vi) Periodically. Within the DoD, the minimum circumstances requiring re-authentication are privilege escalation and role changes.

Checks: C-14851r290199_chk

If organization-defined circumstances or situations require re-authentication, and these situations are not configured to terminate existing logins to require re-authentication, this is a finding.

Fix: F-14849r290200_fix

Determine the organization-defined circumstances or situations that require re-authentication and ensure that the following SQL is executed in those situations. To require a single user to re-authenticate, use this SQL: "select pg_terminate_backend(pid) from pg_stat_activity where user='<username>';" To require all users to re-authenticate, use this SQL: "select pg_terminate_backend(pid) from pg_stat_activity where user like '%';".

b

The EDB Postgres Advanced Server must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.

SC-23 - Medium - CCI-002470 - V-213630 - SV-213630r508024_rule

RMF Control

SC-23

Severity

M

CCI

CCI-002470

Version

PPS9-00-009100

Vuln IDs

V-213630
V-69013

Rule IDs

SV-213630r508024_rule
SV-83617

Only DoD-approved external PKIs have been evaluated to ensure that they have security controls and identity vetting procedures in place which are sufficient for DoD systems to rely on the identity asserted in the certificate. PKIs lacking sufficient security controls and identity vetting procedures risk being compromised and issuing certificates that enable adversaries to impersonate legitimate users. The authoritative list of DoD-approved PKIs is published at http://iase.disa.mil/pki-pke/interoperability. This requirement focuses on communications protection for the DBMS session rather than for the network packet.

Checks: C-14852r290202_chk

Verify that the root.crt certificate was issued by a valid DoD entity. > openssl x509 -in <postgresql data directory>/root.crt –text | grep –i “issuer”. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) If any issuers are listed that are not valid DoD certificate authorities, this is a finding.

Fix: F-14850r290203_fix

Remove any certificate that was not issued by a valid DoD certificate authority. Contact the organization's certificate issuer and request a new certificate that is issued by a valid DoD certificate authorities.

b

The EDB Postgres Advanced Server must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.

SC-28 - Medium - CCI-002475 - V-213631 - SV-213631r508024_rule

RMF Control

SC-28

Severity

M

CCI

CCI-002475

Version

PPS9-00-009200

Vuln IDs

V-213631
V-69015

Rule IDs

SV-213631r508024_rule
SV-83619

DBMSs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the DBMS or implemented via additional software or operating system/file system settings, as appropriate to the situation. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides.

Checks: C-14853r290205_chk

Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from modification, which must include, at a minimum, PII and classified information. If no information is identified as requiring such protection, this is not a finding. Review the configuration of the DBMS, operating system/file system, and additional software as relevant. If any of the information defined as requiring cryptographic protection from modification is not encrypted in a manner that provides the required level of protection, this is a finding.

Fix: F-14851r290206_fix

Create an encrypted partition to host the "<postgresql data directory>" directory. This can be done at the OS level with a technology such as db-crypt or other encryption technologies provided by third-party tools. If only certain columns require encryption, use pgcrypt to encrypt those columns as documented here: http://www.postgresql.org/docs/current/static/pgcrypto.html

b

The EDB Postgres Advanced Server must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.

SC-28 - Medium - CCI-002476 - V-213632 - SV-213632r508024_rule

RMF Control

SC-28

Severity

M

CCI

CCI-002476

Version

PPS9-00-009300

Vuln IDs

V-213632
V-69017

Rule IDs

SV-213632r508024_rule
SV-83621

DBMSs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the DBMS or implemented via additional software or operating system/file system settings, as appropriate to the situation. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides.

Checks: C-14854r290208_chk

Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from modification, which must include, at a minimum, PII and classified information. If no information is identified as requiring such protection, this is not a finding. Review the configuration of the DBMS, operating system/file system, and additional software as relevant. If any of the information defined as requiring cryptographic protection from modification is not encrypted in a manner that provides the required level of protection, this is a finding.

Fix: F-14852r290209_fix

Create an encrypted partition to host the "<postgresql data directory>" directory. This can be done at the OS level with a technology such as db-crypt or other encryption technologies provided by third-party tools. If only certain columns need encryption, use pgcrypt to encrypt those columns as documented here: http://www.postgresql.org/docs/current/static/pgcrypto.html

b

The EDB Postgres Advanced Server must maintain the confidentiality and integrity of information during preparation for transmission.

SC-8 - Medium - CCI-002420 - V-213633 - SV-213633r557394_rule

RMF Control

SC-8

Severity

M

CCI

CCI-002420

Version

PPS9-00-009500

Vuln IDs

V-213633
V-69019

Rule IDs

SV-213633r557394_rule
SV-83623

Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, the DBMS, associated applications, and infrastructure must leverage transmission protection mechanisms. EDB Postgres Advanced Server provides native support for using SSL connections to encrypt client/server communications. To enable the use of SSL, the postgres “ssl” configuration parameter must be set to “on”, and the database instance needs to be configured to use a valid server certificate and private key installed on the server. With SSL enabled, connections made to the database server will default to being encrypted. However, it is possible for clients to override the default and attempt to establish an unencrypted connection. To prevent connections made from non-local hosts from being unencrypted, the postgres host-based authentication settings should be configured to only allow hostssl (i.e., encrypted) connections. The hostssl connections can be further configured to require that the client present a valid (trusted) SSL certificate for a connection.

Checks: C-14855r557392_chk

If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, this is not a finding. Open "<postgresql data directory>/pg_hba.conf" in a viewer or editor. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.) If any rows do not have TYPE of "hostssl" as well as a METHOD of "cert", this is a finding.

Fix: F-14853r557393_fix

To configure EDB Postgres Advanced Server to use SSL, open the ”postgresql.conf" file in an editor. Note that the default location for the postgresql.conf file is in the postgresql data directory. The location of the postgresql.conf for a running EDB Postgres instance can be found using the following command run from a command prompt: psql -d <database name> -U <database superuser name> -c “SHOW config_file” Where, <database name> is any database in the EDB postgres instance and <database superuser name> is a database superuser. By default, a database named "edb" and a superuser named "enterprisedb" are installed with EDB Postgres Advanced Server (EPAS). In the postgresql.conf file, set the “ssl” parameter as follows: ssl = on Make sure the parameter is uncommented. In order to start an EDB Postgres Advanced Server instance in SSL mode, files containing the server certificate and private key must exist. By default, these files are expected to exist in the Postgres data directory and are expected to be named server.crt and server.key, respectively. Update the ssl_cert_file and ssl_cert_key parameters in the postgresql.conf file if the files are placed in a different location or are named differently. Note that changes to the SSL parameter setting and any of the other SSL-related parameters require a database server restart to be put the changes into effect. To restart the database on a systemd server, issue the following command as the root user or a user with sudo access: systemctl restart edb-as-<EPAS version> Where, “<EPAS version>” is the major version of the EDB Postgres Advanced Server instance (e.g., 9.6). To restart the database on an initd server, issue the following command as the root user or a user with sudo access: service edb-as-<EDB Postgres version> restart Where, “<EPAS version>” is the major version of the EDB Postgres Advanced Server instance (e.g., 9.6). After verifying SSL is enabled for the database, open the pg_hba.conf file in an editor to configure the host-based authentication settings. Note the default location for the pg_hba.conf file is in the postgresql data directory. The location of the pg_hba.conf file for a running EDB postgres instance can be found using the following command run from a command prompt: psql -d <database name> -U <database superuser name> -c "SHOW hba_file" Where, <database name> is any database in the EDB postgres instance and <database superuser name> is a database superuser. By default, a database named "edb" and a superuser named "enterprisedb" are installed with EDB Postgres Advanced Server (EPAS). Obtain approval and document any uncommented entries with corresponding justification that are not of type hostssl and do not include the “clientcert=1” option. For any entries that are not of type hostssl authentication with the “clientcert=1” option and not documented and approved, change the "TYPE" column to “hostssl” and add the “clientcert=1” authentication method option. Note that changes to the host-based authentication settings require a database reload in order to apply the updated settings. To reload the database on a systemd server, issue the following command as the root user or a user with sudo access: systemctl reload edb-as-<EPAS version> Where, “<EPAS version>” is the major version of the EDB Postgres Advanced Server instance (e.g., 9.6). To reload the database on an initd server, issue the following command as the root user or a user with sudo access: service edb-as-<EDB Postgres version> reload Where, “<EPAS version>” is the major version of the EDB Postgres Advanced Server instance (e.g., 9.6). For more information on configuring PostgreSQL to use SSL, consult the following documentation: https://www.postgresql.org/docs/current/ssl-tcp.html

b

The EDB Postgres Advanced Server must maintain the confidentiality and integrity of information during reception.

SC-8 - Medium - CCI-002422 - V-213634 - SV-213634r557397_rule

RMF Control

SC-8

Severity

M

CCI

CCI-002422

Version

PPS9-00-009600

Vuln IDs

V-213634
V-69021

Rule IDs

SV-213634r557397_rule
SV-83625

Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. This requirement applies only to those applications that are either distributed or can allow access to data nonlocally. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When receiving data, the DBMS, associated applications, and infrastructure must leverage protection mechanisms. EDB Postgres Advanced Server provides native support for using SSL connections to encrypt client/server communications. To enable the use of SSL, the postgres “ssl” configuration parameter must be set to “on” and the database instance needs to be configured to use a valid server certificate and private key installed on the server. With SSL enabled, connections made to the database server will default to being encrypted. However, it is possible for clients to override the default and attempt to establish an unencrypted connection. To prevent connections made from non-local hosts from being unencrypted, the postgres host-based authentication settings should be configured to only allow hostssl (i.e., encrypted) connections. The hostssl connections can be further configured to require that the client present a valid (trusted) SSL certificate for a connection.

Checks: C-14856r557395_chk

If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, this is not a finding. First, check if SSL is enabled for the database instance by executing the following command from a command prompt: psql -d <database name> -U <database superuser name> -c "SHOW ssl” Where, <database name> is any database in the EDB postgres instance and <database superuser name> is a database superuser. By default, a database named "edb" and a superuser named "enterprisedb" are installed with EDB Postgres Advanced Server (EPAS). If the result is not "on", this is a finding. Next, open the pg_hba.conf file in a viewer or editor and review the authentication settings that are configured in that file. Note the default location for the pg_hba.conf file is in the postgresql data directory. The location of the pg_hba.conf file for a running EDB postgres instance can be found using the following command run from a command prompt: psql -d <database name> -U <database superuser name> -c "SHOW hba_file" Where, <database name> is any database in the EDB postgres instance and <database superuser name> is a database superuser. By default, a database named "edb" and a superuser named "enterprisedb" are installed with EDB Postgres Advanced Server (EPAS). If any uncommented lines are not of TYPE "hostssl" and do not include the "clientcert=1" authentication option and are not documented in the system security plan or equivalent document as being approved, this is a finding.

Fix: F-14854r557396_fix

To configure EDB Postgres Advanced Server to use SSL, open the ”postgresql.conf" file in an editor. Note the default location for the postgresql.conf file is in the postgresql data directory. The location of the postgresql.conf for a running EDB Postgres instance can be found using the following command run from a command prompt: psql -d <database name> -U <database superuser name> -c “SHOW config_file” Where, <database name> is any database in the EDB postgres instance and <database superuser name> is a database superuser. By default, a database named "edb" and a superuser named "enterprisedb" are installed with EDB Postgres Advanced Server (EPAS). In the postgresql.conf file, set the “ssl” parameter as follows: ssl = on Make sure the parameter is uncommented. In order to start an EDB Postgres Advanced Server instance in SSL mode, files containing the server certificate and private key must exist. By default, these files are expected to exist in the Postgres data directory and are expected to be named server.crt and server.key, respectively. Update the ssl_cert_file and ssl_cert_key parameters in the postgresql.conf file if the files are placed in a different location or are named differently. Note that changes to the SSL parameter setting and any of the other SSL- related parameters require a database server restart to be put the changes into effect. To restart the database on a systemd server, issue the following command as the root user or a user with sudo access: systemctl restart edb-as-<EPAS version> Where, “<EPAS version>” is the major version of the EDB Postgres Advanced Server instance (e.g., 9.6). To restart the database on an initd server, issue the following command as the root user or a user with sudo access: service edb-as-<EDB Postgres version> restart Where, “<EPAS version>” is the major version of the EDB Postgres Advanced Server instance (e.g., 9.6). After verifying that SSL is enabled for the database, open the pg_hba.conf file in an editor to configure the host-based authentication settings. Note that the default location for the pg_hba.conf file is in the postgresql data directory. The location of the pg_hba.conf file for a running EDB postgres instance can be found using the following command run from a command prompt: psql -d <database name> -U <database superuser name> -c "SHOW hba_file" Where, <database name> is any database in the EDB postgres instance and <database superuser name> is a database superuser. By default, a database named "edb" and a superuser named "enterprisedb" are installed with EDB Postgres Advanced Server (EPAS). Obtain approval and document any uncommented entries with corresponding justification that are not of type hostssl and do not include the “clientcert=1” option. For any entries that are not of type hostssl authentication with the “clientcert=1” option and not documented and approved, change the "TYPE" column to “hostssl” and add the “clientcert=1” authentication method option. Note that changes to the host-based authentication settings require a database reload in order to apply the updated settings.

b

When invalid inputs are received, the EDB Postgres Advanced Server must behave in a predictable and documented manner that reflects organizational and system objectives.

SI-10 - Medium - CCI-002754 - V-213635 - SV-213635r508024_rule

RMF Control

SI-10

Severity

M

CCI

CCI-002754

Version

PPS9-00-009700

Vuln IDs

V-213635
V-69023

Rule IDs

SV-213635r508024_rule
SV-83627

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. This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.

Checks: C-14857r290217_chk

Execute the following SQL as enterprisedb: SELECT * FROM sqlprotect.list_protected_users; If the database and user that handles user input is not listed or if sqlprotect.list_protected_users does not exist (meaning SQL/Protect is not installed), and an alternative means of reviewing for vulnerable code is not in use, this is a finding.

Fix: F-14855r290218_fix

Install and configure SQL/Protect as documented here: http://www.enterprisedb.com/docs/en/9.5/eeguide/Postgres_Plus_Enterprise_Edition_Guide.1.072.html# Alternatively, implement, document, and maintain another method of checking for the validity of inputs.

b

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

SI-2 - Medium - CCI-002605 - V-213636 - SV-213636r508024_rule

RMF Control

SI-2

Severity

M

CCI

CCI-002605

Version

PPS9-00-009900

Vuln IDs

V-213636
V-69025

Rule IDs

SV-213636r508024_rule
SV-83629

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. Timeframes 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-14858r290220_chk

Obtain evidence that software patches are obtained from EnterpriseDB and are consistently applied to the DBMS within the timeframe defined for each patch. If such evidence cannot be obtained, or the evidence that is obtained indicates a pattern of noncompliance, this is a finding. If an administrator is not registered on the EDB Support Portal with an email address for monitoring technical alerts, this is a finding.

Fix: F-14856r290221_fix

Institute and adhere to policies and procedures to ensure that patches are consistently obtained from EnterpriseDB and applied to the DBMS within the time allowed. Ensure that a monitored email address is registered as a user on the EDB support portal and is receiving technical alerts.

b

The EDB Postgres Advanced Server must generate audit records when security objects are accessed.

AU-12 - Medium - CCI-000172 - V-213637 - SV-213637r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-010000

Vuln IDs

V-213637
V-69027

Rule IDs

SV-213637r508024_rule
SV-83631

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-14859r290223_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14857r290224_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful attempts to access security objects occur.

AU-12 - Medium - CCI-000172 - V-213638 - SV-213638r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-010100

Vuln IDs

V-213638
V-69029

Rule IDs

SV-213638r508024_rule
SV-83633

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 To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-14860r290226_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14858r290227_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.

AU-12 - Medium - CCI-000172 - V-213639 - SV-213639r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-010200

Vuln IDs

V-213639
V-69031

Rule IDs

SV-213639r508024_rule
SV-83635

Changes in categorized 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-14861r290229_chk

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14859r290230_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

Audit records must be generated when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.

AU-12 - Medium - CCI-000172 - V-213640 - SV-213640r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-010300

Vuln IDs

V-213640
V-69033

Rule IDs

SV-213640r508024_rule
SV-83637

Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. 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-14862r290232_chk

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14860r290233_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when privileges/permissions are added.

AU-12 - Medium - CCI-000172 - V-213641 - SV-213641r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-010400

Vuln IDs

V-213641
V-69035

Rule IDs

SV-213641r508024_rule
SV-83639

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 REVOKE command.

Checks: C-14863r290235_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14861r290236_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful attempts to add privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-213642 - SV-213642r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-010500

Vuln IDs

V-213642
V-69037

Rule IDs

SV-213642r508024_rule
SV-83641

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 REVOKE command. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-14864r290238_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14862r290239_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when security objects are modified.

AU-12 - Medium - CCI-000172 - V-213643 - SV-213643r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-010800

Vuln IDs

V-213643
V-69039

Rule IDs

SV-213643r508024_rule
SV-83643

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-14865r290241_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14863r290242_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful attempts to modify security objects occur.

AU-12 - Medium - CCI-000172 - V-213644 - SV-213644r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-010900

Vuln IDs

V-213644
V-69041

Rule IDs

SV-213644r508024_rule
SV-83645

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. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-14866r290244_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14864r290245_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

Audit records must be generated when categorized information (e.g., classification levels/security levels) is created.

AU-12 - Medium - CCI-000172 - V-213645 - SV-213645r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011000

Vuln IDs

V-213645
V-69043

Rule IDs

SV-213645r508024_rule
SV-83647

Changes in categorized 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-14867r290247_chk

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14865r290248_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

Audit records must be generated when categorized information (e.g., classification levels/security levels) is modified.

AU-12 - Medium - CCI-000172 - V-213646 - SV-213646r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011050

Vuln IDs

V-213646
V-69087

Rule IDs

SV-213646r508024_rule
SV-83691

Changes in categorized 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-14868r290250_chk

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14866r290251_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

Audit records must be generated when unsuccessful attempts to create categorized information (e.g., classification levels/security levels) occur.

AU-12 - Medium - CCI-000172 - V-213647 - SV-213647r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011100

Vuln IDs

V-213647
V-69045

Rule IDs

SV-213647r508024_rule
SV-83649

Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. 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-14869r290253_chk

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14867r290254_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

Audit records must be generated when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.

AU-12 - Medium - CCI-000172 - V-213648 - SV-213648r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011150

Vuln IDs

V-213648
V-69089

Rule IDs

SV-213648r508024_rule
SV-83693

Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. 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-14870r290256_chk

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14868r290257_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when privileges/permissions are deleted.

AU-12 - Medium - CCI-000172 - V-213649 - SV-213649r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011200

Vuln IDs

V-213649
V-69047

Rule IDs

SV-213649r508024_rule
SV-83651

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 command.

Checks: C-14871r290259_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14869r290260_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful attempts to delete privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-213650 - SV-213650r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011300

Vuln IDs

V-213650
V-69049

Rule IDs

SV-213650r508024_rule
SV-83653

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 command. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-14872r290262_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14870r290263_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when security objects are deleted.

AU-12 - Medium - CCI-000172 - V-213651 - SV-213651r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011400

Vuln IDs

V-213651
V-69051

Rule IDs

SV-213651r508024_rule
SV-83655

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-14873r290265_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14871r290266_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful attempts to delete security objects occur.

AU-12 - Medium - CCI-000172 - V-213652 - SV-213652r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011500

Vuln IDs

V-213652
V-69053

Rule IDs

SV-213652r508024_rule
SV-83657

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-14874r290268_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14872r290269_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

Audit records must be generated when categorized information (e.g., classification levels/security levels) is deleted.

AU-12 - Medium - CCI-000172 - V-213653 - SV-213653r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011600

Vuln IDs

V-213653
V-69055

Rule IDs

SV-213653r508024_rule
SV-83659

Changes in categorized 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-14875r290271_chk

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14873r290272_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

Audit records must be generated when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.

AU-12 - Medium - CCI-000172 - V-213654 - SV-213654r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011700

Vuln IDs

V-213654
V-69057

Rule IDs

SV-213654r508024_rule
SV-83661

Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. 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-14876r290274_chk

Review the system documentation to determine whether it is required to track categorized information, such as classification or sensitivity level. If it is not, this is not applicable (NA). Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14874r290275_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when successful logons or connections occur.

AU-12 - Medium - CCI-000172 - V-213655 - SV-213655r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011800

Vuln IDs

V-213655
V-69059

Rule IDs

SV-213655r508024_rule
SV-83663

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

Checks: C-14877r290277_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_connect; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14875r290278_fix

Execute the following SQL as enterprisedb: SHOW edb_audit_connect; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding. Fix Text: Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_connect = 'all'; ALTER SYSTEM SET edb_audit_disconnect = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful logons or connection attempts occur.

AU-12 - Medium - CCI-000172 - V-213656 - SV-213656r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-011900

Vuln IDs

V-213656
V-69061

Rule IDs

SV-213656r508024_rule
SV-83665

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-14878r290280_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_connect; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14876r290281_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_connect = 'all'; ALTER SYSTEM SET edb_audit_disconnect = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records for all privileged activities or other system-level access.

AU-12 - Medium - CCI-000172 - V-213657 - SV-213657r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-012000

Vuln IDs

V-213657
V-69063

Rule IDs

SV-213657r508024_rule
SV-83667

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 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-14879r290283_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14877r290284_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.

AU-12 - Medium - CCI-000172 - V-213658 - SV-213658r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-012100

Vuln IDs

V-213658
V-69065

Rule IDs

SV-213658r508024_rule
SV-83669

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 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. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-14880r290286_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14878r290287_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records showing starting and ending time for user access to the database(s).

AU-12 - Medium - CCI-000172 - V-213659 - SV-213659r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-012200

Vuln IDs

V-213659
V-69067

Rule IDs

SV-213659r508024_rule
SV-83671

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-14881r290289_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_connect; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14879r290290_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_connect = 'all'; ALTER SYSTEM SET edb_audit_disconnect = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when concurrent logons/connections by the same user from different workstations occur.

AU-12 - Medium - CCI-000172 - V-213660 - SV-213660r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-012300

Vuln IDs

V-213660
V-69069

Rule IDs

SV-213660r508024_rule
SV-83673

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-14882r290292_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_connect; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14880r290293_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_connect = 'all'; ALTER SYSTEM SET edb_audit_disconnect = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must be able to generate audit records when successful accesses to objects occur.

AU-12 - Medium - CCI-000172 - V-213661 - SV-213661r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-012400

Vuln IDs

V-213661
V-69071

Rule IDs

SV-213661r508024_rule
SV-83675

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-14883r290295_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14881r290296_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records when unsuccessful accesses to objects occur.

AU-12 - Medium - CCI-000172 - V-213662 - SV-213662r508024_rule

RMF Control

AU-12

Severity

M

CCI

Version

PPS9-00-012500

Vuln IDs

V-213662
V-69073

Rule IDs

SV-213662r508024_rule
SV-83677

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-14884r290298_chk

Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.

Fix: F-14882r290299_fix

Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.

b

The EDB Postgres Advanced Server must generate audit records for all direct access to the database(s).

AU-12 - Medium - CCI-000172 - V-213663 - SV-213663r508024_rule

RMF Control

AU-12

Severity

M

CCI