Replies: 3 comments 12 replies
-
Hi, the high-level idea for that is to send a snapshot request via threatbus. The app (ie. threatbus_misp) should then translate that into a request for the historic data from MISP, and put the results back onto the bus. |
Beta Was this translation helpful? Give feedback.
-
UHmm ... If I am not wrong, snapshot option is: option snapshot_intel: interval = 0 sec &redef; Is this correct?. I did a simple test: I stopped the MISP instance, stopped the ThreatBus process on the FreeBSD host, restarted the MISP instance and the threatbus process. In ThreatBus log appears the following:
And on Zeek's reporter.log:
Which seems to me to be correct. But I have done the simple test of resolving a domain listed in MISP and ThreatBus has not taken any action ..... This IOC, without stopping the MISP instance, was detected by threatbus:
Do I need to reconfigure snapshot_option under Zeek to retrieve IOCs from the last 30 days, for example? Regards. |
Beta Was this translation helpful? Give feedback.
-
Many thanks @mavam |
Beta Was this translation helpful? Give feedback.
-
Good afternoon,
After seting up threatbus with Zeek and MISP plugins enabled and working, I have a doubt regarding how IOC's are queried by threatbus.
The IOC's that are loaded through the workers via a scheduled job, I see that they are consulted via ZeroMQ. But what happens with the rest of the IOC's stored in previous days?
I don't see that they are consulted via ThreatBus. Is it possible to query all IOC's stored in a MISP instance?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions