[SERVER-73718] Improve audit logging coverage of dropCollection command Created: 07/Feb/23  Updated: 13/Feb/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Security Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Security
Participants:

 Description   

During SERVER-43894 is was observed that there are error locations that do not appear to have audit logging coverage, along with errors that do: there is inconsistent audit logging.

Perhaps some kind of new scope guard could be put in place to catch error throws as well as the final command reply. Instead of error by error point audit logging. It is likely worth investigating other commands for which audit logs are made, to ensure their coverage.


Generated at Thu Feb 08 06:25:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.