Fundamental to UXP Object Creation
The UXP Identity contains and protects the empowering components that permit the UXP Object to be intelligent and proactive. The UXP Identity continues securing the UXP Object, once authenticated, while the data is in-use.
The UXP Identity is necessary for generating a UXP Object. In a protected format, the Identity houses the owner specified access and mitigation policies and a list of permitted users for a dataset. These policies and the user list (together, referred to as artifacts) are required to create the unique protection scheme within the UXP Object. Before a UXP Object can be generated, a UXP Identity must be present at the time and place when a dataset is protected. It provides essential artifacts that are incorporated into the process for constructing the protection scheme for the UXP Object.
Once created as file, the UXP Identity Object appears as an inert, binary file showing an*.iic extension. This file type is unidentifiable unless proximal to UXP Technology libraries. It looks ordinary and nondescript on any O/S and can be easily designated as junk.
The primary differences between a UXP Identity and a UXP Object are that the Identity is uneditable and contains no customer data. Additionally, the UXP Identity contains two types of artifacts, public and private. Both types are defined and controlled by the process or person who creates the UXP Identity.
The following components are universal in the UXP Identity:
- Permitted users
- UXP Intelligence
- File system
- Header file