MarkLogic Server v9 Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
MarkLogic Server must prohibit the use of cached authenticators after an organization-defined time period.
If cached authentication information is out-of-date, the validity of the authentication information may be questionable.Rule Medium Severity -
SRG-APP-000427-DB-000385
Group -
MarkLogic 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.
Only DoD-approved external PKIs have been evaluated to ensure that they have security controls and identity vetting procedures in place sufficient for DoD systems to rely on the identity asserted i...Rule Medium Severity -
SRG-APP-000428-DB-000386
Group -
MarkLogic 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.
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 mecha...Rule High Severity -
SRG-APP-000429-DB-000387
Group -
SRG-APP-000504-DB-000355
Group -
SRG-APP-000456-DB-000390
Group -
Security-relevant software updates to MarkLogic Server 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 secur...Rule Medium Severity -
SRG-APP-000492-DB-000332
Group -
MarkLogic Server 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 speci...Rule Medium Severity -
SRG-APP-000492-DB-000333
Group -
MarkLogic Server 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 speci...Rule Medium Severity -
SRG-APP-000494-DB-000344
Group -
MarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.
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 -
SRG-APP-000494-DB-000345
Group -
SRG-APP-000495-DB-000326
Group -
MarkLogic Server 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 privileges could go undetected. Elevat...Rule Medium Severity -
SRG-APP-000495-DB-000327
Group -
MarkLogic Server 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 privileges could go...Rule Medium Severity -
SRG-APP-000495-DB-000328
Group -
MarkLogic Server 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 privileges could go undetected. Elevat...Rule Medium Severity -
SRG-APP-000495-DB-000329
Group -
MarkLogic Server 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 privileges could go...Rule Medium Severity -
SRG-APP-000496-DB-000334
Group -
MarkLogic Server 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,...Rule Medium Severity -
SRG-APP-000496-DB-000335
Group -
SRG-APP-000498-DB-000346
Group -
MarkLogic Server must generate audit records when categories of information (e.g., classification levels/security levels) are modified.
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 -
SRG-APP-000498-DB-000347
Group -
MarkLogic Server must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.
Changes in categories of 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 faile...Rule Medium Severity -
SRG-APP-000499-DB-000330
Group -
MarkLogic Server 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 privileges could go undetected. Elevat...Rule Medium Severity -
SRG-APP-000499-DB-000331
Group -
MarkLogic Server 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 privileges could go...Rule Medium Severity -
SRG-APP-000501-DB-000336
Group -
MarkLogic Server DBMS 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.Rule Medium Severity -
SRG-APP-000501-DB-000337
Group -
SRG-APP-000502-DB-000348
Group -
SRG-APP-000502-DB-000349
Group -
MarkLogic Server must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.
Changes in categories of 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 faile...Rule Medium Severity -
SRG-APP-000503-DB-000350
Group -
MarkLogic Server 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 -
SRG-APP-000503-DB-000351
Group -
MarkLogic Server 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 ...Rule Medium Severity -
SRG-APP-000504-DB-000354
Group -
SRG-APP-000506-DB-000353
Group -
MarkLogic Server 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 uses of the system, such co...Rule Medium Severity -
SRG-APP-000507-DB-000356
Group -
MarkLogic 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 r...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.