[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 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. |