On July 14, 2026, Saudi SASO issued an urgent notice through the SABER system that changes the protocol whitelist used for Perimeter Alarms connecting to the national smart security cloud platform. The update expands the permitted IoT communication protocols from NB-IoT only to include LoRaWAN 1.1 and Matter-over-Thread, while making protocol-stack preregistration a practical gate for SABER CoC completion. For manufacturers, exporters, certification teams, procurement units, and project delivery participants tied to Saudi government procurement and infrastructure projects, this matters because the change is directly linked to Q3 2026 delivery eligibility rather than being only a technical specification adjustment.

What the SABER Notice Confirms

The confirmed facts are limited but clear. Saudi SASO released the notice on July 14, 2026 through the SABER system. The notice concerns Perimeter Alarms that need to connect to the national smart security cloud platform. Under this update, the relevant IoT communication protocol whitelist is no longer limited to NB-IoT and now also includes LoRaWAN 1.1 and Matter-over-Thread. The notice also states that models which have not preregistered the corresponding protocol stack will not be able to complete SABER CoC certification. According to the provided summary, this will affect delivery for all Saudi government procurement and infrastructure projects starting in Q3 2026.

Where the Immediate Pressure Falls

Product and manufacturing teams face a model-level compliance checkpoint

From an industry perspective, the most direct impact falls on companies that manufacture or configure Perimeter Alarms for the Saudi market. The issue is not only whether a device can technically communicate through LoRaWAN 1.1 or Matter-over-Thread, but whether the relevant protocol stack has been preregistered in a way that allows the model to move through SABER CoC. This can affect product configuration control, model mapping, technical file preparation, and the alignment between hardware, firmware, and certification records.

Export and market-entry workflows may tighten around documentation and timing

For exporters and trade-facing teams, the update creates a more explicit compliance dependency between protocol selection and market access. If a model intended for Saudi delivery is not preregistered under the corresponding protocol stack, the blockage appears at the certification stage rather than later in the commercial process. What deserves closer attention is the risk this creates for shipment planning, contract execution, and handover schedules tied to projects beginning in Q3 2026.

Procurement and project delivery teams need closer specification alignment

Procurement units, contractors, and project delivery teams may also be affected because protocol eligibility now has a direct bearing on whether a model can be certified for use in relevant projects. This means bid specifications, approved vendor lists, and delivery planning may need to reflect not just product category compliance but protocol-stack preregistration status. In practical terms, any gap between tender requirements, selected device models, and SABER certification readiness could become a delivery risk.

Certification and testing service providers may see a shift in review focus

For certification-related service providers, the notice points to a change in review emphasis. Analysis shows that protocol-stack preregistration is now part of the compliance path that companies need to verify early, especially for models aimed at public procurement and infrastructure execution. Even where testing scope or documentation requirements are not detailed in the input, the need for closer checking of technical declarations and certification readiness becomes more immediate.

What Companies Should Review Now

Check whether affected models are matched to the correct protocol path

Companies supplying Perimeter Alarms into Saudi projects should review which models are intended to connect to the national smart security cloud platform and whether those models rely on NB-IoT, LoRaWAN 1.1, or Matter-over-Thread. The key practical question is whether the corresponding protocol stack has already been preregistered for the specific model intended for certification and delivery.

Revisit certification files and technical support documents

Observably, this update makes document consistency more important across certification submissions, product technical materials, and project-facing specifications. Companies should pay attention to whether product descriptions, protocol declarations, model identifiers, and supporting technical documents are aligned, since any mismatch could complicate SABER CoC processing. The input does not provide detailed documentation rules, so this should be treated as a compliance review priority rather than a confirmed new filing requirement.

Watch procurement documents and delivery commitments for Q3 2026 exposure

Because the provided summary links the certification issue to all Saudi government procurement and infrastructure project deliveries from Q3 2026, suppliers and project teams should review active tenders, pending orders, and scheduled handovers that involve the affected product category. It is more appropriate to understand this as a timing and eligibility issue that may influence project execution if certification readiness has not been secured in advance.

Follow later execution language before assuming a stable long-term practice

The notice is described as an urgent SABER update, but the input does not include further detail on implementation guidance, review procedures, or any transitional handling. For that reason, companies should continue monitoring how the requirement is expressed in subsequent certification practice, procurement documents, and project acceptance processes rather than assuming that all execution details are already settled.

Why This Looks Like an Execution Signal

Analysis shows that this development is more than a technical whitelist adjustment because it directly links protocol-stack preregistration to SABER CoC completion and then to project delivery from Q3 2026. That gives the update an operational compliance character. At the same time, the available facts do not yet describe the full enforcement method, document thresholds, or any implementation nuances. It is therefore more appropriate to understand this as a rule change with immediate execution implications, while still treating the detailed certification approach and market response as items that require continued observation.

How the Market Should Read This Update

The significance of this notice lies in where it acts: at the intersection of device communication architecture, certification eligibility, and public-project delivery. For affected companies, the issue is not abstract regulatory direction but whether specific models can still pass through the required SABER path in time for Q3 2026 commitments. A neutral reading is that the update should be treated as an implemented compliance signal with direct commercial consequences for the affected product segment, while the finer points of execution still need to be verified through later official wording and market practice.

Basis of This Article and What Still Needs Verification

This article is based on the user-provided news title, event date, and event summary. For developments of this type, relevant source categories typically include official notices, regulator publications, trade or customs authority information, industry association updates, standard-setting documents, and reporting by authoritative sector media. No specific official source link was provided in the input, so the exact official publication path still needs to be verified on an ongoing basis. Further observation is also needed on detailed certification interpretation, execution language within SABER processes, procurement document changes, industry feedback, and how companies implement the requirement in practice.