Invalidity dossier

US 9135418

System and method for creating secure applications

Current assignee: Congruent Media Resourcing LLC

Added 4/27/2026, 7:40:36 AM

Active provider: Google · gemini-2.5-flash

Auto-generating section 1 of 2: Extensions

Each section takes ~30-60s with web-search grounding. Keep this tab open — sections will fill in below as they complete.

Patent summary

Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.

✓ Generated

Here is a concise summary of US patent 9135418:

US Patent 9135418: System and method for creating secure applications

  • Title: System and method for creating secure applications
  • Assignee: Congruent Media Resourcing LLC (originally OpenPeak Inc.)
  • Inventors: Christopher Michael Wade, Danilo Tan, John R. Brown, Paul Krzyzanowski, Daniel Gittleman, Robert M Dare
  • Filing Date: 2014-02-25
  • Issue Date: 2015-09-15
  • Abstract: The patent describes a method for creating a secure application. This involves taking a target application, decomposing it into its original files containing predictable instructions, then modifying it by binding "intercepts." These intercepts allow the predictable instructions to be altered based on policies, making the secure application behave differently from the original. The secure application is then repackaged with these integrated intercepts. The process preserves the original operating system interactions and imposes a unique, unpredictable namespace on the application's internal communications to prevent unauthorized access.

Plain-Language Overview of Independent Claims:

  • Claim 1 (Method for generating a secure application): This claim describes a method to convert a standard application into a secure one. It involves breaking down the original application, injecting new instructions or replacements ("intercepts") based on security policies, and then repackaging it so these new instructions are permanently integrated. The process ensures that the secure application maintains its compatibility with the original operating system. Additionally, it applies a scrambled, unique identifier to the application's internal communications to block other, unauthorized applications from accessing its data.
  • Claim 12 (Method for generating a secure application, focusing on configuration): This method also focuses on creating a secure application from a pre-compiled one without needing access to its source code or disrupting the operating system's normal functions. It involves identifying specific instructions in the application and configuring them to allow for selective changes in behavior. A key aspect is automatically intervening in any calls the application makes to share or store data, ensuring that sensitive data is handled securely.
  • Claim 18 (Method for generating a secure application, focusing on preserving functionality): This claim outlines a method where a target application is modified by adding intercepts to change its behavior. The core of this claim is that while the overall behavior of the secure application can be different from the original, its original functions ("pre-existing functionality") are maintained. The change in behavior is achieved by selectively controlling when and how that pre-existing functionality is allowed to execute, often based on specific conditions.
  • Claim 26 (Method of restricting access to an application): This claim details a method for isolating applications to prevent unauthorized data access. It involves taking an application that normally communicates openly and, during a "securitization" process, assigning it a hidden, unique identifier (an "obfuscated namespace") for its internal communications. This setup allows other secure applications, which also use this unique namespace, to share data with it, but prevents non-secure applications from understanding or processing these communications.
  • Claim 30 (Method of managing application behavior): This claim describes how a secure application's behavior is managed when it's launched. The secure application has both its original behaviors and new, imposed secure behaviors. When the application is activated, the system forces the secure application to prioritize and perform the new, secure behaviors. The claim also includes the ability to selectively allow the original behaviors to occur, but only if specific, predefined criteria are met.
  • Claim 35 (System for generating a secure application): This claim describes the actual system components that perform the securitization. It includes a "disassembler" that breaks down a target application into its basic instructions. A "securitization agent" then identifies these instructions, modifies the application by adding intercepts (without needing the original source code), integrates these intercepts, and ensures the application still works with its intended operating system. This agent also imposes a secure and unpredictable namespace on the application's internal communications to prevent unauthorized data access.

USPTO and CAFC 2026 Dockets:
As of April 26, 2026, the patent US9135418 is active and is set to expire on 2032-11-25.
The patent family is involved in litigation. Multiple US cases were filed in the Texas Western District Court and Texas Eastern District Court in both 2025 and 2026.

Specifically for 2026, cases include:

  • Texas Western District Court, case 7:26-cv-00156
  • Texas Western District Court, case 7:26-cv-00155

No dockets specifically for the Court of Appeals for the Federal Circuit (CAFC) in 2026 were found for US9135418 based on the provided information, indicating that the district court litigation may still be ongoing or has not yet reached the appellate stage.

Generated 5/30/2026, 12:45:38 PM