<?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>ZZTopping &#187; security</title>
	<atom:link href="http://blog.zztopping.com/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.zztopping.com</link>
	<description>A Blog by a Non-Blogger</description>
	<lastBuildDate>Tue, 09 Aug 2011 02:25:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Simple Debian Lockdown(for those of you under NESSUS scrutiny)</title>
		<link>http://blog.zztopping.com/2008/06/19/simple-debian-lockdown/</link>
		<comments>http://blog.zztopping.com/2008/06/19/simple-debian-lockdown/#comments</comments>
		<pubDate>Thu, 19 Jun 2008 19:08:39 +0000</pubDate>
		<dc:creator>ZZTopping</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[lockdown]]></category>
		<category><![CDATA[nessus]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blog.zztopping.com/?p=17</guid>
		<description><![CDATA[There are a million ways to lock down a server. I prefer the non-paranoid method, since none of the data I work with is valuable enough warranting all the extra setup for paranoia-mode. I recommend the following three, very simple, tasks to lock down your Linux server(specifically Debian Etch). Prevent root logins from SSH Turn [...]]]></description>
			<content:encoded><![CDATA[<p>There are a million ways to lock down a server. I prefer the non-paranoid method, since none of the data I work with is valuable enough warranting all the extra setup for paranoia-mode.</p>
<p>I recommend the following three, very simple, tasks to lock down your Linux server(specifically Debian Etch).</p>
<ol>
<li>Prevent root logins from SSH</li>
<li>Turn off ident</li>
<li>Disable RPC(only do this if you do not use NFS)</li>
</ol>
<p>Preventing root logins via SSH is a good idea for two reasons.</p>
<ul>
<li>Allows you to accurately log who is accessing your system&#8230;root can be somewhat anonymus if people know the password.</li>
<li>If someone who does know the root password becomes a threat, you simple have to restrict their username from being granted access(and physical security of course). This is a lot better than haveing to change the root password in a pinch (I like not having to update documentation every time someone leaves my company).</li>
</ul>
<p>Removing Ident is merely to make NESSUS complain less. Its not really needed so lets shut it off.</p>
<ul>
<li>Open <strong>/etc/inetd.conf</strong> in Vi/Emacs/whatever</li>
<li>Comment out the line that begins with ident(just add a # at the beginning of the line)</li>
<li>Save the file and restart inetd:  <strong>/etc/init.d/inetd restart</strong></li>
</ul>
<p>Finally, another thing to make NESSUS happy is to disable RPC if you arent using it(NFS shares mainly). Simple remove the package portmap from your system. On Debian: <strong>apt-get remove portmap</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zztopping.com/2008/06/19/simple-debian-lockdown/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

