[GH-ISSUE #137] [Feature Request] File Upload Flowsint Type #776

Open
opened 2026-04-24 17:47:12 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @z3rodaycve on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/137

Hello,

During my development of new Flowsint enrichers, I realized that I could really use a “File” Flowsint type, where users would be able to upload a file and use it later within enrichers.

For ex., a user could upload an output file from an earlier investigation using a third-party tool and continue their investigation in Flowsint.

Currently there are both “File” and “Document” Flowsint types, but neither of them currently allows users to upload a file.

This feature could also help finish feature request #107, but I believe it would benefit a wider range of users (myself included).

Thank you

Originally created by @z3rodaycve on GitHub (Apr 13, 2026). Original GitHub issue: https://github.com/reconurge/flowsint/issues/137 Hello, During my development of new Flowsint enrichers, I realized that I could really use a “File” Flowsint type, where users would be able to upload a file and use it later within enrichers. For ex., a user could upload an output file from an earlier investigation using a third-party tool and continue their investigation in Flowsint. Currently there are both “File” and “Document” Flowsint types, but neither of them currently allows users to upload a file. This feature could also help finish feature request #107, but I believe it would benefit a wider range of users (myself included). Thank you
Author
Owner

@dextmorgn commented on GitHub (Apr 14, 2026):

Hey @z3rodaycve,

Could you give me examples of what things you would do with the file ?

Something like a picture document, and extract exif info using an enricher ?

Basically that would involve creating a new file storage system, maybe using a minio service in the docker-compose

<!-- gh-comment-id:4244426952 --> @dextmorgn commented on GitHub (Apr 14, 2026): Hey @z3rodaycve, Could you give me examples of what things you would do with the file ? Something like a picture document, and extract exif info using an enricher ? Basically that would involve creating a new file storage system, maybe using a minio service in the docker-compose
Author
Owner

@z3rodaycve commented on GitHub (Apr 14, 2026):

Hello @dextmorgn,

I had a few ideas for enrichers. Most of the time, I would be extracting the contents of the uploaded file.
The NMAP importer idea by @johanneskolik (#107) is a good example.

I think this opens up more possibilities and functionality for Flowsint enrichers.

<!-- gh-comment-id:4244811187 --> @z3rodaycve commented on GitHub (Apr 14, 2026): Hello @dextmorgn, I had a few ideas for enrichers. Most of the time, I would be extracting the contents of the uploaded file. The NMAP importer idea by @johanneskolik (#107) is a good example. I think this opens up more possibilities and functionality for Flowsint enrichers.
Author
Owner

@dextmorgn commented on GitHub (Apr 16, 2026):

Let me clarify some points to make sure I understand:
Here is a scenario:

  • user creates a new "Document" node type (name, metadata, etc)
  • The Document form proposes for example a drop zone to add the document as blob or whatever
  • the node is inserted and the actual doc is inserted in a persistant storage (s3, minio, etc.)

In parallel, there would be document enricher, maybe compatible with extension type, like NmapDocumentParser that would extract and insert results as nodes ?

<!-- gh-comment-id:4258209824 --> @dextmorgn commented on GitHub (Apr 16, 2026): Let me clarify some points to make sure I understand: Here is a scenario: - user creates a new "Document" node type (name, metadata, etc) - The Document form proposes for example a drop zone to add the document as blob or whatever - the node is inserted and the actual doc is inserted in a persistant storage (s3, minio, etc.) In parallel, there would be document enricher, maybe compatible with extension type, like `NmapDocumentParser` that would extract and insert results as nodes ?
Author
Owner

@z3rodaycve commented on GitHub (Apr 16, 2026):

Let me clarify some points to make sure I understand:
Here is a scenario:

  • user creates a new "Document" node type (name, metadata, etc)
  • The Document form proposes for example a drop zone to add the document as blob or whatever
  • the node is inserted and the actual doc is inserted in a persistant storage (s3, minio, etc.)

In parallel, there would be document enricher, maybe compatible with extension type, like NmapDocumentParser that would extract and insert results as nodes ?

Yes, exactly something like that.

<!-- gh-comment-id:4258268266 --> @z3rodaycve commented on GitHub (Apr 16, 2026): > Let me clarify some points to make sure I understand: > Here is a scenario: > - user creates a new "Document" node type (name, metadata, etc) > - The Document form proposes for example a drop zone to add the document as blob or whatever > - the node is inserted and the actual doc is inserted in a persistant storage (s3, minio, etc.) > > In parallel, there would be document enricher, maybe compatible with extension type, like `NmapDocumentParser` that would extract and insert results as nodes ? Yes, exactly something like that.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/flowsint#776