Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add MongoDB.Logging.Toggled rule #1203

Merged
merged 1 commit into from
Apr 9, 2024
Merged

Add MongoDB.Logging.Toggled rule #1203

merged 1 commit into from
Apr 9, 2024

Conversation

melenevskyi
Copy link
Contributor

@melenevskyi melenevskyi commented Apr 9, 2024

Goal

Detect when audit logging is changed.

Categorization

https://attack.mitre.org/techniques/T1562/008/

Strategy Abstract

Looks for MongoDB Atlas events indicating logging settings have been enabled/disabled.

Technical Context

Disable audit settings to generate relevant events.

Blind Spots and Assumptions

Assumes proper MongoDB Atlas logging. Atlas logs do not indicate whether the logging change was enabled or disabled.

False Positives

Could be legitimate administrative activity

Validation

Disable audit settings to generate alerts.

Priority

Medium

Response

Re-enable audit logging

Additional Resources

https://www.mongodb.com/docs/v4.2/tutorial/configure-auditing/

https://www.mongodb.com/docs/atlas/database-auditing/

@melenevskyi melenevskyi requested review from a team April 9, 2024 08:38
@arielkr256 arielkr256 merged commit 918fa2a into release Apr 9, 2024
5 checks passed
@arielkr256 arielkr256 deleted the threat-252 branch April 9, 2024 14:05
egibs pushed a commit that referenced this pull request Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants