Telecom IoT Device Security Events

This dataset provides granular, real-time records of security events and uptime metrics for edge-connected IoT devices in telecom networks. It supports operational monitoring, compliance reporting, and vulnerability assessment, enabling telecom managers and IoT administrators to proactively address security threats and optimize device performance. The dataset is ideal for digital transformation, sustainability initiatives, and regulatory audits in the telecommunications sector.

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

Real-time security event monitoring for IoT devices

Sample rows

preview · 8 of 112 rows · all 17 columns
event_idstringdevice_typestringuptime_secondsintegercompliance_flagbooleandevice_locationstringdevice_idstringnetwork_segmentstringevent_timestampdatetimeevent_typestringevent_severitystringremediation_statusstringremediation_timestampdatetimereported_bystringfirmware_versionstringvendorstringdevice_statusstringevent_descriptionstring
EVT-001-A2B3C4D5gateway89300trueSiteAlpha-Rack2DEV-GW-01VLAN-102024-06-01T09:12:45Zunauthorized_accesscriticalresolved2024-06-01T09:35:20Znetwork monitorv2.5.1AcmeIoTdegradedUnauthorized access attempt detected from external IP. Incident logged for compliance review.
EVT-002-X9Z8T7Y6sensor123456trueWarehouse-Bay3DEV-SENSOR-06VLAN-252024-06-02T07:42:10Zpolicy_violationhighin_progressblankdevice agentv3.0.0SecureTechdegradedSensor exceeded allowed threshold for external communication. Compliance report created.
EVT-003-F4W2E1R8router3788falseBranchEast-Floor1ROUTER-88XYZVLAN-992024-06-02T11:30:51Zfirmware_updateinforesolved2024-06-02T12:00:00Zadminv1.7.2RouterPromaintenanceDevice firmware updated to v1.7.2 for enhanced security.
EVT-004-L1P6Q9S2camera48910trueSiteBeta-Pole5CAM-OUTDOOR-12VLAN-322024-06-03T14:45:27Zmalware_detectedcriticalresolved2024-06-03T15:10:00Znetwork monitorv4.4.0-EUViewPlusofflineMalware signature detected in outbound traffic. Compliance action necessary.
EVT-005-U5T8B2J9edge-compute155520000falseDataCenter-Row1DEV-EDGE-ULTRA1VLAN-12024-05-30T16:20:15Znetwork_anomalycriticalin_progressblanknetwork monitorv5.1.3EdgewaredegradedAbnormal surge in data flow detected. Investigation required.
EVT-006-Q2R7N5Y8smart-light0falseRetailWest-Floor2LGT-ZONE-E7VLAN-442024-06-01T19:05:34Zdevice_rebootinforesolved2024-06-01T19:07:12Zadminv2.2.8LumimaintenanceSmart light rebooted following scheduled maintenance.
EVT-007-M6C2V1Z0sensor9360falseWarehouse-Bay1SENSOR-TEMP-09VLAN-32024-06-01T23:55:12Znetwork_anomalymediumopenblankdevice agentv1.2.7SensorSystemsonlineTemperature sensor showed brief network latency spike.
EVT-008-K8D7F4X2edge-compute527110trueDataCenter-Row1DEV-EDGE-ULTRA1VLAN-12024-06-04T02:45:01Zmalware_detectedhighresolved2024-06-04T03:02:40Zdevice agentv5.1.3EdgewaredegradedSuspicious executable detected and blocked. Compliance notification issued.

What the 112 rows show

from the 112-row sample

Edge-compute (device type) stands out: mean uptime_seconds is 99,275,079, against 84,862 for the rest.

  • 33%compliance_flag = true
  • 51,550median uptime_seconds
  • 3reported_by values
  • 4remediation statuses
  • 4device statuses
  • 5event severities
Mean uptime_seconds by device_type112 rows
050M100M59,457sens…21 ro…99.3Medge…20 ro…95,402gate…17 ro…34,024came…17 ro…58,209rout…15 ro…244.1ksmar…13 ro…34,690smar…9 rows
uptime_seconds112 rows, in bands of 20M
050100980000077080M160Muptime_seconds →

Median 51,550, from 0 to 155,520,000.

device_location110 rows with a value · 2 left blank
  1. DataCenter-Row19
  2. Warehouse-Bay19
  3. SiteBeta-Pole58
  4. CoreDataZone-Row58
  5. SiteAlpha-Rack27
  6. BranchNorth-Floor37
  7. BranchEast-Floor16
  8. RetailWest-Floor26
  9. SiteBeta-Rack16
  10. SiteGamma-Perimeter6
17 columns by typefrom the column list below
  • string 13
  • integer 1
  • datetime 2
  • boolean 1

Columns

17 columns in four groups
blueprint · 17 columns
columntypedescriptionexample
Text 13 columns
event_idstringUnique identifier for each security event recorduniqueEVT-001-A2B3C4D5
device_idstringUnique identifier for the IoT device reporting the eventDEV-GW-01
device_typestringType or model of the IoT device (e.g., gateway, sensor, router)7 typesgateway
device_locationstringPhysical or logical location of the device (e.g., site name, rack, zone)optionalSiteAlpha-Rack2
network_segmentstringNetwork segment or VLAN where the device is connected9 segments · optionalVLAN-10
event_typestringType of security event (e.g., unauthorized access, malware detected, firmware update, device reboot)8 valuesunauthorized_access
event_severitystringSeverity level of the event (e.g., critical, high, medium, low, info)critical · high · medium · low · infocritical
event_descriptionstringDetailed description of the security eventoptionalUnauthorized access attem…
remediation_statusstringCurrent status of remediation actions for the event (e.g., open, in_progress, resolved, ignored)open · in_progress · resolved · ignoredresolved
reported_bystringSource reporting the event (e.g., device agent, network monitor, admin)3 values · optionalnetwork monitor
firmware_versionstringCurrent firmware version of the device at the time of the eventoptionalv2.5.1
vendorstringDevice manufacturer or vendor name8 vendors · optionalAcmeIoT
device_statusstringOperational status of the device at event time (e.g., online, offline, degraded)online · offline · degraded · maintenance · optionaldegraded
Numbers 1 column
uptime_secondsintegerDevice uptime in seconds at the time of the event0 or more · optional89300
Dates and times 2 columns
event_timestampdatetimeDate and time when the security event occurred2024-06-01T09:12:45Z
remediation_timestampdatetimeDate and time when remediation was completed (if applicable)optional2024-06-01T09:35:20Z
True or false 1 column
compliance_flagbooleanIndicates if the event has compliance implications (true/false)optionaltrue

Use it for

  • compliance flag33%37 of 112 rowsmean uptime seconds b…59.5ksens…99.3Medge…95.4kgate…34kcame…

    A telecommunications dashboard

    The compliance_flag rate, uptime_seconds by device_type and a breakdown of device_location. Excel, Power BI or Tableau.

  • Why do the 20 edge-compute rows have a mean uptime_seconds of 99,275,079?

    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 events with device_id, device_type and device_location to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 17 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 dataset112 rows17 columns
Yours1,000 rows17 columnsdevice_location: UK only

blueprint · telecom-iot-device-security-events

Behind this dataset

Same schema. As many rows as you need.

These 112 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.

Rules it was built with
  • Each device must log uptime and downtime events daily.
  • Security events are categorized as minor, major, or critical.
  • Devices must report firmware version at each event occurrence.
  • Any critical security event triggers a compliance review record.
  • Uptime percentages are calculated weekly per device model.
  • Devices without security events for 30 days receive a proactive health status.
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
telecom-iot-device-security-events

More in Telecommunications

Browse all
Also in Telecommunications5G Standalone (SA) Core Network LocationsMobile Data Usage Pattern DatasetNetwork Element Alarms and Fault ManagementAll 1,966 datasets

What should your data show?

Preview 20 rows free
No signup. No card.