
CPSTIC taxonomies 2026: a common foundation for security requirements
The CCN is harmonising requirements, threats and assets common to security products. Each family adds requirements for its own functions.
We explain methodologies, CPSTIC access routes, how to choose between CICLON and LINCE, and the technical criteria that affect cloud products, on-premises software and regulated environments.
If your search starts from a specific CCN-STIC guide, this layer separates evergreen content from the blog stream and points you first to the documents that most affect route fit, methodology and evaluation readiness.

The CCN is harmonising requirements, threats and assets common to security products. Each family adds requirements for its own functions.

The updated CCN-STIC 2001 and 2002 guides change how evaluation effort and duration are calculated. Here is what changes when planning your evaluation.

The October 2026 changes that matter most for your project: cloud products, compliance tools, scope review and deadlines.

What ESP-IA (CCN-STIC 2011) is, how it determines which requirements your product will be held to, and what AI vendors should start preparing.

What the DAS for CICLON must include, what the laboratory will review, and what should be clear before the evaluation begins.

What CICLON is, how its iterative evaluation works, and why this methodology matters for cloud products targeting the Spanish public sector.