Record Security Architecture Preventing Hijacking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computing systems face issues with record hijacking, where non-owner users can inadvertently or intentionally modify or cancel event records by asserting unauthorized ownership privileges, leading to security breaches and data loss.
Innovation Solution
A computing system record security architecture that includes a record generation component, a co-owner assignment component, and a record security component, which utilize unique identifiers and email replication to ensure that only the legitimate owner can modify records, and allows for co-owner assignments with specific privileges, preventing unauthorized modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If record modification requests are allowed from any user claiming ownership, then ease of operation is improved, but security is worsened leading to record hijacking
Solution Approach 1:
The patent introduces an intermediary verification mechanism that mediates between record modification requests and actual record changes. The system validates the owner property against the requester's identity before allowing modifications, preventing unauthorized users from hijacking records while still allowing legitimate owners easy access to modify their records.
2Ease of operation
If co-owner privileges are granted to multiple users, then ease of operation is improved for collaborative management, but security is worsened due to potential unauthorized modifications
Solution Approach 1:
The patent applies local quality by granting different levels of access privileges to different users based on their specific roles. Co-owners receive limited modification rights for specific aspects of record management, while the primary owner retains full control. This allows collaborative management where co-owners can perform routine operations without risking unauthorized critical changes.
3Reliability
If strict owner validation is implemented, then security is improved, but device complexity is worsened due to additional validation mechanisms
Solution Approach 1:
The patent uses copying by maintaining an owner property copy within the record structure that can be quickly validated against the requester's identity. This validation copy allows for efficient verification without requiring complex real-time checks, reducing system complexity while maintaining strong security validation.
Data Source
AI summary
A computing system record security architecture comprises, in one example, a record generation component configured to generate a record in a computing system, the record identifying a set of users associated with the record, and having an owner property that identifies a first user as an owner of the record, a co-owner assignment component configured to receive a co-owner assignment request, from the first user, to assign a second user to the record as a co-owner, and a record security component configured to receive a record modification request, from the second user, that requests a modification to the record, and to propagate the record modification request to the set of users with a unique identifier that identifies the first user.