What can be done to protect a exposed SQL 2005 Server without additional hardware?

DevOps & SysAdmins: What can be done to protect a exposed SQL 2005 Server without additional hardware?

Helpful? Please support me on Patreon: https://www.patreon.com/roelvandepaar

With thanks & praise to God, and with thanks to the many people who have made this project possible! | Content (except music & images) licensed under CC BY-SA https://meta.stackexchange.com/help/licensing | Music: https://www.bensound.com/licensing | Images: https://stocksnap.io/license & others | With thanks to user Zypher (serverfault.com/users/5880), user Satanicpuppy (serverfault.com/users/21416), user Remus Rusanu (serverfault.com/users/4605), user NitroxDM (serverfault.com/users/13685), user K. Brian Kelley (serverfault.com/users/385), user jftuga (serverfault.com/users/46738), user Chris S (serverfault.com/users/33417), and the Stack Exchange Network (serverfault.com/questions/157913). Trademarks are property of their respective owners. Disclaimer: All information is provided “AS IS” without warranty of any kind. You are responsible for your own actions. Please contact me if anything is amiss at Roel D.OT VandePaar A.T gmail.com