-
Notifications
You must be signed in to change notification settings - Fork 103
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
CryptoBlocker FSRM rules alert on its own files #7
Comments
Here is a patch that should resolve the issue.
|
m-dwyer
pushed a commit
that referenced
this issue
Aug 26, 2016
…_alert_on_its_own_files Issue #7 - crypto blocker fsrm rules alert on its own files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CryptoBlocker's current ruleset includes a rule to look for and alert when files matching
*crypt*
are found. This causes problems in the following scenarios:In both cases, the current ruleset appears to trigger based on the rule
*crypt*
. A possible solution might be to create an exclusion rule for these specific files.The text was updated successfully, but these errors were encountered: