Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
MarkLogic Server must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
Description
Discussion Text
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.
This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted.
To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.
MarkLogic Server includes an auditing capability. Auditing can be enabled to capture security-relevant events to monitor suspicious database activity or to satisfy applicable auditing requirements. The generation of audit events can be configured by including or excluding MarkLogic Server roles, users, or documents based on URI. Some actions that can be audited are the following:
- Startup and shutdown of MarkLogic Server
- Adding or removing roles from a user
- Usage of amps
- Starting and stopping the auditing system
For the complete list of auditable events and their descriptions, see Auditing Events in the Administrator's Guide:
https://docs.marklogic.com/guide/admin/auditing
This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted.
To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.
MarkLogic Server includes an auditing capability. Auditing can be enabled to capture security-relevant events to monitor suspicious database activity or to satisfy applicable auditing requirements. The generation of audit events can be configured by including or excluding MarkLogic Server roles, users, or documents based on URI. Some actions that can be audited are the following:
- Startup and shutdown of MarkLogic Server
- Adding or removing roles from a user
- Usage of amps
- Starting and stopping the auditing system
For the complete list of auditable events and their descriptions, see Auditing Events in the Administrator's Guide:
https://docs.marklogic.com/guide/admin/auditing
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.