# US 2026/0095482 A1 · Application layer security policy implementation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0095482 A1
- Document ID: US20260095482A1
- Status: Published application
- Kind: A1
- Application number: 19/111,690
- Filed: 2023-09-14
- Published: 2026-04-02
- Earliest claimed: 2022-09-14
- Assignees: Secure Industries Midco, Inc.
- Applicants: Secure Industries Midco, Inc.
- Inventors: Halis Osman Erkan; Murat Demirten
- Web page: https://patentgrep.com/patent/US20260095482A1

## CPC

- H04L 63/168: {above the transport layer}
- G06F 21/50: Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 63/1433: {Vulnerability analysis}
- H04L 63/1483: {service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12)}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 69/30: Definitions, standards or architectural aspects of layered protocol stacks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques include using a browser extension to cause a remote cloud controller to query a threat database; the browser extension takes action based on security policies derived from the threat database. The browser extension applies the security policies by determining whether to allow access to a website, block access to the website, alter content of the website, e.g., to block dangerous links and/or prevent phishing attacks, or remove browser isolation. It is noted that the application of the security policy is performed at the application layer rather than at the data link layer or the network layer of the ISO model.

## Claims

### Claim 1

A method, comprising:
receiving, by processing circuitry via an application layer in a browser, a set of uniform resource indicators (URIs), each URI of the set of URIs indicating an address of a website to which a user has requested access;
sending the set of URIs to a cloud controller external to the processing circuitry, the cloud controller being configured to locate the set of URIs in a threat intelligence database;
receiving, from the cloud controller, threat intelligence data from the threat intelligence database;
analyzing a document object model (DOM) of a website associated with the set of URIs according to the threat intelligence data;
applying a set of security policies to the browser based on the threat intelligence data; and
displaying a rendered browser image on a display for the user according to the set of security policies.

### Claim 2 (depends on 1)

The method as in claim 1, wherein the set of security policies include at least one of block, allow, render read-only, remove browser isolation, or alternate content of the website via the DOM to at least one of remove or disable content that potentially includes threats.

### Claim 3 (depends on 1)

The method as in claim 1, further comprising:
performing a hooking operation on a network request loop to produce a hooked network request loop, the set of URIs being rendered from a relevant function of the hooked network request loop.

### Claim 4 (depends on 3)

The method as in claim 3, wherein the hooking operation is performed with a standard hooking technique of at least one extension in the browser.

### Claim 5 (depends on 3)

The method as in claim 3, wherein the relevant function is an onBeforeRequest function.

### Claim 6 (depends on 3)

The method as in claim 3, wherein the relevant function is an externally_connectable function.

### Claim 7 (depends on 3)

The method as in claim 3, wherein applying the set of security policies includes:
inserting, via at least one content script, the set of security policies into the DOM.

### Claim 8 (depends on 3)

The method as in claim 3, wherein the DOM is continuously inserted into the network request loop.

### Claim 9 (depends on 1)

The method as in claim 1, wherein applying the set of security policies includes:
disabling a data input field of the browser.

### Claim 10 (depends on 9)

The method as in claim 9, wherein the data input field includes a password entry box.

### Claim 11

A computer program product comprising a nontransitive storage medium, the computer program product including code that, when executed by processing circuitry, causes the processing circuitry to perform a method, the method comprising:
receiving, by the processing circuitry via an application layer in a browser, a set of uniform resource indicators (URIs), each URI of the set of URIs indicating an address of a website to which a user has requested access;
sending the set of URIs to a cloud controller external to the processing circuitry, the cloud controller being configured to locate the set of URIs in a threat intelligence database;
receiving, from the cloud controller, threat intelligence data from the threat intelligence database;
analyzing a document object model (DOM) of a website associated with the set of URIs according to the threat intelligence data;
applying a set of security policies to the browser based on the threat intelligence data; and
displaying a rendered browser image on a display for the user according to the set of security policies.

### Claim 12 (depends on 11)

The computer program product as in claim 11, wherein the set of security policies include at least one of block, allow, render read-only, remove browser isolation, or alternate content of the website via the DOM to at least one of remove or disable content that potentially includes threats.

### Claim 13 (depends on 11)

The computer program product as in claim 11, wherein the method further comprises:
performing a hooking operation on a network request loop to produce a hooked network request loop, the set of URIs being rendered from a relevant function of the hooked network request loop.

### Claim 14 (depends on 13)

The computer program product as in claim 13, wherein applying the set of security policies includes:
inserting, via at least one content script, the set of security policies into the DOM.

### Claim 15 (depends on 11)

The computer program product as in claim 11, wherein applying the set of security policies includes:
disabling a data input field of the browser.

### Claim 16

An electronic apparatus, the electronic apparatus comprising:
memory; and
processing circuitry coupled to the memory, the processing circuitry being configured to:
receive, via an application layer in a browser, a set of uniform resource indicators (URIs), each URI of the set of URIs indicating an address of a website to which a user has requested access;
send the set of URIs to a cloud controller external to the processing circuitry, the cloud controller being configured to locate the set of URIs in a threat intelligence database;
receive, from the cloud controller, threat intelligence data from the threat intelligence database;
analyze a document object model (DOM) of a website associated with the set of URIs according to the threat intelligence data;
apply a set of security policies to the browser based on the threat intelligence data; and
display a rendered browser image on a display for the user according to the set of security policies.

### Claim 17 (depends on 16)

The electronic apparatus as in claim 16, wherein the set of security policies include at least one of block, allow, render read-only, remove browser isolation, or alternate content of the website via the DOM to at least one of remove or disable content that potentially includes threats.

### Claim 18 (depends on 16)

The electronic apparatus as in claim 16, wherein the processing circuitry is further configured to:
perform a hooking operation on a network request loop to produce a hooked network request loop, the set of URIs being rendered from a relevant function of the hooked network request loop.

### Claim 19 (depends on 18)

The electronic apparatus as in claim 18, wherein the processing circuitry configured to apply the set of security policies is further configured to:
insert, via at least one content script, the set of security policies into the DOM.

### Claim 20 (depends on 16)

The electronic apparatus as in claim 16, wherein the processing circuitry configured to apply the set of security policies is further configured to:
disable a data input field of the browser.
