Factory IoT Access Audit Log

This dataset provides detailed, timestamped logs of access events to IoT devices on a manufacturing floor, including user identity, device information, event type, outcome, and compliance indicators. It is ideal for security monitoring, compliance auditing, and operational analysis, enabling manufacturers to detect unauthorized activity, investigate incidents, and improve cyber-physical resilience.

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

Detecting and investigating unauthorized IoT device access

Sample rows

preview · 8 of 120 rows · all 17 columns
audit_log_idstringaccess_resultstringis_compliantbooleandevice_typestringevent_timestampdatetimedevice_idstringdevice_namestringdevice_locationstringuser_idstringuser_namestringuser_rolestringaccess_typestringsource_ipstringsource_macstringfactory_zonestringalert_flagbooleanaction_detailsstring
AL0001successtruesensor2024-06-01T07:15:22DV-1001TempSensor-Assembly1Line A - AssemblyUSR-001Alice Chenoperatorlogin192.168.1.101A1:B2:C3:D4:E5:F6assemblyfalseOperator Alice logged in to TempSensor for morning setup.
AL0002successtrueactuator2024-06-01T07:18:34DV-1002Actuator-Assembly2Line B - AssemblyUSR-002Daniel Wuengineerconfiguration10.0.0.45F2:E1:D3:C4:B5:A6assemblyfalseEngineer Daniel updated actuator speed parameters.
AL0003successtruesensor2024-06-01T07:22:10DV-1003HumiditySensor-QAQA LabUSR-003Carmen YuQAread192.168.2.203B3:A4:D5:C6:E7:F8QAfalseQA Carmen read humidity data for sample batch.
AL0004successtruerobot2024-06-01T07:30:55DV-1004RobotArm-Packaging1Packaging Station 1USR-004Brian Leeengineerfirmware_update10.10.1.5E5:F6:A1:B2:C3:D4packagingfalseFirmware updated on RobotArm-Packaging1 for improved grip.
AL0005successtruesensor2024-06-01T07:42:37DV-1005PressureSensor-Assembly3Line C - AssemblyUSR-005Emily Zhangoperatorwrite192.168.1.55A6:B7:C8:D9:E0:F1assemblyfalseEmily calibrated pressure sensor for new product run.
AL0006successtruecontroller2024-06-01T07:50:21DV-1006Controller-Assembly4Line D - AssemblyUSR-006Frank Linoperatorread192.168.1.109C9:D8:E7:F6:A5:B4assemblyfalseFrank reviewed controller status for shift change.
AL0007successtruerobot2024-06-01T08:00:11DV-1007SorterRobot-QA1QA Sorting AreaUSR-007Gina TangQAlogin172.16.2.100F8:E7:D6:C5:B4:A3QAfalseQA Gina logged in to SorterRobot for batch verification.
AL0008successtrueprinter2024-06-01T08:10:18DV-1008LabelPrinter-Packaging2Packaging Station 2USR-008Helen Maengineerwrite192.168.3.222D1:C2:B3:A4:F5:E6packagingfalseHelen printed new batch labels for shipment.

What the 120 rows show

from the 120-row sample

Success (access result) stands out: 89 of its 90 rows have is_compliant = true, against 0 of 30 for the rest.

  • 74%is_compliant = true
  • 5user roles
  • 7access types
  • 7factory zones
Is compliant rate by access_resultis_compliant = true
0%50%100%99%success89 of 900%failure0 of 110%denied0 of 120%timeout0 of 7
device_type120 rows · 7 values
  1. sensor35
  2. robot21
  3. actuator17
  4. controller15
  5. printer15
  6. unknown10
  7. server7
17 columns by typefrom the column list below
  • string 14
  • datetime 1
  • boolean 2

Columns

17 columns in three groups
blueprint · 17 columns
columntypedescriptionexample
Text 14 columns
audit_log_idstringUnique identifier for each access audit log entryuniqueAL0001
device_idstringUnique identifier of the IoT device accessedDV-1001
device_namestringHuman-readable name of the IoT deviceoptionalTempSensor-Assembly1
device_typestringType or category of the IoT device (e.g., sensor, actuator, robot)7 types · optionalsensor
device_locationstringPhysical or logical location of the IoT device within the factoryoptionalLine A - Assembly
user_idstringUnique identifier of the user or system accessing the deviceUSR-001
user_namestringName of the user or system account accessing the deviceoptionalAlice Chen
user_rolestringRole or job function of the user (e.g., operator, engineer, admin, system)5 roles · optionaloperator
access_typestringType of access event (e.g., login, logout, read, write, configuration, firmware_update)7 valueslogin
access_resultstringResult of the access attempt (e.g., success, failure, denied, timeout)success · failure · denied · timeoutsuccess
source_ipstringIP address from which the access was attemptedoptional192.168.1.101
source_macstringMAC address of the source device initiating the accessoptionalA1:B2:C3:D4:E5:F6
factory_zonestringZone or section of the factory where the event occurred (e.g., assembly, packaging, QA)7 zones · optionalassembly
action_detailsstringAdditional details about the access event (e.g., command issued, configuration changed)optionalUpdated packaging speed
Dates and times 1 column
event_timestampdatetimeDate and time when the access event occurred2024-06-01T07:15:22
True or false 2 columns
is_compliantbooleanIndicates whether the access event complied with security policiesoptionaltrue
alert_flagbooleanIndicates if the event triggered a security or compliance alertoptionalfalse

Use it for

  • is compliant74%89 of 120 rowsis compliant by acces…99%succ…0%fail…0%deni…0%time…

    A manufacturing dashboard

    The is_compliant rate, is_compliant by access_result and a breakdown of device_type. Excel, Power BI or Tableau.

  • Why do 89 of 120 rows have is_compliant = 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 audit logs with event_timestamp, device_id and device_name 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 dataset120 rows17 columns
Yours1,000 rows17 columnsdevice_location: UK only

blueprint · factory-iot-access-audit-log

Behind this dataset

Same schema. As many rows as you need.

These 120 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 access event includes timestamp, device ID, user ID, and access type.
  • Flag events outside approved hours as potential anomalies.
  • Track failed access attempts and escalate if exceeding daily threshold.
  • Link device types to sensitivity levels for prioritizing investigations.
  • Audit trail must not contain personal data beyond user IDs.
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
factory-iot-access-audit-log

What should your data show?

Preview 20 rows free
No signup. No card.