# US 2024/0187456 A1 · Updating security rule sets using repository switching

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

- Number: US 2024/0187456 A1
- Document ID: US20240187456A1
- Status: Published application
- Kind: A1
- Application number: 18/419,162
- Filed: 2024-01-22
- Published: 2024-06-06
- Earliest claimed: 2022-02-01
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Srinivas ALLADI; Muthukumar KUBENDRAN
- Web page: https://patentgrep.com/patent/US20240187456A1

## CPC

- H04L 63/205: {involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved (negotiation of communication capabilities H04L69/24)}
- H04L 63/0263: {Rule management}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and systems are described herein for updating cybersecurity enforcement rules in real-time over disparate computer networks. A rule enforcement system may receive a real-time data stream. The real-time data stream may include real-time communications requiring cybersecurity verification. Real-time data communications are processed through a first rule repository. In response to determining that rule updates to rules within the first rule repository are available, a second rule repository is retrieved and brought online. Previously received real-time communication data is processed with the first rule repository and new real-time communication data is routed to the second rule repository. When previously received real-time communication data has been processed, the first rule repository is disabled.

## Claims

### Claim 1

A system for updating cybersecurity enforcement rules in real-time over disparate computer networks, the system comprising:
one or more processors; and
a non-transitory, computer-readable storage medium storing instructions, which when executed by the one or more processors cause the one or more processors to perform operations comprising:
receiving a real-time data stream, the real-time data stream comprising a series of real-time communications requiring cybersecurity verification;
routing the real-time data stream to a first queue associated with a first rule repository, wherein the first rule repository comprises a complete rule set for addressing known cybersecurity incidents, and wherein the series of real-time communications is processed using the first rule repository;
determining that rule updates are available for rules within the first rule repository;
in response to determining that the rule updates are available, retrieving a second rule repository, wherein the second rule repository comprises a revised complete rule set for addressing the known cybersecurity incidents;
in response to verifying that the second rule repository has been received, routing the real-time data stream to a second queue associated with the second rule repository;
in response to routing the real-time data stream to the second queue, processing a first portion of the series of real-time communications in the first queue with the first rule repository and, a second portion of the series of real-time communications in the second queue using the second rule repository; and
setting a flag on the first rule repository that disables the first rule repository based on completion of processing of the first portion of the series of real-time communications.

### Claim 2 (depends on 1)

The system of claim 1, wherein the instructions further cause the one or more processors to, prior to routing the real-time data stream to the second queue, authenticate the second rule repository using metadata associated with the second rule repository.

### Claim 3 (depends on 1)

The system of claim 1, wherein the instructions further cause the one or more processors to:
prior to routing the real-time data stream to the second queue:
transmit one or more synthetic requests to the second rule repository; and
validate the second rule repository based on responses from the second rule repository to the one or more synthetic requests.

### Claim 4 (depends on 1)

The system of claim 1, wherein the instructions further cause the one or more processors to perform the operations comprising:
determining that a number of requests rejected based on processing the second portion of real-time communications using the second rule repository exceeds a threshold; and
in response to determining that the number of requests rejected based on processing the second portion of real-time communications using the second rule repository exceeds the threshold, performing a roll-back operation to the first rule repository.

### Claim 5

A method comprising:
receiving a series of real-time communications requiring cybersecurity verification;
routing the series of real-time communications to a first queue associated with a first rule repository, wherein the first rule repository comprises a complete rule set related to cybersecurity;
retrieving a second rule repository, wherein the second rule repository comprises a revised complete rule set related to cybersecurity;
based on retrieving the second rule repository, switching routing of subsequent real-time communications to a second queue associated with the second rule repository;
based on switching the routing of the subsequent real-time communications to the second queue, processing the series of real-time communications within the first queue using the first rule repository, and the subsequent real-time communications in the second queue using the second rule repository; and
disabling the first rule repository based on completion of the series of real-time communications.

### Claim 6 (depends on 5)

The method of claim 5, further comprising, prior to switching routing of the subsequent real-time communications to the second queue, authenticating the second rule repository using metadata associated with the second rule repository.

### Claim 7 (depends on 5)

The method of claim 5, further comprising:
prior to switching routing of the subsequent real-time communications to the second queue, transmitting one or more synthetic requests to the second rule repository; and
validating the second rule repository based on responses from the second rule repository to the one or more synthetic requests.

### Claim 8 (depends on 5)

The method of claim 5, further comprising:
determining that a number of requests rejected based on processing the subsequent real-time communications using the second rule repository exceeds a threshold; and
in response to determining that the number of requests rejected based on processing the subsequent real-time communications using the second rule repository exceeds the threshold, performing a roll-back operation to the first rule repository.

