[SERVER-3203] Prevent change of profile level at runtime Created: 05/Jun/11  Updated: 03/Sep/11  Resolved: 03/Sep/11

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 1.8.1
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Alvin Richards (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Problem:
Profiling can be changed dynamically at runtime. However there are use cases when this need to be defined as a startup parameter and cannot be changed.

Use Case:
Jim is a security and compliance officer for Mega Corp. All operations that are executed against the financial database need to be logged for audit, compliance, fraud detection and other reasons. Jim need to enforce this policy and therefore wants to startup each mongodb with the shell equivalent of db.setProfilingLevel(2). However, to prevent a DBA from changing this level (and taking the database out of compliance), changing this level should be prevented through the shell and from a connected client.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 03/Sep/11 ]

profile shouldn't be used for auditing

Generated at Thu Feb 08 03:02:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.