Expert Diesel Knowledge. Always Free.
Fleet technician and driver reviewing an Electronic Logging Device and diagnostic equipment inside a semi-truck cab while checking ELD cybersecurity and vehicle network connections.

ELD Cybersecurity: How Hackers Target Connected Trucks

By Michael Nielsen, Publisher | 15+ Years in Diesel Repair

Last Updated: October 2026

⏱ Estimated reading time: 14 minutes

An Electronic Logging Device (ELD) is a small computer wired into a truck's data network, and ELD cybersecurity is the work of keeping that computer from becoming a way into the truck or the fleet. Researchers have shown that some ELDs can be reprogrammed by someone standing nearby, and that the truck can then be slowed.

This guide from Heavy Duty Journal (HDJ), written by publisher Michael Nielsen, explains what the research, the Federal Bureau of Investigation (FBI) and the National Motor Freight Traffic Association (NMFTA) actually say, how to vet a provider, and how to secure the devices you already run.

The earlier version leaned on figures and incidents HDJ could not verify. As of October 2026, HDJ found no public report of criminals compromising a fleet through an ELD. The risk is documented in research and government warnings, and that is how this guide treats it.

Key Takeaways

  • ✓The risk is real but unproven in the field. ELD cybersecurity risk is proven in the lab: researchers took over a test ELD and slowed a truck on a closed airfield. HDJ found no confirmed attack on a real fleet.
  • ✓Defaults are the weak point. The research and a federal advisory both found default Wi-Fi and web passwords on ELDs.
  • ✓Federal rules do not test security. The FBI said in 2020 that the ELD mandate has no cybersecurity requirements for makers and no third-party testing.
  • ✓Ask who really makes the device. NMFTA says many ELDs sold under different names share the same software and hardware.
  • ✓Start with an inventory. Know which ELDs you run, which wireless features are on and whether the passwords are unique.
In This Guide

What ELD Cybersecurity Is and Why It Matters

Federal Motor Carrier Safety Administration (FMCSA) rules require most commercial drivers to record hours of service on an ELD. Under Appendix A to Subpart B of Part 395, the device must be synchronized with the engine and, on model year 2000 and newer trucks with an engine control module (ECM), must establish a link to it. That link is what makes the device useful, and it is also what makes it a security question.

The FBI's Private Industry Notification of July 21, 2020 says ELDs connect to the ECM and allow wireless connectivity, which bridges vehicle systems and wireless networks. The researchers' test device plugged into the nine-pin diagnostic port and drew power from it.

ELD cybersecurity therefore covers two things: the device in the truck, and the accounts and cloud systems behind it. The evidence is stronger for the first than for the second, and this guide keeps them separate.

“

Editorial Insight

The HDJ Perspective

According to Heavy Duty Journal, ELD cybersecurity starts at purchase, because an ELD should be bought like any other computer connected to a truck: the question is not only whether it meets the hours-of-service rule but who has tested it. In HDJ's editorial judgment, fleets do not need panic. They need a vendor questionnaire, unique passwords and the habit of asking where a device's software comes from.

What the Evidence Shows About ELD Cybersecurity

The best-documented work is from Colorado State University. Its Colorado State University research page and 2024 vehicle security workshop paper report three problems in a popular off-the-shelf ELD: wireless control that can send arbitrary messages to the truck's network, malicious firmware that can be loaded, and a possible truck-to-truck worm. The authors do not name the device, and say many rebranded ELDs share similar designs.

Testing was mostly on a bench, plus a 2014 Kenworth T270 research truck. On an airfield at about 20 miles per hour, an attacker joined the ELD's Wi-Fi and reflashed it, and the truck slowed as the device flooded the network with malicious torque-control messages. The authors chose a slowdown payload and did not test anything more dangerous.

The worm was shown only on development boards, not on trucks, and the authors say they held back a full proof of concept. In a stationary test, the boards connected from up to about 12 parking spaces away, roughly 120 feet, and spread in under 30 seconds under the best conditions.

A Cybersecurity and Infrastructure Security Agency (CISA) advisory ICSA-24-093-01 covers the IOSiX IO-1020 Micro ELD, versions before 360. It lists a default Wi-Fi password, a default web password and code downloaded without an integrity check, and says the flaws are not remotely exploitable. CISA also notes it knows of no public exploitation reported to it.

The Colorado State page links that advisory, but the paper does not name its test device, so HDJ cannot say they are the same product. The FBI's 2020 notice cites no actual attacks on trucking companies. Its April 2026 cargo theft alert does not mention ELDs, and describes phishing and account takeover instead.

How an ELD Connects to the Truck and Your Network

An ELD touches three networks. The first is the truck: the device reads engine data from the vehicle data bus, the same network HDJ's CAN bus troubleshooting guide explains for technicians. Anything that can send messages on that bus can affect what the truck's other modules see, which is why ELD cybersecurity starts at the port.

The second is short-range wireless. The tested ELD had Wi-Fi and Bluetooth on by default, according to the researchers' paper. Drivers commonly pair phones or tablets to these devices, which is why the unit has to resist strangers within range, not just unknown people on the internet.

The third is the cloud. The ELD sends records to the provider, and the fleet's dispatchers and safety staff log in to read them. Those accounts are ordinary web logins, so they face the same phishing and password risks as any other business system.

What an ELD collects beyond the regulatory minimum depends on the vendor. HDJ found no neutral source for the earlier transmission frequencies and removed them. Ask each provider for a written list of data collected, where it is stored and who can reach it.

Weaknesses Researchers Found in ELDs

The research and the advisory describe the same few ELD cybersecurity mistakes. None needs advanced skill to understand, and each has a known fix.

  • Predictable Wi-Fi names with weak default passwords, and a firmware upload page protected by a basic password.
  • Bluetooth pairing that needs no confirmation, and a predictable device identifier.
  • A network service on port 23 that could send and receive arbitrary vehicle network messages.
  • Update commands that needed no authentication, and no enforcement of firmware signing.
  • Default credentials and unchecked code downloads in the IOSiX device, per CISA.

The authors recommend disabling unused wireless interfaces and the internal web server, using unique high-entropy default passwords, signing firmware cryptographically and removing the arbitrary-message feature. For older trucks, they suggest a telematics firewall or gateway between the ELD and the diagnostic port.

FMCSA funded early guidance on this: its best practices project page describes aftermarket telematics as a possible point of entry through wired or wireless interfaces. The page does not list the recommendations, so read the full report if you buy equipment.

Get Fleet Security Guides in Your Inbox

Get practical guides on fleet cybersecurity, fraud prevention and operations delivered to your inbox. Join the fleet managers, dispatchers and technicians who read Heavy Duty Journal.

⚠️ Safety Warning

Do not test an ELD's wireless features by sending commands to a truck that is moving or in service. The researchers worked on a closed airfield and a research truck. If you suspect a device is vulnerable, report it to the vendor and take the unit out of service rather than experimenting.

Range matters. At a crowded truck stop, a distance of about 120 feet is not far. That is HDJ's inference from the researchers' figure, not a reported attack, but it is a reason to turn off wireless features nobody uses.

How an ELD Attack Could Work and What It Could Reach

Three routes to an ELD cybersecurity failure are plausible, and they differ in evidence. The first is a nearby attacker using an unprotected device, which the research demonstrated. The second is the provider: the 2026 Transportation Industry Cybersecurity Trends Report says reliance on vendors, including telematics providers, let attackers move from one compromised vendor into multiple fleets, in NMFTA's words turning one weak link into a systemic risk.

The FBI's 2020 notice describes a third, older scenario: using an insecure ELD as an entry point into a company's enterprise network, then stealing personal, financial, location, customer and cargo data or running ransomware. It presented these as possibilities, not incidents.

The documented path in the FBI's April 2026 alert is people, not hardware: phishing sites that install remote monitoring software and give criminals access to broker and carrier systems. HDJ's freight phishing scams guide covers that route.

What could be exposed depends on the system. Driver accounts on an ELD hold identity and license details under Appendix A, and the records show where a truck has been. The Colorado State page says malicious firmware could alter driving-hour records. HDJ found no verified breach cost for trucking and no source for the earlier dollar figures.

GPS spoofing, which falsifies satellite signals, is a separate problem from compromising an ELD. HDJ's GPS spoofing and cargo theft article covers it. Keep the two apart when you assess risk.

Vetting an ELD Provider

