Debugging FIPS Cryptographic Modules via Segmented Security Levels

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The lack of debugging capabilities in FIPS-certified cryptographic modules at Security Level 2 and higher hinders product development and fault analysis, while enabling debugging in lower-level modules creates security risks.

Innovation Solution

Incorporating two FIPS-certified cryptographic modules within a single product, one compliant with SL1 enabling debugging and the other with SL2 disabling debugging, using different firmware images that allow switching between security levels upon boot-up, ensuring compliance with FIPS requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If debugging capabilities are enabled in FIPS-certified cryptographic modules, then ease of product development and fault analysis is improved, but security risks increase

Engineering Contradiction:

Improveproduct development and fault analysisVSAvoidsecurity risks

Core Design Contradiction:

Ease of manufactureVSObject-affected harmful factors

Solution Approach 1:

The cryptographic module is segmented into multiple operational modes or instances: a FIPS-compliant mode that disables debugging for security, and a non-FIPS mode that enables debugging for development and fault analysis. This segmentation allows each mode to have optimized characteristics without compromising the other.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Different debugging capabilities are applied to different parts or modes of the cryptographic module. The FIPS-compliant portion maintains strict security with debugging disabled, while a separate test or development portion enables debugging functionality. This local differentiation resolves the contradiction by providing debugging where needed while maintaining security where required.

Inventive Principle:

Principle #3Local quality

2Reliability

If debugging is disabled in FIPS SL2 and higher cryptographic modules, then security is maintained, but product development and fault analysis become difficult

Engineering Contradiction:

ImprovesecurityVSAvoidproduct development and fault analysis

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The system is divided into FIPS-compliant operational modes and non-FIPS test/development modes. The FIPS mode maintains security with debugging disabled, while the test mode enables debugging functionality. This segmentation allows security and development needs to coexist in different segments of the same cryptographic module.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

An intermediary mechanism or interface is provided that allows debugging access only under specific conditions (non-FIPS mode), acting as a mediator between security requirements and development needs. This intermediary ensures that debugging never compromises FIPS compliance while still enabling development activities.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If a single cryptographic module must comply with both FIPS SL1 (debugging enabled) and FIPS SL2 (debugging disabled), then versatility is improved, but device complexity increases

Engineering Contradiction:

Improvecompliance with different FIPS security levelsVSAvoidcryptographic module structure

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The cryptographic module employs dynamic configuration where debugging capabilities are enabled or disabled based on the operational mode. The module can dynamically switch between FIPS-compliant mode (debugging disabled) and non-FIPS mode (debugging enabled), allowing a single module to adapt to different security requirements without permanent structural complexity.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The debugging capability parameter is changed based on the operational mode. In FIPS-compliant mode, the debugging parameter is set to disabled; in non-FIPS mode, it is enabled. This parameter-based control allows a single cryptographic module to comply with different FIPS security levels without requiring physically separate modules, thereby reducing overall device complexity.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS20230393197A1Systems And Methods For Debugging Cryptographic Modules

Publication Date: 2023.12.07 ALTERA CORP

AI summary

An integrated circuit includes a first cryptographic module that enables debugging of the first cryptographic module and a second cryptographic module that disables debugging of the second cryptographic module. Each of the first and the second cryptographic modules has a logical cryptographic boundary that includes a first block. The logical cryptographic boundary of the first cryptographic module includes a second block that is not included within the logical cryptographic boundary of the second cryptographic module. The logical cryptographic boundary of the second cryptographic module includes a third block that is not included within the logical cryptographic boundary of the first cryptographic module.