<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IntoVPS Blog &#187; VPS Administration</title>
	<atom:link href="http://www.intovps.com/blog/category/vps-administration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.intovps.com/blog</link>
	<description>VPS Hosting</description>
	<lastBuildDate>Mon, 23 Jan 2012 16:17:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Basic VPS security checklist</title>
		<link>http://www.intovps.com/blog/2010/02/20/basic-vps-security-checklist/</link>
		<comments>http://www.intovps.com/blog/2010/02/20/basic-vps-security-checklist/#comments</comments>
		<pubDate>Sat, 20 Feb 2010 16:56:57 +0000</pubDate>
		<dc:creator>Adrian Andreias</dc:creator>
				<category><![CDATA[VPS Administration]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[europe vps]]></category>
		<category><![CDATA[secuirty]]></category>

		<guid isPermaLink="false">http://www.intovps.com/blog/?p=122</guid>
		<description><![CDATA[Every once in a while we have a customer that has been hacked. So I decided to make a short TO DO list for basic VPS security. Obviously security is a vast subject and you should hire a system administrator to take care of your VPS security if you don&#8217;t have the know how. Anyways, [...]]]></description>
			<content:encoded><![CDATA[<p>Every once in a while we have a customer that has been hacked. So I decided to make a short TO DO list for basic VPS security. Obviously security is a vast subject and you should hire a system administrator to take care of your VPS security if you don&#8217;t have the know how.</p>
<p>Anyways, here&#8217;s the basic list:</p>
<ol>
<li><strong>Use strong passwords.</strong> Your passwords must have at least 8 characters (preferably more) and include all of the following: small and upper case letters, numbers and a few special signs, like: !@#$%^&amp;*()_+{}|:&#8221;?&gt;&lt;[]\&#8217;;/,. Or setup keys for SSH authentication. This applies for the root passwords, Hypanel account password and any user account from your VPS.</li>
<li><strong>Update your server.</strong> First time you login to SSH you should update your system (<strong>yum update</strong> in CentOS and alike, <strong>apt-get upgrade</strong> in Ubuntu and alike). The OS template that was used when deploying your system may not be up to date. Although we&#8217;re trying to keep all OS templates up to date, doing this for 30+ templates and tweaking new releases for OpenVZ is quite some work.</li>
<li><strong>And keep your server up to date.</strong> Make sure you update frequently or set up an update daemon/cron.</li>
<li><strong>Disable all daemons/services that you don’t need.</strong> For instance, if you need just VPN, it doesn’t make sense to run a mail server or web server. This will reduce the attack surface on your server and you won&#8217;t be affected by some of the software vulnerabilities. And you&#8217;ll have more memory available for the system processes that you need <img src='http://www.intovps.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> .</li>
<li><strong>Don&#8217;t give your root password to people you don&#8217;t know or don&#8217;t trust.</strong> We had some incidents with customers that picked up some guy on some forum which &#8220;secured&#8221; his VPS. Turned out that the &#8220;security guy&#8221; just wanted a machine for spamming.</li>
<li><strong>Consider changing the default ports</strong>. For instance for SSH configure port 2421 (this is just a random number that cropped up from my keyboard <img src='http://www.intovps.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  ), instead of default 22. But don&#8217;t rely on this too much, while some of the automatic bots that do brute force will try just on port 22, there&#8217;s no excuse for having a weak password.</li>
</ol>
<p>Again, this is just a basic list. Talk to a professional system administrator if you don&#8217;t have the knowledge or you don&#8217;t have the time.</p>
<p>What is your  basic security check list?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.intovps.com/blog/2010/02/20/basic-vps-security-checklist/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