### Claim 9 (depends on 5)

The method of claim 5, further comprising:
determining that a criterion for querying for a rule update has been met;
querying a remote data source for the rule update based the criterion; and
determining, based on results of querying the remote data source, that the rule update is available.

### Claim 10 (depends on 9)

The method of claim 9, wherein determining that the criterion for querying the rule update has been met:
determining whether a size of an incoming request of a plurality of incoming requests has exceeded a size threshold;
determining whether a volume of the plurality of incoming requests has exceeded a volume threshold; and
based on determining that the size of the incoming request has exceeded the size threshold or the volume of the plurality of incoming requests has exceeded the volume threshold, determining that the criterion for querying the rule update has been met.

### Claim 11 (depends on 9)

The method of claim 9, wherein determining that the criterion for querying the rule update has been met:
determining that a rate of change of incoming requests has exceeded a rate threshold; and
based on determining that the rate of change of incoming requests has exceeded the rate threshold, determining that the criterion for querying the rule update has been met.

### Claim 12 (depends on 5)

The method of claim 5, further comprising:
detecting a new cybersecurity incident; and
generating a third rule repository based on the new cybersecurity incident.

### Claim 13

A non-transitory, computer-readable medium storing instructions for updating cybersecurity enforcement rules in real-time over disparate computer networks, when executed by one or more processors, cause the one or more processors to perform operations comprising:
receiving a series of real-time communications requiring cybersecurity verification;
routing the series of real-time communications to a first queue associated with a first rule repository, wherein the first rule repository comprises a complete rule set related to cybersecurity;
retrieving a second rule repository, wherein the second rule repository comprises a revised complete rule set related to cybersecurity;
based on retrieving the second rule repository, switching routing of subsequent real-time communications to a second queue associated with the second rule repository;
based on switching the routing of the subsequent real-time communications to the second queue, processing the series of real-time communications within the first queue using the first rule repository, and the subsequent real-time communications in the second queue using the second rule repository; and
disabling the first rule repository based on completion of the series of real-time communications.

### Claim 14 (depends on 13)

The non-transitory, computer-readable medium of claim 13, wherein the instructions further cause the one or more processors, prior to routing the subsequent real-time communications to the second queue, authenticate the second rule repository using metadata associated with the second rule repository.

### Claim 15 (depends on 14)

The non-transitory, computer-readable medium of claim 14, wherein the instructions further cause the one or more processors, prior to routing the subsequent real-time communications to the second queue, to perform operations comprising:
transmitting one or more synthetic requests to the second rule repository; and
validating the second rule repository based on responses from the second rule repository to the one or more synthetic requests.

### Claim 16 (depends on 13)

The non-transitory, computer-readable medium of claim 13, wherein the instructions further cause the one or more processors to perform operations comprising:
determining that a number of requests rejected based on processing the subsequent real-time communications using the second rule repository exceeds a threshold; and
in response to determining that the number of requests rejected based on processing the subsequent real-time communications using the second rule repository exceeds the threshold, performing a roll-back operation to the first rule repository.

### Claim 17 (depends on 13)

The non-transitory, computer-readable medium of claim 13, wherein the instructions further cause the one or more processors to perform operations comprising:
determining that a criterion for querying for a rule update has been met;
querying a remote data source for the rule update based the criterion; and
determining, based on results of querying the remote data source, that the rule update is available.

### Claim 18 (depends on 17)

The non-transitory, computer-readable medium of claim 17, wherein the instructions for determining that the criterion for querying the rule update has been met further cause the one or more processors to perform operations comprising:
determining whether a size of an incoming request of a plurality of incoming requests has exceeded a size threshold;
determining whether a volume of the plurality of incoming requests has exceeded a volume threshold; and
based on determining that the size of the incoming request has exceeded the size threshold or the volume of the plurality of incoming requests has exceeded the volume threshold, determining that the criterion for querying the rule update has been met.

### Claim 19 (depends on 17)

The non-transitory, computer-readable medium of claim 17, wherein the instructions for determining that the criterion for querying the rule update has been met further cause the one or more processors to perform operations comprising:
determining that a rate of change of incoming requests has exceeded a rate threshold; and
based on determining that the rate of change of incoming requests has exceeded the rate threshold, determining that the criterion for querying the rule update has been met.

### Claim 20 (depends on 19)

The non-transitory, computer-readable medium of claim 19, wherein the instructions further cause the one or more processors to perform operations comprising:
detecting a new cybersecurity incident; and
generating a third rule repository based on the new cybersecurity incident.
