DON27BZ02-NV006 TITLE: Mobile Vehicle Forensics

COMPONENT TECHNOLOGY PRIORITY AREA(S): Human-Machine Interfaces;Integrated Sensing and Cyber;Trusted AI and Autonomy

PROJECTED CMMC LEVEL REQUIREMENT: Level 2 (Self)

OBJECTIVE: Design, develop, and demonstrate a ruggedized, field-deployable vehicle forensics device capable of non-destructive, rapid data triage and extraction.

DESCRIPTION: Operational Need & Gap: During tactical site exploitation (TSE), Marine Corps and Joint operators require immediate, field-deployable hardware and software to recognize, preserve, and collect materials of forensic value. While multi-purpose forensic kits exist to process traditional materials, a critical intelligence gap remains regarding vehicle-derived data. Modern vehicles function as mobile data hubs featuring advanced navigation, localized track logs, and cached external device connections. Exploiting this telematics and informatics data is vital for generating actionable intelligence, mapping networks, and establishing identity dominance.

The Problem (Technological Fragmentation): The primary barrier to tactical vehicle exploitation is severe technological fragmentation. Current vehicle forensic solutions are often designed for controlled laboratory environments. Because In-Vehicle Infotainment (IVI) systems and Electronic Control Units (ECUs) rely on proprietary software architectures and inconsistent file structures, existing tools are often restricted to narrow manufacturer subsets. Consequently, field operators may be forced to perform invasive, time-consuming physical disassembly of the vehicle dashboard—a method that is untenable in many field environments.

Scope of Effort: This SBIR topic seeks innovative proposals to develop a low-SWaP (Size, Weight, and Power), ruggedized, all-in-one device that automates the forensic exploitation of vehicle data systems. The system must interface via standard external access points (e.g., On-Board Diagnostic [OBD-II] ports or Universal Serial Bus [USB]); automatically profile the vehicle’s make, model, year, and digital architecture; and execute an automated script to extract and structure data. Crucially, these features must be achieved through a non-invasive approach requiring no component disassembly, while maintaining strict forensic data integrity and verifiable accuracy.

The system must seamlessly interface with a broad registry of modern commercial and civilian vehicles across diverse model years, makes, and international manufacturers. Specifically, the device must extract and normalize data from disparate telematics systems (e.g., embedded GPS, localized track logs) and informatics modules (e.g., infotainment systems, paired Bluetooth logs, Wi-Fi cache, and cellular device pairings) without requiring laboratory-grade component disassembly.

Performance Goals:

• Threshold (Minimum): Demonstrate compatibility with representative samples of common vehicles; extract high-priority telematics (i.e., GPS, route history) and informatics (paired device logs) in under 15 minutes with verifiable accuracy (i.e., comparison with test data collected separately); packaged in a portable, field-ruggedized kit.
• Objective (Ideal): A pocket-sized, plug-and-play device that requires minimal operator training; demonstrates a modular path to broad vehicle compatibility; and extracts a comprehensive forensic data set in under 5 minutes via an intuitive, automated interface.

PHASE I: Develop a technical approach and assess the feasibility of a mobile, software-intelligent vehicle forensics capability that enables rapid data extraction from vehicle telematics (e.g., GPS, navigation logs) and infotainment systems (e.g., paired Bluetooth devices, call histories) and prioritizes universal applicability across diverse vehicle head units, makes, and models, avoiding dependencies on specific hardware teardowns.

Required Phase I deliverables include:

• A comprehensive feasibility study and initial system design architecture.
• An assessment of projected data extraction speeds, performance metrics, and technical limitations.
• A detailed Phase II development plan mapping out performance goals, key technical milestones, and risk mitigation strategies.

PHASE II: Develop, demonstrate, and validate a functional, field-ready prototype based on the feasibility concepts established in Phase I. Focus on expanding compatibility across a broader registry of vehicle makes, models, and head unit architectures, while increasing the depth and fidelity of extracted telematics and informatics data. Ensure that the prototype is ruggedized or packaged appropriately for expeditionary testing.

Required Phase II deliverables include:

• A fully functional prototype vehicle forensics tool (software, hardware, or hybrid) ready for Government evaluation.
• Demonstrations of the tool’s capability in an operationally relevant environment against representative vehicle targets.
• Complete technical documentation, including system architecture, user operating manuals, and finalized performance data metrics.
• A commercialization and transition plan detailing manufacturing viability and scaling strategies for military integration.

PHASE III DUAL USE APPLICATIONS: Upon successful completion of Phase II, support technology transition into a Phase III acquisition pathway for integration into the Forensics Dominance System – Marine Corps (FDS-MC) tactical site exploitation kits. Given the Joint requirement, position this rapid field-extraction capability for immediate transition to U.S. Special Operations Command (USSOCOM) exploitation programs and other Department of War service forensic intelligence elements.

In the commercial sector, this software-intelligent tool has direct dual-use applicability for federal, state, and local civilian law enforcement agencies by significantly modernizing digital forensics units through enabling roadside or scene-of-crime vehicle data extraction, thus bypassing extensive laboratory backlogs. Additionally, the capability will serve private sector markets, including automotive insurance fraud investigators, crash reconstruction experts, and corporate cybersecurity firms analyzing fleet vehicle telematics breaches.

REFERENCES:

1. "iVe Vehicle and System Support." Berla Corp., 2024. https://berla.co
2. "CAN Bus Explained - A Simple Intro." CSS Electroinics, 2024. https://www.csselectronics.com/pages/can-bus-simple-intro-tutorial
3. "NIST Special Publication 800-101 Revision 1, Guidelines on Mobile Device Forensics." National Institute of Standards and Technology, 2014. https://csrc.nist.gov/publications/detail/sp/800-101/rev-1/final
4. "Rusolut Vehicle Data Reconstructor." Rusolut, 2024. https://rusolut.com/vehicle-data-recovery/ https://rusolut.com/vehicle-data-reconstructor/
5. "United States Special Operations Command (USSOCOM) Tactical Forensics Event (TFE) 21.1, 2025".

https://www.vulcan-sof.com/login/ng2/collection/a1e8fd06-ac2a-4fc6-bfb8-b1fcbe101b1c

KEYWORDS: Vehicle; forensics; information; collection; telematics; informatics

TPOC 1: Christopher Outlaw
christopher.j.outlaw.civ@us.navy.mil

TPOC 2: Kristin DeAngles
kristin.r.deangles.civ@us.navy.mil