IoT Device Security Incident Log
This dataset provides a detailed log of security incidents reported by IoT devices, including device identifiers, incident types, severity levels, response actions, and compliance flags. It enables organizations to monitor threat trends, analyze device vulnerabilities, and assess incident response effectiveness for regulatory and operational security management.
Sample rows
preview · 8 of 150 rows · all 17 columns| incident_idstring | detected_bystring | response_time_minutesfloat | resolvedboolean | device_idstring | device_typestring | device_locationstring | incident_datetimedatetime | reported_datetimedatetime | incident_typestring | severity_levelstring | response_actionstring | response_datetimedatetime | resolution_datetimedatetime | compliance_flagboolean | reporting_user_idstring | incident_descriptionstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| INC-0001 | automated_alert | 3.1 | true | DEV-1001-A | camera | HQ_Floor1_Room201 | 2024-01-03T23:59:59Z | 2024-01-04T00:01:03Z | unauthorized_access | critical | device_isolated | 2024-01-04T00:03:05Z | 2024-01-04T00:22:12Z | true | SYS-SEC | Unauthorized access detected by camera in HQ. Multiple failed login attempts followed by successful breach. |
| INC-0002 | automated_alert | 5.3 | true | DEV-1450-Z | sensor | BuildingA_Lab5 | 2024-01-10T08:17:46Z | 2024-01-10T08:18:02Z | malware_detected | high | firmware_updated | 2024-01-10T08:23:19Z | 2024-01-10T08:39:50Z | true | SYS-SEC | Sensor firmware flagged suspicious process. Malware signature matched during scheduled scan. |
| INC-0003 | automated_alert | 1.8 | true | DEV-212X | smart_lock | Warehouse_Entry2 | 2024-01-13T13:05:00Z | 2024-01-13T13:06:20Z | denial_of_service | critical | device_isolated | 2024-01-13T13:08:09Z | 2024-01-13T14:01:42Z | true | blank | Smart lock became unresponsive after multiple high-frequency access attempts. Possible DoS attack. |
| INC-0004 | external_report | 33.9 | false | DEV-BETA-003 | gateway | EdgeNet_Node5 | 2024-01-14T16:12:27Z | 2024-01-14T16:13:29Z | data_exfiltration | critical | device_isolated | 2024-01-14T16:47:20Z | blank | false | SYS-NOC | Large data transfer detected from gateway node to external IP. Possible exfiltration attempt. |
| INC-0005 | manual_review | 9.2 | true | DEV-88888 | window_sensor | Greenhouse_SectionB | 2024-01-19T12:00:00Z | 2024-01-19T12:01:10Z | configuration_change | medium | settings_reverted | 2024-01-19T12:10:14Z | 2024-01-19T12:25:47Z | true | USR-257 | Window sensor configuration altered remotely. Change confirmed by manual review. |
| INC-0006 | manual_review | 11.8 | true | DEV-700-L | humidity_sensor | Warehouse_Rack3 | 2024-01-22T09:44:10Z | 2024-01-22T09:44:45Z | other | low | no_action_required | 2024-01-22T09:56:00Z | 2024-01-22T10:15:00Z | true | USR-198 | Humidity sensor reported unexpected values. Manual inspection found no fault. |
| INC-0007 | manual_review | 16 | true | DEV-LG-7 | environment_sensor | HQ_Floor2_Room205 | 2024-01-24T17:00:00Z | 2024-01-24T17:02:00Z | configuration_change | medium | settings_reverted | 2024-01-24T17:18:00Z | 2024-01-24T17:33:00Z | true | USR-324 | Unauthorized configuration change detected on environment sensor. Settings reverted. |
| INC-0008 | automated_alert | 6.4 | true | DEV-AC-999 | air_quality_monitor | DataCenter_RoomA | 2024-01-27T01:00:00Z | 2024-01-27T01:01:10Z | malware_detected | high | device_restarted | 2024-01-27T01:07:22Z | 2024-01-27T01:29:15Z | true | blank | Air quality monitor flagged malware during scheduled scan. Network anomaly detected. |
| INC-0009 | manual_review | 11.2 | true | DEV-XYZ-22 | thermostat | BuildingB_ConfRoom1 | 2024-02-01T08:20:00Z | 2024-02-01T08:21:00Z | other | low | settings_verified | 2024-02-01T08:32:12Z | 2024-02-01T08:45:30Z | true | USR-150 | Thermostat reported temperature fluctuation outside normal range. No further action required. |
| INC-0010 | automated_alert | 1.3 | true | DEV-1001-A | camera | HQ_Floor1_Room202 | 2024-02-04T03:10:22Z | 2024-02-04T03:11:41Z | unauthorized_access | high | device_isolated | 2024-02-04T03:13:00Z | 2024-02-04T03:32:59Z | true | SYS-SEC | Camera detected unauthorized login attempt. Access denied and alert triggered. |
| INC-0011 | automated_alert | 1.8 | true | DEV-1450-Z | sensor | BuildingA_Lab6 | 2024-02-06T11:14:00Z | 2024-02-06T11:15:12Z | denial_of_service | high | device_restarted | 2024-02-06T11:17:02Z | 2024-02-06T11:36:00Z | true | blank | Sensor experienced repeated connection failures. Suspected denial of service. |
| INC-0012 | external_report | 34 | false | DEV-212X | smart_lock | Warehouse_Entry4 | 2024-02-10T22:48:30Z | 2024-02-10T22:50:00Z | data_exfiltration | critical | alert_escalated | 2024-02-10T23:22:30Z | blank | false | USR-567 | Smart lock detected suspicious outbound data transfer. Reported to security team. |
| INC-0013 | automated_alert | 5.3 | true | DEV-BETA-003 | gateway | EdgeNet_Node7 | 2024-02-12T14:35:45Z | 2024-02-12T14:36:10Z | malware_detected | high | firmware_updated | 2024-02-12T14:41:30Z | 2024-02-12T14:59:00Z | true | SYS-SEC | Gateway scanned and found malware signature. Firmware update initiated. |
| INC-0014 | manual_review | 15.2 | true | DEV-88888 | window_sensor | Greenhouse_SectionD | 2024-02-15T21:14:00Z | 2024-02-15T21:15:00Z | configuration_change | low | settings_verified | 2024-02-15T21:30:14Z | 2024-02-15T21:45:14Z | true | USR-290 | Window sensor configuration updated by authorized technician. No further action required. |
| INC-0015 | manual_review | 4.8 | true | DEV-700-L | humidity_sensor | Warehouse_Rack5 | 2024-02-17T03:40:00Z | 2024-02-17T03:41:11Z | malware_detected | medium | device_restarted | 2024-02-17T03:46:00Z | 2024-02-17T04:10:00Z | true | USR-198 | Humidity sensor flagged for malware. Device restarted remotely. |
| INC-0016 | automated_alert | 4.3 | true | DEV-LG-7 | environment_sensor | HQ_Floor3_Room309 | 2024-02-19T11:20:00Z | 2024-02-19T11:21:00Z | denial_of_service | high | device_restarted | 2024-02-19T11:25:20Z | 2024-02-19T11:52:00Z | true | blank | Environment sensor failed to respond after multiple rapid queries. Service restored after device restart. |
| INC-0017 | external_report | 34.5 | false | DEV-AC-999 | air_quality_monitor | DataCenter_RoomB | 2024-02-21T09:00:00Z | 2024-02-21T09:01:30Z | data_exfiltration | critical | device_isolated | 2024-02-21T09:36:00Z | blank | false | USR-467 | Air quality monitor detected outbound traffic spike. Possible data exfiltration. |
| INC-0018 | manual_review | 11.3 | true | DEV-XYZ-22 | thermostat | BuildingB_ConfRoom2 | 2024-02-22T06:20:00Z | 2024-02-22T06:21:01Z | other | medium | settings_verified | 2024-02-22T06:32:20Z | 2024-02-22T06:45:00Z | true | USR-150 | Thermostat showed short-lived anomaly. Settings verified by technician. |
| INC-0019 | automated_alert | 3 | true | DEV-1001-A | camera | HQ_Floor1_Room203 | 2024-02-24T13:00:00Z | 2024-02-24T13:02:07Z | unauthorized_access | critical | device_isolated | 2024-02-24T13:05:00Z | 2024-02-24T13:26:00Z | true | SYS-SEC | Camera flagged unauthorized access attempt. Device isolated for investigation. |
| INC-0020 | automated_alert | 2.2 | true | DEV-1450-Z | sensor | BuildingA_Lab7 | 2024-02-28T09:22:00Z | 2024-02-28T09:23:00Z | denial_of_service | high | device_restarted | 2024-02-28T09:25:10Z | 2024-02-28T09:49:00Z | true | blank | Sensor denied connection requests for extended period. Automated alert triggered. |
What the 150 rows show
from the 150-row sampleExternal_
- 82%resolved = true
- 4.8median response_
time_ minutes - 4severity levels
- 6incident types
- 8response actions
- 10device types
Median 4.8, from 1.3 to 87.6.
- string 10
- float 1
- datetime 4
- boolean 2
Columns
17 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 10 columns | |||
incident_id | string | Unique identifier for each security incidentunique | INC-0001 |
device_id | string | Unique identifier for the IoT device reporting the incident11 devices | DEV-1001-A |
device_type | string | Type or category of the IoT device (e.g., sensor, camera, thermostat)10 types | camera |
device_location | string | Physical or logical location of the device (e.g., building, room, network segment)optional | HQ_Floor1_Room201 |
incident_type | string | Classification of the security incident (e.g., unauthorized access, malware detected, data exfiltration)6 values | unauthorized_access |
severity_level | string | Severity rating of the incident (e.g., low, medium, high, critical)low · medium · high · critical | critical |
incident_description | string | Detailed description of the incident, including observed symptoms and contextoptional | Unauthorized access detec… |
detected_by | string | Method or system that detected the incident (e.g., automated alert, manual review, external report)3 values · optional | automated_alert |
response_action | string | Primary action taken in response to the incident (e.g., device isolated, firmware updated, alert escalated)8 actions · optional | device_isolated |
reporting_user_id | string | Identifier for the user or system that reported the incidentoptional | SYS-SEC |
| Numbers 1 column | |||
response_time_minutes | float | Time in minutes between incident detection and first response action0 or more · optional | 3.1 |
| Dates and times 4 columns | |||
incident_datetime | datetime | Timestamp when the security incident occurred or was detected | 2024-01-03T23:59:59Z |
reported_datetime | datetime | Timestamp when the incident was reported to the monitoring system | 2024-01-04T00:01:03Z |
response_datetime | datetime | Timestamp when the first response action was initiatedoptional | 2024-01-04T00:03:05Z |
resolution_datetime | datetime | Timestamp when the incident was marked as resolvedoptional | 2024-01-04T00:22:12Z |
| True or false 2 columns | |||
resolved | boolean | Indicates whether the incident has been fully resolved | true |
compliance_flag | boolean | Indicates if the incident was handled according to regulatory or organizational compliance standardsoptional | true |
Use it for
A technology dashboard
The resolved rate, response_
time_ minutes by detected_ by and a breakdown of device_ id. Excel, Power BI or Tableau. Why do the 27 external_
report rows have a mean response_ time_ minutes of 30.1? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Incidents150INC-00013.1automate…INC-00025.3automate…INC-000433.9external…
A software demo
Believable incidents with device_
id, device_ type and device_ location to fill a screen in front of a buyer.
blueprint · iot-device-security-incident-log
Behind this dataset
Same schema. As many rows as you need.
These 150 rows came out of a blueprint — 17 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.
- Each row represents a unique security incident from a registered IoT device.
- Incident severity is categorized as Low, Medium, or High.
- Include device type, location (generalized: facility or sector, not geo), event timestamp, and resolution status.
- Devices must be assigned to an operational domain (e.g., HVAC, access control, lighting, sensors).
- Resolution time must be tracked in hours and flagged if over 24h.
- Compliance check result (Pass/Fail) assigned to each incident.
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
- iot-device-security-incident-log