-
Notifications
You must be signed in to change notification settings - Fork 381
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
FortiGuard URL: taxonomy is too rigid #295
Comments
Thanks @srilumpa for raising this valid issue. @jeromeleonard or @3c7 will look into it when they have some time. However, we won't make the taxonomy adjustable before Cortex 2.2+. This feature is indeed important but it will need some serious work on our side. |
the pb resides in the analyzer. Need to select Fortiguard Categories (https://fortiguard.com/webfilter/categories) and tell for everyone which is "suspicious", "malicious", "info" or "safe", and update the code with something like this:
Maybe there are other categories. |
I have submitted the PR #296 which implement the logic your are describing, but basing the malicious and suspicious categories on two multi-values fields in the configuration of the analyzer. |
thank you @srilumpa, will look at it. |
Request Type
Analyzer / Bug (Feature?)
Work Environment
Description
When categorizing URL or domains, the taxonomy used against some categories does not show as suspicious or malicious when they seem they are
Steps to Reproduce
Possible Solutions
Allow customization of taxonomy level by the Cortex organization admins instead of having it hard-coded in the analyzer.
The text was updated successfully, but these errors were encountered: