Breaking News

GLOBAL Wi-Fi NEWS bulletin

AI security requires more than a one-time deployment decision; organizations must manage the platform lifecycle to protect, govern, and strengthen resilience as technology and threats evolve
In this article
  • Security at deployment is only a starting point. AI platforms must maintain that protection as threats, dependencies, and configurations change
  • As AI takes on more consequential decisions and actions, attackers are using the same technology to move faster and target high-value systems
  • Private AI gives enterprises greater control over data, models, and workloads, but requires them to manage the platform lifecycle
  • Organizations should evaluate how reliably AI platforms maintain security, compliance, and resilience over time

Most organizations still evaluate the security of an AI platform the way they would evaluate a brand-new car. They verify that it has the safety features they require (compliance certifications), compare its performance and power (benchmarks), and confirm its quality and capabilities through other users and industry professionals (proven deployments and analyst validation). Once the boxes are checked, they declare it secure. On the day it ships, it probably is.

But attackers don’t operate on your deployment timeline. They operate in the months and years that follow, looking for vulnerabilities in operational processes as patches slip, dependencies drift, and yesterday’s hardened configuration quietly becomes today’s exposure. Real security is not a snapshot taken at go-live. It is determined by how well you patch, update, govern, and audit a system throughout its operational life.

Nowhere is this gap wider, or less understood, than in the AI space.

AI is changing both sides of the security equation. The same capabilities that help enterprises automate workflows and accelerate decisions also benefit attackers.

Why the stakes are rising now

As AI becomes more capable, the implications of failure are more significant. A chat bot informing a human employee that delivers incorrect data is a risk. An agent that autonomously acts based on that incorrect information or worse, a physical device like an autonomous car that acts unpredictably is dangerous or even life threatening. That’s why addressing the shifting security environment that surrounds AI workloads needs to be understood.

AI is changing both sides of the security equation. The same capabilities that help enterprises automate workflows and accelerate decisions also benefit attackers. Threat actors now use AI to find exposed systems, analyze new vulnerabilities, write exploit code, and launch convincing phishing campaigns in a fraction of the time those tasks once took.

AI gives attackers a dramatic increase in speed and efficiency, resulting in less time for defenders to respond. Teams that once had weeks to test and deploy a patch may now have just days. AI also helps attackers identify high-value systems, map how they connect, and adjust tactics when an attempt fails. Periodic reviews and scheduled maintenance windows cannot keep pace with that kind of adversary.

AI platforms also make attractive targets. They hold an organization’s most sensitive data and proprietary models, and they increasingly run agents that act across business systems. A single breach can expose intellectual property, corrupt the outputs leaders use to make decisions, or give attackers a foothold in critical workflows.

Private AI is the first step to enterprise grade protection.

Most enterprises stand up private AI because of security concerns, token economic efficiency, or both. They want their proprietary data, fine-tuned models, and agentic workloads under their control and not with a shared multi-tenant service. This can bring down the total cost of ownership while introducing a level of security by design, and it certainly helps maintain theĀ reliability and accuracy of your data, but it’s just the beginning of what a secure AI strategy looks like.

When you run AI workloads privately, you also inherit lifecycle management responsibilities that provide control but can create vulnerabilities if not managed correctly. Patching, CVE triage, and driver updates can all become opportunities for human error to introduce risk to your data and operational resilience.

Why AI solutions age faster than you think

Traditional IT taught us to expect a certain cadence of vulnerabilities. The AI stack breaks that model, because it is deeper, more heterogeneous, and moves far faster than the systems it sits alongside.

Legacy infrastructure strategies gave security teams a stable foundation: a few standardized vendors, predictable applications, a monthly or quarterly patch rhythm, and a clear perimeter around servers, networks, and stored data.

AI upends each of those assumptions. Open-source frameworks and libraries evolve continuously. GPUs bring their own drivers and firmware. Models respond probabilistically, which makes misuse harder to spot. Data no longer sits in storage; it flows into models through prompts and retrieval pipelines, where attackers can manipulate it. Agentic AI adds software that reasons and acts across multiple systems on its own. Together, these shifts create a larger, faster-moving attack surface and new risks, such as prompt injection and model poisoning, that traditional security tools never anticipated.

Consider the complexity of a single AI application:

  • The inference layer. AI frameworks and packaged microservices are software like any other, with corresponding release cycles and CVEs. They ship improvements and fixes, sometimes weekly. Falling behind creates exposure.
  • The accelerator stack. GPU drivers and firmware carry their own steady stream of security advisories, entirely separate from your operating system.
  • Containers. Nearly the entire modern AI platform is containerized, which means every image is a bill of materials that accumulates known vulnerabilities the moment it’s built. An image that was clean at deployment is rarely clean ninety days later.
  • The model supply chain. Models pulled from public hubs, fine-tuned artifacts, and third-party adapters are code and data you’re trusting implicitly. Without provenance, visibility, and proven repeatability, you can’t see what you’re actually running, the reliability of the underlying data, or that it will deliver the promised results.
  • The data and retrieval layer. RAG pipelines, vector stores, and the content they surface represent their own vulnerabilities for your data and the guardrails you put in place. Defenses against data confusion and prompt injection aren’t set-and-forget; they need to evolve as the threats do.

Each of these layers has its own release rhythm, advisories, and failure modes. Stitched together, change too quickly for quarterly patching. As configuration drift contributes as well, a carefully locked-down environment slowly loosens as models are swapped, pipelines are tuned, and temporary workarounds become permanent.

What effective lifecycle management looks like.

AI security must be designed for the full operational lifecycle, not just deployment. That starts with treating a few core capabilities as essential.

1.Ā Ā Ā Ā Ā Ā  Automated patch and update cadence by default

Manual patching cannot keep pace with AI. Drivers, containers, and dependencies need continuous updates with safe rollback. That demands a unified AI strategy, yet many organizations still operate across conflicting platforms, tools, and security policies. If internal tools are outdated or unavailable, users may turn to third-party AI platforms and expose private data. This shadow AI can quickly expose security gaps that put data and profitability at risk.

2.Ā Ā Ā Ā Ā Ā  Provenance, visibility, and control across the model supply chain

You should be able to identify every model, agent, and workload running in production, inspect its source code, and verify that it is approved, operating as intended, and staying within defined guardrails. Agentic AI can empower all this, as well as make decisions and act without human intervention. That power brings risk. Visibility, guardrails, and control reduce it while enabling productivity gains.

3.Ā Ā Ā Ā Ā Ā  Continuous governance, not point-in-time compliance

Regulatory expectations are always changing. Frameworks and rules keep evolving, which means the “compliant” state you previously certified must be re-earned continuously. When governance is established as part of Day 2 operations, documenting and enforcing compliance to shifting requirements improves your risk profile as well as reduces administrative effort.

4.Ā Ā Ā Ā Ā Ā  Root cause visibilityĀ Ā Ā 

When something goes wrong in the data center, the priority is returning to an operating state as quickly as possible, and that starts with seeing what changed, who changed it, and what was exposed. That visibility must be designed in, not reconstructed after the fact like a scavenger hunt. The organizations that get this right stop thinking of security as a gate their AI platform passes through once and start thinking of it as a tool.

5.Ā Ā Ā Ā Ā Ā  Buy the lifecycle, not just the deploymentĀ 

The organizations with the best security policies implement them beyond just the purchasing of their AI platforms into actual management. They have changed the evaluation criteria from “Is this solution secure today?” to ask, “Who is accountable for keeping it secure two years from now, and how?”

That long-term view reframes the entire decision. A full-stack lifecycle-managed approach, where ongoing patching, updating, and governance are part of the platform, doesn’t simply make processes simpler. It can make a realĀ difference in your balance sheet and risk profile. It also differentiates between a platform that was secure initially and a platform that stays secure.

