MariaDB Enterprise 10.x Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
MariaDB 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...Rule Medium Severity -
MariaDB 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.Rule Medium Severity -
MariaDB 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...Rule Medium Severity -
MariaDB 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...Rule Medium Severity -
MariaDB 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 MariaDB lasts. This can be achieved by recording disconnections, in addition to...Rule Medium Severity -
MariaDB 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 MariaDB. Concurrent connections by the same user from multiple workstations may be valid use of the system; or such c...Rule Medium Severity -
MariaDB 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 r...Rule Medium Severity -
MariaDB 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 ...Rule Medium Severity -
MariaDB 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 ...Rule Medium Severity -
MariaDB 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. M...Rule Medium Severity
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.