FPGA Configuration Tamper Detection Using Dirty Bit Counters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to effectively secure programmable logic devices against tampering, particularly during the configuration stage where encryption keys can be deciphered by analyzing responses to false configuration data.

Innovation Solution

Employing a dirty bit and sticky error counter to detect multiple unsuccessful configuration attempts, triggering anti-tampering measures such as clearing encryption keys or disabling the device to prevent unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If encryption algorithms are implemented to secure configuration data, then security against unauthorized access is improved, but vulnerability to deciphering attacks through false configuration data analysis remains

Engineering Contradiction:
ImprovesecurityVSAvoiddeciphering attack
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by implementing a dirty bit mechanism that is set before configuration attempts and checked beforehand to detect potential attacks. The control block determines the status of the dirty bit before beginning a given configuration attempt, and if set, initiates anti-tampering operations preemptively to prevent deciphering attacks before they can succeed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies preliminary anti-action by implementing countermeasures that activate before the device enters user-mode where many security algorithms are implemented. The control block initiates anti-tampering operations when the dirty bit is determined to be set before beginning the configuration attempt, providing security protection during the vulnerable configuration stage rather than after the fact.

Inventive Principle:
Principle #9Preliminary anti-action

2Ease of operation

If multiple unsuccessful configuration attempts are allowed, then device functionality and ease of operation are maintained, but security against tampering attacks deteriorates

Engineering Contradiction:
Improveconfiguration attemptsVSAvoidtampering security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies feedback by implementing a control block that continuously monitors configuration attempts and checks the dirty bit status before each attempt. The system provides feedback through alarm generation and anti-tampering operations when suspicious activity is detected, creating a closed-loop security mechanism that responds to attempted configurations in real-time.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies parameter changes by modifying the behavior of the configuration system based on the dirty bit state. When the dirty bit is set, the system changes from allowing normal configuration attempts to initiating anti-tampering operations, effectively changing the operational parameters of the device based on detected security conditions.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11436382B2Systems and methods for detecting and mitigating programmable logic device tampering
Publication Date: 2022.09.06 ALTERA CORP
  • US11436382B2 patent drawing
  • US11436382B2 patent drawing
  • US11436382B2 patent drawing

AI summary

Systems and methods are disclosed for preventing tampering of a programmable integrated circuit device. Generally, programmable devices, such as FPGAs, have two stages of operation; a configuration stage and a user mode stage. To prevent tampering and/or reverse engineering of a programmable device, various anti-tampering techniques may be employed during either stage of operation to disable the device and/or erase sensitive information stored on the device once tampering is suspected. One type of tampering involves bombarding the device with a number of false configuration attempts in order to decipher encrypted data. By utilizing a dirty bit and a sticky error counter, the device can keep track of the number of failed configuration attempts that have occurred and initiate anti-tampering operations when tampering is suspected while the device is still in the configuration stage of operation.