-
Notifications
You must be signed in to change notification settings - Fork 385
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
Analyzers for Valhalla and Thunderstorm #943
Conversation
Can you improve analyzer json info following this guidelines https://thehive-project.github.io/Cortex-Analyzers/analyzers_definition/ with README, logo and subscription info? thanks! |
For Thunderstom it's ok to have here in the pull. If you can provide me a temporary key I'll test it otherwise we will release it in any case without test. |
@dadokkio I cannot provide a key, but a source IP whitelisting --- or I'll send you an Email |
If you switch to update_docs branch we are working to update documentation for all analyzer: |
Ah, I just noticed that the |
Do I need that favicon.svg as well? |
I never noticed that.. so I hope not 😄 |
I've added the changes:
|
Two analyzers for our products
Valhalla is publicly accessible and can be queried with the demo key (default in configuration).
THOR Thunderstorm is a commercial on-premise web service that receives samples and returns a scan result as JSON. Some customers asked for that analyzer. Should I provide analyzers for commercial services separately in our companies repo? (https://github.com/NextronSystems/Cortex-Analyzers)
I hope I did everything right. It's the first time I submit an analyzer.
Both analyzers have been tested in a demo installation.