Custom Website vs Premade Website Software
In the modern day of the Internet, it feels almost expected to run an existing website framework of sorts, rather than building an entire website from the ground-up. I want to explore this a bit more in-depth.
As I'm running a more common website framework to host my personal site, as oppose to writing everything from scratch myself, I am beginning to notice some glaring differences. Namely in Security.
While writing and running my own custom web application, in either Django, or in fpWeb, I was writing everything from scratch, so all custom endpoints, and how data was loaded and saved. In way, this created security through obscurity, which is how Microsoft Windows does things, as not many people have access to the source code of Microsoft Windows. This is a similar security mentality for when it comes to building more closed off web applications. Even with Django, I am able to change very common end-points to limit any wide-spread Django afflicting bug for example. Most people never consider changing the Django admin URL endpoint, and so it can technically lead to a huge bug down the road for example. The Django websites I put up, purposely used an in-common endpoint path on all my websites, so only I personally knew how to access the Django admin section.
Some people reading this that also know I don't usually change my SSH default port from 22 might be laughing and saying, well why don't you change this very important end-point port then? Simple, I have other SSH securities measures in place that I have quite a bit of confidence in. One of my previous methods was to only allow my home IP address to ever connect on port 22, which entirely solved any problems with the port being exposed, as my home IP address rarely changes, it made it the perfect way to secure this port from anyone. I also never allow the root user to ever connect over SSH, and of course completely disable password authentication, which added an additional layer of security. I will actually be closing up port SSH in a very short while, so it won't be exposed online anymore, so don't worry about me using the default port 22 and worry about your own business and servers you manage. Thankfully in a corporate cloud environment, there is now zero reason to ever have port 22 exposed on the public Internet if you configure all your WAFs and VPCs correctly.
Anyway, by having a fully custom website, a lot of the URLs that most attackers would be scanning for, just simply won't exist. The argument against having a closed source website like this would be that there might be a ton of security bugs in my own code that I didn't personal account for. I'm not perfect, and every developer will make bugs in their code, so there is a bit of a point to be had here for sure. However, if I take enough precautions, such as not using any common endpoints, and all the endpoints that are publicly seen can't do much, and it's code has been tested well, then I think it's a decent trade-off. I doubt an attacker will overly spend their time trying to find a way to attack a server with such closed off source code, especially when there would be little to gain, it simply wouldn't be worth their time and effort. Microsoft Windows is a target with this security by obscurity because of it's massive install-base. If someone build a fun hobby project in their free-time to run their own personal website, regardless of any security issues, it's fairly doubtful that it will be targeted, unless the attacker had some sort of agenda I guess.
Now that my personal website is running some both common and open sourced, this is a situation where I need to be much more security aware though, as a mass attack targeting any server running Plone, could leave my website vulnerable of course. I see bots running through my server logs all the time, trying various wordpress end-points for example, among other popular web software. If you run something that is common and especially open source, keeping up with any security updates on it in the modern era of computing is extremely important.
