<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.securitypractice.org/~d/styles/atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.securitypractice.org/~d/styles/itemcontent.css" type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0"><id>tag:blogger.com,1999:blog-6233015771421939379</id><updated>2009-01-05T15:00:28.599Z</updated><title type="text">Security Practice: Life, Crypto, Network forensics.</title><subtitle type="html">Tales from the....</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://www.lacunae.org/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://www.lacunae.org/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>165</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><logo>http://creativecommons.org/images/public/somerights20.gif</logo><link rel="self" href="http://feeds.securitypractice.org/SecurityPractice" type="application/atom+xml" /><entry><title type="text">Links for 2008-09-10 [del.icio.us]</title><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895910/joncare" /><updated>2008-09-11T00:00:00-05:00</updated><id>http://del.icio.us/joncare#2008-09-10</id><summary type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.pingtrip.com/weblog/2008/09/installing-hacme-bank-on-xp-pro"&gt;Installing Hacme Bank on an XP Pro VMWare Image - PingTrip&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</summary><content type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.pingtrip.com/weblog/2008/09/installing-hacme-bank-on-xp-pro"&gt;Installing Hacme Bank on an XP Pro VMWare Image - PingTrip&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895910" height="1" width="1"/&gt;</content><feedburner:origLink>http://del.icio.us/joncare#2008-09-10</feedburner:origLink></entry><entry><title type="text">Links for 2008-09-09 [del.icio.us]</title><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895911/joncare" /><updated>2008-09-10T00:00:00-05:00</updated><id>http://del.icio.us/joncare#2008-09-09</id><summary type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.damnvulnerablelinux.org/content/view/22/27/"&gt;Damn Vulnerable Linux - The most vulnerable and exploitable operating system ever - First steps with Damn Vulnerable Linux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</summary><content type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.damnvulnerablelinux.org/content/view/22/27/"&gt;Damn Vulnerable Linux - The most vulnerable and exploitable operating system ever - First steps with Damn Vulnerable Linux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895911" height="1" width="1"/&gt;</content><feedburner:origLink>http://del.icio.us/joncare#2008-09-09</feedburner:origLink></entry><entry><title type="text">Links for 2008-07-17 [del.icio.us]</title><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895912/joncare" /><updated>2008-07-18T00:00:00-05:00</updated><id>http://del.icio.us/joncare#2008-07-17</id><summary type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://samy.pl/chownat/"&gt;chownat - NAT to NAT communication&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://thomer.com/howtos/nstx.html"&gt;NSTX (IP-over-DNS) HOWTO&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://thomer.com/icmptx/"&gt;ICMPTX (IP-over-ICMP) HOWTO&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</summary><content type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://samy.pl/chownat/"&gt;chownat - NAT to NAT communication&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://thomer.com/howtos/nstx.html"&gt;NSTX (IP-over-DNS) HOWTO&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://thomer.com/icmptx/"&gt;ICMPTX (IP-over-ICMP) HOWTO&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895912" height="1" width="1"/&gt;</content><feedburner:origLink>http://del.icio.us/joncare#2008-07-17</feedburner:origLink></entry><entry><title type="text">Links for 2008-07-03 [del.icio.us]</title><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895913/joncare" /><updated>2008-07-04T00:00:00-05:00</updated><id>http://del.icio.us/joncare#2008-07-03</id><summary type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.ghost-writer.co.uk/default.htm"&gt;Ghost-writer | home&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</summary><content type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.ghost-writer.co.uk/default.htm"&gt;Ghost-writer | home&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895913" height="1" width="1"/&gt;</content><feedburner:origLink>http://del.icio.us/joncare#2008-07-03</feedburner:origLink></entry><entry><title type="text">Links for 2008-07-02 [del.icio.us]</title><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895914/joncare" /><updated>2008-07-03T00:00:00-05:00</updated><id>http://del.icio.us/joncare#2008-07-02</id><summary type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.extelligence.co.uk/dictionary/e/"&gt;Words List - Extelligence: Archaic and Creative Word Dictionary&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</summary><content type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.extelligence.co.uk/dictionary/e/"&gt;Words List - Extelligence: Archaic and Creative Word Dictionary&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895914" height="1" width="1"/&gt;</content><feedburner:origLink>http://del.icio.us/joncare#2008-07-02</feedburner:origLink></entry><entry><title type="text">Links for 2008-07-01 [del.icio.us]</title><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895915/joncare" /><updated>2008-07-02T00:00:00-05:00</updated><id>http://del.icio.us/joncare#2008-07-01</id><summary type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://technet.microsoft.com/en-us/security/cc242650.aspx"&gt;UrlScan Security Tool&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</summary><content type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://technet.microsoft.com/en-us/security/cc242650.aspx"&gt;UrlScan Security Tool&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895915" height="1" width="1"/&gt;</content><feedburner:origLink>http://del.icio.us/joncare#2008-07-01</feedburner:origLink></entry><entry><title type="text">Links for 2008-06-25 [del.icio.us]</title><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895916/joncare" /><updated>2008-06-26T00:00:00-05:00</updated><id>http://del.icio.us/joncare#2008-06-25</id><summary type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.darkreading.com/document.asp?doc_id=157088"&gt;Tech Insight: Finding Security-Sensitive Data - on a Shoestring Budget - Desktop Security News Analysis - Dark Reading&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.cit.cornell.edu/security/tools/spider-windows.html"&gt;Spider for Windows&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</summary><content type="html">&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.darkreading.com/document.asp?doc_id=157088"&gt;Tech Insight: Finding Security-Sensitive Data - on a Shoestring Budget - Desktop Security News Analysis - Dark Reading&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.cit.cornell.edu/security/tools/spider-windows.html"&gt;Spider for Windows&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895916" height="1" width="1"/&gt;</content><feedburner:origLink>http://del.icio.us/joncare#2008-06-25</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-8857435508817032104</id><published>2008-03-25T09:15:00.003Z</published><updated>2008-03-25T10:25:30.777Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-25T10:25:30.777Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="PCI DSS" /><title type="text">A Lawyer's analysis of PCI</title><content type="html">PCI-DSS - the Payment Card Industry Data Security Standard, has attracted some interesting views to it. The latest one is &lt;a href="http://infoseccompliance.blogspot.com/2008/02/legal-implications-risks-and-problems.html"&gt;here&lt;/a&gt;. The writer describes it operating "like a court" - I don't quite agree, it operates under contract law, and I've been involved in at least one case where the issuing brand failed to have a recovery clause in the contract allowing them to seek reparation from the retailer-in-breach.&lt;br /&gt;&lt;br /&gt;However, the interesting thing is that its not just &lt;span style="font-style: italic;"&gt;a good idea&lt;/span&gt; to be compliant with PCI if you are "storing, processing or transmitting" credit card numbers. If you want to take payment with credit cards, then your bank (urged by VISA and MasterCard) will require you to sign up for PCI, with contractual caveats that any PCI breaches and costs thereof are born by .. erm, you.&lt;br /&gt;&lt;br /&gt;In other news, my friend Branden has a&lt;a href="http://blogs.verisign.com/securityconvergence/2008/03/all_qsas_are_not_created_equal.php"&gt; spiffy blog online&lt;/a&gt;. Go check it out. The link is to his "All QSA's are not created equal" post, which given the legal post above, is worth considering. Not only do you get what you pay for, but selection of a high quality QSA over a bucket shop could save a hell of a lot of money in PCI reparation costs.
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=Rt9Yio"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=Rt9Yio" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=N83gO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=N83gO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=JvYEo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=JvYEo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=qlPeo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=qlPeo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=dZBio"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=dZBio" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895917" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/8857435508817032104/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=8857435508817032104" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/8857435508817032104?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/8857435508817032104?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895917/lawyers-analysis-of-pci.html" title="A Lawyer's analysis of PCI" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/lawyers-analysis-of-pci.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-4461603327959756648</id><published>2008-03-17T15:37:00.004Z</published><updated>2008-03-17T15:47:26.558Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-17T15:47:26.558Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="computer society" /><category scheme="http://www.blogger.com/atom/ns#" term="phorm" /><category scheme="http://www.blogger.com/atom/ns#" term="privacy" /><title type="text">Sir Tim and I agree</title><content type="html">&lt;div style="text-align: justify;"&gt;In a previous post, I recommended you write to your MP, cancel your phone service, and call Jeremy Vine (from someone else's phone) if your ISP started using Phorm.&lt;br /&gt;&lt;br /&gt;Well, Sir Tim Berners-Lee says:&lt;br /&gt;&lt;br /&gt;       &lt;span style="font-style: italic;"&gt;The creator of the web has said consumers need to be protected&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         against systems which can track their activity on the internet.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         Sir Tim Berners-Lee told BBC News he would change his internet&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         provider if it introduced such a system.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         Plans by leading internet providers to use Phorm, a company&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         which tracks web activity to create personalised adverts, have&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         sparked controversy.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         Sir Tim said he did not want his ISP to track which websites&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         he visited.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         "I want to know if I look up a whole lot of books about some form&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         of cancer that that's not going to get to my insurance company&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         and I'm going to find my insurance premium is going to go up by 5%&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         because they've figured I'm looking at those books," he said.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         Sir Tim said his data and web history belonged to him.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         He said: "It's mine - you can't have it. If you want to use it for&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         something, then you have to negotiate with me. I have to agree,&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;         I have to understand what I'm getting in return."&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Seriously folks, imagine how you'd feel if the Royal Mail said "hey, we opened your post and saw that you had a letter from the bank warning you about your overdraft, can we interest you in a low-price loan"? Or if your phone company rang you up and said "You've had a call from the hospital, would you like some low-price funeral expenses  insurance?" I could hope that this will encourage more people to use encryption such as PGP, but that's not likely. People have never really understood why encyrption is important in reducing their internet footprint.&lt;br /&gt;&lt;br /&gt;More to the point, it would be &lt;span style="font-weight: bold;"&gt;illegal. Has the law not caught up with the fact that we conduct sensitive and private communications over the Internet, not just by phone and letter?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;I wonder if Sir Tim will get an invite from Phorm's PR company to a business briefing as well?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;&lt;span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=LLBSXJ"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=LLBSXJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=SMMAO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=SMMAO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=83Suo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=83Suo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=kqbwo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=kqbwo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=4QYMo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=4QYMo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895918" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/4461603327959756648/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=4461603327959756648" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/4461603327959756648?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/4461603327959756648?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895918/sir-tim-and-i-agree.html" title="Sir Tim and I agree" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/sir-tim-and-i-agree.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-4304454253364756516</id><published>2008-03-17T13:46:00.003Z</published><updated>2008-03-17T13:53:42.250Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-17T13:53:42.250Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="online dating" /><category scheme="http://www.blogger.com/atom/ns#" term="computer security" /><category scheme="http://www.blogger.com/atom/ns#" term="government" /><title type="text">Saying no, the third way</title><content type="html">&lt;div style="text-align: justify;"&gt;My favourite line in &lt;span style="font-style: italic;"&gt;The Vicar of Dibley&lt;/span&gt;&lt;span&gt; is:&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;GERALDINE: There are two answers to your question, the long one and the short one. The short answer is "No", and the long answer is "Noooooooooooooooooooooo".&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;I signed the &lt;a href="http://www.pm.gov.uk/output/Page15059.asp"&gt;petition to form a national e-crime unit&lt;/a&gt; recently. The gub'mint have found a Third Way:&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;Thank you for the e-petition, asking for the Government to give priority to the creation of an e-crime unit as proposed by the Metropolitan Police Service and ACPO.&lt;/span&gt;&lt;/div&gt;&lt;p style="font-style: italic; text-align: justify;"&gt;The Government takes seriously all forms of crime, and has passed legislation to support the prosecution of those who steal data and attack IT systems, or who create the technical mechanisms to support such attacks&lt;/p&gt;&lt;p style="font-style: italic; text-align: justify;"&gt;The Government is currently in receipt of the proposal by the Metropolitan Police Service and ACPO and are actively considering the issues it has raised and the value of creating such a unit.&lt;/p&gt;&lt;p style="font-style: italic; text-align: justify;"&gt;Government has allocated £29 million over 3 years to implement the recommendations of the Fraud Review. This includes the creation of a National Fraud Strategic Authority (NFSA) which will drive forward a comprehensive strategy for tackling fraud, bringing together the Government, criminal justice practitioners, business and the public. It also includes a new national lead force role for the City of London Police and National Fraud Reporting Centre (NFRC) which will collect and analyse data on all types of fraud (including online fraud), equip law enforcement agencies with a powerful intelligence tool and help form the basis of better prevention advice and alerts to fraud threats for business and the public.&lt;/p&gt;&lt;p style="font-style: italic; text-align: justify;"&gt;Both the Child Exploitation Online Protection Centre (CEOP) and the Internet Watch Foundation (IWF) have 24 hour reporting mechanisms aimed at members of the public to report instances of child abuse or websites containing child abuse images. &lt;/p&gt;&lt;p style="font-style: italic; text-align: justify;"&gt;The National Hi Tech Crime Unit (NHTCU) was originally part of the National Crime Squad (NCS), and moved into SOCA along with the rest of NCS in 2006. The name was changed to SOCA e-crime to reflect the new organisation. SOCA e-crime has more resources than the NHCTU and greater international reach via SOCA's international liaison network. The e-crime unit brings together experts from different organisations under one roof and has already developed a national e-Crime strategy with key partners. This aims to improve links with industry and to develop ways for educating businesses and the public about e-crime.&lt;/p&gt;&lt;p style="font-style: italic; text-align: justify;"&gt;The Government is committed to providing adequate responses to this area of crime in a unified way without duplicating the work carried out by other organisations.&lt;/p&gt;There is of course the fourth way, or "Internet Dating" method of saying no, which is simply to disappear and never be heard from again. But I guess we'd miss Gordon if he did that one.&lt;br /&gt;&lt;p style="font-style: italic; text-align: justify;"&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=8hY7kz"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=8hY7kz" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=jKwlO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=jKwlO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=HMeVo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=HMeVo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=FNwKo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=FNwKo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=h9gyo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=h9gyo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895919" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/4304454253364756516/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=4304454253364756516" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/4304454253364756516?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/4304454253364756516?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895919/saying-no-third-way.html" title="Saying no, the third way" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/saying-no-third-way.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-2638547587805643490</id><published>2008-03-13T21:50:00.001Z</published><updated>2008-03-13T21:58:55.321Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-13T21:58:55.321Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Life" /><title type="text">Deep into Sleep  (July-August 2005)</title><content type="html">&lt;a href="http://harvardmagazine.com/2005/07/deep-into-sleep.html"&gt;Deep into Sleep  (July-August 2005)&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;What does this have to do with security?&lt;br /&gt;Well, apparently we all have messed up sleep patterns (your author included), and this means our decision making skills are impaired.&lt;br /&gt;&lt;br /&gt;Hence, security lapses.
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=VVsRlN"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=VVsRlN" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=eDmCO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=eDmCO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=TEUyo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=TEUyo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=CacYo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=CacYo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=se4Yo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=se4Yo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895920" height="1" width="1"/&gt;</content><link rel="related" href="http://harvardmagazine.com/2005/07/deep-into-sleep.html" title="Deep into Sleep  (July-August 2005)" /><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/2638547587805643490/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=2638547587805643490" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/2638547587805643490?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/2638547587805643490?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895920/deep-into-sleep-july-august-2005.html" title="Deep into Sleep  (July-August 2005)" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/deep-into-sleep-july-august-2005.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-5303105824491788805</id><published>2008-03-07T19:34:00.002Z</published><updated>2008-03-07T19:37:44.027Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-07T19:37:44.027Z</app:edited><title type="text">Musing: differences between the US and the UK</title><content type="html">US: "If everyone is a speeder, the cops won't arrest everyone"&lt;br /&gt;UK: "If everyone is a speeder, then put automated cameras to catch them"&lt;br /&gt;&lt;br /&gt;Inspired by &lt;a href="http://www.pbs.org/cringely/pulpit/2008/pulpit_20080307_004467.html"&gt;Cringely&lt;/a&gt;.
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=I98jJO"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=I98jJO" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=O80ZO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=O80ZO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=E60Co"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=E60Co" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=3equo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=3equo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=CS5bo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=CS5bo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895921" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/5303105824491788805/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=5303105824491788805" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/5303105824491788805?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/5303105824491788805?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895921/musing-differences-between-us-and-uk.html" title="Musing: differences between the US and the UK" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/musing-differences-between-us-and-uk.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-6760148479426468489</id><published>2008-03-07T12:44:00.002Z</published><updated>2008-03-07T13:19:05.425Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-07T13:19:05.425Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="happiness" /><category scheme="http://www.blogger.com/atom/ns#" term="coffee" /><category scheme="http://www.blogger.com/atom/ns#" term="gaggia" /><category scheme="http://www.blogger.com/atom/ns#" term="facebook" /><title type="text">Facebook users set stupidity tests</title><content type="html">I see these on FaceBook:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.spywareguide.com/upload/2008/03/altf4.gif"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 574px; height: 77px;" src="http://blog.spywareguide.com/upload/2008/03/altf4.gif" alt="" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;So, for those who don't know - Alt-F4 closes your current window. Its a stupidity test, don't fall for it.&lt;br /&gt;&lt;br /&gt;In other news, a grateful "thank you" to &lt;a href="http://www.gaggia.uk.com/"&gt;Gaggia&lt;/a&gt;, who sent me an upgraded coffee machine after I returned the first one to them, worn out. Espresso powered computer security is here once more.
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=zVlr9t"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=zVlr9t" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=3AfhO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=3AfhO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=ESRlo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=ESRlo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=0Cz9o"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=0Cz9o" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=BWpmo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=BWpmo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895922" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/6760148479426468489/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=6760148479426468489" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/6760148479426468489?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/6760148479426468489?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895922/facebook-users-set-stupidity-tests.html" title="Facebook users set stupidity tests" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/facebook-users-set-stupidity-tests.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-7376531098319440332</id><published>2008-03-07T12:38:00.000Z</published><updated>2008-03-07T12:40:47.243Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-07T12:40:47.243Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="shredders" /><category scheme="http://www.blogger.com/atom/ns#" term="cynicsm" /><category scheme="http://www.blogger.com/atom/ns#" term="computer security" /><title type="text">Why we love PaperGhost</title><content type="html">Just &lt;a href="http://www.vitalsecurity.org/2008/03/punisher-punished.html"&gt;because&lt;/a&gt;.&lt;br /&gt;&lt;p&gt;&lt;br /&gt;&lt;img src="http://www.vitalsecurity.org/uploaded_images/punlol-791584.gif" /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=re2DtR"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=re2DtR" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=AT8TO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=AT8TO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=lZdro"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=lZdro" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=YUVLo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=YUVLo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=DlETo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=DlETo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895923" height="1" width="1"/&gt;</content><link rel="related" href="http://www.vitalsecurity.org/2008/03/punisher-punished.html" title="Why we love PaperGhost" /><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/7376531098319440332/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=7376531098319440332" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/7376531098319440332?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/7376531098319440332?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895923/why-we-love-paperghost.html" title="Why we love PaperGhost" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/why-we-love-paperghost.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-2264007639700546938</id><published>2008-03-07T09:03:00.000Z</published><updated>2008-03-07T09:03:45.943Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-07T09:03:45.943Z</app:edited><title type="text">SUR in English</title><content type="html">&lt;a href="http://www.surinenglish.com/noticias.php?Noticia=12352"&gt;SUR in English&lt;/a&gt;: "Having survived a complicated divorce and secured custody of the children the thought of moving to another country and reducing contact with an ex husband or wife becomes attractive. What many parents don’t realise, however, is that taking a child out of their country of origin without authorisation from their former partner violates international law."
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=u1iyBN"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=u1iyBN" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=m06eO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=m06eO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=Dcz3o"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=Dcz3o" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=vbVlo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=vbVlo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=9zHmo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=9zHmo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895924" height="1" width="1"/&gt;</content><link rel="related" href="http://www.surinenglish.com/noticias.php?Noticia=12352" title="SUR in English" /><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/2264007639700546938/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=2264007639700546938" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/2264007639700546938?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/2264007639700546938?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895924/sur-in-english.html" title="SUR in English" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/sur-in-english.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-351230044840548746</id><published>2008-03-06T21:21:00.006Z</published><updated>2008-03-06T22:04:23.372Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-06T22:04:23.372Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="phorm" /><category scheme="http://www.blogger.com/atom/ns#" term="BT" /><category scheme="http://www.blogger.com/atom/ns#" term="privacy" /><title type="text">We don't care, we dont have to, we're the phone company</title><content type="html">&lt;div style="text-align: justify;"&gt;Lauren Weinstein&lt;a href="http://lauren.vortex.com/archive/000375.html"&gt; writes about&lt;/a&gt; how BT are quite callously exploiting the privacy (and ignorance) of their customers. Let's face it, technically aware people avoid BT like herpes.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;Edit:&lt;/span&gt; &lt;span style="font-style: italic;"&gt;I've actually had quite a fun idea which would screw this up completely. In the same way that we can screw up Sky Digital's audience monitoring system by leaving the DigiBox tuned to 504 (BBC Parliament) when we aren't watching anything else, why not have a little perl script running in the background of your system which submits a list of stupid and bogus queries to google, say once a second. The traffic and system load would be minimal, and it would crap out the Phorm Phactor.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;I'm reproducing Lauren's post in full, because it sums it up.&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;Greetings.  Given the CCTV surveillance fetish in the UK these days, it seems somehow sickly appropriate that British ISPs are in the forefront when it comes to spying on the content of their subscribers' Web browsing -- and it appears that Google users are in the bull's-eye.&lt;br /&gt;&lt;br /&gt;Most of the related media attention so far has revolved around the manner in which the three largest UK ISPs have gone to bed with "Phorm" -- toward the goal of monetizing Web browsing habits of subscribers and providing targeted ads&lt;br /&gt;( &lt;a wot1204836827781="www.theregister.co.uk" href="http://www.theregister.co.uk/2008/02/29/phorm_roundup/" target="_blank"&gt;http://www.theregister.co.uk&lt;wbr&gt;/2008/02/29/phorm_roundup/&lt;/a&gt; ).&lt;br /&gt;&lt;br /&gt;Of course, there's a lot "soothing" promotional blather on the BT site claiming that the data collected regarding the sites that you visit is quickly deleted or anonymized.  And while officially the ISPs claim that they haven't made a decision about opt-out vs. opt-in, the current British Telecom limited deployment -- they call the "service" "Webwise" ( &lt;a wot1204836827781="webwise.bt.com" href="http://webwise.bt.com/webwise/index.html" target="_blank"&gt;http://webwise.bt.com/webwise&lt;wbr&gt;/index.html&lt;/a&gt; ) and promote it as mainly an anti-phishing system -- appears to be opt-out (requiring either maintaining a special cookie in your browser or blocking all cookies from a particular site).&lt;br /&gt;&lt;br /&gt;Third-party tracking of the Web sites that you visit is bad enough, but Webwise (and presumably the other incarnations of the Phorm system) go one big step farther -- they actually *spy* on your Web content and extract for their own use the search terms that you enter into search engines:&lt;br /&gt;&lt;br /&gt;"We [Webwise] use the website address, keywords and search terms&lt;br /&gt;from the page viewed to match a category or area of interest&lt;br /&gt;(e.g., travel or finance)."&lt;br /&gt;&lt;br /&gt;Given that the vast majority of searches these days are conducted with Google, it's obvious that this ISP-based system will be attempting to monetize the vast number of search transactions between users and Google, in a technical manner that seems eerily similar to wiretapping.&lt;br /&gt;&lt;br /&gt;This is unbelievably intrusive and unacceptable, except perhaps on a fully-informed opt-in basis.  When I use a search engine -- let's say Google -- I am expressing an implicit belief that my search data will not be abused or misused by Google.  I have made no such determinations regarding any use in any manner of this search query&lt;br /&gt;data by ISPs or their partners.&lt;br /&gt;&lt;br /&gt;I'm communicating with Google.  Period.  I don't care if the ISPs claim that the data is quickly discarded, or anonymized so well that it looks like an iPhone that's been put through a blender ( &lt;a wot1204836827781="youtube.com" href="http://youtube.com/watch?v=qg1ckCkm8YI" target="_blank"&gt;http://youtube.com/watch?v&lt;wbr&gt;=qg1ckCkm8YI&lt;/a&gt; ), nobody but Google and I have any rights to those search terms!&lt;br /&gt;&lt;br /&gt;And we all know that search keywords can be very sensitive.  Names, addresses, social security numbers (sloppy, but people do it), searches for new words to be used for domains or product names -- all manner of personally and commercially sensitive information can be found in search query data.&lt;br /&gt;&lt;br /&gt;Anyone who tried this stunt on such a basis with physical mail or phone calls they'd probably land in prison.  But ISPs are increasingly pushing the envelope in terms of spying on and even altering subscriber Web traffic.  This latest example is utterly beyond the pale, and it's hard to see how such abusive behavior can continue to pass legal muster indefinitely.&lt;br /&gt;&lt;br /&gt;If subscribers wish to opt-in to such systems with a full understanding of what's involved -- well, I wouldn't recommend it but that's their choice.  However, if these systems are fully deployed in a manner that requires subscribers to opt-out to avoid having their communications with Google and other search engines being intercepted, then I foresee some very angry subscribers, and a particular search services giant who will likely be anything but amused.&lt;/blockquote&gt;Wake up people. Write to your MP. Cancel your phone service. Call Jeremy Vine. This is appalling behaviour from a cynical monopolist who is moving tens of thousands of jobs abroad, (as an insider told me "90% of the work will be done offshore") and happily raking in profits through the abuse of its customers.&lt;br /&gt;&lt;br /&gt;Webwise? Terribly patronising name. WebStupid more like.&lt;br /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=bBaSj1"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=bBaSj1" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=QTAIO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=QTAIO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=QvkVo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=QvkVo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=x7Nho"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=x7Nho" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=IiI1o"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=IiI1o" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895925" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/351230044840548746/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=351230044840548746" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/351230044840548746?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/351230044840548746?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895925/we-dont-care-we-dont-have-to-were-phone.html" title="We don't care, we dont have to, we're the phone company" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/we-dont-care-we-dont-have-to-were-phone.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-510419947584757793</id><published>2008-03-04T16:19:00.001Z</published><updated>2008-03-04T16:21:39.154Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-04T16:21:39.154Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="humour" /><category scheme="http://www.blogger.com/atom/ns#" term="music" /><title type="text">I'm doing Science, I'm still alive</title><content type="html">&lt;em&gt;Now these points of data make a beautiful line.&lt;br /&gt;And we're out of beta.&lt;br /&gt;We're releasing on time.&lt;/em&gt;&lt;br /&gt;&lt;br /&gt;&lt;object height="355" width="425"&gt;&lt;param name="movie" value="http://www.youtube.com/v/Y6ljFaKRTrI"&gt;&lt;param name="wmode" value="transparent"&gt;&lt;embed src="http://www.youtube.com/v/Y6ljFaKRTrI" type="application/x-shockwave-flash" wmode="transparent" width="425" height="355"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;br /&gt;&lt;br /&gt;More at &lt;a href="http://www.youtube.com/watch?v=Y6ljFaKRTrI"&gt;http://www.youtube.com/watch?v=Y6ljFaKRTrI&lt;/a&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=5sSmaB"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=5sSmaB" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=10D3O"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=10D3O" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=f37zo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=f37zo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=m1lro"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=m1lro" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=4NWHo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=4NWHo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895926" height="1" width="1"/&gt;</content><link rel="related" href="http://www.youtube.com/watch?v=Y6ljFaKRTrI" title="I'm doing Science, I'm still alive" /><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/510419947584757793/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=510419947584757793" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/510419947584757793?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/510419947584757793?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895926/im-doing-science-im-still-alive.html" title="I'm doing Science, I'm still alive" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/im-doing-science-im-still-alive.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-1934653499085766922</id><published>2008-03-03T12:35:00.001Z</published><updated>2008-03-03T12:38:07.264Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-03T12:38:07.264Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="computer security" /><category scheme="http://www.blogger.com/atom/ns#" term="scribd" /><title type="text">White Paper - SABSA</title><content type="html">&lt;script&gt;document.write('&lt;noscript&gt;');&lt;/script&gt; &lt;object codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=9,0,0,0" id="embedded_flash_2206800_50905_object" name="embedded_flash_2206800_50905_object" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" align="middle" height="500" width="100%"&gt;&lt;param name="flashvars" value="&amp;document_id=2206800&amp;access_key=key-14g5hzgdicuun8w2dz0u&amp;page="&gt;  &lt;param name="movie" value="http://documents.scribd.com/ScribdViewer.swf"&gt;   &lt;param name="quality" value="high"&gt;   &lt;param name="play" value="true"&gt;  &lt;param name="loop" value="true"&gt;   &lt;param name="scale" value="showall"&gt;  &lt;param name="wmode" value="opaque"&gt;   &lt;param name="devicefont" value="false"&gt;  &lt;param name="bgcolor" value="#ffffff"&gt;   &lt;param name="menu" value="true"&gt;  &lt;param name="allowFullScreen" value="true"&gt;   &lt;param name="allowScriptAccess" value="always"&gt;   &lt;param name="salign" value=""&gt;  &lt;embed flashvars="&amp;document_id=2206800&amp;access_key=key-14g5hzgdicuun8w2dz0u&amp;page=" src="http://documents.scribd.com/ScribdViewer.swf" quality="high" pluginspage="http://www.macromedia.com/go/getflashplayer" play="true" loop="true" scale="showall" wmode="opaque" devicefont="false" bgcolor="#ffffff" name="embedded_flash_2206800_50905_object" menu="true" allowfullscreen="true" allowscriptaccess="always" salign="" type="application/x-shockwave-flash" align="middle" height="500" width="100%"&gt;&lt;/embed&gt; &lt;/object&gt;&lt;/noscript&gt;&lt;script type="text/javascript" src='http://www.scribd.com/javascripts/view.js'&gt;&lt;/script&gt;&lt;div id='embedded_flash_2206800_50905' style="width:100%;height:100%"&gt;&lt;span style="display:none"&gt;Read this doc on Scribd: &lt;a href="http://www.scribd.com/doc/2206800/SABSA-White-Paper"&gt;SABSA White Paper&lt;/a&gt;&lt;/span&gt; &lt;/div&gt; &lt;script type="text/javascript"&gt;  var scribd_doc = new scribd.Document(2206800, 'key-14g5hzgdicuun8w2dz0u');       scribd_doc.write('embedded_flash_2206800_50905');&lt;/script&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=hf81Dz"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=hf81Dz" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=NtOuO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=NtOuO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=5Ju6o"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=5Ju6o" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=ZfAYo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=ZfAYo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=X9Kgo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=X9Kgo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895927" height="1" width="1"/&gt;</content><link rel="related" href="http://www.scribd.com/full/2206800?access_key=key-14g5hzgdicuun8w2dz0u" title="White Paper - SABSA" /><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/1934653499085766922/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=1934653499085766922" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/1934653499085766922?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/1934653499085766922?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895927/white-paper-sabsa.html" title="White Paper - SABSA" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/white-paper-sabsa.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-1757858788909766836</id><published>2008-03-03T10:09:00.002Z</published><updated>2008-03-03T10:53:04.534Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-03-03T10:53:04.534Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="identity" /><title type="text">Hooray, yet another online ID</title><content type="html">I've just signed up for online access to my GP's surgery. I have three new pieces of identity information:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;A numeric Practice number&lt;/li&gt;&lt;li&gt;A numeric access ID&lt;/li&gt;&lt;li&gt;A password (which mercifully I got to chose)&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;I understand that &lt;a href="http://www.emis-online.com/"&gt;E-MIS &lt;/a&gt;need this information to register me, but why can't I then associate my &lt;a href="http://www.openid.net/"&gt;OpenID&lt;/a&gt;, or my &lt;a href="http://www.verisign.com/products-services/security-services/unified-authentication/"&gt;token &lt;/a&gt;with my account for authentication?&lt;/p&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=iPWqcT"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=iPWqcT" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=gCLtO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=gCLtO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=biyvo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=biyvo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=3HQXo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=3HQXo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=7h7oo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=7h7oo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895928" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/1757858788909766836/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=1757858788909766836" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/1757858788909766836?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/1757858788909766836?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895928/hooray-yet-another-online-id.html" title="Hooray, yet another online ID" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/03/hooray-yet-another-online-id.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-9147985382784645561</id><published>2008-02-29T09:21:00.003Z</published><updated>2008-02-29T09:57:14.975Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-29T09:57:14.975Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Fraud" /><title type="text">When you're in a good mood, all your creativity goes out the window</title><content type="html">&lt;div align="justify"&gt;I think it may have something to do with actually getting enough sleep last night. So in a fit of lazyblogging, I read this article on CIO.com about &lt;a href="http://www.cio.com/article/189400/Tips_for_Honing_the_Auditor_s_Interviewing_Skills"&gt;interviewing skills&lt;/a&gt;. Its not bad, and covers the basics, although I was struck with laughter when I read the advisory note on "witness intidimation", wondering whether the author was for it or against it! Reading this won't turn you into &lt;a href="http://en.wikipedia.org/wiki/Leroy_Jethro_Gibbs"&gt;Gibbs&lt;/a&gt;, and it doesn't deal with other issues such as when to make (or break) &lt;a href="http://en.wikipedia.org/wiki/Rapport"&gt;rapport&lt;/a&gt;, or how to take control over the interview. (For example: questions such as "what happens if the witness wants to record the interview" means you are not in control).&lt;/div&gt;&lt;div align="justify"&gt; &lt;/div&gt;&lt;div align="justify"&gt;Furthermore, Muffett has pointed me at "&lt;a href="http://duckdown.blogspot.com/2008/02/ten-mistakes-that-cios-consistently.html"&gt;Ten Mistakes that CIOs consistently make that weaken enterprise security&lt;/a&gt;". Interesting, funny, insightful reading. Its worth quoting here (because this is a lazy blog day after all). &lt;/div&gt;&lt;ul&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Use process as a substitute for competence:&lt;/strong&gt; The answer to &lt;a href="http://enterprisearchitect.typepad.com/" target="_new"&gt;every problem is almost always methodology&lt;/a&gt;, so you must focus savagely on CMMi and ITIL while not understanding the fact that hackers attack software.&lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Ostritch Principle&lt;/strong&gt;: Since you were so busy aligning with the business which really means that you are neither a real IT professional nor business professional, you have spent much of your time perfecting memorization of cliche phrases and nomenclature and hoping that the problem will go away if you ignore it.&lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Putting network engineers in charge of security&lt;/strong&gt;: When will you learn that folks with a network background can't possibly make your enterprise secure. If a hacker attacks software and steals data yet you respond with hardware, whom do you really think is going to win the battle.&lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Over Rely on your vendors by relabelling them as partners:&lt;/strong&gt; You trust your software vendors and outsourcing firms so much that you won't even perform due diligence on their staff to understand whether they have actually received one iota of training&lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Rely primarily on a firewall and antivirus:&lt;/strong&gt; Here is a revelation. Firewalls are not security devices, they are more for network hygiene. Ever consider that a firewall can't possibly stop attacks related to cross site scripting, SQL injection and so on. Network devices only protect the network and can't do much nowadays to protect applications.&lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Stepping in your own leadership&lt;/strong&gt;: Authorize reactive, short-term fixes so problems re-emerge rapidly &lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Thinking that security is expensive while also thinking that CMMi isn't&lt;/strong&gt;: Why do you continue to fail to realize how much money their information and organizational reputations are worth.&lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;The only thing you need is an insulting firm to provide you with a strategy:&lt;/strong&gt; Fail to deal with the operational aspects of security: make a few fixes and then not allow the follow through necessary to ensure the problems stay fixed &lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Getting it twisted to realize that Business / IT alignment is best accomplished by talking about Security and not SOA: &lt;/strong&gt;Failing to understand the relationship of information security to the business problem -- they understand physical security but do not see the consequences of poor information security. Let's be honest, your SOA is all about integration as you aren't smart enough to do anything else.&lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;&lt;strong&gt;Put people in roles and give them titles, but don't actually train them:&lt;/strong&gt; Assign untrained people to maintain security and provide neither the training nor the time to make it possible to do the job.&lt;/div&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p align="justify"&gt;I'd add another one to this list - "Outsource everything in the belief that IT is non-core". IT, like it or not, is not only the brains, but the entire digital nerve system of your organisation. Handing it over to people who are paid a tenth of what you pay your own staff, and don't be surprised if your digital nerve system gives your organisation Parkinson's disease.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=hwsqfj"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=hwsqfj" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=vBVsO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=vBVsO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=aomDo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=aomDo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=4iD8o"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=4iD8o" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=YhUso"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=YhUso" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895929" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/9147985382784645561/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=9147985382784645561" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/9147985382784645561?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/9147985382784645561?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895929/when-youre-in-good-mood-all-your.html" title="When you're in a good mood, all your creativity goes out the window" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/when-youre-in-good-mood-all-your.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-541152484995512059</id><published>2008-02-26T18:26:00.002Z</published><updated>2008-02-26T18:28:58.326Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-26T18:28:58.326Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="cynicsm" /><category scheme="http://www.blogger.com/atom/ns#" term="current affairs" /><category scheme="http://www.blogger.com/atom/ns#" term="data protection" /><category scheme="http://www.blogger.com/atom/ns#" term="information warfare" /><category scheme="http://www.blogger.com/atom/ns#" term="government" /><title type="text">We could tell you, but then we'd have to tax you</title><content type="html">&lt;span style="font-weight: bold;"&gt; Scenario:&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;I suspect fraudulent use of National Insurance Numbers. I go to HMRC website and find this page:&lt;br /&gt;&lt;br /&gt;&lt;a wot1204019252156="www.hmrc.gov.uk" href="http://www.hmrc.gov.uk/manuals/nimmanual/NIM39100.htm" target="_blank"&gt;http://www.hmrc.gov.uk/manuals&lt;wbr&gt;/nimmanual/NIM39100.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;hmm NIM39140 looks like what I need so I click on it. Go on try it.&lt;br /&gt;&lt;br /&gt;My flabber is ghasted, but its nice to see HMRC taking confidentiality of information seriously.
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=VepKdI"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=VepKdI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=vbRKO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=vbRKO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=rNMlo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=rNMlo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=zObLo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=zObLo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=1svRo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=1svRo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895930" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/541152484995512059/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=541152484995512059" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/541152484995512059?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/541152484995512059?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895930/we-could-tell-you-but-then-wed-have-to.html" title="We could tell you, but then we'd have to tax you" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/we-could-tell-you-but-then-wed-have-to.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-1558246395264508717</id><published>2008-02-26T08:57:00.005Z</published><updated>2008-02-26T12:46:40.651Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-26T12:46:40.651Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="network" /><category scheme="http://www.blogger.com/atom/ns#" term="information warfare" /><category scheme="http://www.blogger.com/atom/ns#" term="Net neutrality" /><title type="text">BGP stands for Bring Complete Paranoia</title><content type="html">&lt;div align="justify"&gt;Rory Cellan writes in his &lt;a href="http://www.bbc.co.uk/blogs/technology/2008/02/youtube_and_pakistan_how_did_i.html"&gt;BBC blog &lt;/a&gt;that:&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;&lt;em&gt;&lt;blockquote&gt;&lt;p align="justify"&gt;&lt;em&gt;So the Pakistani authorities order the country's ISPs to block access to&lt;br /&gt;YouTube. That is done by the country's telecoms provider sending out what is, in&lt;br /&gt;effect, a new - and false - route to get to YouTube. The result is that any&lt;br /&gt;traffic from Pakistani users to YouTube gets directed into a cul-de-sac. So far,&lt;br /&gt;so normal, for any country - China, Turkey, Iran - which decides to control its&lt;br /&gt;population's access to certain websites.&lt;br /&gt;But what appears to have happened in this case is that the dodgy route map somehow leaked beyond Pakistan's borders, and was adopted by the giant Asian telecoms business &lt;/em&gt;&lt;a href="http://www.pccw.com/eng/"&gt;&lt;em&gt;PCCW&lt;/em&gt;&lt;/a&gt;&lt;em&gt;. Once it started broadcasting this new way to find YouTube, the rest of the world's ISPs altered their maps, sending everyone up the wrong road.&lt;/em&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;/em&gt;&lt;div align="justify"&gt;&lt;br /&gt;&lt;/div&gt;&lt;p align="justify"&gt;Now, I'm no longer a network engineer. Terribly bright people now shepherd Internet traffic around the world, carefully grooming and optimising traffic routes between the different Internet "clouds" (known more formally as Autonomous Systems, or AS). In fact, the BBC is an AS, as is BT, and most big ISPs are autonomous. This means that clouds can choose which way is best for traffic going into - and out of - their cloud. So for example my ISP at home can decide that the best way for me to get traffic to and from Australia, for example, is via a cheaper (but longer) land link running through Asia, than by a satellite hop. And they'd probably be right, satellite links tend to be slooow.&lt;br /&gt;&lt;br /&gt;What happens here is an issue of &lt;em&gt;transitive trust&lt;/em&gt;. Most "peering agreements" (the name for the decisions two AS's make to send traffic between each other) are technically complex, and some include the following rules:&lt;br /&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;div align="justify"&gt;If I can't send traffic to another third party directly, I'll send it to you.&lt;/div&gt;&lt;/li&gt;&lt;li&gt;&lt;div align="justify"&gt;If you can't send traffic to another third party directly, you can send it to me.&lt;/div&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p align="justify"&gt;Those two rules sound pretty simple, however they're pretty important. The question then arises how does an AS know where it can and cannot send traffic to? Enter the Border Gateway Protocol, or BGP for short. BGP controls &lt;em&gt;routing information&lt;/em&gt; which can be thought of as meta-data on the traffic. Its an automated system for updating clouds on which other clouds can be reached through each other. Then the router decides which route is the shortest (or best in some other way configured by its network engineers - for example, "send as much traffic as possible over the cheap landline rather than over the expensive satellite link") and voila, you get to see the Google homepage.&lt;/p&gt;&lt;p align="justify"&gt;There is a whole industry built up around providing expertise and BGP services, from companies like &lt;a href="http://www.internap.com/"&gt;InterNAP&lt;/a&gt;, and industry associations such as &lt;a href="http://www.linx.net/"&gt;LINX&lt;/a&gt;. BGP routes get used to advertise places we shouldn't go - for example, some anti-spam services provide a list of IP addresses that network engineers can say "don't try and send traffic here". It can include malware sites, persistent spammers, and as we've seen, a government can mandate that all traffic can be dropped and that all routers in a particular jurisdiction must carry this "&lt;a href="http://en.wikipedia.org/wiki/Internet_death_penalty"&gt;internet death penalty&lt;/a&gt;". &lt;/p&gt;&lt;p align="justify"&gt;Where this becomes a security issue, is that BGP is designed to propagate the "best" routing information around the internet. This is designed to assist the internet's self-healing process, so if a cable going under the atlantic is cut - separating a link between two clouds, other routes are automatically brought into play. If you have a collection of routers who say "We know that the best route to youtube.com is to just drop the traffic on the floor", they will announce this route to their peers, and the peers will pick this up, announcing it to their peers, and so on. &lt;/p&gt;&lt;p align="justify"&gt;This is a &lt;em&gt;transitive trust&lt;/em&gt; issue. While network engineers can force the routers to filter the routes sent to them, most of the time they prefer not to - and why would I be jaded and cynical about a peering ISP who I know well and probably go for drinks with their staff? Well, we've seen the answer. &lt;/p&gt;&lt;p align="justify"&gt;Security pro's would note that the potential for damage of wild and crazy routes being propagated across the Internet, both in terms of PR damage, lost time, and so on, would be worth the mitigation cost of filtering out bogus routes before they are adopted into the routing tables, however ISP's typically focus on availability, throughput - all the things that their customers demand. Network Engineers are highly skilled people, but they're not security experts.&lt;/p&gt;&lt;p align="justify"&gt;All this puts an interesting slant on the arguments for and against &lt;a href="http://en.wikipedia.org/wiki/Network_neutrality"&gt;Net Neutrality&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=4qH83K"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=4qH83K" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=yYb3O"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=yYb3O" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=hJMro"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=hJMro" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=DmDKo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=DmDKo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=QE0oo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=QE0oo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895931" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/1558246395264508717/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=1558246395264508717" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/1558246395264508717?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/1558246395264508717?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895931/bgp-stands-for-bring-complete-paranoia.html" title="BGP stands for Bring Complete Paranoia" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/bgp-stands-for-bring-complete-paranoia.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-2387255586062431506</id><published>2008-02-26T08:45:00.002Z</published><updated>2008-02-26T08:51:08.671Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-26T08:51:08.671Z</app:edited><title type="text">This is not news</title><content type="html">&lt;a href="http://searchsecurity.techtarget.com/news/article/0,289142,sid14_gci1299156,00.html?track=sy160&amp;amp;asrc=RSS_RSS-10_160"&gt;Deloitte reports &lt;/a&gt;that:&lt;br /&gt;&lt;blockquote&gt;IT security pros working in the technology, telecommunications, media and&lt;br /&gt;entertainment industries say they're confident they can handle external security&lt;br /&gt;threats, but nearly half lack a formal security strategy, according to a new&lt;br /&gt;survey&lt;/blockquote&gt;&lt;br /&gt;Indeed true. And without a strategy, there's no planning. Without planning, there's no real threat and risk control. Without threat and risk control, then we're back to the good 'ol "Hey! We gotta firewall!" (or&lt;em&gt; insert-the-name-of-your-favourite-new-appliance-here&lt;/em&gt;) approach.
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=KQkT0X"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=KQkT0X" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=u9uLO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=u9uLO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=hwDKo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=hwDKo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=IX1xo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=IX1xo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=VkMko"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=VkMko" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895932" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/2387255586062431506/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=2387255586062431506" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/2387255586062431506?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/2387255586062431506?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895932/this-is-not-news.html" title="This is not news" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/this-is-not-news.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-1640031919460378334</id><published>2008-02-25T13:22:00.002Z</published><updated>2008-02-25T13:26:46.359Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-25T13:26:46.359Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Fraud" /><title type="text">How to spot a boiler room</title><content type="html">&lt;div style="text-align: justify;"&gt;&lt;span style="font-style: italic;"&gt;I received the following post from the Motley Fool financial investing service. Not that I have any cash to invest, but the following is very good anti-fraud advice.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;As our 'Good, Bad and the Ugly email campaign continues, we look at a nasty share scam - the 'boiler room'.&lt;br /&gt;I think the 'boiler room' is the ugliest financial scam of them all.&lt;br /&gt;Telesales staff outside the UK call up unsuspecting private investors and pressure them to buy dodgy shares at inflated prices. Some people believe the crooks' sales patter and frequently they end up losing all the money they've invested. Don't assume that it won't happen to you. Often the victims are pretty sophisticated folk who have been playing the markets for ten years or more.&lt;br /&gt;Indeed, the Financial Services Authority (FSA) has highlighted one case where a management consultant in his 50s lost 40,000 to a boiler room scam, and he had been investing in the stock market for 12 years.&lt;br /&gt;&lt;a wot1203873443890="www.lnksrv.com" href="http://www.lnksrv.com/m.asp?i=2464668&amp;amp;u=1473957" target="_blank"&gt;http://www.lnksrv.com/m.asp?i&lt;wbr&gt;=2464668&amp;amp;u=1473957&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt; How does it work?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Boiler rooms are always based outside the UK and are not regulated by the FSA. The boiler rooms use various techniques to get hold of names to call. They can follow up initial market research calls or call up investors on shareholder registers of small companies. Dealers can then offer free research on a punter's favourite share, and a relationship can be built from there. Or you might be offered free research via junk mail. If you send a reply card back with a tick in a particular box, the dealing room can then claim it's making a legitimate phone call.&lt;br /&gt;Often the boiler room salespeople push shares that 'are about to IPO' (list on the stock market) and 'big profits' can be expected. More often than not, the company never lists and the investors lose all their cash. Sometimes the shares are listed, often on fairly obscure markets such as the 'pink sheets' in the US. On occasion, the shares are listed on better known exchanges, but either way there's a good chance that the share price will start to fall shortly after you've paid your cash. What's more, the boiler room may have taken an outrageously high dealing commission.&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Why does it work?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The boiler rooms don't give up easily. They will constantly call a target, trying to build a relationship and get their confidence. According to FSA research, six out of ten targets were pursued for at least a month regardless of whether they purchased shares. Nearly a quarter of targets said they were receiving calls from the same boiler room for more than a year.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;What can you do?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;If you're cold-called by somebody trying to sell you a share, be very suspicious indeed. If it's such a sure thing, why is he ringing up complete strangers and telling them about it? The simplest approach is to hang up as quickly as possible. If your curiosity won't let you do that, you can check the FSA's list of unauthorised overseas firms that are targeting UK investors. But if a firm isn't on the list, don't assume it's a kosher operation. Boiler rooms frequently change names to get around this.&lt;br /&gt;&lt;a wot1203873443890="www.lnksrv.com" href="http://www.lnksrv.com/m.asp?i=2464669&amp;amp;u=1473957" target="_blank"&gt;http://www.lnksrv.com/m.asp?i&lt;wbr&gt;=2464669&amp;amp;u=1473957&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;You can find out much more about boiler rooms in this excellent FAQ compiled by star poster JakNife on our discussion boards. Also read these useful tips by my Foolish friend David Kuo.&lt;br /&gt;&lt;a wot1203873443890="www.fool.co.uk" href="http://www.fool.co.uk/m.asp?i=2464670&amp;amp;u=1473957" target="_blank"&gt;http://www.fool.co.uk/m.asp?i&lt;wbr&gt;=2464670&amp;amp;u=1473957&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a wot1203873443890="www.fool.co.uk" href="http://www.fool.co.uk/m.asp?i=2464671&amp;amp;u=1473957" target="_blank"&gt;http://www.fool.co.uk/m.asp?i&lt;wbr&gt;=2464671&amp;amp;u=1473957&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&gt; Anatomy Of A Boiler Room Scam&lt;br /&gt;&lt;br /&gt;&lt;a wot1203873443890="www.fool.co.uk" href="http://www.fool.co.uk/m.asp?i=2464672&amp;amp;u=1473957" target="_blank"&gt;http://www.fool.co.uk/m.asp?i&lt;wbr&gt;=2464672&amp;amp;u=1473957&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&gt; How To Spot A Scam&lt;br /&gt;&lt;br /&gt;&lt;a wot1203873443890="www.fool.co.uk" href="http://www.fool.co.uk/m.asp?i=2464673&amp;amp;u=1473957" target="_blank"&gt;http://www.fool.co.uk/m.asp?i&lt;wbr&gt;=2464673&amp;amp;u=1473957&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=CqU6i3"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=CqU6i3" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=5STwO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=5STwO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=UrVBo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=UrVBo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=6scjo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=6scjo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=Ty6Po"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=Ty6Po" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895933" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/1640031919460378334/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=1640031919460378334" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/1640031919460378334?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/1640031919460378334?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895933/how-to-spot-boiler-room.html" title="How to spot a boiler room" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/how-to-spot-boiler-room.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-8821481155203190649</id><published>2008-02-25T11:27:00.009Z</published><updated>2008-02-25T15:30:10.934Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-25T15:30:10.934Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="virus" /><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="instant messenger" /><title type="text">Get hacked by google, bush, and hotmail</title><content type="html">&lt;div style="text-align: justify;"&gt;Over the weekend, I got the following message on MSN.&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;&lt;table id="BodyTable" style="table-layout: fixed; font-size: 67%; vertical-align: top; text-align: left; margin-left: 0px; margin-right: 0px;" cellspacing="0"&gt;&lt;tbody style="vertical-align: top;"&gt;&lt;tr style="background-color: rgb(224, 237, 255);"&gt; &lt;td&gt;23/02/2008&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;22:43:03&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;Jonathan *mssoc&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;d@hotmail.com&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;&lt;span style="color: rgb(0, 0, 0);font-family:MS Shell Dlg;" &gt;:)&lt;/span&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr style="background-color: rgb(224, 237, 255);"&gt; &lt;td&gt;23/02/2008&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;22:44:04&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;Jonathan *mssoc&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;d@hotmail.com&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;&lt;span style="color: rgb(0, 0, 0);font-family:MS Shell Dlg;" &gt;hey&lt;/span&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr style="background-color: rgb(224, 237, 255);"&gt; &lt;td&gt;23/02/2008&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;22:44:04&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;Jonathan *mssoc&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;d@hotmail.com&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;&lt;span style="color: rgb(0, 0, 0);font-family:MS Shell Dlg;" &gt;it watches this  animation of bush :P&lt;/span&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr style="background-color: rgb(224, 237, 255);"&gt; &lt;td&gt;23/02/2008&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;22:44:04&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;Jonathan *mssoc&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;d@hotmail.com&lt;/td&gt; &lt;td&gt;&lt;br /&gt;&lt;/td&gt; &lt;td&gt;&lt;span style="color: rgb(0, 0, 0);font-family:MS Shell Dlg;" &gt;http://[deleted].googlepages.com/bush.exe&lt;/span&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;div style="text-align: justify;"&gt;&lt;br /&gt;I've changed the name of the sender, and deleted the googlepages website name, because frankly, you don't want the ball of infection that is &lt;span style="font-family:courier new;"&gt;bush.exe&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;First thing is, never run an .exe from the internet. Even if your friend has told you its safe (How do they know? Answer most commonly given "Well it didn't trip out my copy of McAfee").  As we'll see, even downloading the little pucker can be hazardous.&lt;br /&gt;&lt;br /&gt;Normally when I do malware research, I use the electronic equivalent of thick rubber gloves and a bacterial safety screen. No one is pleased when malware stomps all over their system, including me.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.alwil.com/"&gt;Avast&lt;/a&gt; didn't pick it up. Not quite trusting one AV, I submitted the result to &lt;a href="http://www.virustotal.com/analisis/8f6a088e4ef41f4db28957ce7314537f"&gt;VirusTotal&lt;/a&gt;, and the scan results showed a couple of potential heuristic nasties (the link is to the report). In the meantime, I deleted bush.exe unopened.&lt;br /&gt;&lt;br /&gt;And this is where it went wrong.&lt;br /&gt;&lt;br /&gt;You see, even deleting a file (or moving it to the Recycle Bin) counts as an access to a file. On access virus scanners open up a packed file (like bush.exe) to see what's inside. This means that code set to execute when the file is opened... does. The next thing I knew, my resident protection for &lt;a href="http://www.safer-networking.org/"&gt;Spybot S&amp;amp;D &lt;/a&gt;was going crazy.&lt;br /&gt;By the way, Spybot S&amp;amp;D is freeware. If you don't have it installed, either you didn't know about it (you do now), or you are certifiably crazy. Go install it now, I'll wait.&lt;br /&gt;&lt;br /&gt;Spybot reported that three new files had appeared, and were trying to insert themselves into my startup. Those files:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;C:\WINDOWS\CYA.EXE&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;C:\WINDOWS\WINLOGON.EXE&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;C:\WINDOWS\LSASS.EXE&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;They picked C:\WINDOWS because that's the default setting of the %temp% variable in Windows. There are times when UNIX's &lt;span style="font-family:courier new;"&gt;/tmp&lt;/span&gt; folder looks eminently more sensible than using a system executable folder to drop stuff in, and this is indeed one of them.&lt;br /&gt;&lt;br /&gt;A popup appeared (in Spanish) asking me to install the latest Flash player. Oops. Clicking "don't install" did not help, and Spybot screamed at me for firing off more instances of the virus. I blacklisted the processes from adding themselves to my startup registry, and spybot went ballistic, warning me that this thing was indeed running rife through my system, trying to infect as much as possible.&lt;br /&gt;&lt;br /&gt;So, while spybot was ringing every alarm bell it could find to let me know I had a problem (Houston?) and bringing my machine to a crawl, I fired up &lt;a href="http://www.neuber.com/taskmanager/index.html"&gt;Security Task Manager&lt;/a&gt; (not free, but useful) and quarantined the nasty processes. I booted from clean, ran a startup AV scan. Everything looked ok.&lt;br /&gt;&lt;br /&gt;This took about 2 hours, and the lessons I'd pass on are:&lt;br /&gt;&lt;/div&gt;&lt;ul style="text-align: justify;"&gt;&lt;li&gt;Don't ever download and run an .exe file. My friend didn't even know that I'd received this message from her, as it fires up windows messenger silently (fortunately I have this set to block already).&lt;/li&gt;&lt;li&gt;Run Spybot. Its a line of defence.&lt;/li&gt;&lt;li&gt;If you absolutely must download these things, use a virtual machine (Microsoft's Virtual PC, or VMWare) and examine what's going on under a clean disk image. Then wipe and start afresh. Better not to.&lt;/li&gt;&lt;li&gt;Don't trust processes that "look good". &lt;span style="font-family:courier new;"&gt;WINLOGON.EXE&lt;/span&gt; and &lt;span style="font-family:courier new;"&gt;LSASS.EXE &lt;/span&gt;are both names of system processes, however they normally live in %systemdir% (&lt;span style="font-family:courier new;"&gt;C:\WINDOWS\SYSTEM32&lt;/span&gt;)&lt;/li&gt;&lt;li&gt;I got thwacked in the chops by being too careless, and was lucky. My friend still has this thing running around their machine. Not so good.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;div style="text-align: justify;"&gt;So, that was my weekend fun. How was yours?&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=ezm7qD"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=ezm7qD" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=vH2gO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=vH2gO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=H9tWo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=H9tWo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=ScdXo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=ScdXo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=vSqmo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=vSqmo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895934" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/8821481155203190649/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=8821481155203190649" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/8821481155203190649?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/8821481155203190649?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895934/get-hacked-by-google.html" title="Get hacked by google, bush, and hotmail" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/get-hacked-by-google.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-6532519701087405189</id><published>2008-02-24T18:36:00.003Z</published><updated>2008-02-24T19:42:54.930Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-24T19:42:54.930Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="information warfare" /><category scheme="http://www.blogger.com/atom/ns#" term="biometrics" /><category scheme="http://www.blogger.com/atom/ns#" term="myth" /><title type="text">Fingerprint scan at nursery door</title><content type="html">The BBC reports that a &lt;a href="http://news.bbc.co.uk/1/hi/wales/7247103.stm"&gt;nursery has installed fingerprint scanning at its entrance &lt;/a&gt;to increase the safety of its young pupils.&lt;br /&gt;&lt;br /&gt;In an interesting quote, UK Biometrics director Ryan Hole said: "By fitting a biometric access system they now have the one key that cannot be lost, stolen, forged or hacked - the human fingerprint".&lt;br /&gt;&lt;br /&gt;Some ways I can think of subverting a biometric access system:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Go in the window&lt;/li&gt;&lt;li&gt;Kick the door in&lt;/li&gt;&lt;li&gt;Lift a fingerprint (needs sellotape, google for it)&lt;/li&gt;&lt;li&gt;Bribe, con or coerce an authorised user. For example, "My finger doesn't work, I need to get my kid to the doctor now!" (Given that there is a Felinfoel pub just up the road, there is good beer available for bribery). &lt;/li&gt;&lt;li&gt;Wear a bandaid, bemoan the office shredder/photocopier/rabid secretary. Repeat the above con.&lt;/li&gt;&lt;li&gt;Tailgate behind an authorised user&lt;/li&gt;&lt;li&gt;Use someone else's authorised finger, having first thoughtfully removed it from their body&lt;/li&gt;&lt;li&gt;Exploit the software. All software has bugs, some bugs are interesting security holes. (attributed to &lt;a href="http://www.crypticide.com/"&gt;Muffett&lt;/a&gt;).&lt;/li&gt;&lt;li&gt;Get a rogue fingerprint on the database.&lt;/li&gt;&lt;li&gt;Grab a kid before (or after they go in the door). Better still, push the parents in the door, and shut it after them, so they have to use the fiddly biometric lock to get out.&lt;/li&gt;&lt;li&gt;Put superglue on the sensor. Wait until lock is removed. Enter.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;The point about all of this is that security "point solutions" don't work, neither in the physical world, nor in the exciting online world where all of our bank details slush about. Its essential that all risks are assessed, and solutions combined to make sure you don't just shift a threat from one attack point to the other (for example, no window locks means that the expensive biometric lock will actually remove very little risk). &lt;/p&gt;&lt;p&gt;The other things to think about are that when a failure of the security device occurs (not if), how will the nursery audit who went in and out of the nursery, and when? More importantly, if a "rogue" fingerprint gets into the database, how easy is it to detect and remove? Can I register my index finger under the print for the left little finger of the headmistress? &lt;/p&gt;&lt;p&gt;Most importantly, the risk of biometric systems is that the credentials &lt;em&gt;can&lt;/em&gt; be stolen. Fingerprints can be copied, and facsimile "fakers" make that duplicate the print of the target. Now if you find out that stanley's password is "yelnats", he can change it. But how do you change your fingerprint once its been lifted off a glass you drank from?&lt;/p&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=CtJQG6"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=CtJQG6" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=d2XiO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=d2XiO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=1WU7o"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=1WU7o" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=s82Io"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=s82Io" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=JH0eo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=JH0eo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895935" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/6532519701087405189/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=6532519701087405189" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/6532519701087405189?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/6532519701087405189?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895935/fingerprint-scan-at-nursery-door.html" title="Fingerprint scan at nursery door" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/fingerprint-scan-at-nursery-door.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-8373871586907918855</id><published>2008-02-24T03:17:00.004Z</published><updated>2008-02-24T11:32:49.731Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-24T11:32:49.731Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="current affairs" /><category scheme="http://www.blogger.com/atom/ns#" term="psychology" /><category scheme="http://www.blogger.com/atom/ns#" term="information warfare" /><title type="text">On Coercive Psychology</title><content type="html">&lt;div align="justify"&gt;I encountered someone who was into "The ISA Experience" recently. I was interested, then became aware how one of this person's goals was to recruit me into ISA. I'm not very recruitable. &lt;/div&gt;&lt;div align="justify"&gt;I found the following article on Coercive Psychology on &lt;a href="http://factnet.org/?p=275"&gt;F.A.C.T.Net&lt;/a&gt;, and its worth noting here. Remembering that the weakest link in Information Security is the soft squidgy thing in front of the keyboard, good ISO's should be aware of some of the pressures that can be brought to make people act abnormally.&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;WARNING&lt;/strong&gt;: This stuff is &lt;em&gt;nasty&lt;/em&gt;. You will win few friends if you deploy this sort of stuff in your daily lives (but it might be fun watching your local church group to see how many of these techniques accidentally get used).&lt;/div&gt;&lt;div align="justify"&gt;&lt;br /&gt;&lt;strong&gt;The Definition&lt;br /&gt;&lt;/div&gt;&lt;/strong&gt;&lt;div align="justify"&gt;Coercion is defined as “1. To force to act or think in a certain manner, 2. To dominate, restrain, or control by force, 3. To bring about by force.”&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;Coercive psychological systems are behavioral change programs which use psychological force in a coercive way to cause the learning and adoption of an ideology or designated set of beliefs, ideas, attitudes, or behaviors. The essential strategy used by the operators of these programs is to systematically select, sequence and coordinate many different types of coercive influence, anxiety and stress-producing tactics over continuous periods of time.&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;In such a program the subject is forced to adapt in a series of tiny “invisible” steps. Each tiny step is designed to be sufficiently small so the subjects will not notice the changes in themselves or identify the coercive nature of the processes being used. The subjects of these tactics do not become aware of the hidden organizational purpose of the coercive psychological program until much later, if ever. These tactics are usually applied in a group setting by well intentioned but deceived “friends and allies” of the victim. This keeps the victim from putting up the ego defenses we normally maintain in known adversarial situations.&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;/div&gt;&lt;div align="justify"&gt;The coercive psychological influence of these programs aims to overcome the individual’s critical thinking abilities and free will-apart from any appeal to informed judgment. Victims gradually lose their ability to make independent decisions and exercise informed consent. Their critical thinking, defenses, cognitive processes, values, ideas, attitudes, conduct and ability to reason are undermined by a technological process rather than by meaningful free choice, rationality, or the inherent merit or value of the ideas or propositions being presented.&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;How Do They Work?&lt;br /&gt;&lt;/strong&gt;&lt;/div&gt;&lt;div align="justify"&gt;The tactics used to create undue psychological and social influence, often by means involving anxiety and stress, fall into seven main categories.&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;TACTIC 1.&lt;/strong&gt; Increase suggestibility and “soften up” the individual through specific hypnotic or other suggestibility-increasing techniques such as: Extended audio, visual, verbal, or tactile fixation drills, Excessive exact repetition of routine activities, Sleep restriction, and/or Nutritional restriction.&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;TACTIC 2.&lt;/strong&gt; Establish control over the person’s social environment, time and sources of social support by a system of often-excessive rewards and punishments. Social isolation is promoted. Contact with family and friends is abridged, as is contact with persons who do not share group-approved attitudes. Economic and other dependence on the group is fostered.&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;TACTIC 3.&lt;/strong&gt; Prohibit disconfirming information and non supporting opinions in group communication. Rules exist about permissible topics to discuss with outsiders. Communication is highly controlled. An “in-group” language is usually constructed.&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;TACTIC 4.&lt;/strong&gt; Make the person re-evaluate the most central aspects of his or her experience of self and prior conduct in negative ways. Efforts are designed to destabilize and undermine the subject’s basic consciousness, reality awareness, world view, emotional control and defense mechanisms. The subject is guided to reinterpret his or her life’s history and adopt a new version of causality.&lt;br /&gt;&lt;/div&gt;&lt;strong&gt;&lt;/strong&gt;&lt;div align="justify"&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;TACTIC 5.&lt;/strong&gt; Create a sense of powerlessness by subjecting the person to intense and frequent actions and situations which undermine the person’s confidence in himself and his judgment.&lt;br /&gt;&lt;/div&gt;&lt;strong&gt;&lt;/strong&gt;&lt;div align="justify"&gt;&lt;strong&gt;TACTIC 6.&lt;/strong&gt; Create strong aversive emotional arousals in the subject by use of nonphysical punishments such as intense humiliation, loss of privilege, social isolation, social status changes, intense guilt, anxiety, manipulation and other techniques.&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;TACTIC 7.&lt;/strong&gt; Intimidate the person with the force of group-sanctioned secular psychological threats. For example, it may be suggested or implied that failure to adopt the approved attitude, belief, or consequent behavior will lead to severe punishment or dire consequences such as physical or mental illness, the reappearance of a prior physical illness, drug dependence, economic collapse, social failure, divorce, disintegration, failure to find a mate, etc.&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;These tactics of psychological force are applied to such a severe degree that the individual’s capacity to make informed or free choices becomes inhibited. The victims become unable to make the normal, wise or balanced decisions which they most likely or normally would have made, had they not been unknowingly manipulated by these coordinated technical processes. The cumulative effect of these processes can be an even more effective form of undue influence than pain, torture, drugs or the use of physical force and physical and legal threats. &lt;/div&gt;&lt;div align="justify"&gt;&lt;br /&gt;&lt;strong&gt;How does Coercive Psychological Persuasion Differ from Other Kinds of Influence?&lt;br /&gt;&lt;/strong&gt;Coercive psychological systems are distinguished from benign social learning or peaceful persuasion by the specific conditions under which they are conducted. These conditions include the type and number of coercive psychological tactics used, the severity of environmental and interpersonal manipulation, and the amount of psychological force employed to suppress particular unwanted behaviors and to train desired behaviors.&lt;br /&gt;Coercive force is traditionally visualized in physical terms. In this form it is easily definable, clear-cut and unambiguous. Coercive psychological force unfortunately has not been so easy to see and define. The law has been ahead of the physical sciences in that it has allowed that coercion need not involve physicalforce. It has recognized that an individual can be threatened and coerced psychologically by what he or she perceives to be dangerous, not necessarily by that which is dangerous.&lt;br /&gt;Law has recognized that even the threatened action need not be physical. Threats of economic loss, social ostracism and ridicule, among other things, are all recognized by law, in varying contexts, as coercive psychological forces. &lt;/div&gt;&lt;div align="justify"&gt;&lt;br /&gt;&lt;strong&gt;Why are Coercive Psychological Systems Harmful?&lt;/strong&gt;&lt;br /&gt;&lt;/div&gt;&lt;div align="justify"&gt;Coercive psychological systems violate our most fundamental concepts of basic human rights. They violate rights of individuals that are guaranteed by the First Amendment to the United States Constitution and affirmed by many declarations of principle worldwide.&lt;br /&gt;By confusing, intimidating and silencing their victims, those who profit from these systems evade exposure and prosecution for actions recognized as harmful and which are illegal in most countries such as:fraud, false imprisonment, undue influence, involuntary servitude, intentional infliction of emotional distress, outrageous conduct, and other tortious acts. &lt;/div&gt;
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=VbVQ9Z"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=VbVQ9Z" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=tSrTO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=tSrTO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=4OMro"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=4OMro" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=XMP6o"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=XMP6o" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=3Ppgo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=3Ppgo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895936" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/8373871586907918855/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=8373871586907918855" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/8373871586907918855?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/8373871586907918855?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895936/on-coercive-psychology.html" title="On Coercive Psychology" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/on-coercive-psychology.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-3207022297113414871</id><published>2008-02-23T14:47:00.004Z</published><updated>2008-02-23T16:39:52.785Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-23T16:39:52.785Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="humour" /><category scheme="http://www.blogger.com/atom/ns#" term="relationships" /><title type="text">51 things women wish men knew</title><content type="html">This is a public service announcement, shortly to be followed by "&lt;a href="http://www.menshealth.com/cda/article.do?site=MensHealth&amp;channel=sex.relationships&amp;category=hooking.up&amp;conitem=9fd767233a322110VgnVCM20000012281eac____"&gt;1056 things men wish women knew... well actually just one or two.&lt;/a&gt;"&lt;br /&gt;&lt;br /&gt;1. When you see a girl with huge knockers, do not go "Damn!" and then laugh appreciatively to yourself - we can hear you.&lt;br /&gt;&lt;br /&gt;2. Whenever possible, please say whatever you have to say during commercials.&lt;br /&gt;&lt;br /&gt;3. If you don't act like soap-opera guys, don't expect us to dress like Victoria Secret models.&lt;br /&gt;&lt;br /&gt;4. Mark anniversaries on a calendar.&lt;br /&gt;&lt;br /&gt;5. There is no such thing as too much spooning.&lt;br /&gt;&lt;br /&gt;6. Just because you L the C doesn't mean we have to S the D.&lt;br /&gt;&lt;br /&gt;7. This is how we see it . . . Don't call = Don't Care.&lt;br /&gt;&lt;br /&gt;8. Which also means that if we don't call, take the hint.&lt;br /&gt;&lt;br /&gt;9. We like you to be a little jealous . . . but overly possessive is not necessary.&lt;br /&gt;&lt;br /&gt;10. Putting things in our butt does not turn us on.&lt;br /&gt;&lt;br /&gt;11. Return favors: we massage, you massage; we shave, you shave (and not just your face).&lt;br /&gt;&lt;br /&gt;12. Foreplay is not an option . . . its a prerequisite.&lt;br /&gt;&lt;br /&gt;13. We're allowed to be late . . . you are not.&lt;br /&gt;&lt;br /&gt;14. Eye contact is key.&lt;br /&gt;&lt;br /&gt;15. Don't take longer to get ready than we do.&lt;br /&gt;&lt;br /&gt;16. Laugh at our jokes.&lt;br /&gt;&lt;br /&gt;17. Three words . . . honesty, honesty, honesty.&lt;br /&gt;&lt;br /&gt;18. Girls can be groupies. Guy groupies are stalkers.&lt;br /&gt;&lt;br /&gt;19. We never have to wonder if your orgasm was real.&lt;br /&gt;&lt;br /&gt;20. Do not start with us. You will not win... not kidding .. we ALWAYS win&lt;br /&gt;&lt;br /&gt;21. Would you like it if a guy treated your sister that way? We didn't think so.&lt;br /&gt;&lt;br /&gt;22. If you ask nicely, we usually answer the same way.&lt;br /&gt;&lt;br /&gt;23. We will never have enough clothes or shoes! Ever!&lt;br /&gt;&lt;br /&gt;24. We have an excuse to act bitchy at least once a month. Come on guys...most of you have more PMS then us girls..&lt;br /&gt;&lt;br /&gt;25. Open the door for us no matter where we are . . . even at our house and getting into the car. I know it seems like a lot but is it that hard?&lt;br /&gt;&lt;br /&gt;26. We love surprises!&lt;br /&gt;&lt;br /&gt;27. We liked to be kissed softly, not with an iron tongue.&lt;br /&gt;&lt;br /&gt;28.Pay attention to the little things we do, because they mean the most.&lt;br /&gt;&lt;br /&gt;29. Boxers and maybe boxer briefs sometiems . . . NEVER whitey-tighties, NEVER!&lt;br /&gt;&lt;br /&gt;30. Clean your room before we come over.&lt;br /&gt;&lt;br /&gt;31. Always brush your teeth before you see us . . . a fresh mouth and white teeth are a necessity plus we do the same for you.&lt;br /&gt;&lt;br /&gt;32. When we use our teeth it means that you suck at going down on us, so we are just returning the favor.&lt;br /&gt;&lt;br /&gt;33. Even though you are sometimes insensitive and hurt us, we still love you with everything we are.&lt;br /&gt;&lt;br /&gt;34. Sometimes even when you think we hate you, we don't, we just want you to apologize so we can be allowed to love you again&lt;br /&gt;&lt;br /&gt;35. Don't act hard around your friends because I won't make you hard tonight. AKA don't be an ass&lt;br /&gt;&lt;br /&gt;36. Sometimes "NO!" really means "NO!"&lt;br /&gt;&lt;br /&gt;37. "Wife Beaters" are not an adequate form of fashion.&lt;br /&gt;&lt;br /&gt;38. If we wanted to be on video tape, we'd be a porn star not your girlfriend.&lt;br /&gt;&lt;br /&gt;39. Sensitive guys are great . . . but crying more than we do in a movie just isn't right.&lt;br /&gt;&lt;br /&gt;40. Don't let ex-girlfriends cause drama, relationships are stressful enough!!!!!&lt;br /&gt;&lt;br /&gt;41. It takes a special kind of stupid to forget birthdays.&lt;br /&gt;&lt;br /&gt;42. Guys who are good cuddlers = guys who know how to satisfy a woman.&lt;br /&gt;&lt;br /&gt;43. "Fat Chicks" have feelings too--all chicks have feelings.&lt;br /&gt;&lt;br /&gt;44. Silent treatment + shoulder shrugs + tears + yelling + nasty looks = YOU DID SOMETHING WRONG!&lt;br /&gt;&lt;br /&gt;45. If you are not a good dancer, please be self-aware.&lt;br /&gt;&lt;br /&gt;46. Just because a girl doesn't pick up on the first ring doesn't mean she's not waiting by the phone.&lt;br /&gt;&lt;br /&gt;47. You don't have to spend a lot, if it means a lot.&lt;br /&gt;&lt;br /&gt;48. Don't say you love me if you don't mean it.&lt;br /&gt;&lt;br /&gt;49. Don't lie to us . . . we will catch you...eventually we always catch you.&lt;br /&gt;&lt;br /&gt;50. When the girls get together, we talk about EVERYTHING. Meaning my best friends know everything about you.&lt;br /&gt;&lt;br /&gt;51. Don't Make Promises You Can't Keep &lt;br /&gt;&lt;br /&gt;So, how many of those things were actually a surprise, gentlemen?
&lt;p&gt;&lt;a href="http://feeds.securitypractice.org/~a/SecurityPractice?a=yg654C"&gt;&lt;img src="http://feeds.securitypractice.org/~a/SecurityPractice?i=yg654C" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=4OKqO"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=4OKqO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=6rQXo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=6rQXo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=zjfYo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=zjfYo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.securitypractice.org/~f/SecurityPractice?a=VLeVo"&gt;&lt;img src="http://feeds.securitypractice.org/~f/SecurityPractice?i=VLeVo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.securitypractice.org/~r/SecurityPractice/~4/457895937" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.lacunae.org/feeds/3207022297113414871/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=6233015771421939379&amp;postID=3207022297113414871" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/3207022297113414871?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6233015771421939379/posts/default/3207022297113414871?v=2" /><link rel="alternate" type="text/html" href="http://feeds.securitypractice.org/~r/SecurityPractice/~3/457895937/51-things-women-wish-men-knew.html" title="51 things women wish men knew" /><author><name>Jonathan Care</name><uri>http://www.blogger.com/profile/14512533837971314322</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-sa/2.0/" /><feedburner:origLink>http://www.lacunae.org/2008/02/51-things-women-wish-men-knew.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-6233015771421939379.post-1787221512228514517</id><published>2008-02-22T00:55:00.006Z</published><updated>2008-02-24T11:08:05.106Z</updated><app:edited xmlns:app="http://purl.org/atom/app#">2008-02-24T11:08:05.106Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="openID" /><category scheme="http://www.blogger.com/atom/ns#" term="cool tools" /><category scheme="http://www.blogger.com/atom/ns#" term="work" /><category scheme="http://www.blogger.com/atom/ns#" term="innovation" /><category scheme="http://www.blogger.com/atom/ns#" term="scribd" /><category scheme="http://www.blogger.com/atom/ns#" term="publishing" /><title type="text">Scribd: doing sensible things with iPaper</title><content type="html">How do you