WAAP / API level management security system and method based on block chain

Abstract

The present disclosure provides a blockchain-based security system and method that endows a life cycle to an application programming interface (API) at a cloud-based integrated network security scheme (WAAP), manages a WAAP / API level, and thus can defend various attacks against public or private networks. The security method comprises the following steps: receiving an API security level confirmation request from a block chain under the condition of establishing a session with the block chain; confirming an API security level; and transmitting confirmation information about the API security level to the block chain.

Description

Technical Field

[0001] This disclosure relates to a blockchain-based security system and method that, in an integrated network security solution through cloud-based web application and API protection (WAAP), assigns a life cycle to the application programming interface (API) and manages the WAAP / API level, thereby defending against various attacks against public or private networks. Background Technology

[0002] Recently, social and economic activities conducted through the internet and other networks have become very active. Therefore, the importance of security in application programming interfaces (APIs), which are commonly used for communication between networked terminals, is increasing.

[0003] An API is a collection of definitions and protocols used to build and integrate application software. When using APIs, clients, servers, and other endpoints can communicate with each other without needing to build a connection infrastructure. For example, in API communication, a client can send a key value used to access data to the server, and if the key value is correct, the server can send the data to the client.

[0004] Furthermore, as the use of APIs continues to expand, so too are the number of hacker attacks and security incidents targeting personal data such as credit information, login information, and public data such as weather, public transportation information, and medical information. For example, security incidents caused by API attacks are on the rise, such as obtaining information by compromising user authentication or keys, deliberately allocating excessive system resources, or stealing response data midway through the process.

[0005] To prevent such security incidents, individuals and businesses need to implement security solutions for their networks connected to the internet, but implementing such single-function solutions is very costly. Therefore, considering factors such as cost, the demand for integrated network security solutions that can comprehensively protect the network environment is increasing.

[0006] In particular, recent integrated network security solutions are evolving beyond existing firewall functionality, moving towards integrated solutions that also include API protection, bot mitigation, and distributed denial-of-service (DDoS) defense. Against this backdrop, the demand for integrated network security solutions with API security features that meet OWASP's top 10 API security standards is increasing. Summary of the Invention

[0007] Technical issues This disclosure was made to meet the needs of the aforementioned prior art. The purpose of this disclosure is to provide an integrated network security solution that combines the functions of an existing network firewall with the security functions of an application programming interface (API).

[0008] That is, the purpose of this disclosure is to provide an API reliability assurance security system and method, which utilizes the technology of generating API lifecycle and constituting the web application and API protection (WAAP) ecosystem and blockchain integrity assurance technology, wherein the API lifecycle utilizes the distributed synchronization technology of blockchain.

[0009] Another objective of this disclosure is to provide a security system and method that integrates cybersecurity solutions and blockchain technology, forming a management ecosystem not only for APIs as security objects but also for WAAP itself as an integrated cybersecurity solution, thereby ensuring the reliability of the security solution.

[0010] That is, another objective of this disclosure is to provide a security system and method based on WAAP object verification and management technology that utilizes distributed synchronization technology, which is an inherent feature of blockchain.

[0011] Solution to the problem The security method of this disclosure for solving the above-mentioned technical problems is implemented by an integrated network security scheme (web application and API protection, WAAP) and utilizes a blockchain-based security method managed by WAAP and application programming interface (API) levels, comprising the following steps: when a session is established between WAAP and the blockchain, receiving a Level 1 WAAP confirmation request for API security level from the blockchain; confirming the API security level; and transmitting information about the API security level to the blockchain.

[0012] The steps to confirm the security level of the above APIs include: independently verifying the security level of the above API vulnerabilities within the management API data of WAAP with the highest security level (e.g., level 1).

[0013] The aforementioned WAAP may have a security level representing the highest level of security among WAAPs (e.g., level 1). The aforementioned blockchain may store the WAAP identification information of the aforementioned WAAP and a list of APIs registered in the aforementioned WAAP with the highest security level (e.g., security level 1). This may refer to synchronizing the corresponding WAAP and the blockchain with the list of APIs with the highest security level (e.g., security level 1) as the object.

[0014] The aforementioned security method may further include the following step: receiving WAAP vulnerability testing API sample code from the aforementioned blockchain. The aforementioned API sample code is malicious sample code.

[0015] The above security method may also include the following steps: calculating the security level of the API sample code used for the above WAAP vulnerability testing.

[0016] The aforementioned security method may further include the following steps: transmitting information about the API security level status, including the calculated security level, to the aforementioned blockchain.

[0017] Based on information about the security level status of the aforementioned API, the blockchain can calculate the security level of the API sample code used for the WAAP vulnerability test. If the WAAP is classified as the highest level, it is a vulnerable WAAP, and its level is downgraded.

[0018] Based on information about the security level status of the aforementioned API, the blockchain can calculate the security level of the API sample code used for the WAAP vulnerability test, classify it as a stable WAAP (the lowest level), and upgrade its level accordingly.

[0019] The aforementioned security method may further include the following steps: requesting the aforementioned WAAP to be tested from the aforementioned blockchain; receiving an API sample code security level confirmation request from the aforementioned blockchain; and transmitting API security level status information, including confirmation information about the aforementioned API security level, to the aforementioned blockchain.

[0020] Another aspect of the security method disclosed herein for addressing the aforementioned technical problems is a blockchain-based security method implemented through an integrated network security scheme (web application and API protection, WAAP) and managed at the WAAP and application programming interface (API) levels. This method includes the following steps: requesting a WAAP test from the blockchain via a session established between the blockchain and WAAP; receiving an API sample code security level confirmation request from the blockchain; performing vulnerability testing on the API sample code received from the blockchain; calculating the API security level after performing the vulnerability testing; and transmitting API security level status information, including confirmation information regarding the API security level, to the blockchain.

[0021] The aforementioned API security level status information includes the results of performing vulnerability tests and calculating the security level on the API sample code received by WAAP from the blockchain.

[0022] Before requesting testing of the WAAP, the above security method may also include the following steps: upgrading the functionality of the WAAP with administrator privileges.

[0023] The aforementioned blockchain can, based on information about the security level status of the aforementioned API, calculate the security level of the API sample code used for the aforementioned WAAP vulnerability test and classify it as a WAAP with the highest security level, then downgrade its level; or the aforementioned blockchain can, based on information about the security level status of the aforementioned API, calculate the security level of the API sample code used for the aforementioned WAAP vulnerability test and classify it as a WAAP with the lowest security level, then upgrade its level.

[0024] After performing the step of adjusting the WAAP level with administrator privileges based on the WAAP test results, the above security method may further include the following step: re-requesting the WAAP level test used to upgrade the WAAP level from the above blockchain, so as to restore the WAAP level downgraded with the administrator privileges of the above WAAP.

[0025] The aforementioned blockchain can, based on the API security level calculation results of the re-requested WAAP according to the aforementioned WAAP level test, classify the WAAP with the highest security level calculated using the API sample code of the aforementioned WAAP vulnerability test as a vulnerable WAAP and downgrade its level; or the aforementioned blockchain can, based on information about the security level status of the aforementioned API, classify the WAAP with the lowest security level calculated using the API sample code of the aforementioned WAAP vulnerability test as a stable WAAP and upgrade its level.

[0026] Another aspect of the security system disclosed herein, used to address the aforementioned technical problems, is a blockchain-based security system utilizing integrated web application and API protection (WAAP) and application programming interface (API) level management. This system includes: a memory; and at least one processor connected to the memory to execute a program comprising at least one instruction. Through the at least one instruction, when establishing a session with the blockchain, the WAAP receives an API security level confirmation request from the blockchain, confirms the API security level, and transmits confirmation information regarding the API security level to the blockchain.

[0027] The aforementioned WAAP can have a security level of 1, representing the most secure WAAP. The aforementioned blockchain can store the WAAP's WAAP identification information and a list of security level 1 APIs registered in the aforementioned WAAP. Therefore, the aforementioned blockchain can synchronize with the corresponding WAAP, using the list of APIs with the highest security level as its target.

[0028] The processor can also perform the following: receiving WAAP vulnerability testing API sample code from the blockchain, calculating the security level of the WAAP vulnerability testing API sample code, and transmitting information about the API security level status, including the calculated security level, to the blockchain.

[0029] Based on information about the security level status of the aforementioned API, the blockchain can calculate the security level of the API sample code used for WAAP vulnerability testing. If the security level is the highest level, it can classify the WAAP as a vulnerable WAAP and downgrade its level. Conversely, based on the same information, the blockchain can also calculate the security level of the API sample code used for WAAP vulnerability testing. If the security level is the lowest level, it can classify the WAAP as a stable WAAP and upgrade its level.

[0030] The processor may also perform the following: requesting the blockchain to test the WAAP, receiving an API sample code security level confirmation request from the blockchain, and transmitting API security level status information, including confirmation information about the API security level, to the blockchain.

[0031] After adjusting the WAAP level based on the WAAP test results, the processor can still perform the self-update of the WAAP with the administrator privileges of the WAAP before requesting a test of the WAAP level to restore the level.

[0032] Before requesting the blockchain to test the WAAP or requesting a retest of the WAAP level due to a downgrade adjustment based on previous test results, the processor can also perform the function of automatically upgrading the WAAP with the administrator privileges of the WAAP.

[0033] The effects of the invention According to this disclosure, by constructing an API management system based on "distributed synchronization" technology, an inherent feature of blockchain, and a WAAP management system, which is an integrated network security solution, advantages can be gained in API security. Furthermore, by ensuring API reliability through "integrity assurance" technology, another inherent feature of blockchain, technical issues related to enabling users to use secure APIs can be resolved.

[0034] Furthermore, according to this disclosure, the blockchain-based WAAP / API level management integrated security system can be roughly divided into three parts: "API management effect", "WAAP management effect", and "authentication API usage effect" utilizing blockchain technology.

[0035] Specifically, blockchain-based "API management" refers to WAAP calculating API levels from the most secure Level 1 to the most vulnerable Level 3, and then recording and managing these levels and other API information on the blockchain. Based on this blockchain-based "API management" technology, API security levels and information can be shared among all nodes within the blockchain network. This demonstrates the information sharing management effect of blockchain-based distributed storage technology, ensuring that the security levels and other information of the corresponding APIs registered in the blockchain cannot be tampered with, thus providing a reliable API management effect based on blockchain-based data integrity assurance technology.

[0036] Furthermore, "WAAP management" utilizing blockchain technology refers to the technique of conducting WAAP functional tests on all WAAPs linked in the blockchain network to calculate WAAP levels ranging from the most stable level 1 to the least stable level 3. This involves recording and managing the WAAP IDs and levels of the tested objects on the blockchain. This technology leverages the inherent "distributed synchronization" characteristic of blockchain, enabling the following process: WAAP functional test sample code is recorded on the blockchain and propagated to all interconnected WAAPs, followed by confirmation of the response value. Based on this blockchain-based "WAAP management" technology, the management effectiveness of continuously updating and upgrading WAAPs as an API verification scheme can be derived, ultimately improving user reliability and thus enhancing user satisfaction through WAAP management.

[0037] As described above, according to this disclosure, by utilizing the characteristics of blockchain technology, namely "distributed synchronization of data" and "integrity protection against data tampering," the integrated security solution systematically performs the functions of "API management" and "WAAP management," ultimately ensuring secure and authenticated API usage for users. That is, according to this disclosure, "authenticated API usage effects" can be provided.

[0038] Furthermore, the inherent advantage of the security technology disclosed herein lies in its dynamic formulation of API and WAAP management policies, rather than their static formulation. This is achieved by using a blockchain-based integrated network security solution to imbue API and WAAP management with a "life cycle," rather than statically formulating API and WAAP management policies on each device. Based on this structure, an integrated network security solution with the capability to protect the overall network environment can be provided. That is, in addition to network security, it can provide web application and API protection (WAAP) with additional functions such as API protection, bot mitigation, and distributed denial-of-service (DDoS) defense.

[0039] Furthermore, according to this disclosure, WAAP can not only effectively manage API security, but also effectively manage the overall infrastructure and network services. Attached Figure Description

[0040] Figure 1 This is an illustrative diagram used to illustrate application programming interface (API) communication that can be used in a method of one embodiment of the present invention.

[0041] Figure 2 This is a simplified schematic diagram of a WAAP-based security system for client API security according to an embodiment of the present invention.

[0042] Figure 3 For illustrative purposes Figure 2 An example diagram illustrating the main features of WAAP.

[0043] Figure 4 This is an illustrative diagram used to illustrate the API lifecycle that can be used in a security method according to an embodiment of the present invention.

[0044] Figure 5 This is a flowchart illustrating the API blockchain registration confirmation and registration process that can be used in a security method that can be employed in an embodiment of this disclosure.

[0045] Figure 6 This is a flowchart illustrating a WAAP vulnerability discovery and update process that can be used in a security method that may be employed in an embodiment of this disclosure.

[0046] Figure 7 This is a flowchart illustrating the WAAP update level restoration and re-rating request process that can be used in a security method of one embodiment of the present invention.

[0047] Figure 8 A simplified block diagram illustrating the security system configuration according to another embodiment of the present invention.

[0048] Figure 9 For can Figure 8 A simplified block diagram of the main WAAP configuration used in the security system.

[0049] Figure 10 For can Figure 8 A simplified block diagram of the main WAAP configurations in the administrator mode used in the security system.

[0050] Figure 11 This is a block diagram illustrating a software module that may be used in a security system according to another embodiment of this disclosure. Detailed Implementation

[0051] This invention can be modified in many ways and can have many embodiments. Specific embodiments are shown in the accompanying drawings and described in detail. However, this is not to limit the invention to the specific implementation, but should be understood to include all changes, equivalent technical solutions, or alternative technical solutions included in the concept and technical scope of the invention.

[0052] The terms "first," "second," etc., can be used to describe various constituent elements, but the constituent elements described above are not limited to these terms. These terms are only used to distinguish one constituent element from another. For example, without departing from the scope of this invention, a first constituent element may be named a second constituent element, and correspondingly, a second constituent element may be named a first constituent element. The term "and / or" includes a combination of multiple related descriptions or one of multiple related descriptions.

[0053] In embodiments of this application, "at least one of A and B" can refer to "at least one of A or B" or "at least one of a combination of more than one of A and B". Furthermore, in embodiments of this application, "more than one of A and B" can refer to "more than one of A or B" or "more than one of a combination of more than one of A and B".

[0054] When a constituent element is referred to as "connected" or "linked" to another constituent element, it should be understood as being directly connected or linked to the other constituent element, and that other constituent elements may exist in between. Conversely, when a constituent element is referred to as "directly connected" or "directly linked" to another constituent element, it should be understood as not having other constituent elements in between.

[0055] The terminology used in this application is for illustrative purposes only and does not limit the invention. Unless otherwise defined in the context, singular expressions include plural expressions. It should be understood in this application that terms such as "comprising" or "having" are used to specify the presence of features, numbers, steps, actions, components, parts, or combinations thereof as described in the specification, and not to preclude the presence or additional possibilities of more than one other feature or number, step, action, component, part, or combination thereof.

[0056] Unless otherwise defined, the terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Terms as defined by commonly used dictionaries should be interpreted as having the same meaning as they have in the context of the relevant art, and should not be interpreted as having an ideal or overly formal meaning unless expressly defined in this application.

[0057] Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the accompanying drawings. When describing the present invention, for ease of overall understanding, the same reference numerals will be used for the same constituent elements in the drawings, and repeated descriptions of the same constituent elements will be omitted.

[0058] Figure 1This is an illustrative diagram used to illustrate application programming interface (API) communication that can be used in a method of one embodiment of the present invention.

[0059] Reference Figure 1 In API communication, client 10 sets up an access session with server 100 and passes a key value used to access specific data to server 100. If the key value is correct, server 100 can pass data to client 10.

[0060] Furthermore, various attacks can be launched through malicious users such as hackers during the aforementioned API communication. The main API attack vulnerabilities in API communication are as follows.

[0061] First, client 10 may transmit an API key that does not conform to the specified format to server 100. In this case, if the server 100 does not perform a proper verification process, various problems may occur. Specifically, vulnerabilities such as API format ignoring and null character insertion attacks may occur. "API format ignoring" refers to a situation where, although API keys are required to follow a specific format (length, character combinations, etc.), server 100 fails to properly verify them, resulting in arbitrary data being registered as an API key. Furthermore, "null character insertion attacks" refer to a situation where server 100 fails to correctly handle null characters during API verification, allowing attackers to transmit keys containing null characters and bypass the key verification logic.

[0062] Furthermore, client 10 may possess a hard-coded API key. Hard-coded encryption keys are stored directly within the source code, posing a risk of leakage along with the source code, and also presenting a security vulnerability as the key cannot be easily changed based on environmental changes. In other words, if a hard-coded encryption key is used within the source code, it is vulnerable to brute-forde attacks, and some hash functions hard-coded in constant format can be reverse-engineered, potentially leading to the leakage of encrypted information.

[0063] Furthermore, there is a vulnerability that may include an API format defect in server 100. The API format may include the API message format, which can use UTF-8 encoding in JavaScript Object Notation (JSON) format. JSON can refer to an open standard message format that represents data objects as attributes and values, i.e., key-value (key:value) format, for sending or receiving small messages. Moreover, UTF-8 refers to a standard encoding method that represents all global character codes by extending the American Standard Code for Information Interchange (ASCII). During API communication, if server 100 cannot properly handle the corresponding UTF-8 encoding, a security vulnerability may occur due to corrupted characters. A "corrupted character vulnerability" refers to a vulnerability where, if client 10 transmits data using incorrect UTF-8 encoding, causing server 100 to be unable to process the data correctly and resulting in data corruption, the corrupted characters may disrupt the system and potentially lead to buffer overflow attacks.

[0064] Furthermore, during the API call process where client 10 passes the API key value to server 100 in order to receive data from server 100, a man-in-the-middle attack (MITM) may occur from a spoofed server or a spoofed client, resulting in ransomware attacks via Address Resolution Protocol (ARP), spoofing, or Domain Name System (DNS) deception. In other words, ransomware attacks can occur during the API call process where a client passes the API key value to the server in order to receive data from the server.

[0065] To defend against attacks that occur under the aforementioned major API vulnerabilities, it is advisable to store the encryption key encrypted in external space or a file. Furthermore, it is advisable to manage the encryption key, for example, using a seed extracted from a random function and encryption code generated based on an initialization vector. As the random function, an enhanced security random function can be used, for example, obtained by generating cryptographically secure arbitrary numbers using the .NET RNGCryptoServiceProvider class.

[0066] However, the aforementioned API protection schemes are implemented in API communications within a network environment. Therefore, security vulnerabilities occurring in a network environment may be similar to API vulnerabilities.

[0067] For example, the top 10 OWASP cybersecurity projects are shown in Table 1 below.

[0068] Table 1 serial number OWASP Top 10 Network Application Security (2023) A01 Broken Access Control A02 Cryptographic failures A03 Injection attack A04 Insecure Design A05 Security misconfiguration. A06 Vulnerable and outdated components A07 Identification and Authentication Failures A08 Software and data integrity failures A09 Security Logging and Monitoring Failures A10 Server-Side Request Forgery (SSRF) In addition, the top 10 OWASP API security items and their descriptions are shown in Table 2 below.

[0069] Table 2 serial number Top 10 OWASP API Security Rankings (2023) Security Risk Statement 1 Broken ObjectLevel Authorization If an endpoint that handles object identifiers is exposed in an API, an attack surface for object access control occurs. 2 BrokenAuthentication has failed. If the authentication mechanism is not properly implemented, attackers can extort authentication tokens or steal other users' identities. 3 Broken Object Property Level Authorization This could lead to the unauthorized party leaking or manipulating information. 4 Unrestricted Resource Combustion Processing API requests requires resources such as network bandwidth, CPU, memory, and storage devices. In particular, APIs for email / SMS / telephone / biometric authentication are charged per request by the service provider; therefore, a successful DoS attack would significantly increase operating costs. 5 Function-level authorization broken. The lack of clarity in the distinction between complex access control policies and management based on different levels, groups, and roles, as well as general functions, may lead to authentication vulnerabilities. 6 Unrestricted Access to Sensitive Business Flows The API with this vulnerability risks exposing business processes, and excessive access in an automated manner could lead to losses. 7 Server-Side Request Forgery (SSRF) SSRF vulnerabilities occur when an API fails to check the validity of a user-provided URI and grants access to a remote resource. Even when protected by a firewall or Virtual Private Network (VPN), an attacker can send requests from an application targeting an unintended objective. 8 Security misconfiguration. For complex configurations that support the use of custom APIs, various types of attacks can occur if DevOps engineers miss security configurations or fail to follow best practices. 9 Improper API Improper Inventory Management An API manifest is a complete list of APIs used throughout an organization or software. APIs are exposed to more endpoints than typical web applications, therefore, it is necessary to keep the API manifest up-to-date. 10 Unsafe use of APIs Developers tend to trust data received from third-party APIs more than user input, and therefore tend to adopt weaker security standards. Attackers can exploit this to compromise third-party services rather than directly attacking the target API.

