Cloud Security Framework Using Cryptographic Puzzles and Key Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional security systems are inadequate in the cloud computing paradigm, as they rely on assumptions about resource ownership and control, which are broken in cloud environments, leading to vulnerabilities in both front-end and back-end security, particularly with regards to data breaches and DDoS attacks.

Innovation Solution

A computer application security framework that provides front-end security through multi-factor authentication and DDoS mitigation using cryptographic puzzles, and back-end security through a virtual private data-store created within an insecure environment using existing object-relational mapping (ORM) layers or database drivers, ensuring data encryption, integrity, and key management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional back-end security systems are used in cloud computing, then resource ownership assumptions are maintained, but security is undermined because 3rd party administrators can access sensitive data

Engineering Contradiction:
Improveback-end securityVSAvoiddata breach risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the encryption keys from the database server environment and stores them in the application server's memory space. This separation ensures that even though the database server is administered by a 3rd party, the sensitive data remains protected because the keys necessary to decrypt it are not accessible to the database administrator or any other 3rd party personnel.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system segments the security functions by separating data storage (in the database server) from key management (in the application server). This segmentation allows the database server to be managed by cloud providers while the application server maintains control over cryptographic keys, creating a security boundary that prevents 3rd party access to encrypted data.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If traditional front-end authentication systems are used, then implementation simplicity is maintained, but security is weakened because passwords are vulnerable to guessing attacks

Engineering Contradiction:
Improveauthentication implementationVSAvoidfront-end security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent transforms the authentication mechanism by changing the parameter from simple password verification to cryptographic puzzle solving. Instead of relying on password strength, the system requires clients to demonstrate computational work by solving cryptographic puzzles, making authentication resistant to guessing attacks while maintaining ease of implementation through standardized cryptographic protocols.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If basic password authentication is used, then user experience simplicity is maintained, but security is insufficient against modern attack vectors

Engineering Contradiction:
Improveuser authenticationVSAvoidauthentication vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces cryptographic puzzles as an intermediary mechanism between the user and the authentication system. Instead of directly verifying passwords, the system requires users to solve cryptographic puzzles that serve as a mediator, proving legitimate access intent while blocking automated guessing attacks and credential stuffing attempts.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If cloud computing resources are rented rather than owned, then resource flexibility is improved, but security assumptions are broken leading to vulnerabilities

Engineering Contradiction:
Improveresource flexibilityVSAvoidsecurity model
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent adds a new dimension to security by implementing cryptographic boundaries that operate independently of resource ownership models. By using encryption and key management in the application server layer, the system creates a security dimension that transcends the cloud computing rental/ownership relationship, allowing flexible resource usage while maintaining strong security guarantees.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS20220309176A1Systems and methods for front-end and back-end data security protocols
Publication Date: 2022.09.29 CRYPTERON INC
  • US20220309176A1 patent drawing
  • US20220309176A1 patent drawing
  • US20220309176A1 patent drawing

AI summary

A security framework and methodology is provided which provides front-end security through authentication and authorization, and back-end security through a virtual private data-store created within an insecure environment using existing object-relational mapping (ORM) layers or database drivers. The front-end security utilizes numerous multi-factor authentication metrics and a distributed denial of service (DDoS) cryptographic boundary to proactively attack malicious users using a cryptographic puzzle, and the back-end security provides data encryption and decryption, data privacy, data integrity, key management, pattern monitoring, audit trails and security alerts while simultaneously hiding the complexity behind an identical or similar ORM or database drive application programming interface (API).