<?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>Web Admin Blog &#187; most</title>
	<atom:link href="http://www.webadminblog.com/index.php/tag/most/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webadminblog.com</link>
	<description>Real Web Admins.  Real World Experience.</description>
	<lastBuildDate>Wed, 25 May 2011 03:02:28 +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>The 10 Least-Likely and Most Dangerous People on the Internet</title>
		<link>http://www.webadminblog.com/index.php/2009/11/13/the-10-least-likely-and-most-dangerous-people-on-the-internet/</link>
		<comments>http://www.webadminblog.com/index.php/2009/11/13/the-10-least-likely-and-most-dangerous-people-on-the-internet/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 18:15:25 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[OWASP AppSec DC 2009]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[companies]]></category>
		<category><![CDATA[dangerous]]></category>
		<category><![CDATA[hansen]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[most]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[robert]]></category>
		<category><![CDATA[rsnake]]></category>
		<category><![CDATA[worst]]></category>

		<guid isPermaLink="false">http://www.webadminblog.com/?p=338</guid>
		<description><![CDATA[This presentation was by Robert "RSnake" Hansen and was designed to be a fun conversation to have over drinks with security people.  I feel privileged to have been one of those security people who he talked about this with beforehand.  A very interesting topic about the non-obvious threats that may or may not exist.   [...]]]></description>
			<content:encoded><![CDATA[<p>This presentation was by Robert "RSnake" Hansen and was designed to be a fun conversation to have over drinks with security people.  I feel privileged to have been one of those security people who he talked about this with beforehand.  A very interesting topic about the non-obvious threats that may or may not exist.   My notes are below:</p>
<p><span style="text-decoration: underline;"><strong>Why?</strong></span></p>
<ul>
<li>Because I use the Internet</li>
<li>Because I'm a target</li>
<li>Because most people don't know</li>
<li>Because it's a fun conversation to have over drinks with security guys</li>
<li>Maybe/hopefully you'll continue this conversation instead of just arguing!</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Ground Rules</strong></span></p>
<ul>
<li>Must be non-obvious and must be directly related to the Internet.  Not:
<ul>
<li>...the President or any other gov'ernment official</li>
<li>...or someone involved with SCADA Systems/Brick and mortar</li>
</ul>
</li>
<li>Must be in control of some infrastructure or software, etc</li>
<li>Must have the largest or widest negative impact possible for the least amount of work and least likelihood of being stopped</li>
<li>No magic - must be real and dangerous</li>
<li>They can't be "bad" people</li>
<li>You can't take this list too seriously</li>
</ul>
<p><span style="text-decoration: underline;"><strong>How I Got Started</strong></span></p>
<ul>
<li>Started thinking about core technologies that everything relies on</li>
<li>Made a big list</li>
<li>Shopped it around to dozens of security experts</li>
<li>Assigned an arbitrary, unscientific, hand-wavy, risk-rating system of my own design</li>
<li>Ranked them in order of how scared I am of them personally</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#10</strong></span></p>
<ul>
<li>John Doe at C|Net</li>
<li>Job: Network Engineer</li>
<li>Why: Controls com.com</li>
<li>Impact: Largest collection point of typo traffic both for web adn email.
<ul>
<li>Doesn't require anything overt or even indefensible</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#9</strong></span></p>
<ul>
<li>Giorgio Maone of NoScript</li>
<li>Job: Consultant</li>
<li>Why: Controls NoScript</li>
<li>Impact: Nearly every security researcher on the planet - complete compromise.  In general the most paranoid people on earth would be compromised.
<ul>
<li>Builds arbitrary whitelists (ebay.com)</li>
<li>Has changed functionality to subvert Adblock Plus</li>
</ul>
</li>
</ul>
<p><span id="more-338"></span></p>
<p><span style="text-decoration: underline;"><strong>#8</strong></span></p>
<ul>
<li>Eddy Nigg at StartCom Ltd...
<ul>
<li>or John Doe at SSL Cert Reseller</li>
</ul>
</li>
<li>Job: Developer/QA</li>
<li>Why: Has access to create wildcard SSL certs for any domain</li>
<li>Impact: Would allow an attacker to steal any information they were able to man in the middle.
<ul>
<li>Previously demonstrated bad security</li>
<li>Much smaller and therefore less controlled than Verisign or Thawt</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#7</strong></span></p>
<ul>
<li>John Doe at Authorize.net</li>
<li>Job: Network admin/Server admin</li>
<li>Why: Has the ability to see the vast majority of online transactions.</li>
<li>Impact: Would allow an attacker to get PII and credit card information for the bulk of the US online shopping population and many international shoppers as well</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#6 (RSnake recants this one after dinner last night)<br />
</strong></span></p>
<ul>
<li>John Doe at Mozilla</li>
<li>Job: Has check-in access</li>
<li>Why: Has the ability to change functionality within the browser, including installing new SSL certs.</li>
<li>Impact: Would allow the attacker to man in the middle and read all SSL traffic.
<ul>
<li>Almost no documentation</li>
<li>The verification process is very open and subject to tampering - meaning the update mechanism isn't probably much better</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#5</strong></span></p>
<ul>
<li>Chirag and Floyd at Adwords</li>
<li>Job: Whomever checks in code</li>
<li>Why: Has access to millions of websites because it is XSS</li>
<li>Impact: Can be leveraged for stealing cookies and hijacking web functionality
<ul>
<li>Is embedded in millions of web pages</li>
<li>Is already obfuscated heavily</li>
<li>Is seen daily by the bulk of the Internet population</li>
<li>Begs the question about CDNs in particular</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#4</strong></span></p>
<ul>
<li>John Doe at Google's Postini</li>
<li>Job: Programmer/Server admin</li>
<li>Why: Controls and can view the bulk of the world's email - including Gmail</li>
<li>Impact: Would enable attacker to steal credentials, spoof conversations, tamper with data, introduce malware, etc
<ul>
<li>More dangerous than Adwords because it's passive</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#3</strong></span></p>
<ul>
<li>John Doe at 1 Wilshire</li>
<li>Job: NOC Monkey</li>
<li>Why: One of the largest peering centers on the west coast</li>
<li>Impact: Can tamper with machines, install malware, inject malicious traffic, intercept communications, etc...
<ul>
<li>Most amount of data links in one physical location</li>
<li>CIA has already demonstrated interest in choke points in San Francisco as outed by Mark Klein</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#2</strong></span></p>
<ul>
<li>John Doe at gtei.net</li>
<li>Job: Network Admin/Server Admin</li>
<li>Why: Controls 4.2.2.2 and 4.2.2.3</li>
<li>Impact: Can be used to subvert a huge chunk of Internet traffic by giving erroneous DNS answers
<ul>
<li>Used by default in many devices</li>
<li>Used by tons of individuals and companies who are lazy</li>
<li>Can be used in very targeted attacks for a very short period of time</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#1</strong></span></p>
<ul>
<li>John Doe at iDefense</li>
<li>Job: Security Engineer/Consultant</li>
<li>Why: Consults for and is owned by Verisign, who owns Network Solutions, who controls authoritative DNS for ".com"</li>
<li>Impact: Would allow the bulk of the Internet traffic to be modified
<ul>
<li>Heavily monitored and protected but still could lead to temporary and targeted compromise</li>
<li>More dangerous than 4.2.2.2 because it controls all of .com and not just a subset of users</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Disappointed?  Upset?</strong></span></p>
<p>The room is full of people who care that your feelings are hurt.</p>
<p>The List</p>
<ol>
<li>John Doe at iDefense</li>
<li>John Doe at gtei.net</li>
<li>John Doe at 1 Wilshire</li>
<li>John Doe at Google's Postini</li>
<li>Chirag and Floyd at Adwords</li>
<li>John Doe at Mozilla</li>
<li>John Doe at Authorize.net</li>
<li>Eddy Nigg at StartCom Ltd.</li>
<li>Giorgio Maone of NoScript</li>
<li>John Doe at C|Net</li>
</ol>
<p><span style="text-decoration: underline;"><strong>Questions/Comments?</strong></span></p>
<ul>
<li>Robert Hansen
<ul>
<li>Robert_at_sectheory d0t c0m</li>
<li>http://www.sectheory.com</li>
<li>http://ha.ckers.org/</li>
<li>Detecting Malice
<ul>
<li>http://www.detectmalice.com/</li>
</ul>
</li>
<li>XSS Book: XSS Exploits and Defense
<ul>
<li>ISBN: 1597491543</li>
</ul>
</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.webadminblog.com/index.php/2009/11/13/the-10-least-likely-and-most-dangerous-people-on-the-internet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