[0070] Taking similar security vulnerabilities and API vulnerabilities occurring in the network environment as examples, items A03, A05, and A09 in the OWASP Top 10 Network Security vulnerabilities shown in Table 1 are the same as items A07, A08, and A10 in the OWASP Top 10 API Security vulnerabilities shown in Table 2. Items A01, A07, and A08 in the OWASP Top 10 Network Security vulnerabilities are similar to items A02, A05, and A09 in the OWASP Top 10 API vulnerabilities.

[0071] Figure 2 This is a simplified schematic diagram of a WAAP-based security system for client API security according to an embodiment of the present invention.

[0072] Reference Figure 2 The WAAP-based security system (hereinafter referred to as the "security system") includes WAAP 300, API server 510 and API database (DB) 530.

[0073] WAAP 300 is an integrated network security solution configured to perform web application security and API security. WAAP 300 can include service providers and hash verification tools. Furthermore, WAAP 300 can be configured with a network firewall (WAF), API security, bot mitigation, and DDoS protection capabilities. For this type of WAAP 300, see the reference... Figure 3 The details of these are specifically mentioned below, therefore, to avoid repetition, a detailed description of them is omitted here.

[0074] API server 510 can refer to a server in API communication that responds to API requests. This API server 510 can refer to a service API server on a client's private network or intranet.

[0075] API DB 530 can refer to an off-chain database (DB) that stores and manages APIs. This API DB530 can also refer to an internal API management database within a client's intranet.

[0076] The aforementioned security system includes WAAP 300 based on cloud-specific service APIs, which can be configured to assign a life cycle to the API via WAAP 300.

[0077] Additionally, the security system can migrate API information from API server 510 to API DB 530 to calculate the security level for the client's intranet and the API. Furthermore, the security system can migrate API information from API server 510 to WAAP 300. Additionally, the security system can store API hash values ​​on WAAP 300 after receiving at least one API tagging API ID from API server 510. Moreover, when a service user outside the client requests verification of the security of an API received from the corresponding client's service server (i.e., API server) through WAAP 300, the security system can verify the security of the corresponding API.

[0078] As described above, the security system in this embodiment assigns a lifecycle to the API, enabling the design of a WAAP ecosystem capable of defending against various attacks. Furthermore, for client API security, the security system can perform client intranet security through the API registration and hash value verification process. Moreover, based on the verification results of the API registration and hash value verification process, the security system calculates the security level for the API and applies these cycles periodically, thereby making the client intranet security more reliable.

[0079] Figure 3 For illustrative purposes Figure 2 An example diagram illustrating the main features of WAAP.

[0080] Reference Figure 3 WAAP 300 is an evolution of the Web Application Firewall (WAF). It can refer to a security solution that, in addition to the basic functions of the Web Application Firewall 310, also has additional network security features. Specifically, WAAP 300 can have four core functions: WAF 310, API protection 320, bot mitigation 330, and DDoS protection 340.

[0081] To elaborate on the specific functions, WAF (Web Application Firewall) functions can include detecting and blocking network attacks such as Structured Query Language (SQL) injection and cross-site scripting (XSS). WAF functions monitor all HTTP / HTTPS traffic transmitted to the web server or inspect the user URLs in request packets to prevent the transmission of unexpected content to web applications. Furthermore, WAF functions monitor the content of HTTP response packets passing through the web server using proxy server principles, thereby preventing the leakage of specific information.

[0082] API protection can refer to protecting APIs from misuse, malicious bot attacks, and other cybersecurity threats. In particular, API protection can be expanded as API security evolves. That is, with the emergence of microservices architectures leveraging Internet of Things (IoT) and cloud-native technologies, APIs have expanded to enable seamless communication and call routing between applications and throughout the DevOps environment. High-quality APIs such as Representational State Transfer (REST) ​​and Simple Object Access Protocol (SOAP) coordinate application integration, specifying data formats and indicating call types, processes, and rules. Furthermore, web APIs such as GraphQL, REST APIs, and SOAP APIs are expanding their functionality across countless complex networks, including a wide range of integration capabilities. Additionally, these latest APIs heavily rely on API endpoints to achieve their functionality; therefore, enterprises and security teams ultimately adopt robust security measures to protect data and network services in order to maximize the use of IT resources. Thus, this embodiment provides a method for giving APIs a lifecycle as one of the robust security measures.

[0083] Bot mitigation functionality may include: when receiving a data request from an external client (where the client is a bot), integrating a network security system to transmit an acknowledgment message for the corresponding request, acknowledging an abnormal response to the acknowledgment message received from the client or a response received from an abnormal IP address, thereby intercepting the client's corresponding request.

[0084] Distributed Denial-of-Service (DDoS) defense capabilities may include: when the number of multiple messages with incomplete requests exceeds a certain number within a unit of time, the integrated network security system detects and intercepts application-layer denial-of-service (DoS) attacks or distributed denial-of-service (DDoS) attacks such as multiple messages with incomplete requests.

[0085] The aforementioned security system can also be configured to automatically identify problems that occur during system operation through self-checking functions and send real-time alerts to the administrator. To this end, the security system can be configured to self-diagnose resource status, network status, and hardware status, identify security risks and other risks, transmit alerts to the administrator, or perform automatic recovery functions based on self-diagnostic items and their set values.

[0086] Figure 4 This is an illustrative diagram used to illustrate the API lifecycle that can be used in a security method according to an embodiment of the present invention.

[0087] Reference Figure 4 The API lifecycle can be configured as a cycle of design, manage, monitor, deploy, and assess.

[0088] Design refers to classifying APIs by calculating their security level.

[0089] Management refers to the registration and management of API-related information and security levels both off-chain (API DB) and on-chain (blockchain) blockchains. On-chain refers to the method of recording all transaction details occurring within the blockchain (On), while off-chain refers to the method of recording transaction details outside the blockchain network (Off).

[0090] Monitoring refers to the process of verifying the integrity and ensuring the continuous visibility of data related to API information and security levels registered in the blockchain.

[0091] Deployment refers to the process of distributing the information and security level data of newly registered APIs on a blockchain network in an on-chain manner.

[0092] Assessment refers to the process of evaluating APIs based on API information and security level data uploaded to the blockchain, in conjunction with clients within the network.

[0093] The network security layer API levels and their characteristics using the aforementioned APIs are shown in Table 3 below.

[0094] Table 3 API Level feature 1 Known vulnerabilities do not exist in the API, which is either problematic or insecure. 2 APIs that have not been re-verified or passed Level 2 WAAP certification for more than 1 year 3 APIs that have been found to have vulnerabilities or have passed Level 3 WAAP authentication Furthermore, the levels and characteristics of web application and API protection (WAAP), which is one of the integrated network security solutions used for the aforementioned API protection and web application security functions, are shown in Table 4 below.

[0095] Table 4 WAAP level feature 1 Firewalls with known vulnerabilities that are not problematic 2 No vulnerabilities were found in the firewall, which has not been updated for more than a year. 3 Firewalls that discover vulnerabilities As described above, API security can be implemented using an integrated network security solution. In particular, the security system of this embodiment can perform basic network firewall (WAF) functions while also enabling bot detection and DDoS protection, and dynamically managing APIs.

[0096] For example, in robot detection and interception, when a data request is received from an external client (where the client is a robot), the integrated network security system transmits an acknowledgment message for the corresponding request. If an abnormal response to the acknowledgment message is received from the client or a response is received from an abnormal IP address, the corresponding request from the client can be intercepted.

[0097] In addition, for DDoS defense, when the number of multiple messages with incomplete requests exceeds a certain number within a unit of time, the integrated network security system detects and intercepts application-layer denial-of-service (DoS) attacks or distributed denial-of-service (DDoS) attacks such as multiple messages with incomplete requests.

[0098] Furthermore, the integrated network security system in this embodiment can be configured to automatically identify problems that occur during system operation using a self-testing function, and transmit information or alarms about the identified problems to the administrator and / or the linked blockchain network in real time.

[0099] To this end, the integrated network security system can self-diagnose resource status, network status, and hardware status, identify security risks and other risks, transmit alerts to administrators and / or the blockchain network, or initiate automatic recovery functions based on self-diagnostic items and their set values.

[0100] Figure 5 This is a flowchart illustrating the API blockchain registration confirmation and registration process that can be used in a security method that can be employed in an embodiment of this disclosure.

[0101] Reference Figure 5Users can perform a TLS handshake process (S510) for the Blackchain blockchain and the transport layer security (TLS) protocol. A TLS handshake can refer to establishing a session for communication between the user and the blockchain.

[0102] Users can include internet-connected user devices, and the blockchain can include a blockchain network consisting of multiple nodes connected via the internet. This blockchain is implemented by storing and comparing web application and API protection (WAAP) identification information, WAAP-level information, and API-level information. For example, the blockchain can be configured to store data or information through smart contracts and compare them. WAAP identification information can be represented by a WAAP ID, and API-level information can include level information regarding API security.

[0103] The WAAP mentioned above is one of the integrated network security solutions evolved from web application firewalls (WAF). As a core feature, it can have basic network firewall functions for network security, API protection functions, bot mitigation functions, and DDoS defense functions as additional network security functions.

[0104] Afterwards, the user can check whether the API has been registered on the blockchain (S520). That is, the user can send a confirmation request message to the blockchain to confirm whether specific API information has been registered on the blockchain.

[0105] Next, the blockchain can determine whether the API requested by the user is registered on the blockchain based on the user's API registration confirmation request (S530). For example, the blockchain can determine whether the following three conditions are met based on the user's API registration confirmation request: that is, the blockchain can judge three conditions, namely, the corresponding API is not registered on the blockchain (non-registration), the corresponding API information is registered on the blockchain, but the registered API has a security level of 3, or even if the corresponding API registered on the blockchain has a security level of 1 or 2, the security level is still calculated, or the WAAP level of the integrated network security solution for the corresponding API is judged to be 3.

[0106] The conditions for confirming whether to register an API on a blockchain for this type of API information are as follows.

[0107] [API registration confirmation request conditions] Based on the above conditions, for cases where "API information is not registered on the blockchain", "the corresponding WAAP information is registered on the blockchain, but the registered API has a security level of 3", or "the security level of the API registered on the blockchain is 1 or 2, but the security level of the WAAP is judged to be 3", level 1 WAAP and API security verification can be performed.

[0108] Next, the blockchain can execute a Level 1 WAAP and TLS handshake process to perform API security verification. That is, the Level 1 WAAP can execute the blockchain and TLS handshake process (S540). This TLS handshake can refer to establishing a session for communication between the blockchain and the Level 1 WAAP. TLS handshake can refer to a security handshake in a broad sense. Furthermore, Level 1 WAAP can refer to a WAAP with security level 1.

[0109] After establishing a session between the blockchain and the Level 1 WAAP, the blockchain can request confirmation of the API security level from the WAAP. That is, the WAAP can receive a request for API security verification from the blockchain (S550).

[0110] API security verification requests may include information about the relevant user, such as user identification information, API identification information, API configuration information, API settings information, API dynamic manifest information, API usage information, etc.

[0111] Next, Level 1 WAAP can execute a pre-defined process based on the blockchain's request, or perform API security verification through a verification module or model that executes such a process, and transmit the verification result regarding the API security status to the blockchain. That is, the blockchain can receive the verification result regarding the API security status from the WAAP (S560). The verification result regarding the API security status may include information such as the API security level.

[0112] Subsequently, the blockchain can store WAAP identification information (ID, e.g., α), WAAP level information (e.g., level 1), and API security level information (e.g., level 1) in block form in a distributed data storage environment. This distributed data storage environment is based on a chain-like connection ring (S570) generated in a peer-to-peer (P2P) manner. The API security level information, stored in the blockchain, may include the ID of the WAAP with security level 1 and a list of APIs registered with the corresponding WAAP at security level 1. Storing this information can refer to the process of synchronizing the API list to the blockchain.

[0113] Next, the blockchain can transmit the API status and WAAP level obtained as verification results regarding API security to the user (S580). That is, the blockchain can introduce API information and WAAP level to the user.

[0114] According to this embodiment, users can request API information from the blockchain and receive information about API status and WAAP level from the blockchain.

[0115] The aforementioned process of requesting API information from the blockchain is essentially the same as the process of requesting the blockchain to reconfirm the API for Level 3 WAAP authentication. Therefore, the aforementioned "process of requesting API information from the blockchain" can be used as a process of re-requesting the API information for Level 3 WAAP authentication from Level 1 WAAP.

[0116] Figure 6 This is a flowchart illustrating a WAAP vulnerability discovery and update process that can be used in a security method that may be employed in an embodiment of this disclosure.

[0117] Reference Figure 6 To perform the WAAP vulnerability discovery and update process, an API vulnerability researcher can establish a session with the blockchain via a TLS handshake process (S610). An API vulnerability researcher may include a user or a user device used by the researcher to discover API vulnerabilities; they can be simply referred to as a researcher or user.

[0118] Once the TLS handshake process is complete, researchers can register the discovered vulnerabilities and corresponding sample code on the blockchain (S620). The sample code may include vulnerability test code, or simply vulnerability testing code.

[0119] Next, if a vulnerability and its sample code are registered, the blockchain can notify all WAAP(s) of the corresponding vulnerability and sample code (S630). Notifications of blockchain vulnerabilities and sample code can be broadcast to all WAAP(s) belonging to the blockchain network. That is, the blockchain can propagate WAAP vulnerability testing API sample code to all WAAP(s). This functionality is one of the inherent functions of the blockchain, such as the "distributed synchronization" function.

[0120] Subsequently, at least one WAAP(s) that received the vulnerability testing API sample code notification can transmit the API security status of the aforementioned WAAP vulnerability testing API sample code to the blockchain (S640). That is, after calculating the security level for the WAAP vulnerability testing API sample code, the WAAP can transmit the response value as the calculation result to the blockchain again.

[0121] Next, the blockchain can determine the API status (S650) by judging whether the security level of all WAAP(s) transmitted as response values ​​for the API sample code is level 1 or level 3. That is, for WAAPs whose security level is calculated as 1 for malicious API sample code used in vulnerability testing, the blockchain classifies the corresponding WAAP as a vulnerable WAAP and adjusts its level to 3. Furthermore, for WAAPs whose security level is calculated as 3 for malicious API sample code used in vulnerability testing, the blockchain classifies the corresponding WAAP as a stable WAAP and updates its level to 1.

[0122] Subsequently, if the security level of the received API vulnerability example code is 1, the blockchain determines that the WAAP that transmits the corresponding level 1 as a response value is vulnerable, sets the security level of the corresponding WAAP to 3, and allows the storage of the corresponding WAAP ID.

[0123] Furthermore, if the security level of the received API vulnerability example code is 3, the blockchain accurately classifies the API example code that is harmful to the WAAP transmitted as a response value at the corresponding level 3 as security level 3. Therefore, the security level of the corresponding WAAP is specified as 1, and the corresponding WAAP ID can be stored. Through the process described above, the blockchain can store information on WAAP ID, WAAP level, and vulnerability update (S660).

[0124] According to this embodiment, the researcher stores the API vulnerability and corresponding sample code on the blockchain. The blockchain receives the API security status from all WAAP(s) in the blockchain network based on the vulnerability and sample code. Based on the API security status received from each WAAP, the API status is confirmed. The WAAP ID, WAAP level and vulnerable WAAP information can be stored according to the confirmed API status, or the WAAP ID, WAAP level and vulnerability update information can be stored.

[0125] Figure 7 This is a flowchart illustrating the WAAP update level restoration and re-rating request process that can be used in a security method of one embodiment of the present invention.

[0126] Reference Figure 7 For WAAP level restoration and re-rating requests, WAAP can perform a self-update process in administrator mode (S710). Administrators can perform updates to upgrade the WAAP's security level with WAAP administrator privileges. Administrator-mode WAAP can refer to WAAP that is being used by an administrator or is operating in administrator mode, such as WAAP being used by a user who has obtained user authentication as an administrator.

[0127] Subsequently, WAAP in administrator mode can perform blockchain and TLS handshake processes for WAAP-level recovery and re-rating requests (S720).

[0128] After establishing a session with the blockchain via TLS handshake, the WAAP can re-request the WAAP level test to restore the WAAP level adjusted by the blockchain propagation vulnerability API sample code test results (S730). Identification information for the tested WAAP can be expressed, for example, by α. For instance, a WAAP that was downgraded in a previous process can re-request the WAAP level test from the blockchain after being updated for level restoration.

[0129] Next, the blockchain can request API sample code security verification from the WAAP. Specifically, the WAAP in administrator mode can receive API sample code security verification requests from the blockchain (S740). API sample code security verification can be performed by the blockchain transmitting malicious API sample code for vulnerability testing to the corresponding WAAP and requesting verification. This API sample code security verification is to determine the stability of the WAAP as an integrated network security solution from the administrator's perspective using registered malicious API sample code for vulnerability testing.

[0130] Subsequently, WAAP can transmit the API security status, verified from the administrator's perspective, to the blockchain (S750). That is, the administrator-mode WAAP defines the security level for malicious API sample code used in WAAP testing and can transmit the verification results, including the API security status, to the blockchain.

[0131] Next, the blockchain confirms the API status (S760) and can store the corresponding WAAP ID, WAAP level, and vulnerability information based on the confirmed API's security level, or store the WAAP ID, WAAP level, and vulnerability update information (S770). That is, if a malicious API used for a specific WAAP transmission test has a security level of 1, the blockchain classifies the corresponding WAAP as a vulnerable WAAP and downgrades its WAAP level to level 3 for storage. Furthermore, if a malicious API used for a specific WAAP transmission test has a security level of 3, the blockchain classifies the corresponding WAAP as a stable WAAP and upgrades its WAAP level to level 1 for storage.

[0132] Figure 8 A simplified block diagram illustrating the security system configuration according to another embodiment of the present invention.

[0133] Reference Figure 8 The security system 800 may include at least one processor 810, a memory 820, and a transceiver 830 connected to a network to perform communication. The at least one processor 810 and memory 820 may be comprised of at least one controller. Furthermore, the transceiver 830 may be equipped with a sub-communication system supporting a wired network or a wireless communication module (WCM) supporting a wireless network.

[0134] In addition, the security system 800 may also include a storage device 840, an input interface device 850, an output interface device 860, etc. The various components included in the security system 800 can be connected to each other via a bus 870 to communicate.

[0135] However, the various components included in the security system 800 are connected via separate interfaces or separate buses centered on the processor 810, rather than via a general-purpose bus. For example, the processor 810 may be connected to at least one of the memory 820, transceiver 830, storage device 840, input interface device 850, and output interface device 860 via a dedicated interface.

[0136] The processor 810 can execute program commands stored in at least one of the memory 820 and the storage device 840. The processor 810 can refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor for executing the security methods of the embodiments of the present invention. The program commands may include at least one instruction for implementing the aforementioned security methods.

[0137] The memory 820 and the storage device 840 may each be composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 820 may be composed of at least one of a read-only memory (ROM) and a random access memory (RAM).

[0138] The aforementioned security system 800 can be implemented by desktop computers, servers, portable terminals, laptops, personal portable communication terminals, etc. Security system 800 can refer to nodes, servers, management systems, service systems, etc., located on wired networks, short-range wireless communication networks, mobile communication networks, satellite networks, or combined networks of these.

[0139] Figure 9 For can Figure 8 A simplified block diagram of the main WAAP configuration used in the security system.

[0140] Reference Figure 9 WAAP 900 is a Level 1 security system that can be configured with a service provider 910 and an authentication tool 950. The service provider 910 can be configured with a handshake processing unit 920, an API security level authentication unit 930, and a notification processing unit 940, all implemented by at least one software module.

[0141] The WAAP 900 in this embodiment can execute the result of confirming the corresponding API information based on the blockchain's confirmation request regarding whether the user has registered for the API.

[0142] To provide a more detailed explanation of the components of WAAP 900, service provider 910 can register the API with authentication tool 950. At this time, authentication tool 950 can store the API, its identifier (ID), and hash. Furthermore, authentication tool 950 can transmit the ID and hash to service provider 910. Additionally, authentication tool 950 can be configured to compare the API's hash value with its own stored hash value.

