Hunt reports
A hunt report is the written account of a hunt. Scout writes it from the hunt's own evidence: its steps and results, the entities it found, and your tags, notes and investigation timeline. The template you pick sets its shape. You read it on the hunt's Report page and download it as a Word document or Markdown. For the customer, Huntbase also builds a plain customer report you can save as a PDF. When you conclude a hunt, its outcome is saved as a finding you can print or share through an expiring link.

Generate a report
- Open the report: Generate report (or Open report, once there is one) in the hunt's verdict cell, Open internal report / Go to the report tab in the Conclude sheet, or the hunt's Report tab. A concluded hunt's report stays open to anyone who can see the hunt.
- If the hunt has no report yet, the tab says No report has been generated yet. Pick a template in the Report template select. Its description and sections are shown below it.
- Optionally tick Also save a spreadsheet snapshot to keep the tracker spreadsheet as it stands, paired with this report. It's unticked by default.
- Click Generate report. The tab shows Generating report… while Scout works, usually for under a minute.
A report opens in the same scope as its hunt. If it belongs to another scope, the tab names the hunt's organization, for example This hunt belongs to Cyberdyne Systems, and offers Switch to Cyberdyne Systems. See A hunt opens in its own scope.
You can also ask Scout in the hunt's chat. See Write up a hunt with Scout.
To write the report again after the hunt has moved on, or with a different template, pick the template next to Regenerate and click Regenerate. Each run is a new version, and earlier versions are kept as they were (see Versions and snapshots). The header shows the hunt's verdict (Verdict: Confirmed, for example), when the report was generated, its version and the template it used. If generation fails, the tab says why and offers Retry, with the template picker beside it.
Choose a template
The Report template select groups templates by where they come from:
| Group | What's in it |
|---|---|
| Your organisation | Every template your organisation keeps, the default first. See Report templates. |
| From content packs | Templates provided by content packs your organisation has installed. |
| Huntbase | The templates Huntbase ships (below). |
The template used when you don't pick one is marked · Default. It's your organisation's default template if you have set one, otherwise Threat hunt report. A template that no longer parses isn't offered.
The templates Huntbase ships:
| Template | Use it for |
|---|---|
| Threat hunt report | A hypothesis-driven write-up: findings, analysis, risk, IOCs, ATT&CK mapping, watcher candidates and follow-up hunts. |
| Incident / hunt investigation report | An incident-style report built on your investigation timeline, notes and tags. It covers the attacker timeline, affected systems, compromised accounts, IOCs, containment and open questions. |
The Incident / hunt investigation report has these sections: Executive Summary, Scope and Data Sources, Timeline of Attacker Activity, Affected Systems, Compromised Accounts, Indicators of Compromise, Findings and Evidence, MITRE ATT&CK Mapping, Analyst Notes, Containment and Remediation Recommendations, Open Questions and Conclusion.
What goes into the report
Scout reads:
- the hunt's hypothesis, steps, results and verdict
- the entities it found, its tagged rows and tagged or IOC entities, and the hunt's labels
- the investigation timeline
- notes made in the hunt, on the hunt, and on the entities, endpoints and graph nodes its evidence points to
Some sections are copied from your work, not written by Scout. In the incident template, Timeline of Attacker Activity, Affected Systems, Compromised Accounts and Analyst Notes are tables built from your timeline and notes, exactly as you recorded them. Affected Systems and Compromised Accounts list the systems and accounts named on the timeline. Events marked False positive are left out. To change these tables, change the timeline or the notes and regenerate.
Tag suggestions from Scout that you haven't accepted aren't evidence, so they don't reach the report.
A section with nothing to say is left out rather than padded. A note at the foot of the report lists how many sections were omitted. Sections such as Indicators of Compromise say Not assessed and why.
Read the caveats
Before it stores a report, Huntbase checks it against the hunt's evidence. Anything that changes how you should read the report appears in an amber box above the body, headed One claim in this report needs checking or N claims in this report need checking:
| Caveat | What it means |
|---|---|
| Draft report: generated while the hunt was still open | The hunt wasn't closed. Findings, timeline and verdict may still change. Close the hunt and regenerate for the final report. |
| repeats specifics from the hypothesis that no evidence in this hunt shows, followed by unverified: and the specifics | The report restates a premise from the hypothesis as a finding, such as where a user "always" signs in from. Nothing in the hunt shows it. Check it or remove it before sharing. |
| states duration(s) not present in the evidence, followed by unverified: and the durations | A duration, such as "a 100-minute session", that Scout worked out rather than read from the data. Check the arithmetic against the timeline. |
| removed indicator(s) this hunt never observed | Scout named an IP, hash, domain or URL the hunt never saw. It was removed from the indicator list, and any mention in the prose is marked [unverified]. |
| cited node ID(s) that are not part of this hunt — removed | A citation pointed outside the hunt and was removed. |
These checks only flag. They never rewrite your timeline or tables, and nothing is removed silently.
Where the report cites a cell of the hunt, the reference is a link that opens that cell in the notebook.
Follow-up hunts and watcher candidates
Each follow-up hunt the report suggests has Hunt this, which starts a hunt with the suggestion's title and hypothesis and opens it. Each watcher candidate has Watch for this, which opens the watcher editor on Watchers with the rule filled in; the new watcher starts in Shadow. A caveat is a prompt to check the claim before you share the report. See What is checked regardless of your template.
Versions and snapshots
Every time a report is generated or regenerated, Huntbase stores it as a new version: v1, v2 and so on. A regenerate never overwrites an earlier version. Click Versions & snapshots in the report header to see them. The same list is on the report's side panel in the hunt reports list.

