Presentation overview
The Big Break Era: A Journey into the Fourth Industrial Revolution examined the transition toward increasingly interconnected devices and services. I delivered the presentation in March 2020.
- Sensor
Measure occupancy or temperature; retain units and timestamps.
- Gateway
Forward measurements across an authenticated communications boundary.
- Application
Interpret the measurement and authorize a control decision.
- Actuator → environment
Change ventilation; the changed environment feeds the sensor again.
Technology and security
The talk connected wireless communications and 5G with smart homes, connected vehicles, and access-control systems. It explored both the engineering possibilities of these systems and the security implications of expanding their connectivity.
The central question was how the benefits of interconnection change the boundaries defenders must understand. Device behavior, network access, and application functions become connected security concerns.
Technical context: connectivity changes the control loop
This explanation develops the presentation’s themes; the architecture below is a hypothetical example rather than a system built or tested for the talk.
In a connected building, an occupancy sensor might send readings to a gateway, an application might infer which rooms are in use, and a controller might adjust ventilation. The important security question is not simply whether the network connection is fast. It is whether each participant is allowed to influence the next step, and what happens when information is delayed, altered, or unavailable.
The path from measurement to decision also explains why electronics and software need to be considered together. A plausible-looking value can be wrong because of sensor drift, a software conversion error, an incorrect unit, or deliberate manipulation. A network alert alone cannot distinguish all of these causes.
Separating communications from authorization
Wireless connectivity makes information accessible, but access to a transport does not automatically justify access to an application function. A device may be permitted to publish measurements without being permitted to reconfigure another device. An operator may be allowed to view a dashboard without changing the control policy.
Faster communication can improve responsiveness while leaving these authorization questions unchanged. Likewise, local processing can reduce dependence on a remote service, but introduces software and configuration that must be maintained at the edge. Neither a cloud-based nor a local design is secure merely because of where it runs.
Engineering trade-offs to examine
Three questions make the discussion more concrete:
- What is the required behavior during disconnection? Retaining the last command, stopping, and continuing autonomously can have different consequences.
- Which changes need explicit authorization? Firmware, device identities, control thresholds, and remote-access settings deserve separate consideration.
- What evidence survives a fault? An investigation needs enough timing and configuration history to distinguish an outage from a malicious change.
These questions become especially important when software affects a physical process. NIST’s Guide to Operational Technology Security treats safety, reliability, and performance as distinct requirements alongside security. That 2023 guidance is a later technical reference, not material attributed to the March 2020 presentation.
The connection to Industry 4.0 is therefore concrete: integrating systems also integrates their dependencies, administrative decisions, and failure modes.
Connection to my work
This presentation joins my electronics background with research into networks and malware. It complements my IoT threat landscape presentation and Near Cloud security research.
Archive record
The title, month, and presentation scope are recorded in my 2024 technical presentations history. This is a retrospective of the 2020 talk.