NIS2
Identify your national implementation and prepare governance, security controls and incident reporting.
European Common Criteria cybersecurity certification scheme
Prepare the specific ICT product, version and security claims for a Common Criteria evaluation under EUCC.
ICT product developers choosing EUCC or where a separate procurement, market or regulatory route calls for product certification.
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.
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
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.
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.
Check product security and any conformity obligations independently.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Set the target of evaluation and route | Product security + certification lead | Before selecting an evaluation facility | Set a start date | System boundary; Route memo | Open |
| Make claims and evidence traceable | Product architect + development team | Before evaluator fieldwork | Set a start date | Security target brief; Testing matrix; Technical documentation | Open |
| Support evaluation and certification | Evaluator + certification body + product team | During the assessment | Set a start date | Assessment evidence; Response log; Certification decision | Open |
| Maintain the evaluated version | Product security response + certification lead | After issuance and on changes | Set a start date | Change log; Vulnerability handling procedure; Renewal calendar | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify exact hardware, firmware, environment and claims. Confirm assurance level, protection profiles and permitted evaluation approach.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Describe security functionality, assumptions and threats. Link requirements to design, configuration, developer testing and vulnerability analysis.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Give the evaluator controlled access, reproduce tests and respond to findings. Track corrections and submitted evidence versions.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Record restrictions and published scope, follow vulnerability handling and certificate maintenance requirements, and evaluate product changes before distribution.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.