I had my website deployed as a virtual host using web station. Then I moved it into a virtual DSM where I setup web station and backends etc. Exactly the same (restored a hyper backup of web station and website files/databases into the VM then uninstalled same from the main NAS). Then to get to it over the web, my NAS has a reverse proxy that routes the traffic to the VM. The way it's setup the only port that will... Source: almost 2 years ago

May use a combination of .htaccess and robots.txt. Read for more examples here. For a first line of defense would go with CloudFlare, too. Also for bots that scan for vulnerabilities, etc., consider this. Source: almost 3 years ago

Consider CloudFlare WAF (Pro subscription), and/or hardening your security with an established sec plugin like WordFence, Sucuri. (I personally prefer a lighter plugin.). Source: almost 3 years ago

Against hackers, I fancied this plugin instead of Wordfence. Source: almost 3 years ago

This is a free plugin that takes a different approach to security. Source: almost 3 years ago

After a successful clean up, install a security plugin to shield from future attacks. I personally prefer a more lightweight one like this. Source: about 3 years ago