IoT Device Security Incident Logs

This dataset provides detailed logs of security incidents affecting smart IoT devices across distributed networks, including device information, incident types, severity, response actions, and compliance status. It enables cybersecurity teams to identify vulnerabilities, optimize incident response, and benchmark security posture for edge environments. The dataset is ideal for compliance monitoring, real-time event triage, and operational risk analysis.

  • last updated 27 Dec 2025
  • by GoMask
The brief that made it

Vulnerability identification and remediation tracking

Sample rows

preview · 8 of 120 rows · all 21 columns
incident_idstringincident_severitystringcompliance_violationbooleandevice_vendorstringdevice_idstringdevice_typestringdevice_firmware_versionstringnetwork_segmentstringincident_datetimedatetimeincident_typestringincident_statusstringreported_bystringassigned_teamstringresponse_actionstringvulnerability_idstringlocation_street_addressstringlocation_citystringlocation_statestringlocation_postal_codestringlocation_countrystringdescriptionstring
INC2024-1A2B3C4DcriticaltrueBoschdev-001Asensorv3.2.1Plant-West-42023-10-17T09:25:12Zmalwareresolvedsystem-monitor-1SOC-Team-AlphaquarantinedCVE-2023-5512425 Industrial AveClevelandOH44115USAMalware detected on sensor device in manufacturing plant. Quarantined and patched to prevent propagation.
INC2023-2B3C4D5EhightrueAxisdev-002Bcamerav5.0.2Lobby-East-12024-02-12T16:45:09Zunauthorized_accessinvestigatinguser-345SOC-Team-Betalockedblank100 Main StBostonMA02110USAUnauthorized login attempt detected on Axis camera in office lobby. Investigation ongoing.
INC2024-3C4D5E6FmediumtrueCiscodev-003Cgatewayv9.1.0Core-Backbone-22023-11-22T13:12:08Zdosresolvedsystem-monitor-4SOC-Team-Gammamonitoredblank200 Market StDallasTX75201USADenial of Service attack mitigated on core gateway. Traffic monitored for recurrence.
INC2024-4D5E6F7GhightrueNestdev-004Dthermostatv2.0.0Home-Main-32022-07-14T11:22:36Zvulnerability_exploitresolvedauto-monitor-1HomeSecpatchedCVE-2022-1478487 Maple DrSan JoseCA95112USAExploit detected in Nest thermostat. Firmware updated and patched to close vulnerability.
INC2024-5E6F7G8HcriticaltrueHoneywelldev-005Esensorv6.1.3Warehouse-North-22024-03-05T08:17:44Zdata_leakdetectedsystem-monitor-7SecOps-Betaquarantinedblank621 Commerce BlvdHoustonTX77002USASensitive data transmission detected on Honeywell sensor. Device quarantined for review.
INC2023-6F7G8H9ImediumfalseDahuadev-006Fcamerav4.3.0-labelOutdoor-West-72023-08-28T19:33:52Zconfiguration_changeresolveduser-678IT-Helpdeskloggedblank879 Park AveSeattleWA98101USASuspicious configuration change logged on Dahua camera. Settings reverted and incident closed.
INC2024-7G8H9I0JhightrueABBdev-007Genvironmental-sensorv1.0.0-testPlant-East-52023-12-01T07:54:23Zmalwaredetectedsystem-monitor-2Industrial-SecpatchedCVE-2023-2937921 Factory RdColumbusOH43215USAMalware signature found on ABB environmental sensor. Device patched immediately.
INC2023-8H9I0J1KmediumtrueBoschdev-008Hsensorv4.9.2Plant-South-12022-11-09T14:00:00Zdosinvestigatingsystem-monitor-6SOC-Team-Alphamonitoredblank303 Tech CenterAustinTX78701USAUnusual network traffic on Bosch sensor. Possible DoS attack under investigation.

What the 120 rows show

