Security depends on the deployment, access model, data scope, and operating process. FireIntel discusses those controls in the context of the implementation rather than publishing unsupported blanket claims.
At a glance
- Scope-aware security planning
- Explicit export boundaries
- A responsible reporting path
Plan controls around the data in scope
External threat intelligence may include credentials, source records, infrastructure data, third-party findings, and analyst notes. Access, retention, export, and audit requirements should reflect the sensitivity of each category and the organization’s authority to use it.
During deployment planning, teams should define tenant scope, user roles, approved workflows, evidence-retention expectations, and where exported intelligence may be stored or shared.
- Apply least-privilege access to sensitive evidence.
- Define retention and export rules before broad use.
- Keep source provenance available for review and audit.
Use record-specific export boundaries
Not every intelligence object should expose the same download action. FireIntel’s full-log ZIP control is limited to qualifying leak and stealer-log records and is not shown on unrelated result types.
Risk lists, fusion files, reports, and individual evidence views remain distinct workflows. Available controls and permissions should be confirmed for the deployment scope.
Report a potential vulnerability responsibly
Send an initial report to support@fireintel.net with a clear subject, affected surface, reproduction summary, and potential impact. Do not include passwords, personal data, raw credential collections, or unnecessary sensitive evidence in the first email.
Avoid social engineering, denial-of-service testing, destructive actions, persistence, or accessing data that does not belong to you. Wait for a coordinated handling path before sending sensitive proof. This page provides a contact route and is not a bug-bounty promise or statement of reward eligibility.