If you require a Common Criteria certificate, then you are at the right place.
Start your CC evaluation now with our cyberlab.
Request a free consultation to find out how to get your product certified.
A Common Criteria EAL4+ evaluation is possible within 4 months!
Start your CC certification project in 2024 to get it certified faster before EUCC enforcement begins.
Developers/Sponsors should be aware that the existing Common Criteria national schemes will accept applications by the end of 2024; however, the certification processes must be finalized by February 2027. It is high time to start your CC certification project ASAP with the existing, well-known processes to save time and extra effort. Learn how to prepare for the new EU Cybersecurity Certification.
These new CC certificates which will be issued by the existing national schemes will also remain valid for 5 years even after the EUCC scheme is in operation from February 27th, 2025. From February 27th, 2025, the current national cybersecurity certification schemes will cease operation.
Finish your Common Criteria evaluation in 4 months. If you are not sure whether your product fits for an (ISO 15408) Common Criteria Certification, we offer pre-evaluation services to prepare you for an evaluation project to avoid delays and additional costs during the CC certification process. We offer evaluations up to EAL 4+ or EAL 5 within the shortest possible timeframe using our industry-leading agile methods.
Learn more about Common Criteria assurance levels.
Are you struggling to prepare the required Developer Documents for your upcoming Common Criteria certification project?
Do you think you could use the already existing docs for your product's evaluation?
Do you think it is time-consuming or sometimes even confusing to comply with Common Criteria requirements?
If you are preparing for your first Common Criteria certification project, or you already have experience with CC evaluation but are willing to save some time and money in preparation.
Secure signature creation device - Part 2: Device with key generation / Protection profiles for secure signature creation device – Part 2: “Device with Key Generation”
Secure signature creation device - Part 3: Device with key import / Protection profiles for secure signature creation device - Part 3: Device with key import
Secure signature creation device - Part 4: Extension for device with key generation and trusted communication with certificate generation application / Protection profiles for secure signature creation device – Part 4: “Extension for device with key generation and trusted communication with certificate generation application”
Secure signature creation device - Part 5: Cryptographic Module for Trust Services / Protection profiles for secure signature creation device – Part 5: Extension for device with key generation and trusted communication with signature creation application
Secure signature creation device - Part 6: Extension for device with key import and trusted communication with signature creation application / Protection profiles for secure signature creation device - Part 6: Extension for device with key import and trusted channel to signature creation application
Trustworthy Systems Supporting Server Signing Part 2: Protection Profile for QSCD for Server Signing
Protection profiles for TSP Cryptographic modules - Part 5 Cryptographic Module for Trust Services
Version 2.1, 2018-12-01 (NIAP)
Version 1.3, 2019-09-27
Version 3.2, 2021-04-15
Version 1.4, 2021-10-07
Certificate Issuing and Management Components Protection Profile, Version 1.5
Machine Readable Travel Document with ICAO Application and Basic Access Control (MRTD-PP)
Machine Readable Travel Document with ICAO Application, Extended Access Control (PP-MRTD EAC)
Machine Readable Travel Document using Standard Inspection Procedure with PACE (PACE PP)
Security IC Platform Protection Profile with Augmentation Packages
Machine-Readable Electronic Documents based on BSI TR-03110 for Official Use (MR.ED-PP)
Version 1.3, 1 March 2019 (NIAP)
Version 2.2e, 2020-03-23
Version 1.1, 2020-06-18
Version 1.0, 2016-02-08
Version 1.1, 2019-02-12
Do you want to know more about Common Criteria evaluation?
Do you want to know how you can get your product certified?
CCLab is excited to announce its free on-demand webinar on European Cybersecurity Certification (EUCC) Scheme. Register now and delve into the intricacies of EUCC and its implications for cybersecurity stakeholders.
Find out everything you need to know about Common Criteria evaluation & learn more about our new CC educational material, CCGuide.
Common Criteria (CC) are used for evaluating and certifying the security features and capabilities of information technology (IT) products and systems. The purpose of Common Criteria is to provide a standardized framework that ensures these products meet specified security standards, allowing organizations and governments to make informed decisions about the security of IT products. Common Criteria facilitate a globally recognized approach to evaluating and certifying IT security, enhancing trust and confidence in the security attributes of IT products and systems across various industries and sectors.
The Common Criteria (CC) is an international standard, also available as ISO/IEC 15408 used when evaluating the security properties of IT products and systems. It defines a framework for the oversight of evaluations, syntax for specifying the security requirements to be met and a methodology for evaluating those requirements. The CC is used by governments and other organizations around the world to assess the security of information technology products and is often specified as a prerequisite to procurement. See https://www.commoncriteriaportal.org/cc/ for more information or to obtain the standard.
A Common Criteria (CC) test is an evaluation process used to assess the security features and capabilities of an information technology (IT) product or system against a set of internationally recognized security standards. This testing aims to ensure that the product meets specific security requirements and performs reliably under defined conditions.
There are three parties involved in the CC evaluation process:
1. Vendor or Sponsor. The vendor/developer engages an accredited laboratory and submits their product and associated evidence for evaluation.
2. Laboratory. The laboratory performs the evaluation and reports evaluation results to the scheme. Evaluation is iterative in nature and the vendor is able to address findings during the evaluation.
3. Scheme. Certificate authorizing schemes (also known as a certification body) issue CC certificates and perform certification/validation oversight of the laboratory. Each scheme has its own policies with regard to how the CC is used in that country and what products may be accepted into evaluation