Information security, cybersecurity and privacy protection — Physically unclonable functions — Part 1: Security requirements
Introduction: This document specifies the security requirements for physically unclonable functions (PUFs) for generating non-stored cryptographic parameters. Cryptographic modules generate the certain class of critical security parameters such as a secret key using a random bit generator within the modules. Such modules can store generated security parameters in embedded non-volatile memory elements. For higher security, a combination of tamper response and zeroization techniques may be used for protecting stored security parameters from active unauthorized attempts of accessing such parameters. However, as the reverse-engineering technology advances, the risk of theft of such stored security parameters has become higher than ever. The rapidly pervading technology called a PUF is promising to mitigate the above-mentioned risks by enabling security parameter management without storing such parameters. PUFs are hardware- based functions providing steadiness and randomness of their outputs and physical and mathematical unclonability of the functions themselves, taking advantage of intrinsic subtle variations in the device’s physical properties, which are also considered object’s fingerprints. PUFs can be used for security parameter generation (e.g. key, initialization vector, nonce and seed), entity authentication or device identification in cryptographic modules. Now, security requirements of PUFs should be considered at system level, meaning that they should consider many possible attack p
Scope: This document specifies the security requirements for physically unclonable functions (PUFs). Specified security requirements concern the output properties, tamper-resistance and unclonability of a single and a batch of PUFs. Since it depends on the application which security requirements a PUF needs to meet, this documents also describes the typical use cases of a PUF. Amongst PUF use cases, random number generation is out of scope in this document.