Power line communication is a method of carrying data over existing electrical wiring. It injects modulated signals onto power cables and uses coupling, filtering and modem interfaces to separate data from mains electricity, often for building automation, smart metering or home networking.
How Power Line Communication Works
Power line communication, or PLC, turns existing electrical wiring into a data path by superimposing modulated signals on the mains conductors. The power and data layers share the same physical medium, so PLC depends on coupling circuits, filtering, and modem design to keep communications usable without interfering with electrical service.
That shared-medium design is the defining feature. PLC is attractive because it avoids new cabling, but it also means the communication channel inherits the layout, noise, and electrical characteristics of the building or utility network it rides on.
Where PLC Is Used
PLC is most often deployed where wiring already exists and adding separate communications media would be costly or impractical. Common uses include building automation, smart metering, lighting control, and home networking, where the infrastructure already spans many endpoints and a modest data rate is acceptable.
In operational settings, PLC can connect devices that are physically distributed but electrically joined. That makes it useful for retrofit projects and utility environments, especially where the communication fabric must reach places that would be awkward to cable separately.
Security and Reliability Considerations
PLC inherits the strengths and weaknesses of the electrical network it uses. Noise, impedance changes, transformers, switching equipment, and poorly controlled wiring can reduce signal quality, narrow coverage, or create unstable links. Because the data rides on an electrical medium rather than a purpose-built network, exposure can extend farther than operators expect if the wiring leaves a defined boundary.
From a security perspective, the main concern is trust in the shared medium. A PLC segment may be accessible from more outlets, panels, or branches than a team initially assumes, so encryption, authentication, segmentation, and careful filtering matter when PLC carries sensitive commands or metering data.
Failure mechanism: Uncontrolled coupling or weak isolation can let signals propagate beyond the intended circuit, while electrical noise and poor filtering can corrupt frames and create intermittent service failures.
Impact: Attackers or unauthorised listeners may gain visibility into traffic, and operators may see unreliable control, inaccurate telemetry, or degraded availability in connected systems.
Design and Deployment Trade-offs
PLC is usually chosen for reach and convenience, not for raw performance. Its practical value comes from leveraging existing wiring, but that same convenience introduces variability that network designers must account for, including topology uncertainty, interference from appliances, and limited predictability across building segments.
For practitioners, the key design question is whether PLC is being used as a convenience layer or as part of an operational control path. The more important the traffic, the more careful the design must be around isolation, signal coupling points, and the assumptions made about who can physically access the wiring.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | PLC deployments that carry operational traffic need authenticated users and operators. |
| SC-8 — Transmission Confidentiality and Integrity | PLC transmits data over shared wiring, so protecting data in transit is central. | |
| SC-7 — Boundary Protection | PLC depends on physical electrical boundaries that can be wider than expected. | |
| Recommendation — Require strong authentication for systems and operators that manage PLC-connected assets. Protect PLC traffic in transit to preserve confidentiality and integrity on the wire. Segment PLC networks and enforce boundary controls around coupling points and branches. | ||
Practitioner Guidance
What to watch for: Treat PLC as a communications technology with physical and operational constraints, not as a simple substitute for Ethernet or wireless. Validate reach, noise tolerance, and segmentation assumptions in the actual electrical environment before relying on it for critical telemetry or control.
Governance implication: Ownership should cover both the networking function and the electrical installation, because changes to wiring, breakers, filters, or connected equipment can alter security and reliability properties without changing the application layer.
Related resources from NHI Mgmt Group
- What is agent communication poisoning?
- How do IAM teams adjust governance when developers supervise agents instead of writing every line themselves?
- Why do communication tools create sovereignty risk for IAM teams?
- Who is accountable when a communication platform does not meet sovereignty requirements?