Digital Forensics and Incident Response
MISP connects forensic observations to threat intelligence and turns reviewed findings into scoped hunting and response inputs. Use it to preserve the context of selected evidence, compare observations across investigations, document analytical judgments, and exchange useful indicators with responders. Acquire disk images, memory and endpoint collections with the appropriate forensic tools; retain the authoritative evidence and chain of custody in the case’s evidence repository. MISP holds the selected intelligence and its provenance, rather than replacing that repository or a case-management system.
Worked examples cover selected Windows findings, Active Directory replication metadata, a Sleuth Kit filesystem timeline and a DNS/HTTP packet capture. It also covers memory, endpoint, network, email, mobile and cloud investigations, and provides a complete source inventory of candidate misp-modules across import, expansion, export and action families.
The screenshots show the running MISP 3.0.0 interface from 3.0_wip commit 99ebee729, with the light theme and a site-administrator account in an isolated documentation instance. The Windows finding is synthetic: it does not demonstrate an intrusion or execution of Hayabusa against real EVTX evidence. The Windows, filesystem and PCAP exercises retain their recorded misp-modules revision d7ec3654. The ADTimeline exercise and updated inventory follow commit f4899ad4, which includes the new importer merged in PR #1141. MISP and misp-modules have separate release cycles; check your service’s GET /modules, dependencies, object templates and organization permissions before using a listed module.
Place MISP in the investigation
Begin with a specific question, such as whether an unusual service logon relates to a known incident. Record the case identifier, source system, evidence reference, collector/tool versions, relevant time window and the question’s scope. Select a manageable set of findings from the forensic tool rather than uploading an entire case by default.
| Investigation stage | MISP contribution | Preserve alongside the observation |
|---|---|---|
| Preparation | Agree on object templates, audience, module services and output consumers. | Evidence retention, authorized collection scope, handling rules and tool versions. |
| Collection and triage | Import selected exported results, artifacts or a bounded capture. | Source export hash, underlying evidence reference, host/device identity and collection method. |
| Analysis and scoping | Inspect occurrences, enrich selectors, compare timelines and record competing explanations. | Source time semantics, provider query time, confidence and the evidence supporting each conclusion. |
| Containment and eradication | Supply reviewed indicators, queries or lists to the chosen responder/tool. | Intended scope, approval, expiry, deployment receipt and rollback/removal procedure. |
| Recovery and improvement | Record sightings and negative results, reassess selectors and update detection content. | Search coverage, execution times, false-positive decisions and remaining gaps. |
An indicator match is a lead. A rule title, antivirus label, sandbox score or imported unreviewed detection is not an analyst-confirmed conclusion. Use Analyst Data and Event Reports to explain what the evidence establishes, alternative explanations and what still needs checking.
Preserve evidence and time semantics
Use an organization-only, unpublished event while building the investigation. Add the case/evidence reference and a concise question to its report, and apply the actual handling markings and distribution required by your organization. An unpublished event can still be visible to users allowed by its distribution; publication and access control are separate settings. Tags describe handling and context, while distribution and sharing groups control MISP access. See Sharing before changing the audience.
Keep three kinds of information distinct:
- Source evidence: the original image, EVTX, PCAP, collection or export, its integrity hash and evidence-system reference.
- Recorded observation: a row or object with source record identifiers, host/device/sensor context, raw fields and the meaning of its timestamps.
- Analytical conclusion: an assessment supported by identified observations, with confidence and review status.
The hash of findings.jsonl identifies that export’s bytes; it does not verify the Security.evtx path mentioned inside it. Likewise, a memory-results hash is distinct from the memory-image hash, and an EVE/Zeek log hash is distinct from a capture hash. Preserve the original export outside MISP when needed, even if a module also attaches it. Attaching data to MISP subjects those bytes to the event’s access and retention arrangements.
Preserve timezone, epoch unit, precision and timestamp meaning. Use observation times for activity timelines, collection times for collection, and provider lookup times for enrichment. MISP’s modification timestamp, event date and import time do not establish when the underlying activity happened. Missing or ambiguous times should remain unresolved until a source supplies the missing context.
Several dedicated DFIR importers below deliberately set IDS off and correlation disabled, even on hashes and IPs. This preserves unreviewed evidence without treating every extracted value as a detection selector. Promote a validated selector deliberately, keeping a reference to its source observation; do not enable correlation or IDS across every imported field. Other importers have their own defaults, so inspect the preview rather than assuming this behavior is universal.
Import selected Windows findings in MISP 3.0
The example JSONL contains one fictional Hayabusa-shaped finding for workstation.example. It reports Windows Event ID 4624, record 42, with service logon type 5 at 15 November 2026, 09:20 UTC. Successful service logons can be routine; the example’s informational severity and test rule status supply context, not a malicious verdict.
Select and review an import
An administrator must make the module service reachable, enable import services and enable evtx_findings_import for the intended users. The Modules chapter describes service discovery and configuration. In the event, choose Import from (shown as Import in the compact action bar), then Evtx Findings Import, the displayed name of the evtx_findings_import module in this interface. Upload the selected export and run the import to reach MISP’s review screen.
The importer accepts Hayabusa JSON object streams, JSON/JSONL and supported CSV timelines, or Chainsaw hunt JSON/JSONL. It imports detection output; it neither parses EVTX binaries nor runs the producer. Keep rule ID, provider, channel, event/record IDs and EVTX reference in the producer’s export when available. For example, Hayabusa’s available profiles and command names depend on its version; follow the importer’s version-specific guide.
Check the source filename/hash, observation time, host and record identifier, rule metadata, raw fields, references and IDS settings before saving. The module response also exposes summary and warnings; the MISP import screen may not display these supplementary fields. Inspect the service response when checking skipped, unmapped or ambiguous fields, and treat an error JSON field as a failed import even if HTTP status is 200.
Keep the finding connected to its source
Saving this example creates three objects: a source file, a windows-event-log-detection and a windows-event-log-record. The original JSONL is attached to the source file, whose SHA-256 and size identify the export. The detection preserves rule metadata and starts as unreviewed; the event record preserves the reported Windows event context. Their references retain the source-to-result associations returned by the module.
Open the event context and inspect record 42 in the original evidence through the case’s forensic tools. Compare the account, process, service configuration and surrounding logons before deciding whether further collection is justified. An exported path is a reference, not a file MISP has acquired or authenticated.
Record the conclusion separately in an Event Report: what was checked, why it matters, what remains uncertain and the next action. Only selectors supported by that review should become hunting or detection inputs. The example remains organization-only and unpublished, with every imported attribute non-IDS and non-correlating.
Choose the right evidence importer
The dedicated importers below consume selected results rather than performing acquisition. Their detailed input contracts matter: a filename extension alone does not establish that a producer’s schema is supported. The complete module inventory at the end of this chapter links to each handler at the reviewed revision.
| Module | Accepted evidence exchange | DFIR use and important boundary |
|---|---|---|
evtx_findings_import |
Hayabusa JSON streams, JSON/JSONL or supported CSV; Chainsaw hunt JSON/JSONL. | Preserve rule matches and linked Windows event context. EVTX binaries and Chainsaw search/dump output are outside its detection contract. |
adtimeline_import |
Native ADTimeline semicolon-delimited timeline_*.csv, with required DN, attribute and last-originating-change fields. |
Preserve unreviewed AD replication metadata, linked-value times and source bytes. Does not connect to AD, execute PowerShell, import ADobjects XML or identify the modifying actor. |
volatility3_import |
Native Volatility 3 JSON/JSONL, including nested renderer rows; explicit plugin identity required. | Supported Windows process, command-line, socket, malfind and YARA result mappings. Does not read memory images, execute plugins or cover every Volatility plugin. |
velociraptor_import |
Offline JSON/JSONL/CSV result tables with artifact/source identity and collection context. | Map supported process, service, netstat and file artifacts; preserve other rows as source results. Does not run VQL, contact a server or import collection ZIPs. |
osquery_import |
Native event/batch differential logs and snapshot JSON/JSONL; explicit context for ad-hoc rows. | Preserve host/query identity, execution time, additions/removals and export source maps. Does not execute SQL or infer a no-match result from silence. |
timesketch_import |
Selected Timesketch API/CLI/OpenSearch JSON, JSONL or CSV; selected Plaso psort -o json_line. |
Preserve source IDs, timestamps, annotations and raw events. Does not read native .plaso storage or turn source labels into MISP verdicts. |
autopsy_import |
Autopsy selected-row CSV or the explicit misp-forensic-selected version 1 JSON interchange. |
Browser/download, communication and installed-application artifacts with case/device provenance. The interchange supports adapters for mobile parsers; native UFED, Magnet, XRY or Oxygen report support is not claimed. |
zeek_import |
Selected native JSON/JSONL or ASCII/TSV with required Zeek headers. | Preserve network observations, connection context, UIDs and source-provided Community IDs. JSON needs explicit stream context when _path is absent. Does not run Zeek. |
suricata_import |
Selected EVE JSON/JSONL, optionally filtered by event type and flow ID. | Retain alerts, flow/protocol observations and native identifiers. Does not run a sensor, retrieve rules or equate an alert with compromise. |
pcap_import |
Bounded PCAP/PCAPNG, processed locally with TShark 4.0 or newer. | Preserve capture/flow provenance and reconstruct supported HTTP/email content when available. Encrypted or incomplete transfers limit reconstruction; it is a parser, not a traffic collector. |
Memory and endpoint scoping
For Volatility results, supply the producing plugin, framework/plugin versions and image name/hash when known. The supported mappings include windows.pslist.PsList, windows.psscan.PsScan, windows.pstree.PsTree, windows.cmdline.CmdLine, windows.netscan.NetScan, windows.netstat.NetStat, supported malfind paths, windows.vadyarascan.VadYaraScan and yarascan.YaraScan. Keep physical/virtual offsets, raw columns and row hierarchy; a PID alone cannot identify a process across images or runs. Malfind suspicion and a YARA match both require review.
For Velociraptor, retain deployment/client/flow/hunt identifiers as well as host and artifact name. An analyst-supplied default for one client or collection must not overwrite the identity of a multi-host export. For osquery, preserve the exporter-generated sources map so a scheduled query can be traced back to its originating MISP event, object and attribute. The importer cannot recover those references from a hashed query name alone.
Active Directory analysis with ADTimeline
Use ANSSI-FR’s ADTimeline when the question concerns changes to directory permissions, privileged group membership, delegation, Group Policy or other collected directory objects. ADTimeline reads replication metadata and exports a partial timeline of last changes to replicated attributes, with linked-value history where available. It can provide useful leads when event-log coverage is incomplete, but it does not reconstruct every intervening change or establish that a change was malicious. The new adtimeline_import module brings selected native CSV records into MISP as ad-replication-metadata objects, linked to an attached source file.
Collect and select the directory evidence
Run ADTimeline separately, following its Windows prerequisites and online/offline collection instructions. Record the ADTimeline version, collection time, domain/forest scope, queried server, collection privileges and any omitted or inaccessible objects. For an offline directory database, retain its image/database and transaction-log provenance alongside the analysis-copy reference. The MISP module reads the supplied export locally; it performs no LDAP queries, remote retrieval or PowerShell execution.
Preserve the original timeline_<domain>.csv, collection log and separate ADobjects_*.xml / gcADobjects_*.xml inventories in the evidence repository. The importer accepts the timeline CSV only, not those XML inventories, Splunk search exports or an ntds.dit database. Select records that answer a bounded question, and retain the original export reference and selection method alongside the uploaded slice’s hash. The reviewed handler accepts at most 10 MiB and 1,000 data records per import; split larger exports at CSV-record boundaries, preserving the header and quoting. Native CSV uses a semicolon delimiter and supports quoted/multiline values; UTF-8 with or without a BOM and BOM-marked UTF-16 are accepted. Each record needs DN, pszAttributeName and ftimeLastOriginatingChange; unknown columns remain in raw-record.
This selected teaching CSV contains the first two data records of the module project’s PowerShell-serialized synthetic fixture. Its BOM, quoting and retained records are byte-preserved; no live AD collection took place. The question is: what does this slice establish about an ACL-related change and a removed group-membership link, and what evidence is still needed? The example provenance records the selection, source hashes, module revision and live MISP checks.
Import and inspect the replication metadata
An administrator must install the current service with PyMISP, enable import services and enable adtimeline_import for the intended users. The handler bundles the ad-replication-metadata template for parsing; also ensure the MISP instance recognizes that template before saving. For these screenshots, the unchanged bundled version 1 definition was registered in the isolated MISP instance, alongside its existing file template version 25. See the ADTimeline import contract for the complete limits and field mappings.
Create an organization-only, unpublished event, choose Import → Adtimeline Import, and upload timeline_selected.csv. Set domain_scope to example.test and collection_server to dc02.example.test, then choose Run Adtimeline Import. These optional fields describe the collection context: the module does not infer a domain by splitting a distinguished name. Only apply a shared collection-server value when it is valid for all records in the supplied slice.
The real review contains three objects and 53 attributes: one source file and two replication-metadata observations. Each observation has a derived-from reference to the source, a one-based CSV data-record index, the source SHA-256, all raw column values and an initial unreviewed status. The index counts CSV records, not physical text lines, which matters for multiline values. All returned attributes have IDS matching and correlation disabled; keep these settings while reviewing the evidence. The service response reports two records and no warnings for this fixture; consult summary, warnings and any error in the API response when validating other exports.
Before saving, compare the source digest, affected DN, replicated attribute, raw and normalized times, linked DN, server context and counters with the source export. Saving this fixture preserves the 1,183-byte CSV attachment byte-for-byte, including its BOM and line endings; downloading it reproduces SHA-256 ddc6daef55bd41ef0256e20b2354aaa2800d9eb8a99aff5d83adcc6ef820def7. The recorded module response comes from a separate API run with the same filename, bytes and context; its stable object UUIDs match the saved example. Stable identities do not by themselves establish how every MISP import path will handle a repeated submission; inspect the destination before importing again.
Analyze changes and corroborate the conclusion
Both observations concern CN=Synthetic,OU=Lab,DC=example,DC=test, with a last-originating-change time of 2 January 2026, 03:04:05 UTC. The fixture deliberately uses large textual USNs to test preservation; their magnitude is not an anomaly finding.
| Observation or field | What this slice supports | Follow-up needed |
|---|---|---|
nTSecurityDescriptor, version 3 |
A reported last change to that attribute at the supplied time. | Compare security descriptors, owners and ACEs in appropriate directory snapshots or retained audit evidence. The metadata supplies no before/after ACL or modifying user. |
member with linked DN CN=Target,DC=example,DC=test |
A linked-value creation time of 1 January 2026, 00:00 UTC and deletion time of 2 January, 03:04:05 UTC. | Establish the group’s privileges and the target’s identity, then look for supported membership-change audit events and authorized change records. The two endpoints do not prove continuous effective privilege or use of it. |
| Originating DSA DN and invocation ID | The reported originating directory-server context. | Compare with the relevant DC inventory and its historical incarnation; the server is not the authenticated actor. |
Originating USN 18446744073709551610; local USN 9007199254740993 |
Exact counters preserved as text. | Scope the former to the originating server/invocation and the latter to the LDAP collection server. USNs are not global timestamps or counters comparable across unrelated DCs. |
Collected Name, SamAccountName, DN and SID |
Identity context as supplied by the export. | Account for renames, object lifetime and collection scope. The object’s account name does not name the person who made the change. |
Keep timestamp meanings separate: change-time normalizes ftimeLastOriginatingChange, object-created represents WhenCreated, and link-created / link-deleted represent linked-value times. The module always retains nonempty raw timestamp text, but normalizes only supported ISO timestamps with seconds, an explicit known timezone and at most six fractional digits. Ambiguous, timezone-free or unsupported values remain raw and produce warnings. The FILETIME sentinel 1601-01-01T00:00:00Z remains raw without a normalized time; it must not become a real deletion date. For altRecipient records, the native Member column maps to a linked recipient DN, not a group-membership claim. Removed links and collected deletion metadata remain evidence; importing them never instructs MISP to delete data.
Corroborate the directory lead with available DC Security events, ADTimeline object inventories, relevant GPO/SYSVOL evidence, administrative change records and endpoint activity. For example, examine Event ID 5136 for directory-object modifications and the applicable group-membership events for the group’s type/scope, where auditing and retention provide them. Use evtx_findings_import for supported Hayabusa/Chainsaw findings from those logs, and endpoint importers for related host observations; preserve native source record IDs and link the reviewed observations explicitly. Matching times alone do not prove that two changes share an actor or purpose, and missing audit events do not establish that no change occurred. At the reviewed revision, timesketch_export has no dedicated mapping for ad-replication-metadata times; do not assume it will export this object’s change-time without a separately validated mapping.
Record the supported conclusion and remaining gaps in an Event Report or Analyst Data. For this fixture, the conclusion remains two unreviewed metadata observations requiring corroboration, with no demonstrated malicious actor, privilege use or compromise. Any restoration of membership, ACLs or delegation belongs in the approved directory-response process, supported by verified state and impact analysis.
Timeline reconstruction
Use timesketch_import to bring a selected timeline slice and its annotations into the investigation. Prefilter the source export when appropriate; its default selection=all treats the supplied file as the selection. An API search hit is not the same as an explicit Timesketch selection flag. Numeric timestamp uses microseconds; numeric datetime requires a declared unit, and CLI JSON/JSONL produced through pandas commonly needs datetime_unit=ms.
Use timesketch_export for the return direction. It emits timestamped observations as JSONL, including supported process/file/network and Windows-event times and explicit first/last-seen endpoints. It does not substitute MISP metadata dates for activity times, upload to a sketch or transfer attachments and complete raw records. Its source IDs, tags and distribution fields are descriptive metadata; configure the destination sketch’s access separately. Repeated uploads can create duplicate timeline entries.
In the Windows exercise, MISP serializes these two saved activity times with the compact offset +0000, while that exercise’s pinned d7ec3654 Timesketch exporter requires the colon form +00:00. A direct export of the saved example therefore returns No supported timestamped observations selected with two timestamp warnings. This incompatibility is fixed by merged misp-modules PR #1140; updated services accept these offsets directly. The example export helper normalizes only explicit compact offsets on datetime attributes in an export-only copy, leaving the original event/export unchanged and unknown offsets unresolved. The resulting two-observation JSONL was produced by the real module service; it has not been uploaded to a Timesketch instance.
For an older service that requires the workaround, save one selected MISP event as standard JSON, review its audience and content, then run the helper against your local or approved module service:
# Requires Python requests and a service exposing timesketch_export.
python dfir/examples/export_timeline.py selected-event.json observations.jsonlSet MISP_MODULES_URL when that service uses a different base URL. Inspect the helper’s summary and warnings, then choose the intended sketch and upload the JSONL through Timesketch’s normal import workflow.
When selection excludes rows, timesketch_import and autopsy_import omit the full original attachment to avoid including excluded records. The network importers also document selection-aware attachment handling. Check each module’s response and retain the authoritative full export in the evidence system.
Filesystem timeline with The Sleuth Kit
Use a filesystem timeline to ask which recorded file timestamps fall within the investigation window, then keep their meanings distinct when importing them. This worked example follows /case/notes.txt from a synthetic filesystem image through Sleuth Kit output to MISP’s native Forensic analysis → Mactime review. This core import path is separate from misp-modules and does not acquire or examine the filesystem image itself.
The compressed example image contains a 4 MiB ext2 filesystem with one harmless 47-byte text file in /case. The image was authored with e2fsprogs 1.47.2, and the file’s timestamps were explicitly assigned for this exercise. The provenance record records the image hash, inode, tool versions and output hashes. All three screenshots below use the same pinned MISP 3.0_wip revision as the Windows example; the filesystem event is organization-only and unpublished.
Produce and inspect the evidence timeline
The following commands run from the book root with The Sleuth Kit 4.12.1 installed. They decompress the synthetic image into the working directory, extract filesystem metadata with fls, and select one file before running mactime. The image contains a filesystem starting at byte zero, so this example needs no partition offset; a partitioned evidence image requires the appropriate filesystem offset. The -m / option supplies the path prefix for bodyfile output; it does not mount the image. The Sleuth Kit fls and mactime manuals describe the output and date-range options.
mkdir -p work/dfir-sleuthkit
gzip -dc dfir/examples/sleuthkit/filesystem.img.gz > work/dfir-sleuthkit/filesystem.img
cd work/dfir-sleuthkit
sha256sum filesystem.img
fls -r -m / -z UTC filesystem.img > filesystem.body
awk -F '|' '$2 == "/case/notes.txt"' filesystem.body > notes.body
LC_ALL=C mactime -b notes.body -z UTC 2026-11-16..2026-11-17 > notes-timeline.txtCompare the image digest with the recorded SHA-256. The complete bodyfile preserves filesystem metadata, while the selected bodyfile retains inode 13, UID/GID 1000, size 47, permissions and the file’s timestamp fields. The bodyfile’s leading hash field is 0, meaning no file-content hash was supplied by this fls command; it is not an integrity digest for the file. Reading inode 13 with icat filesystem.img 13 recovers the same bytes as the harmless source file.
The actual human-readable Mactime output is:
Mon Nov 16 2026 09:20:00 47 m... -/rrw-r----- 1000 1000 13 /case/notes.txt
Mon Nov 16 2026 09:23:00 47 ..c. -/rrw-r----- 1000 1000 13 /case/notes.txt
Mon Nov 16 2026 09:25:00 47 .a.. -/rrw-r----- 1000 1000 13 /case/notes.txt
Every displayed time is UTC because mactime was run with -z UTC. The activity columns use MACB order: modification, access, metadata change and birth.
| Time on 16 November 2026, UTC | Flag | What the timestamp represents |
|---|---|---|
| 09:20:00 | m... |
Recorded file-content modification time. |
| 09:23:00 | ..c. |
Recorded inode metadata-change time; ctime does not mean file creation. |
| 09:25:00 | .a.. |
Recorded access time, whose interpretation depends on the filesystem and collection context. |
This ext2 fixture supplies no birth time. Its bodyfile preserves a zero birth-time value, and an unbounded mactime run displays an unknown-date placeholder for that field. The explicit date window excludes that placeholder from the upload rather than turning it into an invented creation time. A timestamp sequence alone does not establish who acted, execution of the file, or malicious activity; this example’s values were assigned deliberately.
For analysis in a spreadsheet or another parser, mactime -d produces the companion CSV. Upload the human-readable .txt output to the pinned MISP Mactime form: its parser expects the default whitespace layout, not CSV or fls bodyfile rows. Check every previewed path, activity and time, especially when a larger output contains grouped timestamps or filenames with spaces.
Review and save the filesystem observations
Create an organization-only event for the filesystem question. Choose Import → Forensic analysis → Mactime, select notes-timeline.txt, and choose Upload analysis file. See Populate from for the surrounding import controls.
Review the three rows for /case/notes.txt, with activity Modified, Changed and Accessed, before selecting them and choosing Create objects. The review’s Time accessed column is a generic heading in this interface: use the Activity value to interpret each timestamp, including the metadata-change row.
The core importer creates one mactime-timeline-analysis object per selected row. In this example, the three objects contain 18 attributes in total, with IDS disabled. Each object retains the path, its activity and datetime, size, permissions, and the complete uploaded timeline text as an attachment. Select the permitted file/time scope before uploading: checking fewer rows in this review does not remove unselected source lines from that attachment. In the tested browser form, LF line endings became CRLF in the attached text, so the attachment is not byte-identical to the original mactime output. Keep the original export and its hash in the evidence repository rather than substituting the imported attachment for it. Correlation settings remain separate; this core path does not automatically disable them as some dedicated evidence modules do.
The importer links adjacent selected rows with preceded-by and followed-by references. These links reflect the submitted row order, not independently established causal relationships. Retain the image hash and case reference separately from the timeline attachment’s hash, and record the timestamp interpretation in the event’s report.
Network and email investigations
Start with zeek_import or suricata_import for a selected sensor export, and use pcap_import when supported content reconstruction from a bounded capture answers the question. Record the sensor, capture/run, producer version and time range. Zeek UIDs, Suricata flow IDs, TCP/UDP streams and record ordinals have different scopes; matching identifiers alone do not merge records across captures. Community ID comparison also requires compatible algorithm version, seed, tuple and time scope.
For phishing and business-email investigations, email_import extracts message context, attachments and optionally URLs or partial inline forwards. Its extraction switches have separate semantics; retain the original message and inspect nested/forwarded content before making sender or attachment associations. dmarc_import imports aggregate reports, which describe reported authentication results and counts over an interval, rather than individual authenticated message histories. Use email_security_check, DNS and reputation lookups as additional context, keeping current configuration separate from historical evidence.
Other intake paths cover sandbox results and existing intelligence:
| Task | Candidate modules |
|---|---|
| Import local sandbox output | cuckooimport (Cuckoo/CAPE JSON or supported archives), joe_import, threatanalyzer_import, vmray_import, vmray_summary_json_import. |
| Retrieve a sandbox report by identifier/link | anyrun_sandbox_import; lastline_import is legacy and carries an upstream deprecation notice. |
| Import text, documents or an IOC list | csvimport, ocr, openiocimport, mispjson, url_import. Review field mappings, extraction errors and any remote retrieval. |
| Import passive DNS or intelligence exchange | cof2misp, taxii21, socradar_taxii_feed. Preserve source provenance and assess imported intelligence against the case. |
| Mobile, location or financial context | autopsy_import, gpx_import, geojson_import, nmea_import, kml_import, goamlimport; see geographic data. |
| Validate exposure/remediation hypotheses | darkmoon_import imports the producer’s penetration-test findings; those findings are not incident evidence by themselves. |
PCAP case with DNS and HTTP
Start with a question that the supplied capture can answer: did 192.0.2.10 request /case/notice.txt from updates.example, and which file bytes can be recovered? The example PCAP is authored teaching data, generated without transmitting packets. It contains 12 Ethernet/IPv4 packets, two transport streams and one harmless HTTP response, using reserved example addresses and a .example domain. Its timestamps were assigned explicitly, from 16 November 2026, 10:00:00.000000 to 10:00:01.900000 UTC. The generator reproduces the capture byte-for-byte; provenance records input/output hashes, tool versions and the live import checks.
Establish the packet evidence
On an analysis workstation with TShark installed, run these commands from the book root. Use a fresh export directory for each analysis run so previous files do not mix with the recovered content. The -n option disables name resolution, and -r reads the supplied capture rather than capturing live traffic. This example was dissected with TShark 4.4.19.
mkdir -p work/dfir-pcap/http-files
sha256sum dfir/examples/pcap/download-example.pcap
tshark -n -r dfir/examples/pcap/download-example.pcap -q -z conv,udp -z conv,tcp
tshark -n -r dfir/examples/pcap/download-example.pcap \
--export-objects http,work/dfir-pcap/http-files -q
sha256sum work/dfir-pcap/http-files/notice.txtThe capture is 1,185 bytes, with SHA-256:
8364adeccca609aa1e3d542aa1fc63da2fb9d518490c29518b46d8b2412104a3
The actual packet summary and conversation statistics provide the following evidence. All times below are UTC on 16 November 2026.
| Frame | Time | Observed packet content |
|---|---|---|
| 1 | 10:00:00.000000 | 192.0.2.10:49153 asks resolver 192.0.2.53:53 for an A record for updates.example. |
| 2 | 10:00:00.100000 | The DNS response contains A address 198.51.100.20. |
| 3 | 10:00:01.000000 | The observed TCP handshake begins with a SYN from 192.0.2.10:49152 to 198.51.100.20:80. |
| 6 | 10:00:01.300000 | The HTTP request is GET /case/notice.txt, with Host updates.example and User-Agent MISP-DFIR-Example/1.0. |
| 7 | 10:00:01.400000 | An HTTP 200 OK response supplies the complete 49-byte text payload. |
| 12 | 10:00:01.900000 | The final observed TCP ACK follows connection teardown. |
Import and review the capture
An administrator must enable pcap_import and install its dependencies on the misp-modules service, including TShark 4.0 or newer and the PyMISP helpers required by the handler. See Modules and the PCAP import contract. The handler processes the supplied capture offline; it does not fetch the HTTP URL or resolve the domain. Use a bounded capture that fits its 50 MiB input limit and the configured processing timeout.
Create an organization-only event for the packet question, then choose Import → Pcap Import, select download-example.pcap and choose Run Pcap Import. These screenshots use the same pinned MISP 3.0_wip revision as the preceding exercises, with a separate PCAP event that remains unpublished.
The real result contains four objects: one pcap-metadata, two network-connection objects and one reconstructed file. It also proposes ten standalone network attributes; the review’s total of 53 attributes includes 43 inside the objects. Review the audience, values, observation times, references and IDS flags before saving. Network observations arrive with IDS off, but the reconstructed file has seven IDS flags enabled by its file template in this runtime. Clear those flags for this context-only exercise, then choose Import; the saved example has IDS off on all 53 attributes.
Analyze the connections and recovered content
First, inspect pcap-metadata and compare its SHA-256, 1,185-byte size, 12-packet count and first/last packet times with the original capture. This object describes the uploaded bytes; the module does not attach the original PCAP again. Retain that file in the evidence repository with the case reference.
Next, inspect the two connection objects. The DNS flow is 192.0.2.10:49153 → 192.0.2.53:53, while the HTTP flow is 192.0.2.10:49152 → 198.51.100.20:80. The DNS answer address is an observation within the DNS exchange, not the DNS flow’s destination endpoint. Both are stream 0 within their own transport: identify a stream by capture hash, transport and stream index, not by the index alone.
The HTTP connection spans 10:00:01.000000–10:00:01.900000, with six source-direction and four reverse-direction packets. The module orients endpoints by the first observed packet; the visible SYN and subsequent HTTP request support the client role in this particular capture. A capture beginning midstream would need additional evidence before making that inference. Event-level values are deduplicated, so a value’s first/last-seen interval can span several packets or flows; use the connection objects for flow-specific bounds.
Finally, inspect the reconstructed notice.txt object. Its size is 49 bytes, and its SHA-256 matches the independently exported payload:
280b6cfbb18139c732a360926bb99beef5e8fdd5070f591d77972f92aa4f3516
The module matches the exact HTTP payload bytes to TCP stream 0 and completion frame 7. The file attributes’ observation interval is therefore 10:00:01.400000 at both endpoints, rather than the entire connection’s duration. The file object links back to its capture metadata and connection with derived-from references.
This file object uses MISP’s malware-sample storage representation even though the payload is harmless teaching text. The normal sample download is packaged as an encrypted ZIP; compare the hash of the unpacked 49-byte content, rather than the ZIP wrapper, with the recovered payload. The live check unpacked that download and verified the bytes match notice.txt exactly.
At this core revision, the import review preserves reference targets and relationship types but omits the module’s reference comments. The recorded module API result, from a separate offline run of the same capture, retains the detailed frame/payload provenance before review. Its generated UUIDs can differ from those in the saved event; compare capture hashes, transport/stream keys and payload hashes. Keep that provenance with the original capture when detailed frame-level references are required, rather than assuming every module field survived the UI round trip.
The supported conclusion is that the synthetic client requested this URL and received the recovered bytes within the supplied packet window. HTTP reassembly does not establish that the client wrote a file to disk. The capture alone does not establish file execution, persistence, compromise or activity outside that window. This case uses plaintext HTTP; the handler does not decrypt HTTPS traffic. Record the assessment and next scoping question in the Event Report before promoting any selector to hunting or response content.
Explore observations with MISP’s timeline
MISP’s event Timeline tab helps compare observation windows, inspect an object’s dated attributes, filter relevant items and return to their records for review. In the pinned MISP 3.0 Overmind interface, Seen, Modified and Created choose different clocks for placing rows. The choice is remembered in the browser, so check the active button before interpreting a chart. This view uses the current event and, when viewing event extensions together, the accessible events in that extension view; it is not a search across every event in MISP.
| Timeline basis | What places a row | DFIR interpretation |
|---|---|---|
| Seen | Attribute/object first_seen and last_seen metadata; an object also spans its dated children. |
Compare reported observation windows. These are not automatically the datetime values stored in an object’s attributes. |
| Modified | The MISP attribute/object’s last modification timestamp; an object includes its attributes’ modification times. | Inspect the latest recorded changes to MISP content. This is neither source activity time nor a complete edit history; use History for audit context. |
| Created | When this MISP instance created an attribute; objects span their attributes’ creation times. | Inspect data arrival/creation in this instance, not file creation, AD object creation or the original observation time. Attributes predating MISP 3.0 may have no creation timestamp. |
Read ranges, endpoints and undated items
The timeline teaching event is a separate authored fixture, with fictional observations on 12–14 November 2026. It was saved in an organization-only, unpublished event on 16 November, so its Seen dates differ from its MISP creation/modification dates. No domain lookup, network connection or file collection produced these example intervals.
Open the event and choose Timeline → Seen. The domain updates.example has both observation endpoints, the file object has a range with two dated children, and 203.0.113.25 has only a first-seen value. An item with a missing endpoint displays not recorded; the one-sided marker does not supply an invented last observation. The standalone text observation has no seen dates, so MISP counts it in the undated notice and offers a link to list it. That notice counts undated top-level rows, not every undated attribute inside a dated object.
Expand the file row with its chevron to compare the filename interval with the path’s single-time observation. Hover over a row or marker to inspect full UTC dates and its recorded metadata; the date columns may show only times of day when the selected window is short. The object envelope covers its own dates and the dated attributes visible to the reader, so it need not describe one continuous activity. A first/last-seen span also does not establish continuous traffic, execution or compromise throughout the gap. Click a row to open the corresponding record in Objects or Attributes, where its source and analytical context can be checked.
Filter and narrow the investigation window
Use Search values… for a value of interest, or open Filters to select standalone attribute/object rows, a type or object name, and a category. An extension view also offers a source-event filter. For this fixture, Type or object → file retains the file row and its dated children; the active filter chip and row count describe the reduced view. Reset filters when returning to the full set of dated rows.
For longer spans or a capped result, MISP shows an Activity across the event overview strip. Drag across it to select a date window and inspect the rows beneath it; use Show the whole span or reset the strip to restore the full window. The overview uses buckets and a square-root height scale: it summarizes rows seen in a period, rather than proving a count of packets, logons or distinct incidents. At this revision, a response lists at most 2,000 top-level rows and marks capped results; narrow the window or filters before drawing conclusions from missing rows. Counts, object children and dates also depend on the reader’s access and current event/extension scope.
Review observation metadata without confusing the clocks
Choose Modified to place the same teaching records on their MISP modification day instead of their fictional activity days. For a user allowed to modify the event, the calendar action beside a row opens Seen dates, where first/last-seen metadata can be set or corrected in UTC. Saving is a real MISP edit and updates modification time; it does not rewrite a datetime-valued attribute such as a file’s modification-time. The editor rejects a last-seen value preceding first-seen, and an unknown endpoint should remain blank. Use source-supported observation times and record the reason for a correction; the shortcut to copy modification time is appropriate only when that is actually the intended observation time.
The Created view places this fixture’s attributes on their creation day in the documentation instance. Its file object still stores a separate datetime-valued modification-time of 12 November, 08:00 UTC, which is not used to place that field in Seen without first/last-seen metadata. The UI exercise verified a temporary first-seen correction on the synthetic IP through the native editor, then restored the original value while leaving last-seen unset. The pictured domain editor was closed without saving.
The ADTimeline example makes the distinction especially visible: its two observations preserve change-time, object-creation and link times, but the importer does not assign first/last-seen metadata. Consequently, Seen reports three undated objects, including the source file, even though meaningful source dates remain inside those objects. This does not mean the evidence is timeless or the import failed.
If the investigation requires a directory change on the Seen timeline, explicitly map a validated change observation to its own observation point and document that choice, retaining the original raw/normalized time fields and source reference. Do not combine an object’s creation time and a member-link deletion time into an unsupported activity interval. Use the timeline exchange workflow for supported Timesketch/Plaso interchange; importing a datetime field, displaying an observation in MISP and exporting it to another timeline have separate mappings. The timeline fixture provenance records these live checks and the pinned timeline implementation.
Enrich a selector without losing its meaning
Choose an enrichment module to answer a question about a selected hash, address, domain, URL, certificate or rule. Record the provider, query time, queried value, returned source reference and relevant historical interval. Preview results and check whether they support the incident’s hypothesis before importing or promoting them. The pivoting use case explains how to evaluate shared infrastructure and weak selectors.
| Investigation question | Useful module examples | Interpretation and data flow |
|---|---|---|
| Is a file already known? | hashlookup, hashdd, malwarebazaar, threatfox, virustotal, virustotal_public, google_threat_intelligence, mwdb_query, vmray_analyzer, reversinglabs_malware_presence. |
Usually a hash lookup to a configured service. Known-file membership, first submission and a vendor verdict have different meanings; a known hash is not a blanket clearance. |
| What does existing analysis say? | anyrun_lookup, assemblyline_query, joesandbox_query, triage_query, hybrid_analysis, intezer, manalyze, reversinglabs_spectra_analyze, malpedia, eset_report. |
Check the specific handler: some retrieve reports, while others may obtain sample data or start analysis. Preserve analysis IDs and distinguish sandbox behavior from behavior observed on a victim. |
| What infrastructure was observed? | circl_passivedns, farsight_passivedns, passivetotal, securitytrails, dnslytics, domaintools_iris_investigate, domaintools_iris_pivot, validin, hyasinsight, circl_passivessl, passive_ssh. |
Historical provider observations have collection limits and time windows. Shared addresses or certificates do not establish common control. |
| What resolves or is registered now? | dns, dns_query, reversedns, url_dns, whois, rdap, domaintools, domaintools_iris_enrich, whoisfreaks, tls_certificate_check, ssh_fingerprint. |
Current resolution/registration or direct protocol queries can differ from incident-time observations. Direct connections may be visible to the queried infrastructure. |
| What exposure or background activity exists? | censys_enrich, censys_enrichmentapis, shodan, shodan_internetdb, ivre, onyphe, onyphe_full, zoomeye, criminal_ip, greynoise, crowdsec, abuseipdb, dshield, bgpranking, team_cymru_scout. |
Reputation, scan and telemetry context helps prioritize leads; it does not establish local compromise or complete asset coverage. |
| Can I extract document or URL context? | extract_url_components, docx_enrich, pdf_enrich, xlsx_enrich, pptx_enrich, odt_enrich, ods_enrich, ocr_enrich, qrcode, html_to_markdown, hygiene, bingraph. |
Inspect dependencies and effects. Parsing may be local, while some converters fetch URLs; extracted text and OCR require validation. |
| Does a page resemble known phishing? | urlscan, lookyloo, lookyloo_capture, phishunt, urlhaus, google_safe_browsing, dnstwist, rst_favicon, rst_html, rst_screenshot, rst_ssl, webarchive. |
Existing-result lookup, generated variants and a fresh capture are different activities. A new capture may contact infrastructure; dnstwist candidates are hypotheses until observed. |
| Could a vulnerability explain initial access? | cve, cve_advanced, vulnerability_lookup, vulners, vuldb, vulndb, cpe, gcve_cpe, first_epss, rapid7_attackerkb, cisco_psirt, qualys_cve, greynoise_vuln. |
Match affected products/versions and exposure to local evidence. CVE association, EPSS and exploit reporting do not prove exploitation on a host. |
| Can existing security platforms add context? | crowdstrike_falcon, cortex_xdr_ioc_lookup, cortex_xsoar_indicator_lookup, n8n_data_table_lookup, shuffle_datastore_lookup, tines_record_lookup, torq_observable_lookup, opencti, yeti, flowintel. |
Read the configured platform’s indicator or contextual records; these names do not imply raw EDR telemetry acquisition or automated remediation. |
| Is there ransomware, identity or transaction context? | ransomlook, ransomcoindb, btc_scam_check, btc_steroids, sochain, hibp, xposedornot, osint_industries, phone_number_info, socialscan. |
Apply only when relevant to the case and permitted data use. Breach, extortion and account-presence reporting requires independent corroboration. |
| Where might infrastructure be located? | geoip_city, geoip_country, geoip_asn, mmdb_lookup, ipinfo, ip2locationio, ipgeolocation, ipasn, ripestat. |
Network geolocation and ASN context do not locate a person or prove actor attribution. Check local-database versus remote-provider processing. |
The complete inventory below includes additional providers and specialized utilities so that a case-specific integration is not overlooked. Their presence in source is not a guarantee of provider availability, maintained APIs or compatibility with your deployed environment.
Distinguish lookups from submissions
Before invoking a handler, check whether it sends only the selector, downloads a sample, uploads bytes/tags, visits a URL or creates a remote job. MISP distribution settings do not prevent a module from sending supplied data to its configured service. Even a hash-only query can disclose investigative interest.
Modules with submission capabilities include anyrun_sandbox_submit, assemblyline_submit, cape_sandbox, cuckoo_submit, joesandbox_submit, triage_submit, vmray_submit, lastline_submit, virustotal_upload, malshare_upload, mwdb, malwagon_submit, pandora_submit, mobsf, paloalto_wildfire, fortisandbox, sophoslabs_intelix and reversinglabs_spectra_intel_submission. This is a review queue, not a claim that every handler has the same submission contract. For example, mobsf retrieves an existing static report for MD5 input but uploads/scans supplied application bytes; cape_sandbox gates sample submission behind submit_samples; mwdb can forward tags/comments and its mwdb_public default is true. virustotal_downloader retrieves content rather than merely looking up a verdict. Check the source, service configuration, provider sharing settings and permitted evidence handling before selecting these paths.
Turn reviewed findings into hunts and response inputs
Keep unreviewed evidence in its original objects and derive a bounded hunting set from the findings you validated. Choose selectors that can answer the scoping question and record why each was included, its validity interval and expected false positives. IDS eligibility is one useful export filter; it is not an approval record or a universal rule shared by every exporter.
| Output or integration | Modules | Operational check |
|---|---|---|
| Endpoint hunts | osqueryexport, osquery_pack_publish, osquery_import, nexthinkexport. |
Inspect SQL, platform requirements and scan paths. Publishing an osquery pack does not distribute/reload it or execute queries; retain the sources map and collect results separately. |
| YARA, Sigma, EQL and STIX patterns | yara_query, yara_syntax_validator, cccs_yara, sigma_syntax_validator, sigma_queries, rulezet_validator, eql, stix2_pattern, stix2_pattern_syntax_validator; exports yara_export, sigma_export, mass_eql_export, stix2_pattern_export. |
Validate syntax/metadata and test against representative data. A generated hash rule is a selector, not a behavioral detector; backend conversion does not guarantee equivalent semantics. |
| Network/SIEM detection exchange | zeek_intel_export, splunk_export, elastic_ecs_export, cef_export, bpf_export, qradar_reference_set_export, wazuh_cdb_export, defender_endpoint_export. |
Review supported types, field mapping, filtering, expiry and target ingestion. A generated file has not been deployed or matched. |
| EDR/SIEM publication | crowdstrike_ioc_publish, sentinelone_ioc_publish, cortex_xdr_ioc_publish, qradar_reference_set_publish, wazuh_cdb_publish, export_sentinel. |
Use explicit destination/scope and the handler’s dry run when provided. Verify per-indicator outcomes and remote state; export_sentinel requires an existing MISP2Sentinel/MISP2Defender installation. |
| Network containment configuration | cisco_acl_export, cisco_asa_export, cisco_firesight_manager_ACL_rule_export, fortios_export, junos_export, mikrotik_export, netfilter_export, owasp_crs_export, panos_export, pf_export, squid_export. |
Inspect generated syntax and expected impact before a separate deployment. Scope and expiry are especially important for shared or reassigned addresses. |
| Case creation and orchestration | cortex_xsoar_incident_create, tines_case_create, torq_case_create, n8n_webhook, shuffle_workflow_execute, doppel_alert_takedown. |
These can create cases, execute workflows or request an external action. Check retries, duplicate creation and downstream behavior; takedown is a separate response decision. |
| Responder handoff | matrix, mattermost, slack, signal, nextcloud_talk, irc; pdfexport, csv_export, liteexport, jinja_template_rendering, convert_markdown_to_pdf. |
Minimize transmitted content and check channel membership. A delivered message or PDF does not acknowledge containment or completion. |
| Timeline and intelligence exchange | timesketch_export, threat_connect_export, threatStream_misp_export, virustotal_collections, vt_graph. |
Check destination audience and lossy field mappings. Repeated export/publication can create duplicate or stale records. |
Track the destination receipt, owner and expiry of a deployed indicator. A workflow trigger or successful request is not proof that every destination accepted the data or took the intended action. Return the actual results and scope to the investigation, recording collection/execution time separately from import time. Use Sightings for appropriately supported observations, false-positive feedback or expiry; absence of a result supports a conclusion only within known search coverage. See Workflows for MISP workflow configuration and False Positives for review and correction.
Apply the process to other investigations
| Scenario | Evidence and modules | Questions before a response |
|---|---|---|
| Suspected ransomware | Selected evtx_findings_import, velociraptor_import, volatility3_import results; hash/report lookups; ransomlook for public context. |
Which hosts show observed execution, encryption or lateral movement? Are public extortion claims independently corroborated? |
| Phishing or business-email compromise | email_import, dmarc_import, qrcode, document parsers and approved URL/DNS/report lookups. |
What is the original message provenance? Which recipients interacted, and what identity/audit logs support account misuse? |
| Memory-resident execution | volatility3_import with process/socket/malfind/YARA context, endpoint exports and reviewed YARA hunts. |
Are findings from the same image and process lifetime? Do suspicious regions have corroborating execution evidence? |
| Active Directory change or suspected persistence | adtimeline_import for selected replication metadata, evtx_findings_import for supported audit findings and endpoint imports for corroboration. |
What changed, on which object and server, and what independently supports attribution or impact? Preserve linked-value time semantics and distinguish collected state from historical values. |
| Network intrusion or suspected exfiltration | zeek_import, suricata_import, bounded pcap_import, historical DNS/TLS context and timeline exchange. |
Is traffic direction established? Are capture gaps or encryption limiting visibility, and do timestamps align with endpoint evidence? |
| Mobile/device investigation | autopsy_import selected artifacts, mobsf for an authorized app-analysis path, and geographic importers where relevant. |
Does the adapter preserve device/source identity and timestamp semantics? Does app presence establish execution or user action? |
| Cloud or SaaS incident | Selected audit exports mapped through csvimport/mispjson, compatible timeline imports and platform-context lookups. |
Who collected the records, from which tenant/account and time window? Preserve immutable resource/session identifiers; do not assume a generic CSV importer performs cloud acquisition. |
Complete module inventory
The following inventory covers 331 production Python handlers in the four module families at misp-modules revision f4899ad4: 33 import, 240 expansion, 39 export and 19 action modules. It excludes private/helper files, skeletons, import_blueprint and the three test* handlers. It is deliberately broad: specialized financial, geographic, identity and reporting modules may support a particular investigation even when they are not forensic parsers. Use the earlier process tables to select a path, then follow the handler link and check its contract and runtime availability. Descriptions below are source-declared purposes, not a certification that a provider works or that every module is appropriate for a case.
Download the machine-readable module inventory, including declared inputs, requirements, configuration fields, source links and file hashes. The inventory provenance records the reviewed commit, scope and family counts.
Import modules (33)
| Module | Declared purpose |
|---|---|
adtimeline_import |
Import ADTimeline CSV replication metadata with linked-value times, server-scoped counters and source provenance. |
anyrun_sandbox_import |
A module designed to retrieve an analysis report from the ANY.RUN Sandbox by its unique ID and extract results (such as verdict, malware tags, and IOCs), converting them into MISP attributes within your event. |
autopsy_import |
Import selected browser, download, communication and application artifacts with forensic provenance. |
cof2misp |
Passive DNS Common Output Format (COF) MISP importer |
csvimport |
Import MISP attributes from base64-encoded UTF-8 CSV contents. |
cuckooimport |
Module to import Cuckoo and CAPE JSON reports or analysis archives. |
darkmoon_import |
Module to import the JSON findings of the Darkmoon autonomous AI penetration testing platform. |
dmarc_import |
Import DMARC aggregate XML reports, including gzip and ZIP files. |
email_import |
Email import module for MISP |
evtx_findings_import |
Import Hayabusa timelines and Chainsaw hunt results as unreviewed detections with linked Windows event context. |
geojson_import |
Import GeoJSON datasets with linked geolocation objects for point features. |
goamlimport |
Module to import MISP objects about financial transactions from GoAML files. |
gpx_import |
Import GPX files as a gpx object with linked geolocation objects. |
joe_import |
A module to import data from a Joe Sandbox analysis json report. |
kml_import |
Import KML documents and KMZ packages with linked Point and gx:Track geolocations. |
lastline_import |
Deprecation notice: this module will be deprecated by December 2021, please use vmware_nsx module. Module to import and parse reports from Lastline analysis links. |
mispjson |
Module to import MISP JSON format for merging MISP events. |
nmea_import |
Import NMEA 0183 receiver logs with linked geolocation observations. |
ocr |
Optical Character Recognition (OCR) module for MISP. |
openiocimport |
Import legacy OpenIOC 1.0 and 1.1 files into MISP. |
osquery_import |
Import osquery snapshots and differential results with host, query/pack and source-indicator provenance. |
pcap_import |
Import a PCAP or PCAPNG capture, including reassembled files, emails and network indicators. |
socradar_taxii_feed |
Import threat indicators from SOCRadar TAXII 2.1 feed with MITRE ATT&CK, malware family, confidence, and geo tagging. Leave collection_id empty and type ‘list’ to discover available collections. |
suricata_import |
Import selected Suricata EVE findings with timestamps, flow/Community IDs, signatures and capture references. |
taxii21 |
Import content from a TAXII 2.1 server |
threatanalyzer_import |
Module to import ThreatAnalyzer archive.zip / analysis.json files. |
timesketch_import |
Import selected or annotated Timesketch/Plaso entries with source references and annotation context. |
url_import |
Simple URL import tool with Faup |
velociraptor_import |
Import Velociraptor JSON, JSONL or CSV results with linked forensic observations and provenance. |
vmray_import |
Module to import VMRay (VTI) results. |
vmray_summary_json_import |
Import a VMRay Summary JSON report. |
volatility3_import |
Import Volatility 3 process, network, suspicious-memory and YARA results with memory-image provenance. |
zeek_import |
Import selected Zeek records with timestamps, connection/Community IDs and capture provenance. |
Expansion modules (240)
| Module | Declared purpose |
|---|---|
abuseipdb |
AbuseIPDB MISP expansion module |
alphaMountain |
alphaMountain threat intelligence lookup for IPs, domains, hostnames, and URLs - adds risk score tags |
anyrun_lookup |
Search ANY.RUN threat intelligence for existing observations without submitting a sandbox task. |
anyrun_sandbox_submit |
A module designed to submit URLs or files to the ANY.RUN Sandbox for analysis and return the unique analysis link and ID. |
apifreaks |
An expansion module for https://apifreaks.com/ that provides an enriched analysis of a domain, hostname, IP address, ASN or email address, including WHOIS, DNS, subdomains and domain-availability information. |
apiosintds |
On demand query API for OSINT.digitalside.it project. |
apivoid |
Query APIVoid v2 for DNS records, SSL certificates and email verification. |
assemblyline_query |
A module to query the AssemblyLine API with a submission ID to get the submission report and parse it. |
assemblyline_submit |
A module to submit samples and URLs to AssemblyLine for advanced analysis, and return the link of the submission. |
backscatter_io |
Backscatter.io module to bring mass-scanning observations into MISP. |
bgpranking |
Query CIRCL BGP Ranking for the daily ranking of an Autonomous System number. |
bingraph |
Create entropy and byte histogram PNG plots of an attachment or malware sample. |
btc_scam_check |
An expansion hover module to query a special dns blacklist to check if a bitcoin address has been abused. |
btc_steroids |
An expansion hover module to get a blockchain balance from a BTC address in MISP. |
cape_sandbox |
Submit supplied samples to CAPEv2 or retrieve a completed JSON report by numeric task ID. |
cccs_yara |
Validate YARA rule metadata against the CCCS YARA specification. |
censys_enrich |
An expansion module to enrich attributes in MISP by quering the censys.io API |
censys_enrichmentapis |
Retrieve Censys host enrichment, web properties on ports 80 and 443, or certificate metadata. |
circl_passivedns |
Module to access CIRCL Passive DNS. |
circl_passivessl |
Modules to access CIRCL Passive SSL. |
cisco_psirt |
Retrieve Cisco PSIRT security advisories by CVE, Cisco advisory ID or Cisco bug ID. |
cisco_umbrella |
Enrich a domain with Cisco Umbrella Investigate categorization and risk scores. |
clamav |
Submit file to ClamAV |
cluster25_expand |
Module to query Cluster25 CTI. |
convert_markdown_to_pdf |
Render the markdown (under GFM) into PDF. Requires pandoc (https://pandoc.org/), wkhtmltopdf (https://wkhtmltopdf.org/) and mermaid dependencies. |
cortex_xdr_ioc_lookup |
Look up exact hash, domain and IP IOC rules in a Cortex XDR tenant. |
cortex_xsoar_indicator_lookup |
Look up a MISP observable in Cortex XSOAR 8’s indicator store with reputation and expiration metadata. |
countrycode |
Module to expand country codes. |
cpe |
An expansion module to query the CVE search API with a cpe code to get its related vulnerabilities. |
criminal_ip |
Retrieve IPv4 risk and infrastructure reports, existing domain scan listings, or a completed domain scan by numeric text ID. |
crowdsec |
Module to access CrowdSec CTI API. |
crowdstrike_falcon |
Query CrowdStrike Falcon Intelligence indicators on demand. |
cuckoo_submit |
Submit files and URLs to Cuckoo Sandbox |
cve |
An expansion hover module to expand information about CVE id. |
cve_advanced |
An expansion module to query the CIRCL CVE search API for more information about a vulnerability (CVE). |
cytomic_orion |
An expansion module to enrich attributes in MISP by quering the Cytomic Orion API |
darkeye |
Look up domain exposure metadata in HaveIBeenRansom and Breach House. |
dbl_spamhaus |
Checks Spamhaus DBL for a domain name. |
dectrax |
Enrich IP observables against DECTRAX honeypot telemetry, decoy interactions, and EDL interdiction status. |
dns |
Simple DNS expansion service to resolve IP address from MISP attributes |
dns_query |
Enumerate DNS record types and extract domain, IP, email and URL pivots. |
dnslytics |
Run an explicit DNSlytics domain dataset query supplied as a text attribute. |
dnstwist |
Generate domain permutations locally with optional DNS resolution. |
docx_enrich |
Module to extract freetext from a .docx document. |
domaintools |
Legacy DomainTools WHOIS, reputation and reverse lookup expansion module. |
domaintools_iris_enrich |
Retrieve DomainTools Iris Enrich results using the provider reference field and query conventions. |
domaintools_iris_investigate |
Retrieve DomainTools Iris Investigate results using the provider reference field and query conventions. |
domaintools_iris_pivot |
Retrieve DomainTools Iris Pivot results using the provider reference field and query conventions. |
dshield |
Look up IP reports, target counts, network ownership and threat-feed observations in DShield / SANS ISC. |
duckduckgo_search |
Search DuckDuckGo for web references to an attribute without an API key. |
email_security_check |
Check email security posture (SPF, DKIM, DMARC, MTA-STS) for a domain. |
eql |
EQL query generation for a MISP attribute. |
eset_report |
Download an ESET ETI PDF from a supported report download link and return a report object with its PDF attachment and SHA-256. |
eupi |
A module to query the Phishing Initiative service (https://phishing-initiative.lu). |
extract_url_components |
Extract URL components |
extuno |
Query Extuno for the reputation of a browser extension, an IDE extension or a package, identified by its store id or its listing URL. |
farsight_passivedns |
Module to access Farsight DNSDB Passive DNS. |
first_epss |
Query FIRST directly for a CVE EPSS probability, percentile and score date without requiring another vulnerability service. |
flowintel |
Find Flowintel cases containing the queried attribute value. |
flowtriq |
Query Flowtriq for DDoS attack intelligence on IP addresses |
fortisandbox |
Authenticate to a FortiSandbox appliance and retrieve an existing rating by SHA-1 or SHA-256. |
gcve_cpe |
Expand CPE attributes with GCVE CPE catalog metadata, package mappings and vulnerability references. |
geoip_asn |
Query a local copy of the MaxMind GeoLite2 ASN database (MMDB format) |
geoip_city |
An expansion module to query a local copy of MaxMind GeoIP2 or GeoLite2 database with an IP address, in order to get information about the city where it is located. |
geoip_country |
Query a local MaxMind GeoIP2 or GeoLite2 Country database (MMDB format) |
geoplugin |
An expansion and hover module to geolocate an IP address with geoPlugin. |
glimps_malware |
Retrieve GLIMPS Detect results by SHA-256 or analysis UUID supplied as text. |
google_safe_browsing |
Google safe browsing expansion module |
google_threat_intelligence |
An expansion module to have the observable’s threat score assessed by Google Threat Intelligence. |
greynoise |
Module to query IP and CVE information from GreyNoise |
greynoise_vuln |
Retrieve dedicated GreyNoise CVE intelligence, including available exploitation activity, exploit counts, product details and prioritization fields. |
hashdd |
A hover module to check hashes against hashdd.com including NSLR dataset. |
hashlookup |
An expansion module to query the CIRCL hashlookup services to find it if a hash is part of a known set such as NSRL. |
hibp |
Module to access haveibeenpwned.com API. |
hostio |
Retrieve Host.io DNS, website and co-hosted domain observations. |
html_to_markdown |
Expansion module to fetch the html content from an url and convert it into markdown. |
hyasinsight |
HYAS Insight integration to MISP provides direct, high volume access to HYAS Insight data. It enables investigators and analysts to understand and defend against cyber adversaries and their infrastructure. |
hybrid_analysis |
Look up Hybrid Analysis reports or submit a file or URL for sandbox analysis. |
hygiene |
Check an observable against local MISP warninglists and record the matching lists. |
import_external_reference |
Capture a public web reference as Markdown or a PDF attachment. |
intel471 |
Module to access Intel 471 |
intel471_hunt |
Retrieve Intel 471 Hunter hunt packages, Sigma rules and analyst guidance. |
intezer |
Retrieve Intezer Analyze file reports or submit an attachment for analysis. |
ip2locationio |
An expansion module to query IP2Location.io to gather more information on a given IP address. |
ipapi_is |
An expansion and hover module to enrich an IP address with geolocation, ASN, company and abuse contact data, and VPN (with the provider), proxy, Tor and datacenter detection from ipapi.is. |
ipasn |
Module to query an IP ASN history service (https://github.com/D4-project/IPASN-History). |
ipgeolocation |
An expansion and hover module to enrich an IP address with geolocation, ASN, company, threat intelligence (threat score, VPN, proxy, Tor, bot and spam signals) and abuse contact information from IPGeolocation.io, either through the API… |
ipinfo |
An expansion module to query IPinfo for geolocation, ASN and contextual IP intelligence. |
ipqs_fraud_and_risk_scoring |
IPQualityScore MISP Expansion Module for IP reputation, Email Validation, Phone Number Validation, Malicious Domain,Malicious URL Scanner,Malicious File Scanner & Compromised username, Password, Email |
iprep |
Module to query IPRep data for IP addresses. |
ismalicious |
Query isMalicious for IP, domain, hostname, and URL reputation. |
ivre |
Retrieve active scan observations from an IVRE web API. |
jinja_template_rendering |
Render the template with the data passed |
joesandbox_query |
Query Joe Sandbox API with a submission url to get the json report and extract its data that is parsed and converted into MISP attributes and objects. |
joesandbox_submit |
A module to submit files or URLs to Joe Sandbox for an advanced analysis, and return the link of the submission. |
kaspersky |
Retrieve Kaspersky commercial Threat Intelligence Portal reports. |
lamis_network |
Lamis Network IP Intelligence and Risk Scoring expansion module. |
lastinfosec |
Retrieve LastInfoSec STIX 2.1 intelligence and convert it to MISP. |
lastline_query |
Deprecation notice: this module will be deprecated by December 2021, please use vmware_nsx module. Query Lastline with an analysis link and parse the report into MISP attributes and objects. |
lastline_submit |
Deprecation notice: this module will be deprecated by December 2021, please use vmware_nsx module. Module to submit a file or URL to Lastline. |
lookyloo |
Find Lookyloo captures containing an IP, hostname, URL, resource hash or favicon hash. |
lookyloo_capture |
Enrich a Lookyloo capture link or UUID with observed resources and analysis context. |
macaddress_io |
MISP hover module for macaddress.io |
macadress_com |
Module to access macadress.com API. |
macvendors |
Module to access Macvendors API. |
malbeacon |
Retrieve MalBeacon C2 and actor infrastructure observations. |
malpedia |
Search Malpedia families and actors, or expand a sample hash or Malpedia record URL. |
malshare_upload |
Module to push malware samples to MalShare |
malwagon |
Look up a SHA256 digest in the Malwagon sandbox and return the scans it already has for it. |
malwagon_submit |
Detonate a sample or a URL in the Malwagon sandbox and return the analysis. |
malwarebazaar |
Query Malware Bazaar to get additional information about the input hash. |
manalyze |
Analyze PE attachments and malware samples with a local Manalyze installation. |
mcafee_insights_enrich |
Lookup McAfee MVISION Insights Details |
metras |
Enrich file hashes and IP addresses with Metras EDR inventory and fleet context. |
mmdb_lookup |
A hover and expansion module to enrich an ip with geolocation and ASN information from an mmdb server instance, such as CIRCL’s ip.circl.lu. |
mobsf |
Submit mobile applications to MobSF or retrieve static analysis reports by MD5. |
modat |
Enrich internet infrastructure using MODAT Magnify host, service and DNS observations. |
mwdb |
Module to push malware samples to a MWDB instance |
mwdb_query |
Query an MWDB instance for an existing file by hash. |
n8n_data_table_lookup |
Find an observable in a selected n8n Data Table string column using the public REST API. |
netapi |
Check a domain, hostname, URL or IP address against the NetAPI compromised feeds and get the domain’s position in the NetAPI Top 1M. |
neutrino |
Enrich public IP addresses with NeutrinoAPI blocklist categories, detection flags, timestamps and sensor context. |
ocr_enrich |
Module to process some optical character recognition on pictures. |
ods_enrich |
Module to extract freetext from a .ods document. |
odt_enrich |
Module to extract freetext from a .odt document. |
onion_lookup |
MISP module using the MISP standard. Uses the onion-lookup service to get information about an onion. |
onyphe |
Module to process a query on Onyphe. |
onyphe_full |
Module to process a full query on Onyphe. |
opencti |
Query an OpenCTI instance for exact observable matches and their context and source references. |
orange_cyberdefense |
Look up indicators in the Orange Cyberdefense Datalake API. |
orion_malware |
Retrieve existing Orion Malware reports by file hash. |
osint_industries |
Find OSINT Industries account and identity context for an email, phone, username or wallet. |
otilabs |
An expansion module for the OTI Labs Domain Intelligence API (https://oti-labs.com/domain-intelligence-api). |
otx |
Module to get information from AlienVault OTX. |
paloalto_wildfire |
Retrieve WildFire verdicts and XML reports, or submit an attachment for analysis. |
pandora_submit |
Submit attachments and malware samples to Pandora and return a link to the analysis. |
passive_ssh |
An expansion module to enrich, SSH key fingerprints and IP addresses with information collected by passive-ssh |
passivetotal |
The PassiveTotal MISP expansion module brings the datasets derived from Internet scanning directly into your MISP instance. |
pdf_enrich |
Module to extract freetext from a PDF document. |
pgp_keyserver |
Pivot on OpenPGP key IDs, fingerprints, email addresses and UIDs using an HKP keyserver. |
phishunt |
Look up a host in phishunt (phishunt.io), the free CC0 feed of live phishing domains: the phishing URLs detected on that exact host, the brand they target, when they were first seen, where they are hosted and which other feeds flag them. |
phone_number_info |
Offline phone-number normalization, numbering-plan geography and original carrier lookup. |
plum_island |
Retrieve historical scan observations from the Plum Island Discovery API v1. |
plum_island_search |
Find IPs observed with a domain, hostname, network or certificate fingerprint in Plum Island. |
polyswarm |
Retrieve PolySwarm sample reputation, engine verdicts and file metadata. |
polyswarm_sandbox |
Retrieve PolySwarm sandbox tasks or submit an existing PolySwarm sample for sandbox analysis. |
pptx_enrich |
Module to extract freetext from a .pptx document. |
proofpoint_et_intelligence |
Enrich domains, IPv4 addresses and MD5 hashes using Proofpoint ET Intelligence. |
ptrclassify |
Classify PTR hostnames and tag queried attributes with the ptrclassify taxonomy. |
pulsedive |
Look up IP, domain and URL risk, linked threats, feeds and DNS observations in Pulsedive. |
qintel_qsentry |
A hover and expansion module which queries Qintel QSentry for ip reputation data |
qrcode |
MISP Expansion Module: QR Code Decoder (Anti-Quishing) This module downloads and decodes QR codes from local attachments or remote URLs. It includes security hardening against SSRF and DoS attacks. |
qualys_cve |
Retrieve Qualys KnowledgeBase vulnerability details for a CVE identifier. |
ransomcoindb |
Module to access the ransomcoinDB (see https://ransomcoindb.concinnity-risks.com) |
ransomlook |
Query the RansomLook API and return matching ransomware leak-site posts as MISP objects. |
rapid7_attackerkb |
AttackerKB MISP Module Author: R7 Labs Description: Enrich CVEs via AttackerKB API and return structured MISP events. |
rbl |
Module to check an IPv4 address against known RBLs. |
rdap |
An expansion module to query the public RDAP bootstrap (rdap.org) for registration data of a domain, hostname, IP address or URL. |
recordedfuture |
Module to enrich attributes with threat intelligence from Recorded Future. |
reversedns |
Simple Reverse DNS expansion service to resolve reverse DNS from MISP attributes. |
reversinglabs_malware_presence |
Retrieve ReversingLabs file reputation and malware presence. |
reversinglabs_spectra_analyze |
Module to enrich file hashes, domains, IPs and URLs with ReversingLabs Spectra Analyze threat intelligence. |
reversinglabs_spectra_intel_submission |
Submit a file hash, URL or attachment to ReversingLabs Spectra Intelligence dynamic analysis. |
ripestat |
Query RIPEstat for the announcing ASNs, prefixes and ASN holders of IP, prefix and AS attributes. |
rst_cs_beacon |
Scan a target IP[:port] for a Cobalt Strike beacon configuration via RST Scan API. |
rst_favicon |
Fetch a target’s favicon (image + all hashes for Shodan/Netlas/Censys pivoting) via RST Scan API. |
rst_html |
Fetch rendered HTML body or extracted JavaScript for a URL/IP target via RST Scan API. |
rst_ioc |
Enrich indicators with RST Cloud threat intelligence. Returns an rst-ioc object (score, attribution, geo/ASN for IPs, DNS/WHOIS for domains, parsed components for URLs, related hashes for file hashes) linked back to the enriched attribute. |
rst_noise_control |
Check whether a value (IP, domain, URL or hash) is known-good / noise via RST Noise Control. Returns an rst-noise object (verdict, category) linked back to the enriched attribute. |
rst_screenshot |
Capture a page screenshot (first/full/last frame) of a URL/IP target via RST Scan API. |
rst_ssl |
Fetch the SSL certificate for an IP[:port] as an x509 object via RST Scan API. |
rst_whois |
Retrieve parsed WHOIS information for a domain via RST Cloud. |
rulezet_validator |
Validate the syntax of detection rules (YARA, Sigma, Suricata, Zeek, NOVA, Wazuh, Kunai, NSE, CRS, Splunk, Elastic, KQL, ATR, PLUM, Sagan) with the Rulezet API. |
scanmalware |
Query ScanMalware for subdomains, browser-observed hosts and sandbox scan results. |
securitytrails |
An expansion modules for SecurityTrails. |
shadowtrackr |
Enrich IP addresses with ShadowTrackr false-positive and infrastructure context. |
sherlock |
Find social media accounts by username with Sherlock. |
shodan |
Module to query on Shodan. |
shodan_internetdb |
Look up exposed services, hostnames, CPEs and vulnerabilities in the free Shodan InternetDB API. |
shuffle_datastore_lookup |
Look up a MISP observable’s key in a selected Shuffle organization and Datastore category. |
siberkapan |
Hover and expansion module to look up an IP address in SiberKapan threat intelligence. |
sigma_queries |
An expansion hover module to display the result of sigma queries. |
sigma_syntax_validator |
An expansion hover module to perform a syntax check on sigma rules. |
sigmf_expand |
Expands a SigMF Recording object into a SigMF Expanded Recording object, extracts a SigMF archive into a SigMF Recording object. |
silentpush |
Retrieve domain and IP risk and infrastructure context from Silent Push. |
sochain |
Get the balance, activity, counterparties and address poisoning findings of a BTC, LTC, DOGE or ZEC address from SoChain. |
socialscan |
A hover module to get information on the availability of an email address or username on some online platforms. |
socradar_lookup |
Enrich MISP attributes with SOCRadar threat intelligence. Queries SOCRadar IoC Enrichment API for categorization, malware families, threat actors, confidence scores, feed source history, and geographic attribution. |
sophoslabs_intelix |
An expansion module to query the Sophoslabs intelix API to get additional information about an ip address, url, domain or sha256 attribute. |
sourcecache |
Module to cache web pages of analysis reports, OSINT sources. The module returns a page-capture object holding the cached page. |
spamcop |
Check an IPv4 address against the SpamCop Blocking List (SCBL). |
ssh_fingerprint |
Grab SSH server fingerprint from an IP and return as passive-ssh MISP object. |
ssllabs |
Retrieve SSL Labs API v4 TLS assessments, endpoint grades and certificate details for a hostname. |
stairwell |
Module to query the Stairwell API to get additional information about the input hash attribute |
stix2_pattern |
Generate a validated STIX 2.1 pattern from a MISP attribute. |
stix2_pattern_syntax_validator |
An expansion hover module to perform a syntax check on stix2 patterns. |
team_cymru_scout |
Retrieve Scout foundation intelligence for an IP address or search for a domain. |
team_cymru_scout_search |
Run an explicit Scout search query and import the returned intelligence. |
threatcrowd |
Module to get information from ThreatCrowd. |
threatfox |
Module to search for an IOC on ThreatFox by abuse.ch. |
threatminer |
Module to get information from ThreatMiner. |
tines_record_lookup |
Find a MISP observable in a selected Tines record type and field using Records v2 search. |
tls_certificate_check |
Extract TLS certificate details from a domain and return as x509 MISP object. |
torq_observable_lookup |
Look up a MISP observable in Torq and return verified matches with reputation and threat intelligence. |
triage_query |
Retrieve Triage overview reports by trusted report link or search existing analyses by file hash. |
triage_submit |
Module to submit samples to tria.ge |
trustar_enrich |
Module to get enrich indicators with TruSTAR. |
tweetfeed |
Look up an IOC in TweetFeed (tweetfeed.live), the free CC0 feed of URLs, domains, IPs and hashes shared by the infosec community on X/Twitter: who reported it and when, the source tweets and hashtags, cross-feed corroboration,… |
unpac_me |
Find existing UnpacMe unpacking results for a SHA-256 hash. |
url_dns |
Resolve URL hosts into IPv4/IPv6 IP-port objects and IPv4 ASN objects. |
url_shortener |
Resolve known HTTP(S) URL shorteners into a shortened-link object. |
urlhaus |
Query of the URLhaus API to get additional information about the input attribute. |
urlscan |
An expansion module to query urlscan.io. |
validin |
Validin internet dataset expansion. Returns dns-records, web crawls, registration (WHOIS) records, and certificates from Validin’s historic internet intelligence dataset. |
variotdbs |
An expansion module to query the VARIoT db API for more information about a vulnerability. |
virustotal |
Enrich observables with the VirusTotal v3 API |
virustotal_downloader |
Download an existing file from VirusTotal by hash. |
virustotal_public |
Enrich observables with the VirusTotal v3 public API |
virustotal_upload |
Module to push malware samples to VirusTotal |
vmray_analyzer |
Retrieve existing VMRay sample and analysis context by file hash. |
vmray_submit |
Module to submit a sample to VMRay. |
vmware_nsx |
Module to enrich a file or URL with VMware NSX Defender. |
vuldb |
Expand CVEs, VulDB identifiers and CPEs using the VulDB API. |
vulndb |
Module to query VulnDB (Flashpoint). |
vulnerability_lookup |
Expand vulnerabilities and CPEs with Vulnerability Lookup advisories and enrichment |
vulners |
An expansion hover module to expand information about CVE id using Vulners API. |
vysion |
Module to enrich the information by making use of the Vysion API. |
webarchive |
Query the Internet Archive Wayback Machine for an existing web page snapshot. |
whisper |
Enrich IPs, domains, and ASNs with threat intelligence and infrastructure context from the Whisper graph. |
whois |
Module to query a local instance of uwhois (https://github.com/rafiot/uwhoisd). |
whoisfreaks |
An expansion module for https://whoisfreaks.com/ that enriches a domain or an IP address. |
wiki |
Look up Wikidata labels and aliases and return related annotation objects. |
xforceexchange |
An expansion module for IBM X-Force Exchange. |
xlsx_enrich |
Module to extract freetext from a .xlsx document. |
xposedornot |
Query the XposedOrNot API to check whether an email address appears in known data breaches. |
yara_query |
The module takes a hash attribute (md5, sha1, sha256, imphash) as input, and is returning a YARA rule from it. |
yara_syntax_validator |
An expansion hover module to perform a syntax check on if yara rules are valid or not. |
yeti |
Module to process a query on Yeti. |
zetalytics |
Look up passive DNS records in Zetalytics. |
zoomeye |
Search ZoomEye API v2 for IP addresses, domains, hostnames and SHA-1 certificate fingerprints. |
Export modules (39)
| Module | Declared purpose |
|---|---|
bpf_export |
Export IDS-marked event and object network attributes as a tcpdump/libpcap capture filter. |
cef_export |
Module to export a MISP event in CEF format. |
cisco_acl_export |
Export IDS-marked network attributes as Cisco IOS/IOS-XE IPv4 and IPv6 ACL fragments. |
cisco_asa_export |
Export Cisco ASA 9.x unified IPv4/IPv6 extended access lists. |
cisco_firesight_manager_ACL_rule_export |
Module to export malicious network activity attributes to Cisco fireSIGHT manager block rules. |
csv_export |
Export event and object attributes of any type as CSV. |
defender_endpoint_export |
Validated, table-specific Defender hunting queries with bounded indicator batches |
elastic_ecs_export |
Export event and object indicators as ECS threat indicators in Elasticsearch Bulk NDJSON. |
fortios_export |
Export FortiOS 7.4 unified firewall policy and dependent objects. |
geojson_export |
Export geojson attachments and geolocation objects as GeoJSON. |
goamlexport |
This module is used to export MISP events containing transaction objects into GoAML format. |
gpx_export |
Export gpx attachments and geolocation objects as GPX. |
junos_export |
Export Junos stateless inet/inet6 firewall filter terms. |
kml_export |
Export geolocations as KML or return a single original KML attachment unchanged. |
kmz_export |
Export original KML/KMZ datasets and geolocations as a KMZ package. |
liteexport |
Lite export of a MISP event. |
mass_eql_export |
Export MISP event in Event Query Language |
mikrotik_export |
Export MikroTik RouterOS v7 IPv4/IPv6 firewall filter commands. |
netfilter_export |
Export IDS-marked event and object network attributes as nftables block or logging rules. |
nexthinkexport |
Nexthink NXQL query export module |
nmea_export |
Export original NMEA 0183 log attachments in a ZIP archive. |
osqueryexport |
Export MISP event and object indicators as an osquery query pack. |
owasp_crs_export |
Export IDS-marked proxy and HTTP indicators as custom ModSecurity rules alongside OWASP CRS. |
panos_export |
Export PAN-OS local security rules and custom TCP/UDP services. |
pdfexport |
Simple export of a MISP event to PDF. |
pf_export |
Export IDS-marked event and object network attributes as OpenBSD PF block or logging rules. |
qradar_reference_set_export |
Export deduplicated, typed MISP indicators as QRadar reference-set CSV or JSON values. |
sigma_export |
Export stored Sigma rules and optionally generate Windows IOC detections. |
splunk_export |
Export event and object indicators as a Splunk CSV lookup with CIM field mapping hints. |
squid_export |
Export IDS-marked event and object attributes as Squid proxy ACLs and deny rules. |
stix2_pattern_export |
Export stored STIX patterns and generate patterns from IDS-marked MISP attributes. |
threatStream_misp_export |
Module to export a structured CSV file for uploading to threatStream. |
threat_connect_export |
Module to export a structured CSV file for uploading to ThreatConnect. |
timesketch_export |
Export supported timestamped observations as Timesketch JSONL with MISP and source references. |
virustotal_collections |
Creates a VT Collection from an event iocs. |
vt_graph |
This module is used to create a VirusTotal Graph from a MISP event. |
wazuh_cdb_export |
Export MISP event and object indicators as a typed Wazuh CDB source list. |
yara_export |
Export stored YARA collections and optionally generate literal IOC content searches. |
zeek_intel_export |
Export validated MISP event and object indicators as a Zeek Intel Framework feed. |
Action modules (19)
| Module | Declared purpose |
|---|---|
cortex_xdr_ioc_publish |
Upload missing Cortex XDR IOC rules from IDS-marked MISP event and object attributes. |
cortex_xsoar_incident_create |
Create a Cortex XSOAR 8 incident with a MISP event reference and selected-data counts. |
crowdstrike_ioc_publish |
Create and renew module-owned Falcon custom IOCs from MISP event and object attributes. |
doppel_alert_takedown |
Create Doppel alerts or explicitly request takedown for an existing alert. |
export_sentinel |
Export indicators to Microsoft Sentinel or Microsoft Defender. Requires an existing installation of MISP2Sentinel or MISP2Defender. |
irc |
Send a message to an IRC channel. |
matrix |
Send a message to an unencrypted Matrix room. |
mattermost |
Simplistic module to send message to a Mattermost channel. |
n8n_webhook |
Send selected MISP event attributes to an authenticated n8n Webhook trigger. |
nextcloud_talk |
Simplistic module to send a message to a Nextcloud talk conversation. |
osquery_pack_publish |
Publish a MISP query pack to a configured local osquery pack directory. |
qradar_reference_set_publish |
Publish typed MISP indicators to an existing QRadar reference set and explicit domain. |
sentinelone_ioc_publish |
Publish MISP event and object indicators to SentinelOne Threat Intelligence with explicit scope. |
shuffle_workflow_execute |
Start a Shuffle workflow with selected MISP event and object attributes as its JSON execution argument. |
signal |
Send a message to Signal recipients or a group through signal-cli-rest-api. |
slack |
Simplistic module to send messages to a Slack channel. |
tines_case_create |
Create a Tines Cases v2 case with a MISP event reference and selected-data counts. |
torq_case_create |
Create a Torq case with a MISP event reference, provenance tags and selected-data counts. |
wazuh_cdb_publish |
Upload MISP event and object indicators to an explicitly named Wazuh CDB source list. |
Related guidance and source contracts
- Modules for discovery, service configuration and differences between the MISP and module-service APIs.
- MISP Objects, Categories and Types and Correlation for representation and comparison.
- Value Intelligence and Pivoting for contextual analysis of selected values.
- Automation and PyMISP for repeatable integrations.
- The reviewed module documentation for importer selection, timestamp handling, limits, external effects and output contracts.
- ADTimeline’s collection and analysis guide for directory collection scope and replication-metadata interpretation.
The editable Mermaid sources are the DFIR lifecycle, Active Directory analysis, timeline exchange and the hunting feedback loop. Their committed SVGs use the book’s shared theme for HTML, PDF and EPUB.

