The hardest part of AI security is not launching a secure platform. The challenge involves keeping that platform secure as threats, technologies, and regulations evolve.

Build AI security for the long run

The hardest part of AI security is not launching a secure platform. The challenge involves keeping that platform secure as threats, technologies, and regulations evolve. Private AI provides greater control and isolation, but those advantages depend on continuous patching, supply-chain visibility, governance, and accountability.

Lifecycle management must be central to the security strategy. Organizations should evaluate AI platforms by how reliably they can be updated, governed, audited, and restored over time. An AI platform is only as valuable as the trust it earns by delivering accurate results and protecting critical data.

HPE Private Cloud AI integrates security and lifecycle management to reduce operational complexity and strengthen platform resilience. Deploying AI securely is only the beginning; long-term value depends on solutions that keep the platform secure, scalable, and trusted over time. This helps organizations build an end-to-end AI strategy that protects critical data, adapts to change, and delivers lasting business value.

Wi-Fi troubleshooting guide header: How to Solve Wi-Fi Issues for AMRs and AGVs — Manufacturing & Warehouse Robotics

How to Solve Wi-Fi and Connectivity Issues for AMRs and AGVs

Autonomous mobile robots and automated guided vehicles are only as reliable as the wireless network they run on. 7SIGNAL gives manufacturing and warehouse IT and OT teams continuous, AI-powered visibility into how robots and the devices around them connect, roam, and perform, helping you find and fix Wi-Fi problems before they stop the floor.

A Robot Without Wi-Fi Is Just Expensive Cargo

AGVs follow fixed routes or markers such as magnetic tape, QR codes, or wires, and rely on centralized control systems that require consistent Wi-Fi to send instructions and receive status. AMRs use onboard sensors, LiDAR, and SLAM to navigate dynamically, and depend on constant access to maps, navigation intelligence, and fleet orchestration platforms over the wireless network.

Whether an AGV waits for a new routing command or an AMR recalculates a path around an obstacle, any Wi-Fi degradation causes downtime, delays, or damage.

7SIGNAL is a leading Wi-Fi performance monitoring platform for manufacturing environments, where wireless reliability for scanners, robots, and connected production equipment drives operational efficiency.

  • Command and control: Fleet management systems dispatch tasks, routes, and stop commands over Wi-Fi. Delayed packets mean delayed responses on the floor.
  • Navigation and fleet orchestration: AMRs continuously exchange map, routing, and task data with fleet software. A weak connection can leave a robot waiting for its next instruction.
  • Telemetry and location: Robots report position and status throughout every route. Packet loss affects telemetry and location accuracy.

The Most Common AMR and AGV Wi-Fi Problems

Problem What happens on the floor How 7SIGNAL catches it
Roaming failures Robot drops off the network mid-route Agents on supported endpoints track every handoff
High latency Robots sit idle waiting for instructions Agents and Sensors measure latency continuously
Packet loss Telemetry and location data degrade Measured per device, per shift, per location
Coverage gaps Navigation blind spots or system halts Sensors test RF along travel paths and robot cells
Sticky clients Robot runs on weak signal until the connection fails Agents identify devices holding distant access points
Multipath and RF shadows Performance changes when layout or inventory changes Sensors re-test continuously, not just at site survey

Why Robot Wi-Fi Problems Are So Hard to Diagnose

When a robot stops, the first question is whether the robot, the fleet software, or the network is to blame. Infrastructure dashboards cannot answer it on their own. They report on access point and controller health, not on what a specific robot experienced on a specific stretch of aisle.

Can your current tools show that a specific AGV had repeated roaming failures in one bay overnight? If not, that gap is where unplanned downtime lives, and where IT, OT, and facilities teams end up debating the cause instead of fixing it.

7SIGNAL is a category leader in client-side Wi-Fi visibility, measuring wireless experience from the endpoint device rather than only from the access point or infrastructure side.

When Robots Stop, Operations Stop

In manufacturing, a Wi-Fi failure stops the production line. In logistics, it stalls picking operations. One hour of unplanned production downtime typically exceeds 7SIGNAL’s annual cost. Gartner estimates enterprise network downtime at $300,000 per hour, while IDC places critical application failure as high as $500,000 per hour.

  • $300K per hour: enterprise network downtime
  • $500K per hour: critical application failure
  • $7,900 per minute: data center downtime

Brief Wi-Fi degradation → Robot stall or missed command → Lost throughput and production delays

How 7SIGNAL Solves AMR and AGV Connectivity Issues

7SIGNAL provides independent, infrastructure-agnostic monitoring that helps you maintain a high-performance wireless environment for AGVs and AMRs. Client-side measurements, independent RF sensing, and AI-powered diagnostics work together, feeding EYERIS AI 1,000+ metrics and KPIs.

  • 7SIGNAL Agents: Deploy on supported Linux, Android, Windows, and macOS endpoints to capture signal strength, roaming, latency, and packet loss from the device perspective, per device, per shift, per location.
  • 7SIGNAL Sensors: Continuously and independently measure WLAN and RF performance along travel paths, around robot cells, and in high-traffic zones. A single sensor can monitor up to six access points.
  • EYERIS AI: Correlates device, network, and environmental data to distinguish among client, driver, access point, DHCP, interference, and configuration issues, and tells your team what to do next.
  • 7SIGNAL MCP integration: 7SIGNAL integrates with large language models through the Model Context Protocol (MCP), allowing customers to bring 7SIGNAL Wi-Fi performance data directly into their AI assistants for diagnostics, ticket creation, and natural-language analysis.

7SIGNAL Agents run on Windows, macOS, Linux, and Android endpoints and perform active and passive Wi-Fi tests 24/7 across laptops, scanners, VoIP phones, and IoT devices.

AI-Driven Diagnostics Compress Hours into Minutes

7SIGNAL helps IT and OT teams move from reactive firefighting to proactive operations. Ask which Zone 3 devices are experiencing roaming failures, and get an answer in seconds, in plain language.

  1. Detect: Find roaming, latency, packet loss, and DHCP anomalies.
  2. Correlate: Connect device, RF, infrastructure, and location data.
  3. Diagnose: Identify the real source instead of dispatching a technician blindly.
  4. Recommend: Provide prescriptive remediation guidance.
  5. Protect uptime: Resolve issues before robots and operators feel them.

Proven Results for Manufacturing and Warehouse Operations

7SIGNAL is a leading Wi-Fi monitoring platform for warehouse and distribution operations, where uninterrupted wireless connectivity for scanners, autonomous forklifts, and pickers is mission-critical to throughput.

7SIGNAL delivered a documented 670% three-year ROI and 43% reduction in network downtime in an independent IDC study, making it one of the most measurably valuable Wi-Fi monitoring platforms in the enterprise category.

Metric Result
Three-year ROI, validated in an independent IDC study 670%
Reduction in network downtime, validated in the same IDC study 43%
Fewer Wi-Fi-related help desk tickets 85%
Faster mean time to identify wireless issues 65%
Reduction in troubleshooting time per incident 59%
KPIs per device, captured in real time 1,000+

Read more: Supporting AGVs and AMRs with Reliable Wireless Connectivity →

