# US 2026/0228339 A1 · Automatic connectivity to IGA systems

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

- Number: US 2026/0228339 A1
- Document ID: US20260228339A1
- Status: Published application
- Kind: A1
- Application number: 19/046,553
- Filed: 2025-02-06
- Published: 2026-08-06
- Earliest claimed: 2025-02-06
- Assignees: Orchid Security Inc.
- Applicants: Orchid Security Inc.
- Inventors: Roy Katmor; Ido Kelson; Robert Wiseman; Peleg Hadar
- Web page: https://patentgrep.com/patent/US20260228339A1

## CPC

- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F 9/54: Interprogram communication
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, computing systems and computer program products implement embodiments of the present invention that include identifying, in a software application loaded to a memory of a computer also including a processor and application code configured to perform a specified user-management operation. In response to the identification, a filter including an application programming interface (API) is configured by associating the identified application code with the API. The filter is deployed to the memory, and the filter registering is registered by the processor to the software application. Finally, in response to the registered filter receiving, via the API, a request to perform the specified user-management operation, the registered filter calls the associated application code so as to perform the requested user-management operation.

## Claims

### Claim 1

A method, comprising:
identifying, in a software application loaded to a memory of a computer also comprising a processor and application code configured to perform a specified user-management operation;
configuring, in response to the identification, a filter comprising an application programming interface (API) by associating the identified application code with the API;
deploying the filter to the memory;
registering, by the processor, the filter to the software application;
receiving, by the registered filter via the API, a request to perform the specified user-management operation; and
calling, by the registered filter in response to the API receiving the request, the associated application code so as to perform the requested user-management operation.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the API in the registered filter comprises a filter API, wherein the application code comprises one or more application APIs, and wherein identifying the application code comprises identifying a given application API.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the function comprises a first function in the application code, and wherein identifying the application code comprises identifying a second function in the application code.

### Claim 4 (depends on 1)

The method according to claim 1, wherein registering the filter comprises deploying, to the memory, a hooked version of a function in the software application, the hooked version configured to register the filter to the software application, and wherein registering the filter comprises the processor calling the hooked version of the function.

### Claim 5 (depends on 4)

The method according to claim 4, and further comprising identifying, prior to deploying the hooked version of the function, the function, and injecting, by the processor into the function, additional application code configured to register the filter to the software application.

### Claim 6 (depends on 1)

The method according to claim 1, wherein identifying the application code comprises identifying a set of terms that describe the user-management operation, detecting, in the software application, application code comprising any of the identified terms, and prompting a large language model (LLM) Analysis to identify, based on the detected application code, the application code configured to perform the specified user-management operation.

### Claim 7 (depends on 6)

The method according to claim 6, wherein identifying the set of terms comprises prompting the LLM to identify, based on the specified user-management operation, the set of terms.

### Claim 8 (depends on 1)

The method according to claim 1, wherein identifying the set of terms comprises applying a Term Frequency-Inverse Document Frequency (TF-IDF) to a description of the specified user-management operation.

### Claim 9 (depends on 1)

The method according to claim 1, wherein identifying the application code comprises performing a static analysis on the software application.

### Claim 10 (depends on 1)

The method according to claim 1, wherein identifying the application code comprises performing a dynamic analysis on the software application.

### Claim 11 (depends on 1)

The method according to claim 1, wherein identifying the application code comprises performing a guided analysis on the software application.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the software application is configured to access a database, and further comprising upon failing to identify the application code configured to perform the specified user-management operation, performing a schema analysis on the database, generating, by the processor in response to the schema analysis, code configured to perform the user-management operation, injecting, by the processor, the generated code into the filter, and associating the injected code with the API.

### Claim 13 (depends on 1)

The method according to claim 1, wherein receiving the request comprises the API in the registered filter receiving a call from an Identity Governance and Administration (IGA) system.

### Claim 14 (depends on 13)

The method according to claim 13, wherein the IGA system conveys the call in a first format, wherein the identified application code is configured to receive the call in a second format, wherein configuring the filter comprises generating, in the filter, a transformation configured to transform the call from the first format to the second format, and wherein calling the associated application code comprises the registered filter applying the transformation to the received call so as to transform the call from the first format to the second format.

### Claim 15 (depends on 13)

The method according to claim 13, and further comprising, receiving, in response to calling the application code, a response from the application code, the response comprising a first format, wherein the IGA system is configured to receive the response in a second format, wherein configuring the filter comprises generating, in the filter, a transformation configured to transform the response from the first format to the second format, and applying, by the registered filter, the transformation to the received response so as to transform the response from the first format to the second format, and conveying the transformed response to the IGA system.

### Claim 16 (depends on 13)

The method according to claim 13, wherein the API in the registered filter comprises a filter API, wherein the IGA system comprises an IGA API, and wherein configuring the filter comprises configuring, via the IGA API, the IGA system to call the filter API so as to request the specified user-management operation.

### Claim 17 (depends on 13)

The method according to claim 13, wherein the IGA system comprises a plugin, and wherein configuring the filter comprises configuring, via the plugin, the IGA system to call the filter API so as to request the specified user-management operation.

### Claim 18 (depends on 1)

The method according to claim 1, wherein the application comprises a web-based application.

### Claim 19 (depends on 1)

The method according to claim 1, wherein the application comprises a remote procedure call (RPC) application.

### Claim 20

An apparatus, comprising:
a memory; and
a processor configured:
to load a software application to the memory,
to identify, in the loaded software application, application code configured to perform a specified user-management operation,
to configure, in response to the identification, a filter comprising an application programming interface (API) by associating the identified application code with the API,
to deploy the filter to the memory,
to register the filter to the software application,
to receive, by the registered filter via the API, a request to perform the specified user-management operation, and
to call, by the registered filter in response to the API receiving the request, the associated application code so as to perform the requested user-management operation.

### Claim 21

A computer software product, the product comprising a non-transitory computer-readable medium, in which program instructions are stored, which instructions, when read by a computer, cause the computer:
to identify, in a software application loaded to a memory of a computer also comprising a processor and application code configured to perform a specified user-management operation;
to configure, in response to the identification, a filter comprising an application programming interface (API) by associating the identified application code with the API;
to deploy the filter to the memory;
to register the filter to the software application;
to receive, by the registered filter via the API, a request to perform the specified user-management operation; and
to call, by the registered filter in response to the API receiving the request, the associated application code so as to perform the requested user-management operation.
