<?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>Cisco Blog &#187; incident response</title>
	<atom:link href="http://blogs.cisco.com/tag/incident-response/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.cisco.com</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 18:51:19 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Coordinated Attacks Against the U.S. Government and Banking Infrastructure</title>
		<link>http://blogs.cisco.com/security/coordinated-attacks-against-the-u-s-government-and-banking-infrastructure/</link>
		<comments>http://blogs.cisco.com/security/coordinated-attacks-against-the-u-s-government-and-banking-infrastructure/#comments</comments>
		<pubDate>Wed, 01 May 2013 19:11:28 +0000</pubDate>
		<dc:creator>Mike Schiffman</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[advisories]]></category>
		<category><![CDATA[ASA]]></category>
		<category><![CDATA[botnet]]></category>
		<category><![CDATA[botnets]]></category>
		<category><![CDATA[Cisco Security]]></category>
		<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[cloud security]]></category>
		<category><![CDATA[data center security]]></category>
		<category><![CDATA[DDoS]]></category>
		<category><![CDATA[exploits]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[incident response]]></category>
		<category><![CDATA[IPS]]></category>
		<category><![CDATA[IPS signatures]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[mitigations]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[targeted attacks]]></category>
		<category><![CDATA[TRAC]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=111984</guid>
		<description><![CDATA[Prologue On April 10, 2013, a collective of politically motivated  <a href="http://en.wikipedia.org/wiki/Hacktivism">hacktivists</a>  announced a round of planned attacks called  <a href="http://pastebin.com/0HH61ev4">#OPUSA</a> . These attacks, [...]]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/coordinated-attacks-against-the-u-s-government-and-banking-infrastructure/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>I Can’t Keep Up with All These Cisco Security Advisories: Do I Have to Upgrade?</title>
		<link>http://blogs.cisco.com/security/i-cant-keep-up-with-all-these-cisco-security-advisories-do-i-have-to-upgrade/</link>
		<comments>http://blogs.cisco.com/security/i-cant-keep-up-with-all-these-cisco-security-advisories-do-i-have-to-upgrade/#comments</comments>
		<pubDate>Tue, 02 Apr 2013 13:00:48 +0000</pubDate>
		<dc:creator>Omar Santos</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[advisories]]></category>
		<category><![CDATA[CVSS]]></category>
		<category><![CDATA[cybersecurity]]></category>
		<category><![CDATA[exploits]]></category>
		<category><![CDATA[incident response]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[psirt]]></category>
		<category><![CDATA[security advisories]]></category>
		<category><![CDATA[security advisory]]></category>
		<category><![CDATA[security notice]]></category>
		<category><![CDATA[security notices]]></category>
		<category><![CDATA[security top of mind]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=108217</guid>
		<description><![CDATA["A security advisory was just published! Should I hurry and upgrade all my Cisco devices now?" This is a question that I am being asked by customers on a regular basis. In fact, I am also asked why there are so many security vulnerability advisories. To start with the second question: Cisco is committed to protecting customers by sharing critical security-related information in a very transparent way. Even if security vulnerabilities are found internally, the Cisco Product Security Incident Response Team (PSIRT) – which is my team – investigates, drives to resolution, and discloses such vulnerabilities. To quickly answer the first question, don't panic, as you may not have to immediately upgrade your device. However, in this article I will discuss some of the guidelines and best practices for responding to Cisco security vulnerability reports.]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/i-cant-keep-up-with-all-these-cisco-security-advisories-do-i-have-to-upgrade/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Targeted Attack, Targeted Response:  Designing and Implementing an Incident Response Plan That Works</title>
		<link>http://blogs.cisco.com/security/targeted-attack-targeted-response-designing-and-implementing-an-incident-response-plan-that-works/</link>
		<comments>http://blogs.cisco.com/security/targeted-attack-targeted-response-designing-and-implementing-an-incident-response-plan-that-works/#comments</comments>
		<pubDate>Tue, 04 Sep 2012 14:30:20 +0000</pubDate>
		<dc:creator>Omar Santos</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[incident response]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=81659</guid>
		<description><![CDATA[The security landscape has changed dramatically over the last couple of years and is expected to change even more going forward and most likely at a more rapid rate than we’ve seen in the past. Subsequently, incident response methodologies have to adapt.]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/targeted-attack-targeted-response-designing-and-implementing-an-incident-response-plan-that-works/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Compromised Accounts, Stepping Stones</title>
		<link>http://blogs.cisco.com/security/compromised-accounts-stepping-stones/</link>
		<comments>http://blogs.cisco.com/security/compromised-accounts-stepping-stones/#comments</comments>
		<pubDate>Tue, 17 Jul 2012 18:49:23 +0000</pubDate>
		<dc:creator>Jeff Shipley</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[event monitoring]]></category>
		<category><![CDATA[incident response]]></category>
		<category><![CDATA[password manager]]></category>
		<category><![CDATA[passwords]]></category>
		<category><![CDATA[situational awareness]]></category>
		<category><![CDATA[targeted attacks]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=76779</guid>
		<description><![CDATA[The list of account compromises over the past week is almost too long to list, and the numbers of verified [...]]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/compromised-accounts-stepping-stones/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Product Security Incident Managers…A Closer Look</title>
		<link>http://blogs.cisco.com/security/product-security-incident-managersa-closer-look/</link>
		<comments>http://blogs.cisco.com/security/product-security-incident-managersa-closer-look/#comments</comments>
		<pubDate>Thu, 12 Jul 2012 16:22:29 +0000</pubDate>
		<dc:creator>Mike Adler</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[incident]]></category>
		<category><![CDATA[incident response]]></category>
		<category><![CDATA[psirt]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=76261</guid>
		<description><![CDATA[This article gives the reader an insider's look into the life of a Cisco Product Security Incident Response Team (PSIRT) member, the roles and responsibilities of PSIRT, and the processes and procedures that are followed by PSIRT Incident Managers (IMs).]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/product-security-incident-managersa-closer-look/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JetBlue Pilot Incident and Expected Response?</title>
		<link>http://blogs.cisco.com/security/jetblue-pilot-incident-and-expected-response/</link>
		<comments>http://blogs.cisco.com/security/jetblue-pilot-incident-and-expected-response/#comments</comments>
		<pubDate>Fri, 06 Apr 2012 19:03:47 +0000</pubDate>
		<dc:creator>Jeff Shipley</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[incident response]]></category>
		<category><![CDATA[physical security]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=65613</guid>
		<description><![CDATA[In our weekly review call for the Cisco Cyber Risk Report for March 26-April 1, 2012 we discussed the incident of the JetBlue mid-air emergency incident.  The incident has been widely reported, but a short summary is that the pilot was reportedly acting irrationally, which caused the co-pilot to lock him out of the cockpit and led to the crew and passengers having to subdue him until the aircraft could be landed and authorities removed the pilot.  While the investigation of this incident continues, there have also been several of these types of incidents.  A review of the incident raised several security questions with us over the incident response policies and procedures. ]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/jetblue-pilot-incident-and-expected-response/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