The FBI's notice says to ask suppliers detailed security questions covering the in-vehicle hardware, communications, user interfaces and cloud back ends. It says solutions failing high-criticality requirements, such as enforcing engine-to-ELD communication controls, should be avoided. NMFTA's Cybersecurity Requirements for Telematics Systems is the checklist the notice points to; the page shows March 2022 while the file is version 1.5, so confirm the current version.

Brand names can mislead, and they complicate ELD cybersecurity vetting. The white-labeled ELDs research found more than a dozen families of white-labeled ELDs, some with dozens of related products sharing software, hardware and code. A September 2026 column by NMFTA's chief operating officer in Commercial Carrier Journal puts registered ELDs at about 1,050 and estimates about 720 models may share one vulnerability.

That estimate is NMFTA's, and HDJ could not verify it independently. The practical point is simple: the name on the box may not tell you who wrote the firmware. Ask, and put the answers in the contract. The table lists six questions.

Ask the providerWhy it mattersA weak answer
Who makes the hardware and firmware?White-labeled devices can share platforms and flawsThe provider cannot name the maker
Are Wi-Fi and web passwords unique per unit?Default passwords were found in the research and the advisoryThe same password on every device
Is firmware signed and are updates authenticated?The tested device did not enforce signingChecksums only, or no answer
Can the device send arbitrary commands to the vehicle network?The authors call this an unwarranted riskYes, or the provider will not say
Has an independent firm tested the device, and when?Penetration testing is on the FBI list of controlsOnly the vendor tests its own product
How are vulnerabilities reported and patched?CISA advisory shows the fix is a version updateNo public process or contact

ISO 27001 and SOC 2 reports show how a company runs its organization. HDJ treats them as supporting evidence, not proof that a device is secure, and that is practitioner judgment, not a federal rule.

What Federal Rules Require and Leave Out

The federal ELD cybersecurity rules are thin because the rules focus on record accuracy. Appendix A requires user authentication at login, preserves original records when edits are made and requires data check values. As of October 2026, the portion HDJ read has no encryption or security testing requirement. HDJ could not read the data-transfer sections, so check them yourself.

The FBI's 2020 notice says the mandate has no cybersecurity requirements for ELD makers and no third-party testing before self-certification. HDJ found no FMCSA rule adding them since, in the sources it searched. The FMCSA's ELD list says listed devices are self-certified by the manufacturer and that FMCSA does not endorse any ELD.

Tampering rules protect the record, not the device from outsiders. 49 Code of Federal Regulations (CFR) 395.8(e) bars drivers and carriers from reprogramming or tampering with an ELD so it does not accurately record required data. HDJ's ELD tampering guide covers that side. Carriers must also use only a device on FMCSA's list, per 49 CFR 395.22.

Voluntary frameworks fill the gap. Cybersecurity Framework 2.0 from the National Institute of Standards and Technology (NIST) now has six functions, including a new Govern function; the earlier article listed five. The Surface Transportation Cybersecurity Resource Toolkit is for operators under 1,000 employees, and the resources HDJ read focus on transit, rail and pipelines, not trucking. The Transportation Systems Sector page lists a Highway and Motor Carrier subsector and no information-sharing group.

State law may also apply. The California Privacy Protection Agency lists California fines of up to $2,663 per violation and $7,988 per intentional violation since January 2025, and $107 to $799 per consumer per incident in breach suits. Whether it covers your business is a question for an attorney.

Securing the ELDs You Already Run

Start ELD cybersecurity work with an inventory: every ELD, its make, its firmware version and which wireless features are on. Turn off Wi-Fi, Bluetooth and any web interface nobody uses. Change default passwords where the device allows it, and ask the vendor to fix what you cannot change. These steps follow the researchers' recommendations, and HDJ would do them first.

Update firmware when the vendor releases it. For the IOSiX unit, the vendor fix listed in CISA's advisory is version 360, so ask your provider which version your units run. For older trucks, ask whether a telematics gateway or firewall between the ELD and the diagnostic port is practical.

Protect the accounts behind the device. Use multifactor authentication on provider portals, give each person their own login, and remove accounts when people leave. HDJ found no federal rule requiring these steps for ELD portals, so they are practitioner judgment based on how the FBI describes account takeover.

Key Recommendation

Before you buy or renew any ELD, send the provider the six questions in the table and keep the written answers. A vendor that will not answer in writing has already answered.

