Start hereSet the target of evaluation and route
~144 days leftOpen step
Guide library
Certification Europe

EUCC product certification

European Common Criteria cybersecurity certification scheme

Prepare the specific ICT product, version and security claims for a Common Criteria evaluation under EUCC.

Who it applies to

ICT product developers choosing EUCC or where a separate procurement, market or regulatory route calls for product certification.

What you’ll produce

A certificate for the evaluated product configuration, version and assurance scope when granted.

The certificate covers a specific target of evaluation and configuration. Track updates and security incidents against maintenance and disclosure rules.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What do we need the certification to cover?
Confirm the applicable edition, sites, products or service boundary and the certification route. Budget for assessment, changes needed to pass, and maintaining certification.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

EUCC product certification kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Set the target of evaluation and route · Product security + certification lead [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which security claims and product configuration would a customer rely on?
  • Does the buyer name a protection profile or assurance level, and is the requested scope eligible under current EUCC rules?

Worked scenario

A smart-card vendor plans to certify one hardware and firmware combination. It records required configuration assumptions in the security target and checks how a supplier’s chip revision would affect maintenance before release.

What to read next

The whole journeyabout 144 days across 4 steps
  1. 01Set the target of evaluation and routeProduct security + certification lead · ~21 days
  2. 02Make claims and evidence traceableProduct architect + development team · ~42 days
  3. 03Support evaluation and certificationEvaluator + certification body + product team · ~60 days
  4. 04Maintain the evaluated versionProduct security response + certification lead · ~21 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Set the target of evaluation and routeProduct security + certification leadBefore selecting an evaluation facilitySet a start dateSystem boundary; Route memoOpen
Make claims and evidence traceableProduct architect + development teamBefore evaluator fieldworkSet a start dateSecurity target brief; Testing matrix; Technical documentationOpen
Support evaluation and certificationEvaluator + certification body + product teamDuring the assessmentSet a start dateAssessment evidence; Response log; Certification decisionOpen
Maintain the evaluated versionProduct security response + certification leadAfter issuance and on changesSet a start dateChange log; Vulnerability handling procedure; Renewal calendarOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Set the target of evaluation and route

    Who Product security + certification lead When Before selecting an evaluation facility

    Identify exact hardware, firmware, environment and claims. Confirm assurance level, protection profiles and permitted evaluation approach.

    What to produce

    System boundaryMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Route memoSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

  2. 02

    Make claims and evidence traceable

    Who Product architect + development team When Before evaluator fieldwork

    Describe security functionality, assumptions and threats. Link requirements to design, configuration, developer testing and vulnerability analysis.

    What to produce

    Security target briefMemo

    Gather first

    • Product boundary and configuration
    • Applicable protection profile and evaluation scheme
    • Security architecture and threat model

    How to prepare it

    1. Identify the target of evaluation by version, components, users, operating environment and evaluated configuration.
    2. List threats, assumptions and claims, then trace them to functions, requirements and tests. Record protection profile claims and the selected assurance route where applicable.
    3. Review the brief with the evaluator before freezing the official security target. Match every scope and configuration statement across the supporting records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Target and configuration
    Example cryptographic module v2.1, approved boot and hardware configuration only
    Threat
    Unauthorized modification of the module’s firmware
    Assumption
    Physical deployment and operating environment follow administrator guidance.
    Security claim and evidence
    Verified boot checks signed firmware. Link design and negative tests.
    Evaluation reference
    Record the scheme, assurance level and applicable protection profile.

    Check before handing it over

    The target, claims and assumptions describe the exact product a buyer will deploy.

    Use the facility’s current security target guidance for the official submission.

    Testing matrixSpreadsheet

    Gather first

    • Product claims and risk file
    • Applicable standards, study design and acceptance evidence
    • Design configuration and test facilities

    How to prepare it

    1. Trace each claim and risk control to a test objective and acceptance criterion. Specify units, sample rationale, version and worst-case configurations.
    2. Write the method and expected evidence before testing. Assign approvals and record protocol deviations and their effects.
    3. Compare results to the criteria. Keep failed cases, raw data and rationale for repeat testing. Link the approved reports back to the requirements.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or claim
    Battery alert appears before the device can no longer capture readings.
    Protocol and design
    TR-014, test the production hardware and locked firmware at worst-case temperature.
    Acceptance criteria
    Use the limits approved in the design input before testing.
    Sample and method
    Record sample sizes, lot IDs, conditions and operator.
    Result and evidence
    Link signed protocol, raw output and approved report.

    Check before handing it over

    Every essential claim and risk control has evidence or a documented justification for the gap.

    Give the approved protocol to the testing team and the traceability matrix to the submission owner.

    Technical documentationMemo

    Gather first

    • Current authority instructions or package list
    • Approved source records and evidence
    • Submission owner and intended review route

    How to prepare it

    1. Download the current instructions and confirm the required format and version. Create an index that maps every required document or answer to a file and owner.
    2. Cross-check names, version numbers and scope across the package. Check file size, required signatures, redactions and all attachment references against the actual portal requirements.
    3. Have a second person run a completeness check. Save a read-only copy of the submitted version, receipt, and follow-up owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Package section
    Evidence and supporting technical records
    Requirement and source
    Authority package checklist, current release
    Artifact and version
    Test report TR-017 v2, approved
    Responsible person
    Submission coordinator with technical reviewer
    Submission and receipt
    Record the official filing ID and date after upload

    Check before handing it over

    The submitted package can be recreated from the index and the receipt is linked to the exact files.

    Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.

  3. 03

    Support evaluation and certification

    Who Evaluator + certification body + product team When During the assessment

    Give the evaluator controlled access, reproduce tests and respond to findings. Track corrections and submitted evidence versions.

    What to produce

    Assessment evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Response logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

    Certification decisionIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

  4. 04

    Maintain the evaluated version

    Who Product security response + certification lead When After issuance and on changes

    Record restrictions and published scope, follow vulnerability handling and certificate maintenance requirements, and evaluate product changes before distribution.

    What to produce

    Change logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

    Vulnerability handling procedureMemo

    Gather first

    • Product inventory and support dates
    • Disclosure contact and criteria
    • Incident, patch and regulator workflows

    How to prepare it

    1. Define intake, the acknowledgement owner and how to reproduce the report safely. Record product version, technical impact and evidence of exploitation.
    2. Set severity, escalation and reporting decision rules. Assign ownership of mitigation, customer updates and any separate legal clocks.
    3. Run a mock report through disclosure and patch release. Verify deadlines, authority contact and customer instructions before adopting the procedure.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Intake
    Product security mailbox and monitored vulnerability disclosure form
    Triage
    Identify affected releases and preserve reproduction details in the restricted case.
    Escalation
    Page product security for signs of active exploitation. Regulatory affairs checks reporting triggers.
    Release and validation
    Engineer builds a fix, QA runs exploit regression and service tests.
    Disclosure and closure
    Publish an approved advisory, record receipts and update the affected-version register.

    Check before handing it over

    The workflow routes a report to a named decision maker even while facts are incomplete.

    Provide the procedure to support, engineering, security and regulatory owners before the product enters service.

    Renewal calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes