# US 2026/0093830 A1 · Application programming interface (api) based network security using zero trust api access (ztaa) with security posture tags

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

- Number: US 2026/0093830 A1
- Document ID: US20260093830A1
- Status: Published application
- Kind: A1
- Application number: 18/921,335
- Filed: 2024-10-21
- Published: 2026-04-02
- Earliest claimed: 2024-09-30
- Assignees: Fortinet, Inc.
- Applicants: Fortinet, Inc.
- Inventors: Julian H. Benavides
- Web page: https://patentgrep.com/patent/US20260093830A1

## CPC

- G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Responsive to the Application Programming Interface (API) consumption request, a security posture tag for to the specific API is calculated by a Zero Trust API Access (ZTAA) server and/or one or more agents running as daemons on one or more API network resources. The daemons can test the API network resources with API calls to generate initial security posture tags. Then the initial security posture tags are dynamically updated responsive to changes on the API network resources. API security rules relevant to the security posture tag of the API. Consumption of the API for allowed or denied per the API consumption request, according to the API consumption rate in view of API security rules associated with the API.

## Claims

### Claim 1

A computer-implemented method in an Application Programming Interface (API) server device, on a data communication network, for providing zero trust API access (ZTAA) based on security posture tags associated with APIs, the method comprising:
tracking API consumption rates associated with a plurality of APIs that are requested for consumption from network resources;
receiving a request to consume a specific API, wherein the API consumption request is associated with a validated API key for a specific API of a plurality of APIs;
responsive to the API consumption request, calculating a security posture tag for to the specific API by one or more agents running as daemons on one or more API network resources, wherein the daemons test the API network resources with API calls to generate initial security posture tags, and wherein the initial security posture tags are dynamically updated responsive to changes on the API network resources;
identifying API security rules relevant to the security posture tag of the API; and
allowing or denying access to the API for consumption per the API consumption request according to the API consumption rate in view of API security rules associated with the API.

### Claim 2 (depends on 1)

The method of claim 1, wherein the consumption rate of the specific API is based on activity for more than one API resource device.

### Claim 3 (depends on 1)

The method of claim 1, wherein the consumption rate of the specific API is based on activity for a specific API resource device of the plurality of API network resources.

### Claim 4 (depends on 1)

The method of claim 1, wherein the information for the security posture updates are initiated by plurality of security agents upon identifying an internal operation relevant to network security.

### Claim 5 (depends on 1)

The method of claim 1, wherein the ZTAA security posture tags are stored separately from corresponding data files.

### Claim 6 (depends on 1)

The method of claim 1, wherein the request is allowed by the data access policies and not allowed by the network access policies.

### Claim 7 (depends on 1)

The method of claim 1, wherein the API consumption request is received over a Virtual Private Network (VPN) security layer, subject to a VPN policy.

### Claim 8 (depends on 1)

The method of claim 1, wherein the API consumption request has been approved for the API service over a Zero Trust Network Access (ZTNA) security layer, subject to a ZTNA policy.

### Claim 9 (depends on 1)

The method of claim 1, wherein the API consumption request has been allowed to access a data file relevant to the API consumption request over a Zero Trust Data Access (ZTDA) security layer, subject to a ZTDA policy.

### Claim 10 (depends on 1)

The method of claim 1, wherein the API consumption request comprises the validated API key as permission for use of the specific API, subject to a ZTDA security layer.

### Claim 11 (depends on 1)

The method of claim 1, wherein the API consumption request clears VPN, ZTNA and ZTDA security layers, but is denied access to the specific API due to the consumption rate.

### Claim 12 (depends on 11)

The method of claim 11, wherein the consumption rate for the specific API is based on consumption at different local area networks (LANs).

### Claim 13 (depends on 11)

The method of claim 11, wherein the consumption rate for the specific API is based on consumption at different API network resources.

### Claim 14 (depends on 1)

The method of claim 1, wherein the consumption rate comprises utilization for a group of APIs, including the specific API.

### Claim 15 (depends on 1)

The method of claim 1, wherein the consumption rate comprises a specific pattern of APIs that are indicative of malicious activity, including the specific API.

### Claim 16

A non-transitory computer-readable medium in an Application Programming Interface (API) server device, on a data communication network, for providing zero trust API access (ZTAA) based on security posture tags associated with APIs, the method comprising:
tracking API consumption rates associated with a plurality of APIs that are requested for consumption from network resources;
receiving a request to consume a specific API, wherein the API consumption request is associated with a validated API key for a specific API of a plurality of APIs;
responsive to the API consumption request, calculating a security posture tag for to the specific API by one or more agents running as daemons on one or more API network resources, wherein the daemons test the API network resources with API calls to generate initial security posture tags, and wherein the initial security posture tags are dynamically updated responsive to changes on the API network resources;
identifying API security rules relevant to the security posture tag of the API; and
allowing or denying access to the API for consumption per the API consumption request according to the API consumption rate in view of API security rules associated with the API.

### Claim 17

An Application Programming Interface (API) server device, on a data communication network, for, on a data communication network, for providing zero trust API access (ZTAA) based on security posture tags associated with APIs, the API server device comprising:
a processor;
a network interface communicatively coupled to the processor and to a data communication network; and
a memory, communicatively coupled to the processor and storing:
a security posture tag module to
tracking API consumption rates associated with a plurality of APIs that are requested for consumption from network resources;
receiving a request to consume a specific API, wherein the API consumption request is associated with a validated API key for a specific API of a plurality of APIs;
responsive to the API consumption request, calculating a security posture tag for to the specific API by one or more agents running as daemons on one or more API network resources, wherein the daemons test the API network resources with API calls to generate initial security posture tags, and wherein the initial security posture tags are dynamically updated responsive to changes on the API network resources;
identifying API security rules relevant to the security posture tag of the API; and
allowing or denying access to the API for consumption per the API consumption request according to the API consumption rate in view of API security rules associated with the API.
