provide browser access to Zeek-extracted files directory (quarantined, preserved) #34
Labels
carving
Relating to carving (extraction) of files from traffic and the scanning of those files
enhancement
New feature or request
nginx
Relating to Malcolm's use of nginx
Zeek-extracted files can be preserved/"quarantined" based on scanning results, but there's not a real convenient way to get at those files.
I've added optional environment variables for a new feature:
EXTRACTED_FILE_HTTP_SERVER_ENABLE
– if set totrue
, the directory containing Zeek-extracted files will be served over HTTP at./extracted-files/
(e.g., https://localhost/extracted-files/ if you are connecting locally)EXTRACTED_FILE_HTTP_SERVER_ENCRYPT
– if set totrue
, those Zeek-extracted files will be AES-256-CBC-encrypted in anopenssl enc
-compatible format (e.g.,openssl enc -aes-256-cbc -d -in example.exe.encrypted -out example.exe
)EXTRACTED_FILE_HTTP_SERVER_KEY
– specifies the AES-256-CBC decryption password for encrypted Zeek-extracted files; used in conjunction withEXTRACTED_FILE_HTTP_SERVER_ENCRYPT
The encryption is more for safety's sake than anything (as the files may contain live malware). It's a very no-frills HTTP server. It's disabled by default.
The text was updated successfully, but these errors were encountered: