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

How should false positives be reported when they occur? #7

Open
rickyboone opened this issue Dec 22, 2022 · 0 comments
Open

How should false positives be reported when they occur? #7

rickyboone opened this issue Dec 22, 2022 · 0 comments

Comments

@rickyboone
Copy link

We have a signature (TwinWave.EvilPDF.QakySoWaky.221221) that is likely hitting too many legitimate files to keep enabled in our use case. I'm aware of the process for debugging (for the most part) and adding signatures to an internally maintained false positive list, however for the developers/maintainers of the signatures, what process is preferred for reporting them?

I know this can be a bit of a can of worms, but I didn't want to assume how it should be handled upstream.

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