By configuring ssh, only set IP can log in over ssh. I found this important since I'm going to provide public-facing web services which would expose my IP. Moreover, I can't use a CDN for some reason I prefer not to share. Furthermore, I need to protect against zero-days in sshd. (Credits: @mti2935 )
However, I don't have a static public IP and do not have control of the network environment. People on the network I'm using are potential attackers and I can't move to a new network. Plus the VPS provider does not provide a console application (or something that can change the configuration) in its web interface. For some other reason, I prefer not to pick another provider.
Thus, it is infeasible for me to whitelist my current public IP in the target server.
Thus, I decided to rent another VPS and use it as the midpoint. On this VPS, I follow the best practices for ssh without setting up IP whitelisting. On the target server, I only whitelist the midpoint. Then I ssh to the target server using the midpoint. Both VPS are of one provider. The midpoint is not going to be used for anything else.
Does it improve the security of the target server, or does it pose additional risks to it?
Is this problem better solved using other methods?