Provider Object Replacement for Compromised PNR Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing security measures for passenger name records (PNRs) are inadequate, particularly for online access, leading to increased data leaks and compromise, and traditional security methods like multifactor authentication are impractical due to user experience concerns.
Innovation Solution
A method involving data extraction from compromised provider objects, creation of a clean provider object using an injection query with a cross-reference element, and deactivation of the compromised object, while notifying third-party systems of the new identifier.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional security methods like multifactor authentication are implemented for PNR access, then security level is improved, but user experience deteriorates
Solution Approach 1:
The system creates a duplicate PNR record when the original is compromised. This copy serves as a secure replacement that maintains data integrity while allowing continued access without requiring complex authentication changes. The duplicate PNR mechanism resolves the contradiction by providing security through data redundancy rather than through cumbersome access controls.
Solution Approach 2:
The system introduces an intermediary mechanism (the duplicate PNR creation process) between the compromised PNR and the user access. This intermediary automatically handles the security issue by creating a clean replacement record, thereby maintaining both security and ease of operation without requiring direct user involvement in security protocols.
2Reliability
If online access to PNR is secured with higher security measures, then data protection is improved, but accessibility deteriorates
Solution Approach 1:
When online PNR access is compromised, the system creates a duplicate PNR record that serves as a protected replacement. This copying approach maintains data protection by isolating the compromise to a single record while preserving accessibility through the new clean record, avoiding the need to restrict online access for all users.
Solution Approach 2:
The system extracts the compromised data element (the compromised PNR record) from the system by creating a separate duplicate. This extraction isolates the security issue to a specific record rather than requiring system-wide security restrictions, thereby maintaining both data protection and accessibility.
3Adaptability or versatility
If PNR data is shared with multiple stakeholders, then service quality is improved, but security risk increases
Solution Approach 1:
When a PNR shared with multiple stakeholders is compromised, the system creates a duplicate record that can be distributed to all stakeholders. This copying approach maintains service quality by ensuring all parties have access to a valid PNR while concentrating the security risk to a single record that can be independently managed and replaced.
Solution Approach 2:
The system segments the PNR data into a compromised original record and a clean duplicate record. This segmentation allows the compromised record to be isolated and deactivated while the duplicate can be safely shared with stakeholders, thereby maintaining service quality while managing security risk through record separation.
Data Source
AI summary
A method for database synchronization in response to a unique provider object being compromised is described. The method comprises extracting data from a compromised provider object; building an injection query using the extracted data; adding a cross-reference element to the injection query, the cross-reference element including a provider object identifier for the compromised provider object; initiating creation of a clean provider object using the extracted data and the cross-reference element; forcing creation of the clean provider object; notifying third party systems of a provider object identifier for the created clean provider object; and deactivating the compromised provider object. An intermediation server configured to implement the method is also disclosed.