Fischer et al., 2020 - Google Patents
Hardware penetration testing knocks your SoCs offFischer et al., 2020
View PDF- Document ID
- 16245646982075128649
- Author
- Fischer M
- Langer F
- Mono J
- Nasenberg C
- Albartus N
- Publication year
- Publication venue
- IEEE Design & Test
External Links
Snippet
Hardware Penetration Testing Knocks Your SoCs Off Page 1 14 2168-2356/20©2020 IEEE
Copublished by the IEEE CEDA, IEEE CASS, IEEE SSCS, and TTTC IEEE Design&Test
Hack@DAC Editor’s notes: This article highlights how software simulations can, on the one …
- 230000035515 penetration 0 title description 4
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/28—Testing of electronic circuits, e.g. by signal tracer
- G01R31/317—Testing of digital circuits
- G01R31/3181—Functional testing
- G01R31/3183—Generation of test inputs, e.g. test vectors, patterns or sequence
- G01R31/318385—Random or pseudo-random test pattern
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/28—Testing of electronic circuits, e.g. by signal tracer
- G01R31/317—Testing of digital circuits
- G01R31/3181—Functional testing
- G01R31/3185—Reconfiguring for testing, e.g. LSSD, partitioning
- G01R31/318533—Reconfiguring for testing, e.g. LSSD, partitioning using scanning techniques, e.g. LSSD, Boundary Scan, JTAG
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/577—Assessing vulnerabilities and evaluating computer system security
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3648—Software debugging using additional hardware
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/26—Functional testing
- G06F11/263—Generation of test inputs, e.g. test vectors, patterns or sequences; with adaptation of the tested hardware for testability with external testers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/2236—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test CPU or processors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material
- G06F21/12—Protecting executable software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
- G06F17/50—Computer-aided design
- G06F17/5009—Computer-aided design using simulation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F2207/00—Indexing scheme relating to methods or arrangements for processing data by operating upon the order or content of the data handled
- G06F2207/72—Indexing scheme relating to groups G06F7/72 - G06F7/729
- G06F2207/7219—Countermeasures against side channel or fault attacks
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Farzana et al. | Soc security verification using property checking | |
| Farahmandi et al. | System-on-chip security | |
| Cruz et al. | Hardware Trojan detection using ATPG and model checking | |
| Contreras et al. | Security vulnerability analysis of design-for-test exploits for asset protection in SoCs | |
| Arribas et al. | Cryptographic fault diagnosis using VerFI | |
| Guo et al. | Pre-silicon security verification and validation: A formal perspective | |
| Kitsos et al. | Exciting FPGA cryptographic Trojans using combinatorial testing | |
| Azar et al. | Fuzz, penetration, and ai testing for soc security verification: Challenges and solutions | |
| Karmakar et al. | Efficient key-gate placement and dynamic scan obfuscation towards robust logic encryption | |
| Hossain et al. | Socfuzzer: Soc vulnerability detection using cost function enabled fuzz testing | |
| Hoffmann et al. | ARMORY: fully automated and exhaustive fault simulation on ARM-M binaries | |
| Werner et al. | An end-to-end approach for multi-fault attack vulnerability assessment | |
| Fischer et al. | Hardware penetration testing knocks your SoCs off | |
| Kitsos et al. | Towards a hardware Trojan detection methodology | |
| Farzana et al. | SoC Security Properties and Rules. | |
| Kampel et al. | Locating hardware trojans using combinatorial testing for cryptographic circuits | |
| Plusquellic et al. | Information leakage analysis using a co-design-based fault injection technique on a RISC-V microprocessor | |
| Jayasena et al. | Scalable detection of hardware trojans using atpg-based activation of rare events | |
| Nahiyan et al. | Code coverage analysis for IP trust verification | |
| Vijayan et al. | Runtime identification of hardware Trojans by feature analysis on gate-level unstructured data and anomaly detection | |
| Farahmandi et al. | CAD for hardware security | |
| Vali et al. | Bit-flip detection-driven selection of trace signals | |
| Farahmandi et al. | Formal approaches to hardware trust verification | |
| Portillo et al. | Building trust in 3PIP using asset-based security property verification | |
| Walters et al. | Sleak: A side-channel leakage evaluator and analysis kit |