Details
Audit records can be generated from various components within the information system, such as network interfaces, hard disks, modems, etc. From an application perspective, certain specific application functionalities may be audited as well.
The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records (i.e., auditable events, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked).
Organizations may define the organizational personnel accountable for determining which application components shall provide auditable events.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Configure the SharePoint server configuration to allow designated organizational personnel to select which auditable events are to be audited by specific components of the system.
Navigate to Central Administration.
Click ‘Monitoring’.
Click ‘Configure Diagnostic Logging’.
Select the event categories and trace levels to match those defined by the organization’s system security plan.
Remember that a base set of events is always audited.
Click ‘Ok’.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Windows.
References
- 800-53|AU-12b.
- CAT|II
- CCI|CCI-000171
- Rule-ID|SV-223247r612235_rule
- STIG-ID|SP13-00-000055
- STIG-Legacy|SV-74383
- STIG-Legacy|V-59953
- Vuln-ID|V-223247