<?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>Startup Security &#187; Incident Response</title>
	<atom:link href="http://startupsecurity.info/blog/category/incident-response/feed/" rel="self" type="application/rss+xml" />
	<link>http://startupsecurity.info</link>
	<description>Security, for Startups</description>
	<lastBuildDate>Wed, 16 Dec 2009 18:42:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Incident Response Cheatsheets</title>
		<link>http://startupsecurity.info/blog/2008/11/20/incident-response-cheatsheets/</link>
		<comments>http://startupsecurity.info/blog/2008/11/20/incident-response-cheatsheets/#comments</comments>
		<pubDate>Fri, 21 Nov 2008 04:46:24 +0000</pubDate>
		<dc:creator>Damon Cortesi</dc:creator>
				<category><![CDATA[Incident Response]]></category>
		<category><![CDATA[Compromise]]></category>
		<category><![CDATA[Forensics]]></category>

		<guid isPermaLink="false">http://startupsecurity.info/?p=105</guid>
		<description><![CDATA[One of the things any organization should be prepared for is a potential &#8220;incident&#8221;. The definition of incident can vary widely, but it can be anything from an unauthorized internal data access to a &#8220;hacker&#8221; breaking in. 
Monitoring is a big part of detecting incidents and perhaps a post for another day. If you do [...]]]></description>
			<content:encoded><![CDATA[<p>One of the things any organization should be prepared for is a potential &#8220;incident&#8221;. The definition of incident can vary widely, but it can be anything from an <a href="http://www.cnn.com/2008/POLITICS/11/20/obama.cell.breach/index.html?eref=rss_topstories">unauthorized internal data access</a> to a &#8220;hacker&#8221; <a href="http://www.time.com/time/politics/article/0,8599,1842097,00.html">breaking in</a>. </p>
<p>Monitoring is a big part of detecting incidents and perhaps a post for another day. If you do suspect somebody has unauthorized access to one of your systems, though, there are certain steps that should be taken. I recently came across a good <a href="http://www.zeltser.com/network-os-security/security-incident-survey-cheat-sheet.html">cheat sheet for server administrators</a> that should be kept handy in the event of an incident. There&#8217;s also a cheatsheet for those <a href="http://www.zeltser.com/network-os-security/security-incident-questionnaire-cheat-sheet.html">responding to potential incidents</a>.</p>
<p>I came across these cheatsheets over on the <a href="http://isc.sans.org/">SANS Internet Storm Center</a> blog, a good feed to have in your reader to keep up-to-date on the latest security incidents around the net.</p>
<p>Enjoy, and hopefully you won&#8217;t need to reach for these in the near future. But they are good to have on hand!</p>
]]></content:encoded>
			<wfw:commentRss>http://startupsecurity.info/blog/2008/11/20/incident-response-cheatsheets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
