-
Notifications
You must be signed in to change notification settings - Fork 176
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
MongoDB - alerting disabled (rule) #1180
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#1142) * Fix key when retrieving string_set in Okta Stolen Session Rule * fmt
Co-authored-by: Evan Gibler <evan.gibler@panther.com>
Co-authored-by: Evan Gibler <evan.gibler@panther.com>
Co-authored-by: Evan Gibler <evan.gibler@panther.com>
…1146) * base64 rules use python funtions not regex * better alertcontext for standard_dns_base64 * command line tools as global var * regex and length checks for edge cases * new global_helper for is_base64()
Co-authored-by: Evan Gibler <evan.gibler@panther.com>
…1146) * base64 rules use python funtions not regex * better alertcontext for standard_dns_base64 * command line tools as global var * regex and length checks for edge cases * new global_helper for is_base64()
…1149) * Add GCP.IAM.serviceAccounts.getAccessToken.Privilege.Escalation rule * Add GCP.IAM.serviceAccounts.signBlob rule
* lower severity and set disabled false * lower severity and disable
* add npm install in dockerfile * Remove Python optimizations; add prettier to PATH --------- Co-authored-by: egibs <keybase@egibs.xyz>
* Update github_advanced_security_change.py Set severity of business_secret_scanning_push_protection_custom_message.disable action to HIGH Add repository_vulnerability_alerts.disable action as HIGH * fmt --------- Co-authored-by: egibs <keybase@egibs.xyz>
😱 [INFO][root]: ignoring file package-lock.json [INFO][root]: ignoring file package.json [ERROR][root]: There are packs that are potentially missing detections: mongodb.yml: MongoDB.Alerting.Disabled.Or.Deleted
<!-- thollander/actions-comment-pull-request "check-packs" --> |
akozlovets098
force-pushed
the
THREAT-253-MongoDB---alerting-disabled
branch
from
April 5, 2024 08:26
4bd302e
to
dc27082
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
MongoDB.Alerting.Disabled.Or.Deleted
rule (Jira)