Bug / Feature Request

Work Environment

Problem Description

There are no longer any default dashboards

Possible Solutions

Add the default da

Sorry, not enough english to explain correctly, I'll try to reproduce it:

:  man tcpflow | col -b | grep scan_http
	      tcpflow -e scan_http -o outdir host sundown
: su -
Password: 
root: tcpflow -e scan_http -o outdir host example.org
Invalid scanner name 'scan_http'
root: tcpflow -e http -o outdir host example.org     
reportfilename: outdir/report.xml
tcpflow: listening on wlp

Is anyone experiencing the disappear of comments after uploading some date?
In this case after 6 mans:

Data inside is present, just the table with comments has problem, probably some js not correctly loaded.
Issue persists also restarting docker.

Work Environment

Problem Description

After updating database in Cortex, when the create adminis

Artifact output is one or more tables with column names set by the VQL itself. It is often convenient to forward artifact output to additional systems and so it would be nice to develop some naming guidelines around columns.

Additionally it would be useful to develop a minimal set of columns to output so each row can be tagged in an external system (e.g. Elastic index).

This bug is to facili

This issue helps tracking TheHive4 documentation progress

• Hardware Pre-requisites in home page (cc @To-om)
• Installation Guide (cc @jeromeleonard)
• Migration guide (cc @To-om)
• Admin Guides
  • Connectors (cc @To-om )
  • Authentication
  • Backup_restore
  • Cassandra Security
  • Culstering
  • HTTPS
• User guides
  • Quick

Describe the bug
The following analyzers are missing cortexutils:

• SpamhausDBL
• ProofPoint
• TeamCymruMHR
• Umbrella

To Reproduce
find ./analyzers -name "requirements.txt" -print -exec cat {} \;

Complementary information
The current dep. installation implementation allowed this error to slip under the radar, but containerized analyzers did not have this critical depe

Let the user define the columns / indexes of a submitted csv for such things like system_name in dfirtrack.config.

A good starting point is dfirtrack_main.importer.file.csv.systems_tags.

Hola,

I'd potentially like to use aff4 in a new project, but I'm not sure where to start.

• Where can I read the docs?
• Who's in charge?
• What policies apply? (I note my team member has made significant contributions and had to change them to conform with the notoriously C++-hostile Google C++ "Style" Guidelines. But then... it seems... the API is C++-based? So there are ABI breakage iss

I ran verify.py against all the examples in this directory, and got verification issues (terms not in case.ttl) with these files:

• Oresteia.json
• accounts.json
• bulk_extractor_forensic_path.json
• file.json
• forensic_lifecycle.json
• message.json
• multipart_file.json
• raw_data.json