API Lifecycle Security Measures for Adaptive Data Protection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

APIs are prime targets for cyber attackers, leading to an exponential rise in API-related attacks and data leakage due to inadequate security measures across the API lifecycle phases.

Innovation Solution

An API security management method and platform that obtains security information of target data resources, determines security measures for various lifecycle phases, and adjusts measures based on check results to enhance security and reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If comprehensive security measures are implemented across all API lifecycle phases, then data security and reliability are improved, but system complexity and implementation cost increase

Engineering Contradiction:
Improvedata securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments security management into distinct lifecycle phases (design, development, test, registration, running) with phase-specific security measures. Each phase has tailored security requirements and check items, allowing comprehensive security without overwhelming system complexity. For example, the design phase focuses on security classification and requirement analysis, while the running phase emphasizes monitoring and anomaly detection.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary security actions in early lifecycle phases before data leakage can occur. Security measures are proactively applied during design and development phases, including security requirement analysis, security design, and code security checks, rather than reacting to threats after they materialize. This prevents security issues from propagating to later stages.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If strict security measures are applied throughout the API lifecycle, then data leakage is reduced, but development efficiency and productivity decrease

Engineering Contradiction:
Improvedata securityVSAvoiddevelopment efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies different security measure intensities to different lifecycle phases and data sensitivity levels. High-security measures are concentrated in critical phases like data access control and transmission encryption, while less critical phases use streamlined checks. This localized approach maintains security effectiveness without uniformly burdening the entire development process.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent incorporates feedback mechanisms where security check results from one phase inform and adjust security measures in subsequent phases. Security issues identified in development phase feedback into the test phase for verification, and running phase monitoring feedback adjusts security policies. This continuous feedback loop improves security while avoiding redundant checks that would harm productivity.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If security measures are adjusted dynamically based on check results, then security adaptability improves, but management complexity increases

Engineering Contradiction:
Improvesecurity adaptabilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic security measure adjustment where security requirements and check items are not fixed but adapt based on lifecycle phase transitions and check results. For instance, security measures evolve from design-phase theoretical requirements to development-phase implementation checks to running-phase operational monitoring. This dynamic adaptation improves security responsiveness while following structured phase transitions that manage complexity.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20260023862A1Application programming interface security management method and API management platform
Publication Date: 2026.01.22 HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
  • US20260023862A1 patent drawing
  • US20260023862A1 patent drawing
  • US20260023862A1 patent drawing

AI summary

An approach described includes: obtaining security information of a target data resource to be accessed through a target API; determining, based on the security information of the target data resource, a security measure, for the target data resource, corresponding to at least one of a plurality of phases of a target API full lifecycle; taking the corresponding security measure for the target data resource in the part or all of the phases, and obtaining a check result of the security measure corresponding to the part or all of the phases; and taking an adjusted security measure for the target data resource in a second phase based on a check result of a security measure in a first phase, to perform security detection or security protection on the target data resource in the second phase.