Dataflow defines how customer's data should be available to Hunters.
It is built out of three key components:
- Data type - Which data should be ingested. It defines the schema to which the data should conform.
- Source - Where the data should be ingested from. Including the source identity and properties necessary to access this source, such as host address, username and relevant access keys.
- Sink - Where the data should be ingested to. By default the ingested data is stored in a secure data lake accessible only to Hunters' threat hunting machine. A sales representative would be happy to elaborate on dedicated alternatives.
All active data flows are monitored and displayed in the "Data Flows" tab in the Hunters portal, including the amount of raw data being ingested over time.