When docking with a third-party interface, will there be any security problems after giving your own server ip to the other party?

the server is on Aliyun. When we dock with a third party, we give them the access address of our server. Although it is a pure interface interaction, this server is also the address where we access the background management system. Whether this will cause our business system to be exposed to each other, now the browser will enter this address and open the home page of the background, although there is a login user name as a restriction. But it"s still possible to be invaded. We have also considered using ip whitelist before, but because both customers and our technology will go up to do maintenance, we cannot exhaust ip. We have thought of using a special suffix path to open the background page, which may be safer but still not safe. I wonder if there is any good plan to prevent our internal system from being exposed?

Apr.16,2022

according to the information above, the solutions suitable for you at this stage can be as follows:

  1. the domain name that limits access to your background management system. If another domain name is used for the interface service, the domain name of the interface service is not allowed to access the domain name managed by the background.
  2. add IP whitelist mechanism with external maintenance and management requirements, and use mechanisms such as jump machine and VPN to limit it (that is, you must log in to the jump machine before you can remotely log in to the machine and VPN can be connected to a whitelist IP address before you can access the background management)

the above two can be used together.

there is another kind of thing that is designed to solve the problem of interface exposure like yours, which is called open gateway.
you need to register your interface with the open gateway, others are calling the open gateway to call your system.

Menu