Versions
The Versions tab lists every version, newest first. Each one shows:
- vN of M, with Latest on the newest version and Read-only on every older one
- Draft or Final: a draft was generated while the hunt was still open
- the template it used, when it was generated and by whom
- what produced it, when Huntbase knows: Generated by hand, Regenerated, Written by Scout or On hunt close
- how many quality flags it has (see Read the caveats)
Open shows any version. An older version opens read-only, exactly as it was generated: older versions are kept for the record and can't be edited or overwritten. The download menu on each version offers Word document (.docx) and Markdown (.md), so you can send the version a stakeholder saw rather than the latest one. To change a report, regenerate it. That makes a new latest version and leaves the old ones as they were.
Snapshots
A report says what you found. The tracker spreadsheet holds the evidence behind it, and the hunt's evidence can keep changing after the report goes out. To keep the workbook that matches a report, save a snapshot. Nothing is stored unless you ask: an ordinary export is downloaded and not kept.
- Tick Also save a spreadsheet snapshot next to Generate report or Regenerate. Huntbase stores the workbook of tagged evidence when you click, labels it With report vN and pairs it with the new version.
- Or click Save snapshot now on the Snapshots tab, with an optional Label and the Contents (Tagged evidence or All results).
The Snapshots tab lists each snapshot with its label, contents, size, the report version it was taken with, when it was saved and by whom. Download gets the stored file. Delete removes it permanently after you confirm. See Snapshots for who can save, see and delete them.
Download
Download ▾ is split by audience:
| Group | Option | What you get |
|---|---|---|
| Internal report | Word document (.docx) | The report as a Word document, with its headings and tables, ready to edit or send. |
| Markdown (.md) | The same document as Markdown. | |
| For the customer | Customer report (PDF)… | Opens the customer report. |
| Evidence workbook (.xlsx)… | The tracker spreadsheet, set up for a customer. |
Download in the report header gets the latest version. To download an older one, use its download menu under Versions & snapshots.
Reports written before templates existed can only be downloaded as Markdown. For the evidence behind the report as a workbook, export the tracker spreadsheet.
Customer or shareable report
The hunt report is for your team. The customer report is a short, plain A4 report built from the hunt itself, for the people you investigated for. It's called the Shareable report if your organisation doesn't manage customers. It contains no query text, no internal notes, no Scout reasoning and no IDs. Open it from Customer report in the answer box at the top of a hunt once it has a verdict, from ⋯ › Export › Customer report…, from Download ▾ › For the customer › Customer report (PDF)…, or from the Customer copy write-up in the Conclude sheet. Once the hunt has a finding with a customer copy, Customer report (PDF)… opens that copy instead, so you share the same words everywhere.
It has these sections: the outcome and severity, Prepared for / Prepared by and the date; a headline; What happened; Affected; What we checked, each check's title with a plain result; What we found, the evidence cells with up to three rows each; Limitations, the open issues you acknowledged when you concluded; and What you need to do.
The report's facts come from the hunt's checks, not from Scout's prose: What we checked lists the searches that actually ran, where and over what period, and Limitations lists what couldn't be searched and why. When an analyst's verdict is stronger than the checks can support (for example, the hunt is concluded as Clear but a source failed), the outcome is labelled as the analyst's judgement and says that the checks alone can't rule it out, and why. If no check completed at all, the report says the outcome rests on the analyst's judgement alone.
The words follow the verdict. The headline says what the verdict means for the customer, for example Not affected. We ran 2 checks across CrowdStrike and found no trace of this activity. for Clear, Affected. We found evidence of this activity on … for Confirmed, or Not yet determined. … for Inconclusive, where the limitations are titled What we couldn't check. Benign and False positive have their own lines. On Confirmed, the default next steps never say no action is needed.
It says only what was seen. Affected appears only on a Confirmed verdict, and lists only the systems, accounts and indicators that turned up in the hunt's results, not every value the hunt or its source named. The source's own website, reference sites and the customer's own tenants are never listed as indicators. Indicators the hunt searched for become one line under What we checked, for example 2 indicators checked across CrowdStrike: none seen.
Defaults. What happened starts from the hunt report's executive summary. What you need to do starts from response actions not yet carried out, the report's recommended actions and follow-ups meant for the customer. Edit both before you send.
- Open the customer report. The dialog says what it is built from.
- Choose One page (headline, summary, what was affected, one sentence on what was checked, limitations and next steps: for a manager) or Full report (the full write-up with records).
- Check the Title, Prepared for, Prepared by, What happened and What you need to do (one per line). Prepared by starts with your organization and you, never the customer.
- Internal steps (checkpoints, approvals, reviews) and checks that never ran are left out of What we checked; the checks that didn't run are summed up in one limitations line, such as Not checked: "A" and "B". Turn on Show internal steps and checks that didn't run to list them.
- Click Save as PDF to print it to a PDF, or Copy text to paste it elsewhere. Both follow the One page / Full report choice.
If the hunt has no verdict yet, the dialog says to conclude it first. If the evidence behind the verdict is thin, the dialog warns you and the report says so.
Findings
When you conclude a hunt, Huntbase saves a finding: the outcome of the hunt as a short report you can print or share with a customer. A hunt has one finding; concluding again updates it.
The finding page
Open a finding from Open finding in the Conclude sheet, from the hunt's Linked strip, or from the Findings list. Its header shows the verdict and severity as words, the title, and who concluded it and when. The Linked strip links back to the hunt, to the entities it involved and to any active share links.
Switch between Internal and Customer copy at the top. What you print follows the one you picked.
| View | What it shows |
|---|---|
| Internal | Bottom line (your reason, with a line of counts), Evidence (each cell links to its cell in the hunt, with rows and tagged rows), Entities by role, Follow-ups with a status you can change (To do, Done, Failed, Skipped), Notes for the team (editable) and Method, with Open hunt. |
| Customer copy | Exactly what a share link shows: the customer report built from the hunt. Edit opens the customer report dialog and saves to the finding; Copy text copies it. Without one yet, it says No customer copy yet. and offers Write the customer copy. |
Print / Save as PDF prints the view you're on. The internal print adds your notes to the same layout.
Share a finding with a customer
The Share with the customer panel on the right of a finding creates read-only links to its customer copy. Write the customer copy first; until then the panel says so.
- Pick how long the link lasts under Expires after: 7, 30 or 90 days.
- Click Create link. The link is shown once, so copy it now.
- Send it to the customer. They see the customer copy with no Huntbase sign-in and no app around it, a note that it is a read-only report and when the link expires, and a print button.
The panel lists active and past links with their views and expiry. Revoke link stops a link working, after you confirm. A revoked, expired or unknown link reads This link has expired or was revoked.
Find reports
The new navigation is rolling out and may not be enabled for your organization yet.
In the new navigation, Reporting › Hunt reports lists Findings first (Verdict, Title, Hunt, Shared, Concluded; click a row to open the finding), then every hunt's report: Write-ups of concluded hunts, for your team or for a customer. The reports list has the Draft / Final and Template filters and a Verdict column. In the classic layout, the same list is Activity's Reports view. Each row's side panel shows the verdict and the report's versions.
Next steps
- Report templates: keep your organisation's own templates
- Investigation timeline: the timeline the incident report is built on
- Tracker spreadsheet: the evidence workbook, and saving snapshots of it
- Conclude a hunt: the verdict, open issues, the write-up and the finding