<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-6050101211475163815</id><updated>2012-01-27T20:01:09.541-08:00</updated><category term='mobile'/><category term='oregon'/><category term='ACLU'/><category term='nigerian'/><category term='FAQ'/><category term='securityfocus'/><category term='Retention'/><category term='joomla'/><category term='av'/><category term='congress'/><category term='development'/><category term='malware'/><category term='fbi'/><category term='privacy'/><category term='wal-mart'/><category term='swayze'/><category term='linkedin'/><category term='RMB'/><category term='Boston'/><category term='city hall'/><category term='ranum'/><category term='spy'/><category term='inexpensive'/><category term='armarix'/><category term='security program'/><category term='amazon'/><category term='secure coding'/><category term='krebs'/><category term='Career'/><category term='defacement'/><category term='Consultancy'/><category term='firewall'/><category term='russian'/><category term='Kineavy'/><category term='EC2'/><category term='Records'/><category term='Startup'/><category term='bots'/><category term='doj'/><category term='CISO'/><category term='facebook'/><category term='hack'/><category term='sneaky'/><category term='PCI'/><category term='breach'/><category term='ohio'/><category term='kodak'/><category term='safe handgund'/><category term='nhlogin'/><category term='congressman'/><category term='419'/><category term='legal'/><category term='cloud'/><category term='menino'/><category term='Growth'/><category term='tjx id theft PCI credit card breach'/><category term='public record law'/><category term='Consultant'/><category term='ATT'/><category term='antivirus'/><category term='HIPAA'/><category term='svr'/><category term='foia'/><category term='virus'/><category term='Red Eye Crew'/><category term='house'/><category term='Fortify'/><category term='Rocky Mountain Bank'/><category term='insecure design'/><category term='fail'/><category term='ISMS'/><category term='scam'/><category term='Mentoring'/><category term='google apps'/><category term='google'/><category term='DOS'/><category term='discovery'/><title type='text'>Technology/Security/Society Musings</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>JI</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>34</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-2669240654708853147</id><published>2012-01-27T20:01:00.000-08:00</published><updated>2012-01-27T20:01:09.547-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='sneaky'/><category scheme='http://www.blogger.com/atom/ns#' term='linkedin'/><category scheme='http://www.blogger.com/atom/ns#' term='privacy'/><title type='text'>LinkedIn's sneaky privacy policy change</title><content type='html'>[Only relevant if you are on LinkedIn]&lt;br /&gt;&lt;br /&gt;While the world is railing against Google's privacy policy change, LinkedIn has quietly opted in its members to a policy that says they can use the members'&lt;br /&gt;name/photo in advertisements.&lt;br /&gt;&lt;br /&gt;Forwarded email below:&lt;br /&gt;&lt;blockquote&gt;Some simple actions to be considered:&lt;br /&gt;&lt;br /&gt;1. Place the cursor on your name at the top right corner of the screen. From the small pull down menu that appears, select "settings"&lt;br /&gt;2. Then click "Account" on the left/bottom&lt;br /&gt;3. In the column next to Account, select the option "Manage Social Advertising"&lt;br /&gt;4. Finally un-tick the box "LinkedIn may use my name and photo in social advertising"&lt;br /&gt;5. and Save&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;I normally cringe when I see "tell all your contacts" but in this case I guess it is justified. So tell all your contacts.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-2669240654708853147?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/2669240654708853147/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=2669240654708853147' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2669240654708853147'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2669240654708853147'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2012/01/linkedins-sneaky-privacy-policy-change.html' title='LinkedIn&apos;s sneaky privacy policy change'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-2242105925615967209</id><published>2011-01-17T07:04:00.000-08:00</published><updated>2011-01-17T07:04:17.834-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='malware'/><category scheme='http://www.blogger.com/atom/ns#' term='krebs'/><category scheme='http://www.blogger.com/atom/ns#' term='bots'/><title type='text'>Malware kits becoming professional, with a ton of metrics</title><content type='html'>Krebs on Security has posted an image of the administration dashboard of 2 malware kits&lt;br /&gt;&lt;br /&gt;Here is one:&lt;br /&gt;&lt;a href="http://krebsonsecurity.com/wp-content/uploads/2010/12/dragon2.jpg" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="190" src="http://krebsonsecurity.com/wp-content/uploads/2010/12/dragon2.jpg" width="320" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Apart from the interesting background and the mis-spelled 'Unics' the analytics is very nice. After all, every cybercriminal businessman needs metrics!&lt;br /&gt;&lt;br /&gt;Here is the &lt;a href="http://krebsonsecurity.com/2011/01/exploit-packs-run-on-java-juice/" target="_blank"&gt;full post&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;While Brian talks about these being Java exploit packs, I am more alarmed by the professional (for lack of a better word) look of the kits. This is geared towards someone who wants to see what works and what does not so attacks can be fine-tuned or changed. And I am afraid it is going to get workse&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-2242105925615967209?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/2242105925615967209/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=2242105925615967209' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2242105925615967209'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2242105925615967209'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2011/01/malware-kits-becoming-professional-with.html' title='Malware kits becoming professional, with a ton of metrics'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-3445269606509250390</id><published>2010-06-29T05:33:00.000-07:00</published><updated>2010-06-29T13:42:27.794-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='spy'/><category scheme='http://www.blogger.com/atom/ns#' term='fbi'/><category scheme='http://www.blogger.com/atom/ns#' term='russian'/><category scheme='http://www.blogger.com/atom/ns#' term='svr'/><title type='text'>Russian spies and adhoc wi-fi</title><content type='html'>On June 28, 2010, the FBI arrested 10 Russian spies. The &lt;a href="http://www.cbsnews.com/htdocs/pdf/Complaint_1.pdf" target="_blank"&gt;complaint&lt;/a&gt; against two of them, Anna Chapman and Mikhail Semenko is fascinating. Instead of dead drops at cemeteries or brush-passes at crowded restaurants, these spies set up adhoc wireless networks between 2 laptops and exchanged information.&lt;br /&gt;&lt;br /&gt;The complaint first describes what an adhoc wireless network is:&lt;br /&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;/div&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;/div&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/_RaDk956KPXY/TCndpgIgMsI/AAAAAAAAAJ0/uHJxlSlk2Q4/s1600/russianspy-1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="145" src="http://2.bp.blogspot.com/_RaDk956KPXY/TCndpgIgMsI/AAAAAAAAAJ0/uHJxlSlk2Q4/s400/russianspy-1.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;and then cites many examples of how when Anna Chapman opened up her laptop, and when a certain Russian government official was nearby (in a van outside a coffeeshop or standing outside a bookstore), an ad-hoc wireless network with the same two MAC addresses sprung up.&lt;br /&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://1.bp.blogspot.com/_RaDk956KPXY/TCneQr2_38I/AAAAAAAAAJ8/Xl1tc5X_JuU/s1600/russianspy-2.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="231" src="http://1.bp.blogspot.com/_RaDk956KPXY/TCneQr2_38I/AAAAAAAAAJ8/Xl1tc5X_JuU/s400/russianspy-2.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;Semenko used the same technique. In one instance, he was sitting in a restaurant, while a car with diplomatic plates (issued to the Russian embassy) entered the parking lot and sat there for 20 minutes and then left.&lt;br /&gt;&lt;br /&gt;Further down, Semenko described to an undercover FBI agent posing as a Russian diplomat how he zipped up the files, opened up his laptop to set up the adhoc wifi and transferred the files.&lt;br /&gt;&lt;br /&gt;A number of questions and thoughts:&lt;br /&gt;- Because the FBI knew enough to pose to undercover agents as Russians and arrange meets with the spies, they had penetrated the ring for a very long time. Other documents mention search warrants against safe-deposit boxes as early as 2001.&lt;br /&gt;- Which brings up another question. Why did Russian agent and FBI counter-intelligence honcho &lt;a href="http://en.wikipedia.org/wiki/Robert_Hanssen" target="_blank"&gt;Robert Hanssen&lt;/a&gt;, not warn them? His position in the FBI should have guaranteed he knew about this.&lt;br /&gt;- Or did Hanssen, who was arrested in 2001, give them up?&lt;br /&gt;- But if Hanssen knew about this team, why didn't the Russians pull them out?&lt;br /&gt;- Anna Chapman must have smelled a rat, and that's why she bought a disposable phone (to call Russia?) and did not show up for the meeting the next day (June 27)&lt;br /&gt;- Which must have led to the arrests on the 28th because the FBI decided the spies were on to them.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-3445269606509250390?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/3445269606509250390/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=3445269606509250390' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/3445269606509250390'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/3445269606509250390'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2010/06/russian-spies-and-adhoc-wi-fi.html' title='Russian spies and adhoc wi-fi'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_RaDk956KPXY/TCndpgIgMsI/AAAAAAAAAJ0/uHJxlSlk2Q4/s72-c/russianspy-1.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-7943108124873855722</id><published>2010-05-06T20:04:00.000-07:00</published><updated>2010-05-06T20:06:00.597-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='virus'/><category scheme='http://www.blogger.com/atom/ns#' term='av'/><category scheme='http://www.blogger.com/atom/ns#' term='antivirus'/><title type='text'>What Virustotal says about a suspicious attachment and AV products</title><content type='html'>I received a $50 iTunes gift certificate today as a zip file. Yay!&lt;br /&gt;&lt;br /&gt;I uploaded it to Virustotal, and the result is below. If the formatting is lost, you can see the report here: http://shar.es/m6tDP&lt;br /&gt;&lt;br /&gt;First, Virustotal told me that they already have seen this file. Next, very few AVs identified it as a threat. And at the risk of beating up on McAfee again, their gateway version with a May 6 def identified it, but their regular (?) version with a May 7 def did not! In all, only 8 of 41 identified it.&lt;br /&gt;&lt;br /&gt;AVG, which is on my laptop, did not identify it either.&lt;br /&gt;&lt;br /&gt;My question: what happened to AV companies sharing knowledge? I would&lt;br /&gt;have thought in 24 hours at least all the big boys would have shared the&lt;br /&gt;signature. A 20% detection rate is pretty bad. But as McAfee's left hand&lt;br /&gt;does not know what its other left hand is doing, I guess I should not be&lt;br /&gt;too surprised.&lt;br /&gt;&lt;br /&gt;&lt;pre wrap=""&gt;&lt;/pre&gt;&lt;table border="0" cellpadding="0" cellspacing="0" id="tablaMotores" style="width: 550px;"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;Antivirus&lt;/th&gt; &lt;th&gt;Version&lt;/th&gt; &lt;th&gt;Last Update&lt;/th&gt; &lt;th&gt;Result&lt;/th&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;a-squared&lt;/td&gt; &lt;td&gt;4.5.0.50&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;AhnLab-V3&lt;/td&gt; &lt;td&gt;2010.05.07.00&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;AntiVir&lt;/td&gt; &lt;td&gt;8.2.1.236&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;Antiy-AVL&lt;/td&gt; &lt;td&gt;2.0.3.7&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Authentium&lt;/td&gt; &lt;td&gt;5.2.0.5&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;Avast&lt;/td&gt; &lt;td&gt;4.8.1351.0&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Avast5&lt;/td&gt; &lt;td&gt;5.0.332.0&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;AVG&lt;/td&gt; &lt;td&gt;9.0.0.787&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;BitDefender&lt;/td&gt; &lt;td&gt;7.2&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td class="positivo"&gt;Gen:Variant.Bredo.4&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;CAT-QuickHeal&lt;/td&gt; &lt;td&gt;10.00&lt;/td&gt; &lt;td&gt;2010.05.04&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;ClamAV&lt;/td&gt; &lt;td&gt;0.96.0.3-git&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;Comodo&lt;/td&gt; &lt;td&gt;4783&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;DrWeb&lt;/td&gt; &lt;td&gt;5.0.2.03300&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;eSafe&lt;/td&gt; &lt;td&gt;7.0.17.0&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;eTrust-Vet&lt;/td&gt; &lt;td&gt;35.2.7472&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;F-Prot&lt;/td&gt; &lt;td&gt;4.5.1.85&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;F-Secure&lt;/td&gt; &lt;td&gt;9.0.15370.0&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td class="positivo"&gt;Gen:Variant.Bredo.4&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;Fortinet&lt;/td&gt; &lt;td&gt;4.0.14.0&lt;/td&gt; &lt;td&gt;2010.05.05&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;GData&lt;/td&gt; &lt;td&gt;21&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td class="positivo"&gt;Gen:Variant.Bredo.4&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;Ikarus&lt;/td&gt; &lt;td&gt;T3.1.1.84.0&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Jiangmin&lt;/td&gt; &lt;td&gt;13.0.900&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;Kaspersky&lt;/td&gt; &lt;td&gt;7.0.0.125&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;McAfee&lt;/td&gt; &lt;td&gt;5.400.0.1158&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;McAfee-GW-Edition&lt;/td&gt; &lt;td&gt;2010.1&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td class="positivo"&gt;Artemis!ECB1C56D7D93&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Microsoft&lt;/td&gt; &lt;td&gt;1.5703&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;NOD32&lt;/td&gt; &lt;td&gt;5092&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Norman&lt;/td&gt; &lt;td&gt;6.04.12&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;nProtect&lt;/td&gt; &lt;td&gt;2010-05-06.02&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td class="positivo"&gt;Gen:Variant.Bredo.4&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Panda&lt;/td&gt; &lt;td&gt;10.0.2.7&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td class="positivo"&gt;Suspicious file&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;PCTools&lt;/td&gt; &lt;td&gt;7.0.3.5&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Prevx&lt;/td&gt; &lt;td&gt;3.0&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;Rising&lt;/td&gt; &lt;td&gt;22.46.03.04&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Sophos&lt;/td&gt; &lt;td&gt;4.53.0&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td class="positivo"&gt;Mal/FakeAV-BW&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;Sunbelt&lt;/td&gt; &lt;td&gt;6272&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;Symantec&lt;/td&gt; &lt;td&gt;20091.2.0.41&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;TheHacker&lt;/td&gt; &lt;td&gt;6.5.2.0.277&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;TrendMicro&lt;/td&gt; &lt;td&gt;9.120.0.1004&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td class="positivo"&gt;PAK_Generic.001&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;TrendMicro-HouseCall&lt;/td&gt; &lt;td&gt;9.120.0.1004&lt;/td&gt; &lt;td&gt;2010.05.07&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;VBA32&lt;/td&gt; &lt;td&gt;3.12.12.4&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr class="odd"&gt; &lt;td&gt;ViRobot&lt;/td&gt; &lt;td&gt;2010.5.6.2304&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt; &lt;/tr&gt;&lt;tr&gt; &lt;td&gt;VirusBuster&lt;/td&gt; &lt;td&gt;5.0.27.0&lt;/td&gt; &lt;td&gt;2010.05.06&lt;/td&gt; &lt;td&gt;-&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;pre wrap=""&gt;&lt;/pre&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-7943108124873855722?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/7943108124873855722/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=7943108124873855722' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7943108124873855722'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7943108124873855722'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2010/05/what-virustotal-says-about-suspicious.html' title='What Virustotal says about a suspicious attachment and AV products'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-7206694509484435640</id><published>2010-04-10T06:47:00.000-07:00</published><updated>2010-04-10T06:57:54.692-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='nigerian'/><category scheme='http://www.blogger.com/atom/ns#' term='scam'/><category scheme='http://www.blogger.com/atom/ns#' term='419'/><title type='text'>Cheapest 419 scam ever</title><content type='html'>&lt;span style="font-size: small;"&gt;Received this just now.&lt;/span&gt;&lt;span style="font-size: small;"&gt;Are they just giving up now? Or is it some sort of ultra-soft-sell?&lt;br /&gt;&lt;br /&gt;Also notice that they are not sure about my religious affiliation&lt;/span&gt; &lt;br /&gt;&lt;big style="padding: 10px;"&gt; &lt;/big&gt;&lt;br /&gt;&lt;big style="padding: 10px;"&gt;新しいメールアドレスをお知らせします&lt;/big&gt; &lt;br /&gt;&lt;div style="padding: 10px;"&gt;新しいメールアドレス： &lt;b&gt;sadiqaliman1@yahoo.co.jp&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="color: green;"&gt;Dearest one,&lt;br /&gt;&lt;br /&gt;I greet you in names of our almighty allah? however let me give you brief introduction myself, My name is Aliman Keita the only surviving daughter of Mr &amp;amp;Mrs Sadiq Keita, he deposited ($6.5) I will give more details concerning me and the transaction.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Miss Aliman.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;- &lt;span style="color: green;"&gt;Keita Sadiq Aliman&lt;/span&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-7206694509484435640?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/7206694509484435640/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=7206694509484435640' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7206694509484435640'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7206694509484435640'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2010/04/cheapest-419-scam-ever.html' title='Cheapest 419 scam ever'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-6362653436850666768</id><published>2010-01-30T11:42:00.000-08:00</published><updated>2010-01-30T12:01:27.386-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='fail'/><category scheme='http://www.blogger.com/atom/ns#' term='armarix'/><category scheme='http://www.blogger.com/atom/ns#' term='safe handgund'/><title type='text'>A "safe" handgun or a $9700 design fail waiting to happen?</title><content type='html'>Wired is &lt;a href="http://www.wired.com/dangerroom/2010/01/high-tech-guns-digital-revolvers-koosh-bullets-and-triple-tasers" target="_blank"&gt;reporting&lt;/a&gt; that Armatix introduced a Euro 7000 (US$ 9700) handgun that can only be fired if it is armed via a wristwatch worn by the shooter.&lt;br /&gt;&lt;blockquote&gt;This year, the highest-tech gun belonged to Armatix. The German firm has an electronic safety that automatically disables the pistol when it’s not within a few inches of a custom wristwatch. The watch sends a wireless arming signal to the gun. If the gun is picking up a signal from the watch, a green LED on the back lights up. Try squeezing the handle without wearing the watch, and you will see a red warning light. Anyone can pick up a limited edition version of the pistol for about 7,000 euro, which is pretty steep for a .22cal plinker. They start shipping next month.&lt;/blockquote&gt;&lt;br /&gt;Few inches, eh? Smells like RFID. Then we found this on Armatix's &lt;a href="http://www.armatix.com/Smart-System.38.0.html?&amp;amp;L=1" target="_blank"&gt;website&lt;/a&gt;: &lt;br /&gt;&lt;blockquote&gt;The benefits of biometrics (sole allocation to specific people) are also combined with those of Radio Frequency Identification ( split- Seconf activation, hands-free operation.&lt;/blockquote&gt;&lt;br /&gt;"Seconf" above should be "second", but that might be the least of their problems. My problem is, given the many, many security failures I have seen in basic authorization/authentication schemes, I anticipate a slew of them in this handgun. Here are some of them:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;It's not like RFID has been read or cloned. Oh wait!&lt;/li&gt;&lt;li&gt;RFID can be jammed. For that matter, any RF can be jammed.&lt;/li&gt;&lt;li&gt;Forget hightech.. throwing a bucket of water at the person holding the gun at you might work. I see a Rush Hour sequel where Chris Tucker almost gets Jackie Chan killed by spilling coffee on his wrist and rendering his gun into a paperweight.&lt;/li&gt;&lt;li&gt;The flip-side of jamming is arming. People have &lt;a href="http://www.engadget.com/2009/02/02/video-hacker-war-drives-san-francisco-cloning-rfid-passports/" target="_blank"&gt;read RFID passport numbers and cloned&lt;/a&gt; them. Then it is just a matter of playing that back, from a more powerful transmitter, and suddenly the "safe" gun will fire a bullet.&lt;/li&gt;&lt;li&gt;And then ofcourse, the same RFID scanners can be used to identify who is carrying those guns and wrist-watches.&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;One can only hope that this gun will be completely safe because there are no morons who will pay that kind of money for a .22&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-6362653436850666768?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/6362653436850666768/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=6362653436850666768' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/6362653436850666768'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/6362653436850666768'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2010/01/safe-handgun-or-9700-design-fail.html' title='A &quot;safe&quot; handgun or a $9700 design fail waiting to happen?'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-6008252074364969030</id><published>2010-01-28T07:32:00.000-08:00</published><updated>2010-01-28T07:32:35.693-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='joomla'/><category scheme='http://www.blogger.com/atom/ns#' term='house'/><category scheme='http://www.blogger.com/atom/ns#' term='defacement'/><category scheme='http://www.blogger.com/atom/ns#' term='Red Eye Crew'/><category scheme='http://www.blogger.com/atom/ns#' term='congress'/><category scheme='http://www.blogger.com/atom/ns#' term='hack'/><category scheme='http://www.blogger.com/atom/ns#' term='congressman'/><title type='text'>Multiple Congresspeople websites defaced</title><content type='html'>National Journal's Hotcall &lt;a href="http://hotlineoncall.nationaljournal.com/archives/2010/01/hackers_hit_hou.php" target="_blank"&gt;reported&lt;/a&gt; around 3:20 AM on Thursday, January 28 that various congress people's (both republican and democrat) websites were defaced.&lt;br /&gt;&lt;br /&gt;The message was crude and simple:&lt;br /&gt;&lt;blockquote&gt;"F--- OBAMA!! Red Eye CREW !!!!! O RESTO E HACKER!!! by HADES; m4V3RiCk; T4ph0d4 -- FROM BRASIL," the messages read.&lt;/blockquote&gt;&lt;br /&gt;&lt;a href="http://praetorianprefect.com/archives/2010/01/congressional-web-site-defacements-follow-the-state-of-the-union/" target="_blank"&gt;Praetorian Prefect&lt;/a&gt; has some screenshots and what seems to be a pretty complete list (perhaps compiled by going through the sites manually around 4 AM!)&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;http://www.joewilson.house.gov/&lt;br /&gt;http://bachus.house.gov/&lt;br /&gt;http://www.baird.house.gov/&lt;br /&gt;http://www.barrow.house.gov/&lt;br /&gt;http://www.gonzalez.house.gov/&lt;br /&gt;http://mcnerney.house.gov/&lt;br /&gt;http://mikepence.house.gov/&lt;br /&gt;http://driehaus.house.gov/&lt;br /&gt;http://carson.house.gov/&lt;br /&gt;http://campbell.house.gov/&lt;br /&gt;http://doggett.house.gov/&lt;br /&gt;http://coffman.house.gov/&lt;br /&gt;http://www.kosmas.house.gov/&lt;br /&gt;http://hersethsandlin.house.gov/&lt;br /&gt;http://lujan.house.gov/&lt;br /&gt;http://www.mccollum.house.gov/&lt;br /&gt;http://teague.house.gov/&lt;br /&gt;http://mitchell.house.gov/&lt;br /&gt;http://www.roe.house.gov/&lt;br /&gt;http://www.lofgren.house.gov/&lt;br /&gt;http://carnahan.house.gov/&lt;br /&gt;http://www.chrismurphy.house.gov/&lt;br /&gt;http://hunter.house.gov/&lt;br /&gt;http://olver.house.gov/&lt;br /&gt;http://arcuri.house.gov/&lt;br /&gt;http://olver.house.gov/&lt;br /&gt;http://tierney.house.gov/&lt;br /&gt;&lt;br /&gt;A few committee sites were affected as well:&lt;br /&gt;&lt;br /&gt;http://republicans.financialservices.house.gov/&lt;br /&gt;http://republicans.oversight.house.gov/&lt;br /&gt;http://gop.cha.house.gov/&lt;/blockquote&gt;&lt;br /&gt;Ironically, one of the first defacements discovered was on Congressman (R-SC) Joe Wilson's site, who (in)famously yelled "You Lie!" at Obama. Mr. Wilson gave one of the first live responses to Obama's SOTU speech.&lt;br /&gt;&lt;br /&gt;The websites are maintained by the House IT staff, and most of them run on identical systems and software. So it is not surprising that after the first site was found to be vulnerable, the attackers found a rich array of soft targets. &lt;br /&gt;&lt;br /&gt;As a result, the serial defacement does not surprise me--if anything, I am surprised they did not hack 500+ sites.&lt;br /&gt;&lt;br /&gt;Praetorian Prefect identified the Joomla CMS as the one common factor on all the defaced websites (but not all Congressional sites running Joomla were defaced)&lt;br /&gt;&lt;br /&gt;It seems a particular Joomla component or module was vulnerable and was exploited. I just hope the knee-jerk reaction to this is not to go back to some proprietary CMS.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-6008252074364969030?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/6008252074364969030/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=6008252074364969030' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/6008252074364969030'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/6008252074364969030'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2010/01/multiple-congresspeople-websites.html' title='Multiple Congresspeople websites defaced'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-8556194043348346463</id><published>2010-01-16T09:55:00.000-08:00</published><updated>2010-01-16T11:27:05.421-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='mobile'/><category scheme='http://www.blogger.com/atom/ns#' term='fail'/><category scheme='http://www.blogger.com/atom/ns#' term='facebook'/><category scheme='http://www.blogger.com/atom/ns#' term='ATT'/><title type='text'>How mobile phone users stumbled into other people's FaceBook account</title><content type='html'>AP is &lt;a href="http://www.boston.com/business/technology/articles/2010/01/15/ap_exclusive_network_flaw_causes_scary_web_error/" target="_blank"&gt;reporting&lt;/a&gt;: "Network flaw causes scary Web error":&lt;br /&gt;&lt;blockquote&gt;A Georgia mother and her two daughters logged onto Facebook from mobile phones last weekend and wound up in a startling place: strangers' accounts with full access to troves of private information.&lt;br /&gt;&lt;br /&gt;The glitch -- the result of a routing problem at the family's wireless carrier, AT&amp;T -- revealed a little known security flaw with far reaching implications for everyone on the Internet, not just Facebook users.&lt;/blockquote&gt;True. Most internet sites that do not use secure login (https) may be vulnerable until AT&amp;T fixes their problem. Boston Globe readers are reporting that they faced the same problem as far back in 2007, on carriers other than ATT Wireless.&lt;br /&gt;&lt;br /&gt;As an aside, I had to laugh after reading this line in the AP article:&lt;br /&gt;&lt;blockquote&gt;In each case, the Internet lost track of who was who, putting the women into the wrong accounts. &lt;/blockquote&gt;Reminds me of this AOL helpdesk gem: "This is not an AOL problem. Have&lt;br /&gt;you tried calling the Internet's support department?"&lt;br /&gt;&lt;br /&gt;To understand how this could have happened, lets take a look at how a website knows who is who once they log in. Of course, they could just have your username added to each page request. But then anyone who knew your username would be able to impersonate you. One popular mechanism is using session cookies. Here is a very simplified description:&lt;br /&gt;HTTP is stateless (meaning the web server has no memory of who you are or what you just did), so the server has no way of keeping track of the users who logged in (and tying them to a specific browser).&lt;br /&gt;&lt;br /&gt;Once a user logs in, a cookie is set with a lifetime (say, 15 minutes), and this cookie and matching userid is stored somewhere, preferably a database. It is typically a long and random string like xyn29f071bca9bf7f85da28205439fc3, so someone can not just guess it.&lt;br /&gt;&lt;br /&gt;Every time the user tries to go to a protected page, the server reads the cookie from the browser, looks up the username that matches the cookie, and allows (or disallows) access. The cookie is also updated with each request (lifetime extended by 15 minutes). If no request is made, the cookie expires, and user gets logged out for inactivity. If the user chooses to log out or in the previous case gets logged out due to idle timeout, his/her cookie is deleted on the server, so they can not access protected pages any more.&lt;br /&gt;&lt;br /&gt;So, if for some reason Alice gets Bob's cookie (before Bob logs out), the server will think Alice is Bob, look up pages that Bob has access to, and bada bing!--Alice will be looking at Bob's pages.&lt;br /&gt;&lt;br /&gt;Now the million dollar question is, how would Alice get access to Bob's Facebook session cookies? Stealing session-cookies is a &lt;a href="http://en.wikipedia.org/wiki/Session_hijacking" target="_blank"&gt;well-known attack&lt;/a&gt;; people have demonstrated this on multiple sites including &lt;a href="http://xs-sniper.com/blog/2008/04/14/google-xss/" target="_blank"&gt;Google Spreadsheets&lt;/a&gt;, and bad guys have used this to compromise accounts. But we can be pretty sure in this case the person who experienced this wasn't doing any such attack. So what happened?&lt;br /&gt;&lt;br /&gt;Here we enter the murky territory of speculation. We know that AT&amp;T is &lt;a href="http://www.nytimes.com/2009/12/10/technology/companies/10iphone.html" target="_blank"&gt;worried&lt;/a&gt; about the amount of data usage by it's wireless customers because their network can't keep up. So is it possible they used &lt;a href="http://www.mozilla.org/projects/netlib/http/pipelining-faq.html"&gt;HTTP pipelining&lt;/a&gt; to improve performance?&lt;br /&gt;&lt;blockquote&gt;Normally, HTTP requests are issued sequentially, with the next request being issued only after the response to the current request has been completely received. Depending on network latencies and bandwidth limitations, this can result in a significant delay before the next request is seen by the server.&lt;br /&gt;&lt;br /&gt;HTTP/1.1 allows multiple HTTP requests to be written out to a socket together without waiting for the corresponding responses. The requestor then waits for the responses to arrive in the order in which they were requested. The act of pipelining the requests can result in a dramatic improvement in page loading times, especially over high latency connections.&lt;/blockquote&gt;&lt;br /&gt;What I think happened was: ATT's web proxy uses pipelining. User A and User B where both trying to log onto Facebook at the same time. When the responses came back it messed up the order, and sent the response destined for User A to User B's browser, thus giving her access to User A's facebook page.&lt;br /&gt;&lt;br /&gt;PS: Where did the response meant for User B go? To user A? To yet another person who has not come forward yet? To User B's browser, which then discarded it because it thought it already got a response to its original request? To the bit-bucket? Who knows.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-8556194043348346463?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/8556194043348346463/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=8556194043348346463' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/8556194043348346463'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/8556194043348346463'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2010/01/how-mobile-phone-users-stubmbled-into.html' title='How mobile phone users stumbled into other people&apos;s FaceBook account'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-1828275500364638451</id><published>2010-01-11T18:18:00.000-08:00</published><updated>2010-01-11T18:18:57.667-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='CISO'/><category scheme='http://www.blogger.com/atom/ns#' term='google apps'/><title type='text'>Harsh: Google Security chief's night-job</title><content type='html'>Gawker has a &lt;a href="http://valleywag.gawker.com/5439749/google-security-chief-by-day-tv-magician-eran-raven-by-night" target="_blank"&gt;post&lt;/a&gt; about Google Apps' Director of Security Eran Feigenbaum, and his not so secret identity as Eran Raven, mentalist/magician.&lt;br /&gt;&lt;br /&gt;I had to laugh out loud after reading this:&lt;br /&gt;&lt;blockquote&gt;Maybe it should come as no surprise that Google's Director of Security is also a "mentalist" magician; few can better sell the illusion of ironclad internet security, after all, than a master of deception who fooled thousands of NBC viewers.&lt;br /&gt;&lt;br /&gt;But Eran Feigenbaum — better known as "Eran Raven" — has turned the cheese knob up awfully high, considering his buttoned-down job as the Director of Security for the putative blue-chip operation that is Google Enterprise, which is trying to sell "cloud computing" to no less uptight a customer than the federal government. &lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-1828275500364638451?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/1828275500364638451/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=1828275500364638451' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1828275500364638451'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1828275500364638451'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2010/01/harsh-google-security-chiefs-night-job.html' title='Harsh: Google Security chief&apos;s night-job'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-8982032090189799138</id><published>2010-01-05T08:03:00.000-08:00</published><updated>2010-01-06T09:29:34.496-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='kodak'/><category scheme='http://www.blogger.com/atom/ns#' term='insecure design'/><category scheme='http://www.blogger.com/atom/ns#' term='fail'/><category scheme='http://www.blogger.com/atom/ns#' term='privacy'/><title type='text'>We don't need no stinking security in our digital photo frames</title><content type='html'>&lt;span style="font-size: x-small;"&gt;&lt;b&gt;Update (Jan 6, 2010): &lt;/b&gt;Looks like FrameChannel is doing something to block access to known URLs. It could be something as simple as user-agent checking, but at least it is a start.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;2010's first security vulnerability (that I know of) is a doozy. But before getting into that, lets take a peek into the design meeting that resulted in it.&lt;br /&gt;&lt;br /&gt;Person 1: Lets see.. how would each customer identify the product for activation?&lt;br /&gt;Person 2: We will stick a random code on each package&lt;br /&gt;Big boss: No, that is too much work&lt;br /&gt;Person 3: You know, each device already has an unique identifier. This MAC address...&lt;br /&gt;Person 2: Shouldn't it be random? Should we talk to the security guys? &lt;br /&gt;Big Boss: Awesome. Why would a photo frame need security? This MAC thingy sure looks very unfriendly, so lets label it as a user-convenience feature. While you guys do that, I will go tell my boss I came up with the idea.&lt;br /&gt;&lt;br /&gt;This not-so-unlikely scenario is brought to you courtesy of an &lt;a href="http://seattlewireless.net/%7Ecasey/?p=13" target="_blank"&gt;excellent blog post&lt;/a&gt; by Casey Halverson, owner of two W820 Kodak digital picture frames.&lt;br /&gt;&lt;br /&gt;Knowing that the frames can display pretty much any RSS feed, Mr. Halvereson discovered that the configuration screen shows a URL for the RSS feed that ends in what looks suspiciously like a MAC address, because, you guessed it--it IS a MAC address. (The link below is not clickable by choice--we don't know what will be there if you visit it)&lt;br /&gt;&lt;blockquote&gt;&lt;div style="color: purple;"&gt;http://rss.framechannel.com//productId=KD9371/frameId=00:23:4D:B8:07:6D&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;Look, its an RSS feed of what my picture frame is showing now! I can send this nice URL to everyone I know so they can look at all my private content I have configured for this device. Now, under no circumstances would I recommend changing the last digits of this MAC address frame ID to another number….because you would get someone else’s picture frame content. Why would you want to do that?&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;If you don't know how MAC addresses are assigned and numbered, here is a quick introduction. The first 6 hexadecimal digits (in this case, 00:23:4D) designate the manufacturer of the network card, and the remaining 6 hexadecimal digits identify a serial number assigned by the manufacturer.&lt;br /&gt;&lt;br /&gt;So if you are looking at a Kodak photoframe, who does not make network chips, it is a pretty safe bet that they buy the chip from someone else (or their outsourced manufacturer does, but same effect). It is also a near certainty that because of economies of scale, these chips will be bought from the same company. What I am leading up to is, this means virtually ALL Kodak wireless frames will have the same first 6 digits, making the remaining address-space any number from 00:00:00 to FF:FF:FF -- a total of slightly over 16 million possible numbers: trivial for a computer to generate and check. 00:23:4D:B8:07:6D is &lt;a href="http://www.curreedy.com/stu/nic/" target="_blank"&gt;manufactured by&lt;/a&gt; Hon Hai Precision Ind. Co., Ltd. Obviously, all their cards will not be used on the Kodak frames. But now that we know the name of the manufacturer, a bad guy can go and find other prefixes assigned to them, and expand the search.&lt;br /&gt;&lt;br /&gt;The frames, by the way, can not pull down RSS feeds on their own. The feeds need to be managed through a company called FrameChannel, which, as the name indicates, is in the business of creating channels for picture frames. They very conveniently list a number of &lt;a href="http://www.wirelesspictureframe.com/company-listing/" target="_blank"&gt;frame manufacturers they support&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Could they all be vulnerable to the same attack?&lt;br /&gt;&lt;br /&gt;They also are saying that Woot sold 100,000 Kodak frames on Dec 20, the first day they went on the market. Given the other manufacturers, the problem-size could be more than a million vulnerable frames out there.&lt;br /&gt;&lt;br /&gt;In their FAQ, they answered (as of this writing; I expect this to change soon):&lt;br /&gt;&lt;blockquote&gt;&lt;b&gt;Who can see the pictures in my account?&lt;br /&gt;&lt;/b&gt;&lt;br /&gt;Unless you add pictures to a public or group channel, or share them with your invited friends, you are the only one who will see images in your account. &lt;b&gt;No other FrameChannel user will ever see images you upload or add to your account unless specifically approved by you&lt;/b&gt; (such as in the case of a public user generated or group channel, or as a contributor to your friends' accounts). (emphasis mine)&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;Aw.&lt;br /&gt;&lt;br /&gt;Someone could point all the unsold/unactivated frames to pornography, or other objectionable or even illegal content like child pornography. So if you have one of these frames, what should you do? Don't feel safe because you only have nature photos. If you have the Weather channel configured, a remote viewer may be able to figure out your city and state. If your userid contains your name in some form, they may be able to narrow it down much further.&lt;br /&gt;&lt;br /&gt;In the configuration screen, there is a URL parameter called reset=0. Any guesses as to what reset=1 will do? Yes, it gives a new activation code, and I presume it deactivates the old code. Seems like this can be used to kill feeds to a frame.&lt;br /&gt;&lt;br /&gt;The next one is a bit more serious. One report says they saw something like:&lt;br /&gt;&lt;blockquote&gt;“This frame has been preactivated” and gave the username and password and invited the user to login to framechannel.com to upload their own content.&lt;br /&gt;&lt;/blockquote&gt;&amp;nbsp;As long as you treat this frame as something viewable by the whole world, then you are fine.&lt;br /&gt;&lt;br /&gt;Should you return the product? Your choice. But if you want to keep it, definitely contact the manufacturer and FrameChannel, and ask them to fix this issue.&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Postscript:&lt;/i&gt; The bad guys can point these frames to a photostream of their choice before they are activated by the actual owner. Equally easily, the good guys can load up an image containing an warning about this risk to these frames, but they will not, because that will mean breaking more than one law. So if you know anyone with one of these frames, also tell them about this.&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Rant:&lt;/i&gt;I don't understand why the manufacturers decided to go with a 3rd party which may go out of business (a distinct possibility given this mess) instead of just allowing any random RSS feed. It is not like this 3rd party is hosting my images or creating the RSS feed any way. So why shouldn't consumers be able to use a RSS feed directly?&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Update: &lt;/i&gt;David Stafford asked below if an already activated and used frame can be compromised. The answer is, I think so, although I have not personally tested it yet.&lt;br /&gt;The known/confirmed risks are: &lt;br /&gt;- Someone may be able to view private images- Someone may be able to glean private information from the images or other channels being displayed&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Unconfirmed: &lt;/b&gt;The major risk (remote image upload) might be possible because FrameChannel lets people who knows/guesses the frameid (the MAC address) to reset the frame. The aforementioned reset=0, when changed to reset=1, will do this. I am not posting the actual URL, but it is by now widely available on the Net.&lt;br /&gt;&lt;br /&gt;After a frame activation is reset and re-activated, I believe at least on the Kodak model it can be done.(waiting for confirmation)&lt;br /&gt;&lt;br /&gt;For users on unencrypted (or 40-bit WEP encrypted) WiFi, an attacker who is within the WiFi range will be able to capture the PIN, but that is true about any wireless technology and not particular to this issue&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-8982032090189799138?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/8982032090189799138/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=8982032090189799138' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/8982032090189799138'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/8982032090189799138'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2010/01/we-dont-need-no-stinking-security-in.html' title='We don&apos;t need no stinking security in our digital photo frames'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-6019111594398043064</id><published>2009-11-28T09:42:00.000-08:00</published><updated>2009-11-30T19:40:25.410-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='inexpensive'/><category scheme='http://www.blogger.com/atom/ns#' term='security program'/><category scheme='http://www.blogger.com/atom/ns#' term='nhlogin'/><category scheme='http://www.blogger.com/atom/ns#' term='ISMS'/><title type='text'>Common-sense security at $0</title><content type='html'>Craig and I were privileged to be invited by the fine folks at &lt;a href="http://www.nhlogin.org/" target="_blank"&gt;New Hampshire Local Government Information Network (NHLoGIN)&lt;/a&gt; to speak at New Hampshire Local Government Center's Annual Conference on Nov 19. &lt;br /&gt;&lt;br /&gt;Special thanks to John Barker of the City of Nashua for recommending us to NHLoGIN. John made a great presentation on accepting credit cards for City Hall business.&lt;br /&gt;&lt;br /&gt;We talked about things a non-profit, or a town or city hall can do with a very meager or non-existent information security budget. The first recommendation was policy, followed by training, and then slowly clibming the maturity curve.&lt;br /&gt;&lt;br /&gt;Because you are getting this without us speaking, we feel it is necessary to add a disclaimer: Of course, just because something does not need money to buy does not mean it falls ready-made on your desk some day--it takes time to develop policies, or to deliver (and attend) even free training. &lt;br /&gt;&lt;br /&gt;Check out the presentation: &lt;a href="http://zsquad.com/download/CommonsenseSecurity.pdf" target="_blanks"&gt;Budgeting for Common-Sense Computer Security in Financially Tight Times&lt;/a&gt;, and don't forget to use some of the great videos we linked.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-6019111594398043064?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/6019111594398043064/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=6019111594398043064' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/6019111594398043064'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/6019111594398043064'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/11/common-sense-security-at-0.html' title='Common-sense security at $0'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-233660124426339433</id><published>2009-11-05T05:57:00.000-08:00</published><updated>2009-11-05T06:13:19.830-08:00</updated><title type='text'>Vista Comment</title><content type='html'>From &lt;a href="http://twitter.com/rslade" target="_blank"&gt;Rob Slade&lt;/a&gt;, CISSP:&lt;br /&gt;&lt;blockquote&gt;If you play the Windows Vista installation CD backwards, you hear, and may be affected by, Satanic messages.&lt;br /&gt;&lt;br /&gt;This is, of course, preferable to playing it forwards.&lt;br /&gt;&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-233660124426339433?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/233660124426339433/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=233660124426339433' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/233660124426339433'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/233660124426339433'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/11/vista-comment.html' title='Vista Comment'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-1778011817739692206</id><published>2009-10-27T06:35:00.000-07:00</published><updated>2009-10-27T15:57:52.949-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='DOS'/><title type='text'>How to prepare for Denial of Service attacks against E-commerce sites</title><content type='html'>&lt;i&gt;[This is from a response I sent to someone on a mailing list earlier today]&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;The first thing you should know: unless you are Google or Amazon or some entity of that size and have money to burn, you really should not rely 100% on an on-premise solution against DOS attacks; let your bandwidth or hosting providers be the first defense against it.&lt;br /&gt;&lt;br /&gt;You can (and should) have your own solution, but without the protection beginning before your perimeter, the attack will block users from ever reaching you and thus become a successful attack.&lt;br /&gt;&lt;br /&gt;Here is why:&lt;br /&gt;The general principle of a DOS attack against an e-commerce site is to send a flood of HTTP requests. Most other types of DOS attack against some known problems with various TCP stacks have been fixed a while ago (or can be handled by various on-premise solutions)&lt;br /&gt;&lt;br /&gt;TopLayer, Tipping Point, Arbor or SourceFire (and others) makes excellent intrusion prevention systems (IPS) that can block vanilla DOS attacks launched by 1 or 10 computers. But they are not effective against distributed denial of service attacks that go after your bandwidth.&lt;br /&gt;&lt;br /&gt;If 20,000 computers hit your website at the same time, your bandwidth is going to be saturated (unless you have a grow-on-demand pipe).&lt;br /&gt;&lt;br /&gt;For example, I just measured the front page for Amazon.com. Images, stylesheet and everything else combines for about 77.6 KB. Let's say (for this argument's sake) that Amazon's bandwidth is 100 MBps. So that pipe can serve roughly 13,195 page requests per second for that 77.6K page before becoming 100% saturated (100 x 1024 kbps / 77.6 kb/page). I am not even counting the webserver's CPU/Memory utilization, since that is inside the perimeter.&lt;br /&gt;&lt;br /&gt;It won't matter what IPS they have on-premise; if the pipe is full, legitimate requests are going to be denied or delayed, resulting in a successful Denial of Service attack. This is &lt;a href="http://news.cnet.com/Leading-Web-sites-under-attack/2100-1017_3-236683.html" target="_blank"&gt;exactly what happened&lt;/a&gt; to Amazon, Yahoo, E-Trade, CNN and some others in Feb 2000.&lt;br /&gt;&lt;br /&gt;The bad guys do have thousands of machines with spyware installed at their disposal for this. Some groups reportedly have millions. It is a fact that they &lt;a href="http://blog.damballa.com/?p=330" target="_blank"&gt;rent them out by the hour in blocks of hundreds or thousands&lt;/a&gt; for as little as $200 for 10,000 bots. They are mostly used to send out spam, but it is just as easy to launch a Distributed DOS attack.&lt;br /&gt;&lt;br /&gt;So a belts and suspenders approach would be:&lt;br /&gt;- Have a good IPS--you need that any way&lt;br /&gt;- If using Linux servers, look at Netfilter so you can tar-pit the attacks&lt;br /&gt;- If you are in a co-lo, talk to your bandwidth providers (you should have more than 1) about DDOS protection.&lt;br /&gt;- If you are on a hosted server, pick a vendor like &lt;a href="http://www.rackspace.com/solutions/managed_hosting/services/security/preventier.php" target="_blank"&gt;RackSpace&lt;/a&gt; that provides DoS Mitigation.&lt;br /&gt;&lt;br /&gt;I know Cable &amp;amp; Wireless, ATT and Verizon all offer DDOS mitigation. They route away the bad packets away from you, and even the RBN does not have enough bots to saturate those bandwidths.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-1778011817739692206?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/1778011817739692206/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=1778011817739692206' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1778011817739692206'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1778011817739692206'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/10/how-to-prepare-for-denial-of-service.html' title='How to prepare for Denial of Service attacks against E-commerce sites'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-2596320828947034550</id><published>2009-10-13T17:09:00.000-07:00</published><updated>2009-10-13T17:13:04.187-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='fail'/><category scheme='http://www.blogger.com/atom/ns#' term='breach'/><category scheme='http://www.blogger.com/atom/ns#' term='wal-mart'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI'/><title type='text'>Wal-Mart breach in 2005-6: a lesson on things not to do</title><content type='html'>In 2006, a group of hackers targeted some Wal-Mart developers and stole source code to the Point-of-Sale (POS) system. Wired is &lt;a href="http://www.wired.com/threatlevel/2009/10/walmart-hack/" target="_blank"&gt;reporting&lt;/a&gt; that the stolen source code ended up being sent to a server in Minsk, Belarus, in the former Soviet Union.&lt;br /&gt;&lt;blockquote&gt;The Wal-Mart intrusion began unraveling on Nov. 5, 2006, when the company’s IT security group was brought in to investigate the server crash.&lt;br /&gt;&lt;br /&gt;Wal-Mart has thousands of servers nationwide, and any one of them crashing would ordinarily be a routine event. But this one raised a red flag. Someone had installed L0phtcrack, a password-cracking tool, onto the system, which crashed the server when the intruder tried to launch the program.&lt;br /&gt;&lt;br /&gt;Investigators found that the tool had been installed remotely by someone using a generic network administrator account. The intruder had reached the machine through a VPN account assigned to a former Wal-Mart worker in Canada, which administrators had failed to close after the worker left the company. The day the server crashed, the intruder had been connected to Wal-Mart’s network for about seven hours, originating from an IP address in Minsk, the documents show.&lt;br /&gt;&lt;br /&gt;The security team disabled the compromised VPN account, but the intruder, who should have realized the jig was up, came back in through another account belonging to a different Canadian employee. When that VPN account was closed, the intruder grabbed yet a third account while Wal-Mart workers were still scrambling to get a fix on the scope of the breach.&lt;br /&gt;&lt;br /&gt;When Wal-Mart reviewed its VPN logs, it found that the activity had begun at least as early as June 2005, according to memos written by Wal-Mart employees during the initial stage of the investigation. The company’s server logs recorded only unsuccessful log-in attempts, not successful ones, frustrating a detailed analysis.&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;Wired is also reporting that Wal-Mart had 4 years worth of unencrypted customer and credit card data at the time, but it was not breached. So they did not have to disclose it until now.&lt;br /&gt;&lt;blockquote&gt;Wal-Mart had a number of security vulnerabilities at the time of the attack, according to internal security assessments seen by Wired.com, and acknowledged as genuine by Wal-Mart. For example, at least four years’ worth of customer purchasing data, including names, card numbers and expiration dates, were housed on company networks in unencrypted form. Wal-Mart says it was in the process of dramatically improving the security of its transaction data, and in 2006 began encrypting the credit card numbers and other customer information, and making other important security changes.&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;Wal-Mart's external IT/PCI auditor, CyberTrust, found some astonishing breach of common-sense security (this blog abhors the term "Security Best Practices"):&lt;br /&gt;&lt;blockquote&gt;The assessment lasted six days, during which CyberTrust found numerous problems. Each of the five stores, for example, &lt;b&gt;housed complete backup copies of transaction logs on network-connected UNIX servers, which included at least four years’ worth of unencrypted credit card numbers, cardholder names and expiration dates&lt;/b&gt; from purchases at the stores.&lt;br /&gt;&lt;br /&gt;The auditors also discovered that servers, transaction processing systems, and other network-connected devices handling sensitive information &lt;b&gt;used the same usernames and passwords across every Wal-Mart store nationwide&lt;/b&gt;. In some cases, the passwords could be easily guessed. A hacker or malicious insider who compromised a point-of-sale controller or in-store card processor at one store, could “access the same device at every Wal-Mart store nationwide,” CyberTrust wrote.&lt;/blockquote&gt;&lt;br /&gt;And ofcourse, the intrusion could be traced back to the VPN account of a system administrator who had left the company but his account was not shut down (the report does not implicate the employee)&lt;br /&gt;&lt;br /&gt;Wal-Mart now claims that they have identified every single finding and are now PCI compliant. Fat lot of good being PCI-compliant did Hannaford.&lt;br /&gt;&lt;br /&gt;These companies either forget, or do not understand (we suspect over strenuous objection of their security people) that being PCI complaint is only the lowest common denominator--they can, and should, do much more.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-2596320828947034550?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/2596320828947034550/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=2596320828947034550' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2596320828947034550'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2596320828947034550'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/10/wal-mart-breach-in-2005-6-lesson-on.html' title='Wal-Mart breach in 2005-6: a lesson on things not to do'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-3384655865465042654</id><published>2009-10-08T06:16:00.000-07:00</published><updated>2009-10-08T06:17:11.026-07:00</updated><title type='text'>The Thursday Maxim of Security</title><content type='html'>A gem from &lt;a href="http://www.ne.anl.gov/capabilities/vat/seals/maxims.html" target="_blank"&gt;Dr. Roger Johnston&lt;/a&gt; at Argonne National Lab.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Thursday Maxim:&lt;/b&gt; Organizations and security managers will tend to automatically invoke irrational or fanciful reasons for claiming that they are immune to any postulated or demonstrated attack.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Comments:&lt;/b&gt; So named because if the attack or vulnerability was demonstrated on a Tuesday, it won’t be viewed as applicable on Thursday. Our favorite example of this maxim is when we made a video showing how to use GPS spoofing to hijack a truck that uses GPS tracking. In that video, the GPS antenna was shown attached to the side of the truck so that it could be easily seen on the video. After viewing the video, one security manager said it was all very interesting, but not relevant for their operations because their trucks had the antenna on the roof.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-3384655865465042654?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/3384655865465042654/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=3384655865465042654' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/3384655865465042654'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/3384655865465042654'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/10/thursday-maxim-of-security.html' title='The Thursday Maxim of Security'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-2599394528280232561</id><published>2009-10-07T18:32:00.000-07:00</published><updated>2009-10-07T18:32:06.961-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Kineavy'/><category scheme='http://www.blogger.com/atom/ns#' term='city hall'/><category scheme='http://www.blogger.com/atom/ns#' term='menino'/><category scheme='http://www.blogger.com/atom/ns#' term='Boston'/><title type='text'>Ignore email archiving / public record laws at your own peril</title><content type='html'>The saga of the deleted emails continues, with now the AG &lt;a href="http://www.boston.com/news/local/breaking_news/2009/10/ags_office_says.html" target="_blank"&gt;getting involved&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Prior to that, the Secretary of State stated that he was unhappy with the City Hall's continued failure to comply:&lt;br /&gt;&lt;blockquote&gt;Galvin expressed frustration Tuesday over what he described as the city's failure to fully cooperate with investigators. He told the Globe he was considering taking further action against the Menino administration. Under state law, he could turn the case over to Coakley for possible prosecution.&lt;/blockquote&gt;&lt;br /&gt;Now state Attorney General Martha Coakley (who is running for Ted Kennedy's senate seat BTW) states that she is "involved."&lt;br /&gt;&lt;blockquote&gt;Coakley said in a statement issued this afternoon that Secretary of State William F. Galvin's office has been working to ensure that public records are preserved and "to determine whether there have been any violations of the public records law by City officials."&lt;br /&gt;&lt;br /&gt;"We are now involved in that review," Coakley said.&lt;br /&gt;&lt;br /&gt;She said her office would continue to work with Galvin's office going forward in the effort to find mayoral aide Michael Kineavy's e-mails and "we remain prepared to conduct a full investigation and take all necessary steps to guarantee the preservation of evidence and full compliance with the law."&lt;/blockquote&gt;&lt;br /&gt;Apart from jokes about the Chicken being 'involved' and the Pig being 'committed' in the making of Ham and Eggs, what does that word mean, anyway?&lt;br /&gt;&lt;br /&gt;I personally know that there are Encase-certified digital forensics experts working for Coakley's office. Since City Hall is 'cooperating', it would be trivial to have the AGs office take a look at the hard disk instead of paying an outside consultant, right?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-2599394528280232561?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/2599394528280232561/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=2599394528280232561' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2599394528280232561'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2599394528280232561'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/10/ignore-email-archiving-public-record.html' title='Ignore email archiving / public record laws at your own peril'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-5706651600555108719</id><published>2009-10-07T17:04:00.000-07:00</published><updated>2009-10-07T17:04:14.390-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cloud'/><category scheme='http://www.blogger.com/atom/ns#' term='amazon'/><category scheme='http://www.blogger.com/atom/ns#' term='EC2'/><title type='text'>Marketing, Uncertainty and Doubt: Information Security and Cloud Computing</title><content type='html'>&lt;span&gt;&lt;span style="font-family: Verdana;"&gt; What is the minimum security due diligence that a company needs to do before putting it's data in the cloud?&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;&lt;br /&gt;Since 2007, Amazon has been telling us they are ".. working with a public accounting firm to ... attain certifications such as SAS70 Type II"&amp;nbsp; but these have not happened in 2+ years.&lt;br /&gt;&lt;br /&gt;On one side of the cloud security issue we have the marketing people, who hype up the existing security and gloss over the non-existing. On the other side we have security services vendors, who hawk their wares by hyping up the lack of security. And there are also Chicken Littles who are running around crying that the sky is falling.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;The truth is, there is a class of data for every cloud out there, and there is also someone who will suffer a data breach because they did not secure it properly.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;Can you put the New York Times on a cloud server? Of course, provided certain basic security measures are taken. After all, the Times is designed to be accessible to people (forget the stupid PayWall experiment they tried a few years ago)&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;On the other hand, you should not leave your customer's credit card data on Amazon EC2--they specifically suggest you don't do that.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;Another problem is, people are still not sure what "cloud" is. I saw a cartoon recently: "I fell down the stairs and something white is sticking out of my arms, and it hurts like hell. Is it swine flu?"&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;Most cloud security questions feel like that to me, so I have been accused of ranting in a presentation I did in September. Enjoy.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;span style="font-family: Verdana;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;div style="width:425px;text-align:left" id="__ss_2159543"&gt;&lt;a style="font:14px Helvetica,Arial,Sans-serif;display:block;margin:12px 0 3px 0;text-decoration:underline;" href="http://www.slideshare.net/jikbal/marketing-uncertainty-and-doubt-information-security-and-cloud-computing" title="Marketing, Uncertainty and Doubt: Information Security and Cloud Computing"&gt;Marketing, Uncertainty and Doubt: Information Security and Cloud Computing&lt;/a&gt;&lt;object style="margin:0px" width="425" height="355"&gt;&lt;param name="movie" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=boston-cloud-security-091007185635-phpapp01&amp;stripped_title=marketing-uncertainty-and-doubt-information-security-and-cloud-computing" /&gt;&lt;param name="allowFullScreen" value="true"/&gt;&lt;param name="allowScriptAccess" value="always"/&gt;&lt;embed src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=boston-cloud-security-091007185635-phpapp01&amp;stripped_title=marketing-uncertainty-and-doubt-information-security-and-cloud-computing" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;div style="font-size:11px;font-family:tahoma,arial;height:26px;padding-top:2px;"&gt;View more &lt;a style="text-decoration:underline;" href="http://www.slideshare.net/"&gt;documents&lt;/a&gt; from &lt;a style="text-decoration:underline;" href="http://www.slideshare.net/jikbal"&gt;jikbal&lt;/a&gt;.&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-5706651600555108719?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/5706651600555108719/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=5706651600555108719' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/5706651600555108719'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/5706651600555108719'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/10/marketing-uncertainty-and-doubt.html' title='Marketing, Uncertainty and Doubt: Information Security and Cloud Computing'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-7734482216437997753</id><published>2009-10-06T08:27:00.000-07:00</published><updated>2009-10-06T08:33:50.155-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Kineavy'/><category scheme='http://www.blogger.com/atom/ns#' term='discovery'/><category scheme='http://www.blogger.com/atom/ns#' term='city hall'/><category scheme='http://www.blogger.com/atom/ns#' term='Boston'/><title type='text'>Tangled web woven at Boston City Hall</title><content type='html'>The saga continues at Boston City Hall. Readers of this blog will remember that in response to public record requests, it came out that the Boston Mayor's right-hand man was &lt;a href="http://10domains.blogspot.com/2009/09/records-retention-in-local-government.html"&gt;deleting emails&lt;/a&gt; in a way that they were not getting backed up. So the Secretary of State got involved and ordered the City Hall to change the practice and also to retrieve the emails.&lt;br /&gt;&lt;br /&gt;Today it came out that our international man of mystery actually complained in April 2009 that his computer was running too slow and as a result, &lt;a href="http://www.boston.com/news/local/massachusetts/articles/2009/10/06/boston_mayoral_aide_had_computer_replaced_after_newspapers_e_mail_request/" target="_blank"&gt;received a new computer&lt;/a&gt;. But gosh darn, he plum forgot! And he still does not remember getting a new computer.&lt;br /&gt;&lt;blockquote&gt;City corporation counsel William F. Sinnott said in an interview yesterday that he had been relying on what Kineavy had told him and that Kineavy, the mayor’s chief policy aide and key political strategist, still does not remember getting a new computer.&lt;br /&gt;&lt;/blockquote&gt;Fortunately for people who like sunshine on their government affairs, and possibly unfortunately for Mr. Kineavy, that computer's hard disk was not wiped clean and reissued to another user--it was just sitting in another room. Now it has gone to the forensics firm hired by the City, and presumably the emails (or their remnants from temp files) will be recovered.&lt;br /&gt;&lt;br /&gt;Ironically, I bet that this particular PC was not recycled because the user was a powerful man, and IT suspected/feared that he will ask for some old file from the hard disk that was not accurately transferred to the new PC.&lt;br /&gt;&lt;br /&gt;Now to the cost of recovery. The most well-known commercial software used for digital forensics, Encase (there are others), will suck out anything relevant form that disk in a few hours and nicely categorize them in emails, word documents, etc.&lt;br /&gt;&lt;br /&gt;One might even call the work technologically trivial. If StoneTurn group is really asking for 250K for a single hard disk examination, they are either smoking weed, or abusing a single-source, no-bid contract. I know many highly reputable forensics consultants who will do this for under $10,000, probably for as low as $5,000.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;There are some good lessons here.&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Mr. Kineavy is every information security officer's dream. That man knows how to protect against information leakage&lt;/li&gt;&lt;li&gt;Mr. Kineavy is every compliance officer's nightmare. That man is costing the City Hall time, money and prestige&lt;/li&gt;&lt;li&gt;Not having a good decommissioning policy is hurting Mr. Kiveavy but may help make the City Hall become compliant with the public records law (or at least get away with a slap on the wrist and the hundreds of thousands of dollars in forensics expense)&lt;/li&gt;&lt;/ul&gt;Bottom line: the wheels of justice grinds slowly, but once caught in its maw, there is often no escape&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-7734482216437997753?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/7734482216437997753/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=7734482216437997753' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7734482216437997753'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7734482216437997753'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/10/tangled-web-woven-at-boston-city-hall.html' title='Tangled web woven at Boston City Hall'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-3213206568391732875</id><published>2009-09-26T21:22:00.000-07:00</published><updated>2009-09-26T21:26:30.592-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='RMB'/><category scheme='http://www.blogger.com/atom/ns#' term='google'/><category scheme='http://www.blogger.com/atom/ns#' term='Rocky Mountain Bank'/><title type='text'>Bank invents silver bullet to delete personal records from Google's evil grasp</title><content type='html'>Serendipity. There is no other word to describe Rocky Mountain Bank's latest discovery. But before explaining this modern miracle, let me ask you if you are worried about Google's pervasive presence and how much they know about you?&lt;br /&gt;&lt;br /&gt;Are you worried about Google Street View knowing where you live? Are you worried about Google combing through your Gmail account and sending you ads? Are you worried about the Biggest Brother (TM) technology patented by Google that lets them track your every search you perform on Google.com?&lt;br /&gt;&lt;br /&gt;Then fear not! Rocky Mountain Bank (RMB) just struck a blow for freedom-loving people everywhere. And the sheer simplicity of it is pure genius. Of course, they were aided by an idiot judge, but every discovery has one such sidekick. &lt;br /&gt;&lt;br /&gt;Lets go to the &lt;a href="http://www.mediapost.com/publications/?fa=Articles.showArticle&amp;amp;art_aid=114264" target="_blank"&gt;report&lt;/a&gt;:&lt;br /&gt;&lt;blockquote&gt;On Aug. 12, the bank mistakenly sent names, addresses, social security numbers and loan information of more than 1,300 customers to a Gmail address. When the bank realized the problem, it sent a message to that same address asking the recipient to contact the bank and destroy the file without opening it. No one responded, so the bank contacted Google to ask for information about the account holder. &lt;br /&gt;&lt;br /&gt;In keeping with its privacy policy, Google told the bank it would have to get a court order to obtain such data. The bank then filed papers asking a court to order Google to disclose the information and deactivate the account. &lt;br /&gt;&lt;br /&gt;The bank attempted to file its papers under seal, but U.S. District Court Judge Ronald Whyte denied that request. Earlier this week, the case was transferred to Ware from Whyte.&lt;br /&gt;&lt;br /&gt;Some lawyers say the Ware's order is problematic because it affects the Gmail account holder's First Amendment rights to communicate online, as well as his or her privacy rights. &lt;br /&gt;&lt;br /&gt;"It's outrageous that the bank asked for this, and it's outrageous that the court granted it," says John Morris, general counsel at the Center for Democracy &amp;amp; Technology. "What right does the bank have and go suspend the email account of a completely innocent person?"&lt;br /&gt;&lt;br /&gt;He adds: "At the end of the day, the bank obviously screwed up. But it should not be bringing a lawsuit against two completely innocent parties and disrupting one of the innocent party's email contact to the world." &lt;br /&gt;&lt;br /&gt;&lt;/blockquote&gt;Oh no Mr. Morris--you could not be more wrong. Don't you see RMB actually found the silver bullet to slay the behemoth that is Google? One by one, they will send emails to Gmail users. Then they will file lawsuits to shut down those accounts. Google will be forced to disclose the name of the account holder. Given the lack of privacy, very soon, people will stop using Gmail. Google's resources will be spent on lawyers. And Rockey Mountain Bank would emerge victorious, having finally crushed Google.&lt;br /&gt;&lt;br /&gt;Idiots&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-3213206568391732875?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/3213206568391732875/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=3213206568391732875' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/3213206568391732875'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/3213206568391732875'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/09/bank-invents-silver-bullet-to-delete.html' title='Bank invents silver bullet to delete personal records from Google&apos;s evil grasp'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-166037158311841873</id><published>2009-09-19T04:32:00.000-07:00</published><updated>2009-09-19T04:32:04.520-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='malware'/><category scheme='http://www.blogger.com/atom/ns#' term='swayze'/><title type='text'>Swayze-baited Malware</title><content type='html'>Google searchers for news on Patrick Swayze's funeral may come across links that are loaded with malware.&lt;br /&gt;&lt;br /&gt;Watch where you are going and what you are clicking on. &lt;a href="http://www.securityfocus.com/blogs/2297" target="_blank"&gt;More&lt;/a&gt; from SecurityFocus/F-Secure.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-166037158311841873?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/166037158311841873/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=166037158311841873' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/166037158311841873'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/166037158311841873'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/09/swayze-baited-malware.html' title='Swayze-baited Malware'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-4527323547314441703</id><published>2009-09-18T18:00:00.000-07:00</published><updated>2009-09-18T18:00:31.336-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='HIPAA'/><category scheme='http://www.blogger.com/atom/ns#' term='ohio'/><category scheme='http://www.blogger.com/atom/ns#' term='breach'/><title type='text'>Fool me once...</title><content type='html'>Hmm.. looks like this is not the first brush of data breach at Akron Children's Hospital. In our &lt;a href="http://10domains.blogspot.com/2009/09/spyware-causes-hipaa-violation-at-ohio.html" target="_blank"&gt;last post&lt;/a&gt; we wrote about how a misdirected spyware was installed on a computer there, and subsequently leaked financial and medical information.&lt;br /&gt;&lt;br /&gt;In 2006, an intruder broke into their network and compromised a database. Here is what the &lt;a href="https://www.akronchildrens.org/cms/site/16e6640c0d4a89d8/index.html" target="_blank"&gt;FAQ&lt;/a&gt; says:&lt;br /&gt;&lt;blockquote&gt;Akron Children's Hospital recently identified that during an expansion of its computer systems, there were unauthorized entries (breaches) into two separate computer databases. The first database contained personal information of our patients, and of the parents or guardians who provide their health insurance. This personal information included names, addresses, social security numbers and patient birth dates. We have found no evidence that any medical or financial patient information was exposed. &lt;br /&gt;&lt;br /&gt;The second breach involved a server containing information about individuals who have made donations to the hospital. This breach may have exposed personal financial information, specifically some unencrypted bank account and routing numbers. Social security numbers were not included in this database, and credit card information was protected through the highest level of encryption. &lt;br /&gt;&lt;/blockquote&gt;There is a &lt;a href="http://www.wkyc.com/news/news_links/links_article.aspx?storyid=58464" target="_blank"&gt;report&lt;/a&gt; from the local NBC affiliate that says pretty much the same thing, but adds that the intruders came in via a number of intermediate hops.&lt;br /&gt;&lt;br /&gt;Typically, it takes a security breach to wake up a company--it is their "come to Jesus" moment. If after that 2006 breach they did not include simple things like educating employees to not open attachments and blocking outside email access, they were not doing a very good job.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-4527323547314441703?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/4527323547314441703/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=4527323547314441703' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/4527323547314441703'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/4527323547314441703'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/09/fool-me-once.html' title='Fool me once...'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-1183650069930408672</id><published>2009-09-18T04:22:00.000-07:00</published><updated>2009-09-20T06:11:24.815-07:00</updated><title type='text'>Spyware causes HIPAA violation at Ohio Hospital</title><content type='html'>Man emails spyware to ex girlfriend's Yahoo account. What could go wrong?&lt;br /&gt;&lt;br /&gt;The woman happens to work at a hospital. She opened it at a work computer, and the spyware happily emailed out billing and healthcare information for 65 patients. As other people used that computer, it also emailed out their email and financial information (presumably they looked at their online accounts from there)&lt;br /&gt;&lt;br /&gt;CIO Magazine &lt;a href="http://www.cio.com.au/article/319073/misdirected_spyware_infects_ohio_hospital" target="_blank"&gt;reports&lt;/a&gt;:&lt;br /&gt;&lt;div class="art_lcol"&gt;&lt;blockquote&gt;&lt;div class="storybody"&gt;He allegedly sent the spyware to the woman's Yahoo e-mail address, hoping that it would give him a way to monitor what she was doing on her PC. But instead, she opened the spyware on a computer in the hospital's pediatric cardiac surgery department, creating a regulatory nightmare for the hospital.&lt;br /&gt;&lt;/div&gt;&lt;div class="storybody"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="storybody"&gt;The complaint does not explain how Graham managed to convince the woman to install the program, but clever attackers often trick their victims into clicking on files by saying that they are interesting videos or some kind of useful software.&lt;br /&gt;&lt;/div&gt;&lt;div class="storybody"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="storybody"&gt;Between March 19 and March 28 the spyware sent more than 1,000 screen captures to Graham via e-mail.&lt;br /&gt;&lt;/div&gt;&lt;/blockquote&gt;&lt;div class="storybody"&gt;&amp;nbsp;The hospital is also to blame. It is unclear if they provided any training to employees about not opening attachments from emails, but it is absolutely clear that they were not blocking 3rd party email access from work. &lt;br /&gt;&lt;/div&gt;&lt;div class="storybody"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="storybody"&gt;The article is also unclear about if the girlfriend is still employed at work or not.&lt;br /&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-1183650069930408672?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/1183650069930408672/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=1183650069930408672' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1183650069930408672'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1183650069930408672'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/09/spyware-causes-hipaa-violation-at-ohio.html' title='Spyware causes HIPAA violation at Ohio Hospital'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-15419922106917166</id><published>2009-09-16T14:40:00.000-07:00</published><updated>2009-09-16T18:42:58.187-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='foia'/><category scheme='http://www.blogger.com/atom/ns#' term='public record law'/><category scheme='http://www.blogger.com/atom/ns#' term='oregon'/><title type='text'>In Oregon, a manual on Public Records is NOT Public</title><content type='html'>We just wrote about how some Boston City Hall employees were &lt;a href="http://10domains.blogspot.com/2009/09/records-retention-in-local-government.html" target="_blank"&gt;deleting emails&lt;/a&gt; so they would not be subject to Public Record Laws. But in Oregon, Public Record laws are taking an interesting turn.&lt;br /&gt;&lt;br /&gt;The state attorney general publishes a manual for dealing with public record requests, and sell it for $25. He (not personally, his office) also claims copyright over this (public) manual&lt;br /&gt;&lt;br /&gt;Oh, the irony.&lt;br /&gt;&lt;br /&gt;But lets look at the mundane issue first. He claims the $25 is the cost of publishing the hard-copy version of the manual. Yeah? Hasn't he head of PDF files, and "click here to download"? I know Oregon has lots of trees, but shouldn't he at least pretend to care?&lt;br /&gt;&lt;br /&gt;Next: if he can not claim an exemption from the public records law, then he is required to provide this to, hey presto, THE PUBLIC. How can he (or his office) claim copyright to something created with public funds?&lt;br /&gt;&lt;br /&gt;So a professor at University of Oregon has challenged him by posting a scanned copy of the manual on &lt;a href="http://openuporegon.blogspot.com/2009/09/oregon-attorney-generals-public-records.html"  target="_blank"&gt;his blog&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;&lt;/span&gt;&lt;blockquote&gt;Every 2 years the Oregon DOJ publishes the "Oregon Attorney General's Public Records and Meetings Manual", a very useful guide to public records law. It's essential reading for people trying to use their right to get public records from Oregon government agencies. The DOJ has been trying to keep me from redistributing this manual, on the grounds that they own the copyright to it. Trying to use copyright law to keep the public from getting information about how to get public records strikes me as wrong, so I've posted the manual online at my official UO faculty website. As the email below explains, I am posting this despite the fact that the AG's office has explicitly warned me not to redistribute this manual. Here are the links. (now fixed)&lt;/blockquote&gt;&lt;br /&gt;Any bets on when the attorney general will blink? I am predicting around 4:55 PM local time in oregon on Friday, 18th September 2009.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-15419922106917166?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/15419922106917166/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=15419922106917166' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/15419922106917166'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/15419922106917166'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/09/while-in-oregon-manual-on-public.html' title='In Oregon, a manual on Public Records is NOT Public'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-1341757677140976367</id><published>2009-09-13T08:37:00.000-07:00</published><updated>2009-10-14T14:36:17.070-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Kineavy'/><category scheme='http://www.blogger.com/atom/ns#' term='discovery'/><category scheme='http://www.blogger.com/atom/ns#' term='Records'/><category scheme='http://www.blogger.com/atom/ns#' term='city hall'/><category scheme='http://www.blogger.com/atom/ns#' term='Retention'/><category scheme='http://www.blogger.com/atom/ns#' term='Boston'/><title type='text'>Records retention in local government, and Boston City Hall</title><content type='html'>I have a city-hall as my client. Last month I was teaching an awareness class there, and when I mentioned that they should not have any expectation of privacy when using their computers, there was not a single raised eyebrow. Being the employees of a city government, they all knew about public record laws and freedom of information act requests.&lt;br /&gt;&lt;br /&gt;This is different from a private enterprise, where there is always someone who will argue that point.&lt;br /&gt;&lt;br /&gt;(as an aside, I had to throw away most of my examples of what is "confidential". Individual's salary figures? Not confidential. Next year's budget numbers? Not confidential. Agh).&lt;br /&gt;&lt;br /&gt;Looks like the City of Boston's senior management knew all about the "&lt;a href="http://www.boston.com/news/local/massachusetts/articles/2009/09/13/meninos_office_acknowledges_city_employees_routinely_deleted_e_mails?mode=PF"&gt;no expectation of privacy&lt;/a&gt;" too:&lt;br /&gt;&lt;blockquote&gt;The acknowledgement came after the Globe filed several requests for e-mails sent and received by Menino’s Cabinet chief of policy and planning, Michael J. Kineavy. He is one of Menino’s most powerful and trusted advisers, intimately involved in nearly everything at City Hall, but a search of city computers found just 18 e-mails he had sent or received between Oct. 1, 2008, and March 31 of this year.&lt;br /&gt;&lt;br /&gt;The unusually low figure prompted administration officials to question him about what happened to the rest of the e-mails he was presumably sending and receiving during that period. Kineavy, who is also one of the mayor’s chief political advisers and a strategist on Menino’s reelection campaigns since 1993, told them that he deletes all his e-mails on a daily basis, in such a way that they are not saved on city backup computers, administration officials said.&lt;br /&gt;&lt;br /&gt;There are indications that Kineavy was not the only city employee who may have violated the law. In June, the Globe filed requests for copies of six months’ worth of e-mails sent or received by five other employees, including Transportation Commissioner Thomas Tinlin. City officials said that a search for Tinlin’s e-mails turned up only those he had received, none he had sent.&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-1341757677140976367?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/1341757677140976367/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=1341757677140976367' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1341757677140976367'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1341757677140976367'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2009/09/records-retention-in-local-government.html' title='Records retention in local government, and Boston City Hall'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-8472955361911424789</id><published>2008-10-26T20:27:00.000-07:00</published><updated>2008-10-26T20:52:05.563-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='FAQ'/><category scheme='http://www.blogger.com/atom/ns#' term='Consultant'/><category scheme='http://www.blogger.com/atom/ns#' term='Startup'/><category scheme='http://www.blogger.com/atom/ns#' term='Consultancy'/><title type='text'>How would you start a network/security consulting business?</title><content type='html'>If you the typical security person, sales is not your strong suite. Heck, you may actually be very bad as a sales person. And since without sales you are not going to earn any money from this consultancy, you need someone who can actually close sales.&lt;br /&gt;&lt;br /&gt;So what are you going to sell? Services? Do you have any software or other solution you will be offering? Go ahead, write them down in bullets. I know you know them, but you will be surprised when you try to boil each down into a soundbite. If you don't know this already, it is called an 'elevator pitch' because sometimes you will have a 10 or 20-second opportunity to make your case to a client, and that will not be the time to think up something clever to say. So know what you are selling, and know how to condense that to an elevator pitch.&lt;br /&gt;&lt;br /&gt;Other things:&lt;br /&gt;1. Now that you know what you are going to offer, and what your pitch is, get a good sales guy. Seriously. Your team may be extremely talented, but they need the contacts and they need the personality to 'close' sales. Not something techies are good at.&lt;br /&gt;2. Create proposal, report and assessment templates (and get website/email/phones the usual logistics stuff)&lt;br /&gt;3. More than one person? Think about the corporate structure. LLC, S-corp, C-corp? (Google for the differences and how each may effect you). Don't put this off--no matter how good friends you all are.&lt;br /&gt;3. Land your first customer. Make sure s/he is willing to be a reference. Start looking for this customer now, even before the business is fully formed. The first customer is the hardest to get. Start by talking to people who are in a position to buy your offering. If you are currently working for someone else, you need to have a very clear idea about who is going to be your customer. Talk to every consulting firm, software company and VAR in your region.&lt;br /&gt;4. Speak at places/seminars/conferences where potential customers show up. Stay longer and listen to them, talk to them, solve problems for them or give them pointers. People like nice people.&lt;br /&gt;5. Did I say you need a sales person with a rolodex full of contacts that s/he already knows from previous jobs? You can hire someone on commission. Make a deal with a hardware sales-guy (so there is no conflict of interest)--when s/he visits a customer s/he can mention your company, make an introduction, etc.&lt;br /&gt;6. Prepare for an initial dry spell. If the people can not handle no income, no health insurance, etc. for 6 months (just to be safe) then they are not ready for this. If you do hit the doldrums, look into opportunities for potential part-time contract work. It may sound strange, but this may help provide sustenance during lean periods. (for this, check out &lt;a href="http://www.dice.com/"&gt;DICE&lt;/a&gt;, which lets you search for contract work based on W-2, corp-to-corp, etc). And don't forget, once you are at a contract gig, you are meeting a potential client who may hire your company for the next job.&lt;br /&gt;&lt;br /&gt;Misc:&lt;br /&gt;Any decent-sized clients will ask you about your workman's compensation, liability and errors/omissions insurance. This will set you back a few thousand dollars--talk to an insurance agent and find out.&lt;br /&gt;&lt;br /&gt;Good luck.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-8472955361911424789?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/8472955361911424789/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=8472955361911424789' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/8472955361911424789'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/8472955361911424789'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2008/10/how-would-you-start-networksecurity.html' title='How would you start a network/security consulting business?'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-1147468204616398552</id><published>2008-10-23T08:12:00.000-07:00</published><updated>2009-01-07T09:42:58.983-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Growth'/><category scheme='http://www.blogger.com/atom/ns#' term='CISO'/><category scheme='http://www.blogger.com/atom/ns#' term='Career'/><category scheme='http://www.blogger.com/atom/ns#' term='Mentoring'/><title type='text'>Career Progression: How to become a CISO</title><content type='html'>I am often asked about this--to the degree that this is now a frequently asked question. Sorry, there is no magic formula.&lt;br /&gt;&lt;br /&gt;There are two parts to the answer: How to 'get' the job and How to be 'good at it' that are intermixed.&lt;br /&gt;&lt;br /&gt;My first CISO job was through applying directly. I was a director at a financial industry giant, and became the first CISO at a 500-million-dollar financial services company.&lt;br /&gt;&lt;br /&gt;My next CISO gig was for a company with about $1B in revenue, and I was recruited by a retained search firm.&lt;br /&gt;&lt;br /&gt;Here is the summary of my experience:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Relevant industry sector experience: going from financial services to healthcare (or vice versa is very rare)&lt;/li&gt;&lt;li&gt;CISO/CSOs are typically director or above positions. If you already have a director or VP title, that helps&lt;/li&gt;&lt;li&gt;If you are already a CISO, that also helps. A lot.&lt;/li&gt;&lt;li&gt;If you are not being promoted from within, having a bachelors degree is absolutely required.&lt;/li&gt;&lt;li&gt;Soft skills like communication is absolutely important. So is a demonstrated business skills, budgeting, people management, etc.&lt;/li&gt;&lt;li&gt;If a CISO job description says you need hands-on experience configuring firewalls (or some other specific technology), tread carefully. Either the job description is wrong, or it is not a CISO job. There are exceptions, of course, but this is a good indicator.&lt;/li&gt;&lt;li&gt;If other C-level officers are not in the interview team, you are not getting a 'real' CISO job, regardless of what the title is&lt;/li&gt;&lt;li&gt;As a CISO, your job will be to make people who you have no direct influence over do things for you.&lt;/li&gt;&lt;li&gt;You have to have direct reports and budget experience&lt;/li&gt;&lt;li&gt;At the interview, you have to make them understand that [a] security will help business and [b] you understand and care about the business--you are not just a security-nazi.&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;If you can show most or all of the above in your resume and during the interview, that would be a huge help.&lt;br /&gt;&lt;br /&gt;Networking definitely helps, but we all can't know the CEO, so working with recruiters is the next best thing. If it is a retained search, that is great. If it is a contingency, that is fine, too--but before you send a resume, talk to the recruiter and make sure they don't submit you before asking your permission first.&lt;br /&gt;&lt;br /&gt;How about certifications? It is expected that the CISO will have at least one major certification. If the CISO position is asking for just A+ or Security+ certifications, see number 6 above. ISACA designed the CISM for the CISO-level professionals, but not many employers are making this the primary certification requirement. CISSP is still the certification to have for any senior security job, although it really does not cover the management of an information security program. The CISA is not directly needed, but helpful because as a true CISO you will have to deal with internal and external auditors. It is my opinion that the certifications do not indicate how good a candidate will be as a strategic leader, but they certainly show relevant job skills. On the other hand, it is easy to establish your business-friendliness if you have an MBA.&lt;br /&gt;&lt;br /&gt;Good luck.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-1147468204616398552?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/1147468204616398552/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=1147468204616398552' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1147468204616398552'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1147468204616398552'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2008/10/career-progression-how-to-become-ciso.html' title='Career Progression: How to become a CISO'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-1860670868428105837</id><published>2007-10-04T08:44:00.000-07:00</published><updated>2007-10-04T08:46:39.000-07:00</updated><title type='text'>A "Cyberist" meets his match: Stephen Colbert</title><content type='html'>Don't the cops have some murder or rape to investigate? This is a classic case of an overzealous cop eager to pad his stats. Judge for yourself.&lt;br /&gt;&lt;embed FlashVars="videoId=104580" src='http://www.comedycentral.com/sitewide/video_player/view/default/swf.jhtml' quality='high' bgcolor='#cccccc' width='332' height='316' name='comedy_central_player' align='middle' allowScriptAccess='always' allownetworking='external' type='application/x-shockwave-flash' pluginspage='http://www.macromedia.com/go/getflashplayer'&gt;&lt;/embed&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-1860670868428105837?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/1860670868428105837/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=1860670868428105837' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1860670868428105837'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/1860670868428105837'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2007/10/cyberist-meets-his-match-stephen.html' title='A &quot;Cyberist&quot; meets his match: Stephen Colbert'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-7546103030658264353</id><published>2007-03-28T04:45:00.000-07:00</published><updated>2007-03-28T04:59:16.505-07:00</updated><title type='text'>The Immaculate Hack</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_RaDk956KPXY/RgpWOjPbKxI/AAAAAAAAAAU/PFx-prik-gw/s1600-h/634672.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="http://2.bp.blogspot.com/_RaDk956KPXY/RgpWOjPbKxI/AAAAAAAAAAU/PFx-prik-gw/s400/634672.jpg" alt="" id="BLOGGER_PHOTO_ID_5046941140400155410" border="0" /&gt;&lt;/a&gt;The web was mostly built by borrowing other people's code and images, and sometimes even their bandwidth (when one party just linked to the image residing on someone else's server and showed it on his own--this is also known as 'leeching'). Leeching may actually be illegal, because it uses someone else's resources without permission.&lt;br /&gt;&lt;br /&gt;The John McCain crew found out the hard way its not nice to leech.&lt;br /&gt;&lt;br /&gt;Mike Davidson, who created the template used at McCain's MySpace page was a little miffed that McCain's page was leeching the 'contact John' image from his server (and costing him bandwidth and money). So he created a new graphic, and uploaded it to &lt;a href="http://mike.newsvine.com/_news/2007/03/26/633799-hacking-john-mccain"&gt;&lt;span style="font-weight: bold;"&gt;his own server&lt;/span&gt;&lt;/a&gt; under the same name as the previous graphic. And just like that, McCain's position was changed).&lt;br /&gt;&lt;br /&gt;Technically, no crime was committed: Mike changed a graphic on his own equipment. Who else was using it and how, was not his concern.&lt;br /&gt;&lt;br /&gt;I hope the Sen. McCain will have a sense of humor about this because the FBI can, and may, cart away Mike D's hardware first and ask questions later.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-7546103030658264353?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/7546103030658264353/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=7546103030658264353' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7546103030658264353'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7546103030658264353'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2007/03/immaculate-hack.html' title='The Immaculate Hack'/><author><name>J</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_RaDk956KPXY/RgpWOjPbKxI/AAAAAAAAAAU/PFx-prik-gw/s72-c/634672.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-8140830518576881337</id><published>2007-02-19T08:11:00.000-08:00</published><updated>2007-02-19T08:15:50.332-08:00</updated><title type='text'>Card skimming at supermarket checkouts</title><content type='html'>&lt;a href="http://en.wikipedia.org/wiki/Credit_card_fraud#Skimming"&gt;Card skimming&lt;/a&gt; is the technique of installing a fake Credit/Debit card reader to capture card information. Until now, this only existed in the Bank ATM world. But no more: now it happened at &lt;a href="http://www.boston.com/business/globe/articles/2007/02/19/stop__shop_reports_credit_data_was_stolen/"&gt;Stop &amp; Shop checkouts&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;quote&gt;&lt;blockquote&gt;They would not now be able to tamper with the units the way they did before," Keane said. He declined to reveal details of how the scam worked, other than to say it involved card readers being removed, tampered with, and reinstalled. "Our investigation has not uncovered any involvement or suspected involvement of any Stop &amp;amp; Shop personnel in the tampering.&lt;/blockquote&gt;&lt;/quote&gt;I am a regular Stop &amp; Shop customer, and I don't buy this. Someone can't just walk into a store, remove a card reader and reinstall it (even if the whole thing takes 2 minutes). Unless it involved the company that services the POS terminals. In that case, why isn't S&amp;amp;S pointing the finger at them? I think we are seeing another gradual release of bad news (like ChoicePoint and TJX).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-8140830518576881337?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/8140830518576881337/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=8140830518576881337' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/8140830518576881337'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/8140830518576881337'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2007/02/card-skimming-at-supermarket-checkouts.html' title='Card skimming at supermarket checkouts'/><author><name>JI</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-73472028979354873</id><published>2007-01-18T19:20:00.000-08:00</published><updated>2008-10-23T08:25:49.322-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='tjx id theft PCI credit card breach'/><title type='text'>What was TJX thinking?</title><content type='html'>&lt;div&gt;This type of thing happens so regularly its not even news. Massachusetts based TJX, the parent company of TJ-MAX, Marshalls, HomeGoods and Bobs Store, got hacked, and more than a million credit and debit card information, sometimes with drivers license information, were stolen. More than a million? It sure sounds like they don't know the exact figure, but its growing.&lt;br /&gt;&lt;br /&gt;Data going as far back as 2003 was compromised sometime in December 2006, and TJX was working with law enforcement and kept the news hidden until then.&lt;br /&gt;&lt;br /&gt;A &lt;a href="http://www.boston.com/business/articles/2007/01/18/tjx_credit_data_stolen_wide_impact_feared/?page=full"&gt;story in the Boston Globe&lt;/a&gt; seems to indicate it was not an insider.  Of course, TJX will never share the findings about how this happened, but what were they doing with this data in the first place?&lt;br /&gt;&lt;br /&gt;And the magnitude of the breach seems to be &lt;a href="http://www.boston.com/business/ticker/2007/01/banks_report_mo_1.html"&gt;growing&lt;/a&gt;. Are they playing a "gradual disclosure" game like &lt;a href="http://www.consumeraffairs.com/news04/2005/choicepoint_worse.html"&gt;ChoicePoint&lt;/a&gt;? The Massachusetts banker's association &lt;a href="http://www.boston.com/business/ticker/2007/01/banks_report_mo_1.html"&gt;doesn't like the scope and duration of data retention&lt;/a&gt;.&lt;br /&gt;&lt;blockquote&gt;The bankers' association also questioned why TJX kept credit- and debit-card&lt;br /&gt;information on file for so long. "It appears that they may have been&lt;br /&gt;capturing data that is unnecessary," Daniel J. Forte, the bankers&lt;br /&gt;association president, said in a statement today.&lt;br /&gt;&lt;br /&gt;TJX spokeswoman  Sherry Lang would not comment on the bankers' association&lt;br /&gt;statement. She  reiterated that the company does not yet know of any acts of&lt;br /&gt;fraud related  to customers' personal data. &lt;/blockquote&gt;The &lt;a href="https://www.pcisecuritystandards.org/tech/index.htm"&gt;PCI standard&lt;/a&gt; requires protection of stored cardholder data. So what happens if the data is not protected? A slap on the wrist? &lt;a href="https://www.pcisecuritystandards.org/pdfs/pci_security_standards_council_statement_on_recent_data_breaches.pdf"&gt;Not even that&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Oh, by the way, TJX has not offered to provide credit monitoring or any such service. I'd recommend calling TJX at (866) 484-6978 and asking for credit monitoring.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-73472028979354873?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/73472028979354873/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=73472028979354873' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/73472028979354873'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/73472028979354873'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2007/01/what-was-tjx-thinking.html' title='What was TJX thinking?'/><author><name>JI</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-7118119069088520041</id><published>2007-01-08T05:03:00.000-08:00</published><updated>2007-01-08T05:22:23.083-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='secure coding'/><category scheme='http://www.blogger.com/atom/ns#' term='firewall'/><category scheme='http://www.blogger.com/atom/ns#' term='development'/><category scheme='http://www.blogger.com/atom/ns#' term='ranum'/><category scheme='http://www.blogger.com/atom/ns#' term='Fortify'/><title type='text'>Secure coding (and 'Vulnerability Pimps')</title><content type='html'>Application security is one of my favorite areas, and as a result, secure coding techniques, and source code review. &lt;a href="http://www.ranum.com"&gt;Marcus Ranum&lt;/a&gt;, he of the firewall fame, recently wrote an &lt;a href="http://www.ranum.com/security/computer_security/editorials/codetools/"&gt;article &lt;/a&gt;about running an automated source code analyzer against Firewall Toolkit.&lt;br /&gt;&lt;br /&gt;As he says in the footnote,&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;The Firewall Toolkit later became the core of the TIS Gauntlet firewall. For a few years after its release, the FWTK code-base was at the center of more than half of the firewalls on the Internet.&lt;br /&gt;&lt;/blockquote&gt;And the code had been reviewed/worked on by many people, but some security issues, including one buffer overflow, was left undiscovered in the code. Lesson? If you have a large codebase, you need to run a software like &lt;a href="http://www.fortifysoftware.com/"&gt;Fortify &lt;/a&gt;to find the quick hits that would be otherwise buried in the code.&lt;br /&gt;&lt;br /&gt;In the same article, Ranum created a new term: &lt;a href="http://www.ranum.com/security/computer_security/editorials/codetools/#pimp"&gt;Vulnerability Pimps&lt;/a&gt;. These are the so-called security researchers who attempt to discover flaws just to gain fame.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-7118119069088520041?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/7118119069088520041/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=7118119069088520041' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7118119069088520041'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/7118119069088520041'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2007/01/secure-coding-and-vulnerability-pimps.html' title='Secure coding (and &apos;Vulnerability Pimps&apos;)'/><author><name>JI</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-2395192392303062055</id><published>2007-01-01T10:19:00.000-08:00</published><updated>2007-01-01T10:39:23.933-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='legal'/><category scheme='http://www.blogger.com/atom/ns#' term='privacy'/><category scheme='http://www.blogger.com/atom/ns#' term='securityfocus'/><category scheme='http://www.blogger.com/atom/ns#' term='doj'/><category scheme='http://www.blogger.com/atom/ns#' term='ACLU'/><title type='text'>The psychology of risk (and why we worry about stuff we should not)</title><content type='html'>That title could sum up risk management (and will be a recurring theme at 10domains).&lt;br /&gt;&lt;br /&gt;I just read an &lt;a href="http://www.securityfocus.com/brief/396"&gt;article on SecurityFocus&lt;/a&gt; about an effort by the  US Department of Justice (DOJ) to standardize the format they store criminal records, and how its raising privacy fears. I am all for privacy, and a believer in the &lt;a href="http://www.gpoaccess.gov/constitution/html/amdt4.html"&gt;4th amendment&lt;/a&gt;. But I fail to see how a standardized method for record format and access increases the privacy risk.&lt;br /&gt;&lt;span class="body"&gt;&lt;blockquote&gt; "Raw police files or FBI reports can never be verified and can never be corrected," Barry Steinhardt, director of the Technology and Liberty Project at the American Civil Liberties Union, told the Washington Post. "That is a problem with even more formal and controlled systems. The idea that they're creating another whole system that is going to be full of inaccurate information is just chilling."&lt;/blockquote&gt;&lt;/span&gt;&lt;br /&gt;I agree with the first statement. But Mr. Steinhardt fails to explain how a new system increases the risk. I am not pulling out the old chestnut of "if you have done nothing wrong, you have nothing to fear" but seriously, the US DoJ already knows whatever it needs to know about you, and the other LEAs (Law Enforcement Agency) can get access to all the records there are--it just takes longer now. Reducing that timeframe (and associated costs) does not make your life any less private.&lt;br /&gt;&lt;br /&gt;Which reminds me, one of these days I will post my rant against the opposition to a US National ID Card. If you carry a driver's license or have a social security number, you are already part of the Borg collective my friend.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-2395192392303062055?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/2395192392303062055/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=2395192392303062055' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2395192392303062055'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/2395192392303062055'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2007/01/psychology-of-risk-and-why-worry-about.html' title='The psychology of risk (and why we worry about stuff we should not)'/><author><name>JI</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-4840000394990027911</id><published>2007-01-01T09:53:00.000-08:00</published><updated>2007-01-01T10:06:47.540-08:00</updated><title type='text'>Why 10domains?</title><content type='html'>Someone just asked me why I picked 10domains. For people in the information security world, this is actually a pretty easy answer. &lt;a href="http://www.isc2.org"&gt;(ISC)&lt;/a&gt;&lt;sup&gt;&lt;a href="http://www.isc2.org"&gt;2&lt;/a&gt; &lt;/sup&gt;, the organization that runs the &lt;a href="https://www.isc2.org/cgi-bin/content.cgi?category=97"&gt;CISSP &lt;/a&gt;(and a few other) certification program. CISSP stands for Certified Information Systems Security Professional, and requires knowledge in 10 domains of information security:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Access Control&lt;/li&gt;&lt;li&gt;Application Security&lt;/li&gt;&lt;li&gt;Business Continuity and Disaster Recovery Planning&lt;/li&gt;&lt;li&gt;Cryptography&lt;/li&gt;&lt;li&gt;Information Security and Risk Management&lt;/li&gt;&lt;li&gt;Legal, Regulations, Compliance and Investigations&lt;/li&gt;&lt;li&gt;Operations Security&lt;/li&gt;&lt;li&gt;Physical (Environmental) Security&lt;/li&gt;&lt;li&gt;Security Architecture and Design&lt;/li&gt;&lt;li&gt;Telecommunications and Network Security&lt;/li&gt;&lt;/ul&gt;This blog will cover these 10 domains (and use them to label and classify the posts), hence the name.&lt;br /&gt; &lt;img src="https://www.isc2.org/images/color_clear.gif" height="1" width="37" /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-4840000394990027911?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/4840000394990027911/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=4840000394990027911' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/4840000394990027911'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/4840000394990027911'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2007/01/why-10domains.html' title='Why 10domains?'/><author><name>JI</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6050101211475163815.post-4366157358967409347</id><published>2007-01-01T06:33:00.000-08:00</published><updated>2007-01-01T06:36:47.006-08:00</updated><title type='text'>YAB (Yet Another Blog) on Information Security</title><content type='html'>Why?&lt;br /&gt;Call this an effort to give a little back to the world. Hopefully the signal to noise ration will be good enough for people to find this useful.&lt;br /&gt;&lt;br /&gt;The audience for this blog will range from the merely curious to professionals, from soccer moms to industry veterans.&lt;br /&gt;&lt;br /&gt;Welcome.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6050101211475163815-4366157358967409347?l=10domains.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://10domains.blogspot.com/feeds/4366157358967409347/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6050101211475163815&amp;postID=4366157358967409347' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/4366157358967409347'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6050101211475163815/posts/default/4366157358967409347'/><link rel='alternate' type='text/html' href='http://10domains.blogspot.com/2007/01/yab-yet-another-blog-on-information.html' title='YAB (Yet Another Blog) on Information Security'/><author><name>JI</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
