Private Namespace Object Isolation for Malware Collision Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer systems face issues with 'collisions' on named objects, which can lead to denial of service problems and unauthorized data access, as malware can preemptively create named objects, causing conflicts with legitimate programs and potentially exposing sensitive information.
Innovation Solution
A method is introduced to create a private namespace with security attributes validation, ensuring that only authorized processes can create and access objects, thereby preventing collisions and malicious activities by using a create namespace routine that generates a container object if the security attributes match, and an open namespace routine that validates access permissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If antivirus software scans incoming data to detect malware, then detection capability is improved, but system performance deteriorates due to increased scanning overhead
Solution Approach 1:
The system performs preliminary actions by validating security attributes and creating private namespaces before malware can execute malicious code. The create namespace routine validates security attributes in advance, preventing malware from creating objects with legitimate names before the legitimate program does.
Solution Approach 2:
The patent introduces an intermediary mechanism - the private namespace with security attribute validation - that sits between the malware detection layer and the actual object creation. This intermediary prevents collisions by validating security attributes before object creation, reducing the need for extensive scanning.
2Adaptability or versatility
If the operating system allows multiple users to create named objects, then system flexibility is improved, but collision risks increase leading to denial of service
Solution Approach 1:
The patent segments the object creation process into two distinct phases: first, validation of security attributes and creation of a private namespace; second, actual object creation within that namespace. This segmentation prevents collisions between different users' objects while maintaining multi-user flexibility.
Solution Approach 2:
Each user or process receives a private namespace with unique security attributes, creating a local quality distinction. Within each private namespace, objects can be created without conflict, while the namespaces themselves are differentiated by their security attributes, preventing cross-user collisions.
3Object-generated harmful factors
If malware creates named objects preemptively, then malicious functionality is achieved, but legitimate program functionality is denied
Solution Approach 1:
The create namespace routine performs preliminary anti-action by validating security attributes before object creation. If a process attempts to create an object with a name that conflicts with a legitimate program's expected object, the security attribute validation fails, preventing the malware from succeeding while allowing legitimate programs to execute normally.
Data Source
AI summary
Generally described, a method, software system, and computer-readable medium are provided for preventing a malware from colliding on a named object. In accordance with one aspect, a method is provided for creating a private namespace. More specifically, the method includes receiving a request to create a private namespace that contains data for defining the boundary of the private namespace from the current process. Then a determination is made regarding whether a principle associated with the current process has the security attributes that are alleged in the request. In this regard, if the principle that is associated with the current process has the security attributes that are alleged in the request, the method creates a container object to implement the private namespace that is defined by the data received in the request.