Obviousness

Obviousness Analysis of U.S. Patent 10,574,721 under 35 U.S.C. § 103

This analysis assesses the obviousness of U.S. Patent 10,574,721, "Systems and methods for an automatic fresh browser instance for accessing internet content," under 35 U.S.C. § 103, by identifying combinations of prior art references that would render the claims obvious to a person having ordinary skill in the art (PHOSITA). The independent claims 1, 7, and 12 define the core scope of the invention.

The central inventive concept of US10574721 is the automatic launching of a fresh, isolated browser instance for accessing sensitive content, managed by an external daemon that communicates with browser extensions and intercepts system calls.

Key Prior Art References

The patent's citation list includes highly relevant prior art, particularly a non-patent literature (NPL) reference by the same inventors:

1. Zohrevandi & Bazzi (2013): "Auto-FBI: A User-friendly Approach for Secure Access to Sensitive Content on the Web." This NPL is exceptionally relevant as it shares inventors with US10574721 and describes the "Auto-FBI" system, which forms the conceptual basis of the patent.
2. US5974549A (Soliton Ltd.): "Security monitor." This patent discloses the concept of a security monitor that intercepts system calls and network connections to enforce security policies.
3. Jackson et al. (2009): "Protecting browsers from dns rebinding attacks." This NPL addresses methods for protecting browsers from DNS-based attacks, including manipulating DNS responses for security.
4. Garfinkel (2003): "Traps and pitfalls: Practical problems in system call interposition based security tools." This NPL discusses the practicalities and challenges of system call interposition for security.
5. Iverson (2012): "Two Web Browsers can be More Secure than One." This NPL explicitly suggests using multiple web browsers for enhanced security.

Obviousness Combinations and Rationale

Combination 1: Zohrevandi & Bazzi (2013) + General Knowledge in Browser Security and OS Process Control

The NPL "Auto-FBI: A User-friendly Approach for Secure Access to Sensitive Content on the Web" by Zohrevandi & Bazzi (2013) describes the fundamental system and method that the patent claims to embody. The patent's abstract states that its "aspects... involve an automatic fresh browser instance ("FBI") system ("FBI system") for implementing a process that automates compartmentalization practices for accessing different kinds of Internet content with different browser instances." This directly aligns with the title and content of the 2013 paper.

A PHOSITA, seeking to implement the "Auto-FBI" system as described in Zohrevandi & Bazzi (2013), would find the core elements of independent claims 1, 7, and 12 to be obvious or directly taught:

• Content Classification and Separate Browser Instances: The paper inherently teaches categorizing content (e.g., "sensitive sites" vs. "every other type of site" for novice users, or "COI classes" for experienced users) and automatically creating "Fresh Browser Instances" for secure access.
• External Daemon for Management: The patent explicitly describes a "daemon outside the browser" that "keeps track of active instances and launches new instances as needed." This architectural choice for managing browser processes from an external, more privileged entity is a logical and often necessary design for system-level security solutions.
• Browser Extension and Native Application Communication: The patent details that "browser extensions" obtain URLs and "an intermediate process forwards messages between the browser extension and the daemon." This is a known method for a browser-side component to interact with an external, privileged process. The use of "Unix Domain Sockets" for this communication, as specified in claims 7 and 12, is a standard inter-process communication mechanism in Linux environments.
• Confirming No Existing Instance: The patent describes a feature for both novice and experienced users where, if an "existing active instance for the site" or "different browser instance, instance Y that is associated with the class of the URL" is already available, it is reused to process the request. This is a natural optimization for a system managing multiple instances, preventing redundant launches and improving user experience.
• Launching a New Browser: This is the foundational action of the "Auto-FBI" system.

Motivation: Given that Zohrevandi & Bazzi (2013) is a publication by the same inventors describing the "Auto-FBI" system, a PHOSITA would be directly motivated to implement the system as generally described in the paper. Any specific details in the claims not explicitly enumerated in the 2013 paper would likely be considered routine engineering choices for implementing such a system.

Combination 2: Zohrevandi & Bazzi (2013) in view of US5974549A, Jackson et al. (2009), and Garfinkel (2003)

While Zohrevandi & Bazzi (2013) likely covers the high-level design, specific technical enforcement mechanisms found in the patent's claims could be rendered obvious by combining it with other prior art:

• System Call Interception (Claim 3, 4, 5, 9, 10, 14, 15): The patent details an "enforcer" component that intercepts system calls using the ptrace API in Linux. US5974549A teaches a "security monitor" that "intercepts system calls" to enforce security policies. Garfinkel (2003) provides a detailed discussion of system call interposition, confirming this was a known and studied technique.
• DNS Query Rewriting and IP Whitelisting (Claim 11): The patent describes the "tracer" component redirecting DNS queries by "changing the IP addresses in the DNS response to a predefined IP address" to block access, and maintaining an "IP white-list" for allowed connections. Jackson et al. (2009) discusses protecting browsers from DNS rebinding attacks, indicating that manipulating DNS responses for security was known in the art. Employing an IP whitelist is a standard security practice to control network access.

Motivation: A PHOSITA tasked with implementing the "Auto-FBI" system's enforcement mechanism (as outlined in Zohrevandi & Bazzi, 2013) would naturally look to well-known techniques for controlling program behavior and network access at the operating system level.

• The general concept of intercepting system calls for security (taught by US5974549A and Garfinkel (2003)) would provide a clear motivation for the "enforcer" component operating outside the browser.
• Using DNS query rewriting (as exemplified by Jackson et al. (2009) for DNS attack protection) to prevent connections to restricted websites and redirect them would be a logical application of existing knowledge to achieve the "Auto-FBI" system's goal of isolating sensitive content.
• The inclusion of an IP whitelist would be a standard and obvious security measure to ensure the enforcement mechanism cannot be circumvented by hard-coded or cached IP addresses.

Consideration of Different Browser Types (Claims 7 and 12)

The patent further specifies associating content classes with different "browser types" (e.g., Firefox for banking, Chrome for e-commerce), with rules for launching the same or a different type. The NPL by Iverson (2012), titled "Two Web Browsers can be More Secure than One," explicitly suggests the security benefits of using multiple browsers.

Motivation: Given the general concept of compartmentalization and using separate browser instances (from Zohrevandi & Bazzi, 2013), a PHOSITA would be motivated to extend this by utilizing different types of browsers for various sensitive categories to further enhance isolation, leverage specific browser features, or accommodate user preferences, as generally suggested by Iverson (2012). This would be a straightforward design choice given the daemon's role in launching new instances.

In conclusion, the independent claims of US10574721 would be rendered obvious by the combination of the Zohrevandi & Bazzi (2013) paper, which provides the overarching system and method of "Auto-FBI," with well-known techniques for system call interception, DNS manipulation for security, and general principles of secure browser management already present in the cited prior art.