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

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

Details

Version / Release: V1R1

Published: 2018-10-11

Updated At: 2018-11-03 10:31:53

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-98865r1_rule VROM-PG-000005 CCI-000054 MEDIUM The vROps PostgreSQL DB must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. Database management includes the ability to control the number of users and user sessions utilizing a DBMS. Unlimited concurrent connections to the DBMS could allow a successful Denial of Service (DoS) attack by exhausting connection resources; and a syst
    SV-98867r1_rule VROM-PG-000025 CCI-000169 MEDIUM The vROps PostgreSQL DB must provide audit record generation for DoD-defined auditable events within all DBMS/database components. Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the
    SV-98869r1_rule VROM-PG-000030 CCI-000171 MEDIUM The vROps PostgreSQL DB must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events. Suppression of auditing could permit an adversary to evad
    SV-98871r1_rule VROM-PG-000035 CCI-000172 MEDIUM The vROps PostgreSQL DB must be able to generate audit records when privileges/permissions are retrieved. 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.
    SV-98873r1_rule VROM-PG-000045 CCI-001464 MEDIUM The vROps PostgreSQL DB must initiate session auditing upon startup. Session auditing is for use when a user's activities are under investigation. To be sure of capturing all activity during those periods when session auditing is in use, it needs to be in operation for the whole time the DBMS is running.
    SV-98875r1_rule VROM-PG-000050 CCI-001462 MEDIUM The vROps PostgreSQL DB must provide authorized users to capture, record, and log all content related to a user session. Without the capability to capture, record, and log all content related to a user session, investigations into suspicious user activity would be hampered. Typically, this DBMS capability would be used in conjunction with comparable monitoring of a user's
    SV-98877r1_rule VROM-PG-000055 CCI-000130 MEDIUM The vROps PostgreSQL DB must produce audit records containing sufficient information to establish what type of events occurred. 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 respon
    SV-98879r1_rule VROM-PG-000060 CCI-000131 MEDIUM The vROps PostgreSQL DB must produce audit records containing time stamps to establish when the events occurred. 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 ri
    SV-98881r1_rule VROM-PG-000065 CCI-000132 MEDIUM The vROps PostgreSQL DB must produce audit records containing sufficient information to establish where the events occurred. 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 r
    SV-98883r1_rule VROM-PG-000070 CCI-000133 MEDIUM The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the sources (origins) of the events. 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
    SV-98885r1_rule VROM-PG-000075 CCI-000134 MEDIUM The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. 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
    SV-98887r1_rule VROM-PG-000080 CCI-001487 MEDIUM The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. 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
    SV-98889r1_rule VROM-PG-000085 CCI-000135 MEDIUM The vROps PostgreSQL DB must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject. 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 nee
    SV-98891r1_rule VROM-PG-000095 CCI-000140 LOW The vROps PostgreSQL DB must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records. 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 c
    SV-98893r1_rule VROM-PG-000105 CCI-000162 MEDIUM The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized read access. 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
    SV-98895r1_rule VROM-PG-000110 CCI-000163 MEDIUM The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized modification. 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 applica
    SV-98897r1_rule VROM-PG-000115 CCI-000164 MEDIUM The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized deletion. 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 applica
    SV-98899r1_rule VROM-PG-000120 CCI-001493 MEDIUM The vROps PostgreSQL DB must protect its audit features from unauthorized access. 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 applicatio
    SV-98901r1_rule VROM-PG-000125 CCI-001494 MEDIUM The vROps PostgreSQL DB must protect its audit configuration from unauthorized modification. 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
    SV-98903r1_rule VROM-PG-000130 CCI-001495 MEDIUM The vROps PostgreSQL DB must protect its audit features from unauthorized removal. 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
    SV-98905r1_rule VROM-PG-000150 CCI-001499 MEDIUM vROps PostgreSQL DB objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by vROps PostgreSQL DB principals authorized for ownership. 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 w
    SV-98907r1_rule VROM-PG-000155 CCI-001499 MEDIUM The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the vROps PostgreSQL DB, etc.) must be restricted to authorized users. 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 qua
    SV-98909r1_rule VROM-PG-000160 CCI-000381 MEDIUM Default demonstration and sample databases, database objects, and applications must be removed. 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 det
    SV-98911r1_rule VROM-PG-000180 CCI-000382 MEDIUM The vROps PostgreSQL DB must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. 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 po
    SV-98913r1_rule VROM-PG-000185 CCI-000764 MEDIUM The vROps PostgreSQL DB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). 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 org
    SV-98915r1_rule VROM-PG-000190 CCI-000196 MEDIUM If passwords are used for authentication, the vROps PostgreSQL DB must store only hashed, salted representations of passwords. 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 i
    SV-98917r1_rule VROM-PG-000195 CCI-000197 MEDIUM If passwords are used for authentication, the vROps PostgreSQL DB must transmit only encrypted representations of passwords. 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 protec
    SV-98919r1_rule VROM-PG-000220 CCI-000803 HIGH The vROps PostgreSQL DB must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations. 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 correc
    SV-98921r1_rule VROM-PG-000255 CCI-001665 MEDIUM In the event of a system failure, the vROps PostgreSQL DB must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes. Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of th
    SV-98923r1_rule VROM-PG-000265 CCI-001084 MEDIUM The vROps PostgreSQL DB must isolate security functions from non-security functions. 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 en
    SV-98925r1_rule VROM-PG-000270 CCI-001090 MEDIUM vROps PostgreSQL DB contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. 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 specifi
    SV-98927r1_rule VROM-PG-000305 CCI-001314 MEDIUM The vROps PostgreSQL DB must reveal detailed error messages only to the ISSO, ISSM, SA and DBA. 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 ext
    SV-98929r1_rule VROM-PG-000355 CCI-001844 MEDIUM The vROps PostgreSQL DB must utilize centralized management of the content captured in audit records generated by all components of the DBMS. 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 con
    SV-98931r1_rule VROM-PG-000360 CCI-001844 MEDIUM The vROps PostgreSQL DB must provide centralized configuration of the content to be captured in audit records generated by all components of the DBMS. 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 mu
    SV-98933r1_rule VROM-PG-000370 CCI-001855 MEDIUM The vROps PostgreSQL DB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity. 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 tra
    SV-98935r1_rule VROM-PG-000375 CCI-001858 MEDIUM The vROps PostgreSQL DB must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts. 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 operatio
    SV-98937r1_rule VROM-PG-000380 CCI-001890 MEDIUM The vROps PostgreSQL DB must record time stamps, in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT). If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the DBMS must include date and time. Time is commonly expressed in Coordinated Universal Time (UTC),
    SV-98939r1_rule VROM-PG-000385 CCI-001889 MEDIUM The vROps PostgreSQL DB must generate time stamps, for audit records and application data, with a minimum granularity of one second. Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the DBMS must include date and time. Granularity of time measurements refers to the precision availabl
    SV-98941r1_rule VROM-PG-000395 CCI-001813 MEDIUM The vROps PostgreSQL DB must enforce access restrictions associated with changes to the configuration of the DBMS or database(s). 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 c
    SV-98943r1_rule VROM-PG-000405 CCI-001762 MEDIUM The vROps PostgreSQL DB must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance. Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.
    SV-98945r1_rule VROM-PG-000455 CCI-002754 MEDIUM When invalid inputs are received, the vROps PostgreSQL DB must behave in a predictable and documented manner that reflects organizational and system objectives. 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 cau
    SV-98947r1_rule VROM-PG-000465 CCI-002605 HIGH Security-relevant software updates to the vROps PostgreSQL DB must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs). 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 contract
    SV-98949r1_rule VROM-PG-000470 CCI-000172 MEDIUM The vROps PostgreSQL DB must be able to generate audit records when security objects are accessed. 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, typ
    SV-98951r1_rule VROM-PG-000475 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to access security objects occur. 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, typ
    SV-98953r1_rule VROM-PG-000490 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when privileges/permissions are added. 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 t
    SV-98955r1_rule VROM-PG-000495 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to add privileges/permissions occur. 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 environm
    SV-98957r1_rule VROM-PG-000500 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when privileges/permissions are modified. 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 t
    SV-98959r1_rule VROM-PG-000505 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify privileges/permissions occur. Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict individuals' and groups' privileges could go undetected. In PostgreSQL envi
    SV-98961r1_rule VROM-PG-000510 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when security objects are modified. 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 u
    SV-98963r1_rule VROM-PG-000515 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify security objects occur. 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 u
    SV-98965r1_rule VROM-PG-000530 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when privileges/permissions are deleted. 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 t
    SV-98967r1_rule VROM-PG-000535 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete privileges/permissions occur. 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 environm
    SV-98969r1_rule VROM-PG-000540 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when security objects are deleted. 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.
    SV-98971r1_rule VROM-PG-000545 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete security objects occur. 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
    SV-98973r1_rule VROM-PG-000550 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when categories of information (e.g., classification levels/security levels) are deleted. Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categoriz
    SV-98975r1_rule VROM-PG-000560 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when successful logons or connections occur. For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.
    SV-98977r1_rule VROM-PG-000565 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful logons or connection attempts occur. 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 capture
    SV-98979r1_rule VROM-PG-000570 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records for all privileged activities or other system-level access. 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 consider
    SV-98981r1_rule VROM-PG-000575 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. 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 consider
    SV-98983r1_rule VROM-PG-000580 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records showing starting and ending time for user access to the database(s). 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 m
    SV-98985r1_rule VROM-PG-000585 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when concurrent logons/connections by the same user from different workstations occur. 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 re
    SV-98987r1_rule VROM-PG-000590 CCI-000172 MEDIUM The vROps PostgreSQL DB must be able to generate audit records when successful accesses to objects occur. 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
    SV-98989r1_rule VROM-PG-000595 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records when unsuccessful accesses to objects occur. 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 o
    SV-98991r1_rule VROM-PG-000600 CCI-000172 MEDIUM The vROps PostgreSQL DB must generate audit records for all direct access to the database(s). In this context, direct access is any query, command, or call to the DBMS that comes from any source other than the application(s) that it supports. Examples would be the command line or a database management utility program. The intent is to capture all
    SV-98993r1_rule VROM-PG-000605 CCI-002450 HIGH The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-98995r1_rule VROM-PG-000610 CCI-002450 HIGH The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-98997r1_rule VROM-PG-000615 CCI-002450 HIGH The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-98999r1_rule VROM-PG-000620 CCI-001851 MEDIUM The vROps PostgreSQL DB must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems. Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. The DBMS may write audit records to database tables, to fil
    SV-99001r1_rule VROM-PG-000625 CCI-000366 MEDIUM The vROps PostgreSQL DB must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs. Configuring the DBMS to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture