DCT
2:24-cv-00778
DigitalDoors Inc v. PlainsCapital Bank
Key Events
Complaint
Table of Contents
complaint
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: DigitalDoors, Inc. (Florida)
- Defendant: PlainsCapital Bank (Texas)
- Plaintiff’s Counsel: Garteiser Honea, PLLC
- Case Identification: 2:24-cv-00778, E.D. Tex., 09/25/2024
- Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant maintains a regular and established business presence, including physical locations and employees, and specifically targets customers within the district.
- Core Dispute: Plaintiff alleges that Defendant’s data backup and disaster recovery systems, which are asserted to be compliant with the financial industry’s “Sheltered Harbor” standard, infringe four patents related to methods for securely filtering, extracting, and storing sensitive data in distributed computing systems.
- Technical Context: The technology concerns granular data security, where specific sensitive content within data streams is identified and segregated into secure, isolated storage vaults, enhancing resilience against catastrophic data loss or cyberattacks.
- Key Procedural History: The complaint asserts the patents-in-suit are "pioneering" and have been cited as relevant prior art in hundreds of subsequent patent applications by major technology and financial services companies. No prior litigation or post-grant proceedings involving the patents are mentioned.
Case Timeline
| Date | Event |
|---|---|
| 2007-01-05 | Earliest Patent Priority Date ('301, '169, '073, '639 Patents) |
| 2015-04-21 | U.S. Patent No. 9,015,301 Issues |
| 2015-01-01 | Sheltered Harbor initiative launched (approximate date) |
| 2017-08-15 | U.S. Patent No. 9,734,169 Issues |
| 2019-01-15 | U.S. Patent No. 10,182,073 Issues |
| 2019-04-02 | U.S. Patent No. 10,250,639 Issues |
| 2024-09-25 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 9,015,301
- Patent Identification: U.S. Patent No. 9,015,301, "Information Infrastructure Management Tools with Extractor, Secure Storage, Analysis and Classification and Method Therefor," issued April 21, 2015.
The Invention Explained
- Problem Addressed: The patent’s background describes the difficulty enterprises faced in managing unstructured data, controlling access in open information ecosystems, and addressing the changing sensitivity of information over its lifecycle ('301 Patent, col. 1:31-38; 2:3-27). Conventional approaches focused on entire files rather than the sensitive content within them, offering inadequate security and management capabilities (Compl. ¶¶28, 30).
- The Patented Solution: The invention provides a method for organizing and processing data in a distributed system by using "categorical filters" to identify and extract "select content" (important data) from a larger data input. This extracted content is stored in designated data stores, and specific data processes (e.g., copy, archive, destroy) are associated with the activated filter, allowing for the automatic processing of subsequent data inputs that match the filter's criteria ('301 Patent, Abstract; col. 3:17-4:35).
- Technical Importance: This approach enabled a more granular level of data management and security, shifting the focus from securing entire files to securing specific, sensitive information contained within those files (Compl. ¶28).
Key Claims at a Glance
- The complaint asserts infringement of at least independent claim 25 (Compl. ¶99).
- The essential elements of Claim 25 include:
- Providing a plurality of select content data stores operative with designated categorical filters.
- Activating at least one filter to process a data input and obtain select content.
- Storing the obtained select content in a corresponding data store.
- Associating a data process (e.g., copy, extract, archive, distribution, destruction) with the activated filter.
- Applying that associated data process to a further data input processed by the filter.
- The filter activation can be automatic (e.g., time-based, condition-based) or manual.
- The complaint does not explicitly reserve the right to assert dependent claims.
U.S. Patent No. 9,734,169
- Patent Identification: U.S. Patent No. 9,734,169, "Digital Information Infrastructure and Method for Securing Designated Data and With Granular Data Stores," issued August 15, 2017.
The Invention Explained
- Problem Addressed: The patent addresses the need for enhanced data security in distributed and cloud-based systems, where numerous access points and the open nature of the ecosystem create vulnerabilities to data breaches and misuse ('169 Patent, col. 1:11-2:54).
- The Patented Solution: The invention describes a method for a distributed, cloud-based system that separates data into different storage types based on sensitivity. The system extracts "security designated data" and places it in "select content data stores" that are governed by strict access controls. The "remainder data" that was not extracted is parsed and stored separately in "granular data stores." Data can only be retrieved from any store by satisfying the relevant access controls, thereby securing the sensitive information in an isolated environment ('169 Patent, Abstract; col. 3:27-4:27).
- Technical Importance: The claimed architecture is designed to minimize the attack surface by physically or logically isolating critical data from the less sensitive remainder, a key principle in modern cybersecurity for distributed networks (Compl. ¶131).
Key Claims at a Glance
- The complaint asserts infringement of at least independent claim 1 (Compl. ¶130).
- The essential elements of Claim 1 include:
- Providing a system with select content data stores, granular data stores, and a cloud-based server.
- Coupling the stores and server with a communications network.
- Extracting and storing security-designated data in the select content data stores, which have access controls.
- Activating a data store to permit access based on the application of access controls.
- Parsing remainder data not extracted and storing it in the granular data stores.
- Withdrawing data from the stores only when respective access controls are applied.
- The complaint does not explicitly reserve the right to assert dependent claims.
Multi-Patent Capsule: U.S. Patent No. 10,182,073
- Patent Identification: U.S. Patent No. 10,182,073, "Information Infrastructure Management Tools with Variable and Configurable Filters and Segmental Data Stores," issued January 15, 2019.
- Technology Synopsis: This patent describes an information infrastructure where data throughput is processed using a plurality of filters. The system identifies sensitive content with initially configured filters and includes a method for altering these filters (e.g., expanding or contracting their rules) to generate modified filters that organize further data processing ('073 Patent, Abstract; Compl. ¶¶167, 182).
- Asserted Claims: Claim 1 is asserted (Compl. ¶166).
- Accused Features: The complaint alleges that the accused systems' use of dynamic and modifiable "protection policies," which can be created and edited by the bank via a user interface to define what data to back up, infringes the claimed method of altering and generating filters (Compl. ¶¶183, 185, 186).
Multi-Patent Capsule: U.S. Patent No. 10,250,639
- Patent Identification: U.S. Patent No. 10,250,639, "Information Infrastructure Management Data Processing Tools for Processing Data Flow with Distribution Controls," issued April 2, 2019.
- Technology Synopsis: This patent discloses a method for "sanitizing" data in a distributed system. The process involves extracting sensitive content from a data input based on predefined sensitivity levels and associated security clearances, storing the extracted data in secure stores, and using content, contextual, and taxonomic filters to "inference" the resulting sanitized data ('639 Patent, Abstract; Compl. ¶¶194, 218).
- Asserted Claims: Claim 16 is asserted (Compl. ¶193).
- Accused Features: The complaint alleges that the accused systems' extraction of critical financial data into an isolated data vault constitutes the claimed "sanitizing" process, and that the use of protection policies and content scans to identify and analyze this data meets the "inferencing" limitation (Compl. ¶¶215, 221).
III. The Accused Instrumentality
- Product Identification: The "Accused Instrumentalities" are the systems and methods used by PlainsCapital Bank for data backup and disaster recovery, which are alleged to be compliant with the Sheltered Harbor financial industry standard or its functional equivalent (Compl. ¶96). The complaint identifies Dell’s PowerProtect Cyber Recovery solution as an exemplary system that satisfies the Sheltered Harbor specification (Compl. ¶72).
- Functionality and Market Context: The accused systems are designed to protect critical customer financial data from catastrophic events like cyberattacks (Compl. ¶63). The core functionality involves creating daily, encrypted, and immutable copies of critical account data in a secure, isolated "data vault" that is "air-gapped" from the institution's primary production and backup networks (Compl. ¶¶70, 73, 77). The complaint includes a diagram illustrating how data is extracted from a "Production Environment" and replicated to an air-gapped "Data Vault Environment" (Compl. ¶73). In the event of a system failure, this vaulted data can be used to restore basic customer services (Compl. ¶71). Sheltered Harbor is described as an industry-driven standard essential for maintaining public confidence in the financial system (Compl. ¶¶63, 66).
IV. Analysis of Infringement Allegations
'301 Patent Infringement Allegations
| Claim Element (from Independent Claim 25) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| A method of organizing and processing data in a distributed computing system having select content important to an enterprise... | Defendant is the enterprise operating a distributed computing system (the Accused Instrumentalities) for processing important data (critical customer financial account data). | ¶100, 102 | col. 127:67-128:8 |
| providing, in said distributed computing system, a plurality of select content data stores operative with a plurality of designated categorical filters... | The Accused Instrumentalities provide a "data vault" with designated stores for content derived from categorical filters (i.e., protection policies). | ¶105, 107 | col. 128:9-17 |
| activating at least one of said designated categorical filters and processing a data input therethrough to obtain said select content... | The accused systems activate "protection policies" (filters) to extract critical financial account data (select content) from the production environment. | ¶109, 110 | col. 128:18-23 |
| storing said aggregated select content for said at least one categorical filter in said corresponding select content data store; | The extracted critical account data is stored in corresponding storage units within the secure data vault. | ¶113, 114 | col. 128:24-27 |
| associating at least one data process from the group of data processes including a copy process, a data extract process, a data archive process, a data distribution process and a data destruction process; | The system's protection policies associate data processes (e.g., backup/copy, archive) with the filtered data to be vaulted. | ¶116, 117 | col. 128:28-33 |
| applying the associated data process to a further data input based upon a result of said further data being processed by said activated categorical filter... | Once a protection policy is established, all subsequent data inputs (e.g., new data) are automatically processed in the same way (e.g., backed up to the same storage unit). | ¶119, 121 | col. 128:34-42 |
| wherein activating a designated categorical filter encompasses an automatic activation... and said automatic activation is time-based, distributed computer system condition-based, or event-based. | Processing occurs automatically based on a designated time interval (nightly), a condition (detection of new data), or an event. | ¶122, 123 | col. 128:43-49 |
- Identified Points of Contention:
- Scope Questions: The case may turn on whether the financial industry term "data vaulting" for disaster recovery purposes falls within the scope of the patent's claim language for "organizing and processing data." A defendant may argue that creating a backup is functionally distinct from the patent's more granular method of associating multiple, distinct "data processes" with filtered content.
- Technical Questions: A key question is whether a "protection policy" in a modern backup system, which defines what data to copy, is technically equivalent to the claimed "categorical filter." The complaint’s assertion hinges on this equivalence. The complaint includes a diagram from a Dell technical brief illustrating the architecture of the Sheltered Harbor solution, showing "Data Extraction" in a production environment and a separate, air-gapped "Data Vault Environment" where replicated data undergoes "Sheltered Harbor Processes" (Compl. ¶73).
'169 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| A method of organizing and processing data in a distributed cloud-based computing system... | The Accused Instrumentalities are optionally implemented on cloud-based platforms such as AWS, Azure, or Google Cloud. | ¶131, 133 | col. 132:13-18 |
| providing... (i) a plurality of select content data stores...; and (ii) a plurality of granular data stores; and (iii) a cloud-based server, each select content data store having respective access controls... | The system provides a secure data vault (select content stores with access controls) and production/backup systems (granular data stores), operated via a cloud-based server. | ¶137, 138, 140 | col. 132:19-27 |
| providing a communications network operatively coupling said plurality of select content data stores and cloud-based server; | The system includes an operatively coupled communications network that connects the production and vaulting environments. | ¶142, 143 | col. 132:28-31 |
| (with respect to data processed by said cloud-based system) extracting and storing said security designated data in respective select content data stores; | Critical account data is extracted from the production environment and stored in the secure data vault. | ¶144, 148 | col. 132:32-35 |
| activating at least one of said select content data stores... permitting access... based upon an application of one or more of said access controls thereat; | Access to the data vault is permitted only upon satisfaction of security measures like multi-factor authentication. | ¶149, 151 | col. 132:36-41 |
| parsing remainder data not extracted... and storing the parsed data in respective granular data stores; | Non-extracted data remains stored in the production and backup systems, which the complaint identifies as the "granular data stores." A diagram shows "Backup Workloads" in the production data center separate from the "Cyber Recovery Vault" (Compl. ¶153). | ¶152, 154 | col. 132:42-45 |
| withdrawing some or all of said security designated data... only in the presence of said respective access controls... | Data is withdrawn from the vault for restoration only after strict security and access controls are satisfied. | ¶158, 160 | col. 132:53-57 |
- Identified Points of Contention:
- Scope Questions: It raises a question whether leaving data in its original location (the production environment) constitutes "parsing... and storing the parsed data in respective granular data stores." A defendant may argue this requires an active step of parsing and moving data, not merely failing to extract it.
- Technical Questions: The complaint alleges that encrypting data satisfies the limitation of "randomly parsing" or parsing "according to a predetermined algorithm" (Compl. ¶156). This connection may be a point of dispute, as encryption is a data transformation process, whereas parsing is typically understood as analyzing and structuring data.
V. Key Claim Terms for Construction
U.S. Patent No. 9,015,301
- The Term: "categorical filter"
- Context and Importance: This term is the core mechanism for identifying the "select content" to be processed and stored. The breadth of its definition will determine whether the "protection policies" used in the accused backup systems infringe. Practitioners may focus on whether this term requires more than simple data selection rules.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification describes these filters broadly as including "content-based filters, contextual filters and taxonomic classification filters" ('301 Patent, col. 13:35-37), suggesting the term is not limited to a single type of rule.
- Evidence for a Narrower Interpretation: The detailed description often describes the filters in the context of sophisticated classification systems, such as a "hierarchical taxonomic system" that uses a "Knowledge Expander (KE) search engine" ('301 Patent, col. 10:22-32). This could support an argument that the term implies more than a simple backup policy.
U.S. Patent No. 9,734,169
- The Term: "parsing remainder data... and storing the parsed data"
- Context and Importance: The infringement theory depends on equating the act of not extracting data from the production environment with the claim step of "parsing" and "storing" that remainder data elsewhere. The construction of this term is central to whether the accused systems perform this claimed step.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The Abstract states the method includes "parsing remainder data not extracted from data processed... and storing the parsed data," which could suggest the focus is on the result (separation) rather than the specific mechanism.
- Evidence for a Narrower Interpretation: The specification describes an active system for processing data, stating the system "separates extracted data (security sensitive or select content) words... from the remainder" ('169 Patent, col. 45:34-39). This language suggests an active separation process, which may not be met by simply leaving data in its original location.
VI. Other Allegations
- Indirect Infringement: The complaint does not plead separate counts for indirect infringement. The theory of liability is focused on direct infringement by Defendant, who allegedly "makes, owns, operates, uses, or otherwise exercises control" over the accused systems (Compl. ¶96).
- Willful Infringement: The complaint alleges willfulness based on Defendant’s knowledge of the patents since at least the date of service of the complaint (Compl. ¶227). It further alleges willful blindness, asserting on information and belief that Defendant has a policy of not reviewing others' patents and is aware of infringement lawsuits filed by the Plaintiff against competitor financial institutions (Compl. ¶¶227-228).
VII. Analyst’s Conclusion: Key Questions for the Case
- A core issue will be one of definitional scope: Can the technical patent term "categorical filter" be construed broadly enough to read on the "protection policies" used in industry-standard disaster recovery systems like Sheltered Harbor, or do the patents claim a more sophisticated, content-aware classification system that the accused systems do not practice? The complaint's infringement theory rests on mapping the language of one technical domain (patented data processing) onto another (industry-standard data vaulting). A screenshot in the complaint shows a user interface for generating a report with "Filters," which Plaintiff will likely argue demonstrates the accused systems' use of the claimed feature (Compl. ¶183).
- A key evidentiary question will be one of functional equivalence: Does the accused systems' act of leaving non-critical data in a production environment while backing up critical data to a vault constitute the active claim step of "parsing remainder data... and storing the parsed data in respective granular data stores," as required by the '169 Patent? The resolution of this question will likely depend on expert testimony regarding the technical meaning of "parsing" in the context of the patent.
Analysis metadata