For the wider program, HDJ's fleet cybersecurity guide covers network segmentation and access control beyond the ELD.

Training and Response When Something Looks Wrong

People are the documented route, so ELD cybersecurity training matters. The FBI's April 2026 alert recommends verifying requests through a second channel and watching for unauthorized mailbox rules. HDJ's trucking cybersecurity training guide covers a program for drivers and dispatchers.

HDJ suggests teaching drivers to report oddities: an ELD that asks for a password it never needed, a new Wi-Fi network that looks like theirs, or a truck that slows or derates with no fault code. Practitioner advice is to stop safely, report and let the vendor check the unit.

If an ELD stops working, follow your information packet. Under 49 CFR 395.34, the driver notes the malfunction, notifies the carrier within 24 hours and reconstructs the record of duty status, and the carrier has 8 days to correct it. Report suspected compromise to the vendor and to the FBI's Internet Crime Complaint Center at ic3.gov.

If criminals reach your office systems, HDJ's ransomware recovery guide lays out what to do first.

What HDJ Removed From the Earlier Guide

A refresh should say what changed. HDJ removed the 75% cloud-tool figure credited to a Transportation Security Administration (TSA) report, the average breach cost credited to an IBM report, the ransom ranges, four cost tables and the 60% small-business closure claim. None had a source HDJ could confirm.

It also removed the 2023 incident said to have grounded 1,000 trucks, the $2 million GPS spoofing example, the 40% and 22% survey figures, the credential statistics and a quotation attributed to CISA. The claims that researchers controlled brakes and transmissions through telematics were removed because HDJ could not tie them to a source; the Colorado State test showed a slowdown only.

The claims about Social Security numbers in ELDs, pre-compromised counterfeit devices, trucking information-sharing centers, blockchain and artificial intelligence defenses, and a $7,500 California fine were also removed or corrected. HDJ also dropped the four in-body images and the old tools box.

Frequently Asked Questions

What is ELD cybersecurity?

ELD cybersecurity is the set of steps that keep an Electronic Logging Device and the accounts behind it from being misused. That covers unique passwords, wireless settings, firmware updates, vendor vetting and login protection. It matters because the device connects to the engine and to the fleet's cloud systems.

Can hackers disable a truck through an ELD?

Researchers slowed a test truck on a closed airfield by reprogramming a vulnerable ELD over Wi-Fi. They did not attempt more. HDJ found no confirmed attack on a real fleet. The risk needs a vulnerable device and an attacker nearby, so unique passwords and disabled wireless features lower it.

Are ELDs required to meet cybersecurity standards?

Not in the rules HDJ read. The FBI said in 2020 that the mandate has no cybersecurity requirements for makers and no third-party testing before self-certification, and HDJ found no later rule adding them. NMFTA publishes voluntary requirements that fleets can put into contracts.

How do I check whether my ELD is secure?

Ask the provider who makes the hardware and firmware, whether passwords are unique, whether firmware is signed, whether an independent firm tested it and how vulnerabilities are patched. Get answers in writing. If a vendor will not answer, treat that as a warning and consider switching.

What data can an ELD breach expose?

It can expose driver identity and license details, duty records and the truck's location history, depending on the provider. The FBI also lists customer and cargo data as targets if attackers reach the company network. What your devices collect varies, so request a written data list.

How should a small fleet start on ELD cybersecurity?

Make a list of every ELD and turn off wireless features nobody uses. Change default passwords where possible and ask the vendor for firmware updates. Add multifactor authentication to the provider portal, then send your vendor the six questions in the table and keep the replies.

The Bottom Line

ELD cybersecurity is not a reason to remove the devices. It is a reason to ask better questions. The research is real, the fixes are known, and HDJ found no confirmed attack on a real fleet as of October 2026. Unique passwords, fewer open wireless features, updated firmware and a vendor who answers in writing are the core of ELD cybersecurity for a small fleet.

Michael Nielsen and the HDJ editorial team publish more fleet security guidance at heavydutyjournal.com. This week, list your ELDs, check their passwords and send your provider the six questions.

Share This ELD Security Guide

Know a fleet manager or owner-operator who runs ELDs? Share this guide with them. Michael Nielsen and Heavy Duty Journal publish it free at heavydutyjournal.com.

Leave a Comment

Your email address will not be published. Required fields are marked *