Municipal IoT Security Incident Log

This dataset logs security incidents affecting municipal IoT devices in public spaces, capturing detailed information on device type, location, incident category, severity, response actions, and outcomes. It enables government teams to monitor vulnerabilities, assess risks, and optimize the security and resilience of smart city infrastructure. The dataset supports incident trend analysis, rapid response coordination, and strategic device management.

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

Real-time monitoring and response to IoT security threats in urban environments

Sample rows

preview · 8 of 65 rows · all 19 columns
incident_idstringincident_severitystringtime_to_response_minutesintegerdata_compromisedbooleandevice_idstringdevice_typestringdevice_location_latitudefloatdevice_location_longitudefloatdevice_location_descriptionstringincident_datetimedatetimeincident_typestringincident_statusstringreported_bystringresponse_actionstringvulnerability_referencestringaffected_servicesstringresolution_datetimedatetimeincident_descriptionstringresolution_summarystring
INC-8HZ1LKVQhigh23trueDEV-TRAFF-001traffic_sensor40.7128-74.006Broadway & Chambers St2024-04-03T08:22:00unauthorized_accessresolvedOpsTeamNYCDevice isolated, credentials resetCVE-2023-11456traffic control2024-04-03T09:17:00Unauthorized credentials used; traffic flow data accessed.Credentials revoked and device firmware updated
INC-9WE2JKLTcritical7trueDEV-CAM-003surveillance_camera40.7306-73.9866Astor Pl & Lafayette2024-04-10T11:05:00data_breachinvestigatingSecurityBotAlert sent to SOCCVE-2024-02856public safetyblankVideo footage containing personally identifiable information was accessed by unauthorized party.blank
INC-2KJ4GBNTmediumblankfalseDEV-ENV-009environmental_monitor40.7484-73.98575th Ave & 34th St2024-03-30T14:30:00malwareopenIoTManagerblankblankair quality monitoringblankSuspicious process detected on sensor firmware.blank
INC-B5L2VHMZhigh15falseDEV-WIFI-004public_wifi_router40.7624-73.9738Central Park S & 6th Ave2024-04-02T13:12:00denial_of_serviceclosedNetMonSysTraffic filtered, router rebootedblankpublic Wi-Fi2024-04-02T14:01:00High volume of requests caused service unavailability.Router rebooted and traffic filters applied
INC-D0G8YQSFmedium34falseDEV-CAM-003surveillance_camera40.7306-73.9866Astor Pl & Lafayette2024-04-12T19:47:00device_tamperingresolvedPatrolUnit3Physical inspection, casing replacedblankpublic safety2024-04-12T21:10:00Camera casing found open; no data loss detected.Tampered casing replaced, device reconnected
INC-1TQ9NCMWlow5falseDEV-ENV-004environmental_monitor40.7549-73.9847th Ave & 42nd St2024-04-05T15:19:00configuration_errorfalse_positiveSensorOpsConfiguration reviewedblankair quality monitoringblankSensor misconfigured; readings temporarily inaccurate.blank
INC-7KX3BHTRmedium12falseDEV-TRAFF-005traffic_sensor40.7451-73.9986W 23rd St & 8th Ave2024-03-28T09:46:00unauthorized_accessinvestigatingOpsTeamNYCCredentials flaggedCVE-2022-7612traffic controlblankMultiple failed login attempts detected.blank
INC-R1Z6DJKUhigh21falseDEV-CAM-007surveillance_camera40.7587-73.9787Times Sq & 42nd St2024-04-07T21:34:00malwareresolvedSecurityBotDevice isolated, malware removedCVE-2024-04321public safety2024-04-07T22:08:00Malware signature matched on camera system.Malware removed and device monitored

What the 65 rows show

from the 65-row sample

High (incident severity) stands out: 11 of its 18 rows have data_compromised = true, against 8 of 47 for the rest.

  • 29%data_compromised = true
  • 20median time_to_response_minutes
  • 5incident statuses
  • 7incident types
  • 8device types
  • 12affected serviceses
