Segmented Order Management Data Encryption via SPAR
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Order Management Systems (OMS) face challenges in providing comprehensive security for payment card industry data security standards (PCI DSS) compliance, particularly in protecting data at rest from remote attacks and ensuring secure data encryption and decryption processes.
Innovation Solution
The implementation of a Secure PCI at Rest (SPAR) device with multiple interfaces for segmented processing, utilizing Format Preserving Encryption (FPE) and data segmentation, along with encryption and decryption modules, to securely handle and process payment and personal information, ensuring compliance with PCI DSS requirements without storing client data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data is stored in unencrypted format for easy processing, then processing speed and ease of operation improve, but security and protection against remote attacks deteriorate
Solution Approach 1:
The system segments data into encrypted and unencrypted portions, with only necessary data elements decrypted at each processing stage. The encryption module divides payment information into encrypted segments that are selectively decrypted by specific modules (authorization module, capture module, refund module) based on their specific processing needs, rather than decrypting all data at once.
Solution Approach 2:
The encryption module acts as an intermediary between data storage and processing modules. It maintains encrypted data in storage and selectively decrypts only the specific data elements needed by each processing module (authorization, capture, refund) without exposing the entire data set, thus mediating between security requirements and processing needs.
2Reliability
If comprehensive data encryption is implemented for security, then security and protection improve, but processing complexity and device complexity increase
Solution Approach 1:
Different levels of encryption and decryption are applied to different data elements based on their specific security requirements and processing needs. Payment card information, customer names, and billing addresses receive different encryption treatments appropriate to their sensitivity and usage requirements, rather than applying uniform encryption to all data.
Solution Approach 2:
The system changes encryption parameters dynamically based on the processing stage and data type. Full encryption is used for storage, while selective decryption with specific key parameters is applied during processing based on the module's authorization level and data requirements, optimizing both security and processing efficiency.
3Productivity
If all data is decrypted for processing, then ease of processing improves, but data exposure risk and security vulnerabilities increase
Solution Approach 1:
Data is pre-encrypted in storage with structured formatting that allows selective decryption. The encryption module prepares data in advance with appropriate encryption keys and formats, so that when processing is needed, only the specific required elements need to be decrypted rather than the entire data set, improving both security and processing efficiency.
Solution Approach 2:
The system skips the decryption step for data elements that do not need to be processed at a given stage. Each processing module (authorization, capture, refund) only requests decryption of the specific data elements it needs, rapidly processing only necessary portions while leaving other sensitive data encrypted and untouched.
4Adaptability or versatility
If multiple interfaces are used for different processing functions, then versatility and adaptability improve, but security vulnerabilities and attack surfaces increase
Solution Approach 1:
The encryption module serves as a security intermediary for all interfaces (front-end, middle-tier, back-end). Each interface communicates through the encryption module which enforces authentication, authorization, and data encryption/decryption policies, mediating between the diverse interface requirements and security requirements without requiring separate security implementations for each interface.
Data Source
AI summary
An apparatus for segmented processing of order management system data is described herein. The apparatus generally includes: a front end interface that is operative to receive unencrypted payment information and unencrypted personal information relating to at least one customer order and return encrypted payment information and encrypted personal information relating to the at least one customer order; a middle tier interface that is operative to receive encrypted payment information and encrypted personal information relating to at least one customer order and return decrypted personal information only; and/or a back end interface that is operative to receive encrypted payment information and encrypted personal information relating to at least one customer order and return decrypted payment information and decrypted personal information relating to the at least one customer order.