<?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>Immutable Security &#187; Social Engineering</title>
	<atom:link href="http://www.immutablesecurity.com/index.php/tag/social-engineering/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.immutablesecurity.com</link>
	<description>Information Security, Privacy and Personal Liberty</description>
	<lastBuildDate>Sun, 04 Dec 2011 00:03:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>An Analysis of the Analysis of the Apache.org Attack</title>
		<link>http://www.immutablesecurity.com/index.php/2010/04/18/an-analysis-of-the-analysis-of-the-apache-org-attack/</link>
		<comments>http://www.immutablesecurity.com/index.php/2010/04/18/an-analysis-of-the-analysis-of-the-apache-org-attack/#comments</comments>
		<pubDate>Mon, 19 Apr 2010 00:43:15 +0000</pubDate>
		<dc:creator>Michael Starks</dc:creator>
				<category><![CDATA[Computer Crime]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Incident Response]]></category>
		<category><![CDATA[Intrusion Detection]]></category>
		<category><![CDATA[Log Analysis]]></category>
		<category><![CDATA[Secure Administration]]></category>
		<category><![CDATA[Secure Design]]></category>
		<category><![CDATA[Systems Hardening]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[Breaches]]></category>
		<category><![CDATA[Social Engineering]]></category>

		<guid isPermaLink="false">http://www.immutablesecurity.com/?p=484</guid>
		<description><![CDATA[Over at the Apache blog, you&#8217;ll find a nice and detailed incident report on the recent, successful attack on Apache.org. I thought it might be worth a few minutes to share my thoughts on their write-up. First, I would like to say that the level of transparency in this response is truly commendable. Rather than [...]]]></description>
			<content:encoded><![CDATA[<p>Over at the Apache blog, you&#8217;ll find a <a href="https://blogs.apache.org/infra/entry/apache_org_04_09_2010" target="_blank">nice and detailed incident report</a> on the recent, successful attack on Apache.org. I thought it might be worth a few minutes to share my thoughts on their write-up.</p>
<p>First, I would like to say that the level of transparency in this response is truly commendable. Rather than sweep this under the rug, they have chosen to share the details of what happened, why it happened (more on that in a moment) and what their plans are to, hopefully, prevent future breaches.</p>
<p>I encourage you to read the entire post, because it is a good account of how actual, real-world attacks happen. Targeted attacks take advantage of trust (both in people and machines), shared and weak passwords, too much privilege and an assortment of other security 101 vulnerabilities.</p>
<p>The attacks consisted of a XSS vulnerability, brute-force logins, a shortened URL, password sniffing, password re-use and social engineering. Pretty typical stuff, really.</p>
<p>What I find most interesting about this report is the emphasis on technical countermeasures in the <span style="text-decoration: underline;">What are we Changing?</span> section, when the attack succeeded primarily due to vulnerabilities in human beings.</p>
<ul>
<li>The Infrastructure Team members clicked on a cloaked and untrusted link, which launched a XSS attack.</li>
<li>A brute force login succeeded against a poorly chosen password. But prior to it being successful, no one seemed to be getting alerts on so many failed login attempts.</li>
<li>They once again exploited the Infrastructure Team by getting them to log in with a password that the team members, themselves, did not choose.</li>
<li>They took advantage of cached passwords on the server.</li>
<li>Slicehost didn&#8217;t respond to the attack when notified, which enabled one host to continue its attack against someone else.</li>
</ul>
<p>These are all people issues. It&#8217;s the same stuff that we security types have been trying to hammer into the brains of people for years now. There are certainly technical countermeasures which could have helped, but this was an attack on people.</p>
<p>It&#8217;s easy for us to play armchair quarterback and be critical of the response, however that is not my intention, Rather, it is my intent to simply cast another light on the response so we can all learn and secure our assets more effectively.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.immutablesecurity.com/index.php/2010/04/18/an-analysis-of-the-analysis-of-the-apache-org-attack/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Social Engineering from a Three Year Old</title>
		<link>http://www.immutablesecurity.com/index.php/2010/02/16/social-engineering-from-a-three-year-old/</link>
		<comments>http://www.immutablesecurity.com/index.php/2010/02/16/social-engineering-from-a-three-year-old/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 19:16:58 +0000</pubDate>
		<dc:creator>Michael Starks</dc:creator>
				<category><![CDATA[Dialogue]]></category>
		<category><![CDATA[Social Engineering]]></category>

		<guid isPermaLink="false">http://www.immutablesecurity.com/?p=436</guid>
		<description><![CDATA[My three-year old recently tried to social engineer her mother and I. The conversation went something like this: Daughter: I want some milk. Mom: You can&#8217;t have milk right now, honey. You have a cold. How about some juice? Daughter: I don&#8217;t have a cold any more, I gave it to Grandma. Nice try, little [...]]]></description>
			<content:encoded><![CDATA[<p>My three-year old recently tried to social engineer her mother and I. The conversation went something like this:</p>
<blockquote><p>Daughter: I want some milk.</p>
<p>Mom: You can&#8217;t have milk right now, honey. You have a cold. How about some juice?</p>
<p>Daughter: I don&#8217;t have a cold any more, I gave it to Grandma.</p></blockquote>
<p>Nice try, little girl, but your evil plan is foiled!</p>
<p>Little does she realize that giving a cold to someone does not mean that you get rid of it.</p>
<p>Until next time, daughter. Until next time&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.immutablesecurity.com/index.php/2010/02/16/social-engineering-from-a-three-year-old/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

