Background
Finjan LLC holds patents covering methods for detecting malicious software — specifically, systems for identifying and neutralizing potentially harmful code in software that users download from the internet or receive via email. The patents use the term “Downloadable” to describe a category of computer programs subject to the claimed security scanning methods.
ESET, LLC, an antivirus and cybersecurity company, was sued by Finjan for patent infringement. ESET challenged the validity of the asserted claims on multiple grounds, including that the term “Downloadable” was indefinite under 35 U.S.C. § 112(b) because it did not inform those skilled in the art with reasonable certainty about what the claim covered. The district court agreed and construed the term as indefinite, vacating Finjan’s infringement claims as to those patents. Finjan appealed.
The Court’s Holding
The Federal Circuit reversed. The court applied the settled standard for indefiniteness: a claim is indefinite only if the claim language, read in light of the specification and prosecution history, fails to inform those skilled in the art with reasonable certainty about the scope of the invention. The standard requires reasonable certainty, not absolute precision.
The court found that the term “Downloadable” was not indefinite. Looking to the patent’s specification, the court determined that a person of ordinary skill in the cybersecurity and software fields would understand “Downloadable” to mean “an executable or interpretable application program, which is downloaded from a source computer and run on the destination computer.” The term had a well-understood meaning in the relevant technical context: it referred to software programs retrieved from a network that can be executed or interpreted on the receiving computer — precisely the category of software that the claimed malware detection methods were designed to scan. The court vacated the district court’s indefiniteness ruling and remanded for further proceedings on the merits.
Key Takeaways
- The indefiniteness standard under § 112(b) requires that a claim fail to provide “reasonable certainty” about its scope — absolute precision is not required, and terms that are well understood in the relevant technical community will typically satisfy the standard.
- Technical terms in software and cybersecurity patents should be evaluated through the lens of a skilled artisan in that field, who may readily understand terminology that appears ambiguous to a lay reader.
- Claim terms that are not explicitly defined in the specification can still be definite if the specification, prosecution history, and technical context provide reasonable certainty about their meaning.
- Indefiniteness challenges to well-established technical terms in mature fields like cybersecurity face a high bar, particularly when the term has a recognized meaning in the technical literature and the relevant industry.
Why It Matters
Finjan v. ESET is part of a long-running saga of cybersecurity patent litigation involving Finjan’s foundational malware detection patents. The court’s ruling reinforces that indefiniteness challenges — which can invalidate an entire patent claim — require a high showing that even a skilled artisan in the relevant field cannot determine the claim’s scope with reasonable certainty. For software and cybersecurity patents, where technical terminology evolves quickly but fields develop common understandings of key concepts, the ruling provides important protection against definiteness challenges based on unfamiliar or specialized vocabulary.
Cybersecurity is one of the most active areas of patent litigation, with major antivirus, endpoint protection, and network security vendors regularly challenging each other’s patents. The Finjan v. ESET decision is a useful reminder for practitioners on both sides: patent owners should ensure their specifications anchor key technical terms firmly in the relevant field’s understanding, while challengers asserting indefiniteness must show that the term’s meaning is genuinely uncertain to skilled artisans, not merely that it lacks a technical definition in the specification itself.