Skip to contentArticle 14 reporting has applied since 11 September 2026. See the worked example and get the free 4-page overview.
See the kit
Özer Koray Akdemir

About the author

Özer Koray Akdemir

Product cybersecurity architect

LinkedIn profile →

Özer Koray Akdemir turns cybersecurity regulation into engineering work on connected products, and into the evidence that assessors ask for. He first did this when the regulation was still new and its interpretation was forming. The deadline was fixed, and the work ended in an approval audit.

What he brings to the CRA

What the CRA asks forWhere the experience comes from
Risk-based security by design (Art. 13, Annex I)Threat analysis and risk assessment (TARA) for connected products, from concept to production
Vulnerability handling and security updates (Annex I Part II)Architecture for signed software updates delivered over the air, with code signing, key management and PKI
Reporting (Art. 14)Vulnerability and incident handling set up in an organisation, with named roles
Due diligence on components (Art. 13(5))Cybersecurity requirements for suppliers and checks of what they deliver
Technical documentation and conformity (Art. 31, Annex VII)Evidence prepared for approval audits and presented to assessors

Before product cybersecurity, he spent many years on cryptographic systems, secure communications and telecom infrastructure. That background shows in the kit, which treats security as a property of the whole system and of the organisation behind it.

Why the kit exists

Some sectors already have cybersecurity rules for products, for example vehicles (UNECE R155) and radio equipment (Delegated Regulation (EU) 2022/30). The CRA brings comparable obligations to products with digital elements sold in the EU: a risk-based process, security designed in, vulnerability handling, incident reporting and documentation that an authority can check. The kit is the structure he would give a team on its first day: the documents in the order they are needed, each linked to the provisions it supports.

Principles

  • Every template maps to provisions of the regulation.
  • Standards are cited by number only; no standard text is reproduced.
  • The kit helps you organise the work. It does not certify a product or confirm that it conforms.

Education and frameworks

  • M.Sc. in Electronics and Multimedia Signal Processing, Tampere University of Technology.
  • B.Sc. in Electrical and Electronics Engineering, Bilkent University.
  • Works with IEC 62443, ISO/SAE 21434, ISO 27001, UNECE R155 and R156, NIS2 and the CRA.