Changes

Secure hosting guide

870 bytes added, 9 years ago
/* Useful References */
__NOTOC__
 
This document is the result of a collaborative project between [http://www.huridocs.org/ Huridocs] and [https://equalit.ie eQualit.ie].
 
==Useful References==
* [https://github.com/OpenInternet/MyWebsiteIsDown/blob/master/MyWebsiteIsDown.md What to do when your website goes down]
* [http://en.flossmanuals.net/wordpress/ Building a Wordpress site] and then [http://moz.com/blog/the-definitive-guide-to-wordpress-security Guide to secure Wordpress set-up]* The Engine Room's [[Responsible Data Forum on Hosting]]* [http://en.flossmanuals.net/video-hosting-guide-t/index/ Independent video hosting]
=Introduction=
Hosting a website that can withstand various malicious attacks and unauthorised access attempts is not an easy task. There are several approaches to mitigating digital threats and reducing your site's vulnerabilities. There is no one-fits-all solution however and the site's owners or administrators should plan for various contingencies well in advance, in lieu of their financial situation and technical expertise. This guide attempts to describe several scenarios and various approaches for secure hosting.
 
==Step 1: Decide on your level of technical expertise==
A lot of choices made within this guide will depend on your level of technical expertise dealing with server configuration and maintenance. You should evaluate your situation honestly and try not to exceed this level. We will use the following key to differentiate the difficulty associated with each type of activity.
 
*'''High Technical''' - multiple experiences of server administration, can confidently install/update server software; apache, mysql, mail server OR access to a consultant with these skills. Do not attempt to learn as you go!
*'''Intermediate Technical''' - some experience of server administration, can install and manage web services software via guides, can use ssh and commandline interface
*'''Basic Technical''' - no experience with server management. Can use software management interfaces such as CPanel
Hosting a website that can withstand various malicious attacks and unauthorised access is not an easy task. There are several approaches to mitigating digital threats and reducing your site's vulnerabilities. There is no one''Required''' -fits-all solution however basic knowledge about Internet infrastructure and the site's owners or administrators addressing is required should plan for various contingencies well in advanceyou want to maintain anything on the Internet (Facebook, in lieu twitter, other social networks exempted) that is bound to last the test of their financial situation and technical expertisetime. This guide attempts Please read through [https://learn.equalit.ie/wiki/How_does_the_Internet_actually_work%3F HOW DOES THE INTERNET ACTUALLY WORK?] to describe several scenarios get the basics and various approaches for secure hostinggo on from there. You need to know a little bit about architecture before building your house.
==Step1: What are you planning to host?==
*[[Website]] - standalone website, blog, forum
*[[Internet Server]] - mail server, VPN, proxy, VoIP server
*[[Web_application | Web Application]] - custom database, in-browser application
==Step 2: What are your hosting options==
*[[Choose a hosting provider]]
*[[Choose a DNS providername registrar]]*[[Data location Geography, lesgislation and terms of service]]
==Step 3: Plan for contingency and threat mitigation==
For each form of system use relevant threats and strategies to mitigate them are include. These approaches are ordered in terms of technical ability requirements. The following topics are relevant to all setups:
*[[System_Management|System Management]]*[[ Data_Backup | Data backup and recovery]]*[[Password_Management | Password managementAccess Restrictions]]*[[Data_Encryption | Data Encryption]]*[[Secure_Communications | Monitoring]]*[[Webserver setup]]*[[Secure communicationsconnections]]*[[Brute_Force_DDOS | Brute force and Denial of Service and Brute Force attacks]]
==Step 4: Decide on your level of technical expertise==
Throughout this guide we will use the following key to differentiate the difficulty level associated with each type of system setup. More technically complicated setups will require either permanent IT staff or access to an IT provider. The latter may be limited by an organisation financial resources.
*'''High Technical''' - multiple experiences of server administration, can confidently install/update server software; apache, mysql mail server
*'''Intermediate Technical''' - some experience of server administration, can install and manage software via guides, can use ssh and commandline interface
*'''Basic Technical''' - no experience, can use software management interfaces such as CPanel
[[Category: Secure Hosting]]
Dmitri
Bureaucrat, emailconfirmed, administrator, translator
662
edits
Retrieved from "https://learn.equalit.ie/wiki/Special:MobileDiff/155...565"