Fleet Cybersecurity Compliance Tracker
This dataset provides a detailed, vehicle-level view of cybersecurity compliance across transportation fleets, including audit history, vulnerability counts, IoT device exposure, and risk assessments. It enables operational leaders to monitor adherence to industry standards, identify gaps in security, and prioritize remediation efforts for remote assets. The schema supports actionable analytics for risk management and regulatory reporting.
Sample rows
preview · 8 of 72 rows · all 24 columns| vehicle_idstring | compliance_statusstring | open_vulnerabilities_countinteger | remote_access_enabledboolean | remote_access_protocolstring | fleet_idstring | vehicle_typestring | manufacturerstring | modelstring | yearinteger | last_cybersecurity_audit_datedate | next_cybersecurity_audit_duedate | compliance_standardstring | risk_levelstring | identified_vulnerabilities_countinteger | last_vulnerability_remediation_datedate | iot_devices_installed_countinteger | critical_iot_devices_countinteger | last_iot_firmware_update_datedate | last_remote_access_review_datedate | location_citystring | location_statestring | location_countrystring | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| VIN4TGJH23K1A000001 | compliant | 0 | true | VPN | FL-NE-001 | truck | Freightliner | Cascadia | 2019 | 2024-03-05 | 2024-09-05 | ISO 21434 | low | 1 | 2024-03-11 | 7 | 2 | 2024-03-01 | 2024-03-02 | Boston | MA | USA | All vulnerabilities addressed as of last audit. |
| VIN1HKCM82633A00002 | pending | 1 | true | SSH | FL-WEST-002 | van | Ford | Transit Connect | 2022 | 2024-04-17 | 2024-10-17 | NIST SP 800-53 | medium | 2 | 2024-04-18 | 4 | 1 | 2024-04-10 | 2024-04-15 | San Francisco | CA | USA | Pending remediation of one vulnerability. |
| VIN2FTRX18W1XCA0003 | compliant | 0 | false | blank | FL-NE-001 | car | Toyota | Camry Hybrid | 2021 | 2024-01-20 | 2024-07-20 | ISO 21434 | low | 0 | blank | 5 | 1 | 2024-01-12 | blank | Hartford | CT | USA | No vulnerabilities detected. |
| VIN3N1BC13E98L00004 | in-progress | 1 | true | Proprietary | FL-SO-003 | bus | Blue Bird | Vision | 2017 | 2024-02-28 | 2024-08-28 | Company-Sec2023 | medium | 3 | 2024-03-01 | 9 | 3 | 2023-12-27 | 2024-02-28 | Atlanta | GA | USA | Remediation ongoing; audit in progress. |
| VINJH4KA9650MC00005 | compliant | 0 | true | VPN | FL-WEST-002 | truck | Volvo | VNL 860 | 2020 | 2024-05-10 | 2024-11-10 | ISO 21434 | low | 1 | 2024-05-11 | 10 | 4 | 2024-05-08 | 2024-05-09 | Portland | OR | USA | All critical IoT devices up to date. |
| VINWDBRF40J33F00006 | non-compliant | 2 | false | blank | FL-SO-003 | van | Mercedes-Benz | Sprinter | 2015 | 2024-02-03 | 2024-08-03 | NIST SP 800-53 | high | 5 | 2024-02-07 | 3 | 1 | 2024-01-20 | blank | Miami | FL | USA | Non-compliant: open vulnerabilities remain. |
| VIN1GNEK13Z33R00007 | compliant | 0 | true | VPN | FL-MID-004 | car | Chevrolet | Tahoe | 2018 | 2024-03-15 | 2024-09-15 | ISO 21434 | low | 0 | blank | 6 | 2 | 2024-03-13 | 2024-03-14 | Chicago | IL | USA | Routine compliance achieved. |
| VIN2C3KA43R89H00008 | in-progress | 1 | false | blank | FL-MID-004 | bus | IC Bus | CE Series | 2014 | 2024-01-19 | 2024-07-19 | Company-Sec2023 | medium | 2 | 2024-01-20 | 7 | 2 | 2023-12-30 | blank | Detroit | MI | USA | Remediation scheduled for next month. |
| VINJTDKB20U39700009 | compliant | 0 | false | blank | FL-NE-001 | van | Nissan | NV200 | 2016 | 2024-02-14 | 2024-08-14 | NIST SP 800-53 | low | 1 | 2024-02-16 | 3 | 1 | 2024-02-10 | blank | Providence | RI | USA | Remediation completed. |
| VINJM1BK32F87100010 | pending | 1 | true | VPN | FL-MID-004 | truck | Kenworth | T680 | 2023 | 2024-05-03 | 2024-11-03 | ISO 21434 | medium | 2 | 2024-05-05 | 8 | 3 | 2024-05-02 | 2024-05-02 | Cleveland | OH | USA | Pending audit result; one vulnerability open. |
| VIN1HGCM82633A00011 | compliant | 0 | false | blank | FL-WEST-002 | car | Honda | Accord | 2017 | 2024-02-25 | 2024-08-25 | Company-Sec2023 | low | 0 | blank | 6 | 2 | 2024-02-24 | blank | Seattle | WA | USA | No issues detected. |
| VIN2G1WF55KX19200012 | in-progress | 6 | true | Proprietary | FL-WEST-002 | other | Tesla | Cybertruck | 2024 | 2024-06-01 | 2024-12-01 | ISO 21434 | critical | 7 | 2024-06-02 | 12 | 5 | 2024-05-28 | 2024-05-29 | Los Angeles | CA | USA | Critical vulnerabilities; remediation plan in progress. |
| VIN4S4BP62C44700013 | non-compliant | 3 | false | blank | FL-NE-001 | bus | Thomas Built | Saf-T-Liner | 2020 | 2024-04-03 | 2024-10-03 | NIST SP 800-53 | high | 4 | 2024-04-04 | 10 | 4 | 2024-04-01 | blank | New York | NY | USA | Non-compliant; multiple vulnerabilities remain open. |
| VIN1J4FA49S81P00014 | pending | 1 | false | blank | FL-SO-003 | other | John Deere | Gator TX | 2019 | 2024-03-29 | 2024-09-29 | Company-Sec2023 | medium | 2 | 2024-03-30 | 2 | 0 | 2024-03-25 | blank | Orlando | FL | USA | Low IoT exposure. |
| VIN1FTFW1ET1EK00015 | compliant | 0 | true | SSH | FL-MID-004 | truck | Peterbilt | 579 | 2018 | 2024-03-23 | 2024-09-23 | ISO 21434 | low | 0 | blank | 8 | 3 | 2024-03-21 | 2024-03-22 | Indianapolis | IN | USA | All systems up to date. |
| VIN5NPEB4AC6DH00016 | compliant | 0 | false | blank | FL-SO-003 | car | Hyundai | Sonata | 2015 | 2024-02-11 | 2024-08-11 | NIST SP 800-53 | low | 1 | 2024-02-13 | 3 | 1 | 2024-02-10 | blank | Tampa | FL | USA | Routine audit completed. |
| VIN1G1JC52442700017 | non-compliant | 2 | true | Proprietary | FL-WEST-002 | bus | Gillig | Low Floor | 2016 | 2024-02-18 | 2024-08-18 | Company-Sec2023 | high | 3 | 2024-02-19 | 7 | 2 | 2024-02-16 | 2024-02-17 | San Diego | CA | USA | Requires urgent remediation. |
| VINJTDKN3DU6A000018 | pending | 1 | true | SSH | FL-MID-004 | car | Kia | Forte | 2022 | 2024-04-11 | 2024-10-11 | ISO 21434 | medium | 2 | 2024-04-14 | 5 | 1 | 2024-04-10 | 2024-04-10 | Columbus | OH | USA | Pending audit completion. |
| VIN1FAFP404X1F00019 | non-compliant | 5 | false | blank | FL-SO-003 | truck | International | LT Series | 2014 | 2024-01-30 | 2024-07-30 | NIST SP 800-53 | critical | 6 | 2024-02-02 | 6 | 2 | 2024-01-28 | blank | Charlotte | NC | USA | Critical vulnerabilities outstanding. |
| VIN3VW2K7AJ5FM00020 | compliant | 0 | true | VPN | FL-WEST-002 | van | Ram | ProMaster | 2021 | 2024-04-21 | 2024-10-21 | ISO 21434 | low | 0 | blank | 5 | 2 | 2024-04-19 | 2024-04-20 | Denver | CO | USA | Audit passed, all systems nominal. |
What the 72 rows show
from the 72-row sampleNon-compliant (compliance status) stands out: mean open_
- 49%remote_
access_ enabled = true - 1median open_
vulnerabilities_ count - 4risk levels
- 5vehicle types
- 5compliance standards
- 11fleets
Median 1, from 0 to 8.
- string 13
- integer 5
- date 5
- boolean 1
Columns
24 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 13 columns | |||
vehicle_id | string | Unique identifier for each fleet vehicle (e.g., VIN or asset tag)unique | VIN4TGJH23K1A000001 |
fleet_id | string | Identifier for the fleet to which the vehicle belongs11 fleets | FL-NE-001 |
vehicle_type | string | Type of vehicle (e.g., truck, van, car, bus)truck · van · car · bus · other | truck |
manufacturer | string | Vehicle manufacturer nameoptional | Freightliner |
model | string | Vehicle model name or numberoptional | Cascadia |
compliance_status | string | Current compliance status of the vehiclecompliant · non-compliant · pending · in-progress | compliant |
compliance_standard | string | Industry cybersecurity standard or protocol used for compliance (e.g., ISO 21434, NIST, company-specific)5 standards | ISO 21434 |
risk_level | string | Assessed risk level for the vehicle based on audit resultslow · medium · high · critical | low |
remote_access_protocol | string | Protocol used for remote access (e.g., VPN, SSH, proprietary)4 protocols · optional | VPN |
location_city | string | Current city where the vehicle is locatedoptional | Boston |
location_state | string | Current state/province where the vehicle is locatedoptional | MA |
location_country | string | Current country where the vehicle is located12 countries · optional | USA |
notes | string | Additional notes or comments regarding the vehicle’s cybersecurity statusoptional | Remediation completed. |
| Numbers 5 columns | |||
year | integer | Year the vehicle was manufactured1,990 to 2,100 · optional | 2019 |
identified_vulnerabilities_count | integer | Number of cybersecurity vulnerabilities identified in the last audit0 or more | 1 |
open_vulnerabilities_count | integer | Number of unresolved vulnerabilities currently present0 or more | 0 |
iot_devices_installed_count | integer | Number of IoT devices installed in the vehicle0 or more · optional | 7 |
critical_iot_devices_count | integer | Number of critical IoT devices (e.g., those affecting safety or vehicle control)0 or more · optional | 2 |
| Dates and times 5 columns | |||
last_cybersecurity_audit_date | date | Date of the most recent cybersecurity audit for the vehicle | 2024-03-05 |
next_cybersecurity_audit_due | date | Date when the next cybersecurity audit is scheduledoptional | 2024-09-05 |
last_vulnerability_remediation_date | date | Date when the last vulnerability remediation was performedoptional | 2024-03-11 |
last_iot_firmware_update_date | date | Date of last firmware update for IoT devices in the vehicleoptional | 2024-03-01 |
last_remote_access_review_date | date | Date of last review of remote access settingsoptional | 2024-03-02 |
| True or false 1 column | |||
remote_access_enabled | boolean | Indicates whether remote access to vehicle systems is enabled | true |
Use it for
A transportation dashboard
The remote_
access_ enabled rate, open_ vulnerabilities_ count by compliance_ status and a breakdown of remote_ access_ protocol. Excel, Power BI or Tableau. Why do the 12 non-compliant rows have a mean open_
vulnerabilities_ count of 4.6? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Vehicles72VIN4TGJH23K1A0000010compliantVIN1HKCM82633A000021pendingVIN2FTRX18W1XCA00030compliant
A software demo
Believable vehicles with fleet_
id, vehicle_ type and manufacturer to fill a screen in front of a buyer.
This dataset72 rows24 columns
Yours1,000 rows24 columnslocation_city: UK only
blueprint · fleet-cybersecurity-compliance-tracker
Behind this dataset
Same schema. As many rows as you need.
These 72 rows came out of a blueprint — 24 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
Rules it was built with
- Each row represents a unique fleet vehicle.
- Status must indicate compliance, partial, or non-compliance.
- Include last audit date and remediation status.
- Flag vehicles with critical vulnerabilities for immediate review.
- Log type and frequency of cybersecurity incidents per vehicle.
Open the blueprint in Data Factory
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- fleet-cybersecurity-compliance-tracker