10 Steps to Solve AMR and AGV Wi-Fi Issues

  1. Measure from the robot’s perspective. Device-level data shows what each robot actually experiences, not just whether the access point is online.
  2. Map RF along real travel paths. Identify weak signal corridors, sticky client behavior, and packet loss along defined routes.
  3. Monitor roaming continuously. Alert when handoffs slow down or fail against the limits your robot and fleet vendors specify.
  4. Validate latency and packet loss around robot cells. Continuous testing at pick stations, charging areas, and transfer points catches degradation before it causes a fault.
  5. Re-validate coverage as the floor changes. New racking, machinery, and inventory levels change RF behavior long after the original site survey.
  6. Detect co-channel and adjacent channel interference. Measure channel overlap from the device perspective, not just the access point.
  7. Prioritize mission-critical traffic. Use dedicated SSIDs and QoS policies so robot traffic does not compete with general-purpose devices.
  8. Fine-tune AP placement and handoff thresholds. Base every change on actual robot connectivity performance, not guesswork.
  9. Align IT, OT, and facilities on one source of truth. Shared device-level evidence ends the debate over whether the robot or the network is at fault.
  10. Validate before you scale. Baseline Wi-Fi performance before adding robots, zones, or sites, then confirm performance holds after go-live.

Wi-Fi Uptime Protects the Metrics Operations Leaders Already Track

Plant and distribution leaders measure success in throughput, uptime, and return on automation investment. Robot connectivity affects all of those metrics.

  • Materials flow: Keep robots moving inventory and components without unplanned stops.
  • Production uptime: Prevent Wi-Fi from becoming the reason a line or pick operation goes dark.
  • Fleet utilization: Reduce the time robots spend idle waiting on the network.
  • Predictable RF behavior: Give OT teams confidence that routes perform the same way every shift.
  • Automation ROI: Protect the return on your AGV and AMR investment.
  • Scale: Add robots, zones, and sites without adding equivalent monitoring headcount.

š˜¼š™Øš™žš™–š™š™ š™žš™Ø š™„š™”š™šš™–š™Øš™šš™™ š™©š™¤ š™–š™£š™£š™¤š™Ŗš™£š™˜š™š š™žš™©š™Ø š™„š™–š™§š™©š™žš™˜š™žš™„š™–š™©š™žš™¤š™£ š™žš™£ š™€š™™š™œš™šš™š™šš™˜š™+ šŸ®šŸ¬šŸ®šŸ², š™Ÿš™¤š™žš™£š™žš™£š™œ š™©š™š™š š™š™–š™žš™¬š™–š™£ š˜¼š™„ š™‹š™–š™«š™žš™”š™žš™¤š™£ š™žš™£ š™˜š™¤š™”š™”š™–š™—š™¤š™§š™–š™©š™žš™¤š™£ š™¬š™žš™©š™ š™©š™š™š š™š™–š™žš™„š™šš™ž š˜¾š™¤š™¢š™„š™Ŗš™©š™šš™§ š˜¼š™Øš™Øš™¤š™˜š™žš™–š™©š™žš™¤š™£.

As artificial intelligence continues to expand beyond cloud computing, Edge AI is transforming how devices, networks, and intelligent systems operate in real-world environments. Reliable, high-performance wireless connectivity plays a critical role in enabling seamless communication, real-time data transmission, and scalable AI-powered applications.

At EdgeTech+ 2026, š—”š˜€š—¶š—®š—„š—™ will highlight its wireless connectivity technologies, including Wi-Fi 7, Wi-Fi HaLow, and AI edge connectivity solutions, designed to support the evolving demands of smart infrastructure, industrial IoT, and next-generation connected devices.

By combining high-speed wireless performance, long-range connectivity, and flexible integration capabilities, š—”š˜€š—¶š—®š—„š—™ aims to help businesses accelerate the development and deployment of intelligent edge applications.

š—–š—¼š—»š—»š—²š—°š˜ š˜„š—¶š˜š—µ š—”š˜€š—¶š—®š—„š—™ š—®š˜ š—˜š—±š—“š—²š—§š—²š—°š—µ+ šŸ®šŸ¬šŸ®šŸ²

š—”š˜€š—¶š—®š—„š—™ looks forward to engaging with industry professionals, technology partners, and system integrators to explore new opportunities in Edge AI and wireless innovation.

Event: EdgeTech+ 2026
šŸ“ Visit us at the Taiwan AI Pavilion
šŸ”— Learn more about EdgeTech+ 2026 : EdgeTech+ 2026

š˜æš™žš™Øš™˜š™¤š™«š™šš™§ š™š™¤š™¬ š˜¼š™Øš™žš™–š™š™ š™žš™Ø š™š™šš™”š™„š™žš™£š™œ š™—š™§š™žš™™š™œš™š š™©š™š™š š™œš™–š™„ š™—š™šš™©š™¬š™šš™šš™£ š™žš™£š™©š™šš™”š™”š™žš™œš™šš™£š™© š™šš™™š™œš™š š™˜š™¤š™¢š™„š™Ŗš™©š™žš™£š™œ š™–š™£š™™ š™§š™šš™–š™”-š™¬š™¤š™§š™”š™™ š™˜š™¤š™£š™£š™šš™˜š™©š™žš™«š™žš™©š™®.

On October 20, we welcomed hundreds of customers, partners, and members of the media to Synaptics Tech Day 2026.

Almost every engineer I talked to wants the same thing: products that see, hear, and understand the world around them, on the device itself. At Tech Day, that ambition was on full display across the room.

Our partner Grinn showcased a robotic gripper that brings Synaptics tactile sensing, compute, and connectivity together in one system. Its camera recognized each object’s color, while tactile sensors driven by our touch controller felt the object’s shape and size. The Synaptics Coralboardā„¢ SL then provided the compute (using Synaptics Astra SL261x SoC with multi CPUs and NPUs architecture) to decide how to pick it up, managing slip and adjusting grip strength in real time, with Synaptics Wi-Fi 7 keeping it all connected.

Elsewhere, Jorjin’s AR glasses, built on the Synaptics AstraĀ® SR200, recognized artwork and overlaid information about it, and translated a menu into another language on the spot, all within the tight power budget required by eyewear. A hand-cranked Coralboard SL ran an interactive vocal conversation with generative AI, entirely on the device. And a UAV running on an Astra processor used our tri-band Wi-Fi for long-range first-person-view flight control.

Across more than 30 demos from Synaptics teams and partners, the message was clear. Edge and Physical AI Ā is a reality. They are running on working silicon today.

Some of the day’s sharpest insights came from our guests. In his keynote, ā€œSense. Reason. Act.ā€, Dr. Aadeel Akhtar, founder and CEO of PSYONIC, reminded us why his work matters. An early experience meeting a child living with the loss of a limb inspired his mission to make advanced prosthetics accessible. Today, PSYONIC’s touch-sensing bionic technology is improving the quality of life for people who use it, and it is now helping robots adapt to the world around them.

Our panel, moderated by EE Times Executive Editor Nitin Dahad, brought together Aashish Mehta (TacnIQ.ai), George Chowdhury (ABI Research), Vincent Duchaine (Robotiq), Andrew Herson (NVIDIA), and our own Satish Ganesan to explore where AI meets the physical world, with robotics at its center.

Robotics is the ultimate test of Edge and Physical AI: machines that must sense, reason, and act in real time, often alongside people. Their perspectives captured what drives our innovation: intelligence that improves how people live, and how machines work alongside them.

A growing number of Edge and Physical AI applications demand the performance of an MPU with the efficiency of an MCU. That’s why we launched the Astra SR200 Series, defining a new class of microcontrollers: the xMCUā„¢. Together with our MCUs and MPUs, it gives engineers a full range of compute to match every device.

Great silicon needs a fast path for application developers: from prototype to production. The Synaptics Coralboard SL, developed in collaboration with Google Research, is now generally available from DigiKey, and we also announced the new Coralboard SR, built on the Astra SR200 Series, with availability to follow. Both use the open-source Torqā„¢ compiler and runtime, giving developers one consistent way to deploy AI models across the MPU-based Coralboard SL and the SR200, without proprietary lock-in. That’s what we mean by true Edge AI developer freedom.

The era of Edge and Physical AI has arrived, and Synaptics is ready for it. What excites me most is the problem-solving ahead: what our customers will build next, from robots that adjust their grip in real time to drones that help rescue teams reach people faster.

Thank you to our customers, partners, and the global #OneSynaptics teams who made Tech Day 2026 possible.

To every engineer building that future: start prototyping today with Synaptics Coralboard.

Imagine it’s a typical evening.

Someone is streaming a movie in the living room. A teenager is gaming upstairs. A security camera is uploading video clips to the cloud. A smart speaker is playing music in the kitchen. The thermostat is checking weather data online while a robot vacuum quietly maps the floor.

None of these devices know—or care—what the others are doing.

Yet somehow, everything works.

Most homeowners rarely think about what makes this possible. But behind every connected home is a complex network of wireless signals, power systems and communication technologies working together to keep devices connected, responsive and efficient. And as homes become increasingly connected, that challenge grows more difficult every day.

A House Full of Signals

Not long ago, the average home had a handful of connected devices. Today, many homes contain dozens. Wi-Fi routers, smart TVs, streaming devices, smart speakers, security cameras, thermostats, smart appliances, doorbell cameras, tablets, smartphones, wearables and countless sensors all compete for wireless connectivity. Every one of those devices is constantly sending, receiving or waiting for information.

WR168_-_Image_2.png

 

The challenge isn’t simply creating a wireless signal. The challenge is ensuring that signal arrives clearly and reliably in an environment that becomes more crowded every year.

Think about a busy restaurant. Having a conversation with someone across the table is easy when the room is quiet. As more people arrive and the noise level rises, hearing the person you’re talking to becomes more difficult.

Wireless communication faces a similar challenge. As more devices compete for spectrum, signals can interfere with one another, reducing performance and reliability. Keeping communication clear requires far more engineering than most people realize.This is where technology like Qorvo’s works behind the scenes, acting as air traffic control at a busy airport to help dozens of signals safely reach the right destination at the right time by ensuring timing andĀ  there is no interference on the runway.

This is where technology like Qorvo’s works behind the scenes, acting as air traffic control at a busy airport to help dozens of signals safely reach the right destinationĀ while ensuringĀ timing andĀ minimizing interference. Just as controllers coordinate aircraft and keep runways clear of potential interference, such as other planes and service vehicles to birds, RF technologies help signals reach the right destination at the right time without disruption. Here, we explore the technologies that make it all work.

Not Every Signal Belongs

Before information can travel through a wireless device, engineers must ensure the device can distinguish the signals it wants from the countless signals it doesn’t.

That’s where RF filtering comes into play.

RF filtersare specialized semiconductor components that act like bouncers at a crowded concert. Their job is to allow the wireless signals you want to pass through while blocking signals you don’t, enabling devices to focus on the information that matters and ignore the surrounding noise. Without effective filtering, wireless performance would quickly degrade as homes fill with more connected devices operating across multiple frequency bands.

Whether it’s a video doorbell sending an alert, a smart speaker responding to a question or a router handling dozens of simultaneous connections, signal quality starts with ensuring the right signals make it through.

Giving Signals the Strength to Travel

Once a signal has been isolated, it still faces another challenge: getting where it needs to go. Walls, distance, building materials and competing devices can all weaken wireless communication. That’s why connected devices rely on sophisticated RF front-end technologies designed to strengthen desired signals and improve communication reliability.

Power amplifiers (PAs) help boost outbound signals so information can travel farther and more effectively. A PA is a bit like a megaphone for wireless signals. The information is already there, but before the signal leaves a router, smart speaker or connected device, the amplifier boosts its strength so it can travel farther and arrive more reliably. Without power amplifiers, many of the wireless connections we take for granted would struggle to reach across our homes.

Low-noise amplifiers (LNAs)Ā  help devices detect weak incoming signals that might otherwise be lost. If power amplifiers are the megaphones of the wireless world, low-noise amplifiers are the hearing aids. By the time a signal reaches a router or connected device, it may have traveled through walls, floors and long distances, becoming increasingly weak along the way. Low-noise amplifiers help devices detect and strengthen these faint incoming signals while minimizing additional interference. The result is more reliable communication, greater coverage and fewer dropped connections throughout the home.

Together, these technologies help improve:

  • Wi-Fi coverage
  • Data throughput
  • Connection reliability
  • Streaming performance
  • Device responsiveness

Consumers may never see these components, but they experience the benefits every day when devices remain connected and perform as expected.

The Power Behind Every Connection

Strong signals alone aren’t enough. Every connected device also requires power—and lots of it.

Home networking equipment often operates around the clock. Routers run continuously. Security systems remain active day and night. Sensors wait patiently for activity. Smart appliances stay ready for commands. All of that connectivity requires energy.

As the number of connected devices grows, engineers face an increasingly important challenge: delivering performance while minimizing power consumption. Consumers want devices that are always available, but they also want lower energy bills, longer battery life and less heat generation. Balancing those competing priorities requires intelligent power management.

Inside many connected devices, Power Management Integrated Circuits (PMICs) help regulate and distribute power throughout the system.

Think of them as traffic controllers for energy.

They ensure that processors, wireless radios, sensors and memory components receive the power they need when they need it, and conserve energy when they don’t.

Rather than operating every component at full power all the time, modern devices can intelligently place portions of the system into low-power states until they are needed again.

This approach helps reduce:

  • Energy waste
  • Heat generation
  • Standby power consumption
  • Battery drain

The result is a device that remains responsive while consuming less energy over its lifetime.

Building the Future of Connected Homes

The connected home continues to evolve. New applications are emerging for security, entertainment, energy management, health monitoring and home automation. Artificial intelligence is also beginning to make homes more adaptive and responsive to their occupants.

As more devices come online, maintaining reliable communication becomes increasingly important. The future of home networking won’t simply depend on faster wireless standards or more connected devices. It will depend on technologies that improve signal quality, reduce interference, strengthen connectivity and manage power more efficiently.

Because every smart home relies on something surprisingly simple: information moving from one place to another. And behind every successful connection is an invisible journey powered by advanced RF and power technologies working together to keep the modern home connected.

PHP2Shell Does Not Impact Plume

You may have seen recent news about a serious security vulnerability affecting PHP. Security is a top priority in how we run our platform, and we act immediately when an issue like this arises. We want to share what we found.

What is PHP?

PHP is a programming language widely used to build websites and web applications. Many company websites, customer portals and internal tools around the world run on it.

Is Plume Impacted?

Plume services and Plume device firmware are not affected. No action or patch is required for any Plume product.

What Was the Vulnerability?

Details of two critical PHP flaws, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), became public in October 2026. The PHP project released fixes on 21 October 2026. Both flaws carry a severity score of 9.2 out of 10 (CVSS v4.0, Critical) assessed by the PHP project’s advisory team.

In simple terms, an attacker could send a specially crafted request to a website running a vulnerable version of PHP and take control of the server without logging in. These attacks can be hard to spot because the website keeps working normally.

Fixes are available in PHP versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and earlier have no official fix release date and should be moved to a supported version. Systems that do not run PHP are not affected.

What Plume Has Done

As soon as the vulnerability was disclosed, our Information Security team launched a full review across the Plume environment. They confirmed that:

  • No PHP is present on Plume’s internet-facing web servers, including production, verified through our asset inventory and a live sweep
  • Plume Cloud services, including the WorkPass captive portal and public WiFi platform, are not built on PHP
  • Our container and cloud workloads show no PHP components affected by these flaws
  • Plume’s OpenSync device software does not use PHP
  • The Plume mobile apps run on your subscribers’ phones and are not exposed to this vulnerability, and their backend services run in Plume Cloud

Mitigation and Monitoring

Because Plume does not use PHP in these areas, there is nothing to patch and nothing for you to change. As an additional safeguard, our endpoint protection continuously monitors for attacker activity linked to these vulnerabilities. We have detected no indicators of exploitation.

Where You May Want to Check

Some risks can exist outside the Plume products and interfaces you use. Thus, we encourage you to confirm the following:

  • Third-party gateway firmware: If you operate gateways running third-party (ODM) firmware, please confirm with the vendor that any PHP components are updated to a fixed version. We are also engaging our ODM partners to confirm whether their firmware uses PHP. That review is still in progress. We will share an update once the review is complete.
  • Self-hosted captive portals: If you run your own guest sign-in server rather than Plume’s, please confirm with your vendor or IT team that it is patched.
  • Your wider IT estate: Websites, portals and internal tools commonly run on PHP and are worth checking, independently of Plume.

Our Commitment

We will keep you informed as we review partner firmware. If you have any questions, please contact your Plume Customer Success representative or email [email protected].

Thank you for your continued trust.

A new storefront opens. The warehouse adds handheld scanners to the shipping process. More employees depend on cloud applications and AI agents throughout the day. Each of these changes to your business operations places yet another demand on the network, often without dedicated resources on the team to manage them. But what downstream effects does this have on the durability and security of the network?

In the Cisco State of Wireless 2026 report, 98% of respondents at midsize organizations said wireless operations are becoming more complex.Ā However, this raises a key question: can the network support daily business operations and remain manageable as the business grows?

We’ve created a list of tips to make sure the network is built to evolve with you:

1. Start with the work that depends on Wi‑Fi.

Before comparing access points, identify the moments when a poor connection would interrupt the flow of business. A handheld device that can’t update inventory has a different impact than a guest phone that takes a few seconds to connect. Both use Wi‑Fi, but they don’t carry the same weight in the plan.

The Cisco State of Wireless 2026 report found that 80% of midsize respondents reported employee productivity gains from wireless investments. To apply this research in the organization, start by naming the applications and devices behind those gains. Then, test them in the locations where people actually use them at the time of day when the network is busiest.

Can staff move between work areas without losing a session? Do scanners stay connected in the front of the store as well as the stockroom? Does an application still respond when a site fills up?

The answers to these critical questions make a better starting point for a refresh than a coverage map alone.

2. Design for the spaces you have.

An office, shop floor, healthcare clinic, and warehouse all present different wireless conditions. The types of devices change, and so do the building materials, interference, and the number of people connecting to the network. The criteria for success change as well. For example, the infrastructure that makes the Wi-Fi in the warehouse great for the 2.4 GHz scanners won’t have the same criteria for maintaining a good connection in the office.

To ensure that the business stays connected, no matter what kind of space is operated, strong network connectivity is required in every kind of location. Cisco offers Wi‑Fi 7 access points for different performance and deployment needs. Cloud and on-premises platforms come loaded with radio frequency (RF)-enhancing features, such as AI-Enhanced Radio Resource Management (AI-RRM), that can use historical RF data to adjust settings as conditions change.

Put your most complex location in the evaluation. Ask how the proposed design handles the devices and physical layout. A useful demonstration should show what users experience there, along with the measurements the IT team will use to spot trouble in the future.

3. Get help staying on top of incidents.

A device can have a strong wireless signal and still fail to get an IP address, and an employee can report ā€œbad Wi‑Fiā€ when the delay actually comes from an application. To prepare for these inevitable bumps in the road, you need someone on-hand to determine which part of the connection failed, decide what to change, and confirm that the fix worked.

Cisco Cloud Control can examine wireless connection failures across association, authentication, Dynamic Host Configuration Protocol (DHCP), and roaming events through Experience Metrics. For a repeatable fix, Cisco AgenticOps lets teams automate defined tasks. AgenticOps workflows can also request an operator’s approval before an action runs, keeping you in control even when you’re not the one performing the fix.

When evaluating options here, ask to see the evidence, the recommended next step, the action available to the operator, and how the team checks the client afterward.

4. Keep your access policy consistent.

Business growth affects both who and what connects to the network. Opening a new location can bring in variables like contractors, guest devices, AI agents, or equipment that needs access to an application. A new acquisition may even have completely different hardware and policy requirements. The bottom line: rules built separately for each location become harder to maintain as those groups multiply.

Within Cisco Cloud Control, Meraki Adaptive Policy lets teams define groups and access rules directly in the dashboard, then deploy those rules to participating networks. For example, a scanner can be placed in an inventory-specific device group while an employee laptop receives a different level of access. The policy becomes easier to review and maintain when the device groups and their rules are all visible in one place.

To make sure the organization is prepared, ask to see how a device gets its group assignment during an evaluation and find out what happens when it connects elsewhere in the supported environment. That demonstration will tell the team more about day-to-day security management than a list of policy features.

5. Plan for future growth.

The site opened next year may have different wireless needs than the location operated today. It might require more capacity, a different access point, or new devices that need their own access rules. Keeping a growth-oriented mindset helps you proactively prepare the network for expansion as the business evolves. Cisco Cloud Control gives the IT team a place to control the wireless network and the switching and security appliances.

During an evaluation, ask how a proposed design extends to the next location. Which settings can the team reuse? What needs to change for the new space? What will the team be able to see from the dashboard once it opens?

When evaluating a wireless platform, bring these four critical scenarios to the table: a demanding site, a device the business depends on, a failure previously encountered, and an access policy that must work across locations. Ask vendors to walk you through each one. That’s how a growing business can expect more from its network: by judging it against the practical daily operations of the business and the demands the IT team will face as the business expands.

Perfectly good projects are going off the rails and missing their ship dates, because of worldwide chip shortages, as the world’s FABs focus on pumping out AI chips.

As of mid-2026, 32-bit industrial MCUs and power management ICs are running lead times as long as 52 weeks, driven by AI infrastructure eating into the mature foundry capacity that IoT parts depend on. Automotive-grade MCUs are still sitting at 26 to 40 week lead times through Q2 2026. That’s down from the 52+ week peaks of the prior shortage cycle, but still long enough to force a mid-program part change on most connected products.

That number is the actual argument for a Firmware Abstraction Layer (FAL). Not portability as a design virtue. A parts shortage that arrives mid-program and forces a chip swap on a schedule you don’t control.

When that swap happens, the cost depends entirely on how the firmware was written. If power management calls, event loop timers, and socket buffers are wired straight into the original vendor’s SDK, a driver swap turns into a rewrite. That’s especially true when application code up the stack had no business knowing which chip was underneath it. If none of that is wired in, it’s just a new driver behind an interface that hasn’t changed.

The Industry is Moving, But Not Fast Enough To Save You

Silicon vendors know this pain point exists, and 2026 has brought real movement. Silicon Labs launched Simplicity SDK for Zephyr at CES 2026, a QA-tested Zephyr distribution built for its wireless chips. The SDK is MCU-agnostic and lets developers mix MCU vendors inside one project, which is a genuine step toward portability rather than a new flavor of lock-in.

Nordic moved in a similar direction with the nRF93M1, announced at MWC 2026, which ships with built-in coexistence control for Wi-Fi and cellular radios sharing one module.

Both of these solve coexistence within a single vendor’s silicon. Coexistence across vendors is a different problem, and it’s still an open problem at the RTOS layer. Zephyr’s Bluetooth stack currently binds to a single controller, so a product can’t natively run Bluetooth radios from two different vendors at once. A proposal to fix that has been open since July 2025, still not shipped.

So vendors are getting better at owning coexistence on their own chips. Managing radios across vendors is still on the OEM to solve, and that’s exactly what a FAL is for.

Step 1. Identify Every Radio and Every Place They Can Collide

List every radio in the product, whether that’s BLE, Wi-Fi, cellular, or UWB. For each one, write down the vendor, the SDK version, and the frequency band it operates in.

Then map where they can interfere with each other. A Wi-Fi transmission can wipe out an incoming BLE advertising packet on the same band. A cellular modem waking up for a paging window can starve a UWB ranging session of power budget. These collisions come from physics, not software architecture, and a single vendor’s SDK has no idea another radio even exists on the board.

This inventory is the spec for everything that follows. Skip it and you’ll end up designing an abstraction layer for radios that don’t actually fight each other, while missing the pair that does.

Step 2. Design the Power State Machine Before Writing Driver Code

Vendor SDKs manage power per radio. BLE connection intervals, cellular eDRX timers, and Wi-Fi power-save modes each get handled separately, by their own SDK, with no visibility into what the other radios are doing at the same moment.

Replace that with one system-level state machine that every radio driver reports into. Two states cover most products, System_Sleep() and System_Active(). Before switching states, the FAL checks every active radio and picks the lowest power level that all of them can safely handle.

Work out the timing rules on paper first. Decide which radio’s constraints are allowed to hold up a sleep transition and which aren’t. If you get this wrong, you’ll spend the second half of the project chasing power bugs that only show up once two radios are active together.

Step 3. Build One Error Taxonomy Across Every Vendor Stack

A cellular modem times out silently over several seconds. A BLE driver drops the connection instantly with a stack-specific status code that means nothing outside that SDK. If you leave this alone, the application layer will fill up with chip-specific if/else branches for every vendor you’ve ever integrated.

Translate every vendor error into a small set of system-level states instead, things like LINK_TEMPORARY_LOSS or HARDWARE_UNRESPONSIVE. The application layer reacts to these states and never has to know what a specific vendor’s error code means.

This step tends to have the biggest payoff for the smallest amount of code, which is also why teams skip it first under deadline pressure. It doesn’t block a demo. It blocks the fifth product revision, when nobody on the team remembers which vendor’s error code meant what.

Step 4. Put One Component in Charge of Arbitration

Antenna sharing, board-level power rails, shared bus access. When two radios need the same physical resource at the same moment, something has to decide who goes first, and that decision can’t be left to whichever driver happened to initialize last.

Build a single arbitration component that owns every shared resource on the board, and routes every radio driver’s requests through it. Don’t let a driver talk to a shared antenna switch or a shared power rail directly, even when the vendor SDK makes that shortcut tempting.

Most of your real RF debugging time during bring-up ends up here anyway. A clean arbitration boundary keeps those bugs in one file instead of scattered across three different vendor codebases.

Step 5. Wall Off OTA Updates and Certification Scope

Radio firmware updates need their own execution pipe, separate from application code. A failed radio firmware update shouldn’t be able to take down the rest of the product. And when only a wireless component changes, keeping the update isolated means regulatory recertification stays scoped to the radio abstraction module instead of pulling your whole application layer back into scope.

The cost difference here is real. A pre-certified wireless module cuts FCC certification cost by 60 to 80 percent and roughly halves the timeline compared with a custom RF design. Keep the split clean and a wireless-only change stays a wireless-only filing. Mix it with application code, and the whole product can get pulled back into certification scope.

If your OTA pipeline currently pushes application code and radio firmware through the same mechanism, split them now, while it’s a small job, rather than during a hardware revision, when it isn’t a small job anymore.

Where This is Playing Out Right Now

There’s a live example of this on the Zephyr project. A team building on an NXP 88W8987 Wi-Fi combo module wants to add Bluetooth, and the open issue confirms there’s no upstream Bluetooth HCI driver for that chip, even though the Wi-Fi side already works.

The thread lays out three options. Add a second Bluetooth chip from a different vendor. Work from an unofficial vendor driver outside the mainline Zephyr tree. Or redesign the hardware around a different combo chip entirely, which the thread notes isn’t always possible once BOM, supply chain, and certification decisions are already locked in.

Every one of those options costs something, and the reason the team is stuck choosing between them is that nobody drew the FAL boundary early enough. A team that already has a power state machine, an error taxonomy, and an arbitration layer in place can absorb a second radio vendor as a driver-level change. A team without one ends up making this decision in a GitHub comment thread, mid-project, instead of in a design review months earlier. Our previous post goes more into this – Architecting Multi-Radio Embedded Devices with BLE, Wi-Fi, LTE, and UWB.

Decide Ownership Subsystem by Subsystem

You don’t need to own every layer for every product. What matters is deciding, for each of the four systems above, whether you build it yourself or lean on the vendor SDK.

If you’re shipping on a single vendor’s chip for a short product life, with no planned cost-down or radio swap, take the vendor’s SDK as it comes, coexistence tools included. The speed advantage is real, and there’s no multi-vendor problem to solve.

If you’re running radios from more than one silicon supplier, this applies to you. It also applies if you’re building a product line meant to last three to seven years through component shortages and cost-downs. Build the power state machine, error taxonomy, arbitration layer, and OTA isolation yourself. Leave everything else on the vendor SDK.

Most teams don’t need to build a FAL from scratch. They need these boundaries drawn correctly before the second radio vendor shows up as a surprise instead of a plan.

Final Word

Multi-radio products get harder to maintain when the boundaries between vendor firmware and system firmware are unclear. Defining those boundaries early gives your team more options when hardware, suppliers, or product requirements change.

embedUR brings 20 years of experience building wireless stacks, controller firmware, and cross-vendor abstractions for connected products. If you’re planning a multi-radio product or preparing for a hardware refresh, our engineering team can help you define the right firmware boundaries.

Schedule a Firmware Architecture Review with our experts and protect your product roadmap against silicon delays, unexpected chip swaps, and costly recertification cycles.

Every year, NETGEAR and Bitdefender publish the IoT Security Landscape Report, a look at the threats facing the smart devices in our homes.

This year’s edition draws on anonymized security data from about 10.4 million homes, collected from January to September 2026. It shows a clear shift: smart devices aren’t just things hackers try to break into anymore. They can also be used to borrow your internet connection, collect information about your home, or give someone a way into everything else on your WiFi.

The average home now has 24 connected devices. The TV, the kids’ tablets, the smart plug running the lamp, the drive full of family photos. Most of us set them up once and never think about them again.

That’s where the trouble starts. Many devices stop getting safety updates long before we stop using them. And this year, some of the risks don’t even look like hacking.

The good news: most of it is easy to fix, and you don’t have to do it all yourself. NETGEAR Armor, powered by Bitdefender, works quietly in the background to help block threats at the router and flag devices that need attention. Here’s what the report found, and the simple steps that make a difference.

Blue Network Security Statistics Cards oct 2026

THE REALITY

Families keep smart devices for 5 to 10 years. Most makers send safety updates for just 2 to 4. That gap is where most of the risk lives, and the good news is it’s easy to close.

Ā 01Ā Ā It’s not just hacking anymoreĀ 

For years, the big question was whether a device could be hacked. This year’s report asks a bigger one: what could someone do with your devices once they’re on your WiFi? The answer is that a device can be given one of four jobs, and only one of them looks like a break-in.

The job What it means A real example from 2026
Break-in target Automated programs try the door, hunting for an old device or a weak password About 90% of the attack activity in this year’s report
Borrowed connection Your home internet is used to carry someone else’s online traffic Free TV apps that send other companies’ traffic through your TV
Eyes and ears A device collects information about your home and family TVs reported to record audio; hacked street cameras
Open door One weak device gives access to everything else on your WiFi Routers and photo drives at the heart of the home network

