Mobile operators depend on a handful of network equipment vendors for the radio and core functions that national regulators now treat as critical infrastructure, yet most operators cannot test every product release themselves and have little visibility of how vendors build and maintain it. The GSMA Network Equipment Security Assurance Scheme (NESAS) addresses this with two independent assessments: an audit of the vendor's development and product lifecycle processes, and an evaluation of specific products by accredited test laboratories against 3GPP Security Assurance Specifications (SCAS). This guide explains how NESAS works, which documents define it, what a NESAS result does and does not tell you, how to use it in procurement and supplier risk management, and how it is extending to Open RAN. It is for operator security and procurement teams, vendor product security teams and regulators. The wider 5G architecture is in the 5G Security Guide. Scheme details were checked on the GSMA and 3GPP sites on 27 October 2026.
Key takeaways
- Two parts, both needed. A vendor process audit shows the vendor can build and maintain products securely; a product evaluation shows a specific product version met the applicable SCAS tests. Neither substitutes for the other.
- Results are dated and version-specific. GSMA states that process audits are valid for two years, and product evaluations name the exact product version and the SCAS documents applied. A result for last year's release says little about this year's.
- The test content comes from 3GPP. SCAS documents such as TS 33.117 (general requirements) and the TS 33.5xx series (gNB, AMF, UPF, SEPP, NRF and others) define what labs test, and GSMA's FS.63 lists which SCASes the scheme has adopted.
- Independence is structural. Auditors are selected by tender against criteria agreed by the NESAS Oversight Board, and test laboratories hold ISO/IEC 17025 accreditation.
- NESAS reduces, but does not remove, operator testing. Operators still need integration, configuration and deployment testing, because NESAS evaluates products against baseline requirements, not their network.
How NESAS is structured
NESAS is an industry-funded scheme run by GSMA, with requirements based on GSMA specifications and 3GPP standards so that a single result can be reused across markets rather than repeated for each operator or country. It covers network equipment supporting functions defined by 3GPP and ETSI that operators deploy.
| Element | What happens | Who does it | Output |
|---|---|---|---|
| Vendor development and product lifecycle process audit | Vendor processes are audited against NESAS security requirements, from design through delivery and maintenance | NESAS auditing organisations appointed by GSMA tender | Audit summary report; listed on the GSMA results page; valid two years |
| Product evaluation | A specific product version is tested against the applicable SCAS documents, with evidence from the vendor's audited processes | NESAS security test laboratories with ISO/IEC 17025 accreditation | Evaluation report naming product, version, lab, date and SCASes applied |
| Scheme governance | Selection criteria for auditors and labs, scheme rules and document maintenance | GSMA, NESAS Oversight Board and NESAS Group | FS-series documents |
| SCAS development | Standards bodies write product-class security requirements and test cases | 3GPP SA3, ETSI and others, adopted by the NESAS Group | SCAS specifications, listed in FS.63 |
The NESAS documents
GSMA publishes the scheme as a set of FS documents. The current set, as listed on the GSMA NESAS documents page, is:
| Document | Title | Current version |
|---|---|---|
| FS.13 | NESAS Framework | 3.0 |
| FS.14 | Requirements for NESAS Auditing Organisations, NESAS Security Test Laboratories, and Associated Personnel Accreditation | 3.0 |
| FS.15 | Assessment methodology for Vendor Development and Product Lifecycle Processes | 3.0 |
| FS.16 | Security requirements for Vendor Development and Product Lifecycle Processes | 3.0 |
| FS.46 | NESAS Audit Guidelines | 3.0 |
| FS.47 | Methodology for Product and Evidence Evaluation | 3.0 |
| FS.50 | Requirements for Security Assurance Specification Development | 2.0 |
| FS.51 | GSMA NESAS Implementation | 1.0 |
| FS.62 | Adoption Procedure for Security Assurance Specifications | 1.0 |
| FS.63 | List of adopted Security Assurance Specifications | 2.0 |
For buyers, FS.16 (what vendor processes must achieve) and FS.63 (which product test specifications apply) are the two documents to read first. The NESAS Group adopts SCASes for all schemes, and a scheme owner may use all adopted SCASes or a subset, which matters where national schemes build on NESAS.
SCAS: what products are tested against
3GPP's security assurance work, described in its Security Assurance Methodology (SECAM, TR 33.916), splits requirements into a general catalogue and product-class specifications. TS 33.117, the Catalogue of general security assurance requirements, is maintained by 3GPP SA3 and was at version 20.2.0 (Release 20) when checked. Product-class SCASes include:
| Specification | Network product class |
|---|---|
| TS 33.511 | gNodeB |
| TS 33.512 | Access and Mobility management Function (AMF) |
| TS 33.513 | User Plane Function (UPF) |
| TS 33.514 | Unified Data Management (UDM) |
| TS 33.515 | Session Management Function (SMF) |
| TS 33.516 | Authentication Server Function (AUSF) |
| TS 33.517 | Security Edge Protection Proxy (SEPP) |
| TS 33.518 | Network Repository Function (NRF) |
| TS 33.519 | Network Exposure Function (NEF) |
| TS 33.523 | Split gNB product classes |
| TS 33.524 and TS 33.527 | Container-based products and 3GPP virtualised network products |
| TS 33.526 | Management Function (MnF) |
Check FS.63 for which of these, and which versions, NESAS has adopted, and check the evaluation report for which were applied to the product you are buying. A product evaluated only against TS 33.117 general requirements has not been tested against its product-class requirements.
Reading a NESAS result
- Match the product and version: the GSMA conformance results list the product, product version or release, test laboratory, completion date and SCASes applied. Confirm the version you will deploy is the one evaluated, or that the vendor's audited change process covers the delta.
- Check the process audit date: process audits are valid for two years and older ones move to an archive. An evaluation built on an expired process audit deserves questions.
- Read the scope: the process audit names the processes and products included. A vendor may have audited one product line and not another.
- Ask for the reports: the public list confirms a result exists; request the summary report and evaluation report under NDA, including any findings and how they were resolved.
- Remember what is out of scope: NESAS does not evaluate your configuration, integration, operational processes or the vendor's managed service access to your network.
What NESAS does not cover
- Your deployment: network design, segmentation, configuration and the hardening choices your engineers make after installation.
- Operations: how your teams and managed service providers administer the equipment, including remote vendor support access and the credentials it uses.
- Third-party components outside the evaluated product: the cloud platform under a virtualised core, unless it was itself evaluated against the relevant SCAS, and any integrator-supplied tooling.
- Geopolitical and high-risk supplier questions: NESAS assesses security engineering, not ownership or national security risk, which governments handle through their own regimes.
- Future releases: an evaluation is a point-in-time result for one version; ongoing assurance comes from the audited lifecycle processes and your own regression testing.
- Non-3GPP equipment: transport routers, firewalls, IT systems and OSS/BSS platforms sit outside most adopted SCASes, so they need their own assurance route, such as Common Criteria or your own penetration testing. See the Common Criteria Evaluation Guide.
Using NESAS in procurement and supplier risk
- Write it into requirements: require a current NESAS process audit covering the product line, and a product evaluation against the applicable adopted SCASes for each product class, in RFPs and framework agreements.
- Add version obligations: require the vendor to maintain evaluated status for major releases, or to explain how its audited processes cover interim releases.
- Combine with your own testing: use NESAS results to reduce duplicate baseline testing and spend operator test effort on integration, hardening of your configuration, interfaces and management access. GSMA presents reduced operator testing as a benefit of recognising accredited lab results.
- Add supply chain evidence: request SBOMs, vulnerability handling commitments and patch timelines alongside NESAS. See the SBOM Guide and the PSIRT Guide.
- Feed the risk register: record each supplier's NESAS status, expiry dates and gaps as supplier risk items with owners.
- Re-check at renewal: verify NESAS status at each contract renewal and major upgrade, and treat a lapse as a change in supplier risk.
For national telecoms security regimes, NESAS results are useful supplier assurance evidence, but each regime sets its own duties. See the UK Telecommunications Security Act Guide, the EU 5G Security Toolbox Guide and the Telecoms Security Laws Map.
Questions to put to a vendor
A NESAS listing opens the conversation; these questions close the gaps it leaves. Ask them in RFPs and at each major release.
| Question | Good answer | Warning sign |
|---|---|---|
| Which product lines and sites did the process audit cover, and when does it expire? | Named product lines including yours; audit under two years old with renewal planned | Audit covers a different business unit, or has lapsed |
| Which product version was evaluated, against which SCASes and versions? | Deployed or near version; general catalogue plus the product-class SCAS | Only TS 33.117, or a version several releases old |
| What findings did the lab raise and how were they resolved? | Findings listed with fixes and the release that contains them | Refusal to share findings under NDA |
| How do interim releases inherit assurance? | Audited change and security testing process described, with regression of SCAS tests | No answer beyond "same code base" |
| What hardening guidance ships with the product? | Documented secure configuration, default accounts removed or forced to change, insecure protocols off by default | Hardening left to the operator with no guidance |
| How are vulnerabilities reported and patched? | Published disclosure policy, advisory feed, patch timelines by severity | Fixes only in the next major release |
Preparing for NESAS as a vendor
- Read the requirement set: map existing secure development and lifecycle processes to FS.16 and the audit approach in FS.15 and FS.46, and close gaps before booking the audit.
- Scope the audit deliberately: include every product line your customers will ask about; a narrow scope saves money now and costs sales later.
- Collect evidence as a by-product: design reviews, threat models, code review and test records, vulnerability handling and release records should already exist in your tooling, not be assembled for the auditor.
- Plan product evaluations by demand: evaluate the product classes and releases customers deploy most, against the product-class SCAS as well as TS 33.117.
- Fix, then publish: treat lab findings as release blockers, and publish results on the GSMA list once complete.
- Keep it current: schedule process audit renewal before the two-year expiry, and build re-evaluation into the release plan for major versions so customers are never left on an unevaluated release.
Decision guidance
- Large mobile operators: make NESAS a mandatory baseline for core and RAN suppliers and keep an internal lab for integration and configuration testing.
- Smaller operators and private network operators: NESAS results can replace much baseline testing you could not otherwise afford; focus your effort on secure configuration and management access. See the Private 5G and CBRS Enterprise Network Security Guide.
- Vendors: start with the process audit, since product evaluations depend on audited processes, then evaluate the product classes customers buy most.
- Cloud-native cores: look for evaluations against the virtualised and container-based product SCASes as well as the network function SCAS, because the platform layer carries much of the risk.
- Open RAN: the O-RAN Alliance has established a GSMA NESAS-based O-RAN Security Assurance Program and is developing SCASes for O-RU, O-DU and SMO with GSMA. Until those are adopted and in use, combine NESAS for 3GPP functions with WG11 security test results. See the O-RAN Security Guide.
Where identity fits
Many SCAS requirements concern how network products authenticate administrators and other network functions, protect credentials and log access. NESAS confirms the product can do this; the operator must still configure it. The Salt Typhoon telecom intrusions relied overwhelmingly on valid stolen credentials and on secrets held in device configurations, not on product flaws: a strong product evaluation would not have stopped them. Pair supplier assurance with central authentication for management, unique per-device credentials, certificate-based authentication between network functions and monitoring of management access. See the Telecom Network Security Guide.
Detection and measurement
- Percentage of in-service network products (by product class) with a current NESAS product evaluation for the deployed version.
- Percentage of strategic network suppliers with a NESAS process audit less than two years old.
- Number of deployed versions running outside any evaluated release, and age of the gap.
- Number of open findings from NESAS reports or operator acceptance testing, with median days to close.
- Operator test effort per product release before and after recognising NESAS results.
Common failure patterns
- Accepting a logo instead of a report: procurement records "NESAS compliant" without checking product, version, SCAS or dates.
- Evaluated version drift: the evaluated release was superseded many times and the deployed version was never covered.
- Process audit lapse: the vendor's two-year audit expired and nobody noticed at renewal.
- General catalogue only: a product tested against TS 33.117 but not its product-class SCAS is treated as fully evaluated.
- Configuration ignored: secure-capable products deployed with default accounts, shared management passwords or insecure protocols enabled.
- Assuming regulatory sign-off: treating NESAS as satisfying a national security regime on its own.
Framework mapping
| NESAS activity | NIST SP 800-53 Rev. 5 | NIST CSF 2.0 |
|---|---|---|
| Requiring NESAS in contracts | SA-4 Acquisition Process; SR-5 Acquisition Strategies, Tools, and Methods | GV.SC-05 |
| Reviewing vendor process audits | SR-6 Supplier Assessments and Reviews; SA-15 Development Process, Standards, and Tools | GV.SC-07 |
| Product evaluation and acceptance testing | SA-11 Developer Testing and Evaluation; CA-8 Penetration Testing | ID.RA-01 |
| Version and configuration control | CM-2 Baseline Configuration; CM-6 Configuration Settings | PR.PS-01 |
| Vulnerability handling commitments | RA-5; SI-2 Flaw Remediation | ID.RA-08 |
Practitioner checklist
- Require a current NESAS process audit and product evaluations against adopted product-class SCASes in network equipment contracts.
- Verify product, version, laboratory, date and SCASes on the GSMA conformance results page before acceptance.
- Obtain and review the audit summary and evaluation reports, including resolved findings.
- Track process audit expiry (two years) and evaluated version coverage in the supplier risk register.
- Read FS.16 and FS.63 so requirements reference the right documents and SCAS versions.
- Keep operator testing focused on integration, configuration and management access.
- Pair NESAS with SBOMs, patch commitments and vulnerability disclosure terms.
- For Open RAN, combine NESAS results for 3GPP functions with O-RAN WG11 security test evidence.
Standards and references
- GSMA: Network Equipment Security Assurance Scheme (NESAS)
- GSMA: NESAS Documents
- GSMA: NESAS Auditors and Test Laboratories
- GSMA: NESAS Conformance Results
- 3GPP: TS 33.117 Catalogue of general security assurance requirements
- 3GPP: 33 series security specifications (SCAS and SECAM)
- O-RAN Alliance: Security Update 2026
Related NHI Mgmt Group resources: 5G Security Guide · O-RAN Security Guide · UK Telecommunications Security Act Guide · Telecom Network Security Guide