| Measure | Value |
|---|---|
| Organizing units (categories, specialization areas, work roles) | 161 |
| Work roles | 102 |
| Strict elements (tasks and requirements) | 2,488 |
| Subpoints (parsed enumeration lists) | 852 |
| With-examples elements | 3,340 |
| Elements per organizing unit, strict | 15.5 |
| Elements per work role, strict | 22.9 |
| Elements per work role, with-examples | 30.9 |
CyQUAL 1.2.0
Czech Republic National Cybersecurity Qualifications Framework
At a glance
| Steward | CyQUAL, developed at Masaryk University |
| Canonical page | CyQUAL platform |
| Version | 1.2.0 |
| Source format | Open-data JSON export |
| License | Published as open data. Written confirmation from the CyQUAL team permits a derived RDF/JSON-LD graph, on condition of attribution to CyQUAL and to Masaryk University |
framework_summary slug |
cyqual-v1.2.0 |
Structure in cybed: terms
Counts
The source hierarchy is category to specialization area to work role, with tasks and requirements attached to work roles through two join tables that carry no proficiency level, weight, or mandatory flag: every association is an unqualified membership edge. Requirements are additionally classified by a competency and competency-group axis that sits alongside, not beneath, the work-role hierarchy.
Provenance
Source
CyQUAL’s official open-data JSON export, version 1.2.0, retrieved 2026-09-16.
Ingestion
scripts/010-ingest-cyqual.R flattens seven entity arrays and two association arrays into tidy tables and parses the structure into the cybed schema.
License
The open-data JSON export carries no rights field of any kind. The CyQUAL team at Masaryk University confirmed in writing on 2026-09-16 that the framework is published as open data and publicly available, that a derived RDF/JSON-LD graph may be built from it, and that the only condition is attribution to CyQUAL and to Masaryk University.
Caveats
- CyQUAL is ingested from its English-language export when available; the Czech export is used otherwise. No translation happens in the pipeline itself. Provenance records which language a given ingestion run used.
- Neither join table carries a strength-of-relationship signal. A task or requirement attached to a work role is a membership edge only; nothing in the source distinguishes a core task from a peripheral one.
- Organizing-unit counts mix three structurally different tiers (category, specialization area, work role). Analyses comparing “organizing units” across frameworks should filter to
cyqual:WorkRolefor a role-level comparison.