| Checked | Name | Title |
|---|
| ☐ | SV-251183r960735_rule | Redis Enterprise DBMS must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. |
| ☐ | SV-251184r960768_rule | Redis Enterprise DBMS must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. |
| ☐ | SV-251185r960792_rule | Redis Enterprise DBMS must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-251186r961317_rule | Redis Enterprise DBMS must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. |
| ☐ | SV-251187r961317_rule | Redis Enterprise DBMS must enforce access control lists, as defined by the data owner, over defined subjects and objects. |
| ☐ | SV-251188r961353_rule | Redis Enterprise DBMS must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-251189r961359_rule | Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only. |
| ☐ | SV-251190r960879_rule | Redis Enterprise DBMS must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components. |
| ☐ | SV-251191r960882_rule | Redis Enterprise DBMS must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. |
| ☐ | SV-251192r961839_rule | Redis Enterprise DBMS must generate audit records for all direct access to the database(s). |
| ☐ | SV-251195r961392_rule | Redis Enterprise DBMS must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-251196r961860_rule | Redis Enterprise DBMS must offload 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-251197r961398_rule | Redis Enterprise DBMS must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity. |
| ☐ | SV-251198r961401_rule | Redis Enterprise DBMS must provide an immediate real-time alert to appropriate support staff of all audit log failures. |
| ☐ | SV-251199r960915_rule | Redis Enterprise DBMS 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. |
| ☐ | SV-251200r960915_rule | Redis Enterprise DBMS 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-251201r961443_rule | Redis Enterprise DBMS must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT). |
| ☐ | SV-251202r960930_rule | The audit information produced by Redis Enterprise DBMS must be protected from unauthorized read access. |
| ☐ | SV-251203r960933_rule | The audit information produced by Redis Enterprise DBMS must be protected from unauthorized modification. |
| ☐ | SV-251204r960936_rule | The audit information produced by Redis Enterprise DBMS must be protected from unauthorized deletion. |
| ☐ | SV-251205r960939_rule | Redis Enterprise DBMS must protect its audit features from unauthorized access. |
| ☐ | SV-251206r960942_rule | Redis Enterprise DBMS must protect its audit configuration from unauthorized modification. |
| ☐ | SV-251207r960945_rule | Redis Enterprise DBMS must protect its audit features from unauthorized removal. |
| ☐ | SV-251208r1018617_rule | Redis Enterprise DBMS must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. |
| ☐ | SV-251209r961461_rule | Redis Enterprise DBMS must enforce access restrictions associated with changes to the configuration of Redis Enterprise DBMS or database(s). |
| ☐ | SV-251210r960960_rule | Redis Enterprise DBMS must limit privileges to change software modules; to include stored procedures, functions, and triggers, and links to software external to Redis Enterprise DBMS. |
| ☐ | SV-251211r960960_rule | Redis Enterprise DBMS software installation account must be restricted to authorized users. |
| ☐ | SV-251212r960960_rule | Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. |
| ☐ | SV-251213r960960_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 Redis Enterprise DBMS, etc.) must be restricted to authorized users. |
| ☐ | SV-251214r961863_rule | Redis Enterprise DBMS 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. |
| ☐ | SV-251215r961470_rule | Redis Enterprise DBMS 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-251217r960963_rule | Unused database components, DBMS software, and database objects must be removed. |
| ☐ | SV-251218r960963_rule | Unused database components that are integrated in Redis Enterprise DBMS and cannot be uninstalled must be disabled. |
| ☐ | SV-251219r960963_rule | Access to external executables must be disabled or restricted. |
| ☐ | SV-251220r960966_rule | Redis Enterprise DBMS 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-251221r1018618_rule | Redis Enterprise DBMS must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. |
| ☐ | SV-251222r960969_rule | Redis Enterprise DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-251223r1018619_rule | If passwords are used for authentication, Redis Enterprise DBMS must store only hashed, salted representations of passwords. |
| ☐ | SV-251224r961521_rule | Redis Enterprise DBMS must prohibit the use of cached authenticators after an organization-defined time period. |
| ☐ | SV-251225r961038_rule | Redis Enterprise DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. |
| ☐ | SV-251226r961041_rule | Redis Enterprise DBMS must enforce authorized access to all PKI private keys stored/used by Redis Enterprise DBMS. |
| ☐ | SV-251227r961044_rule | Redis Enterprise DBMS must map the PKI-authenticated identity to an associated user account. |
| ☐ | SV-251228r961047_rule | Redis Enterprise DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-251229r961050_rule | Redis Enterprise DBMS must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations. |
| ☐ | SV-251230r961053_rule | Redis Enterprise DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). |
| ☐ | SV-251231r962034_rule | Redis Enterprise DBMS must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements. |
| ☐ | SV-251232r961857_rule | Redis Enterprise DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures. |
| ☐ | SV-251233r961857_rule | Redis Enterprise DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes. |
| ☐ | SV-251234r961857_rule | Redis Enterprise DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements. |
| ☐ | SV-251235r961095_rule | Redis Enterprise DBMS must separate user functionality (including user interface services) from database management functionality. |
| ☐ | SV-251236r961095_rule | Access to the Redis Enterprise control plane must be restricted. |
| ☐ | SV-251237r961116_rule | Redis Enterprise DBMS must recognize only system-generated session identifiers. |
| ☐ | SV-251238r961119_rule | Redis Enterprise DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. |
| ☐ | SV-251239r961596_rule | Redis Enterprise DBMS must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions. |
| ☐ | SV-251240r961122_rule | Redis Enterprise DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
| ☐ | SV-251241r961125_rule | In the event of a system failure, Redis Enterprise DBMS 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-251242r961128_rule | Redis Enterprise DBMS must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-251243r1018562_rule | Redis Enterprise DBMS 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. |
| ☐ | SV-251244r1018563_rule | Redis Enterprise DBMS must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. |
| ☐ | SV-251245r961149_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-251246r961149_rule | Redis Enterprise DBMS must prevent unauthorized and unintended information transfer via shared system resources. |
| ☐ | SV-251247r961149_rule | Access to database files must be limited to relevant processes and to authorized, administrative users. |
| ☐ | SV-251248r961638_rule | Redis Enterprise DBMS must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-251249r961641_rule | Redis Enterprise DBMS must maintain the confidentiality and integrity of information during reception. |
| ☐ | SV-251250r961158_rule | Redis Enterprise DBMS and associated applications must reserve the use of dynamic code execution for situations that require it. |
| ☐ | SV-251251r961158_rule | Redis Enterprise DBMS and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack. |
| ☐ | SV-251252r961677_rule | When updates are applied to Redis Enterprise DBMS software, any software components that have been replaced or made unnecessary must be removed. |
| ☐ | SV-251253r1001008_rule | Security-relevant software updates to Redis Enterprise DBMS must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). |
| ☐ | SV-251426r960879_rule | Redis Enterprise DBMS must generate audit records for DoD-defined auditable events within all DBMS/database components. |
| ☐ | SV-251428r1018620_rule | If DBMS authentication using passwords is employed, Redis Enterprise DBMS must enforce the DOD standards for password complexity and lifetime. |
| ☐ | SV-265880r999546_rule | Redis Enterprise products must be a version supported by the vendor. |
STIGQter: STIG Summary: