Method and system for acquiring credible IP list and computer equipment

By configuring the authorized IP list of internal enterprise applications and the authentication of enterprise collaboration software on the Nginx server, the security risks and inefficiency problems in internal enterprise applications are solved, and more secure and efficient IP access control is achieved.

CN119030740APending Publication Date: 2024-11-26HAIER CONSUMER FINANCE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410970888.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-19
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The existing technology has security risks in the access control of internal enterprises. The login interface becomes a single point of failure. Attackers may use undetected vulnerabilities to illegally access, and employees need to manually enter their username and password each time they log in, which affects the impact. Office efficiency.

Method used

The authorized IP list of enterprise internal applications is published through the Nginx server. Users verify their identity (OPENID and token) in the enterprise collaboration software, configure the verified IP address to the whitelist to realize IP access control and reduce Internet exposure. Only authorized IP access is allowed.

Benefits of technology

It effectively reduces the risk of illegal access, improves the security of internal applications and employee office efficiency, reduces the repeated operations of login verification, and optimizes the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119030740A_ABST
    Figure CN119030740A_ABST
Patent Text Reader

Abstract

The invention relates to a credible IP list obtaining method and system and computer equipment, and the method comprises the steps: issuing an internal application of an enterprise through an Nginx server, and configuring an authorized IP list of the internal application of the enterprise as a white list of an Nginx configuration file; the enterprise internal application interface is configured in enterprise collaboration software, when the enterprise internal application is accessed in the enterprise collaboration software, an identity label of the enterprise collaboration software is obtained and sent to a white list management application to be verified, the identity label comprises an OPENID and a token, and the white list management application comprises a white list; the white list management application is used for sending the identity label to a server of the enterprise collaboration software to verify the legality of the identity label, extracting an IP address of a user request passing verification and configuring a validity period; and updating the IP address and the validity period thereof to the authorized IP list. According to the application, the problem that potential safety hazards exist when an internal application of an enterprise is accessed through account login is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of IP access control, and in particular to a method, system and computer device for obtaining a trusted IP list. Background Art

[0002] There are many ways to access internal enterprise applications. How to access internal enterprise applications safely and stably has become a problem that employees need to solve in their daily office work and companies need to ensure internal information security.

[0003] The existing patent CN117240539A discloses a method for logging into a system, including: receiving first authorization request information sent by a first terminal, the first authorization request information indicating that the first system requests the identity information of an authorized user, the first system including: an internal system or a third-party system integrated by the enterprise; authenticating the first system according to the first authorization request information; if the authentication is successful, sending the first identification and token of the user to the first terminal, the first identification and the token being used to log into the first system and obtain the identity information.

[0004] The existing technology only obtains authorization at the login account level. Through the enterprise's open platform, the user's identity information can be authorized when the user wants to log in to the internal system or third-party system integrated by the enterprise.

[0005] The internal login interface may not be fully detected by external security scanning tools, which may lead to potential security vulnerabilities being overlooked. Attackers may use these undiscovered vulnerabilities to bypass security mechanisms and illegally access internal applications. All access controls are concentrated on the login interface, making the login interface a single point of failure. If the login interface fails or is successfully attacked by an attacker, access to the entire internal application will be affected.

[0006] If the security policy of the login interface is not strong enough (such as using a weak password policy, lack of multi-factor authentication, etc.), then attackers may try to use brute force to guess or crack the user's login credentials. If successful, the attacker can gain illegal access to internal applications.

[0007] The access to internal enterprise applications is limited to the login level. Employees manually enter their usernames and passwords every time they log into internal enterprise applications, which is not conducive to improving their office efficiency.

[0008] However, a large number of enterprises cannot use dedicated lines due to various reasons such as cost and user accessibility and must publish applications to the Internet. In this way, the applications will face security threats from the entire Internet. Summary of the invention

[0009] The embodiments of the present application provide a method, system and computer device for obtaining a trusted IP list, so as to at least solve the problem of potential security risks when entering an enterprise's internal application through account login in the related art.

[0010] In a first aspect, an embodiment of the present application provides a method for obtaining a trusted IP list, including:

[0011] Whitelist acquisition steps: publish internal enterprise applications through the Nginx server, and configure the authorized IP list of internal enterprise applications as the whitelist of the Nginx configuration file;

[0012] A user verification step, configuring the enterprise internal application interface in an enterprise collaboration software, obtaining the identity identifier of the enterprise collaboration software and verifying it in a whitelist management application when accessing the enterprise internal application in the enterprise collaboration software, wherein the identity identifier includes an OPENID and a token, and the whitelist management application is used to send the identity identifier to the server of the enterprise collaboration software to verify the legitimacy of the identity identifier, extract the IP address of the user request that has passed the verification, and configure the validity period;

[0013] The IP list maintenance step updates the IP address and its validity period to the authorized IP list.

[0014] The server of the enterprise collaboration software identifies the identity of the enterprise collaboration software and obtains the legitimacy of the user identity. Only those with legitimacy are allowed to access the internal enterprise applications. The coarse-grained verification of authorized IP access rights is achieved by maintaining a whitelist. The IPs that can access the internal enterprise applications are managed from the IP access control level, which reduces the exposure of the applications on the Internet. The number of applications that can be accessed by nearly 4.3 billion IPs on the Internet is reduced to a few thousand IPs used by internal enterprise users. The number of applications that can be directly accessed on the Internet is greatly reduced, which reduces the exposure risk and ensures the security of the applications.

[0015] In some embodiments, the IP list maintenance step further includes:

[0016] Based on the validity period, the expired IP addresses are deleted from the whitelist according to the expiration time.

[0017] Regularly clear out expired IP addresses in the whitelist to reduce invalid data in the whitelist, thereby alleviating the storage pressure of the IP list in the whitelist and improving the security of IP access by managing the whitelist IP list.

[0018] In some of the embodiments, the whitelist is used to determine whether the IP address requested by the user is in the authorized list when the user accesses the internal enterprise application. If the IP address requested by the user is in the authorized IP list, the user can jump to the internal enterprise application; otherwise, the user verification step is entered and verified in the server of the enterprise collaboration software.

[0019] When a user accesses an internal enterprise application, first check whether the user's current IP is in the authorized IP list. If the user's current IP is already in the authorized IP list, it will be forwarded to the internal enterprise application address by proxy, and then access the internal enterprise application. First determine whether it is in the authorized IP list to reduce repeated verification operations and optimize user experience and verification logic. If the user's current IP is not in the authorized IP list, it will be verified in the server of the enterprise collaboration software. If the verification fails, an error prompt page will pop up to remind the user that the verification failed. Adding a prompt page that jumps when verification fails can prompt the user's verification result for easy viewing.

[0020] In some embodiments, the user verification step further comprises:

[0021] Compare the identity tag with the internal system records of the enterprise collaboration software server to verify the user's identity;

[0022] The server of the enterprise collaboration software feeds back verification information, which includes whether the user is legitimate.

[0023] The verification information fed back by the server of the enterprise collaboration software is used as a basis to determine whether the user is legitimate. This ensures that the users accessing the internal applications of the enterprise are legitimate, reduces the number of illegal intruders, and thus improves the security of the internal applications of the enterprise.

[0024] In some of these embodiments, the initial authorized IP list is a blank list.

[0025] The initial IP list whitelist is a blank list, which makes it easier to maintain the IP list based on actual conditions and actual employee information, and improves the flexibility of IP list maintenance.

[0026] In some embodiments, it also includes:

[0027] When the user's IP changes or expires, a verification prompt will be sent to verify the user's identity again.

[0028] According to the change and validity period of the IP, the user is prompted to verify again. This prevents non-enterprise personnel from using the original IP to access the enterprise's internal applications, thereby reducing the exposure of the enterprise's internal applications and improving the security of the enterprise's internal applications.

[0029] In some embodiments, it also includes:

[0030] The access methods of the enterprise internal application include client, browser and third-party application.

[0031] Access internal enterprise applications in a variety of ways, and flexibly access internal enterprise applications, so that employees can work in a variety of situations and improve their work efficiency.

[0032] In a second aspect, an embodiment of the present application provides a system for obtaining a trusted IP list, including:

[0033] The whitelist acquisition module is configured to publish internal enterprise applications through the Nginx server and configure the authorized IP list of the internal enterprise applications as a whitelist in the Nginx configuration file;

[0034] The user verification module is configured to configure the enterprise internal application interface in an enterprise collaboration software. When accessing the enterprise internal application in the enterprise collaboration software, the identity identifier of the enterprise collaboration software is obtained and verified in a whitelist management application. The identity identifier includes an OPENID and a token. The whitelist management application is used to send the identity identifier to the server of the enterprise collaboration software to verify the legitimacy of the identity identifier, extract the IP address of the user request that has passed the verification, and configure the validity period;

[0035] The IP list maintenance module is configured to update the IP address and its validity period to the authorized IP list.

[0036] In the user verification module, the identity of the enterprise collaboration software is identified through the server of the enterprise collaboration software to obtain the legitimacy of the user identity. Only those with legitimacy are allowed to access the internal enterprise application. The IP list maintenance module maintains the whitelist to implement coarse-grained verification of authorized IP access rights. Managing IPs that can access internal enterprise applications from the IP access control level reduces the exposure of applications on the Internet, reducing the number of applications that were originally accessible by nearly 4.3 billion IPs on the Internet to a few thousand IPs used by internal enterprise users. The number of applications that can be directly accessed on the Internet is greatly reduced, reducing the risk of exposure and ensuring the security of internal enterprise applications.

[0037] In some embodiments, the IP list maintenance module further includes:

[0038] The deleting unit is configured to delete the expired IP address from the whitelist based on the validity period and the expiration time.

[0039] The deletion unit regularly cleans up expired IP addresses in the whitelist to reduce invalid data in the whitelist, thereby alleviating the storage pressure of the IP list in the whitelist and improving the security of IP access by managing the whitelist IP list.

[0040] By allowing verified users to add accessible applications to the whitelist on their own, the application's exposure to the Internet is reduced and application security is ensured without affecting the user experience.

[0041] In a third aspect, an embodiment of the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, a method for obtaining a trusted IP list as described in the first aspect above is implemented.

[0042] Compared with the related art, the embodiments of the present application provide a method, system and computer device for obtaining a trusted IP list. By maintaining the authorized IP list of internal enterprise applications, it solves the problem of security risks when entering internal enterprise applications through account login, and manages the IPs that can access internal enterprise applications at the IP access control level, reducing the number of applications that were originally accessible by nearly 4.3 billion IPs on the Internet to a few thousand IPs used by internal enterprise users. The number of applications that can be directly accessed on the Internet is greatly reduced, reducing exposure risks and ensuring the security of internal enterprise applications.

[0043] Details of one or more embodiments of the present application are set forth in the following drawings and description to make other features, objects, and advantages of the present application more readily apparent. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0045] Figure 1 is a flowchart of a method for obtaining a trusted IP list according to an embodiment of the present application;

[0046] Figure 2 It is a structural block diagram of a system for obtaining a trusted IP list according to an embodiment of the present application;

[0047] Figure 3 is another structural block diagram of a system for obtaining a trusted IP list according to an embodiment of the present application;

[0048] Figure 4 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is described and illustrated below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments provided in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0050] Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. In addition, it can also be understood that although the efforts made in this development process may be complicated and lengthy, for ordinary technicians in this field related to the content disclosed in this application, some changes in design, manufacturing or production based on the technical content disclosed in this application are just conventional technical means, and should not be understood as insufficient content disclosed in this application.

[0051] Reference to "embodiments" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those of ordinary skill in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0052] Unless otherwise defined, the technical terms or scientific terms involved in this application should be understood by people with ordinary skills in the technical field to which this application belongs. The words "one", "a", "a", "the" and the like involved in this application do not indicate a quantitative limitation, and may represent the singular or plural. The terms "include", "comprise", "have" and any of their variations involved in this application are intended to cover non-exclusive inclusions; for example, a process, method, system, product or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units that are not listed, or may also include other steps or units inherent to these processes, methods, products or devices. The words "connect", "connected", "coupled" and the like involved in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "multiple" involved in this application refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships, for example, "A and / or B" can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects before and after are in an "or" relationship. The terms "first", "second", "third", etc. involved in this application are only used to distinguish similar objects and do not represent a specific ordering of the objects.

[0053] This embodiment provides a method for obtaining a trusted IP list. Figure 1 is a flowchart of a method for obtaining a trusted IP list according to an embodiment of the present application, such as Figure 1 As shown, the process includes the following steps:

[0054] In the whitelist acquisition step S101, the enterprise internal application is published through the Nginx server, and the authorized IP list of the enterprise internal application is configured as the whitelist of the Nginx configuration file.

[0055] User verification step S102, configure the enterprise internal application interface in an enterprise collaboration software, when accessing the enterprise internal application in the enterprise collaboration software, obtain the identity of the enterprise collaboration software to a whitelist management application for verification, the identity includes OPENID and token, the whitelist management application is used to send the identity to the server of the enterprise collaboration software to verify the legitimacy of the identity, extract the IP address of the user request that has passed the verification and configure the validity period. Optionally, enterprise collaboration software includes but is not limited to: WeChat for Enterprise, DingTalk, Feishu; correspondingly, its servers include but are not limited to: Tencent, Alibaba.

[0056] The IP list maintenance step S103 updates the IP address and its validity period to the authorized IP list.

[0057] Through the above steps, the identity of the enterprise collaboration software is identified by the server of the enterprise collaboration software, and the legitimacy of the user identity is obtained. Only those with legitimacy are allowed to access the internal enterprise application. The coarse-grained verification of authorized IP access rights is achieved by maintaining a whitelist. The IPs that can access the internal enterprise applications are managed from the IP access control level, which reduces the exposure of the application on the Internet, and reduces the number of applications that can be accessed by nearly 4.3 billion IPs on the Internet to a few thousand IPs used by internal enterprise users. The number of applications that can be directly accessed on the Internet is greatly reduced, which reduces the exposure risk and ensures the security of the application.

[0058] In the above embodiment, the user verification step S102 configures the enterprise internal application interface in an enterprise collaboration software, and provides the enterprise internal application icon in the client interface of the enterprise collaboration software. After the user clicks the application icon, the OPENID and token given to the user by WeChat, DingTalk or Feishu will be carried to a whitelist management application for verification. When verifying the OpenID, the server can query the internal database or user directory service to confirm whether the user is still employed and valid. If the user resigns or the status changes, the system should immediately update the status of his OpenID and notify the relevant services to stop his access rights. After the verification is passed, the public network IP carried in the user request message is extracted, the validity period is set for the IP, and the IP list and expiration time are maintained locally. Among them, the expiration time can be balanced between security and user experience. The shorter the validity period, the higher the security. A validity period of 8 hours can reach a high security level, 48 hours is a medium security level, and 7 days is a low security level. Set the validity period to be less than or equal to 7 days.

[0059] It should be noted that only employed users can use the company's enterprise collaboration software. Users whose enterprise collaboration software has been deactivated due to resignation or other reasons will not be able to use the enterprise collaboration software, nor can they use this function to add to the whitelist, ensuring that users who use this function can only be employed and valid users of the company, thereby improving the security of access to internal enterprise applications.

[0060] In another embodiment, in the user verification step S102, before obtaining the identity of the enterprise collaboration software and verifying it in a whitelist management application, a data acquisition request is sent to the user, and the user's identity is obtained with the user's consent.

[0061] In some embodiments, the IP list maintenance step S103 further includes:

[0062] Based on the validity period, the expired IP addresses are deleted from the whitelist according to the expiration time.

[0063] Based on the above steps, expired IP addresses are regularly cleared in the whitelist to reduce invalid data in the whitelist, thereby alleviating the storage pressure of the IP list in the whitelist. By managing the whitelist IP list, the security of IP access is improved.

[0064] In some embodiments, the user verification step S102 further includes:

[0065] Compare the identity ID with the internal system records of the enterprise collaboration software server to verify the user's identity.

[0066] The server of the enterprise collaboration software feeds back verification information, which includes whether the user is legitimate.

[0067] The verification information fed back by the server of the enterprise collaboration software is used as a basis to determine whether the user is legitimate. This ensures that the users accessing the internal applications of the enterprise are legitimate, reduces the number of illegal intruders, and thus improves the security of the internal applications of the enterprise.

[0068] In order to facilitate the maintenance of the IP list according to the actual situation and actual employee information, the embodiment of the present application sets the initial authorized IP list for internal enterprise applications to a blank list to improve the flexibility of IP list maintenance.

[0069] In some embodiments, it also includes:

[0070] If the user's IP changes or expires, the page will jump to the verification prompt and prompt the user to verify his / her identity again.

[0071] After receiving the user's request, the enterprise's internal application determines that the user's IP has changed or has expired, and forwards the user's request to the verification prompt page, reminding the user that the IP is not in the authorized IP list or the IP has expired, and prompting the user to verify the user's identity again. This prevents non-enterprise personnel from using the original IP to access the enterprise's internal application, thereby reducing the exposure of the enterprise's internal application and improving the security of the enterprise's internal application.

[0072] In some embodiments, it also includes:

[0073] The access methods of the enterprise internal application include client, browser and third-party application.

[0074] Access internal enterprise applications in a variety of ways, and flexibly access internal enterprise applications, so that employees can work in a variety of situations and improve their work efficiency.

[0075] After the user's IP has been added to the authorized IP list, the terminal device using the IP can access the application server at the network level. The application can be accessed through the client, browser, third-party application integration, etc., and the login can be verified through the application's own user authentication method.

[0076] The method for obtaining the trusted IP list based on the present application provides a verification process combining user IP verification based on the Nginx server whitelist and verification based on third-party software. Based on this, when a user accesses an internal enterprise application, the Nginx server will first determine whether the IP address requested by the user is in the authorized IP list based on the whitelist obtained in the whitelist acquisition step S101. Only when the IP address requested by the user is in the authorized IP list can it directly jump to the internal enterprise application based on the enterprise collaboration software; specifically, if the IP address requested by the user is already in the authorized IP list, it will be forwarded to the internal enterprise application address by proxy, and then the internal enterprise application can be accessed. The present application uses the Nginx server to first determine whether it is in the authorized IP list, which can reduce repeated verification operations and optimize user experience and verification logic.

[0077] If the IP address requested by the user is not recorded in the authorized IP list, it needs to be further verified by the server of the enterprise collaboration software through the user verification step S102. The verification process refers to the user verification step S102 of this application. In the case of verification failure, an error prompt page pops up to remind the user that the verification failed. Adding a prompt page that jumps when verification fails can prompt the user of the verification result for easy viewing by the user.

[0078] Compared with VPN and the way administrators manually maintain IP lists, this application can effectively reduce implementation costs, save VPN equipment costs, and improve work efficiency by allowing users to add whitelists.

[0079] When using VPN to reduce exposure, users need to manually enter their username and password for authentication when logging in through VPN. The whole process is inefficient, time-consuming, and generally poor in user experience. Especially when the number of users exceeds 1,000, the daily maintenance workload will become huge, and the operational risk is high, resulting in a backlog of user requests that cannot be handled in a timely manner, causing users to be unable to use the service.

[0080] This application can automatically verify the login with the help of the user verification process of the third-party application, and the verification operation is simple and efficient. Users can add their IP to the authorized IP list by clicking the application icon in the enterprise collaboration software, which improves the user experience and reduces the workload of administrators.

[0081] The existing authentication technology is based on the network without restrictions, while this application is based on the network level, adding control to avoid some security scanning and brute force cracking scenarios, making the application accessible to only a small number of users.

[0082] This embodiment also provides a system for obtaining a trusted IP list, including:

[0083] The whitelist acquisition module is configured to publish the enterprise's internal applications through the Nginx server, and configure the authorized IP list of the enterprise's internal applications as the whitelist of the Nginx configuration file.

[0084] The user verification module is configured in an enterprise collaboration software to configure the enterprise internal application interface. When accessing the enterprise internal application in the enterprise collaboration software, the identity identifier of the enterprise collaboration software is obtained and verified in a whitelist management application. The identity identifier includes OPENID and a token. The whitelist management application is used to send the identity identifier to the server of the enterprise collaboration software to verify the legitimacy of the identity identifier, extract the IP address of the user request that has passed the verification, and configure the validity period.

[0085] The IP list maintenance module is configured to update the IP address and its validity period to the authorized IP list.

[0086] In the user verification module, the identity of the enterprise collaboration software is identified through the server of the enterprise collaboration software to obtain the legitimacy of the user identity. Only those with legitimacy are allowed to access the internal enterprise application. The IP list maintenance module maintains the whitelist to implement coarse-grained verification of authorized IP access rights. Managing IPs that can access internal enterprise applications from the IP access control level reduces the exposure of applications on the Internet, reducing the number of applications that were originally accessible by nearly 4.3 billion IPs on the Internet to a few thousand IPs used by internal enterprise users. The number of applications that can be directly accessed on the Internet is greatly reduced, reducing the risk of exposure and ensuring the security of internal enterprise applications.

[0087] In some embodiments, the IP list maintenance module further includes:

[0088] The deleting unit is configured to delete the expired IP address from the whitelist based on the validity period and the expiration time.

[0089] The deletion unit regularly cleans up expired IP addresses in the whitelist to reduce invalid data in the whitelist, thereby alleviating the storage pressure of the IP list in the whitelist and improving the security of IP access by managing the whitelist IP list.

[0090] It should be noted that the above modules can be functional modules or program modules, and can be implemented by software or hardware. For modules implemented by hardware, the above modules can be located in the same processor; or the above modules can be located in different processors in any combination.

[0091] In addition, combined Figure 1 The method for obtaining the trusted IP list described in the embodiment of the present application can be implemented by a computer device. Figure 4 is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present application, referring to Figure 4 As shown, the computer device may include a processor 81 and a memory 82 storing computer program instructions.

[0092] Specifically, the processor 81 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0093] Among them, the memory 82 may include a large-capacity memory for data or instructions. By way of example and not limitation, the memory 82 may include a hard disk drive (HDD), a floppy disk drive, a solid-state drive (SSD), a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory 82 may include a removable or non-removable (or fixed) medium. Where appropriate, the memory 82 may be inside or outside the data processing device. In a specific embodiment, the memory 82 is a non-volatile memory. In a specific embodiment, the memory 82 includes a read-only memory (ROM) and a random access memory (RAM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (Programmable Read-Only Memory, PROM for short), an erasable PROM (Erasable ProgrammableRead-Only Memory, EPROM for short), an electrically erasable PROM (Electrically Erasable ProgrammableRead-Only Memory, EEPROM for short), an electrically alterable ROM (Electrically Alterable Read-Only Memory, EAROM for short) or a flash memory (FLASH) or a combination of two or more of these. Under appropriate circumstances, the RAM can be a static random access memory (SRAM) or a dynamic random access memory (DRAM), wherein the DRAM can be a fast page mode dynamic random access memory (FPMDRAM), an extended data output dynamic random access memory (EDODRAM), a synchronous dynamic random access memory (SDRAM), etc.

[0094] The memory 82 may be used to store or cache various data files required for processing and / or communication, as well as possible computer program instructions executed by the processor 81 .

[0095] The processor 81 implements any one of the methods for obtaining a trusted IP list in the above embodiments by reading and executing computer program instructions stored in the memory 82 .

[0096] In some of these embodiments, the computer device may further include a communication interface 83 and a bus 80. Figure 4 As shown, the processor 81, the memory 82, and the communication interface 83 are connected via a bus 80 and communicate with each other.

[0097] The communication interface 83 is used to implement communication between the modules, devices, units and / or equipment in the embodiment of the present application. The communication interface 83 can also implement data communication with other components such as: external devices, image / data acquisition equipment, databases, external storage, and image / data processing workstations.

[0098] The bus 80 includes hardware, software or both, and couples the components of the computer device to each other. The bus 80 includes but is not limited to at least one of the following: a data bus, an address bus, a control bus, an expansion bus, and a local bus. By way of example and not limitation, bus 80 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, bus 80 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.

[0099] The computer device can execute the method for obtaining the trusted IP list in the embodiment of the present application based on the obtained user identity, thereby realizing the combination Figure 1 Describes how to obtain the trusted IP list.

[0100] In addition, in combination with the method for obtaining a trusted IP list in the above embodiment, the embodiment of the present application may provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any of the methods for obtaining a trusted IP list in the above embodiment is implemented.

[0101] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0102] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for obtaining a trusted IP list, characterized in that: include: Whitelist acquisition steps: publish internal enterprise applications through the Nginx server, and configure the authorized IP list of internal enterprise applications as the whitelist of the Nginx configuration file; A user verification step, configuring the enterprise internal application interface in an enterprise collaboration software, obtaining the identity identifier of the enterprise collaboration software and verifying it in a whitelist management application when accessing the enterprise internal application in the enterprise collaboration software, wherein the identity identifier includes an OPENID and a token, and the whitelist management application is used to send the identity identifier to the server of the enterprise collaboration software to verify the legitimacy of the identity identifier, extract the IP address of the user request that has passed the verification, and configure the validity period; The IP list maintenance step updates the IP address and its validity period to the authorized IP list.

2. The method for obtaining a trusted IP list according to claim 1, characterized in that: The IP list maintenance step also includes: Based on the validity period, the expired IP addresses are deleted from the whitelist according to the expiration time.

3. The method for obtaining a trusted IP list according to claim 1, characterized in that: The whitelist is used to determine whether the IP address requested by the user is in the authorized list when the user accesses the internal enterprise application. If the IP address requested by the user is in the authorized IP list, the user can jump to the internal enterprise application; otherwise, the user verification step is entered and verified in the server of the enterprise collaboration software.

4. The method for obtaining a trusted IP list according to claim 1, characterized in that: The user verification step further comprises: Compare the identity tag with the internal system records of the enterprise collaboration software server to verify the user's identity; The server of the enterprise collaboration software feeds back verification information, which includes whether the user is legitimate.

5. The method for obtaining a trusted IP list according to claim 1, characterized in that: The initial authorized IP list is a blank list.

6. The method for obtaining a trusted IP list according to any one of claims 1 to 5, characterized in that: Also includes: If the user's IP changes or expires, the page will jump to the verification prompt and prompt the user to verify his / her identity again.

7. The method for obtaining a trusted IP list according to claim 6, characterized in that: Also includes: The access methods of the enterprise internal application include client, browser and third-party application.

8. A system for obtaining a trusted IP list, characterized in that: include: The whitelist acquisition module is configured to publish internal enterprise applications through the Nginx server and configure the authorized IP list of the internal enterprise applications as a whitelist in the Nginx configuration file; The user verification module is configured to configure the enterprise internal application interface in an enterprise collaboration software. When accessing the enterprise internal application in the enterprise collaboration software, the identity identifier of the enterprise collaboration software is obtained and verified in a whitelist management application. The identity identifier includes an OPENID and a token. The whitelist management application is used to send the identity identifier to the server of the enterprise collaboration software to verify the legitimacy of the identity identifier, extract the IP address of the user request that has passed the verification, and configure the validity period; The IP list maintenance module is configured to update the IP address and its validity period to the authorized IP list.

9. The system for obtaining a trusted IP list according to claim 8, characterized in that: The IP list maintenance module also includes: The deleting unit is configured to delete the expired IP address from the whitelist based on the validity period and the expiration time.

10. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for obtaining the trusted IP list according to any one of claims 1 to 7 is implemented.