Prosecution Insights
Last updated: November 12, 2026
Application No. 18/763,191

SYSTEMS AND METHODS FOR JAVASCRIPT BASED APPLICATION CYBERSECURITY

Non-Final OA §112
Filed
Jul 03, 2024
Priority
Aug 31, 2020 — provisional 63/072,581 +3 more
Examiner
LOUIE, HOWARD H
Art Unit
2494
Tech Center
2400 — Computer Networks
Assignee
Seraphic Algorithms Ltd.
OA Round
2 (Non-Final)
82%
Grant Probability
Favorable
2-3
OA Rounds
99%
With Interview

Examiner Intelligence

Grants 82% — above average
82%
Career Allowance Rate
159 granted / 194 resolved
+24.0% vs TC avg
Strong +60% interview lift
Without
With
+59.7%
Interview Lift
resolved cases with interview
Typical timeline
Avg Prosecution
14 currently pending
Career history
209
Total Applications
across all art units

Office Action

§112
Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Continued Examination Under 37 CFR 1.114 A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after allowance or after an Office action under Ex Parte Quayle, 25 USPQ 74, 453 O.G. 213 (Comm'r Pat. 1935). Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, prosecution in this application has been reopened pursuant to 37 CFR 1.114. Applicant's submission filed on 8/5/2006 has been reviewed. Information Disclosure Statement The information disclosure statement(s) (IDS) submitted on 8/5/2006 is/are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement(s) is/are being considered by the examiner. Claim Rejections - 35 USC § 112 The following is a quotation of 35 U.S.C. 112(b): (b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention. The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph: The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention. Claim 38 is/are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor, or for pre-AIA the applicant regards as the invention. Claim 38 recites: 38. The system of claim 37, wherein detecting the original input code occurs via at least one of: a local proxy, a local virtual private network server, a native application to monitor JavaScript files. However, since the claim does not recite one of “or a native application” or “and a native application”, it is unclear which interpretation of the claim applies. It is unclear whether the list is conjunctive or disjunctive. See SuperGuide Corp. v. DirecTV Enters., Inc., 358 F.3d 870 (Fed. Cir. 2004) and subsequent case law. In SuperGuide, the Federal Circuit held that the plain meaning of “at least one of A, B, and C” means at least one A, at least one of B and at least one of C. Thus, the meaning of the claim is unclear without “and” or “or” to clarify whether the list is conjunctive or disjunctive. Appropriate correction is required. Allowable Subject Matter Claims 19-37 are allowed. Reasons for Allowance The following is an examiner’s statement of reasons for allowance: The prior art of record (in particular, Hod et al. U.S. Publication 20210026969 (hereinafter "Hod") in view of Fainberg et al. U.S. Publication 20120089695 (hereinafter "Fainberg"), in view of Wei et al. U.S. Publication 20150088970 (hereinafter "Wei"), in view of Bijzitter et al. Bijzitter et al., Installing Node.js (and npm) on Windows 10, https://stackoverflow.com/questions/27344045/installing-node-js-and-npm-on-windows-10, 2014 (hereinafter “Bijzitter”)) does not expressly disclose all the limitations recited in independent claim(s) and the combination of their features thereon. With respect to independent claim(s) 19, 30, and 36 the closest prior art does not disclose at least the following limitations in the recited context: CLAIM 19 patch exposed application programming interfaces using the injected JavaScript cybersecurity agent, wherein the patching is to cause the exposed application programming interfaces to become patched application programming interfaces that exhibit non-native functionality different from the native functionality, and wherein the non-native functionality differs for different execution contexts of the JavaScript enabled application in order to thwart exploitations; manipulate an invocation of the patched application programming interfaces to obtain a manipulated environment state that is different from an original environment state; and generate a mapping between the manipulated environment state and the original environment state. CLAIM 30 patching exposed application programming interfaces using the injected JavaScript cybersecurity agent, wherein the patching is to cause the exposed application programming interfaces to become patched application programming interfaces that exhibit non-native functionality different from the native functionality, and wherein the non-native functionality differs for differing execution contexts of the JavaScript enabled application in order to circumvent exploitations; manipulating an invocation of the patched application programming interfaces to obtain a manipulated environment state that is different from an original environment state; and generating a mapping between the manipulated environment state and the original environment state. CLAIM 36 patch exposed application programming interfaces using the injected JavaScript cybersecurity agent, wherein the patching is to cause the exposed application programming interfaces to become patched application programming interfaces that exhibit non-native functionality different from the native functionality, and wherein the non-native functionality differs for differing execution contexts of the JavaScript enabled application in order to circumvent exploitations; manipulate an invocation of the patched application programming interfaces to obtain a manipulated environment state that is different from an original environment state; and generate a mapping between the manipulated environment state and the original environment state. The Applicant's response on page 8, fourth paragraph to the bottom of the page of the REMARKS filed 3/16/2026 to Hod, Fainberg, Wei and Bijzitter has been fully considered and is persuasive with respect to independent claims 19, 30, and 36. No additional reasons are needed as Applicant's arguments have clearly distinguished the features of the claimed invention from the most relevant prior art of record (Hod, Fainberg, Wei and Bijzitter) and shown that it would not have been obvious to a person having ordinary skill in the art to incorporate the teachings of Fainberg, Wei and Bijzitter into the system of Hod to disclose the claimed embodiment. Therefore, independents claim 19, 30, and 36 is/are allowable. Dependent claims 20-29, 31-35, and 37 is/are allowable in view of their respective dependence from independent claims 19, 30, and 36. Dependent claim 38 would be allowable if the indefiniteness issue is resolved. None of the prior art of record, either taken by itself or in any combination, would have anticipated or made obvious the claimed embodiments of the allowable claims at or before the time it was filed. For the reasons described above, the prior art of record does not disclose, with respect to independent claim(s) 19, 30, and 36, features corresponding to those of independent claim(s) 19, 30, and 36 in their respective contexts. Therefore, the independent claim(s) 19, 30, and 36 is/are allowed. Dependent claims 20-29, 31-35, and 37 are allowed in view of their respective dependence from independent claim(s) 19, 30, and 36. Dependent claim 38 would be allowable if the indefiniteness issue is resolved. Any comments considered necessary by applicant must be submitted no later than the payment of the issue fee and, to avoid processing delays, should preferably accompany the issue fee. Such submissions should be clearly labeled “Comments on Statement of Reasons for Allowance.” Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to HOWARD H LOUIE whose telephone number is 571-272-0036. The examiner can normally be reached on Monday-Friday 9 AM-5 PM EST. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jung W. Kim can be reached on 571-272-3804. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /HOWARD H. LOUIE/Examiner, Art Unit 2494 /THEODORE C PARSONS/Primary Examiner, Art Unit 2494
Read full office action

Prosecution Timeline

Jul 03, 2024
Application Filed
Dec 16, 2025
Non-Final Rejection mailed — §112
Mar 16, 2026
Response Filed
Apr 13, 2026
Examiner Interview (Telephonic)
Aug 05, 2026
Request for Continued Examination
Aug 08, 2026
Response after Non-Final Action
Oct 28, 2026
Non-Final Rejection mailed — §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12762239
AUTOMATIC SYSTEM FOR DYNAMIC ATTESTATION FOR DEVICE FIRMWARE
2y 5m to grant Granted Oct 13, 2026
Patent 12763932
ORGANIZED DATA STORAGE SYSTEM
1y 10m to grant Granted Oct 13, 2026
Patent 12748840
SYSTEMS AND METHODS FOR INTERPRETER BASED APPLICATION CYBERSECURITY
2y 2m to grant Granted Sep 29, 2026
Patent 12730760
MEMORY ISOLATION SECURITY IN A DATA PROCESSING SYSTEM
2y 5m to grant Granted Sep 08, 2026
Patent 12705318
DATA CONTROL FOR ZERO-TRUST SECURITY CONTAINER
2y 7m to grant Granted Aug 11, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

2-3
Expected OA Rounds
82%
Grant Probability
99%
With Interview (+59.7%)
Moderate
PTA Risk
Based on 194 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month