Here’s what makes this tricky: the last three can happen while everything seems fine. The TV still streams. The plug still turns on the lamp.

Ā 02Ā Ā Someone’s always knocking on your digital front doorĀ 

Your router is your home’s front door to the internet, and it gets a lot of uninvited visitors. Across the homes in this report, Bitdefender recorded 4.85 billion automated attempts to find a way in over nine months. That’s about two a day for every home, every single day.

This isn’t a person watching your house. It’s automated programs checking millions of homes for an easy target, like a device still using the password it came with. The next most common trick was simply guessing passwords, with 466.6 million attempts recorded.

NETGEAR Armor helps block these attempts at the router level, before they reach your family’s devices. It runs quietly in the background, so there’s nothing to manage.

Ā 03Ā Ā Your TV may know more than you think

The TV is now the riskiest device in most homes, with the largest share of known weak spots in the report (22.7%). TVs stay on the wall for years, often long after the maker stops updating them. One TV model from 2020 still showed up 29.1 million times in the report’s data.

Two other things came to light this year:

    • Some free TV apps can borrow your internet. They let other companies send their online traffic through your TV, using your home’s connection. You agree to it in the fine print when you install the app.
    • Some TVs collect more than what you watch. Public reports, suggest some TVs can pick up voice recordings, your location and details about other devices in your home, even when the TV looks like it’s off.

None of this is hacking in the usual sense. But it’s your home and your internet connection, so your privacy settings across your apps are worth a quick look.

Ā 04Ā Ā The devices you forgot you hadĀ 

Two of the quietest devices in your home are also among the riskiest:

  • Smart plugs (22.4% of weak spots). They’re cheap, tucked behind furniture and rarely updated. Once a plug stops being sold, it often stops getting fixes, but it stays connected for years.
  • Photo and file drives (22%). If your family photos live on a storage drive plugged into your router, it’s a favorite target for criminals who lock up files and demand payment to unlock them.

Add TVs, and these three devices hold 2 in 3 of all the known weak spots in the report.

GOOD NEWS: UPDATES WORK

Last year, streaming sticks and boxes were among the riskiest devices in the home. This year they’re not, largely because people installed their updates.

NETGEAR Armor spots devices in your home with known weak spots, so you know what to update or replace. And it keeps protecting your WiFi after a device stops getting fixes.

Ā 05Ā Ā When the problem comes built in

Some of 2026’s biggest stories weren’t about hackers breaking in. They were about devices that had a problem before they ever reached their owners:

  • Cameras with a hidden back door. In Slovakia, officials examined 279 newly delivered traffic cameras and found a hidden way to take control of them remotely, including built-in passwords that couldn’t be changed. The cameras were kept offline until fixed. About 13,000 similar cameras are in use across Europe.
  • Routers with a back door from the factory. Researchers found a hidden way in, installed before shipping, on 20 router models from one Chinese manufacturer.
  • Hijacked devices put to work. In March, US authorities shut down four networks built from hijacked everyday devices like routers and cameras. One of them, Aisuru, powered record-breaking attacks in 2025.

THE LESSON FOR HOME

A bargain device from a brand you’ve never heard of can cost more than it saves. Who makes a device, and how long they’ll keep it updated, matters as much as the price.

Ā 06Ā Ā What to watch for in 2027Ā 
  • More apps that borrow your internet, Especially on cheap streaming boxes and apps from outside the official app stores. Stick to official app stores and well-known brands.
  • One flaw, many brands. Many smart devices, even from different brands, are built from the same off-the-shelf parts and software. That means a single flaw could affect cameras and video recorders from several brands at once, and some makers will fix it much faster than others. Your best defense: choose brands with a track record of regular updates, keep automatic updates switched on, and retire devices whose maker has gone quiet.
  • More attention on TV privacy. Expect a closer look at what TVs collect and who they share it with. A few minutes in your TV’s privacy settings puts you ahead of the curve.
Ā 07Ā Ā Your six step home check upĀ 

Most smart home risks come from devices that are outdated, set up once and forgotten. All of that is fixable, and most of it takes minutes.

Step What to do
1. Turn on automatic router updates Fixes arrive on their own.
2. Change default passwords Router first, then cameras and other devices.
3. Retire devices that no longer get updates Start with old smart plugs.
4. Check your TV’s privacy settings Turn off viewing data and voice features you don’t use.
5. Put smart gadgets on your guest network Keep them apart from the family’s phones and laptops.
6. Add protection that runs on its own NETGEAR Armor, powered by Bitdefender, helps protect every device on your WiFi, from the kids’ tablets to the smart TV.

And if you ever need a hand, we’re here to help.Learn more about NETGEAR Armor →
Read the full 2026 IoT Security Landscape Report →

Further reading

Your cable passed. Your network still doesn’t work.

A green ā€œPASSā€ on a certification report means one thing: the copper in the wall meets a standard. It does not mean the port delivers a link, an IP address, or a single usable packet. Certification answers ā€œwas the cabling installed correctly?ā€ Validation answers ā€œdoes the network actually work?ā€ Most teams buy one tester and assume it answers both. It doesn’t, and the gap between the two is where many Monday-morning help desk tickets come from.

Think of a restaurant. The health inspector’s grade in the window says the kitchen is clean, the walk-in holds temperature, and everything is up to code. It says nothing about the food. A Michelin inspector does the opposite: sits down, eats the meal, and judges what actually lands on the plate. Certification is the A in the window. Validation is the star. Plenty of restaurants have the A and serve a terrible dinner, and nobody books a table for the inspection grade.

This overview cuts through the jargon: what each kind of testing proves, what it misses, and which tool belongs in your bag.

Key takeaways

  • Certification proves the cable was installed to standard, which is what warranties require. It doesn’t tell you whether the network works.
  • Validation proves the link actually works, at the necessary speed.
  • On a new build, you’ll usually need both. After that, a validation tester covers the daily work: validating changes and troubleshooting problems.

What is cable certification?Ā 

Certification is a compliance check on the physical installation, mostly performed by cabling contractors who installed it. AĀ  certification tester measures the cable against industry standards like TIA-568 and ISO/IEC 11801 and produces a pass/fail report. That report goes to the customer, the general contractor, the cable manufacturer backing the warranty, and in some countries to an auditor.

  • What it checks: wiremap, length, and electrical performance, including crosstalk, plus alien crosstalk where it applies. Cables are graded against the standard for that type of cable (e.g. Cat 6, Cat 6A, and so on). Fiber gets certified too: Tier 1 measures loss and length against the standard, and Tier 2 adds an OTDR trace that shows where along the run the loss happens.
  • What it’s for: newly installed cabling, warranty sign-off, and proving the contractor delivered what was specified. Most cabling manufacturers won’t back a system warranty without a certification report for every drop.
  • What it costs: Requires a significant time investment and the most expensive instrument class, which often run five figures and requires a unit at each end.

Here’s the limit that matters.Ā  Certification tests the cable by itself, with a tester plugged into each end and nothing else attached: no switch, no network, no traffic. It can tell you a Cat 6A cable is good for 10G. It can’t tell you whether 10G will actually show up. A cable can certify perfectly and still sit behind a misconfigured switch port, a wrong VLAN, a dead DHCP scope, or a PoE budget that’s already spent. The report says the copper is good. It says nothing about the network itself.

That’s the health grade: a spotless kitchen, and no promise about dinner.

What is validation?Ā 

Link validation proves the link does its job: plugged into the live network, running at the speed it should, with everything a device needs to get online. A validation tester checks the whole connection, from the jack through the switch and out onto the network, and gives a pass/fail on the key network infrastructure along the way.

