Certified - CompTIA Network +

In Episode Ninety-Eight of the Network Plus PrepCast, we take a close look at Internet of Things devices and Supervisory Control and Data Acquisition systems—commonly abbreviated as I o T and S C A D A. These technologies may appear small or specialized, but they are rapidly transforming enterprise and industrial networks. I o T devices include a wide range of sensors, controllers, and connected appliances used in both consumer and business environments. S C A D A systems, by contrast, focus on industrial control and are used to monitor and manage infrastructure such as power grids, water systems, and factory operations.
From a networking perspective, both I o T and S C A D A introduce new challenges. Their communication methods differ from traditional endpoints, and their security posture is often weaker due to limited hardware capabilities or outdated design. Many of these devices are deployed with default settings, minimal encryption, and no regular update process. Despite this, they are being integrated into critical infrastructure more frequently, making them important components in modern networks. The certification exam may include questions on how these systems are deployed, secured, and monitored across various environments.
I o T devices come in many forms, including environmental sensors, smart thermostats, wearable health monitors, and smart lighting systems. They are designed to be network-connected from the start and are typically lightweight in function and size. Unlike servers or desktops, they do not run complex operating systems and often serve a single-purpose role. These devices rely on their ability to communicate efficiently with minimal resource use, which is why they often use specialized low-power protocols and simplified interfaces. Understanding how these devices behave on a network is critical for supporting their functionality.
Communication methods for I o T devices vary widely based on power constraints, coverage area, and data needs. Some devices connect using Wi-Fi or Ethernet, just like standard computers. Others use low-power wireless technologies such as Zigbee, Z-Wave, Bluetooth Low Energy, or LoRaWAN to reduce energy consumption. Many I o T networks use gateways that aggregate device data and forward it to internal systems over a more traditional link. These gateways may also handle protocol conversion, filtering, and even local caching to improve efficiency and reduce latency.
Addressing and identification for I o T devices is often automated and simplified due to the large number of endpoints. Each device has a unique M A C address and may be assigned an I P address through D H C P or static configuration. Administrators frequently use naming conventions to keep devices organized, especially in deployments where hundreds or thousands of sensors must be tracked. Because these devices rarely have screens or keyboards, user interfaces are limited or non-existent. Setup is typically handled through mobile apps, provisioning portals, or management hubs designed specifically for mass deployment.
As the number of I o T devices in a network grows, centralized management becomes essential. Provisioning systems automate the process of enrolling new devices, assigning them addresses, and configuring their operating parameters. Firmware updates can be delivered from a central server, often in batches, to ensure that all devices are using current software versions. Some networks use orchestration tools that apply configuration templates to groups of devices based on their role or location. These systems reduce manual labor and help enforce consistency, a key topic when considering large-scale network administration.
Security is one of the most pressing issues in I o T deployments. Many devices are shipped with default usernames and passwords, which are rarely changed. Some use unencrypted protocols to transmit sensitive data, making them vulnerable to interception. Firmware is often rarely updated, if at all, and many devices lack the capacity for patching or advanced logging. These vulnerabilities make I o T devices attractive targets for attackers looking to gain network access or create botnets. The certification exam may ask you to recognize these risks and identify mitigation strategies such as segmentation, monitoring, or gateway filtering.
S C A D A systems differ from general-purpose I o T devices in both their function and architecture. These systems manage large-scale processes, often in manufacturing or utility contexts. A S C A D A environment includes sensors and actuators in the field, which send data to a centralized controller. This controller interprets inputs, sends commands back to devices, and provides human operators with a graphical interface to oversee operations. The stakes in these networks are high, as a communication failure could affect public safety, service availability, or critical infrastructure performance.
The communication architecture used in S C A D A systems often involves real-time sensor data being sent from field devices to the central controller. These sensors may use older serial protocols that are converted to I P for transmission over modern networks. Timing is critical, and systems must respond to changes within strict parameters. Protocols must be lightweight and reliable, even if bandwidth is limited or connection stability is imperfect. Because of these constraints, S C A D A systems often use specialized transport layers and require careful network planning to meet their unique needs.
Placement of I o T and S C A D A devices within the network must consider performance, reliability, and security. These devices are typically segmented from user devices using V L A Ns or separate physical infrastructure. Gateways often serve as aggregation points, collecting data from numerous sensors before forwarding it to central systems. Isolating control traffic from general-purpose traffic prevents congestion and reduces risk. In many cases, control networks are completely isolated, with only tightly controlled access allowed between management systems and operational devices.
Several protocols are commonly used by I o T and S C A D A systems. For I o T, lightweight publish-subscribe protocols such as Message Queuing Telemetry Transport and Constrained Application Protocol allow devices to send updates with minimal bandwidth and overhead. These protocols are ideal for battery-powered devices with intermittent connectivity. S C A D A systems frequently use industrial protocols like Modbus and Distributed Network Protocol version three. These protocols are designed for minimal overhead and deterministic performance. Understanding which protocol fits a given environment is a topic you can expect to encounter on the exam.
For more cyber-related content and books, please check out cyber author dot me. Also, there are other podcasts on Cybersecurity and more at Bare Metal Cyber dot com.
Gateways serve a vital role in I o T networks by bridging the communication gap between small devices and internal systems. Most I o T devices cannot communicate directly with high-bandwidth or complex services due to their limited resources. Gateways collect messages from multiple endpoints, translate between different protocols, and forward the data to application servers or cloud platforms. In addition to protocol translation, gateways help distribute load by aggregating thousands of messages and performing preprocessing. They reduce congestion, manage retries, and ensure that messages arrive in the correct format for processing by central systems.
Monitoring traffic and behavior is essential when managing I o T systems. Because these devices tend to generate consistent, repetitive data, administrators can define baseline activity levels. Once a baseline is established, any deviation from expected patterns—such as increased frequency, changes in destination, or abnormal payload size—can trigger alerts. These anomalies may indicate misconfigurations, compromised devices, or network faults. Integrating I o T data streams into Security Information and Event Management tools allows for centralized analysis, cross-correlation with other alerts, and automated responses to unusual activity.
S C A D A networks face unique risks due to their direct connection to physical systems. Any disruption in communication or device operation can lead to real-world consequences, including safety incidents or infrastructure downtime. As a result, these networks are typically isolated using firewalls and tightly controlled access points. Because of the sensitivity of these systems, active scanning or intrusive monitoring is often avoided. Instead, administrators rely on passive traffic monitoring to avoid interfering with operations. Understanding this passive approach to S C A D A monitoring is critical when evaluating secure architectures.
Authentication poses a challenge in both I o T and S C A D A environments. Many devices are deployed with shared credentials or rely on simple password-based systems with little variation. Advanced authentication methods, such as certificates or hardware-based tokens, may be unsupported or too resource-intensive. Additionally, some devices lack the ability to rotate credentials or enforce strong password policies. Proper authentication strategies must take device limitations into account while ensuring that unauthorized access is minimized. Recognizing these trade-offs and planning accordingly is important for securing device access across the network.
I o T network segments can be found across nearly every industry. Smart lighting systems use motion sensors and centralized control panels to reduce energy use. Temperature and humidity monitoring sensors are used in storage facilities, data centers, and greenhouses to maintain environmental conditions. Retail and logistics operations rely on inventory tracking tags that communicate position and quantity data in real time. These systems may not transmit large volumes of data, but their continuous operation and cumulative traffic must be accounted for in network design and resource planning.
Power and connectivity constraints also shape how I o T and S C A D A devices are deployed. Many sensors operate on batteries and are expected to last for years without maintenance, which limits how often they can transmit data. As a result, data is often sent in intervals or in bursts rather than in constant streams. Wireless signal strength can be an issue in large facilities or outdoor deployments, requiring the use of repeaters, mesh networking, or long-range wireless protocols. In S C A D A environments, where uptime is critical, devices may include backup communication links such as cellular failover or redundant cabling.
Patch management remains a complex and often overlooked issue in I o T and S C A D A systems. Some devices support automated firmware updates, while others must be updated manually or even physically connected for changes to take effect. Limited storage space, weak processors, and custom operating systems can make patching difficult. In environments where uptime is essential, such as manufacturing floors or power stations, updates must be carefully scheduled to avoid disrupting operations. Understanding these logistical and technical hurdles is vital when developing secure update policies for these devices.
Ultimately, I o T and S C A D A systems represent embedded roles within a larger infrastructure. They are not standalone endpoints but parts of integrated systems that include data collection, control, and feedback. Unlike traditional user devices, their behaviors are often rigid, automated, and purpose-specific. This makes them predictable but also vulnerable to misuse if not properly monitored or segmented. Their integration brings benefits in efficiency and automation, but also introduces new security and management demands that network professionals must address with thoughtful planning and layered defenses.
To recap, I o T and S C A D A systems include small but impactful devices that support operations ranging from building automation to industrial control. These endpoints have unique networking needs, including lightweight protocols, gateway dependencies, and limited user interaction. Their placement, communication behavior, and management practices differ from traditional endpoints. Network professionals must account for power limitations, authentication gaps, update constraints, and protocol compatibility. Recognizing the networking challenges these devices pose will help you design secure, scalable systems and answer related questions on the certification exam.