<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Security</title>
  <subtitle>IT Security</subtitle>
  <link rel="alternate" type="text/html" href="http://stevenimmons.org/content/technology/security"/>
  <link rel="self" type="application/atom+xml" href="http://stevenimmons.org/taxonomy/term/28/atom/feed"/>
  <id>http://stevenimmons.org/taxonomy/term/28/atom/feed</id>
  <updated>2008-05-20T22:39:26-07:00</updated>
  <entry>
    <title>Watch out for the Weather Crooks</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/steve-nimmons/02092008/watch-out-weather-crooks" />
    <id>http://stevenimmons.org/blogs/steve-nimmons/02092008/watch-out-weather-crooks</id>
    <published>2008-09-02T10:24:46-07:00</published>
    <updated>2008-09-02T03:28:40-07:00</updated>
    <author>
      <name>Steve-Nimmons</name>
    </author>
    <category term="Crime" />
    <category term="Security" />
    <summary type="html"><![CDATA[<p><img src="http://stevenimmons.org/images/gangster.jpg" alt="" /></p>
<p>Computerworld <a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9113918&amp;intsrc=hm_list">is reporting</a> that over 100 domains have been registered in the past 48 hours relating to hurricane Gustav.</p>
<p>Although not all will have nefarious purposes, security experts are warning people to be careful of phishing scams and bogus charity scams that might emerge as relief operations go into full swing.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p><img src="http://stevenimmons.org/images/gangster.jpg" alt="" /></p>
<p>Computerworld <a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9113918&amp;intsrc=hm_list">is reporting</a> that over 100 domains have been registered in the past 48 hours relating to hurricane Gustav.</p>
<p>Although not all will have nefarious purposes, security experts are warning people to be careful of phishing scams and bogus charity scams that might emerge as relief operations go into full swing.</p>
<p>It's a sad fact that there are people in this world prepared to steal from the needy. Let's not make their 'job' easy...</p>
    ]]></content>
  </entry>
  <entry>
    <title>Web2.0, Social Engineering and Reputation Protection</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/steve-nimmons/07082008/web20-social-engineering-and-reputation-protection" />
    <id>http://stevenimmons.org/blogs/steve-nimmons/07082008/web20-social-engineering-and-reputation-protection</id>
    <published>2008-08-07T07:29:05-07:00</published>
    <updated>2008-08-21T04:00:30-07:00</updated>
    <author>
      <name>Steve-Nimmons</name>
    </author>
    <category term="Enterprise 2.0" />
    <category term="Enterprise Social Software" />
    <category term="Security" />
    <category term="Social Media" />
    <category term="Social Networking" />
    <category term="Twitter" />
    <category term="Web2.0" />
    <summary type="html"><![CDATA[<p><img alt="Pick Pocket" src="http://stevenimmons.org/images/pickpocket.jpg" /></p>
<p>By <a href="http://stevenimmons.org/content/site-information/author/steve-nimmons" target="_blank">Steve Nimmons</a></p>
    ]]></summary>
    <content type="html"><![CDATA[<p><img alt="Pick Pocket" src="http://stevenimmons.org/images/pickpocket.jpg" /></p>
<p>By <a href="http://stevenimmons.org/content/site-information/author/steve-nimmons" target="_blank">Steve Nimmons</a></p>
<p>I recall (approximately 8 years ago) reading an interesting poster on social engineering at a well-known electronics company in California. The &lsquo;wall-chart&rsquo; communicated sensible advice for dealing with unsolicited phone calls, &lsquo;chance&rsquo; conversations and the importance of discretion when discussing corporate matters on planes, trains and automobiles. Tail gating and the &lsquo;risk of gallantry&rsquo;, the social and psychological tricks used by experienced practitioners to &lsquo;project belonging&rsquo;, the need for discretion and vigilance in public spaces and of course &lsquo;clear desk policies&rsquo; were topics explained in concise, relevant and accessible language. Workforces across this and other enterprises were equipped to deal with the primary aspects of corporate social manipulation. In-house and industry standards shared the wisdom of primary threats, expected behaviours and above all encouraged staff training and awareness.</p>
<p>I visited many technology start-ups during this period. Their social engineering concerns centred on leakage of financial data and intellectual property. With looming IPO (Initial Public Offering) these companies had a lot to lose, the wrong information entering the market at the wrong time being potentially damaging to earnings. Intellectual property was naturally their core competitive differentiator and was suitably protected, including legally through patents and nondisclosure agreements. It was clear what they feared, why they feared it and that they were being proactive in terms of minimising their overall exposure to risk.</p>
<p>Perimeter defences with clear corporate boundaries and technological barriers primarily tamed Web1.0.</p>
<p>Fast-forward 8 years and with the introduction and exponential uptake of Web2.0 it is fascinating (indeed crucial) to explore the considerations for similarly intentioned advice today.</p>
<p>When discussing the Web2.0 revolution I emphasise the &lsquo;practical&rsquo; removal of technological barriers to content publication. Blogs, wikis, forums, social bookmarking and social networks are a selection of means by which individuals can share and debate views (single click, no safety catch). As we discovered (or perhaps suffered) in the past few years, this medium provides ideal conditions for libel, defamation (perhaps creating internal conflict or damaging partner relationships), careless divulgence and the association of the individual and corporations with unflattering and potentially damaging material. These are arguably Web2.0&rsquo;s most concerning corporate side effects. The individual is the power-broker of Web2.0 and with microblogging (particularly Twitter) tipped for &lsquo;meteoric success&rsquo; I think we will see even less control exercised over what are essentially globally distributed sound-bytes. Pseudonyms provide anonymity, personally or corporately identifiable profiles &lsquo;should&rsquo; engender a greater spirit of due care and present an opportunity for positive self and corporate marketing (for example blogging and thought leadership initiatives). But what needs to be understood clearly is that the search engines with their omnipresence &lsquo;discover our sins&rsquo;. The Web and blogosphere contains a cacophony of voices inside which they are the &lsquo;great eavesdroppers and intelligence agents&rsquo;. In print media, yesterday&rsquo;s news wrapped today&rsquo;s fish and chips, but in the electronic age opinion has an almost immortal quality. Search engines have a unique ability to &lsquo;discover&rsquo; and neatly present information that we may prefer remained &lsquo;hidden&rsquo;.</p>
<p>There is an adage that Web2.0 profiles are like tattoos, something you do when you are young and live to regret. With appropriate controls, education and consideration however we can seek to accentuate the positives and in sophisticated cases utilise them in personal branding and corporate marketing strategies.</p>
<p>Where once scraper and &lsquo;shill&rsquo; sites were padded with &lsquo;pointless&rsquo; copies of the Open Directory Project (an old trick to create thousands of pages to bloat a website that was then packed with affiliate programmes and click through advertising) they are now extracting content from RSS feeds, quite a number scraping via Technorati tags that simply mirror their underlying site&rsquo;s (content) taxonomy. I use Technorati tags to categorise content for improved searching and user experience. I am often &lsquo;amused&rsquo; to see how my articles are &lsquo;aggregated&rsquo; onto these sites totally against copyright and any sense of appropriate ownership and control. In some cases the use of such content may be beneficial (e.g. off-site advertising), but consider wisely the potential for widespread distribution of commentary. Keep in mind traditional political and broadcasting advice &ldquo;treat every microphone as if it were live.&rdquo; Something said is difficult to retract in Web2.0&rsquo;s publishing model. This could affect personal reputation, privacy, cause corporate embarrassment or perhaps worse. Social engineers are astute, so be careful of being drawn into electronic conversations that should be avoided.</p>
<p>Solutions to some of these issues are emerging (e.g. online reputation protection services such as Reputation Defender, ClaimID and Naymz), suggesting the commercial and personal need for &lsquo;digital litter cleanup&rsquo;. Digital litter is all of those nuggets of information personally linked to you. Be under no illusion that the collective body of this information is being poured over by fraudsters and marketing companies and in the corporate realm by researchers and competitors. Information of course is not as volatile as might be imagined. Simply deleting it from the original source is no guarantee of its destruction, with scraper sites, search indexes and historical web caches adding to the complexity. Reputation protection may only dilute some of the problems rather than completely remove them.</p>
<p>We must of course accept freedom of speech and the right of fair criticism. In the Web2.0 domain our &lsquo;complaints&rsquo; may well be beyond any reasonable bounds of control. Corporate reputation is also tightly coupled with customer satisfaction, shareholder value, innovation and similar attributes. A key addition to the advice from 2000 is therefore minimising personal and corporate risk from worldwide electronic publishing in which &lsquo;everyone&rsquo; can act as content producers.</p>
<p>In conjunction with shifting the content producer to consumer ratio, Web2.0 has removed traditional corporate boundaries. In Unified Communications we talk about edgeless enterprises. Web2.0 warrants a special mention as it has &lsquo;eroded the edge&rsquo; by (as we have seen) technological simplicity, but also radical reappraisal of the psychology of home and work. In essence the erosion is catalysed by behavioural change and personal empowerment inherent in its purpose. The &lsquo;fear index&rsquo; of such a proposition (which is today&rsquo;s reality) is dependent on factors such as workforce size, employee trust and satisfaction, and employer sophistication. Sophistication in this regard I would describe as the ability to manage the distinct threats and opportunities of the modern (and emerging) Web.</p>
<p>I am unsurprisingly an ardent social networking enthusiast. My collaborative technology journey began with projects in Computer Supported Co-operative Work (CSCW) research in 1993. Looking back, our vision was of a more business-oriented (less entertainment driven) outcome. It was not a world we envisaged would be plagued by the &lsquo;unrighteous&rsquo;. LinkedIn, Facebook, Plaxo, MySpace, a myriad of others and the proliferation of associated groups, today provide a rich hunting ground for the social engineer. Companies can be significantly profiled, names, departments, reporting structures; nature of business, personal links, and networks can be mined and prioritised for further attack. It presents limited challenge to comb sites for information to employ in &lsquo;impersonation attacks&rsquo;, extracting additional detail through email, telephony and other channels. With no identity management (i.e. no established trust) it is simple to create fake pages, groups and details and use these to link the unwitting. IBM&rsquo;s recent announcement to create a private Second Life implementation is an interesting play to re-establish corporate boundaries (without stifling in-house collaborative and social benefits). I am opposed to blanket banning of social network access from corporate estates. Bans of this nature exhibit a glaring weakness, they end when employees are &lsquo;off the clock&rsquo;. They also restrict business benefit that could be derived from &lsquo;appropriate use&rsquo;. Understanding risk exposure, developing appropriate security policies, best practices and employee education are vital. Parental education is a recurring theme in the recent Byron Review (established in 2007 to study the online safety of children) and I draw parallels with employee and employer education in a similar vein.</p>
<p>Threats are &lsquo;evolutionary&rsquo; and social engineering is enjoying an up swell in volume and quality of unsolicited, freely and legally attainable information. Reputation protection faces new challenges due to the speed of content production and distribution, a mechanism of such simplicity and attractiveness that bewildering numbers have embraced it across &lsquo;previously untouched&rsquo; demographics. As digital footprints do not &lsquo;melt&rsquo; I remain concerned about the long-term impacts of careless experiences in Web2.0. There is a strong case for placing the onus on site providers to better protect privacy, but personal accountability must be advocated above all.</p>
<p>The key points that go on my updated &lsquo;wall-chart&rsquo; for 2008 are:</p>
<ul>
<li>Explaining risk exposure in terms of information leakage, libelous, defamatory or brand damaging activities that have indirect or direct association through the employee base. Public comments from identified staff being potentially detrimental to business reputation and relationships</li>
<li>The need to understand and in many cases limit the volume of available corporate data on personnel, roles, responsibilities and professional activities (the social engineering gold mine)</li>
<li>The expanding roles of Marketing and IT Security in meeting new threats and opportunities</li>
<li>The need for &lsquo;Web2.0 savvy&rsquo; security policies and training plans. It is no understatement that the proliferation of Web2.0 opens a sizeable number of holes in the sieve of corporate intelligence (take recent Facebook security leaks and social worms like Secret Crush as examples). Educated personnel make informed decisions and can better manage their own digital footprint as well as that of their employer. It is therefore vital for modern security training to cover the fundamental dangers of Web2.0</li>
<li>The mechanics of auditing, proactive measurement and defence of online reputation. Web intelligence solutions are particularly useful but managing remedial action is still fairly undeveloped</li>
<li>Explaining the opportunity to leverage personnel as a unique and highly scalable marketing entity. With appropriate selection, guidance, motivation and controls there is an exciting opportunity to use the publishing power of Web2.0 for extremely positive personal and corporate gain</li>
</ul>
<p>It is important not to be overtaken or overrun by technological advances. I recently advised a company following the discovery of unofficial social networking groups (bedecked with company name and logo). The groups were innovative and well intentioned (if na&iuml;vely established) and such discoveries indicated corporate IT were losing touch with talented, motivated and active networkers. Establishment of editorial control and content audits were simple wins. It is however important to reflect on the potential for damage as well as the potential for gain if the same enthusiasm were harnessed through focused and &lsquo;moderated&rsquo; corporate initiatives.</p>
<p>There has been a number of very interesting developments in the Web2.0 security and privacy domain over the past few months. At the end of March, IBM announced a $15.8m research grant awarded by the European Union. &lsquo;PrimeLife&rsquo; will be a 3-year study co-ordinated by their research division in Zurich supported by 14 partners from around the world. It will seek to put control of user&rsquo;s data back in user&rsquo;s hands&rdquo;. The extent of privacy and information leaks reached the point in April where the Israeli Defence Force (IDF) was compelled to issue a statement warning that, &ldquo;Facebook was a threat to national security&rdquo;. At the heart of that story was the &lsquo;free and easy&rsquo; manner in which members of the IDF were posting personal information, identifying themselves as members of the security services, pictured at sensitive installations and discussing sensitive subjects. The problems we face are so potentially damaging that they are now &lsquo;on the radar&rsquo; of government security services. Online advertising models deserve a full article in their own right, but I would briefly mention privacy concerns over Phorm and the highly publicised &lsquo;Beacon disaster&rsquo; championed by an &lsquo;unwisely zealous&rsquo; Facebook. These add an additional twist to the complex world of Web2.0 security.</p>
<p>My closing advice is to shape, cultivate, educate and empower your employees. Realise this by comprehending risk exposure and Web2.0&rsquo;s threats. The blinkers of a &lsquo;9 to 5&rsquo; blackout are unworthy; but above all, lose control of your employees, your personal or corporate reputation in Web2.0 at your peril.</p>
    ]]></content>
  </entry>
  <entry>
    <title>Is Phorm Legal?</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/steve-nimmons/06082008/phorm-legal" />
    <id>http://stevenimmons.org/blogs/steve-nimmons/06082008/phorm-legal</id>
    <published>2008-08-06T12:53:33-07:00</published>
    <updated>2008-08-06T13:00:47-07:00</updated>
    <author>
      <name>Steve-Nimmons</name>
    </author>
    <category term="Internet" />
    <category term="Security" />
    <summary type="html"><![CDATA[<p>&nbsp;</p>
<p><img alt="" src="http://stevenimmons.org/images/spies.jpg" /></p>
<p><a target="_blank" href="http://www.computerweekly.com/Articles/2008/08/06/231765/uk-must-clarify-legality-of-phorm-web-tracking-system.htm">Interesting article from Mark Watts</a> on the Risk Management blog at Computer Weekly today with the snippet below requiring Britain to respond to the EU commissioner in respect of whether Phorm complies with data protection legislation.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>&nbsp;</p>
<p><img alt="" src="http://stevenimmons.org/images/spies.jpg" /></p>
<p><a target="_blank" href="http://www.computerweekly.com/Articles/2008/08/06/231765/uk-must-clarify-legality-of-phorm-web-tracking-system.htm">Interesting article from Mark Watts</a> on the Risk Management blog at Computer Weekly today with the snippet below requiring Britain to respond to the EU commissioner in respect of whether Phorm complies with data protection legislation.</p>
<p>Phorm is something I was blogging about recently in relation to <a target="_blank" href="http://stevenimmons.org/blogs/stevenimmons/03082008/developments-online-advertising">developments in online advertising</a>.</p>
<p><em>&quot;Britain must provide an explanation to the European Union on whether </em><a href="http://www.computerweekly.com/Articles/2008/05/12/230645/broadband-users-will-leave-isps-that-adopt-phorm-advertising.htm"><em>Phorm</em></a><em>, the controversial online advertising system that monitors web traffic, complies with data protection legislation.</em></p>
<p><em>The UK government has until the end of the month to respond to a letter from </em><a href="http://ec.europa.eu/commission_barroso/reding/index_en.htm"><em>Viviane Reding</em></a><em>, the EU's commissioner for information society and media, seeking clarification.</em></p>
<p><em>The contents of the letter, sent in mid-July, have not been disclosed.&quot;</em></p>
    ]]></content>
  </entry>
  <entry>
    <title>Increased Threat for DNS Spoofing Vulnerability</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/27072008/increased-threat-dns-spoofing-vulnerability" />
    <id>http://stevenimmons.org/blogs/stevenimmons/27072008/increased-threat-dns-spoofing-vulnerability</id>
    <published>2008-07-27T07:50:13-07:00</published>
    <updated>2008-07-27T07:50:13-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Security" />
    <summary type="html"><![CDATA[<p>More on the DNS exploit courtesy of Microsoft Security Advisory...</p>
<p><a href="http://www.microsoft.com/technet/security/advisory/956187.mspx">Microsoft Security Advisory (956187): Increased Threat for DNS Spoofing Vulnerability - 7/25/2008</a> - </p>
    ]]></summary>
    <content type="html"><![CDATA[<p>More on the DNS exploit courtesy of Microsoft Security Advisory...</p>
<p><a href="http://www.microsoft.com/technet/security/advisory/956187.mspx">Microsoft Security Advisory (956187): Increased Threat for DNS Spoofing Vulnerability - 7/25/2008</a> - </p>
<p>Revision Note: July 25, 2008: Advisory published. Advisory Summary:Microsoft released Microsoft Security Bulletin MS08-037, Vulnerabilities in DNS Could Allow Spoofing (953230), on July 8, 2008, offering security updates to protect customers against Windows Domain Name System (DNS) spoofing attacks. Microsoft released this update in coordination with other DNS vendors who were also similarly impacted. Since the coordinated release of these updates, the threat to DNS systems has increased due to a greater public understanding of the attacks, as well as detailed exploit code being published on the Internet. </p>
<p>[<a href="http://www.microsoft.com/technet/security/">Microsoft Security Advisories</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>Attacks begin on net address flaw</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/27072008/attacks-begin-net-address-flaw" />
    <id>http://stevenimmons.org/blogs/stevenimmons/27072008/attacks-begin-net-address-flaw</id>
    <published>2008-07-27T07:44:39-07:00</published>
    <updated>2008-07-27T07:44:39-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Security" />
    <summary type="html"><![CDATA[<p>More DNS woes circulating...</p>
<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7525206.stm">Attacks begin on net address flaw</a> - Net firms urged to patch address flaw as attacks that exploit it circulate online.</p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>More DNS woes circulating...</p>
<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7525206.stm">Attacks begin on net address flaw</a> - Net firms urged to patch address flaw as attacks that exploit it circulate online.</p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>Oyster card hack to be published</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/21072008/oyster-card-hack-be-published" />
    <id>http://stevenimmons.org/blogs/stevenimmons/21072008/oyster-card-hack-be-published</id>
    <published>2008-07-21T13:38:21-07:00</published>
    <updated>2008-07-21T13:38:21-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Security" />
    <summary type="html"><![CDATA[<p>Seems like a surprising judgement to say the least...</p>
<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7516869.stm">Oyster card hack to be published</a> - A Dutch judge rules that details of how to copy Oyster cards can be published. </p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>Seems like a surprising judgement to say the least...</p>
<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7516869.stm">Oyster card hack to be published</a> - A Dutch judge rules that details of how to copy Oyster cards can be published. </p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>Crying wolf on Facebook security</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/19072008/crying-wolf-facebook-security" />
    <id>http://stevenimmons.org/blogs/stevenimmons/19072008/crying-wolf-facebook-security</id>
    <published>2008-07-19T07:18:10-07:00</published>
    <updated>2008-07-19T07:18:10-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Facebook" />
    <category term="Security" />
    <category term="Social Media" />
    <category term="Social Networking" />
    <category term="Web2.0" />
    <summary type="html"><![CDATA[<p><a href="http://www.computerweekly.com/blogs/it-fud-blog/2008/07/crying-wolf-on-facebook-securi.html">Crying wolf on Facebook security</a> - Facebook is today's  version of  the conversation by the water cooler.Why are we so hung-up on the security issues of social networking sites?           asks Cliff Saran </p>
<p>[<a href="http://www.computerweekly.com/blogs/it-fud-blog/">Cliff Saran's Blog</a>]</p>
    ]]></summary>
    <content type="html"><![CDATA[<p><a href="http://www.computerweekly.com/blogs/it-fud-blog/2008/07/crying-wolf-on-facebook-securi.html">Crying wolf on Facebook security</a> - Facebook is today's  version of  the conversation by the water cooler.Why are we so hung-up on the security issues of social networking sites?           asks Cliff Saran </p>
<p>[<a href="http://www.computerweekly.com/blogs/it-fud-blog/">Cliff Saran's Blog</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>Inside NSA Red Team Secret Ops With Government&#039;s Top Hackers</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/02072008/inside-nsa-red-team-secret-ops-governments-top-hackers" />
    <id>http://stevenimmons.org/blogs/stevenimmons/02072008/inside-nsa-red-team-secret-ops-governments-top-hackers</id>
    <published>2008-07-02T11:59:16-07:00</published>
    <updated>2008-07-02T11:59:16-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Security" />
    <summary type="html"><![CDATA[<p><a href="http://feeds.popularmechanics.com/~r/pm/technology/military_law/~3/323243467/4270420.html">Inside NSA Red Team Secret Ops With Government's Top Hackers</a> - The NSA has made headlines in the past few years for wiretapping and data-mining of questionable legality, but one of its primary functions is protecting the military's computer networks, and that's where the red team comes in.<br style="clear: both;" /></p>
    ]]></summary>
    <content type="html"><![CDATA[<p><a href="http://feeds.popularmechanics.com/~r/pm/technology/military_law/~3/323243467/4270420.html">Inside NSA Red Team Secret Ops With Government's Top Hackers</a> - The NSA has made headlines in the past few years for wiretapping and data-mining of questionable legality, but one of its primary functions is protecting the military's computer networks, and that's where the red team comes in.<br style="clear: both;" /><br />
<img width="1" height="1" border="0" src="http://www.pheedo.com/img.phdo?i=a34ae5081be706750909c83c80256b24" style="border: 0pt none ; height: 1px; width: 1px;" alt="" /> <img width="1" height="1" border="0" alt="" style="display: none;" src="http://www.pheedo.com/feeds/tracker.php?i=a34ae5081be706750909c83c80256b24" /></p>
<div class="feedflare">&nbsp;</div>
<div class="feedflare">[<a href="http://www.origin.popularmechanics.com/technology/military_law/">PopularMechanics Military and Law Enforcement</a>]</div>
    ]]></content>
  </entry>
  <entry>
    <title>Jail sentence for botnet creator</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/12062008/jail-sentence-botnet-creator" />
    <id>http://stevenimmons.org/blogs/stevenimmons/12062008/jail-sentence-botnet-creator</id>
    <published>2008-06-12T13:03:55-07:00</published>
    <updated>2008-06-12T13:03:55-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Security" />
    <summary type="html"><![CDATA[<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7451268.stm">Jail sentence for botnet creator</a> - A malicious hacker who hijacked hundreds of PCs will serve almost four years in jail for his crimes. </p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></summary>
    <content type="html"><![CDATA[<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7451268.stm">Jail sentence for botnet creator</a> - A malicious hacker who hijacked hundreds of PCs will serve almost four years in jail for his crimes. </p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>Yet another data breach</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/11062008/yet-another-data-breach" />
    <id>http://stevenimmons.org/blogs/stevenimmons/11062008/yet-another-data-breach</id>
    <published>2008-06-11T01:15:51-07:00</published>
    <updated>2008-06-11T01:15:51-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Security" />
    <summary type="html"><![CDATA[<p>Additional commentary on the security breach at Cotton Traders from David Lacey...</p>
<p><a href="http://www.computerweekly.com/blogs/david_lacey/2008/06/yet_another_data_breach.html">Yet another data breach</a> - This time it's the credit card details of up to 38,000 customers of clothing retailer Cotton Traders that have been stolen according to the BBC News. The firm claim to have upgraded their security. </p>
<p>[<a href="http://www.computerweekly.com/blogs/david_lacey/">David Lacey's Security Blog</a>]</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>Additional commentary on the security breach at Cotton Traders from David Lacey...</p>
<p><a href="http://www.computerweekly.com/blogs/david_lacey/2008/06/yet_another_data_breach.html">Yet another data breach</a> - This time it's the credit card details of up to 38,000 customers of clothing retailer Cotton Traders that have been stolen according to the BBC News. The firm claim to have upgraded their security. </p>
<p>[<a href="http://www.computerweekly.com/blogs/david_lacey/">David Lacey's Security Blog</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>Card details stolen in web hack</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/11062008/card-details-stolen-web-hack" />
    <id>http://stevenimmons.org/blogs/stevenimmons/11062008/card-details-stolen-web-hack</id>
    <published>2008-06-11T01:10:12-07:00</published>
    <updated>2008-06-11T01:10:12-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Internet" />
    <category term="Security" />
    <category term="Web Technology" />
    <summary type="html"><![CDATA[<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7446871.stm">Card details stolen in web hack</a> - Card details of up to 38,000 customers are stolen after the Cotton Trader website is hacked, the BBC learns. </p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></summary>
    <content type="html"><![CDATA[<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7446871.stm">Card details stolen in web hack</a> - Card details of up to 38,000 customers are stolen after the Cotton Trader website is hacked, the BBC learns. </p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>Facebook &#039;violates privacy laws&#039;</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/30052008/facebook-violates-privacy-laws" />
    <id>http://stevenimmons.org/blogs/stevenimmons/30052008/facebook-violates-privacy-laws</id>
    <published>2008-05-30T22:40:52-07:00</published>
    <updated>2008-05-30T22:40:52-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Facebook" />
    <category term="Security" />
    <category term="Social Networking" />
    <category term="Web2.0" />
    <summary type="html"><![CDATA[<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7428833.stm">Facebook 'violates privacy laws'</a> - Social networking site Facebook is accused of 22 counts of privacy breaches by a Canadian group. </p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></summary>
    <content type="html"><![CDATA[<p><a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/7428833.stm">Facebook 'violates privacy laws'</a> - Social networking site Facebook is accused of 22 counts of privacy breaches by a Canadian group. </p>
<p>[<a href="http://news.bbc.co.uk/go/rss/-/1/hi/technology/default.stm">BBC UK Technology News</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>Helping hacked sites</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/26052008/helping-hacked-sites" />
    <id>http://stevenimmons.org/blogs/stevenimmons/26052008/helping-hacked-sites</id>
    <published>2008-05-26T06:28:47-07:00</published>
    <updated>2008-05-26T06:29:32-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Google" />
    <category term="Security" />
    <category term="Web Technology" />
    <summary type="html"><![CDATA[<p><a href="http://feeds.mattcutts.com/~r/mattcutts/uJBW/~3/298036896/">Helping hacked sites</a> -</p>
<p>A very interesting and useful post on Matt Cutts blog.</p>
<p>---</p>
    ]]></summary>
    <content type="html"><![CDATA[<p><a href="http://feeds.mattcutts.com/~r/mattcutts/uJBW/~3/298036896/">Helping hacked sites</a> -</p>
<p>A very interesting and useful post on Matt Cutts blog.</p>
<p>---</p>
<p>There was a <a href="http://www.techmeme.com/080525/p25#a080525p25">Techmeme</a> discussion this weekend about <a href="http://radar.oreilly.com/archives/2008/05/microhoo-corporate-penis-envy.html">whether Microsoft should chase Google in search</a> or find their own &ldquo;Big Hairy Audacious Goal.&rdquo; Into that discussion came a <a href="http://blog.digitalbackcountry.com/?p=1436">post by Ryan Stewart</a> about being removed from Google&rsquo;s index. It turns out that Ryan&rsquo;s blog had been hacked, and Google does remove hacked sites from our index to protect our users. I left a comment at Ryan&rsquo;s blog, but while I wait for it to be approved I thought that I&rsquo;d post it here as well:</p>
<blockquote>
<p>Hi Ryan, my name is Matt Cutts and I&rsquo;m a software engineer at Google. Sorry to hear that your blog got hacked. I know that it&rsquo;s disappointing if you don&rsquo;t show up in Google, but there&rsquo;s another way to look at it. It looks like your blog was hacked to show &ldquo;buy pharmacy&rdquo;-type links, but what if the hackers had hosted malware on your site? Then every user to your site might have gotten infected just by visiting your site. That danger to Google users is one of the reasons that we temporarily remove hacked sites from Google.</p>
<p>I&rsquo;m glad that things look clean now and I&rsquo;ve revoked the &ldquo;hacked site&rdquo; flag for your domain. I&rsquo;d expect your domain to return to Google within 48 hours, if not sooner.</p>
<p>By the way, we did try to contact you. We sent an email to  contact [at] digitalbackcountry.com, info [at] digitalbackcountry.com, support [at] digitalbackcountry.com, webmaster [at] digitalbackcountry.com, and a gmail.com address on May 19th at 21:25:23 with a subject line of &ldquo;Removal from Google&rsquo;s index.&rdquo; I believe if you had logged into our webmaster console at <a href="http://www.google.com/webmasters/tools">google.com/webmasters</a> and proved that you owned digitalbackcountry.com, we also would have left a message waiting for you there as well. That webmaster console is the primary way to request reconsideration in case your blog has been hacked.</p>
<p>We do try to communicate with hacked blogs where we can, and we also do blog posts to try to help prevent hacked sites and for site owners to recover from hacked sites. Some example posts that we&rsquo;ve done in the past:</p>
<p><a href="http://googlewebmastercentral.blogspot.com/2007/09/quick-security-checklist-for-webmasters.html">http://googlewebmastercentral.blogspot.com/2007/09/quick-security-checklist-for-webmasters.html</a><br />
<a href="http://googlewebmastercentral.blogspot.com/2008/04/my-sites-been-hacked-now-what.html">http://googlewebmastercentral.blogspot.com/2008/04/my-sites-been-hacked-now-what.html</a><br />
<a href="http://www.mattcutts.com/blog/how-google-handles-malware-a-historical-overview/">http://www.mattcutts.com/blog/how-google-handles-malware-a-historical-overview/</a></p>
<p>The only last point I&rsquo;d make is that users tell us loud and clear that they don&rsquo;t want to be sent to hacked sites, because of the potential danger that they represent. Even though it&rsquo;s stressful to be removed from Google, I hope you understand why Google might not want to send users to a hacked blog.</p>
<p>Again, thanks for cleaning up your site and you should return to Google&rsquo;s index soon.</p>
</blockquote>
<p>How Google should handle hacked sites is a tough question, but personally I think Google does a better job than other search engines of protecting our users and communicating with site owners about hacked sites. For example, here is an excerpt of the email that we sent to Ryan on May 19th:</p>
<blockquote>
<p>Dear site owner or webmaster of blog.digitalbackcountry.com,</p>
<p>While we were indexing your webpages, we detected that some of your pages were using techniques that are outside our quality guidelines, which can be found here: http://www.google.com/webmasters/guidelines.html.  This appears to be because your site has been modified by a third party. Typically, the offending party gains access to an insecure directory that has open permissions. Many times, they will upload files or modify existing ones, which then show up as spam in our index.</p>
<p>The following is some example hidden text we found at blog.digitalbackcountry.com:</p>
<p>Acyclovir Adderall Adipex Alprazolam Ambien Ativan Biaxin Bontril Bupropion Butalbital Carisoprodol Celexa Cheap Phentermine Cialis Online Cialis Cipro Clonazepam Codeine Darvocet Diazepam Didrex Diflucan Effexor Ephedrine Fioricet Flexeril Generic Viagra Glucophage Hydrocodone Online Hydrocodone Levitra Lexapro Line Xanax Lipitor Lorazepam Lortab Meridia Nexium Norco Viagra Tramadol Soma Phentermine Valium Norvasc Buy Acyclovir Buy Adderall Buy Adipex Buy Alprazolam Buy Ambien Buy Ativan Buy Biaxin Buy Bontril Buy Bupropion Buy Butalbital Buy Carisoprodol Buy Celexa Buy Cheap Phentermine Buy Cialis Online Buy Cialis Buy Cipro Buy Clonazepam Buy Codeine Buy Com Lvivhost Online Viagra Buy Darvocet Buy Diazepam Buy Didrex Buy Diflucan Buy Effexor Buy Ephedrine Buy Fioricet Buy Flexeril Buy Generic Viagra Buy Glucophage Buy Hydrocodone Online Buy Hydrocodone Buy Levitra Buy Lexapro Buy Line Xanax Buy Lipitor Buy Lorazepam Buy Lortab Buy Meridia Buy Nexium Buy Norco Buy Norvasc Buy Online Xanax Buy Oxycontin Buy Paxil Buy Percocet Buy Phentermine Online Buy Phentermine Buy Propecia Buy Provigil Buy Prozac Buy Renova Buy Seroquel Buy Soma Buy Tadalafil Buy Tamiflu</p>
<p>[...]</p>
<p>In order to preserve the quality of our search engine, we have temporarily removed some of your webpages from our search results.</p>
</blockquote>
<p>(The rest of the email goes on describe how long the blog will be out of Google, and <a href="https://www.google.com/webmasters/tools/reinclusion?hl=en">where to go</a> in order to get back into Google&rsquo;s index faster.)</p>
<p>Getting hacked is not fun. It&rsquo;s just not. But I think Google does the right thing for our users by removing hacked sites from our index temporarily. I also think we do a pretty good job of trying to alert site owners that they&rsquo;ve been hacked &mdash; more than any other search engine does. We alert many webmasters about hacked sites not only via email but also with our <a href="http://www.google.com/webmasters/tools">webmaster console</a>.</p>
<p>Do I want more competition in search? Absolutely, because it keeps everyone on their toes and working hard for our users. But I think Ryan&rsquo;s specific situation actually shows that Google is trying to do the right thing for site owners and users. Ryan, I hope there&rsquo;s no hard feelings that your site was removed from our index after being hacked, and now that it&rsquo;s clean you should be back soon.</p>
<p><img width="1" height="1" src="http://feeds.mattcutts.com/~r/mattcutts/uJBW/~4/298036896" alt="" /> [<a href="http://www.mattcutts.com/blog">Matt Cutts' Google Blog</a>]</p>
    ]]></content>
  </entry>
  <entry>
    <title>How to hijack a bluetooth conversation</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/simonelliott/21052008/how-hijack-bluetooth-conversation" />
    <id>http://stevenimmons.org/blogs/simonelliott/21052008/how-hijack-bluetooth-conversation</id>
    <published>2008-05-21T01:19:21-07:00</published>
    <updated>2008-05-21T01:21:41-07:00</updated>
    <author>
      <name>SimonElliott</name>
    </author>
    <category term="Security" />
    <category term="Telecoms" />
    <summary type="html"><![CDATA[<p>I've just tried this out, with my jebra head set at home and a ubuntu laptop. It works just fine!<br />This is a really good example of a thought leader ship, video. Its entertaining, informative and inspiring</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>I've just tried this out, with my jebra head set at home and a ubuntu laptop. It works just fine!<br />This is a really good example of a thought leader ship, video. Its entertaining, informative and inspiring</p>
<div style='text-align:center'>
<object width='425' height='355' id='FiveminPlayer'><param name='allowfullscreen' value='true' /><param name='allowScriptAccess' value='always' /><param name='movie' value='http://www.5min.com/Embeded/925061/' /><embed src='http://www.5min.com/Embeded/925061/' type='application/x-shockwave-flash' width='425' height='355' allowfullscreen='true' allowScriptAccess='always'></embed></object><p><br/><span style='font-family: Verdana; font-size: 10px;'>More <a href='http://www.5min.com/' target='_blank'>How To Videos</a> at 5min.com</span></br/></p></div>
<p><img style="visibility:hidden;width:0px;height:0px;" border=0 width=0 height=0 src="http://counters.gigya.com/wildfire/CIMP/bT*xJmx*PTEyMTEzNTc*OTE1MjMmcHQ9MTIxMTM1Nzg5NDEzMSZwPTEyNDUxJmQ9Jm49Jmc9MQ==.jpg" /></p>
    ]]></content>
  </entry>
  <entry>
    <title>Security Mindset</title>
    <link rel="alternate" type="text/html" href="http://stevenimmons.org/blogs/stevenimmons/21052008/security-mindset" />
    <id>http://stevenimmons.org/blogs/stevenimmons/21052008/security-mindset</id>
    <published>2008-05-20T22:39:26-07:00</published>
    <updated>2008-05-20T22:39:26-07:00</updated>
    <author>
      <name>SteveNimmons</name>
    </author>
    <category term="Security" />
    <summary type="html"><![CDATA[<p>Interesting thoughts on 'poacher / gamekeeper' philosophy when it comes to designing security systems. In my view, not enough skills are being developed in the UK in terms of ethical hacking.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>Interesting thoughts on 'poacher / gamekeeper' philosophy when it comes to designing security systems. In my view, not enough skills are being developed in the UK in terms of ethical hacking.</p>
<p><a href="http://www.computerweekly.com/blogs/david_lacey/2008/05/security_mindset.html">Security Mindset</a> - Bruce Schneier's remarks about the security mindset, the thinking you need to design effective security countermeasures, to think like an attacker, are interesting. He's certainly correct that such a mindset exists and it's extremely difficult to teach... [<a href="http://www.computerweekly.com/blogs/david_lacey/">David Lacey's Security Blog</a>]</p>
    ]]></content>
  </entry>
</feed>
