You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I originally downloaded the training VM to test. Now tested, I've manually built a hive/cortex instance using Ubuntu 16.04 and the latest version of Cortex (2.1.3-1) and theHive (3.2.1-1).
The issue is different analyzer results between manually built instance and trainingVM.
Steps to Reproduce
When I submit an example IP (111[.]230[.]247[.]243) to the training VM I get these results:
When I submit the same IP to the manually built Ubuntu instance I get these results:
Also, the tags are populating automatically within the observable. I have to click on the Observable tab (which shows me all observables) to then watch the tags come rolling in.
Also, when I click on an observable that has reported something I don't see to report at the bottom beneath the analyzers list like this (screenshot from the working VM. I see nothing in the Ubuntu instance):
The text was updated successfully, but these errors were encountered:
Request Type
Bug
Work Environment
N/A
Description
I originally downloaded the training VM to test. Now tested, I've manually built a hive/cortex instance using Ubuntu 16.04 and the latest version of Cortex (2.1.3-1) and theHive (3.2.1-1).
The issue is different analyzer results between manually built instance and trainingVM.
Steps to Reproduce
When I submit an example IP (111[.]230[.]247[.]243) to the training VM I get these results:
When I submit the same IP to the manually built Ubuntu instance I get these results:
Also, the tags are populating automatically within the observable. I have to click on the Observable tab (which shows me all observables) to then watch the tags come rolling in.
Also, when I click on an observable that has reported something I don't see to report at the bottom beneath the analyzers list like this (screenshot from the working VM. I see nothing in the Ubuntu instance):
The text was updated successfully, but these errors were encountered: