Preparing for NDcPP Certification: A Guide for Network Device Manufacturers

11 نوفمبر 2026

A firewall’s management configuration can change what belongs in its security evaluation. That makes the customer’s intended deployment an early scoping decision.

To prepare for NDcPP (Network Device collaborative Protection Profile) certification, manufacturers should first define the customer deployment, target release, hardware models, management architecture and security claims that the evaluation must cover.

Before starting an NDcPP certification project, define:

  • The customer’s certification requirement

  • The target release and hardware models

  • The management and deployment architecture

  • The security functions and Protection Profile modules in scope

For manufacturers of firewalls, switches, routers, Wi-Fi systems and network operating systems, these decisions give the engineering team and evaluation laboratory a practical starting point.

What does NDcPP certification assess?

The Network Device collaborative Protection Profile, or NDcPP, defines security requirements used in Common Criteria network device certification. Its baseline covers functions such as administrator authentication, secure management, security audit, cryptography and trusted software updates.

Additional security claims may require compatible Protection Profile modules. Examples include stateful traffic filtering, VPN gateway functionality and MACsec. The permitted combinations depend on the NDcPP version and its associated allowed-with list.

The customer’s requirement helps identify the intended configuration and additional claims. It does not remove mandatory profile requirements.

For NDcPP v4.0, exact conformance requires the Security Target to include all mandatory security functional and assurance requirements, plus selection-based requirements where the selected options make them applicable.

Stage 1: Make the first discussion specific

NDcPP certification preparation should begin before the Security Target is complete. The Security Target defines the product’s security requirements and evaluation scope.

Bring three inputs to the initial discussion.

  1. The customer requirement. Share the tender wording or procurement specification. Identify the requested certification scheme, Protection Profile Modules, assurance requirements and product listing. A request for NIAP validation needs exrta planning discussion on top of a request for EUCC certification.

  2. A product summary. List the hardware models, firmware or software release, management options and security functions the customer intends to use. Include the target deployment date and significant planned changes.

  3. A deployment diagram. Show the device, management components, controllers and external services, including authentication, logging and cloud dependencies. Mark which components you expect to include in the evaluated product, known as the Target of Evaluation (TOE).

Existing documents are enough to begin this discussion. Record unresolved questions explicitly, particularly where a component’s inclusion or exclusion could change the evaluation.

A firewall example

Consider a hypothetical manufacturer with two firewall appliances running firmware 5.2. Both use the same codebase, but the larger appliance has a different cryptographic accelerator. Firmware 5.3 is in development.

The initial request is to “certify the firewall range.”

The customer then confirms that it needs both models running firmware 5.3, using central management, with evaluated stateful traffic filtering claims.

The scope is now concrete: firmware 5.3, both hardware implementations and the central management configuration.

This changes the preparation work. The team must examine the hardware differences, determine the applicable profile combination and prepare evidence for the intended release. Documentation describing firmware 5.2 alone will leave questions about the configuration the customer plans to buy.

Illustrative configuration. The evaluation boundary depends on the product architecture, security claims and selected certification route.

What belongs in the evaluation NDcPP

Stage 2: Complete an NDcPP readiness assessment

An NDcPP readiness assessment compares the intended product configuration with the applicable requirements and evaluation activities.

Read the Protection Profile alongside its Supporting Document. The latter describes the evaluator’s examination of product explanations, administrator guidance and test results. Use the versions and interpretations accepted for the selected certification route.

For each applicable requirement, ask:

  • Does the product implement the required behavior?

  • Can an administrator configure and operate it using the supplied guidance

  • Can the evaluator reproduce the configuration and test the claim?

These questions help distinguish implementation work from documentation and test preparation.

Where the team needs support interpreting requirements or defining the evaluation boundary, QIMA’s Common Criteria consultation services cover readiness assessments, scope definition and documentation preparation.

Distinguish a missing explanation from a missing capability

Suppose a device supports remote administration through HTTPS and SSH, but its guidance explains failed-login handling only for HTTPS.

The team needs to establish how SSH handles unsuccessful attempts and restores administrator access. If the behavior meets the applicable requirements, the missing explanation can be documented. If it does not, an engineering change may be necessary. The evaluation activities examine authentication failure handling for each supported remote administration method.

Trusted updates provide another useful check. An instruction to “upload the firmware image” leaves unanswered questions: how is the update authenticated, what happens when authentication fails, and how does the administrator check the installed version? These behaviors form part of the trusted update evaluation activities.

Give each identified gap an owner, an action and a target date. Prioritize changes that affect the implementation, architecture or planned release, then align the supporting documentation.

What needs preparing for NDcPP evaluation

Replace assumptions with decisions the team can use

Starting assumption

Decision needed for evaluation preparation

“We will evaluate the current firmware.”

Confirm the customer’s target release and identify what must be implemented and documented for it.

“Both models use the same software.”

Identify hardware and cryptographic differences that could affect security claims or testing.

“The evaluation covers all firewall features.”

Agree the applicable profile combination, evaluated functions and management configuration.

“The administrator manual is finished.”

Check whether it explains the required configuration, operation, failure handling and recovery procedures.

Use these decisions to develop the NDcPP Security Target and supporting evidence. A readiness assessment should leave the team with an actionable work list and a proposed scope that the laboratory can review.

For a broader project checklist, QIMA’s cybersecurity downloads page includes a Guide and Checklist for Common Criteria Evaluations, updated to cover the EUCC scheme.

Address the questions particular to your product

Switches and routers

Create a model matrix covering processors, operating system versions, cryptographic implementations and relevant interfaces. Identify differences that could affect how security functions operate.

If the customer requires evaluated MACsec or VPN functionality, check the relevant module and permitted profile combination.

Explain why evidence from one model should apply to another. A shared family name or software release does not, by itself, explain the significance of different hardware.

Wi-Fi systems

Show the access points, controller, management components and authentication services in the deployment diagram.

The WLAN Access System PP-Module v1.0 describes a distributed TOE containing a controller and one or more access points. That makes the relationship between these components relevant to the evaluation boundary.

As of 29 October 2026, the ND-iTC allowed-with list, version 4.0r2 dated 16 September 2026, lists WLAN Access System v1.0 with NDcPP v3.0e, but does not list it with NDcPP v4.0. Because allowed-with lists and scheme transition conditions can change, confirm the current list before fixing the evaluation plan.

Network operating systems

Explain what the manufacturer supplies and what the customer must provide.

Under NDcPP v4.0, a virtual network device includes the network functionality and operating system within the virtual machine. An application or service whose underlying operating system remains outside the TOE does not qualify as that virtual network device configuration.

A complete virtual appliance and an application installed on a customer-managed operating system therefore raise different scoping questions. Show the proposed boundary, platform versions and dependencies before committing to an evaluation approach.

Stage 3: Give the evaluator a reproducible configuration

Before formal evaluation begins, agree which release, models, management components and security functions the evidence will cover. For the hypothetical firewall project, that means preparing the agreed firmware 5.3 configuration on both hardware implementations, together with the central management components. The handover should enable the evaluator to:

  • Install and identify the agreed software and hardware versions

  • Apply the evaluated security settings

  • Connect the required external services

  • Access the equipment, licenses and tools needed for testing

  • Restore a known configuration when a test needs to be repeated

Review subsequent product changes against that agreed configuration. A cryptographic library update, management interface change or hardware substitution may require changes to the evidence or evaluation plan.

Keep the responsibilities clear. The laboratory performs the evaluation. Under EUCC, a certification body makes the certification decision based on the laboratory’s evaluation. Under NIAP, NIAP validates the laboratory’s results and issues a certificate following a successful evaluation. Publication and any product listing follow the selected scheme’s process.

After certification, give sales and deployment teams a precise description of the covered models, releases and operating conditions. They need to connect the evaluated configuration to what the customer orders and installs.

NDcPP certification FAQs

What should a manufacturer define before NDcPP certification?

Define the customer’s certification requirement, target release, hardware models, management architecture, security claims, deployment conditions and applicable Protection Profile modules. Confirm that the proposed route addresses the customer’s procurement requirement.

Does a firewall need an additional Protection Profile module?

A firewall seeking evaluated claims for stateful traffic filtering may need the relevant firewall module alongside the NDcPP baseline. Confirm the permitted profile combination for the selected NDcPP version and certification scheme.

How does EUCC relate to NDcPP?

EUCC is a European cybersecurity certification scheme based on Common Criteria. NDcPP defines technical requirements for network devices. Confirm whether the proposed evaluation and assurance requirements support the intended EUCC route; conformance to NDcPP does not automatically establish EUCC certification.

QIMA’s Common Criteria and EUCC certification overview explains the broader framework and preparation requirements.

Can preparation start before the Security Target is complete?

Yes. The customer requirement, product summary and deployment diagram provide a practical starting point. They help identify scope questions and readiness work that can inform the Security Target.

Discuss NDcPP certification preparation with CCLab

CCLab, a QIMA company, supports Common Criteria preparation through readiness assessments, Protection Profile interpretation, evaluation scope definition, Security Target and developer documentation. These assistance activities complement the independent evaluation process.

Bring your customer requirement, product summary and deployment diagram to the first discussion.

Discuss your NDcPP certification preparation with QIMA CCLab’s cybersecurity team.

مقالات ذات صلة