US 8271802

To provide a concise summary of US Patent 8271802, I will extract information directly from the patent text and the Google Patents summary provided. I will also clarify the meaning of "independent claim" to explain them in plain language.

What is an Independent Claim?
In patent law, claims are the numbered paragraphs at the end of a patent that legally define the boundaries of the invention and the scope of protection it provides. There are two main types: independent claims and dependent claims. An independent claim stands alone and fully describes the invention without referring to any other claim. It usually includes a preamble, a transitional phrase, and a body listing all essential components or steps that define the invention. Independent claims are generally broader than dependent claims and are critical for defining what the patent covers. A patent can have multiple independent claims, each covering a different aspect of the invention (e.g., a system, a method of making, or a method of using).

Summary of US Patent 8271802

• Title: Secure data parser method and system
• Assignee: Security First Innovations LLC (current assignee)
• Inventors: Rick L. Orsini, Mark S. O'Hare, Roger S. Davenport, Steven Winick
• Filing Date: 2012-02-10
• Issue Date: 2012-09-18
• Abstract: The abstract describes a method and system for securing data from unauthorized access or use. The method involves parsing, splitting, and/or separating data into two or more portions, and optionally encrypting these portions. The split data, potentially encrypted, can be stored in one or multiple locations. The system reconstitutes the data for authorized access. The invention also includes a "trust engine" with server-centric keys and user authentication data, where cryptographic functions are performed on the server side without releasing private keys to users. The trust engine uses a data splitting process to create portions of cryptographic keys and authentication data, requiring predetermined portions from multiple locations for reconstruction, thereby enhancing security.

Plain-Language Overview of Independent Claims

US Patent 8271802 contains several independent claims covering different aspects of the invention, including methods and systems for secure data handling and cryptographic operations.

Claim 1: A method of securing data comprising:
This claim describes a process for making data secure. It involves:

1. Breaking up data: Taking the original data and dividing it into two or more smaller pieces or "portions."
2. Making it unreadable: Encrypting the original data (this can happen before or after it's broken up).
3. Storing the pieces: Storing these encrypted, broken-up pieces of data.
4. Putting it back together: Reconstructing the secure data into its original usable form when authorized.

Claim 12: A data parser system comprising:
This claim describes a system (a collection of components) designed to secure data. It includes:

1. A data splitting tool: This part breaks data into multiple pieces.
2. An encryption/decryption tool: This part handles making data unreadable (encrypting) and readable again (decrypting).
3. An assembly tool: This part puts the data pieces back together.
   The system also includes places to store these data pieces.

Claim 22: A cryptographic system comprising:
This claim focuses on a system for managing and performing cryptographic functions securely, particularly with user keys. It comprises:

1. A depository system: This stores private cryptographic keys and user enrollment data (data used to identify a user). Each user is linked to specific keys.
2. An authentication engine: This compares a user's current identification data with their stored enrollment data to confirm their identity.
3. A cryptographic engine: If the user is successfully identified, this engine performs cryptographic tasks (like encrypting/decrypting) using the associated private keys, without ever giving the private keys to the user.
4. A transaction engine: This component manages the flow of data between users and the other parts of the system (depository, authentication, cryptographic engines).

Claim 31: A method of facilitating cryptographic functions comprising:
This claim describes a process for enabling secure cryptographic operations for users. It involves:

1. Linking users to keys: Connecting a user to one or more private cryptographic keys that are stored in a secure location (like a secure server).
2. Verifying identity: Receiving identification data from the user and comparing it to their stored data to confirm who they are.
3. Performing crypto functions: Using the associated keys to carry out cryptographic tasks for the user, again, without ever giving the keys to the user.

Claim 40: An authentication system comprising:
This claim defines a system specifically for securely authenticating users. It includes:

1. Data storage facilities: One or more places that store portions of user enrollment data.
2. An authentication engine: This communicates with the storage facilities and includes:
   • A data splitting module: This tool breaks down the enrollment data into portions.
   • A data assembling module: This tool gathers the portions from storage and reconstructs the full enrollment data.
   • A data comparator module: This compares the user's current identification data with the reconstructed enrollment data to determine if the user is uniquely identified.

Claim 46: A cryptographic system comprising:
This claim describes a system focused on the secure handling of cryptographic keys. It includes:

1. Data storage facilities: One or more places that store portions of cryptographic keys.
2. A cryptographic engine: This communicates with the storage facilities and includes:
   • A data splitting module: This tool breaks down the cryptographic keys into portions.
   • A data assembling module: This tool gathers the portions from storage and reconstructs the full cryptographic keys.
   • A cryptographic handling module: This receives the reconstructed keys and performs cryptographic functions with them.

Claim 53: A method of storing data comprising:
This claim details a method for securely storing any type of data, including authentication or cryptographic data. It involves:

1. Receiving data: A "trust engine" (a secure server) receives the data.
2. Combining with random values: The trust engine combines the data with a first random value to create a "first combined value," and with a second random value to create a "second combined value."
3. Creating pairings: It creates two specific pairings of these values and random numbers:
   • A first pairing of the first random value with the second combined value.
   • A second pairing of the first random value with the second random value.
4. Distributed storage: It stores the first pairing in a first secure storage facility and the second pairing in a second secure storage facility that is physically separate from the first.

Federal Circuit (CAFC) 2026 Dockets:
A search for "CAFC 2026 dockets US patent 8271802" does not yield specific cases related to this patent. Appeals from PTAB decisions or District Court cases to the CAFC would typically occur after a final written decision or final judgment. Given that the IPR (IPR2025-01200) was denied institution and the Virginia Eastern District Court case (1:25-cv-00514) is ongoing (and likely just initiated in 2025), it is unlikely to have reached the CAFC docket by April 26, 2026. Therefore, there is no authoritative information about CAFC activity for this patent in 2026 at this time.