Defining Security Requirements With the Common Criteria: Applications, Adoptions, and Challenges

Nan Sun, Chang-Tsun Li, Hin Chan, Ba Dung Le, Md Zahidul Islam, Leo Yu Zhang, Warren Armstrong

Introduction

In an era of increasingly sophisticated cyberattacks, trust in Information and Communications Technology (ICT) products is no longer a given; it must be rigorously demonstrated. The Common Criteria (CC), formalized as ISO/IEC 15408, serves as the international gold standard for certifying the security of IT products. However, despite its prestige, the CC is often viewed as a "black box"—a complex, expensive, and time-consuming hurdle for developers. This paper demystifies the CC framework, analyzes global adoption trends, and shares practical lessons from the Australian DACCA project to provide a roadmap for building "secure-by-design" technology.

Understanding the Common Criteria Framework

Unlike many security standards that evaluate an entire organization (such as ISO 27001), the Common Criteria is laser-focused on the specific product being evaluated, known as the Target of Evaluation (TOE). This product-centric approach ensures that security claims are verified through independent testing.

Conceptual relationship between security elements in the Common Criteria framework.

As shown in the conceptual model above, the framework operates by identifying Threat Agents and the Threats they pose, which increase the Risk to valuable Assets. To mitigate these risks, Owners require Countermeasures that are both Sufficient and Correct. The evaluation process provides the necessary Confidence that these countermeasures effectively reduce risk to an acceptable level.

A statistical analysis of the official Common Criteria Portal (data through December 2021) reveals significant industry trends. Examining a dataset of 1,619 active and 3,226 archived certified products, several key insights emerge:

  • Dominant Sectors: Integrated Circuits (ICs) and Smart Cards are the clear leaders in certification. This is driven by the high-security requirements of the telecommunications and financial payment industries.
  • Assurance Levels: The most common rigor level for certification is EAL4+, accounting for 33.5% of analyzed profiles. This level represents a "sweet spot" between rigorous testing and commercial viability.
  • Regional Differences: The United States leads in certifying against specific Protection Profiles (PPs)—standardized security requirements for product categories—while other nations often rely on more general Evaluation Assurance Level (EAL) ratings.

Challenges to Implementation

Despite its benefits, the CC faces three primary barriers to wider adoption:

  1. Cost: The average certification lifecycle costs approximately $250,000 USD, making it prohibitive for smaller vendors.
  2. Time: Evaluations typically take 6 to 12 months, which can exceed the entire lifecycle of fast-moving technologies like IoT devices.
  3. Complexity: The standard is notoriously dense, requiring specialized expertise to navigate and implement correctly.

The DACCA Case Study

The Development of Australian Cyber Criteria Assessment (DACCA) project provides a blueprint for overcoming these hurdles. By focusing on creating a Protection Profile for encryption key management, the project demonstrated that security requirements should not be developed in isolation. Instead, an iterative cycle of "Q&A -> Draft -> Refine -> Polish" with industry partners is essential to creating a usable and effective security specification.

The Future of Common Criteria

To remain relevant in a rapidly evolving landscape, the CC must adapt to emerging frontiers such as Blockchain, Quantum Computing, AI Systems, and IoT. Future work focuses on three key areas:

  • Automation: Using formalized tools to write security specifications and reduce human error.
  • Agility: Integrating CC requirements into "Agile" development cycles rather than treating security as a final checkbox.
  • Linguistic Expressiveness: Improving the standardized language of the CC to better describe the unique threats inherent in decentralized and autonomous systems.

Summary updated

Abstract

Advances of emerging Information and Communications Technology (ICT) technologies push the boundaries of what is possible and open up new markets for innovative ICT products and services. The adoption of ICT products and systems with security properties depends on consumers' confidence and markets' trust in the security functionalities and whether the assurance measures applied to these products meet the inherent security requirements. Such confidence and trust are primarily gained through the rigorous development of security requirements, validation criteria, evaluation, and certification. Common Criteria for Information Technology Security Evaluation (often referred to as Common Criteria or CC) is an international standard (ISO/IEC 15408) for cyber security certification. In this paper, we conduct a systematic review of the CC standards and its adoptions. Adoption barriers of the CC are also investigated based on the analysis of current trends in security evaluation. Specifically, we share the experiences and lessons gained through the recent Development of Australian Cyber Criteria Assessment (DACCA) project that promotes the CC among stakeholders in ICT security products related to specification, development, evaluation, certification and approval, procurement, and deployment. Best practices on developing Protection Profiles, recommendations, and future directions for trusted cybersecurity advancement are presented.
BibTeX
@article{sun2022defining,
  author = {Nan Sun and Chang-Tsun Li and Hin Chan and Ba Dung Le and Md Zahidul Islam and Leo Yu Zhang and Md. Rafiqul Islam and Warren Armstrong},
  title = {{Defining Security Requirements With the Common Criteria: Applications, Adoptions, and Challenges}},
  journal = {IEEE Access},
  year = {2022},
  doi = {10.1109/access.2022.3168716},
}
Figure