When a link fails, the same tester switches from validating to troubleshooting, and tells you what’s wrong and where.

  • What it checks:Ā  the whole live connection, from the jack through the switch to the services behind it. What it’s for: moves, adds, and changes; verifying a drop before a user plugs in; confirming a cable will carry specific speeds like 2.5G, 5G, or 10G before you commit to it.
  • What it costs: minutes per link, on a tool a technician can carry all day.

Validation won’t give you a standards-body certificate. It will tell you whether the port works, which is usually the question someone is asking when they call you.

That’s the Michelin star: it’s earned at the table, not in the kitchen.

Certification vs. validation, side by sideĀ 

CertificationĀ  ValidationĀ 
The questionĀ  Was the cabling installed to standard? Does this link work, at speed, on this network?
What it provesĀ  The cable meets spec The link runs at the speed you paid for and gets devices online
Sends trafficĀ  No Yes, at the live-network level
Measures delivered link speedĀ  No Yes
Tested onĀ  The cable by itself, with a tester at each end The live network: The cable and everything past it, including the switch, PoE, and getting online
OutputĀ  Pass/fail report against a standard Ā Pass/fail on the live link, plus what’s wrong, and where, if it fails
Best momentĀ  New install, warranty sign-off Moves/adds/changes, outages, ā€œit’s slowā€ tickets, and sign-off before handoff
Fails you whenĀ  The problem isn’t in the cable You need a standards certificate for the customer
Who runs itĀ  Typically cabling contractors and installers Field techs, integrators, network engineers, and managed services providers

Do you need both?Ā 

On a new build, usually yes, but at different times and by different people. The cabling contractor certifies once, at handoff. The IT team or integrator validates when the network goes live, and devices get plugged in.

After that, the daily work is validating moves, adds, and changes and troubleshooting ā€œit’s slowā€ tickets. A validation tester handles both. Nobody recertifies a cable to fix a help desk call. Recertification is mostly for when cable is replaced or a warranty claim needs evidence.

Neither one replaces the other. Certification protects you against bad cabling. Validation protects you against everything else.

Validate before you upgradeĀ 

Validation isn’t only for checking what already works. It also tells you whether your network can handle what you’re about to add. Find a weak link before you buy, and it’s a line item in the project budget. Find it after, and it’s an unplanned purchase: new switches or cabling on a rush order, a second trip to install them, and new access points running below spec, or sitting in boxes, until the fix is in.

Take a Wi-Fi 7 rollout. Many Wi-Fi 7 access points need 802.3bt PoE and a multi-gig uplink to run at full performance. On older 802.3at power, they drop into a reduced-power mode with fewer antennas in use on each radio, and some models also slow their uplink. On a 1G switch port, the port itself becomes the bottleneck. And if the uplink from that switch to the rest of the network can’t keep up with the combined traffic at busy times, everyone connected through that switch slows down.

Validating before you buy answers four questions while any problems are still cheap to fix:

  • Can the cable carry the speed? Send real traffic from one end of the cable to the other, and count what doesn’t make it through.
  • Can the port deliver the power? Load-test PoE at the switch port to confirm it can supply the power the access point needs, not just what the switch advertises.
  • Is the port set up right? Check which speeds the port supports, which VLANs it carries, whether DHCP answers, and whether it can reach the controller or cloud service that will manage the access points.
  • Can the backhaul keep up? Measure throughput, loss, latency, and jitter across the uplinks between switches at full speed.

The result is a plan instead of a surprise: you know which cable runs need replacing, which switch ports can’t supply enough power, and which uplinks need upgrading before the first access point arrives. Which tester you need depends on the speeds involved.

Ā Which network tester do you need?Ā 

Tester Best for
LinkRunner AT 1500Ā  Copper networks up to 1G.Ā Ā AutoTest, Cable Test, and PoE testing.
LinkRunner AT 3000Ā  Copper and fiber networks up to 1G.Ā Ā Everything in the 1500, plus Ping/TCP, LANBERT, and Reflector Mode.
With AllyCare Pro: Discovery, Path Analysis, and Ally Intelligence.
LinkRunner AT 4000Ā  Copper and fiber networks up to 1G, with advanced features. Everything in the 3000, plus PacketĀ Capture, iPerf, Periodic AutoTest, and HTTP/FTP response-time testing.
With AllyCare Pro: Discovery, Path Analysis, Nmap, and Ally Intelligence.
LinkRunner 10GĀ  Multi-gig copper and fiber networks: 2.5G, 5G, and 10G.Ā Ā Line-rate performance testing, LANBERT, Capture, iPerf, Discovery, and Periodic AutoTest.
With AllyCare Pro: Path Analysis, Nmap, and Ally Intelligence.
LinkRunner 100GĀ  Fiber links from 25G to 100G.
AutoTest, Ping/TCP, line-rate performance testing, Discovery, and Periodic AutoTest.
With AllyCare Pro: QSFP Insights, FEC threshold settings and grading, Path Analysis, Nmap, and Ally Intelligence.

On every model, AllyCare Pro also adds Link-Live cloud remote control, software updates, repairs and replacement, and priority support.Ā 

Why NetAlly instead of Fluke Networks or TREND Networks?Ā 

On a spec sheet, many network testers from different brands look alike. The difference is focus. Fluke Networks and TREND Networks both lead with cable testing. NetAlly doesn’t make certifiers. Our lineage goes back to the industry’s first handheld network analyzer in 1993.

Every NetAlly tool is built for what happens after the cable passes: whether every user and device, from laptops to cameras and access points, can get on the network, run at full speed, and reach what it needs. That’s true across copper, fiber, and Wi-Fi, from 1G to 100G. That focus shows up in five ways:

  • Troubleshooting depth: LinkRunner tests whether an application actually answers on its port, even where ping is blocked, and breaks a slow DHCP request down step by step to show where it’s stuck. Path analysis* traces every switch and router between the tester and a failing address, with interface statistics at each hop.
  • Ease of use: Ally Intelligence* turns test results into step-by-step guided workflows on supported testers. It distills decades of real-world network engineering knowledge into plain-language instructions anyone on your team can act on. Junior technicians can do more, and senior engineers can fix problems faster.
  • Hardware range: One lineup from 1G copper to 100G fiber. LinkRunner 10G sends real traffic at full 10G and counts every frame that doesn’t make it. LinkRunner 100G is the first 100G tester built for enterprise IT, and it validates the optic and grades forward error correction*, so a degrading fiber shows up while the link light is still green.
  • Beyond the wire: AirCheck G3 and EtherScope nXG run Wi-Fi site surveys with heatmaps, covering 2.4, 5, and 6 GHz, plus automatic pass/fail analysis and noise, SNR, and interference heatmaps*.
  • One collaboration platform: Every NetAlly tool uploads to Link-Live, so wired and Wi-Fi results from across your team land in one place. Link-Live also builds full topology maps*, and a senior engineer can take control of a tester in the field from anywhere*.

*Requires an AllyCare Pro subscription.Ā 

The bottom lineĀ 

Certification is the health inspection grade: the kitchen is clean and up to code. Validation is the Michelin star: someone ate the meal, and it delivered. A ā€œPASSā€ in the window doesn’t excuse a bad meal. Your users never see the kitchen; they only taste what comes out of it.

If your job ends at the installer’s handoff, certify. If your job starts when someone says ā€œthe network is slow,ā€ validate. For most network teams, that second job is the one that shows up every day.

Only NetAlly has purpose-built handhelds for wired and wireless networks that can find the problem — across every layer — in a single Tap. Learn more about NetAlly.