[0143] Additionally, the handshake processing unit 920, integrated into the service provider 910, can execute a TLS handshake process to establish a session with the blockchain. According to the implementation, the handshake processing unit 920 can execute a secure handshake process to establish a session between the service provider 910 and the verification tool 950.

[0144] The API security level verification unit 930 can receive API security level confirmation requests for Level 1 WAAPs from the blockchain. In this case, the API security level verification unit 930 can transmit API security status information, including the API security level confirmation result, to the blockchain. At this time, the blockchain can receive the identifier of the Level 1 WAAP, the list of security level 1 APIs registered in the WAAP, and store them on the blockchain. This corresponds to the blockchain completing blockchain synchronization with the list of secure APIs as the object.

[0145] Additionally, API vulnerability researchers can register vulnerabilities and sample code on the blockchain. The sample code can include vulnerability testing code. In this case, the blockchain can disseminate the API sample code for WAAP vulnerability testing to all WAAP applications. This is achieved through the blockchain's inherent "distributed synchronization" capability.

[0146] The notification processing unit 940 can receive notifications propagated or broadcast from the blockchain. Notifications may include WAAP vulnerability reports and API sample code for WAAP vulnerability testing. That is, if the notification processing unit 940 receives vulnerabilities and sample code, the API security level verification unit 930 can, based on the received API sample code, retransmit API security status information, including the calculation result after calculating the API security level, to the blockchain.

[0147] At this point, the blockchain can classify a WAAP with a security level of 1 calculated using malicious API sample code for vulnerability testing as a vulnerable WAAP and downgrade its level to low. Conversely, the blockchain can classify a WAAP with a security level of 3 calculated using malicious API sample code for vulnerability testing as a stable WAAP and upgrade its level to high.

[0148] Figure 10 For can Figure 8 A simplified block diagram of the main WAAP configurations in the administrator mode used in the security system.

[0149] Reference Figure 10 The WAAP 1000 in administrator mode can be configured with an update processing unit 1010, a handshake processing unit 1020, a sample code verification processing unit 1030, and an API security level processing unit 1040.

[0150] The update processing unit 1010 is capable of performing updates for restoring WAAP level updates with WAAP administrator privileges.

[0151] The handshake processing unit 1020 can perform a secure handshake to establish a session with the blockchain. The secure handshake may include a TLS handshake, but is not limited to this, and other security methods may also be applicable.

[0152] The example code verification processing unit 1030 can request a WAAP level test from the blockchain. For a downgraded WAAP, the example code verification processing unit 1030 can update itself to restore the WAAP level and then request a WAAP level test from the blockchain. Furthermore, the example code verification processing unit 1030 can perform verification on the malicious API example code used for vulnerability testing from the blockchain and calculate the API security level.

[0153] The API security level processing unit 1040 can transmit API security status information, including the API security level calculation of the sample code verification processing unit 1030 and the adjustment result based on its WAAP level, to the blockchain.

[0154] Based on the aforementioned security system, to ensure the security of enterprise service APIs, a WAAP service API security level calculation function can be provided to perform security level calculations on vulnerabilities of each service API. Furthermore, to ensure enterprise service API security, an ID and hash value for each service API can be generated and matched, or a WAAP service API management function that matches hash values ​​can be provided.

[0155] Furthermore, based on the aforementioned security system, for the security of enterprise service APIs, a WAAP service API security verification function can be provided to perform security confirmation requests verification on user service APIs. The prerequisites for the service API security verification function may include that the service APIs are structured API services that adhere to consistent rules, patterns, and protocol standards.

[0156] Furthermore, based on the aforementioned security system, for the security of external users, a user-initiated reverse WAAP function can be provided to verify the security of the service API by sending a WAAP-linked blockchain request to the service provider (corresponding to the service provider). Additionally, for the security of external users, a pre-interception function for API vulnerabilities can be provided, such as publicly announcing the hash value of the service API to prevent its forgery. Moreover, for the security of external users, a secure user service exploitation environment function can be provided, such as providing a secure service API through a service API verification process.

[0157] Furthermore, based on the aforementioned security system, WAAP network firewall functionality can be provided for enterprise intranet security. This network firewall functionality may include DMZ Zone service server security, bot detection, and DDoS blocking.

[0158] Figure 11 This is a block diagram illustrating a software module that may be used in a security system according to another embodiment of this disclosure.

[0159] Reference Figure 11 The processor 1100 of the security system includes at least one software module, which can be configured to include a network firewall function unit 1110, an API security function unit 1120, a robot mitigation function unit 1130, a DDoS defense function unit 1140, a self-verification function unit 1150, and an alarm processing unit 1160.

[0160] Network firewall functional unit 1110 is at least a part of the WAAP network firewall function and can be configured to respond to network attacks or primary attacks aimed at gathering information for secondary attacks. Network firewall functional unit 1110 can be configured with a network firewall engine based on multiple rules and custom rules. The network firewall engine detects and blocks HTTP / HTTPS-based network attacks by analyzing the signals or data of attackers or circumventing attackers, and maintains the security of the client's internal network.

[0161] API Security Function Unit 1120 is at least part of the WAAP network firewall function or enterprise service API security function. It calculates the security level of the API, verifies whether the API is secure or has been tampered with, and informs the user.

[0162] The bot mitigation unit 1130 is at least part of the WAAP network firewall function or enterprise service API security function, and can be configured to identify and detect bot cheating behavior and block it. The bot mitigation unit 1130 uses pre-defined Suspicious Access (SA) rules, leveraging inherent information about the client (in this case, the attacker), to identify and block the bot's cheating behavior, preventing it from attempting an attack. Specifically, the SA rules determine characteristics such as those of the bot's automated attack tools to block access or restrict access from clients that are not using normal web browsers.

[0163] DDoS defense function unit 1140 is at least part of the WAAP network firewall functionality and can be configured to detect and block DDoS attacks at the application layer. For example, DDoS defense function unit 1140 can detect and block attacks that overload a session by repeatedly sending incomplete requests.

[0164] The self-verification function unit 1150 can be configured to automatically identify problems occurring during the operation of the safety device. The self-verification function unit 1150 can be configured to self-diagnose its own status, identify risk situations, and automatically perform recovery actions in real time according to a preset process. The automatic recovery function can be executed through preset self-diagnostic items and according to their set values.

[0165] When alarm usage settings are available, the alarm processing unit 1160 can transmit the alarm to the administrator or client of the security device based on the preset risk level distinction results such as self-diagnosis and risk situation identification and / or the set value for issuing the alarm.

[0166] At least one of the aforementioned software modules, or at least one of the following configurable program instructions: network firewall function unit 1110, API security function unit 1120, robot mitigation function unit 1130, DDoS defense function unit 1140, self-verification function unit 1150, and alarm processing unit 1160.

[0167] In addition, program instructions may include at least one instruction for implementing the security method. For example, program instructions may include handshake processing instructions, API registration verification processing instructions, API security level processing instructions, notification processing instructions, update processing instructions, sample code verification processing instructions, etc.

