https://www.patsnap.com/resources/blog/rd-blog/fault-injection-and-countermeasures-patent-landscape/ · Patsnap · data cut-off 2026-07-31 · downloaded from the live page
Patent Landscape · Secure Chips & Payments
Fault injection and countermeasure patents: mapping who holds the glitch-detection claims
  • 41.8% concentration at the top. The top 5 of 59 ranked assignees hold 102 of 244 records in scope — filing is concentrated, but a long tail of single- and few-filing entrants remains.
  • Filing peaked in 2022 at 42 records, then eased to 21 by 2024 (-30% from 2021's 30) — read this as claim space filling up, not the field cooling, since 2025-26 data is still incomplete.
  • G06F digital-processing claims dominate at 55.7%, while G07F vending/payment-terminal claims sit at just 4.1% of the 244 records — a narrow foothold for a category this attack model was originally built to protect.
Get a prior-art report on your approach
244
Published Records
42%
Top-5 Share of All Records
-30%
Filing Growth 2021→2024
US
Leading Jurisdiction

Filing growth compares 2021 (30 records) with 2024 (21) — a three-year span. 2024 is the most recent year we treat as complete: publication lags filing by roughly 18 months, so 2025 onwards are still filling in and any growth rate that ends there would understate the field. Top-5 share is the combined record count of the five largest assignees divided by all 244 records in scope (CR5), not by the ranked leaders only.

Published byPatsnap Research··7 min readSourced from Patsnap Eureka
Overview

What this landscape covers

Fault injection covers a family of physical attacks — voltage glitching, clock glitching, laser fault injection and electromagnetic pulse injection — used to force a chip into an unintended state and bypass its security checks. The countermeasure side of the same search captures redundant computation, control-flow integrity checks and photodiode sensing, the detection and recovery mechanisms vendors build in response. This dataset spans 244 published records from 2015 through the 2026-07-31 cut-off, drawn from a search string that requires both an attack term and a countermeasure or detection term in the same record.

Because publication lags filing by roughly 18 months, the 2025 and 2026 figures in any trend line are undercounts by construction; 2024 is the most recent year that can be read as complete. The dataset draws primarily on secure-element and smart-card vendors, general semiconductor makers and a smaller set of payment-terminal and cloud-hardware filers, which shows up clearly in the IPC composition below.

Filing activity and technology composition, 2015–2026
  1. 1NXP BV29
  2. 2NUVOTON28
  3. 3SECURE IC22
  4. 4NDS12
  5. 5THALES DIS FRANCE SA11
  6. 6NORDIC SEMICONDUCTOR10
  7. 7INTEL CORP9
  8. 8GOOGLE LLC8
  9. 9WINBOND ELECTRONICS CORP8
  10. 10SAMSUNG ELECTRONICS CO LTD8
Source: Patsnap Eureka. Assignee ranking and totals. Derived from a Patsnap search on Fault Injection and Countermeasures covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP

Let an AI agent run this analysis on your own technology

Pick a task. Every answer cites the patents behind it.

10,000 free credits to start
The Data

Filing trend and technology composition

Two views of the same 244 records: filing activity by year, and the IPC subclasses those records carry. Because a single record can carry several IPC classes, the class shares below sum to well over 100% of the record total — that is expected and is not a sign of double-counting.

Filing rose to a 2022 peak, then eased

Annual filings climbed from 17 in 2017 to a peak of 42 in 2022, then declined to 21 by 2024 — a -30% move from 2021's 30 filings over that three-year span. Treat 2025 and 2026 as still filling in rather than as evidence of a further slowdown.

Filing rose to a 2022 peak, then eased013253850172017201820192020202142202220232024202522026Most recent year is partial — publication lag means later filings are not yet visible.

G06F and H04L carry the bulk of the claims

G06F (electric digital data processing) appears in 55.7% of the 244 records and H04L (digital information transmission) in 28.3%, with G01R (electric and magnetic measurement) at 20.9% covering the physical glitch-detection circuitry itself. G07F (coin-freed and vending apparatus), the payment-terminal-specific class, sits at only 4.1% — a thin slice relative to how often fault injection is discussed as a payment-security threat.

G06F and H04L carry the bulk of the claimsG06F · Electric digital data processi…13655.7%H04L · Digital information transmissi…6928.3%G01R · Electric & magnetic measurement5120.9%H03K · Pulse technique & logic circui…3916.0%G06K · Data recognition & presentation3413.9%G11C · Static & digital memories229.0%H01L · Semiconductor devices145.7%G07F · Coin-freed & vending apparatus104.1%Other4719.3%

Shares are the percentage of the 244 records in scope. A patent can carry several IPC classes, so the shares add up to more than 100%.

Source: Patsnap Eureka. Filing trend and technology composition. Derived from a Patsnap search on Fault Injection and Countermeasures covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.

Go deeper on Fault Injection and Countermeasures with Eureka

This page is one run against one query. Ask Eureka your own question about fault injection and countermeasures and every answer comes back with the patent numbers behind it.

Try Eureka
Key Patents

Representative and most-cited filings

Representative recent filing
US20240005045A12024-01-04

System on chip with voltage glitch detection based on clock synchronization monitoring (US20240005045A1, Thales DIS France, filed 2024-01-04)

THALES DIS FRANCE SAS

The system on chip carries a memory controller with clock synchronization circuitry built on a locked loop, paired with a voltage glitch attack detector that monitors the clock synchronization signal and checks whether it is nominal or characteristic of a voltage glitch attack. The detector can be implemented as software running on the processing unit rather than dedicated analog hardware.Other embodiments are disclosed beyond the monitoring circuit described here.

US20240005045A1 — patent drawing 1US20240005045A1 — patent drawing 2
View full record
Most-cited records in this landscape
#Publication no.Patent titleCitations
1US20030226082A1Voltage-glitch detection device and method for securing integrated circuit device from voltage glitch attack81
2US20080061843A1Detecting voltage glitches42
3US6880752B2System for testing, verifying legitimacy of smart card in-situ and for storing data therein38
4US20150346246A1Method and Apparatus for Supply Voltage Glitch Detection in a Monolithic Integrated Circuit Device37
5US20210004461A1Quantitative digital sensor31
6US20170228562A1Circuit protection system and method29
7US10474846B1Processor power supply glitch detection25
8US20190005269A1Automatic Reset Filter Deactivation During Critical Security Processes24
9US20170141911A1Split-and-merge approach to protect against DFA attacks23
10US7085979B2Voltage-glitch detection device and method for securing integrated circuit device from voltage glitch attack23

Citation counts reflect influence within the searched corpus and favour older filings; they are not a measure of current commercial importance.

Each row carries its publication number; clicking a row searches Eureka by that number.

Source: Patsnap Eureka. Citation counts and representative records. Derived from a Patsnap search on Fault Injection and Countermeasures covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
Run it yourself

Put your own technology through the same analysis


  
Where to run it
Fastest

Eureka on the web

When you want the answer in the next five minutes.

The agent works the prompt against patents and technical literature, citing every source.

Run your analysis now →
For builders

MCP server & REST API

When it has to run inside your own pipeline.

Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.

Browse MCP servers →
Insights

What the numbers mean for a filing decision

Three patterns worth acting on before drafting claims in this space.

Concentration
41.8% of 244
held by top 5 of 59 ranked assignees

The leader board is short, the tail is long

One assignee leads at 29 records, with fifth place at 11 and tenth at 8 — a steep drop-off after the top few. The other 49 ranked assignees split the remainder in small counts, which means most of the field's claim space is still held in narrow, single-vendor slices rather than blocked by a handful of broad players.

Top 10 combined reach 59.4% of all 244 records.
Filing momentum
-30%, 2021→2024
peak year 2022 at 42 filings

Activity is past its peak, not abandoned

Filings rose from 17 in 2017 to 42 in 2022, then fell to 21 by 2024. That decline reads as core detection mechanisms (voltage and clock glitch sensing) becoming well-claimed rather than the underlying attack surface losing relevance — new work is more likely to sit in adjacent, less-crowded branches.

2025-26 counts are understated by publication lag and should not be read as a further drop.
Class distribution
4.1% G07F vs 55.7% G06F
share of 244 records

Payment-terminal claims are thin

G06F (digital processing) and H04L (transmission) dominate the corpus, while G07F (coin-freed/vending apparatus, the class covering payment terminals) sits at just 10 of 244 records. For a threat model frequently discussed in point-of-sale and smart-card contexts, terminal-specific claim language is comparatively open.

G01R (measurement circuitry) at 20.9% shows where sensor-level claims concentrate instead.
Eureka AI Agent
Looking for what nobody has claimed yet?

Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to fault injection and countermeasures, with the prior art for and against each one.

Find the white space →
Source: Patsnap Eureka. Co-assignee relationships and derived observations. Derived from a Patsnap search on Fault Injection and Countermeasures covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
Players

Who is filing, and where momentum has cooled

Filing is led by secure-element and smart-card vendors alongside general semiconductor makers, with several previously active filers showing no filings in the latest tracked year.

Leader
29 records
top-ranked assignee

A clear leader, but not a lock on the field

The top-ranked assignee holds 29 of the 244 records in scope, well ahead of fifth place at 11 — but that still leaves 215 records spread across 58 other assignees, most in single digits.

Concentration sits at the top without shutting out smaller filers.
Momentum
0 in latest year
for several previously active filers

Recent-year activity has gone quiet for named incumbents

Several assignees that were active earlier in the window, including NXP, Nuvoton, Nordic Semiconductor and Thales DIS France, show zero filings in the latest tracked year. This is consistent with the broader 2021-2024 decline and with publication lag, not necessarily with those firms exiting the space.

Read alongside the -30% three-year filing trend, not as a standalone signal.
Collaboration
6 co-assignee pairs
across the dataset

Co-filing is rare and mostly inventor-linked

Only six co-assignee pairs appear in the dataset, the strongest tied to a single company's named inventors rather than cross-company joint filings. This is a field of largely independent filers rather than one built on formal patent-pooling or joint-development arrangements.

No dominant cross-assignee cluster emerges from the pairs available.
🔍
Under-claimed technical branches
Sub-areas with comparatively thin filing density relative to the core voltage/clock glitch detection claims
Payment-terminal-specific glitch detection (G07F)Photodiode-based laser fault injection sensingControl-flow integrity for embedded firmwareRedundant computation for post-quantum crypto coresEM pulse injection detection in memory arrays
Rank all filers by momentum →
Recent-year filing momentum by assignee
AssigneeRecent yearYoY
NXP B.V.0-100%
Nuvoton Technology Corporation0-100%
Secure IC0-100%
NDS Limited0—
Thales DIS France SA0—
Nordic Semiconductor0—
Google LLC0—
Intel Corporation0—
Source: Patsnap Eureka. Assignee-level momentum. Derived from a Patsnap search on Fault Injection and Countermeasures covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
What's Next

Where to take this next

The landscape points to specific next steps depending on whether the goal is freedom-to-operate, portfolio-building or monitoring a competitor.

Check freedom-to-operate against the top 10

Before drafting claims around voltage or clock glitch detection, check them against the top 10 assignees, who together hold 59.4% of the 244 records in this landscape.

Run a freedom-to-operate check in Eureka →

Draft into the thinner branches

G07F payment-terminal claims and photodiode-based sensing sit well below the corpus average in filing density, which is where a first claim has more room to stand.

Explore white space with Eureka →

Track quiet incumbents for re-entry

Several previously active filers show zero filings in the latest tracked year; a renewed filing from any of them is worth flagging early given their earlier concentration in this space.

Set up assignee monitoring in Eureka →
Source: Patsnap Eureka. Forward-looking reading of the same dataset. Derived from a Patsnap search on Fault Injection and Countermeasures covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
FAQ

Common questions on fault injection patents

Answers are grounded in the same dataset. Derived from a Patsnap search on Fault Injection and Countermeasures covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP

Research Fault Injection and Countermeasures in depth with Eureka

Go past this page: query the whole fault injection and countermeasures corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.

Try Eureka

Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.

Patent data carries inherent limitations: recent filings (typically the most recent 18–24 months) are under-counted due to standard publication lag; counts may be reported at either a patent-family or a patent-record basis and are not always directly comparable; classification, applicant-name, and citation data may contain errors, duplicates, or omissions; and the underlying search query defines and constrains the scope shown. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.

Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, or validity search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. Any patent, commercial, or strategic decision should be verified independently and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.

Machine translation. Assignee and organisation names originally recorded in Chinese, Japanese or Korean have been rendered into English by an AI translation step so that the tables stay readable. These renderings are best-effort and may not match a company's registered English name; the original name is what the underlying patent record carries, and it is what any Eureka query launched from this page uses.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.