The cards below come from the same capability catalogue used by the live Forensic Lab. Each card tells you what the domain is for, what it accepts, how it is processed and the important boundary you must understand.
01
Evidence Collection & Intake
Document authority, scene/source state, identifiers, provenance, preservation and custody before examination.
Typical inputs- physical/digital evidence
- provider productions
- exports
- forensic images
Processing pathbuilt_in
- built-in evidence register
- dual-hash preservation
- custody/audit chains
Important limitPhysical safety, seizure authority, packaging, Faraday isolation and organizational SOPs remain examiner responsibilities.
02
Computer & Disk Forensics
Preserve and examine Windows, macOS and Linux computer evidence with built-in artefact parsing plus established-engine imports/connectors.
Typical inputs- preserved files
- browser SQLite
- EVTX/log exports
- TSK/Autopsy/KAPE/Zimmerman/Plaso exports
- E01/raw via validated engine
Processing pathhybrid
- built-in hash/metadata/browser
- TSK/Autopsy import
- KAPE/Zimmerman import
- Plaso import
Important limitRaw/E01 filesystem traversal, unallocated-space recovery and carving use validated external engines rather than unvalidated PHP reimplementations.
03
Filesystem, Imaging & Recovery
Track forensic images, partitions, filesystems, deleted-file recovery, carving, keyword/string searches and write-protection validation.
Typical inputs- E01/Ex01/raw images
- TSK/libewf exports
- carving/recovery exports
- CFTT/Federated test reports
Processing pathexternal_engine
- libewf/TSK boundary
- PhotoRec/tsk_recover/bulk_extractor imports
Important limitBlock-device imaging and hardware write blocking require validated acquisition tools/hardware and are not emulated by the web app.
04
Remote Endpoint Collection
Normalise focused collections from authorised remote-response tools while preserving collection scope and provenance.
Typical inputs- Velociraptor collections
- osquery results
- EDR/exported triage bundles
- KAPE remote collections
Processing pathimport
- Velociraptor/osquery/KAPE adapters
Important limitRemote execution requires the organization’s authorised endpoint tooling and credentials; this product does not deploy covert agents.
05
Damaged Media & Data-Recovery Casework
Record condition, recovery attempts and specialist imaging/recovery outputs for damaged HDD/SSD/NVMe/NAND media.
Typical inputs- ddrescue maps/logs
- specialist recovery manifests
- partial images
Processing pathspecialist_boundary
- recovery-log adapter
- specialist-lab connector boundary
Important limitClean-room repair, chip transplant, NAND reconstruction and invasive hardware recovery require a qualified specialist laboratory.
06
Android, iPhone & Mobile App Forensics
Preserve lawfully accessible mobile data and analyse trusted backups, exports and forensic reports including communications, payments, app usage, Wi-Fi, location, health/fitness and social artefacts.
Typical inputs- trusted iOS backups
- Android shared/exported data
- ALEAPP/iLEAPP
- vendor forensic reports
- UICC/SIM exports
Processing pathhybrid
- desktop trusted acquisition
- ALEAPP/iLEAPP import
- vendor-report adapter
Important limitNo passcode bypass, exploit acquisition, Secure Enclave bypass or proprietary full-filesystem extraction is included.
07
Memory / RAM Forensics
Normalise captured-memory results for processes, network connections, injected-code indicators, handles and related volatile artefacts.
Typical inputs- Volatility 3 JSON/CSV
- memory acquisition manifests
Processing pathexternal_engine
Important limitMemory acquisition and plugin parsing remain validated external-engine functions.
08
Network / Packet Forensics
Reconstruct network activity from packet, flow, DNS, HTTP, TLS and IDS/NSM records.
Typical inputs- tshark/Wireshark exports
- Zeek logs
- Suricata EVE
- PCAP/PCAPNG via desktop engine
Processing pathhybrid
- tshark
- Zeek
- Suricata adapters
Important limitDeep protocol dissection and stream reconstruction require installed packet-analysis tooling.
09
Wi-Fi, Bluetooth & Wireless Evidence
Correlate supplied wireless scan, association, Bluetooth and device-network records.
Typical inputs- Wi-Fi history exports
- pcap metadata
- Bluetooth logs
- mobile/OS wireless artefacts
Processing pathimport
- generic wireless-event adapter
- mobile/endpoint imports
Important limitActive RF interception, spectrum capture and protected wireless decryption require lawful specialist equipment/workflows.
10
Malware Triage & Reverse-Engineering Imports
Triage suspicious files without executing them and import results from rule engines, antivirus, sandboxes and reverse-engineering tools.
Typical inputs- files
- YARA
- ClamAV
- sandbox reports
- static-analysis exports
Processing pathhybrid
- hash sets
- YARA/ClamAV
- sandbox/reverse-engineering adapters
Important limitDynamic execution belongs in an isolated malware laboratory; imported detections are indicators, not attribution or intent conclusions.
11
Browser & Web Artefacts
Analyse histories, downloads, searches, bookmarks, cache/export metadata and browser databases from supported acquisitions.
Typical inputs- Chromium History
- Safari History.db
- Firefox Places exports
- browser forensic exports
Processing pathbuilt_in
- built-in SQLite browser parsing
- Firefox/export adapters
Important limitEncrypted credentials/session secrets are not extracted for account takeover.
12
Email & Messaging Evidence
Read message headers/routes and normalise authorised mailbox/message exports.
Typical inputs- EML
- MBOX/provider exports
- message-trace exports
Processing pathbuilt_in
- built-in RFC822 parser
- mail export normaliser
Important limitDeleted/restricted provider-side data requires an authorised provider export/connector.
13
Cloud & SaaS Forensics
Preserve collection manifests and normalise authorised cloud audit, storage and SaaS exports.
Typical inputs- AWS
- Azure/Entra
- Google Cloud
- Microsoft 365
- SaaS provider exports
- cloud collection manifests
Processing pathhybrid
- cloud audit normaliser
- provider connector boundary
Important limitPrivate provider-side acquisition requires legitimate credentials, legal process or provider tooling.
14
Telecom / CDR / BTS
Normalise calls, messages and tower/site records supplied by an authorised source.
Typical inputs- CDR CSV
- BTS/site tables
- provider productions
- authorised telecom connector
Processing pathhybrid
- CDR/BTS normaliser
- provider plug-in boundary
Important limitSubscriber data and provider-side live/historical network location require authorised operator access. CDR/site records do not by themselves identify who used a device or pinpoint an exact handset position.
15
Historical Cell-Site & RF Analysis
Correlate supplied CDR/site/sector records and RF survey measurements without overstating location precision.
Typical inputs- CDR/BTS
- sector/azimuth tables
- drive-test/RF survey CSV
- mapping exports
Processing pathhybrid
- HCSA/RF deterministic import
- telecom-provider boundary
Important limitRF propagation and historical cell-site interpretation require trained experts, validated measurements and jurisdiction-appropriate methodology; the system does not perform live covert tracking.
16
Financial & Transaction Tracing
Follow supplied bank, card, UPI, gateway and wallet transaction records and correlate references/times/accounts.
Typical inputs- bank/UPI CSV
- gateway exports
- mobile-payment artefact exports
Processing pathbuilt_in
- transaction normaliser
- entity correlation
Important limitPrivate financial data requires a lawful source export or authorised connector.
17
Cryptocurrency & Blockchain Analysis
Follow supplied/public-chain transactions, addresses, timestamps and transaction identifiers without guessing ownership.
Typical inputs- transaction CSV/JSON
- wallet/address lists
- public explorer exports
Processing pathimport
- chain-export normaliser
- entity correlation
Important limitAddress ownership/attribution is never inferred solely from an address or transaction graph.
18
Photo / Video / Document Metadata
Preserve media/documents and extract or import available metadata, hashes, codec/container properties and GPS fields.
Typical inputs- photos
- video
- audio
- documents
- ExifTool
- ffprobe
Processing pathhybrid
- hash/metadata
- ExifTool/ffprobe adapters
Important limitMetadata can be absent, transformed or manipulated and must be corroborated.
19
Forensic Image Analysis & Authentication
Manage integrity, enhancement provenance and specialist image-authentication/content-analysis results.
Typical inputs- image files
- camera/scanner test records
- authentication/enhancement reports
Processing pathhybrid
- metadata/fixity
- specialist report adapter
Important limitSource-camera attribution, manipulation/deepfake conclusions and photogrammetric interpretation require validated specialist methods and human review.
20
Forensic Video & DVR Evidence
Preserve video/DVR exports, normalise codec/timing metadata and import forensic video-analysis results with transformation provenance.
Typical inputs- video files
- DVR exports
- ffprobe/FFmpeg reports
- video-analysis reports
Processing pathhybrid
- ffprobe/FFmpeg metadata import
- DVR/specialist report adapter
Important limitProprietary DVR extraction, frame-accurate interpretation and authenticity opinions may require specialist hardware/software and examiner review.
21
Forensic Audio Evidence
Preserve audio, record processing provenance and import codec/waveform/enhancement/specialist results.
Typical inputs- audio files
- ffprobe/FFmpeg/SoX reports
- forensic-audio reports
Processing pathhybrid
- audio metadata adapter
- specialist report adapter
Important limitSpeaker comparison, intelligibility enhancement conclusions and authenticity opinions require qualified forensic-audio methods and review.
22
Online Content Preservation
Preserve public-facing web content captures and normalise HAR/WARC/screenshot/export provenance.
Typical inputs- HAR
- WARC metadata
- web capture manifests
- screenshots/PDF exports
Processing pathbuilt_in
- HAR/WARC adapter
- fixity/provenance
Important limitCollection must respect applicable authority, terms, privacy and platform constraints; private-account bypass is not performed.
23
OSINT & Threat Intelligence
Correlate public or lawfully supplied indicators and STIX objects.
Typical inputs- STIX 2 JSON
- IOC lists
- public research exports
Processing pathimport
- STIX/IOC normaliser
- entity correlation
Important limitThe core does not access private accounts, bypass platform controls or make identity attribution solely from public indicators.
24
Server, Web, Application & Service Logs
Normalise server/application/security records to reconstruct incidents.
Typical inputs- Apache/Nginx
- auth/system logs
- application logs
- SIEM exports
Processing pathbuilt_in
- generic event normalisers
Important limitConclusions are bounded by source log completeness, clock accuracy and retention.
25
Identity, Authentication & Access Forensics
Rebuild sign-ins, MFA, account changes, VPN/SSO and access events from authorised audit logs.
Typical inputs- AD/Entra
- Okta/Auth0
- VPN/RADIUS
- SSO exports
Processing pathimport
- identity-event normaliser
Important limitRequires authorised identity-provider audit exports/connectors.
26
Database & SQLite Forensics
Review preserved SQLite databases and imported database audit/query/transaction records.
Typical inputs- SQLite copies
- audit/query logs
- specialist recovery exports
Processing pathhybrid
- read-only SQLite metadata
- database audit adapters
Important limitProprietary transaction-log/page recovery requires engine-specific specialist tooling.
27
Virtual Machine, Hypervisor & Container Forensics
Analyse supplied VM snapshots, hypervisor records, container events and Kubernetes audit data.
Typical inputs- VM exports
- Docker/Podman events
- Kubernetes audit
- hypervisor logs
Processing pathimport
- Kubernetes/container normalisers
Important limitGuest filesystem examination follows the endpoint/filesystem engine boundary.
28
IoT, Wearable & Embedded Evidence
Preserve and normalise lawfully acquired smart-home, router, wearable and embedded-device logs/exports.
Typical inputs- device logs
- firmware images
- router exports
- wearable exports
Processing pathhybrid
- hash/metadata
- IoT export adapters
Important limitChip-off/JTAG/ISP, proprietary firmware decoding and destructive hardware methods require qualified specialist tooling.
29
Vehicle Infotainment & Telematics
Normalise authorised vehicle/infotainment exports including paired devices, navigation destinations, events and telematics records.
Typical inputs- vehicle forensic reports
- infotainment exports
- telematics CSV/JSON
Processing pathhybrid
- vehicle-export adapter
- vendor/specialist boundary
Important limitPhysical acquisition and proprietary decoding are vehicle/vendor specific and may require specialist tools.
30
Drone / UAS Forensics
Normalise aircraft/controller/app flight logs, GPS paths, launch/landing points, telemetry and device identifiers.
Typical inputs- flight logs
- controller exports
- mobile app reports
- vendor forensic exports
Processing pathhybrid
- drone-flight adapter
- vendor/specialist boundary
Important limitDamaged aircraft, chip-level extraction, proprietary decoding and RF countermeasure analysis require specialist handling.
31
Encryption & Protected Evidence
Track encryption state, supplied keys/recovery material and outputs from authorised specialist decryption workflows.
Typical inputs- encryption metadata
- recovery-key records
- decrypted forensic copies
- specialist reports
Processing pathspecialist_boundary
- provenance/fixity
- specialist boundary
Important limitNo online credential attacks, credential theft, covert key capture or authentication bypass is provided.
32
Super Timeline & Relationship Graph
Combine normalised records into time-ordered and linked-entity views with source-time provenance.
Typical inputs- all normalised case records
- Plaso/Timesketch exports
Processing pathbuilt_in
- built-in timeline/entities
- Plaso/Timesketch import
Important limitTimeline quality is bounded by source timestamp quality, clock drift and timezone context.
33
Archiving, Retention & Fixity
Create self-contained case archives and verify retained evidence/report fixity over time.
Typical inputs- case evidence
- case snapshot
- retention metadata
Processing pathbuilt_in
- built-in archive/fixity ledger
Important limitOrganizational redundancy, off-site storage, legal holds and retention policy remain administrative responsibilities.
34
Authorised Security Assessment
Check approved systems for exposed services and import vulnerability/web-assessment results to recommend remediation.
Typical inputs- authorised target
- Nmap
- Nessus/OpenVAS
- ZAP/Burp reports
Processing pathhybrid
- signed-ticket safe Nmap
- scanner imports
Important limitNo exploit delivery, password attack, persistence, stealth, destructive testing or unauthorized access is included.