| Checked | Name | Title |
|---|
| ☐ | SV-98865r1_rule | 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. |
| ☐ | SV-98867r1_rule | The vROps PostgreSQL DB must provide audit record generation for DoD-defined auditable events within all DBMS/database components. |
| ☐ | SV-98869r1_rule | 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. |
| ☐ | SV-98871r1_rule | The vROps PostgreSQL DB must be able to generate audit records when privileges/permissions are retrieved. |
| ☐ | SV-98873r1_rule | The vROps PostgreSQL DB must initiate session auditing upon startup. |
| ☐ | SV-98875r1_rule | The vROps PostgreSQL DB must provide authorized users to capture, record, and log all content related to a user session. |
| ☐ | SV-98877r1_rule | The vROps PostgreSQL DB must produce audit records containing sufficient information to establish what type of events occurred. |
| ☐ | SV-98879r1_rule | The vROps PostgreSQL DB must produce audit records containing time stamps to establish when the events occurred. |
| ☐ | SV-98881r1_rule | The vROps PostgreSQL DB must produce audit records containing sufficient information to establish where the events occurred. |
| ☐ | SV-98883r1_rule | The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the sources (origins) of the events. |
| ☐ | SV-98885r1_rule | The vROps PostgreSQL DB must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. |
| ☐ | SV-98887r1_rule | 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. |
| ☐ | SV-98889r1_rule | 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. |
| ☐ | SV-98891r1_rule | 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. |
| ☐ | SV-98893r1_rule | The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized read access. |
| ☐ | SV-98895r1_rule | The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized modification. |
| ☐ | SV-98897r1_rule | The audit information produced by the vROps PostgreSQL DB must be protected from unauthorized deletion. |
| ☐ | SV-98899r1_rule | The vROps PostgreSQL DB must protect its audit features from unauthorized access. |
| ☐ | SV-98901r1_rule | The vROps PostgreSQL DB must protect its audit configuration from unauthorized modification. |
| ☐ | SV-98903r1_rule | The vROps PostgreSQL DB must protect its audit features from unauthorized removal. |
| ☐ | SV-98905r1_rule | 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. |
| ☐ | SV-98907r1_rule | 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. |
| ☐ | SV-98909r1_rule | Default demonstration and sample databases, database objects, and applications must be removed. |
| ☐ | SV-98911r1_rule | 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. |
| ☐ | SV-98913r1_rule | The vROps PostgreSQL DB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-98915r1_rule | If passwords are used for authentication, the vROps PostgreSQL DB must store only hashed, salted representations of passwords. |
| ☐ | SV-98917r1_rule | If passwords are used for authentication, the vROps PostgreSQL DB must transmit only encrypted representations of passwords. |
| ☐ | SV-98919r1_rule | The vROps PostgreSQL DB must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations. |
| ☐ | SV-98921r1_rule | 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. |
| ☐ | SV-98923r1_rule | The vROps PostgreSQL DB must isolate security functions from non-security functions. |
| ☐ | SV-98925r1_rule | vROps PostgreSQL DB contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-98927r1_rule | The vROps PostgreSQL DB must reveal detailed error messages only to the ISSO, ISSM, SA and DBA. |
| ☐ | SV-98929r1_rule | The vROps PostgreSQL DB must utilize centralized management of the content captured in audit records generated by all components of the DBMS. |
| ☐ | SV-98931r1_rule | The vROps PostgreSQL DB must provide centralized configuration of the content to be captured in audit records generated by all components of the DBMS. |
| ☐ | SV-98933r1_rule | 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. |
| ☐ | SV-98935r1_rule | The vROps PostgreSQL DB must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts. |
| ☐ | SV-98937r1_rule | 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). |
| ☐ | SV-98939r1_rule | The vROps PostgreSQL DB must generate time stamps, for audit records and application data, with a minimum granularity of one second. |
| ☐ | SV-98941r1_rule | The vROps PostgreSQL DB must enforce access restrictions associated with changes to the configuration of the DBMS or database(s). |
| ☐ | SV-98943r1_rule | 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. |
| ☐ | SV-98945r1_rule | When invalid inputs are received, the vROps PostgreSQL DB must behave in a predictable and documented manner that reflects organizational and system objectives. |
| ☐ | SV-98947r1_rule | 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). |
| ☐ | SV-98949r1_rule | The vROps PostgreSQL DB must be able to generate audit records when security objects are accessed. |
| ☐ | SV-98951r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to access security objects occur. |
| ☐ | SV-98953r1_rule | The vROps PostgreSQL DB must generate audit records when privileges/permissions are added. |
| ☐ | SV-98955r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to add privileges/permissions occur. |
| ☐ | SV-98957r1_rule | The vROps PostgreSQL DB must generate audit records when privileges/permissions are modified. |
| ☐ | SV-98959r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify privileges/permissions occur. |
| ☐ | SV-98961r1_rule | The vROps PostgreSQL DB must generate audit records when security objects are modified. |
| ☐ | SV-98963r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to modify security objects occur. |
| ☐ | SV-98965r1_rule | The vROps PostgreSQL DB must generate audit records when privileges/permissions are deleted. |
| ☐ | SV-98967r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete privileges/permissions occur. |
| ☐ | SV-98969r1_rule | The vROps PostgreSQL DB must generate audit records when security objects are deleted. |
| ☐ | SV-98971r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to delete security objects occur. |
| ☐ | SV-98973r1_rule | The vROps PostgreSQL DB must generate audit records when categories of information (e.g., classification levels/security levels) are deleted. |
| ☐ | SV-98975r1_rule | The vROps PostgreSQL DB must generate audit records when successful logons or connections occur. |
| ☐ | SV-98977r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful logons or connection attempts occur. |
| ☐ | SV-98979r1_rule | The vROps PostgreSQL DB must generate audit records for all privileged activities or other system-level access. |
| ☐ | SV-98981r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. |
| ☐ | SV-98983r1_rule | The vROps PostgreSQL DB must generate audit records showing starting and ending time for user access to the database(s). |
| ☐ | SV-98985r1_rule | The vROps PostgreSQL DB must generate audit records when concurrent logons/connections by the same user from different workstations occur. |
| ☐ | SV-98987r1_rule | The vROps PostgreSQL DB must be able to generate audit records when successful accesses to objects occur. |
| ☐ | SV-98989r1_rule | The vROps PostgreSQL DB must generate audit records when unsuccessful accesses to objects occur. |
| ☐ | SV-98991r1_rule | The vROps PostgreSQL DB must generate audit records for all direct access to the database(s). |
| ☐ | SV-98993r1_rule | The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures. |
| ☐ | SV-98995r1_rule | The vROps PostgreSQL DB must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes. |
| ☐ | SV-98997r1_rule | 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. |
| ☐ | SV-98999r1_rule | 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. |
| ☐ | SV-99001r1_rule | 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. |
STIGQter: STIG Summary: