ENISA ECSF v1

European Cybersecurity Skills Framework

workforce
eu
Published

May 8, 2026

At a glance

Steward European Union Agency for Cybersecurity (ENISA)
Canonical page European Cybersecurity Skills Framework
Version 1
Released 2022-09-19
Source format PDF report with companion JSON and XLSX
License The Role Profiles report PDF is CC BY 4.0 by its own notice. The ingested JSON and XLSX carry no notice, and rest on ENISA’s site-wide notice authorising reproduction with acknowledgement
framework_summary slug ecsf-v1

Structure in cybed: terms

ENISA ECSF structural mapping Frameworkecsf:FrameworkProfileecsf:Profile= cybed:Role= cybed:OrganizingUnitKSAecsf:KSA= cybed:RoleElementcontainscybed:hasOrganizingUnithas elementcybed:hasElement
Click any box or edge label to flip between plain English and the technical schema name.

Counts

Table 1
Measure Value
Profiles 12
Strict elements 374
Subpoints (parsed enumeration lists) 16
With-examples elements 390
Elements per profile, strict 31.2
Elements per profile, with-examples 32.5

Provenance

Source

ENISA’s ECSF reference document.

Ingestion

scripts/010-ingest-ecsf.R parses the structure into the cybed schema.

License

The Role Profiles report PDF is CC BY 4.0 by its own copyright notice. The JSON and XLSX that cybedtools ingests carry no notice of any kind, and rest instead on ENISA’s site-wide notice, which authorises reproduction of ENISA material provided the source is acknowledged. The package does not bundle ECSF source text. Users stage it locally.

Caveats

  • ECSF profiles point at the European e-Competence Framework (e-CF) at fine granularity, but those cross-references are not expanded into RDF triples. Full ECSF coverage requires consulting the source’s e-CF pointers directly.
  • ECSF is aspirational by design. The framework was authored as a high-level interoperability frame across European cybersecurity workforce vocabularies, not as a hiring-grade enumeration like NICE or DCWF. Per-profile element counts read low because the framework is intentionally light at this layer.
  • The ingested data reflects ENISA’s published export at retrieval time. Re-run the ingestion script against a newer export to pick up subsequent versions.
Back to top

Reuse

ENISA re-use notice