Security blindspots for selfhosted website
Security blindspots for selfhosted website
Hello. I’m pretty new here. I just managed to get my Raspberry Pi setup at home to selfhost a simple website that will act as my portfolio for some art I do.
I’m using WordPress to make the content of the website, meaning it runs on Apache, MariaDB and MySQL in the background. It’s connected via port 80 since I don’t want to pay for SSL certificates to setup https. There will be no accounts or transactions happening on my website. I don’t have anything to manage my dynamic IP but I’ll figure that out later. I’ve deleted the default Pi user on the RPi.
Are there security issues I should address preemptively? I’m worried for instance that I am exposing my home network, making it easier for someone to breach into whatever is connected there.
Any tips on making sure my setup is secure?
Go https, today there is no real reason not to and tons of good reasons to do it.
Let's encrypt is 100% free and using their certbot its also automated and easy to do.
Take a look at certbot. You don't need to pay for ssl and ssl is actually pretty mandatory for anything served on the internet.
Make sure you don't forward too much ports. And make sure you have a working firewall that only allow those same ports. You should be good to go then.
Also be advised that wordpress will attract all the internet to try and hack in, so make sure you keep everything up to date
Setting up fail2ban to block people trying to brute force the admin panel is a good start.
I would add from an end-user privacy perspective, they might want HTTPS. If I hit a website not using HTTPS, I pretty much immediately back out. Bad actors like hostile governments and hackers can use seemingly meaningless data against you.
I can’t remember exactly what happened but I remember back when WebMD was fighting against rolling out TLS hackers were able to find medical weaknesses against people.
Not too mention the scary browser warnings. It's not a good look tbh if this is your portfolio. Lots of great considerations and tips here already though.
Noted ! I’ll make sure to set https up.
Tbh, I haven’t heard the word firewall since probably 2005… would my router have a firewall built in or is that something I need to add on, let’s say, the RPi ?
Your router probably does have one, but your end devices should too. If your router is some piece of trash ISP-supplied one, it might not even have a firewall for IPv6 (if it even supports IPv6 at all).
Add it to the Pi. Easier maintenance.
Unless you require the dynamic features of Wordpress, you could have a look at some of the static site generators out there (such as Hugo). Having a static site would reduce the attack surface considerably. Also due to the shenanigans happening with Wordpress at the moment, I would be weary of using it.
About SSL, what others have already mentioned, SSL certs are available for free these days, thanks to letsencrypt.
There are also static export plugins for wordpress. One needs to get rid of comment boxes and such as they don't work then of course. But if all content is already in WordPress, serving just the static export is a low friction solution.
I’d almost go through the trouble of getting the content out of Wordpress. The nice thing about static site generators is you can completely switch out the framework, runtime, base Docker image and/or OS at any time.
since I don’t want to pay for SSL certificates to setup https.
You don't need to pay for SSL certs anymore, most of the time. You can get them for free from a bunch of different places now. I use Let's Encrypt. The web server/reverse proxy I use, Caddy is able to automatically get a cert for you, install it, and keep it renewed. The only time you need to pay for a cert is if you are handling financial transactions.
Are there security issues I should address preemptively?
WordPress itself has a generally good reputation for security, though depending on how the current drama goes, that may change. WordPress security problems have almost always stemmed from plugins or poor password hygiene. Remove any plugins you are not actively using, keep the ones you are using updated, and use a good password that you don't use anywhere else. A password wallet like Bit Warden can generate and store such passwords for you.
Better on the security front would be to evaluate whether you actually need something like WordPress at all. A static site would likely be far more secure. There's less moving parts that might be vulnerable.
While you could program a static site yourself, it's more common nowadays to use a static site generator like Hugo to build the site. You set it up once for how you want the site to look and then you write your posts in markdown or whatever your particular generator uses.
I don’t have anything to manage my dynamic IP
Most domain name providers have some sort of setup for dealing with dynamic IP addresses, a program called
ddclientis pretty common and is available in most repos.Wow lots of info. I’ll check all of this out. You have a good point that I don’t need wordpress. Hugo looks interesting, thanks for the advice!
And yes, as said above, I’ll look into the free SSL certs to setup https.
To add to this, you might check out some of the free Hugo themes here: https://themes.gohugo.io/tags/portfolio/
It may or may not be a concern to you, but if you are hosting it from your home then people will be able to determine your IP and rough physical location.
If you're on American cable internet and expecting a lot of traffic, your upload speed may become a problem.
Your first point is a good point. I guess it’s ok for now if my rough location is accessible. It’s not like my art is worth anything.
Regarding upload speed, yeah I know it could become an issue but since it’s just a portfolio website, I don’t expect more than a dozen visits a month.
scraping bots are expected to visit it, nowadays more than in previous years. a few of them are search engines, but there's a lot of scraping for AI training, both on text and image data.
Keep wordpress up-to-date, and keep the number of plugins you use to a minimum.
Let's Encrypt is good practice, but IMO if you're just serving the same static webpage to all users, it doesn't really matter.
Given that it's a tiny raspi, I'd recommend reducing the overhead that WordPress brings and just statically serve a directory with your site. Whether that means using wp static site options, or moving away from wp entirely is up to you.
The worst case scenario would be someone finding a vulnerability in the services that are publicly exposed (Apache), getting persistence on the device, and using that to pivot to other devices on your network. If possible, you may consider putting it in a routing DMZ. Make sure that the pi can only see the internet and whatever device you plan to maintain it with. That way even if someone somehow owns it completely, they won't be able to find any other devices to hack.
The WordFence plugin is a must-have for security.
If you use Caddy instead of Apache then you get SSL automatically. You'll need php-fpm as well, tho.
What does WordFence provide that makes it a must have?
Agreed on word fence.
Definitely use cloudflare in front of your website