When a feed fails—or while developing a new feed—users often download Feed Run files to troubleshoot and understand what went wrong.
Currently, these files are automatically zipped and password protected. This design helps prevent the files from being flagged by security tools, since they may contain data that appears malicious.
However, some organizations (such as financial institutions) have strict security policies that prohibit downloading password-protected files, since they can’t be inspected by endpoint protection tools. This can make troubleshooting feeds more difficult.
We’d like to better understand how you’d prefer to handle this scenario:
-
Would you want the option to toggle password protection for Feed Run files directly from the UI?
-
Would it be more useful to view the file contents securely in-platform, without downloading them?
-
How important is this flexibility for your troubleshooting or development workflows?
-
What security or compliance considerations would you need to balance if such a feature were added?
Your feedback will help shape how ThreatQ could offer more control and visibility into Feed Run data while maintaining strong security practices.
👉 If you have a specific idea—such as an interface toggle, policy control, or in-platform viewer—please create a new Idea describing how you’d like to see this implemented.