from the 120-row sample
  • 78%compliance_violation = true
  • 4incident statuses
  • 7incident types
  • 8location countries
  • 9device types
  • 9response actions
incident_severity120 rows by value
0204014low12%31medium26%37high31%38critical32%
device_vendor108 rows with a value · 12 left blank
  1. Bosch19
  2. Cisco12
  3. Honeywell12
  4. Axis10
  5. Siemens10
  6. Nest9
  7. ABB9
  8. Netgear7
  9. Tesla6
  10. Huawei6
21 columns by typefrom the column list below
  • string 19
  • datetime 1
  • boolean 1

Columns

21 columns in three groups
blueprint · 21 columns
columntypedescriptionexample
Text 19 columns
incident_idstringUnique identifier for the security incident log entryuniqueINC2024-1A2B3C4D
device_idstringUnique identifier for the affected IoT devicedev-001A
device_typestringType or model of the IoT device (e.g., sensor, camera, gateway)9 typessensor
device_vendorstringManufacturer or vendor of the IoT device12 vendors · optionalBosch
device_firmware_versionstringFirmware version running on the device at the time of incidentoptionalv3.2.1
network_segmentstringLogical or physical network segment where the device is locatedoptionalPlant-West-4
incident_typestringCategory of security incident (e.g., unauthorized access, malware, DoS)7 valuesmalware
incident_severitystringSeverity level of the incident (e.g., low, medium, high, critical)low · medium · high · criticalcritical
incident_statusstringCurrent status of the incident (e.g., detected, investigating, resolved, dismissed)detected · investigating · resolved · dismissedresolved
reported_bystringIdentifier or name of the system or user who reported the incidentoptionalsystem-monitor-1
assigned_teamstringName or identifier of the cybersecurity team handling the incident10 teams · optionalSOC-Team-Alpha
response_actionstringAction taken in response to the incident (e.g., quarantined, patched, monitored)9 actions · optionalquarantined
vulnerability_idstringReference identifier for any known vulnerability exploited (e.g., CVE number)optionalCVE-2023-5512
descriptionstringDetailed description of the incident and its contextoptionalMalware detected on senso…
location_street_addressstringStreet address where the affected device is physically locatedoptional425 Industrial Ave
location_citystringCity where the affected device is physically locatedoptionalCleveland
location_statestringState or province where the affected device is physically locatedoptionalOH
location_postal_codestringPostal code of the device's locationoptional44115
location_countrystringCountry where the affected device is physically located8 countries · optionalUSA
Dates and times 1 column
incident_datetimedatetimeTimestamp when the security incident was detected2023-10-17T09:25:12Z
True or false 1 column
compliance_violationbooleanIndicates if the incident represents a compliance violationoptionaltrue

Use it for

  • compliance vio…78%93 of 120 rowsrows by incident seve…14low31medi…37high38crit…

    A technology dashboard

    The compliance_violation rate, compliance_violation by incident_severity and a breakdown of device_vendor. Excel, Power BI or Tableau.

  • Why do 93 of 120 rows have compliance_violation = true?

    A class exercise

    Hand out the rows and one question. Everyone works from the same 120 rows.

  • A software demo

    Believable incidents with device_id, device_type and device_vendor to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 21 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset120 rows21 columns
Yours1,000 rows21 columnslocation_street_address: UK only

blueprint · iot-device-security-incident-logs

Behind this dataset

Same schema. As many rows as you need.

These 120 rows came out of a blueprint — 21 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 incident log must include device type, severity, and detection timestamp.
  • Only edge network connected IoT devices are included; exclude non-IoT endpoints.
  • Incident resolution times must be recorded and calculated.
  • Flag whether incidents triggered automated or manual response protocols.
  • Include device firmware version for all incidents.
Rows
Open the blueprint in Data Factory

1 credit per row. New accounts start with 25 free credits.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
iot-device-security-incident-logs

What should your data show?

Preview 20 rows free
No signup. No card.