Fuse-Based Replay Protection for TPM PIN Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Trusted Platform Modules (TPMs) face challenges in effectively preventing personal identification number (PIN) retry attacks, particularly on large System on a Chip (SOC) dies without non-volatile memory, where attackers can reset the SOC to replay earlier states and enumerate PIN spaces.
Innovation Solution
The implementation of a TPM on a SOC that utilizes programmable fuses as a counter to record PIN attempt failures, with methods such as fuse-based replay protection with conservative, aggressive, and dynamic fuse usage to prevent PIN hammering attacks and detect replay attacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a TPM implements replay protection measures that keep track of incorrect PIN entries, then PIN hammering attacks are prevented, but the device requires non-volatile memory to persistently store the attempt count, which increases device complexity and cost
Solution Approach 1:
The patent extracts the replay protection functionality from requiring full non-volatile memory and implements it using only on-die RAM with fuse-based counters. The critical state (PIN attempt count) is stored in volatile memory during operation, eliminating the need for non-volatile memory while maintaining security against replay attacks.
Solution Approach 2:
The patent changes the storage medium parameter from non-volatile memory to volatile memory with fuse-backed persistence. By using fuses to permanently record the number of PIN attempts and comparing this against the state in on-die RAM, the system achieves persistent replay protection without requiring non-volatile memory components.
2Reliability
If the TPM clears held keys when PIN attempt failures exceed a threshold, then brute force attacks are thwarted, but legitimate users may lose access to encrypted data
Solution Approach 1:
The patent implements dynamic fuse usage where the system adapts its security response based on the current state. Instead of a fixed threshold that permanently locks out users, the system dynamically blows fuses to increment the attempt count and clears keys only when the dynamic state indicates a genuine attack pattern, preserving user access for legitimate scenarios while blocking attacks.
Solution Approach 2:
The system uses feedback from the fuse counter state to dynamically adjust security responses. The TPM monitors the number of blown fuses representing PIN attempts and uses this feedback to determine whether to clear held keys or allow continued access, creating a responsive security mechanism that adapts to the actual threat level rather than using fixed thresholds.
3Reliability
If the TPM blows a fuse for each incorrect PIN attempt, then replay attacks are prevented, but the fuse count depletes quickly reducing the system's operational lifespan
Solution Approach 1:
The patent applies partial action by blowing fuses only when necessary for security rather than for every single PIN attempt. The system uses on-die RAM to track PIN attempts during sessions and only blows fuses when detecting replay attacks or exceeding dynamic thresholds, thereby extending fuse lifespan while maintaining adequate replay protection.
Solution Approach 2:
The system dynamically determines when to blow fuses based on the current operational context and detected threat patterns. By using volatile memory to track attempts and only permanently recording (blowing fuses) when security conditions warrant it, the system extends the operational lifespan of the fuse array while maintaining replay attack prevention.
4Reliability
If the TPM monitors fuse voltage to detect cut attacks, then fuse voltage cut attacks are detected, but the system complexity and power consumption increase
Solution Approach 1:
The patent implements self-service monitoring where the TPM uses its existing operational voltage lines to detect fuse voltage cuts without requiring separate dedicated monitoring circuits. The system leverages the natural voltage fluctuations during fuse blowing operations to detect unauthorized voltage cuts, eliminating the need for additional power-consuming monitoring hardware.
Solution Approach 2:
The voltage monitoring mechanism serves multiple functions: it provides fuse blow detection, detects voltage cut attacks, and verifies operational integrity all using the same voltage sensing infrastructure. This multi-functionality reduces overall system complexity and power consumption compared to dedicated monitoring systems.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A TPM with programmable fuses in an SOC includes an on-die RAM storing a blown-fuse count and a TPM state read from off-die NV memory. During initialization, if the blown-fuse count is greater than a TPM state fuse count, a TPM state PIN-attempt-failure count is incremented, thereby thwarting a replay attack. If a PIN satisfies a PIN failure policy, and if a TPM state previously-passed-PIN indicator is set to true, a fuse is blown and the blown-fuse count incremented depending on the PIN being incorrect, but if the TPM state previously-passed-PIN indicator is set to false, a fuse is blown and the blown-fuse count incremented independent of whether the PIN is correct or incorrect. The TPM state fuse count is set equal to the blown-fuse count. If a counter cleared before processing the PIN remains cleared during the next initialization, a fuse voltage cut is detected and a penalty imposed.