Focused crawls are collections of frequently-updated webcrawl data from narrow (as opposed to broad or wide) web crawls, often focused on a single domain or subdomain.
For consumers of Zeek logs it's handy to have a way to understand the name/goal of the produced logs, what are each log's column names, types, and meaning, etc. Examples of such consumption tasks are
auto-generating docs / cheatsheets
understanding differences in generated logs between Zeek versions, installations, or loaded package sets
It would be nice to have some documentation on search operators and what are some of the common fields to search on (e.g. data_type, event_identifier, etc.). Also probably want to mention partial word matches requires globbing characters, etc.
I was wondering the benefit of using Modular File Management vs Single Config File Management? Why do you consider it easier to use multiple files and then compile? Trying to figure out what the best case is for my use case. Thanks. #
Diffy is a triage tool used during cloud-centric security incidents, to help digital forensics and incident response (DFIR) teams quickly identify suspicious hosts on which to focus their response.
Right now a lot of the logging from the tasks does not get propagated back to the user, so we should make sure that all of the tasks are adding logs and errors to the results so that at minimum the data gets put into the worker-log.txt. Ideally we would store this info in datastore so that the clients could query it later (this part is in #115).
For consumers of Zeek logs it's handy to have a way to understand the name/goal of the produced logs, what are each log's column names, types, and meaning, etc. Examples of such consumption tasks are