[0168] Furthermore, the operation of the security method described in the foregoing embodiments of the present invention can be implemented by a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes all types of recording devices for storing information readable by a computer system. Moreover, the computer-readable recording medium stores and runs computer-readable programs or code distributed across computer systems connected via a network, in a distributed manner.

[0169] In addition, computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as read-only memory (ROM), random access memory (RAM), and flash memory. Program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or similar means.

[0170] Some aspects of the invention are described in the context of apparatus, but may also represent a description according to a corresponding method, wherein blocks or apparatuses correspond to method steps or features of method steps. Similarly, aspects described in the context of a method may also be represented by features of corresponding blocks or items or corresponding apparatuses. Some or all of the method steps may be executed by (or utilize) hardware devices, such as microprocessors, programmable computers, or electronic circuits. In some embodiments, at least one of the most important method steps may be executed by an apparatus as described above.

[0171] In the embodiments, a programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described herein. In the embodiments, the field-programmable gate array may operate in conjunction with a microprocessor for performing one of the methods described herein. Typically, it is preferable that the methods are performed by some hardware device.

[0172] The above description refers to the embodiments. However, it is understood that those skilled in the art can make various modifications and changes to the present invention without departing from the scope of the invention as described in the claims.

Claims

1. A blockchain-based security method, executed by an integrated network security solution, and utilizing integrated network security solution and application programming interface level management, characterized in that, comprises the steps of: receiving an application programming interface security level confirmation request from the blockchain in a case where a session is established with the blockchain; confirming the application programming interface security level, wherein the security level of the application programming interface vulnerability is confirmed from among management application programming interface data of the integrated network security scheme having the highest stability level, by itself; and transmitting information about the application programming interface security level to the blockchain. 2.The blockchain-based security method of claim 1, wherein the integrated network security scheme has a level of 1 indicating the most secure integrated network security scheme in the security aspect, and the blockchain stores integrated network security scheme identification information of the integrated network security scheme and a list of application programming interfaces registered in the security level 1 of the integrated network security scheme. 3.The blockchain-based security method of claim 2, wherein the blockchain synchronization with the corresponding integrated network security scheme is completed with respect to the list of application programming interfaces of the security level 1 as the most secure level in the security aspect. 4.The blockchain-based security method of claim 1, further comprising the step of collecting an integrated network security scheme vulnerability test application programming interface sample code from the blockchain, the application programming interface sample code being a malicious sample code. 5.The blockchain-based security method of claim 4, further comprising the step of calculating a security level with respect to the integrated network security scheme vulnerability test application programming interface sample code. 6.The blockchain-based security method of claim 5, further comprising the step of transmitting information about an application programming interface security level status including the calculated security level to the blockchain. 7.The blockchain-based security method of claim 6, wherein the blockchain classifies the integrated network security scheme having the highest security level calculated with respect to the integrated network security scheme vulnerability test application programming interface sample code as a security-weak integrated network security scheme and downgrades the level thereof, based on the information about the application programming interface security level status. 8.The blockchain-based security method of claim 6, wherein the blockchain classifies the integrated network security scheme having the lowest security level calculated with respect to the integrated network security scheme vulnerability test application programming interface sample code as a stable integrated network security scheme and upgrades the level thereof, based on the information about the application programming interface security level status. further comprising the steps of: requesting a test of the integrated network security scheme to the blockchain; receiving an application programming interface sample code security level confirmation request from the blockchain; and transmitting application programming interface security level status information including confirmation information about the application programming interface security level to the blockchain. comprises the steps of: ​ ​ 9.The blockchain-based security method of claim 1, wherein, ​ ​ ​ ​ 10. A blockchain-based security method, executed by an integrated network security solution, and utilizing an integrated network security solution and application programming interface level management, characterized in that, ​ requesting a test integration network security scheme from a blockchain through a session established with the blockchain; receiving a security level confirmation request for an application programming interface sample code from the blockchain; performing a vulnerability test for the application programming interface sample code received from the blockchain; calculating a security level of the application programming interface after performing the vulnerability test; and transmitting application programming interface security level status information including confirmation information about the security level of the application programming interface to the blockchain. 11.The blockchain-based security method of claim 10, further comprising, before requesting the test integration network security scheme, the step of upgrading a function of the integration network security scheme by itself with an administrator authority of the integration network security scheme. 12.The blockchain-based security method of claim 10, wherein the blockchain classifies an integration network security scheme whose security level of the application programming interface sample code for a vulnerability test is the highest level as a security-weak integration network security scheme and downgrades a level thereof, or classifies an integration network security scheme whose security level of the application programming interface sample code for a vulnerability test is the lowest level as a stable integration network security scheme and upgrades a level thereof, based on information about a status of the security level of the application programming interface. The security system comprises: a memory; and at least one processor coupled to the memory to execute a program including at least one instruction, wherein the processor, through the at least one instruction, receives a security level confirmation request for the integration network security scheme from the blockchain in a case where a session is established with the blockchain, confirms the security level of the application programming interface, and transmits confirmation information about the security level of the application programming interface to the blockchain.

13. A blockchain-based security system that utilizes an integrated network security solution and application programming interface level management, characterized in that, 14.The blockchain-based security system of claim 13, wherein the integration network security scheme has a level 1 indicating a most secure integration network security scheme in a security aspect, the blockchain stores integration network security scheme identification information of the integration network security scheme and a list of application programming interfaces registered in the security level 1 of the integration network security scheme, and the blockchain performs a blockchain synchronization with a corresponding integration network security scheme with respect to the list of application programming interfaces of the highest security level in the security aspect. 15.The blockchain-based security system of claim 13, wherein the processor further performs the steps of receiving an application programming interface sample code for a vulnerability test from the blockchain, calculating a security level of the application programming interface sample code for a vulnerability test of the integration network security scheme, and transmitting information about a status of the security level of the application programming interface including the calculated security level to the blockchain. ​ ​ ​ ​ ​ ​ 16.The blockchain-based security system of claim 15, wherein the blockchain classifies an integrated network security scheme whose security level calculated based on information about a security level status of the application programming interface example code for integrated network security scheme vulnerability testing is the highest level as a security-weak integrated network security scheme and downgrades the level thereof. 17.The blockchain-based security system of claim 15, wherein the blockchain classifies an integrated network security scheme whose security level calculated based on information about a security level status of the application programming interface example code for integrated network security scheme vulnerability testing is the lowest level as a stable integrated network security scheme and upgrades the level thereof. 18.The blockchain-based security system of claim 13, wherein the processor further performs: requesting the blockchain to test the integrated network security scheme, receiving a security level confirmation request for the application programming interface example code from the blockchain, and transmitting application programming interface security level status information including confirmation information about the security level of the application programming interface to the blockchain. 19.The blockchain-based security system of claim 18, wherein the processor further performs: requesting the blockchain to test the integrated network security scheme, or requesting a retest to modify the level of the integrated network security scheme before the retest due to a level downgrade adjustment of the integrated network security scheme according to a previous test result, and upgrading a function of the integrated network security scheme by itself with an administrator authority of the integrated network security scheme. ​ ​ ​ ​

Images