Re:Ask HN: Guidelines/steps to setup a secure Linux server f...
by Someone1234 on Tuesday July 29, 2014 @03:48PM
(#8104538)
In addition to caw's list:
* Disable all modules/extensions on the web-server you aren't using (e.g. don't need PHP? Disable it). This more often have exploits than the web-servers themselves.
* Automate patching and updates (this can be done on both Linux and Windows fairly easily)
I'd also mirror fnom's suggestion. Why not just use something like S3? I just entered details for a basic site on S3 and the calculator suggests it would cost less than $1/month(!). That's with 10-20,000 requests, 1 GB of low redundancy storage, and 1 GB in each direction for data.
* Disable all modules/extensions on the web-server you aren't using (e.g. don't need PHP? Disable it). This more often have exploits than the web-servers themselves.
* Automate patching and updates (this can be done on both Linux and Windows fairly easily)
I'd also mirror fnom's suggestion. Why not just use something like S3? I just entered details for a basic site on S3 and the calculator suggests it would cost less than $1/month(!). That's with 10-20,000 requests, 1 GB of low redundancy storage, and 1 GB in each direction for data.