Government
20 columns
121 rows
8 formats

Municipal IoT Security Audit Log

This dataset provides detailed logs of IoT device security events across municipal infrastructure, including device details, event types, severity, compliance status, and remediation actions. It enables public sector teams to monitor vulnerabilities, benchmark security performance, and support regulatory compliance, making it a valuable resource for smart city cybersecurity and resilience initiatives.

last updated 24 Jan 2026
by GoMask

The brief that made it

Benchmarking IoT security performance across municipalities

Sample rows

preview · 8 of 121 rows · all 20 columns

event_idstring	event_typestring	compliance_flagboolean	device_location_statestring	event_timestampdatetime	device_idstring	device_typestring	device_location_streetstring	device_location_citystring	device_location_postal_codestring	device_location_countrystring	municipality_idstring	municipality_namestring	event_severitystring	event_statusstring	reported_bystring	remediation_actionstring	compliance_standardstring	vulnerability_idstring	event_descriptionstring
A9B3XZ-12	unauthorized-access	true	IL	2022-02-28T09:13:44Z	DEV-001	sensor	120 Maple St	Springfield	62701	US	MUNI-001	Springfield	medium	open	system	blank	NIST	blank	Unusual login detected on sensor device.
KJL-0034-XX	malware-detected	true	CA	2023-11-15T19:04:12Z	DEV-002	camera	503 Oak Ave	Riverside	92501	US	MUNI-002	Riverside	high	investigating	SOC	blank	ISO-27001	blank	Malware signature found in camera firmware.
DEV-003-LOG	firmware-update	false	TX	2024-05-29T16:33:21Z	DEV-003	meter	blank	Fairview	75069	US	MUNI-003	Fairview	low	resolved	automation	Update verified and completed.	none	blank	Routine firmware update applied to smart meter.
9AF1-004L-YY	vulnerability-detected	true	YT	2023-12-25T21:07:00Z	DEV-004	environmental-monitor	88 Snow Rd	Whitehorse	Y1A4N1	CA	MUNI-004	Whitehorse	critical	open	security-team	blank	NIST	CVE-2023-5001	Critical vulnerability detected in air quality monitor.
MUNI-005-LOG1	configuration-change	false	OH	2022-07-04T11:24:38Z	DEV-005	traffic-light	101 Main Ave	Centerville	45459	US	MUNI-005	Centerville	medium	resolved	admin	Settings verified.	none	blank	Traffic light configuration updated.
DEV-006-4421	network-anomaly	true	SC	2023-09-09T14:20:11Z	DEV-006	sensor	25 Elm St	Greenville	29601	US	MUNI-006	Greenville	high	open	NIDS	blank	GDPR	blank	Unexpected traffic spike detected on sensor network.
BATCH1-007	firmware-update	false	TX	2021-04-15T06:10:55Z	DEV-007	meter	blank	Lakeview	75070	US	MUNI-007	Lakeview	medium	resolved	system	Update completed.	none	blank	Power meter updated to v3.4.
T-008-XX	network-anomaly	false	TN	2023-01-01T03:03:03Z	DEV-008	sensor	13 Pine Ln	Kingsport	37660	US	MUNI-008	Kingsport	medium	investigating	IDS	blank	none	blank	Sensor experienced packet loss during New Year.
LOG-009-BATCH1	vulnerability-detected	true	OR	2022-05-10T10:45:56Z	DEV-009	camera	76 River Rd	Portland	97201	US	MUNI-009	Portland	critical	open	pentest-team	blank	HIPAA	CVE-2022-1086	Firmware vulnerability discovered in security camera.
B1-010-LOG	configuration-change	false	WA	2020-02-29T23:59:59Z	DEV-010	traffic-light	blank	Redmond	98052	US	MUNI-010	Redmond	low	resolved	admin	Configuration confirmed.	none	blank	Traffic timing adjusted for leap day.
XX-011-BATCH1	vulnerability-detected	true	blank	2023-03-12T17:15:00Z	DEV-011	environmental-monitor	4 Aurora Dr	Oslo	0181	NO	MUNI-011	Oslo	high	open	AutoScan	blank	ISO-27001	CVE-2023-7002	Air monitor vulnerable to remote exploit.
BATCH1-012LOG	firmware-update	false	WI	2021-07-18T08:18:18Z	DEV-012	meter	230 Cedar St	Madison	53703	US	MUNI-012	Madison	low	resolved	system	Update completed.	none	blank	Smart meter firmware updated to latest version.
LOG-013-XY	other	false	blank	2022-10-05T12:05:15Z	DEV-013	other	blank	Testville	blank	XY	MUNI-013	Testville	low	open	test-user	blank	none	blank	Device type registered for testing.
BATCH1-014ZZ	network-anomaly	true	MA	2024-01-01T01:01:01Z	DEV-014	sensor	1 Innovation Blvd	Boston	02108	US	MUNI-014	Boston	medium	investigating	system	blank	GDPR	blank	Sensor reported connectivity issues after midnight.
BATCH1-015-LOG	malware-detected	true	blank	2022-12-25T10:10:10Z	DEV-015	camera	99 Holiday St	London	W1A 1AA	UK	MUNI-015	London	critical	open	AV-Scanner	blank	ISO-27001	blank	Malware found on London traffic camera.
LOG-016-AU	vulnerability-detected	true	NSW	2023-06-01T15:00:01Z	DEV-016	environmental-monitor	7 Beach Rd	Sydney	2000	AU	MUNI-016	Sydney	high	open	security-team	blank	NIST	CVE-2023-8152	Environmental sensor firmware vulnerable to exploit.
LOG-017-GL	vulnerability-detected	true	blank	2022-03-15T18:45:35Z	DEV-017	environmental-monitor	blank	Nuuk	3900	GL	MUNI-017	Nuuk	high	open	security-team	blank	ISO-27001	CVE-2022-1603	Temperature sensor affected by remote code vulnerability.
LOG-018-B1	firmware-update	false	NY	2021-06-12T07:12:34Z	DEV-018	meter	56 Market St	Buffalo	14202	US	MUNI-018	Buffalo	medium	resolved	automation	Update completed and verified.	none	blank	Meter firmware upgraded to v2.2.
LOG-019-CA	unauthorized-access	false	ON	2024-03-17T14:14:14Z	DEV-019	sensor	blank	Toronto	M5H 2N2	CA	MUNI-019	Toronto	high	open	system	blank	none	blank	Unauthorized access attempt on sensor.
LOG-020-NW	network-anomaly	false	blank	2022-08-22T12:22:22Z	DEV-020	other	9999 Test Dr	Legacy	blank	ZZ	MUNI-020	Legacy	critical	false-positive	legacy-system	blank	none	blank	Legacy device caused a network anomaly.

What the 121 rows show

from the 121-row sample

Vulnerability-detected (event type) stands out: 25 of its 25 rows have compliance_flag = true, against 23 of 96 for the rest.

40%compliance_flag = true
4event severities
4event statuses
6device types
6compliance standards
12reported_by values

Compliance flag rate by event_typecompliance_flag = true

device_location_state91 rows with a value · 30 left blank

TX11
CA7
ON5
AZ5
OH4
NY4
WI3
BC3
NE3
MI3

20 columns by typefrom the column list below

string 18
datetime 1
boolean 1

Columns

20 columns in three groups

blueprint · 20 columns
column	type	description	example
Text 18 columns
`event_id`	string	Unique identifier for each security event log entryunique	A9B3XZ-12
`device_id`	string	Unique identifier for the IoT device involved in the event	DEV-001
`device_type`	string	Type or category of the IoT device (e.g., sensor, camera, traffic light)6 values	sensor
`device_location_street`	string	Street address where the device is physically locatedoptional	120 Maple St
`device_location_city`	string	City where the device is located	Springfield
`device_location_state`	string	State or province where the device is located	IL
`device_location_postal_code`	string	Postal code for the device's locationoptional	62701
`device_location_country`	string	Country where the device is located	US
`municipality_id`	string	Unique identifier for the municipality responsible for the device	MUNI-001
`municipality_name`	string	Name of the municipality	Springfield
`event_type`	string	Type of security event (e.g., unauthorized access, firmware update, vulnerability detected)7 values	unauthorized-access
`event_severity`	string	Severity level of the eventlow · medium · high · critical	medium
`event_description`	string	Detailed description of the security eventoptional	Meter firmware updated.
`event_status`	string	Current status of the event (e.g., open, investigating, resolved, false positive)open · investigating · resolved · false-positive	open
`reported_by`	string	Name or identifier of the person/system that reported the event12 values · optional	system
`remediation_action`	string	Description of actions taken to remediate the eventoptional	Settings verified.
`compliance_standard`	string	Name of the compliance standard involved (e.g., NIST, ISO 27001, GDPR)6 values · optional	NIST
`vulnerability_id`	string	Identifier for the vulnerability (if applicable, e.g., CVE number)optional	CVE-2023-5001
Dates and times 1 column
`event_timestamp`	datetime	Date and time when the security event occurred	2022-02-28T09:13:44Z
True or false 1 column
`compliance_flag`	boolean	Indicates whether the event relates to a compliance requirement	true

Use it for

A government dashboard
The compliance_flag rate, compliance_flag by event_type and a breakdown of device_location_state. Excel, Power BI or Tableau.
Why do 48 of 121 rows have compliance_flag = true?
A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
Events121
A9B3XZ-12unauthor…
KJL-0034-XXmalware-…
DEV-003-LOGfirmware…
A software demo
Believable events with event_timestamp, device_id and device_type to fill a screen in front of a buyer.

This dataset121 rows20 columns

Yours10,000 rows20 columnsdevice_location_street: UK only

blueprint · municipal-iot-security-audit-log

Behind this dataset

Same schema. As many rows as you need.

These 121 rows came out of a blueprint — 20 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 one IoT security event on a unique device.
Include device type, event severity, and timestamp for every entry.
Capture location (facility/building) and responsible department.
Flag events related to compliance breaches or failed updates.
Only include events from devices connected to municipal networks.

Rows1,000 rows10,000 rows100,000 rows1,000,000 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: municipal-iot-security-audit-log

What should your data show?

No signup. No card.

Sample rows

What the 121 rows show

Columns

Use it for

A government dashboard

A root-cause class exercise

A software demo

Make it yours.

Same schema. As many rows as you need.

More in Government

What should your data show?