NESAS, the Network Equipment Security Assurance Scheme, is the mobile industry's own answer to "how do we know a 5G base station or core network function was actually built and tested securely?" Jointly defined by GSMA (the mobile operator trade body) and 3GPP (the standards body that specifies the networks themselves), NESAS pairs an audit of a vendor's development process with lab evaluation of specific products against 3GPP SCAS (Security Assurance Specifications) — a growing family of technical specifications that, per 3GPP's own description, is now "the basis for Network Equipment & Cyber security certification programs" adopted well beyond 3GPP's own membership, including by Germany's BSI and India's ITSAR programme.
Key takeaways
- NESAS splits along organizational lines, and 3GPP's TR 33.916, which defines the underlying SECAM methodology, says so in its Scope clause: "This accreditation body has been agreed to be the GSMA.
- GSMA publishes the specifications on its NESAS site.
- 3GPP's SCAS technologies page (by SA3 Chair Suresh P.
- FS.13 v3.0 (section 5.8) describes the product side in four steps.
Who does what, with 3GPP writing requirements and GSMA running the scheme?
NESAS splits along organizational lines, and 3GPP's TR 33.916, which defines the underlying SECAM methodology, says so in its Scope clause: "This accreditation body has been agreed to be the GSMA. 3GPP maintains the overall responsibility for the SECAM scheme and creates the SCASs. The SECAM Accreditation Body is tasked to develop requirements on vendor network product development, the network product lifecycle management process, and SECAM-accreditation for vendors and test laboratories."
- 3GPP's Security Working Group (SA3) writes the requirements and test cases, the SCAS specifications, for each network function class (gNodeB, AMF, UPF, UDM and so on).
- GSMA writes the NESAS specifications for vendor processes, auditors and labs, and runs its own scheme, GSMA NESAS: it appoints auditing organisations, approves test laboratories and publishes results.
Version 3.0 of the NESAS specifications made a separation explicit. GSMA's documents page lists, as a v3.0 change, "Separation of NESAS specifications from scheme run by GSMA", with GSMA's own scheme moved to FS.51 and a defined "Scheme Owner" role. That is how a national body such as Germany's BSI can run its own certification scheme on the same specifications.
Which GSMA documents define NESAS today?
GSMA publishes the specifications on its NESAS site. All core documents moved to version 3.0 on 20 February 2025:
| Document | Title (GSMA) | Current version |
|---|---|---|
| FS.13 | NESAS – Framework | v3.0 (from v2.3) |
| FS.14 | Requirements for NESAS Auditing Organisations, NESAS Security Test Laboratories, and Associated Personnel | v3.0 (from v2.3) |
| FS.15 | Assessment methodology for Vendor Development and Product Lifecycle Processes | v3.0 (from v2.3) |
| FS.16 | Security requirements for Vendor Development and Product Lifecycle Processes | v3.0 (from v2.3) |
| FS.46 | NESAS Audit Guidelines | v3.0 (from v2.1) |
| FS.47 | Methodology for Product and Evidence Evaluation | v3.0 (from v2.0) |
| FS.50 | Requirements for Security Assurance Specification Development | v2.0 |
| FS.62 | Adoption Procedure for Security Assurance Specifications | v1.0 (new) |
| FS.51 | GSMA NESAS Implementation | v1.0 (new; GSMA's own scheme) |
| FS.63 | List of adopted Security Assurance Specifications | v3.0 (12 September 2025) |
The main material change in FS.13 and FS.14 is that test laboratories can now be authorised by a Scheme Owner, making ISO/IEC 17025 accreditation "one of the possible options". The FS.13 v3.0 PDF is the right starting document.
How does a NESAS assessment work, step by step?
3GPP's SCAS technologies page (by SA3 Chair Suresh P. Nair) states: "A NESAS assessment consists of two parts, the first is an audit of the vendor's development and product lifecycle process; and the second is an evaluation of a specific product release and its related documents against test-cases defined in 3GPP SCAS."
| Step | What happens | Who performs it |
|---|---|---|
| 1. Vendor self-assessment | Vendor defines its security-related development and lifecycle processes against FS.16 | Equipment vendor |
| 2. Independent process audit | Auditors assess those processes using FS.15 and FS.46 and issue an audit report | NESAS Auditing Organisation |
| 3. Lab qualification | Lab is accredited to ISO/IEC 17025 or authorised by the Scheme Owner under FS.14 | Accreditation body or Scheme Owner |
| 4. Product compliance declaration | Vendor declares the product release was built under the audited processes | Equipment vendor |
| 5. Product and evidence evaluation | Lab evaluates the evidence and tests the product against the adopted SCAS, per FS.47 | NESAS Security Test Laboratory |
Product evaluation assumes a passed process audit; it is not a parallel check. GSMA's results page adds a time limit: "Process Audits are only valid for two years."
What does a NESAS evaluation report contain, and how long does it last?
FS.13 v3.0 (section 5.8) describes the product side in four steps. The vendor builds the release under its audited processes. It then writes a Compliance Declaration with evidence for each FS.16 requirement, or a rationale where evidence is impossible. The lab's Evaluation Team checks that evidence against FS.47, then runs the tests from the adopted SCAS listed in FS.63. Results must be documented "in a level of detail that allows reproduction of the tests."
Both halves go into one Evaluation Report. FS.13 explains why: "It is the Evidence evaluation that links the tested Network Product to the internally assessed and independently audited vendor processes and this is why only an Evaluation Report that contains both results … is meaningful to a MNO." The report goes to the vendor, who can pass it to operators when they source equipment.
The report is tied to one product release: "A new Release of the Network Product will trigger the need for an up-to-date evaluation," and a change to FS.47 may do the same. Validity periods are left to each Scheme Owner. FS.13 section 9.4 also sets a limit: "In its current construction, NESAS does not include vendor or product certification." Certification needs a Scheme Owner that adds a Certification Body, which is the model BSI follows.
Who are the auditors, labs and audited vendors?
GSMA's auditors and laboratories page lists two appointed auditors, ATSEC and NCC Group, and five approved test laboratories, including atsec information security AB, Potin (Beijing) Technology, Palindrome Technologies and the Security Research Institute of CAICT, each with an expiry date.
The results page (counted 13 November 2026) shows:
- Process audits: 41 in total, nine active, covering ZTE, Ericsson, Nokia, Ribbon Communications, Samsung and Huawei. All active audits but Ribbon's (NCC Group) were approved by ATSEC.
- Product evaluations: 94, from January 2020 to August 2026: Huawei 43, ZTE 29, Ericsson 11, Nokia 10, Samsung 1. Each row names the SCAS applied, for example "TS 33.117, TS 33.511" for a gNodeB.
The list is dominated by large RAN and core vendors. A smaller maker of small cells, Open RAN units or private-5G core software faces the same two-part process.
What do SECAM and the SCAS specifications contain?
SECAM is the framework; SCAS are the per-function requirements and test cases. TR 33.916 lists the evaluation tasks: process assessment, Security Compliance Testing, Basic Vulnerability Testing and Enhanced Vulnerability Analysis, and notes that "Enhanced Vulnerability Analysis is outside the scope of the present release of SECAM." SCAS testing is a defined baseline, not open-ended penetration testing.
The specification family has three layers:
- TR 33.926: product class descriptions, threats and critical assets.
- TS 33.117, "Catalogue of general security assurance requirements": the baseline most product classes share. The current ETSI publication is V19.2.0 (2026-01).
- Function-specific SCAS: TS 33.511 (gNodeB), 33.512 (AMF), 33.513 (UPF), 33.514 (UDM), 33.515 (SMF), 33.516 (AUSF), 33.517 (SEPP), 33.518 (NRF), 33.519 (NEF), 33.520 (N3IWF), 33.521 (NWDAF), 33.522 (SCP), 33.523 (split gNB), 33.326 (NSSAAF), 33.526 (MnF), 33.527 (virtualised products), 33.528 (PCF), 33.529 (SMSF), 33.530 (UDR) and 33.537 (AAnF), plus legacy TS 33.116 (MME), 33.216 (eNodeB) and 33.250 (PGW). GSMA's FS.63 v3.0 lists which are adopted for NESAS, including ETSI NFV-SEC 028 to 031 for virtualisation.
TS 33.117 Clause 4.1 requires the product to be installed, powered on and communicating "over all standardized interfaces and OAM interfaces" before testing, and states that "SCAS testing is not about security in operations and deployments." Clause 4.4, "Basic vulnerability testing requirements," names four aspects in its introduction (port scanning, vulnerability scanning, robustness/fuzz testing and endpoint scanning) and defines three test cases in V19.2.0: TC_BVT_PORT_SCANNING, TC_BVT_VULNERABILITY_SCANNING and TC_BVT_ROBUSTNESS_AND_FUZZ_TESTING. The port-scanning requirement is that "only documented ports on the transport layer respond to requests from outside the system," and the vendor must document in advance "all interfaces providing IP-based protocols," "their open ports and associated services," and their purposes.
How does NESAS connect to EU certification, the 5G Toolbox and the CRA?
EU certification. In February 2021 GSMA proposed NESAS to ENISA as a candidate scheme under the EU Cybersecurity Act, developed with BSI, according to a GSMA deck hosted by ENISA. 3GPP's page says "EU ENISA has adopted 3GPP and GSMA into the certification framework," but ENISA's own certification framework page lists the EU5G scheme among "Schemes under development", and an ENISA presentation of October 2025 says "a EU NESAS scheme is under development". No EU NESAS certificate exists today.
5G Toolbox and CSA2. The EU 5G Toolbox (January 2020) includes measure TM09, using EU certification for 5G components and supplier processes, without naming NESAS. The Commission's 20 January 2026 proposal for a revised Cybersecurity Act would "enable the mandatory derisking of European mobile telecommunications networks from high-risk third-country suppliers"; the proposal does not mention NESAS.
Cyber Resilience Act. The CRA does not mention NESAS or SCAS. It does list routers, modems and switches, and network management systems, as Class I important products in Annex III (see CRA Annex III and IV). NESAS evidence can feed a CRA technical file but gives no presumption of conformity.
National schemes. BSI states that "Since July 2022" it has run BSI NESAS (formerly NESAS CCS-GI) for 5G core components; on 1 September 2026 it published version 2.1, which "implements Version 3.0 of the underlying NESAS scheme of the GSMA." BSI's programme page adds that TR-03163 "designates BSI-NESAS as the only permitted certification program for components that implement functions in the 3GPP core network and NFV MANO classes." India's ITSAR list builds on TS 33.117 and the function-specific SCAS.
Worked example: what does NESAS preparation look like for a small-cell vendor?
Synthetic example; the vendor and product are invented for illustration. A vendor builds a 5G small cell (gNodeB) for private networks and an operator asks for NESAS results.
Pick the SCASTS 33.117 plus TS 33.511 (gNodeB), checked against FS.63. Write the processMap the secure development lifecycle against FS.16: design reviews, code review, third-party component tracking, vulnerability handling, signed builds. Book the auditChoose an auditor from GSMA's list; plan to repeat it within two years. Prepare the interface inventoryList every IP interface, transport protocol, open port and service, as TC_BVT_PORT_SCANNINGrequires.Run your own baseline firstPort scan, vulnerability scan against a current component inventory, and fuzz the exposed protocols before the lab does. Book the lab evaluationwith a compliance declaration for the exact release. Plan re-evaluation per releaseBudget a new lab evaluation for each major release the operator will deploy. Track national rulesFor German core-network sales, check BSI NESAS; for EU sales, plan the CRA file separately.
What are the common pitfalls?
- Treating a product evaluation as a certificate. FS.13 states that NESAS itself includes no certification; certificates come from schemes such as BSI NESAS.
- Reusing a report for a new release. Each evaluation covers one release; a new release needs an up-to-date evaluation.
- Letting the process audit lapse. Audits older than two years move to GSMA's archive.
- Undocumented ports. Any port answering outside the vendor's list fails the port-scanning test case.
- Citing outdated documents. FS.13–FS.16 are at v3.0; the 2021 deck describes v2.x.
- Assuming CRA coverage. NESAS results do not replace CRA conformity assessment for routers or switches.
What is a workable starting point?
Start with TS 33.117, then add the function-specific SCAS. Pass the process audit before product evaluation, and keep it current. Don't confuse SCAS testing with a full penetration test; Enhanced Vulnerability Analysis is outside SECAM's scope. Check national rules, such as BSI's TR-03163 for German core-network classes. Read the v3.0 FS documents and FS.63 on GSMA's NESAS sitebefore scoping.
For a vulnerability-scanning baseline, SoftWSP extracts a CycloneDX 1.6 SBOM from a firmware image, matches its components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report that an engineer reviews. It does not run SCAS test cases, port scans or fuzzing, and it is not a NESAS laboratory. See Device & Firmware Security and firmware SBOM without source code.
This guide quotes 3GPP TR 33.916 and TS 33.117, 3GPP's SCAS technologies page, GSMA's NESAS documents, laboratory and results pages, ENISA and Commission documents, the CRA, and BSI's NESAS pages, as read on 13 November 2026. It is not a substitute for the SECAM/SCAS specifications or NESAS scheme documents and does not constitute compliance or certification advice.
Put this guide to work
Frequently asked questions
What is NESAS, and who actually runs it?
NESAS (Network Equipment Security Assurance Scheme) is a joint scheme defined by GSMA and 3GPP for assuring the security of mobile network equipment — RAN nodes and 5G core network functions. Germany's Federal Office for Information Security (BSI), which operates its own national certification program on top of NESAS, describes it plainly: "The 'Network Equipment Security Assurance Scheme' (NESAS) is a framework developed by the Groupe Speciale Mobile Association (GSMA) and the 3rd Generation Partnership Project (3GPP) to review, assure and improve security in the mobile communications industry." The two bodies split responsibility: per 3GPP's own TR 33.916 (the SECAM methodology specification), "3GPP maintains the overall responsibility for the SECAM scheme and creates the SCASs," while "the SECAM Accreditation Body is tasked to develop requirements on vendor network product development, the network product lifecycle management process, and SECAM-accreditation for vendors and test laboratories" — and TR 33.916 states directly: "This accreditation body has been agreed to be the GSMA." In short: 3GPP writes the technical security requirements and test cases (SCAS); GSMA runs the scheme, accredits test labs and auditors, and governs vendor-process assessment.
What does a NESAS assessment actually consist of?
Two parts, run largely independently. Per 3GPP's own technologies page (authored by SA3 Working Group Chair Suresh P. Nair): "A NESAS assessment consists of two parts, the first is an audit of the vendor's development and product lifecycle process; and the second is an evaluation of a specific product release and its related documents against test-cases defined in 3GPP SCAS." A GSMA-authored overview of the scheme (presented by GSMA's James Moran, hosted on ENISA's site) breaks this into three elements: "Security assessment of vendors' development and product lifecycle processes," "Accreditation of security test laboratories, in accordance with ISO/IEC 17025, to undertake product evaluations," and "Product evaluations by competent test labs using standardised security requirements and test cases." The vendor-process side runs as a self-assessment (vendor defines its processes and signs a Conformance Claim) followed by an independent audit that produces an agreed Audit Report; the product side requires the vendor to declare compliance with its already-assessed processes for a specific product release, after which an accredited test lab evaluates both that Compliance Declaration and the product itself against the applicable SCAS specifications.
What is 3GPP SCAS/SECAM, and what does the generic requirements catalogue (TS 33.117) actually require?
SECAM (Security Assurance Methodology) is 3GPP's overall evaluation framework; SCAS (Security Assurance Specifications) are the per-network-function technical specifications it produces under that framework. Per TR 33.916's own Scope clause, SECAM "defines the complete Security Assurance Methodology... evaluation process... as well as the components of SECAM that are intended to provide the expected security assurance," covering four evaluation tasks: "vendor network product development and network product lifecycle management process assessment, Security Compliance Testing, Basic Vulnerability Testing and Enhanced Vulnerability Analysis" — though it notes "Enhanced Vulnerability Analysis is outside the scope of the present release of SECAM." TS 33.117, "Catalogue of general security assurance requirements," is the specification most network product classes share: per its own Scope, "The present document contains objectives, requirements and test cases that are deemed applicable, possibly after adaptation, to several network product classes... collected in this 'catalogue' document." Its Clause 4.4 ("Basic vulnerability testing requirements") gives a concrete worked example: the Port Scanning requirement states "it shall be ensured that on all network interfaces, only documented ports on the transport layer respond to requests from outside the system," paired with a named test case (TC_BVT_PORT_SCANNING) specifying pre-conditions (a vendor-documented list of every open port and its purpose) and execution steps for the accredited lab to follow.
Which GSMA documents define NESAS, and where are they published?
TR 33.916 itself names the core GSMA scheme documents in its reference list: GSMA FS.13 ("NESAS Overview"), FS.14 ("NESAS Security Test Laboratory Accreditation") and FS.15 ("NESAS Development and Lifecycle Assessment Methodology"). GSMA now publishes the NESAS specifications on its NESAS documents page at gsmaservices.com: FS.13 ("NESAS – Framework"), FS.14, FS.15, FS.16, FS.46 ("NESAS Audit Guidelines") and FS.47 are at version 3.0, dated 20 February 2025, alongside FS.50 v2.0 (requirements for developing a SCAS), the new FS.62 (SCAS adoption procedure), FS.51 (GSMA's own NESAS implementation) and FS.63 (the list of adopted SCAS, v3.0 of September 2025). The same site lists GSMA's appointed auditors, approved test laboratories and published process-audit and product-evaluation results.
How does NESAS connect to EU cybersecurity certification and other national schemes?
GSMA proposed NESAS as a candidate scheme under the EU Cybersecurity Act, and the proposal is documented: per the GSMA-authored ENISA-hosted deck, on 22 February 2021 GSMA's Director General wrote to ENISA's Executive Director, "expressed GSMA support for a single common scheme in accordance with the EU CSA certification framework," and submitted "a formal proposal, developed in conjunction with Germany's Bundesamt für Sicherheit in der Informationstechnik (BSI)," offering NESAS as "an existing scheme that can be adopted and adapted to meet the EU needs." 3GPP's own technologies page states that "EU ENISA has adopted 3GPP and GSMA into the certification framework" for network products, but ENISA's own certification framework page still lists the EU5G scheme among schemes under development, and an ENISA presentation of October 2025 describes an EU NESAS scheme as under development. 3GPP's page separately notes "India, where the Indian Telecommunication Security Assurance Requirements (ITSAR) use the generic SCAS requirements (TS 33.117) and Network Function specific SCASs as the basis for its scheme." At the national level, Germany's BSI has run its own product certification program on top of NESAS since July 2022 — "based on the NESAS evaluation scheme of the GSMA: BSI NESAS, formerly NESAS CCS-GI" — for "highly specialized components in the 5G core network," with BSI's Technical Guideline TR-03163 designating BSI-NESAS as the only permitted certification program for certain German 3GPP-core-network and NFV-MANO product classes; BSI's page states its scheme's version 2.1 "implements Version 3.0 of the underlying NESAS scheme of the GSMA," indicating GSMA's own NESAS framework has itself moved to a v3.0 revision.
Sources
- 3GPP TR 33.916 (ETSI TR 133 916) — Security Assurance Methodology (SECAM) for 3GPP network products: Scope clause (SECAM evaluation tasks, GSMA named as the SECAM Accreditation Body), References listing GSMA FS.13/FS.14/FS.15
- 3GPP TS 33.117 (ETSI TS 133 117) — Catalogue of general security assurance requirements: Scope clause, Clause 4.1 (testing pre-requisites, tool requirements), Clause 4.4 (Basic Vulnerability Testing, Port Scanning requirement and TC_BVT_PORT_SCANNING test case)
- 3GPP: "Security Assurance (SCAS) specifications" — official technologies page, authored by Suresh P. Nair (3GPP SA3 Working Group Chair), first published June 2024 (Highlights Issue 08), last updated April 2025: two-part NESAS assessment, full SCAS specification catalogue table, GSMA FS.50/FS.47 references, EU ENISA and India ITSAR adoption
- GSMA (James Moran): "A year (and a bit) in the life of NESAS" — conference deck, © GSM Association, hosted by ENISA on its Telecom & Digital Infrastructure Security Forum resource page: NESAS three-element structure, vendor process assessment and product evaluation step diagrams, FS.13/14/15/16/46/47 document table, GSMA's 22 Feb 2021 proposal of NESAS to ENISA under the EU Cybersecurity Act
- Germany BSI (Bundesamt für Sicherheit in der Informationstechnik): Certification according to NESAS (BSI-NESAS / NESAS CCS-GI) — official program page: NESAS definition, BSI program operating since July 2022, BSI scheme v2.1 implementing GSMA NESAS v3.0, TR-03163 reference
- GSMA: NESAS documents (FS.13, FS.14, FS.15, FS.16, FS.46, FS.47 v3.0 of 20 February 2025; FS.50; FS.51; FS.62; FS.63) and NESAS maintenance notes
- GSMA: FS.13 NESAS – Framework, version 3.0
- GSMA: FS.63 List of adopted Security Assurance Specifications, version 3.0
- GSMA: NESAS appointed auditors and approved test laboratories
- GSMA: NESAS conformance results (process audits and product evaluations)
- 3GPP TS 33.117 (ETSI TS 133 117) V19.2.0 (2026-01): Catalogue of general security assurance requirements
- ENISA: Cybersecurity certification framework (EUCC published; EU5G under development)
- ENISA (Apostolos Malatras): presentation at DS Cyberdag, October 2025 (EU5G / EU NESAS scheme status)
- European Commission: Cybersecurity of 5G networks – EU Toolbox of risk mitigating measures (January 2020)
- European Commission press release IP/26/105: proposal for a revised Cybersecurity Act (20 January 2026)
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Annex III
- India NCCS: Indian Telecom Security Assurance Requirements (ITSAR) list
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 131 guides.

In this cluster
Questions about this page?