Data compromised rate by incident_severitydata_compromised = true
0%50%100%0%low0 of 135%medium1 of 2061%high11 of 1850%critical7 of 14
time_to_response_minutes59 rows, in bands of 10
0102092013862104070time_to_response_minutes →

Median 20, from 4 to 67.

device_id65 rows · top 10 of 26 values
  1. DEV-WIFI-0044
  2. DEV-ENV-0044
  3. TS-01814
  4. CAM-00214
  5. TS-02454
  6. CAM-00584
  7. DEV-CAM-0033
  8. DEV-ENV-0093
  9. DEV-WIFI-0093
  10. DEV-CAM-0113
19 columns by typefrom the column list below
  • string 13
  • integer 1
  • float 2
  • datetime 2
  • boolean 1

Columns

19 columns in four groups
blueprint · 19 columns
columntypedescriptionexample
Text 13 columns
incident_idstringUnique identifier for each security incidentuniqueINC-8HZ1LKVQ
device_idstringUnique identifier for the IoT device involved in the incidentDEV-TRAFF-001
device_typestringType or category of IoT device (e.g., traffic sensor, surveillance camera, environmental monitor)8 typestraffic_sensor
device_location_descriptionstringHuman-readable description of the device's location (e.g., 'Main St & 3rd Ave')optionalBroadway & Chambers St
incident_typestringCategorization of the security incident (e.g., unauthorized access, malware, data breach, device tampering)7 valuesunauthorized_access
incident_severitystringSeverity level of the incident (e.g., low, medium, high, critical)low · medium · high · criticalhigh
incident_statusstringCurrent status of the incident (e.g., open, investigating, resolved, closed, false positive)open · investigating · resolved · closed · false_positiveresolved
reported_bystringName or identifier of the person, team, or system that reported the incidentoptionalOpsTeamNYC
response_actionstringSummary of actions taken in response to the incident (e.g., device isolated, firmware updated, alert sent)optionalAlert sent to SOC
vulnerability_referencestringReference to known vulnerability (e.g., CVE identifier) if applicableoptionalCVE-2023-11456
affected_servicesstringComma-separated list of city services or systems affected by the incident (e.g., traffic control, public Wi-Fi)12 serviceses · optionaltraffic control
incident_descriptionstringDetailed narrative describing the incident, impact, and contextoptionalUnauthorized credentials …
resolution_summarystringSummary of how the incident was resolved or mitigatedoptionalCredentials revoked and d…
Numbers 3 columns
device_location_latitudefloatLatitude coordinate of the device's physical location-90 to 9040.7128
device_location_longitudefloatLongitude coordinate of the device's physical location-180 to 180-74.006
time_to_response_minutesintegerNumber of minutes between incident detection and initial response action0 or more · optional23
Dates and times 2 columns
incident_datetimedatetimeDate and time when the incident was detected or reported2024-04-03T08:22:00
resolution_datetimedatetimeDate and time when the incident was resolved or closedoptional2024-04-03T09:17:00
True or false 1 column
data_compromisedbooleanIndicates whether sensitive data was compromised in the incidenttrue

Use it for

  • data compromis…29%19 of 65 rowsmean time to response…17.8low26.1medi…23.8high22.9crit…

    A government dashboard

    The data_compromised rate, time_to_response_minutes by incident_severity and a breakdown of device_id. Excel, Power BI or Tableau.

  • Why do 19 of 65 rows have data_compromised = true?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

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

Not quite right?

Make it yours.

Same 19 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 dataset65 rows19 columns
Yours1,000 rows19 columnsdevice_location_latitude: UK only

blueprint · municipal-iot-security-incident-log

Behind this dataset

Same schema. As many rows as you need.

These 65 rows came out of a blueprint — 19 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 record represents a single security incident associated with one IoT device.
  • Include incident type, device ID, timestamp, resolution status, and response time.
  • Flag incidents involving unauthorized access separately from malware or network anomalies.
  • Only include incidents that triggered an automated alert and required human review.
Rows
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
municipal-iot-security-incident-log

What should your data show?

Preview 20 rows free
No signup. No card.