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

Inclusion of .docm - vulnerable filetype, sure, but it's an MS Office file type? #82

Open
mcdodd opened this issue Jun 6, 2019 · 0 comments

Comments

@mcdodd
Copy link

mcdodd commented Jun 6, 2019

Over the last 8-10 days we've started seeing false-positive reports from FSRM because *.docm has been added to the filter list.

This is the Word macro-enabled document type - it's a vulnerable document type (no question), but Word provides other (policy-led) measures to control/limit that vulnerability.

Inclusion has led to false positives which undermine confidence in the notifications from the list. This, in turn, could weaken engineer resolve to check each one properly.

This 'feels' like a step beyond the objective of the filter list. *.docm files can be routinely generated/used by authorised users, whereas previously filter items have been targeted at being specific indicators of ransomware/malware.

Any chance you can change *.docm to something more specific?

While I'm here, thanks for maintaining this tool. It's invaluable.

Thanks
Matthew

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

No branches or pull requests

1 participant