<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;C0IGSHk8eyp7ImA9WhRUF08.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946</id><updated>2012-01-27T19:32:09.773-08:00</updated><category term="Steganography" /><category term="vulnerability" /><category term="malware" /><category term="MD Food Bank" /><category term="photo frames" /><category term="privacy" /><category term="McAfee" /><category term="baltimore" /><category term="Skype" /><category term="US government" /><category term="dslr" /><category term="information security" /><category term="2600" /><category term="resources" /><category term="email" /><category term="xss" /><category term="2008" /><category term="EU Directive 95/46/EC" /><category term="attack" /><category term="VeriSign" /><category term="Department of Homeland Security" /><category term="authentication" /><category term="lock" /><category term="qr code" /><category term="Jeff Moss" /><category term="azure" /><category term="policy" /><category term="government" /><category term="cats" /><category term="Bid Pal" /><category term="trojan" /><category term="mvc" /><category term="obama" /><category term="Matt Asay" /><category term="iPhone" /><category term="power" /><category term="worm" /><category term="marketing" /><category term="asp.net" /><category term="white hat" /><category term="Internet Explorer" /><category term="network" /><category term="cnet river" /><category term="event log" /><category term="membership provider" /><category term="anti-virus" /><category term="google" /><category term="education" /><category term="technology" /><category term="smtp" /><category term="OAuth" /><category term="system.web.management" /><category term="application health monitoring" /><category term="secure" /><category term="event" /><category term="Confliker" /><category term="AVG" /><category term="decieve" /><category term="CEH" /><category term="print to web" /><category term="organized crime" /><category term="Chrome" /><category term="charity" /><category term="filler" /><category term="codec" /><category term="lojack" /><category term="asp.net 2.0" /><category term="CSRF" /><category term="SSL" /><category term="firewall" /><category term="cyber warfare" /><category term="Powerpoint" /><category term="learning" /><category term="branding" /><category term="OneCare" /><category term="ASI" /><category term="hack" /><category term="Houston" /><category term="cloud computing" /><category term="pdc" /><category term="cell phone" /><category term="asirra" /><category term="social engineer" /><category term="Open Source" /><category term="port knocking" /><category term="end point security" /><category term="phishing" /><category term="Evil Twin" /><category term="Web Browser" /><category term="wpf" /><category term="virus" /><category term="polaroid" /><category term="IT business" /><category term="wmi" /><category term="health" /><category term="management" /><category term="port scanning" /><category term="Ireland" /><category term="strong password" /><category term="hip" /><category term="mobile" /><category term="smart grid" /><category term="OSX/Tored-A" /><category term="beyond bullet points" /><category term="MEDEX" /><category term="Channel 9" /><category term="comic" /><category term="facial recognition" /><category term="Conversion" /><category term="application security" /><category term="windows 7" /><category term="firefox" /><category term="encryption" /><category term="Flash" /><category term="computer forensics" /><category term="iPod" /><category term="LinkedIn" /><category term="x-force report" /><category term="network security" /><category term="microsoft tag" /><category term="Safari" /><category term="windows azure" /><category term=".net" /><category term="tv" /><category term="MD5" /><category term="OSX/Jahlav-C" /><category term="jquery mobile" /><category term="laptop" /><category term="Adobe" /><category term="asp" /><category term="Downadup" /><category term="business" /><category term="css 3" /><category term="jQuery" /><category term="cyber crime" /><category term="port daemon" /><category term="Italy" /><category term="Scott Gutherie" /><category term="os" /><category term="security" /><category term="dogs" /><category term="WorldWatch" /><category term="river" /><category term="links" /><category term="hacker" /><category term="stupid human tricks" /><category term="theft" /><category term="software" /><category term="Zune" /><category term="microsoft research" /><category term="europe" /><category term="con" /><category term="Clickjacking" /><category term="china" /><category term="cross site scripting" /><category term="applicaton health" /><category term="vista" /><category term="web injection" /><category term="MSE" /><category term="provider" /><category term="javascript" /><category term="apple" /><category term="IT image" /><category term="web development" /><category term="data delivery" /><category term="ISSA" /><category term="general" /><category term="sql injection" /><category term="maryland" /><category term="Hakin9" /><category term="event mapping" /><category term="security q and a" /><category term="social networking" /><category term="Internet Browser" /><category term="health monitor" /><category term="crime" /><category term="the Myth of Security" /><category term="monitor" /><category term="html 5" /><category term="Presentation" /><category term="windows" /><category term="port" /><category term="threat modelling" /><category term="code review" /><category term="operating system" /><category term="linux" /><category term="computer science" /><category term="DHS" /><category term="cnet" /><category term="Adobe Flash" /><category term="twitter api" /><category term="research" /><category term="internet security" /><category term="law" /><category term="ajax" /><category term="cliff atkinson" /><category term="Music" /><category term="John Viega" /><category term="&quot;I'm a PC&quot;" /><category term="werewolf" /><category term="games" /><category term="bbc" /><category term="biometric" /><category term="API" /><category term="C#" /><category term="trash" /><category term="certification" /><category term="captcha" /><category term="IT's image" /><category term="food" /><category term="microsoft" /><category term="publication" /><category term="article" /><category term="Airline Insider" /><category term="mozilla" /><category term="password" /><category term="brand" /><title>SecCode: Securing the Wild Wild Web</title><subtitle type="html">Examining security and the technologies that will be shaping tomorrow.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://seccode.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>86</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/SeccodeSecuringTheWildWildWeb" /><feedburner:info uri="seccodesecuringthewildwildweb" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;C0IGSHkyfip7ImA9WhRUF08.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-1498798344553653160</id><published>2012-01-27T19:32:00.000-08:00</published><updated>2012-01-27T19:32:09.796-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-27T19:32:09.796-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="web development" /><category scheme="http://www.blogger.com/atom/ns#" term="software" /><category scheme="http://www.blogger.com/atom/ns#" term="management" /><title>Inspirational leadership</title><content type="html">I've been working on a technical post for a while now but am slow going. So I wanted to post something else I have been thinking about lately: inspirational leadership. Lately I have been rereading &lt;a href="http://www.amazon.com/gp/product/1593271832/ref=as_li_ss_tl?ie=UTF8&amp;amp;tag=secsecthewilw-20&amp;amp;linkCode=as2&amp;amp;camp=1789&amp;amp;creative=390957&amp;amp;creativeASIN=1593271832"&gt;Growing Software: Proven Strategies for Managing Software Engineers&lt;/a&gt;&amp;nbsp;by Louis Testa and examining how I have been leading my software team. The book is an excellent survival guide for new development managers and yields some excellent advice on how to build, maintain and nourish a great team. Between this book and another great read &lt;a href="http://www.amazon.com/gp/product/0735623465/ref=as_li_ss_tl?ie=UTF8&amp;amp;tag=secsecthewilw-20&amp;amp;linkCode=as2&amp;amp;camp=1789&amp;amp;creative=390957&amp;amp;creativeASIN=0735623465"&gt;Getting Results from Software Development Teams&lt;/a&gt;&lt;img alt="" border="0" height="1" src="http://www.assoc-amazon.com/e/ir?t=secsecthewilw-20&amp;amp;l=as2&amp;amp;o=1&amp;amp;a=0735623465" style="border: none !important; margin: 0px !important;" width="1" /&gt; by Laurence J. Peters I have boiled down a few techniques that seem to be working for me.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Communication is Key&lt;/b&gt;&lt;br /&gt;
This should be no surprise. Maintaining good communication is important in any relationship most especially manager to employee. Communicate frequently with your team and set a standard for how you want your team to communicate with others. For instance, I encourage a high level of follow-up with my team. If they do not understand something or need to ensure the audience of a communication understood their message, follow up. This encourages conversation instead of a "telling" message that I have seen with many technical people. To support this behavior I make sure to turn email communications into conversations until both parties clearly understand each other. Technical people are often quick to email rather than stop by someone's desk or call. Encourage your team to connect to others in the most personal way possible but to follow up with a documented communication (i.e. email) when necessary.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Check-in but don't&amp;nbsp;interrogate&lt;/b&gt;&lt;br /&gt;
Every morning I make sure to say "Good morning" to each of my team that I encounter. Throughout the day I stop by or give them a call to ask how their day is going and if they need anything from me. This is a balancing act to check-in but not to be interrogating the individual on their daily progress. I try to keep the message short and sweet, "How's it going? Is there anything I can do to help? Do you need anything from me?" I use those three questions a lot to just ping my team to make sure they are not struggling with something that I can help with. Managers are really just support staff to their team. These check-ins allow me to see how I can best support the team.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;One on Ones are about the Person, not the Projects&lt;/b&gt;&lt;br /&gt;
This one is simple, keep one on ones about the individual. Do not let the meeting fall into a project update. One on Ones are to talk about how the person is doing with the company and team. Ask questions like:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;How do you think the team is doing?&lt;/li&gt;
&lt;li&gt;Are there any questions about a recent change in the company or P&amp;amp;Ps?&lt;/li&gt;
&lt;li&gt;What are your future plans? Where do you want to be in 5 years? How can we help you get there?&lt;/li&gt;
&lt;li&gt;How am I (as the manager) doing?&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Value the ideas&lt;/b&gt;&lt;br /&gt;
Technical people are often creative people. To a coder, the language is a brush and the software a canvas awaiting a master piece. Software development is an extremely creative process and that creativity needs to be fed often to grow. Creativity feeds off of ideas and to this end, placing value on ideas will encourage techies to generate more and more ideas. I like it when others recognize my idea's merit, so I try to do that for others. I encourage my team to be creative and discover many solutions for a single problem. While not all ideas are actionable, they all feed the team's creativity and yield more ideas...better ideas. I encourage my team to express ideas by placing value on those ideas. Value is shown through support, recognition and even reward (never under estimate the power of a $25 gift card!).&lt;br /&gt;
&lt;br /&gt;
These are a few things that I have found really brighten up my team. What do you do to inspire your team?&lt;br /&gt;
&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-1498798344553653160?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/nZujDuVHHQ93fonE7AU0cmdUtZI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/nZujDuVHHQ93fonE7AU0cmdUtZI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/nZujDuVHHQ93fonE7AU0cmdUtZI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/nZujDuVHHQ93fonE7AU0cmdUtZI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/CfsS7rpPYdg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/1498798344553653160/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=1498798344553653160" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/1498798344553653160?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/1498798344553653160?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/CfsS7rpPYdg/inspirational-leadership.html" title="Inspirational leadership" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><georss:featurename>Baltimore, MD, USA</georss:featurename><georss:point>39.2903848 -76.6121893</georss:point><georss:box>39.1920723 -76.7701178 39.3886973 -76.4542608</georss:box><feedburner:origLink>http://seccode.blogspot.com/2012/01/inspirational-leadership.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkIHQn86eip7ImA9WhRVEUs.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-7864521343262300353</id><published>2012-01-09T20:08:00.000-08:00</published><updated>2012-01-09T20:08:53.112-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-09T20:08:53.112-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="qr code" /><category scheme="http://www.blogger.com/atom/ns#" term="mobile" /><category scheme="http://www.blogger.com/atom/ns#" term="print to web" /><category scheme="http://www.blogger.com/atom/ns#" term="microsoft tag" /><category scheme="http://www.blogger.com/atom/ns#" term="microsoft" /><title>Continued discussion: QR Tags and Security</title><content type="html">&lt;a href="http://4.bp.blogspot.com/-1WmGvieDjjo/TwuscL97JGI/AAAAAAAAAMM/_3NUexRES7Y/s1600/qr+tag+sample.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="184" src="http://4.bp.blogspot.com/-1WmGvieDjjo/TwuscL97JGI/AAAAAAAAAMM/_3NUexRES7Y/s200/qr+tag+sample.png" width="200" /&gt;&lt;/a&gt;My newest article just hit the Internet today and I'm pretty psyched about the topic: Tagging (more commonly known as QR Codes but I use the term Tag for Microsoft Tag and QR Codes). A few years ago I saw the start up of &lt;a href="http://tag.microsoft.com/" target="_blank"&gt;Microsoft Tag&lt;/a&gt;. I had not heard about QR Codes at the time so the concept of jumping from print to the Internet with a point and click interface was pretty awesome to me. Instantly I saw applications at my work, on side projects, at my karate school and had a brain storm more akin to a&amp;nbsp;tornado. Recently I have had the fortune of implementing some of these solutions and a few security issues came to mind...and then a few more until the tornado became a hurricane threatening to drown the projects.&lt;br /&gt;
&lt;br /&gt;
In the &lt;a href="http://hakin9.org/" target="_blank"&gt;Hakin9&lt;/a&gt; article, I examine three attack vectors using Tags. While I like to play with attack, I enjoy&amp;nbsp;prescribing&amp;nbsp;defense so I thought I would use the blog to discuss some prevention strategies to mitigate your risk of falling victim to a malicious Tag. Here are some tips to avoid a Tag related data compromise:&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;1. Never click on an unknown Tag: &lt;/b&gt;Avoid clicking Tags that you do not have confidence in their intent, the integrity of their publisher or the integrity of distribution. If at any point you are unsure of what a Tag will do after scanning or do not trust the publisher, do not scan the tag. As a motto in security (physical or information) if something does not feel right, it probably is not. Another consideration is the confidence level you have in that the distribution medium has not been tampered with. A Tag in a print magazine that is distributed world wide is less likely to be malicious as compared to a Tag found on a forum. A random tag posted on a blog, forum or web site (or Facebook profile picture) might not be reviewed by an editorial staff. Malicious Tags can sneak in (or be deliberately placed) on these mediums without review or oversight.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;2. Your device can be accessed by more than just you:&lt;/b&gt; This is a standard &lt;a href="https://www.owasp.org/index.php/Top_10_2010-A5" target="_blank"&gt;CSRF &lt;/a&gt;defense but really needs to be considered with Tagging. A CSRF attacks occur when a user (you) do something (like click on a Tag) and a request is sent to the application that does some unintended&amp;nbsp;action (like change your password to something the attacker will know). These attacks only work when you are authenticated to the application being attacked. As diligent computer users, some security aware people log out of the various applications they access through their desktop systems but not their mobile device. We see our mobile device as ours, specific to us and that no one else uses the device. Due to this mindset, we do not perform behaviors to mitigate information exposure (via someone else accessing our device). Yes, this is a generalization and maybe you do not agree but it has been my experience that many average users (non-IT and non-IT Security) people think this way. What many of these people do not realize is that someone can use their device without physical access. Moderns phones are simply tiny computers, some with more power than what might be sitting at the user's desk. Always log out of your applications on your mobile device.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;3. Research your scanner:&lt;/b&gt; Does your Tag scanner provide some protection mechanisms (like Microsoft Tag)? Cloud based Tag systems can provide a level of protection to users such as a black list filter, identifying known malicious tags as well as publishers. Ensure that your Tag scanner has some defenses in place for you, if not consider another vendor.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;4. Don't take candy from strangers: &lt;/b&gt;Never ever download anything from a Tag that you are not confident is from a legitimate publisher. Some Tags offer free downloads. Avoid the instant gratification and do some research. Have others downloaded this product? Are they happy? Do your malware detection systems know anything about this?&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;5. No details, no scan: &lt;/b&gt;It is considered a poor practice by mobile marketers to not describe what a Tag will do. Keeping this in mind, do not scan anything that does not tell you explicitly what the Tag will do. If the Tag veers from the description in any way be wary and refer to #4. Marketing people want to encourage you to follow the tag, they know that surprises can lead to confusion and disengagement. Expect an overload of details. If they are not provided, don't scan.&lt;br /&gt;
&lt;br /&gt;
Notice these are mostly user education things and not technology solutions. Just like any other scam, an educated user is your best defense. Tagging is an amazing technology that can empower business but users need to be aware of the risks just like in the early days of email and the web. So read my article in Hakin9 on Mobile Security called &lt;a href="http://hakin9.org/hakin9-mobile-112-2/" target="_blank"&gt;Tag: You're infected!&lt;/a&gt; and let me know what you think.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://3.bp.blogspot.com/-eLX7GRiNtAI/TwuxAnpmMJI/AAAAAAAAAMU/biSmpSCImJw/s1600/qrcode.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" src="http://3.bp.blogspot.com/-eLX7GRiNtAI/TwuxAnpmMJI/AAAAAAAAAMU/biSmpSCImJw/s1600/qrcode.png" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Never scan a QR Code you do not know&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-7864521343262300353?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/zmH-PvLbHOhP3yZG0ms1dRn8r-4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/zmH-PvLbHOhP3yZG0ms1dRn8r-4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/zmH-PvLbHOhP3yZG0ms1dRn8r-4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/zmH-PvLbHOhP3yZG0ms1dRn8r-4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/8drWtoaDRzA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/7864521343262300353/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=7864521343262300353" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/7864521343262300353?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/7864521343262300353?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/8drWtoaDRzA/continued-discussion-qr-tags-and.html" title="Continued discussion: QR Tags and Security" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-1WmGvieDjjo/TwuscL97JGI/AAAAAAAAAMM/_3NUexRES7Y/s72-c/qr+tag+sample.png" height="72" width="72" /><thr:total>0</thr:total><georss:featurename>Baltimore, MD, USA</georss:featurename><georss:point>39.2903848 -76.6121893</georss:point><georss:box>39.1920723 -76.7701178 39.3886973 -76.4542608</georss:box><feedburner:origLink>http://seccode.blogspot.com/2012/01/continued-discussion-qr-tags-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak8MQn86eSp7ImA9WhRWFUg.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-6349893467243427623</id><published>2012-01-02T18:37:00.000-08:00</published><updated>2012-01-02T18:48:03.111-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-02T18:48:03.111-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="filler" /><category scheme="http://www.blogger.com/atom/ns#" term="Channel 9" /><category scheme="http://www.blogger.com/atom/ns#" term="Ireland" /><category scheme="http://www.blogger.com/atom/ns#" term="food" /><title>Finding a addictive burger in Dublin</title><content type="html">I've been trying to write something interesting (or at least some what interesting) each week. Recently I realized that I have had this blog for a long time but have been horrible at maintaining the content on it. No it is not a 2012 resolution to write more but a dedication to becoming a better writer through actually writing more.&lt;br /&gt;
&lt;br /&gt;
To this end, today is a filler day. This is when I do not have something (i.e. a project) that I am ready to write about and will just talk about my thoughts or post a picture. Tonight being the second day of 2012 I wanted to post a picture from a trip I took with my wife almost 4 years ago now. We hopped around northern Europe hitting Ireland, Norway and Iceland. The trip was a blast and forever changed my world view. Being a foodie, two things really made the trip wonderful: great food and memorable locations. Here are a few pictures from my favorite burger joint in the world (even though it is not a burger joint) &lt;a href="http://www.thesmithgroup.ie/aulddubliner/index.html" target="_blank"&gt;The Auld Dubliner&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
We stumbled on to this place after walking around St. Steven's Green and Grafton Street. I wanted a good Jameson and my wife wanted a good Guinness. We found much more in this little gem. The decor was amazing, the staff were like family and the food embedded a craving in my belly that only an Auld Dubliner burger could&amp;nbsp;quench. If you are in Dublin, Ireland and looking for a&amp;nbsp;tasty&amp;nbsp;burger with a good Jameson, head straight over to the Auld Dubliner and grab one for me.&lt;br /&gt;
&lt;br /&gt;
Enjoy!&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-_6-S6BabsBA/TwJqDfjYyJI/AAAAAAAAALs/oKq98yjmL9k/s1600/089.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="240" src="http://4.bp.blogspot.com/-_6-S6BabsBA/TwJqDfjYyJI/AAAAAAAAALs/oKq98yjmL9k/s320/089.JPG" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-ABFE7XrzgYc/TwJqD_wcCzI/AAAAAAAAAL0/9uQhyA6OkUg/s1600/091.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="320" src="http://1.bp.blogspot.com/-ABFE7XrzgYc/TwJqD_wcCzI/AAAAAAAAAL0/9uQhyA6OkUg/s320/091.JPG" width="240" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-THzmO9oDFFo/TwJqEW6iftI/AAAAAAAAAL8/2D_Xl9v6YgM/s1600/092.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="320" src="http://4.bp.blogspot.com/-THzmO9oDFFo/TwJqEW6iftI/AAAAAAAAAL8/2D_Xl9v6YgM/s320/092.JPG" width="240" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-1bTD4ndNpSM/TwJqE_QrVyI/AAAAAAAAAME/_xDrD9-dq4o/s1600/093.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="240" src="http://1.bp.blogspot.com/-1bTD4ndNpSM/TwJqE_QrVyI/AAAAAAAAAME/_xDrD9-dq4o/s320/093.JPG" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-6349893467243427623?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/B4ZdHlc--Uu8d57abrrH9IGFMYo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/B4ZdHlc--Uu8d57abrrH9IGFMYo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/B4ZdHlc--Uu8d57abrrH9IGFMYo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/B4ZdHlc--Uu8d57abrrH9IGFMYo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/Soqd01edzCE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/6349893467243427623/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=6349893467243427623" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/6349893467243427623?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/6349893467243427623?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/Soqd01edzCE/finding-addictive-burger-in-dublin.html" title="Finding a addictive burger in Dublin" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-_6-S6BabsBA/TwJqDfjYyJI/AAAAAAAAALs/oKq98yjmL9k/s72-c/089.JPG" height="72" width="72" /><thr:total>1</thr:total><georss:featurename>Adair Ln, Ranelagh, Dublin, Co. Dublin, Ireland</georss:featurename><georss:point>53.3462264 -6.260288</georss:point><georss:box>53.3438564 -6.2652235 53.3485964 -6.2553525</georss:box><feedburner:origLink>http://seccode.blogspot.com/2012/01/finding-addictive-burger-in-dublin.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IMSH08eCp7ImA9WhRWEkw.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-2167338226615349436</id><published>2011-12-29T19:24:00.000-08:00</published><updated>2011-12-29T19:26:29.370-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-29T19:26:29.370-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="web development" /><category scheme="http://www.blogger.com/atom/ns#" term="sql injection" /><category scheme="http://www.blogger.com/atom/ns#" term=".net" /><category scheme="http://www.blogger.com/atom/ns#" term="information security" /><category scheme="http://www.blogger.com/atom/ns#" term="code review" /><title>Security Code Review vs. Code Review</title><content type="html">Tomorrow I have a code review to lead, well participate in. I usually lead so tomorrow I really need to focus on listening as it is my code that is being reviewed. Not having written any code in a while I was doubly careful but still know that there are significant issues to be addressed (there always are). In thinking about tomorrows review, I remembered a discussion I had once with a PHP friend who asked what the difference was between a security code review and a regular code review.&lt;br /&gt;
&lt;br /&gt;
The question struck me a bit and made me wonder, what is the difference? Was there a difference? Did someone just tack the word "security" on to make the code review sound more interesting? After a bit of research I came to a conclusion - security was the difference. This is not profound or deep, it is pretty obvious and became more and more obvious as I sat in on many code reviews.&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: large;"&gt;&lt;b&gt;Things that are the same&lt;/b&gt;&lt;/span&gt;&lt;br /&gt;
A code review (security or not) has a core focus: talking about the code. This makes Code Review one of the most important practices to building quality, secure code because it analyzes the one common output from a software project: code. Your review can be as structured or loose fits your environment but you need at least four roles (roles not people):&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;The Author:&lt;/b&gt; The person who wrote the code. They are here to learn and explain when the code cannot explain for them.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;The Reader: &lt;/b&gt;This role reads the code as a narrative to explain to the reviewers what it is doing. This role cannot be held by the author as that will skew the review.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;The Secretary:&lt;/b&gt; The role who records the notes of the meeting. They are also responsible to bring the notes to the team after the meeting.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;The Moderator:&lt;/b&gt; The role who keeps the review positive, productive and actionable. This role also ensures the notes from the review are executed after the review.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
These roles can be held by a single person (except author and reader) which can produce a code review team of 2 people. Sometimes these smaller groups can produce fast results but beware of always reviewing with the same people. A fresh perspective is always necessary as two reviewers who always work together could start to overlook issues due to a "oh that is their coding style" type mindset.&lt;br /&gt;
&lt;br /&gt;
Another aspect that is the same is the focus on good design and execution not "how I would have done it". As soon as you hear someone say, "well, I would have..." stop right there. Dig in and find out why it should be done a different way. If there is not a good reason, such as a pre-existing standard, then agree to disagree. Code is art and critics rarely agree on what is good, great or horrible.&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: large;"&gt;&lt;b&gt;Things that are different&lt;/b&gt;&lt;/span&gt;&lt;br /&gt;
In a Security Code Review you want to discuss Attack Patterns. Is the code&amp;nbsp;susceptible&amp;nbsp;to an attack pattern such as injection? Does the code mix the Data Channel and Command/Control Channel (which can lead to injection)? If so, why? Is it necessary? As an example of this, anytime you see:&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote class="tr_bq"&gt;
var sql = "SELECT * FROM tbl WHERE ID = " + id + " "&lt;/blockquote&gt;
&lt;br /&gt;
Ask why! What data type is id and how are you sure that you did not just open a SQL Injection attack vector.&amp;nbsp;An excellent introduction to attack patterns can be found at&amp;nbsp;&lt;a href="https://buildsecurityin.us-cert.gov/bsi/articles/knowledge/attack/585-BSI.html"&gt;https://buildsecurityin.us-cert.gov/bsi/articles/knowledge/attack/585-BSI.html&lt;/a&gt;. Keep a list of attack patterns handy and ask: "Does the code allow this?". Strong knowledge of attack patterns and the &lt;a href="https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project" target="_blank"&gt;OWASP Top Ten&lt;/a&gt; will provide useful input to this section of the security code review.&lt;br /&gt;
&lt;br /&gt;
Another activity is the examination of assumptions. Dig in to each assumption and ask what happens if that assumption is false. For instance, if the code assumes Request.Querystring["ID"] will be an integer (using int.Parse(Request.Querystring["ID"]) or something like that) what happens when it is not? A great thinking strategy for this is the concept of &lt;a href="http://en.wikipedia.org/wiki/Equivalence_partitioning" target="_blank"&gt;Equivalence Partitioning&lt;/a&gt;. Using Equivalence Partitioning, you break down the input into valid and invalid partitions. For our above example, Alpha characters would be an invalid partition. What happens when we encounter ?ID=A in the query string? Beyond assumptions of data type validate assumptions in logic. If the developer believes that ID will always be between 1 and 10, ask why and what happens when the business decides to allow ids between 11 and 20.&lt;br /&gt;
&lt;br /&gt;
There is a lot more to a security code review but these two items will get you started in the right direction. As security becomes a larger focus for developers code reviews will become security code reviews (thus why it is important to focus on security education for your devs). Examining attack patterns and assumptions will enable you to produce more secure code. Just remember to dig deep, return to review often and work as a team to discover the most secure, highest quality solution.&lt;br /&gt;
&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-2167338226615349436?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/22EvlWZnEyIta6R_g7iJbtYHUgQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/22EvlWZnEyIta6R_g7iJbtYHUgQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/22EvlWZnEyIta6R_g7iJbtYHUgQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/22EvlWZnEyIta6R_g7iJbtYHUgQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/U3gVTiX-2MU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/2167338226615349436/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=2167338226615349436" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/2167338226615349436?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/2167338226615349436?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/U3gVTiX-2MU/security-code-review-vs-code-review.html" title="Security Code Review vs. Code Review" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><georss:featurename>Baltimore, MD, USA</georss:featurename><georss:point>39.2903848 -76.6121893</georss:point><georss:box>39.1920723 -76.7701178 39.3886973 -76.4542608</georss:box><feedburner:origLink>http://seccode.blogspot.com/2011/12/security-code-review-vs-code-review.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8ER3o-cSp7ImA9WhRXFk0.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-2923137327183736918</id><published>2011-12-22T18:36:00.000-08:00</published><updated>2011-12-22T18:36:46.459-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-22T18:36:46.459-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="membership provider" /><category scheme="http://www.blogger.com/atom/ns#" term="asp.net" /><category scheme="http://www.blogger.com/atom/ns#" term="ajax" /><category scheme="http://www.blogger.com/atom/ns#" term="authentication" /><category scheme="http://www.blogger.com/atom/ns#" term="jquery mobile" /><category scheme="http://www.blogger.com/atom/ns#" term="jQuery" /><title>My first jQuery Mobile application</title><content type="html">For the past two weeks I have been working on a jQuery Mobile application (http://www.jquerymobile.com). I have been extremely impressed with the capabilities and simplicity of the API. Being familiar with jQuery and jQuery UI the basics were easy to pick up but there have been a few challenges that I encountered as an ASP.NET WebForms developer.&amp;nbsp;&amp;nbsp;One such challenge was implementing the Membership Provider and Role Provider with jQuery Mobile (being that it has some challenges with Postbacks [ &lt;a href="http://forum.jquery.com/jquery-mobile/search/postback"&gt;http://forum.jquery.com/jquery-mobile/search/postback&lt;/a&gt;]).&lt;br /&gt;
&lt;h2&gt;Why jQuery Mobile?&lt;/h2&gt;For this project I needed to build a mobile application that would render the same on multiple device platforms (and gracefully degrade if necessary). jQuery Mobile has excellent cross-device support (&lt;a href="http://jquerymobile.com/gbs/"&gt;http://jquerymobile.com/gbs/&lt;/a&gt;) and leverages my pre-existing jQuery skill set. Also, I like web applications. I like JavaScript :) and really enjoy working with jQuery.&lt;br /&gt;
&lt;h2&gt;Why Web Forms?&amp;nbsp;&lt;/h2&gt;Yes, ASP.NET MVC is awesome and yes I do want to move in that direction but again, my skill set has been Web Forms and I did not want to side track my jQuery Mobile project with learning MVC as well. Over the holiday I will be dedicating some time to MVC but for now, I needed to stick to Web Forms.&lt;br /&gt;
&lt;h2&gt;Bridging the Gap&lt;/h2&gt;To bridge between ASP.NET and jQuery Mobile I used the Microsoft Ajax Library. In my mobile application jQuery controls the interface and client side actions. ASP.NET is used to decide what to render to the client based on security and business logic rules. When I need to bridge the two, I cannot use jQuery Mobile to do Postbacks, but can use the Microsoft Ajax Library (included by default in ASP.NET 3.5 and above) to interact with server components. When it came to leveraging my custom Membership Provider, the Microsoft Ajax Library had pre-built components ready to use for this task. Enabling and interacting with them was very easy.&lt;br /&gt;
&lt;h2&gt;Implementing Membership Provider login with jQuery Mobile&lt;/h2&gt;&lt;h3&gt;Step 1: Implement the Membership Provider for your Web Forms application&lt;/h3&gt;I will not go through the details on this as it has been documented on many other sources such as&amp;nbsp;&lt;a href="http://www.asp.net/web-forms/overview/security"&gt;http://www.asp.net/web-forms/overview/security&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a href="http://hakin9.org/flexible-access-online-asp-net%E2%80%99s-access-control-for-the-web/"&gt;http://hakin9.org/flexible-access-online-asp-net%E2%80%99s-access-control-for-the-web/&lt;/a&gt;. Follow those links for directions on how to setup the Membership Provider for your site.&lt;br /&gt;
&lt;h3&gt;Step 2: Setup web.config to enable the Authentication service&lt;/h3&gt;To use the client side authentication functions you must first enable the service that will be used to process the authentication. To do this you must add (or uncomment) the following block of code:&lt;br /&gt;
&lt;blockquote&gt;&lt;div&gt;&amp;lt;system.web.extensions&amp;gt;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;lt;scripting&amp;gt;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;webservices&amp;gt;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;authenticationservice enabled="true" requiressl="true"&amp;gt;&amp;lt;/authenticationservice&amp;gt;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/webservices&amp;gt;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;lt;/scripting&amp;gt;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;lt;system.web.extensions&amp;gt;&lt;/div&gt;&lt;/blockquote&gt;&lt;br /&gt;
This will enable the authenticationService (see the middle line enable="true". I have also set this to require SSL in transmitting the credentials. This is good practice so that you do not expose a user's credentials as clear text over the wire. This configuration setting tells ASP.NET to prepare an .axd web service that will receive your user's credentials.&lt;br /&gt;
&lt;h3&gt;Step 3: Add the Authentication service call&lt;/h3&gt;Once the web.config is prepped, you are ready to call the service in JavaScript. This is easily done by calling:&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;Sys.Services.AuthenticationService.login(&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;username,&amp;nbsp;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;password,&amp;nbsp;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;true,&amp;nbsp;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;"default.aspx",&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;""&amp;nbsp;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;success,&amp;nbsp;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;authFail,&amp;nbsp;&lt;/div&gt;&lt;div&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;null);&lt;/div&gt;&lt;br /&gt;
The first and second parameters to this method are the username and password. In this example I have passed in the variables username and password after they have been passed through input validation/ sanitization. Remember to ALWAYS validate input from the user. The third parameter is a boolean value that states whether or not to persist the user's authentication ticket across browser sessions. &amp;nbsp;Fourth, you can define a redirect URL for the system to send the user to after successful authentication. You could pull this from the web.config using a Response.Write for the argument value or any other technique to inject server values into your client side JavaScript (or write the whole JavaScript on the server). Fifth parameter is to pass in any custom information but this value is not used currently by the system. Next you can define your Success and Failure methods (just like any Ajax call) and finally define the User Context which can be passed along to the success/fail methods.&lt;br /&gt;
&lt;br /&gt;
That is all there is to it. Use the Success method to make decisions about what to do after authentication or just let the system process the user to the redirectURL. Using this bridge between ASP.NET and jQuery Mobile, you can use your existing authentication system in your new mobile app. I will add a code sample in the next few days. For now, I need to sleep :)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-2923137327183736918?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/DIKjqCWrM6kQh0F7Im2FF8VErTs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/DIKjqCWrM6kQh0F7Im2FF8VErTs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/DIKjqCWrM6kQh0F7Im2FF8VErTs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/DIKjqCWrM6kQh0F7Im2FF8VErTs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/21T4C1CDvdQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/2923137327183736918/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=2923137327183736918" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/2923137327183736918?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/2923137327183736918?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/21T4C1CDvdQ/my-first-jquery-mobile-application.html" title="My first jQuery Mobile application" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2011/12/my-first-jquery-mobile-application.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0cFQX8_fSp7ImA9WhRQGE8.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-4332650788407828</id><published>2011-12-13T18:16:00.000-08:00</published><updated>2011-12-13T18:16:50.145-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-13T18:16:50.145-08:00</app:edited><title>The Genie and the Bottle</title><content type="html">I've been seeing a lot of people writing lately about the Stop Online Piracy Act (SOPA) and figured I should find out more about this. Turns out the topic is right up my alley, online law (possibly a future career for me :) ). I went over to Wikipedia to see what everyone agrees that SOPA is and how it will impact the online universe. Without diving deep into the contents, the bill basically attempts to protect copyright material and intellectual property by giving the copyright holder legal action against any site that provides or links to a site that infringes copyright. The subtitle for the bill is:&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-family: DeVinne; font-size: small;"&gt;&lt;span style="font-family: DeVinne; font-size: small;"&gt;&lt;blockquote class="tr_bq"&gt;&lt;span style="font-family: DeVinne; font-size: small;"&gt;&lt;span style="font-family: DeVinne; font-size: small;"&gt;&lt;div align="left"&gt;To promote prosperity, creativity, entrepreneurship, and innovation by&lt;/div&gt;combating the theft of U.S. property, and for other purposes.&lt;/span&gt;&lt;/span&gt;&lt;/blockquote&gt;&lt;br /&gt;
First off, I find reading bills about cyber law fascinating. To me the Internet is a lawless place where law makers attempt to enforce rules on a chaotic machine of knowledge, entertainment and cute kittens. Secondly, I believe that his bill has its heart in the right place. The idea that ideas will drive the future and that we need to protect those ideas is admirable. While reading this bill I noticed the focus on US property only which I guess makes sense for a US legal system but I would think that our interest (humanity in general) is to protect Intellectual Property for all not just watching out own backs. So while I find this topic interesting and the purpose with good intent, I do not believe that this bill would have much effect other than to create problems for search engines.&lt;br /&gt;
&lt;br /&gt;
I'm not a cyber law expert, nor an expert on this particular bill but as I read it my mind keeps thinking about Napster. Not the Napster of today but the Napster I grew up with; a feeding frenzy of free content that people used constantly to grow their music collection, software and video libraries. I remember talking with my brother about this world of free content built by Napster and the impact of the Metallica lawsuit. He said something to the effect of: "The genie is out of the bottle and the record companies cannot put it back." SOPA is another attempt to put the genie back in the bottle but I am not sure how this would help unless the site was discoverable or known. Maybe Google/Paypal encounter infringing sites often enough to make SOPA successful but to me this is more about trying to control the wild wild web. With broadband capabilities and shrinking file sizes content can be shared fast and free. &lt;br /&gt;
&lt;br /&gt;
I do believe we need some help protecting the products of creative minds online but I'm not sure how we can do that. SOPA is a well intentioned (it seems) attempt to protect US based creators but how else could we do this? Do we needs police or a neighborhood watch?&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-4332650788407828?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/JFUOcHeG1HME0PG4uK5ZRD8SFH8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/JFUOcHeG1HME0PG4uK5ZRD8SFH8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/JFUOcHeG1HME0PG4uK5ZRD8SFH8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/JFUOcHeG1HME0PG4uK5ZRD8SFH8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/UQzdNds0qq4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/4332650788407828/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=4332650788407828" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4332650788407828?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4332650788407828?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/UQzdNds0qq4/genie-and-bottle.html" title="The Genie and the Bottle" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2011/12/genie-and-bottle.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4MRHc8eSp7ImA9WhdSEU8.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-3111375686808320402</id><published>2011-07-19T17:49:00.000-07:00</published><updated>2011-07-19T17:49:45.971-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-19T17:49:45.971-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="software" /><title>Forensically sound</title><content type="html">I recently took a Digital Forensics class as part of my graduate school program. In the class we discussed "Forensically Sound" systems. These are applications that have been tested and verified by the forensic community to ensure that their "evidence" is lock-solid in court. Knowing the rigors that some software goes through I had to really scratch my head over this one: &lt;span style="font-size: 11pt;"&gt;&lt;span style="font-family: Calibri;"&gt;&lt;a href="http://www.nytimes.com/2011/07/19/us/19casey.html?_r=1&amp;amp;ref=us"&gt;http://www.nytimes.com/2011/07/19/us/19casey.html?_r=1&amp;amp;ref=us&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: 11pt;"&gt;&lt;span style="font-family: Calibri;"&gt;Seems as though the designer/developers of CacheBack found some issues in their code after it was used in&amp;nbsp;a recent&amp;nbsp;media drenched trial. Reading this article made me wonder a few questions:&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;&lt;span style="font-size: 11pt;"&gt;&lt;span style="font-family: Calibri;"&gt;What kind of error makes something appear 84 times when it actually only appeared once? This is more a curious developer question because I like to know how things work.&lt;/span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Is there some kind of test or standards that systems have to meet to be used in investigations? If so, what happened here? &lt;/li&gt;
&lt;li&gt;How does this issue affect previous cases where the software was used? Do all trials where the software was used get called into question?&lt;/li&gt;
&lt;/ul&gt;For a project in my forensics class I built a forensic analysis tool. It was a data mining application. I would never put it out for use by a company or investigation team. This tool was built by just me, reviewed by me and I'm the only one saying it works. I feel sorry for the developer of this tool because it is a bummer to find bugs, even more so when they are so public. The article reminds me to focus my efforts on proactive bug discovery using code reviews and static analysis.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-3111375686808320402?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/eqwfMRvF_FYjSirSDllUIk762DM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/eqwfMRvF_FYjSirSDllUIk762DM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/eqwfMRvF_FYjSirSDllUIk762DM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/eqwfMRvF_FYjSirSDllUIk762DM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/QjsQTu3p3_o" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/3111375686808320402/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=3111375686808320402" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/3111375686808320402?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/3111375686808320402?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/QjsQTu3p3_o/forensically-sound.html" title="Forensically sound" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2011/07/forensically-sound.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUAFQn8yeip7ImA9WhdSEE4.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-6758952040978017957</id><published>2011-07-18T18:08:00.000-07:00</published><updated>2011-07-18T18:08:33.192-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-18T18:08:33.192-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="web development" /><category scheme="http://www.blogger.com/atom/ns#" term="application security" /><category scheme="http://www.blogger.com/atom/ns#" term="software" /><title>Application Security: The view is better but still bleak</title><content type="html">As a development manager it is enough of a challenge to deliver applications on time and under budget. With the growing threats to web applications we need to build secure applicatons on time and under budget. That makes things a bit more complicated. While it is necessary to be proactive in security (because reactive security [i.e. Patch Tuesday]) is not working) via building security in to our software. Unfortunately, many are putting in the investment to do so as this new report from Forrester illustrates: &lt;a href="http://blogs.msdn.com/b/sdl/archive/2011/07/12/application-security-2011-amp-beyond-a-forrester-research-report.aspx"&gt;http://blogs.msdn.com/b/sdl/archive/2011/07/12/application-security-2011-amp-beyond-a-forrester-research-report.aspx&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
This report shows that while people see&amp;nbsp;software security as important, they choose to spend their money elsewhere. How can we show that software security is a true long term fix? Is there an equation to illustrate revenue? Will there ever come a day when software security is held as a requirement to software projects like the structural stability of a bridge? &lt;br /&gt;
&lt;br /&gt;
I thought this report illustrates many interesting points about spending and how to position software security for investment in YOUR organization.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-6758952040978017957?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/wiOmenJUsOd7PwoFDOM7nAfjhM8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/wiOmenJUsOd7PwoFDOM7nAfjhM8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/wiOmenJUsOd7PwoFDOM7nAfjhM8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/wiOmenJUsOd7PwoFDOM7nAfjhM8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/CuqGCmfcZN4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/6758952040978017957/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=6758952040978017957" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/6758952040978017957?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/6758952040978017957?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/CuqGCmfcZN4/application-security-view-is-better-but.html" title="Application Security: The view is better but still bleak" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2011/07/application-security-view-is-better-but.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0ANQ3w9fyp7ImA9WhZbFkw.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-5765040420049248293</id><published>2011-06-20T17:23:00.000-07:00</published><updated>2011-06-20T17:23:12.267-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-20T17:23:12.267-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="stupid human tricks" /><category scheme="http://www.blogger.com/atom/ns#" term="information security" /><title>Marketing people consult with InfoSec prior to a stunt like this...</title><content type="html">I saw this on MSN first then on Sophos' Naked Security but both articles made me scratch my head a bit. BeautifulPeople.com is claiming that a virus permitted 30,000 ugly people to register on their site. The website's schtick is that only attractive people (rated by your peers) are permitted on the site to setup dates with other attractive people. Security professionals like Graham Cluley of Sophos are suspicious that this is simply a media stunt. (&lt;a href="http://nakedsecurity.sophos.com/2011/06/20/beautifulpeople-dupes-mediashrek-virus-media-stunt/"&gt;http://nakedsecurity.sophos.com/2011/06/20/beautifulpeople-dupes-mediashrek-virus-media-stunt/&lt;/a&gt;)&lt;br /&gt;
&lt;br /&gt;
If I were the information security person at BeautifulPeople.com, I would think I would turn in my notice right now. This stunts seems to be begging for a hacker group to tear into them. I don't think drawing attention to your organization's security (or lack there of) is&amp;nbsp;a wise idea in the current security landscape. The claim that a disgruntled developer loaded the virus in the system. This tells me that BeautifulPeople.com do not have adequate change management controls which are a foundation of keeping your production servers clean and functional. If you do not have change management in place, then there are probably some higher level security controls lacking as well.&lt;br /&gt;
&lt;br /&gt;
While I am betting the whole thing is a hoax, I am curious to see who has the last laugh. I'm going to guess that BeautifulPeople.com just painted a target on their site and stay tuned to see when an "ugly" hacker takes the company down.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-5765040420049248293?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/gn3eXz9WYXGrrUMiZfn2fbB-t08/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/gn3eXz9WYXGrrUMiZfn2fbB-t08/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/gn3eXz9WYXGrrUMiZfn2fbB-t08/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/gn3eXz9WYXGrrUMiZfn2fbB-t08/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/g1littkKB6M" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/5765040420049248293/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=5765040420049248293" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/5765040420049248293?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/5765040420049248293?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/g1littkKB6M/marketing-people-consult-with-infosec.html" title="Marketing people consult with InfoSec prior to a stunt like this..." /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2011/06/marketing-people-consult-with-infosec.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEQFSHg8fyp7ImA9WhZUF0g.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-4127300348727073186</id><published>2011-06-10T18:38:00.000-07:00</published><updated>2011-06-10T18:38:39.677-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-10T18:38:39.677-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="social networking" /><category scheme="http://www.blogger.com/atom/ns#" term="social engineer" /><category scheme="http://www.blogger.com/atom/ns#" term="hack" /><title>What's your royal wedding guest name?</title><content type="html">&lt;blockquote&gt;Start with Lord or Lady and the first name of one of your grandparents. Add a double-barreled, hyphenated combo surname consisting of the name of your first pet and the street you lived on as a child.&lt;/blockquote&gt;Does this sound like something that you would fill out? Are you trying to figure out your royal name? Are you sure this fun filled questionnaire is about your royal name or harvesting personal information?&lt;br /&gt;
Look again at the second question:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;consisting of the name of your first pet&lt;/li&gt;
&lt;li&gt;and the street you lived on as a child&lt;/li&gt;
&lt;/ul&gt;These two questions are common questions for password recovery controls. While you are having fun concocting your royal name, someone is collecting a lot of information that can be used to pose as you online. In the past I have filled out many surveys to determine which superhero I would be or which Lord of the Rings character I most identify with but never had I seen a survey directly ask questions that other sites use to secure your account.&lt;br /&gt;
&lt;br /&gt;
While these questions jumped out at my wife (I have programmed her well :) ), many users would probably not connect the dots. This is a great example of a point I make when discussing Social Networking/Media security: Keep your eye on the aggregate! Providing answers to these questions by themselves might not be a security issue but when combined with all the other data you put out into the Social Web it can be easy to have a compromised account. &lt;br /&gt;
&lt;br /&gt;
As an example, suppose that I did fill out the royal name survey. When I fill out the survey and give the application (the Royal Name survey) application permission to my Profile, the application can access a lot of information from my Profile. From this information, an attacker can piece together a usage profile based on information you have provided Facebook. If I have an obvious like such as "Watching Netflix with my wife" then the attacker could try to access my Netflix account. What if they adjust my queues? That is a light hearted example but you get the point.&lt;br /&gt;
&lt;br /&gt;
Playing on Facebook and other social media/networking sites can be fun but keep in mind what you are actually doing. Watch out for surveys that collect a little too much information and ALWAYS be mindful of the aggregate. Think about everything you are putting out to the Social Web and if your individual data points can tell more of a story than you really want strangers to know.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-4127300348727073186?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/M5j1JhreJ23XXuJ5Ive6wakncgQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/M5j1JhreJ23XXuJ5Ive6wakncgQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/M5j1JhreJ23XXuJ5Ive6wakncgQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/M5j1JhreJ23XXuJ5Ive6wakncgQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/o6HLdzy7w8Y" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/4127300348727073186/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=4127300348727073186" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4127300348727073186?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4127300348727073186?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/o6HLdzy7w8Y/whats-your-royal-wedding-guest-name.html" title="What's your royal wedding guest name?" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2011/06/whats-your-royal-wedding-guest-name.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUUGQXc4fCp7ImA9WhZTE0w.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-2465815689195452589</id><published>2011-03-16T16:13:00.000-07:00</published><updated>2011-03-16T16:13:40.934-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-16T16:13:40.934-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="javascript" /><category scheme="http://www.blogger.com/atom/ns#" term="web development" /><category scheme="http://www.blogger.com/atom/ns#" term="jQuery" /><title>Newest publication! ScriptJunkies and jQuery</title><content type="html">I just had a new article published over at &lt;a href="http://msdn.microsoft.com/en-us/scriptjunkie/gg715549.aspx"&gt;ScriptJunkies&lt;/a&gt;. For those not familiar, ScriptJunkies is a client side development site that focuses on HTML, CSS and JavaScript. If you are a web developer you need to get over to the site right away and read on of the many articles they have on improving your JavaScript, designing with HTML5 or CSS3. &lt;br /&gt;
&lt;br /&gt;
My article is about Data Binding with jQuery. The article explores two plugins, $.tmpl and $.fn.DataBinder. &lt;a href="http://weblogs.asp.net/scottgu/archive/2010/10/04/jquery-templates-data-link-and-globalization-accepted-as-official-jquery-plugins.aspx"&gt;$.tmpl&lt;/a&gt;&amp;nbsp;is a jQuery plugin that allows the developers to bind data to a template. The data is JSON but could be anything with a bit of tweaking. &lt;a href="http://bit.ly/fDmVTZ"&gt;$.fn.DataBinder&lt;/a&gt; is&amp;nbsp;a plugin that my development team at MEDEX Global Solutions and I cooked up to do some standard tasks such as sorting, searching and paging the data. The plugins are easy to use and snap in pretty simply. &lt;br /&gt;
&lt;br /&gt;
Let me know what you think about the article and if you have any questions on implementation, don't hesitate to post.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-2465815689195452589?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/huctqe90OwSEkr_bHmpqI28pfQM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/huctqe90OwSEkr_bHmpqI28pfQM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/huctqe90OwSEkr_bHmpqI28pfQM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/huctqe90OwSEkr_bHmpqI28pfQM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/Ic7XbYMFFUg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/2465815689195452589/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=2465815689195452589" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/2465815689195452589?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/2465815689195452589?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/Ic7XbYMFFUg/newest-publication-scriptjunkies-and.html" title="Newest publication! ScriptJunkies and jQuery" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://seccode.blogspot.com/2011/03/newest-publication-scriptjunkies-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkUGQH4-cCp7ImA9Wx5TFU4.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-5962033024911659775</id><published>2010-07-30T17:54:00.000-07:00</published><updated>2010-07-30T18:03:41.058-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-30T18:03:41.058-07:00</app:edited><title>Twitter's case for growth</title><content type="html">Yeah I know this is a bit old, but I thought this was an interesting. As I understand, Twitter's challenge is in having their systems flooded with traffic yet they are not looking at a cloud solution.&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;"Twitter will have full control over network and systems configuration, with a much larger footprint in a building designed specifically around our unique power and cooling needs," the company's engineering blog noted. "Importantly, having our own data center will give us the flexibility to more quickly make adjustments as our infrastructure needs change.&lt;/blockquote&gt;&lt;br /&gt;
While this is all well and good, I have to wonder if keeping the infrastructure in house is a wise decision. There description sounds exactly like why you want to use a cloud facility such as Windows Azure or Amazon Cloud. For those who do not know, using a cloud server system allows the client (in this case Twitter) to be agile in the number of servers they use. Cloud facilities also do some pretty amazing stuff with HVAC to keep the facility cool and thus, the servers functioning. So if a cloud service will take care of their business requirements without having the overhead of hardware, why wouldn't they go with a cloud solution? &lt;br /&gt;
&lt;br /&gt;
On the other hand, you do lose control with a cloud. Keeping the system in-house will allow Twitter to have complete control over what is on the servers and who is accessing them. Administrative functions will also be able to stay in-house keeping Twitter in the know as to who is fixing their systems and building maintenance schedules.&lt;br /&gt;
&lt;br /&gt;
What do you think, should Twitter go cloud?&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://news.cnet.com/8301-13577_3-20011315-36.html?tag=mncol;title"&gt;http://news.cnet.com/8301-13577_3-20011315-36.html?tag=mncol;title&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-5962033024911659775?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ssIGAceoIa4iyr-618rZooov6Rc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ssIGAceoIa4iyr-618rZooov6Rc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ssIGAceoIa4iyr-618rZooov6Rc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ssIGAceoIa4iyr-618rZooov6Rc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/mRQyzH-itEE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/5962033024911659775/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=5962033024911659775" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/5962033024911659775?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/5962033024911659775?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/mRQyzH-itEE/twitters-case-for-growth.html" title="Twitter's case for growth" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/twitters-case-for-growth.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0MCSHszeCp7ImA9WxFaFU0.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-5994636894285589315</id><published>2010-07-18T18:04:00.000-07:00</published><updated>2010-07-18T18:04:29.580-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-18T18:04:29.580-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="html 5" /><category scheme="http://www.blogger.com/atom/ns#" term="information security" /><category scheme="http://www.blogger.com/atom/ns#" term="css 3" /><title>HTML 5 and CSS 3: New attack vectors</title><content type="html">My friend at work/designing guru Clint expounds on the qualities of HTML 5 and CSS 3. He makes the combo sound like the second coming in web design and maybe they are...but to me new technology = new threats. Around rounded corners and less javascript really worth opening a new pandora's box?&lt;br /&gt;
&lt;br /&gt;
Recently SecureIdeas posted this link on Twitter that has a great exploit to do an XSS attack via HTML5's new features. &lt;a href="http://bit.ly/bYMzLR"&gt;http://bit.ly/bYMzLR&lt;/a&gt; &lt;br /&gt;
&lt;br /&gt;
If you are not following &lt;a href="http://twitter.com/secureideas"&gt;@secureideas&lt;/a&gt; and you are into Information Security then get with that twit-feed :) They provide great resources and I've learned a lot from their 140 characters.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-5994636894285589315?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/pEJN-rCHL_r4MJBdtounfU00WXQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/pEJN-rCHL_r4MJBdtounfU00WXQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/pEJN-rCHL_r4MJBdtounfU00WXQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/pEJN-rCHL_r4MJBdtounfU00WXQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/ENidXTCSlRA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/5994636894285589315/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=5994636894285589315" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/5994636894285589315?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/5994636894285589315?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/ENidXTCSlRA/html-5-and-css-3-new-attack-vectors.html" title="HTML 5 and CSS 3: New attack vectors" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/html-5-and-css-3-new-attack-vectors.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0AFR3s_eCp7ImA9WxFaEkk.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-4147010144764606136</id><published>2010-07-15T19:01:00.000-07:00</published><updated>2010-07-15T19:01:56.540-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-15T19:01:56.540-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="social networking" /><category scheme="http://www.blogger.com/atom/ns#" term="policy" /><category scheme="http://www.blogger.com/atom/ns#" term="information security" /><title>Social Media Metrics</title><content type="html">It seems like every company is building a social media strategy, but measuring success can be very subjective. Last night I found this excellent article on Social Media Today that explores "6 Social Media Metrics You Should be Tracking". The article is brief yet provides great information. &lt;br /&gt;
The article examines 3 measurements:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Activity: What are people doing on your social media site?&lt;/li&gt;
&lt;li&gt;Interaction: How well does your audience interact with you?&lt;/li&gt;
&lt;li&gt;Returns: How do your social media activities support your organization's success?&lt;/li&gt;
&lt;/ul&gt;Just like an Economic Feasibility study, you measure each of these items from two mindsets - Quantitative &amp;amp; Qualitative. Quantitative being numeric, Qualitative being more generic/general. An example of a Quantitative Measure would be # of Posts (an example of Activity) because this can be counted and measured. More posts, more value to the client. An example of Qualitative would be Comments, showing that users are engaged in your activity. Mapping these two measuring methodologies provide the following matrix:&lt;br /&gt;
&lt;br /&gt;
&lt;table border="1" cellpadding="3" cellspacing="2"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Quantitative&lt;/td&gt;&lt;td&gt;Qualitative&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Activity&lt;/td&gt;&lt;td&gt;&lt;ul&gt;&lt;li&gt;# of Posts&lt;/li&gt;
&lt;li&gt;Update Frequency&lt;/li&gt;
&lt;/ul&gt;&lt;/td&gt;&lt;td&gt;&lt;ul&gt;&lt;li&gt;Comments&lt;/li&gt;
&lt;/ul&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Interactivity&lt;/td&gt;&lt;td&gt;&lt;ul&gt;&lt;li&gt;# of Comments&lt;/li&gt;
&lt;li&gt;# of Followers/Fans&lt;/li&gt;
&lt;li&gt;# of Views&lt;/li&gt;
&lt;li&gt;Amount of user content&lt;/li&gt;
&lt;/ul&gt;&lt;/td&gt;&lt;td&gt;&lt;ul&gt;&lt;li&gt;Customer Sentiment&lt;/li&gt;
&lt;li&gt;&lt;span class="goog-spellcheck-word"&gt;Learnings&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Buzz&lt;/li&gt;
&lt;/ul&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Returns&lt;/td&gt;&lt;td&gt;&lt;ul&gt;&lt;li&gt;# of Leads&lt;/li&gt;
&lt;li&gt;# of Sales&lt;/li&gt;
&lt;/ul&gt;&lt;/td&gt;&lt;td&gt;&lt;ul&gt;&lt;li&gt;Success stories&lt;/li&gt;
&lt;li&gt;&lt;span class="goog-spellcheck-word"&gt;Learnings&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;
These items are the examples from the Social Media Today article. These metrics are a key starting point for any business' social media strategy. Any business process should support the business some how, these metrics allow marketing staff to point to metrics for success.&lt;br /&gt;
&lt;br /&gt;
What does this mean for security? As marketing can begin proving that social media is not only a valuable business initiative but critical to the continuity of effective marketing. Simply blocking social media and social networking sites will not be a sustainable answer. As Information Security professionals, we must enable business while ensuring the security of the organization. So...what are you doing for social media policy? Let me know your thoughts on Social Media Security Policy. If you need a spark of inspiration, here are some samples.&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="http://www.sun.com/communities/guidelines.jsp"&gt;Oracle&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.intel.com/sites/sitewide/en_US/social-media.htm"&gt;Intel&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://fastlane.gmblogs.com/about.html"&gt;GM&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://blogs.law.harvard.edu/terms-of-use/"&gt;Harvard&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;Social Media Today Article: &lt;a href="http://socialmediatoday.com/mikebrown1/146589/6-social-media-metrics-you-should-be-tracking/"&gt;http://&lt;span class="goog-spellcheck-word"&gt;socialmediatoday&lt;/span&gt;.com/mikebrown1/146589/6-social-media-metrics-you-should-be-tracking/&lt;/a&gt;&lt;br /&gt;
Sample Social Media Policies: &lt;a href="http://www.csoonline.com/article/596966/sample-social-media-and-blogging-policies-from-other-sites"&gt;http://www.&lt;span class="goog-spellcheck-word"&gt;csoonline&lt;/span&gt;.com/article/596966/sample-social-media-and-blogging-policies-from-other-sites-&lt;/a&gt;&lt;br /&gt;
&lt;table style="background: black;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td width="140"&gt;&lt;iframe align="left" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" src="http://rcm.amazon.com/e/cm?t=seccode20&amp;amp;o=1&amp;amp;p=8&amp;amp;l=bpl&amp;amp;asins=0596806604&amp;amp;fc1=FFFFFF&amp;amp;IS2=1&amp;amp;lt1=_blank&amp;amp;m=amazon&amp;amp;lc1=8181FF&amp;amp;bc1=000000&amp;amp;bg1=000000&amp;amp;f=ifr" style="align: left; height: 245px; padding-right: 10px; padding-top: 5px; width: 131px;"&gt;&lt;/iframe&gt;&lt;/td&gt;&lt;td width="140"&gt;&lt;iframe align="left" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" src="http://rcm.amazon.com/e/cm?t=seccode20&amp;amp;o=1&amp;amp;p=8&amp;amp;l=bpl&amp;amp;asins=0470289341&amp;amp;fc1=FFFFFF&amp;amp;IS2=1&amp;amp;lt1=_blank&amp;amp;m=amazon&amp;amp;lc1=8181FF&amp;amp;bc1=000000&amp;amp;bg1=000000&amp;amp;f=ifr" style="align: left; height: 245px; padding-right: 10px; padding-top: 5px; width: 131px;"&gt;&lt;/iframe&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-4147010144764606136?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/vhivAEFibu2otLn6gTfJfwcnTG4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/vhivAEFibu2otLn6gTfJfwcnTG4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/vhivAEFibu2otLn6gTfJfwcnTG4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/vhivAEFibu2otLn6gTfJfwcnTG4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/4-bErx8frJ0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/4147010144764606136/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=4147010144764606136" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4147010144764606136?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4147010144764606136?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/4-bErx8frJ0/social-media-metrics.html" title="Social Media Metrics" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/social-media-metrics.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8DRX8_fCp7ImA9WxFaEEo.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-6459436976832282929</id><published>2010-07-13T19:34:00.000-07:00</published><updated>2010-07-13T19:34:34.144-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-13T19:34:34.144-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="social networking" /><category scheme="http://www.blogger.com/atom/ns#" term="computer forensics" /><category scheme="http://www.blogger.com/atom/ns#" term="information security" /><title>Social Media Forensics</title><content type="html">I just finished watching a web presentation about social media forensics, or the collection of evidence through social media. This evidence could be used for legal purposes (which was the primary focus of the presentation) or can be simply collecting information about people. The presentation was very interesting because it discussed some topics that I have recently been thinking about in a more concrete, example way.&amp;nbsp;I also found some of the tracking methodologies discussed interesting such as using Web Analytics data to identify a user who is trying to subvert detection via an Anonymizer (software that bounces your identity around the Internet to make it harder to track). &lt;br /&gt;
&lt;br /&gt;
One example of evidence they gave was the blog posts of a lady who committed suicide. Her family claimed that the suicide was a result of medication that she was on. The pharma company tracked down blog posts that linked her suicide to a deeper (predating the medication usage) problem which exonerated the company of the wrongful death suite.This is an interesting use of a blog/social site to illustrate an existing condition, as if the dead were to speak in court.&lt;br /&gt;
&lt;br /&gt;
Another topic was how posts and comments can illustrate character and credibility in a trial. Things people post or show via pictures can tell a lot about an individual's trustworthiness. This also can fall under&amp;nbsp;the Evil Twin (sorry, I promise I won't tie everything back to this) defamation of character topic. Imagine how your character can be destroyed with a fake Facebook profile that is open to the public.&lt;br /&gt;
&lt;br /&gt;
The challenge with using Social Media for evidence is that the content is so dynamic, it can be difficult to use a evidence. With an ever changing and dynamic nature, a page's content can change by the minute. This will require new forensic techniques and technologies to capture what was there and store it in a non-refutable manner.&lt;br /&gt;
&lt;br /&gt;
A few ideas to keep an eye on your social media:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Consider employing your change management policies to Social Media (keep a good record of everything you do on these sites)&lt;/li&gt;
&lt;li&gt;Keep a tight grip on Access Control (if you give out your user name and password...stop doing that!)&lt;/li&gt;
&lt;li&gt;Consider recording everything (screen capture at all times could clear you of wrongful accusations)&lt;/li&gt;
&lt;/ul&gt;Are these realistic for everyone? No, but they can be used in an enterprise. My key take aways from this web presentation - be careful what you post because they are watching with many eyes.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-6459436976832282929?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/YaKhNwTDZF9H0HnfAwRCm2gMcvE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/YaKhNwTDZF9H0HnfAwRCm2gMcvE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/YaKhNwTDZF9H0HnfAwRCm2gMcvE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/YaKhNwTDZF9H0HnfAwRCm2gMcvE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/cBo5oh2yYJo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/6459436976832282929/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=6459436976832282929" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/6459436976832282929?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/6459436976832282929?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/cBo5oh2yYJo/social-media-forensics.html" title="Social Media Forensics" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/social-media-forensics.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU8DQ38_cCp7ImA9WxFbF04.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-2622918643026272131</id><published>2010-07-09T20:51:00.000-07:00</published><updated>2010-07-09T20:51:12.148-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-09T20:51:12.148-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="US government" /><category scheme="http://www.blogger.com/atom/ns#" term="cyber warfare" /><category scheme="http://www.blogger.com/atom/ns#" term="cyber crime" /><title>GAO says OSTP has Fatal System Error</title><content type="html">This week the&amp;nbsp;Government Accountability Office (GAO) released a report stating that the White House Office of Science and Technology Policy has put the United States at risk for falling behind other countries in the area of cybersecurity. The report states that OSTP was tasked with developing a cybersecurity strategy and updating it annually in 2003 and as of yet, has not lived up to their responsibilities. While the report recognizes that OSTP is taking steps to build such a plan, "one does not currently exist", the report said.(1) Check out &lt;a href="http://www.csoonline.com/article/598873/gao-white-house-failing-on-cybersecurity"&gt;http://www.csoonline.com/article/598873/gao-white-house-failing-on-cybersecurity&lt;/a&gt;&amp;nbsp;for more about this story. &lt;br /&gt;
&lt;br /&gt;
This report is quite timely with this month's&lt;a href="http://www.economist.com/"&gt; Economist magazine&lt;/a&gt; focusing on Cyberwar. The article examines how the United States and various other countries are building their cyberwar capabilities for an impending digital battleground. Some people believe that war is already upon us and that the United States is struggling to keep up. The United States has pulled a Microsoft in relation to cyberwar, they are late to the game and trying to catch up (as most governments are). A great example of this is in &lt;span&gt;&lt;a href="http://www.amazon.com/Fatal-System-Error-Bringing-Internet/dp/1586487485?ie=UTF8&amp;amp;tag=seccode20&amp;amp;link_code=btl&amp;amp;camp=213689&amp;amp;creative=392969" target="_blank"&gt;Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet&lt;/a&gt;&lt;img alt="" border="0" height="1" src="http://www.assoc-amazon.com/e/ir?t=seccode20&amp;amp;l=btl&amp;amp;camp=213689&amp;amp;creative=392969&amp;amp;o=1&amp;amp;a=1586487485" style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none; margin: 0px; padding-bottom: 0px !important; padding-left: 0px !important; padding-right: 0px !important; padding-top: 0px !important;" width="1" /&gt;&amp;nbsp;in which the United States is not really sure how to deal with the various layers of cybercrime that the main character is trying to expose.&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;span&gt;For the United States, the military might not be the best defense against cyberwarfare/cyberterrorism, business might be. When you consider how many huge Internet companies are based in the US, the powerful infrastructures they have built and the massive talent pool they employ, can the military keep pace? Who do you think is better prepared for a cyberterrorist attack, US Department of Health and Human Services or Google?&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;span&gt;Let me know your thoughts, should government rely on business for cyberdefense capabilities?&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
(1) &lt;a href="http://www.csoonline.com/article/598873/gao-white-house-failing-on-cybersecurity"&gt;http://www.csoonline.com/article/598873/gao-white-house-failing-on-cybersecurity&lt;/a&gt; by Jaikumar Vijayan&lt;br /&gt;
&lt;br /&gt;
&lt;table&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td&gt;&lt;iframe align="left" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" src="http://rcm.amazon.com/e/cm?t=seccode20&amp;amp;o=1&amp;amp;p=8&amp;amp;l=bpl&amp;amp;asins=1586487485&amp;amp;fc1=FFFFFF&amp;amp;IS2=1&amp;amp;lt1=_blank&amp;amp;m=amazon&amp;amp;lc1=8181FF&amp;amp;bc1=000000&amp;amp;bg1=000000&amp;amp;f=ifr" style="align: left; height: 245px; padding-right: 10px; padding-top: 5px; width: 131px;"&gt;&lt;/iframe&gt;&lt;/td&gt;&lt;td&gt;&lt;iframe align="left" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" src="http://rcm.amazon.com/e/cm?t=seccode20&amp;amp;o=1&amp;amp;p=8&amp;amp;l=bpl&amp;amp;asins=B0027VSU9S&amp;amp;fc1=FFFFFF&amp;amp;IS2=1&amp;amp;lt1=_blank&amp;amp;m=amazon&amp;amp;lc1=8181FF&amp;amp;bc1=000000&amp;amp;bg1=000000&amp;amp;f=ifr" style="align: left; height: 245px; padding-right: 10px; padding-top: 5px; width: 131px;"&gt;&lt;/iframe&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-2622918643026272131?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/wQmotOied7OMi9j3Yh5EXYGDMqU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/wQmotOied7OMi9j3Yh5EXYGDMqU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/wQmotOied7OMi9j3Yh5EXYGDMqU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/wQmotOied7OMi9j3Yh5EXYGDMqU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/-JyjlHX7fzE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/2622918643026272131/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=2622918643026272131" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/2622918643026272131?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/2622918643026272131?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/-JyjlHX7fzE/gao-says-ostp-has-fatal-system-error.html" title="GAO says OSTP has Fatal System Error" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/gao-says-ostp-has-fatal-system-error.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUMGSHw4fSp7ImA9WxFbFkk.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-4365754596302217275</id><published>2010-07-08T19:43:00.000-07:00</published><updated>2010-07-08T19:43:49.235-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-08T19:43:49.235-07:00</app:edited><title>InterSec: Where secure minds meet.</title><content type="html">If you are a memeber of the ISC2 or a security minded professional, head over to: https://isc2intersec.leveragesoftware.com and checkout InterSec. It is a really interesting site with tons of great content. If you're a member, here is my quick connect card. Shoot me a message and we can talk about some collaboration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://isc2intersec.leveragesoftware.com/profile_view.aspx?customerid=70d5a72d8c3a4d639b12eae73fefb126"&gt;&lt;img src="http://isc2intersec.leveragesoftware.com/businesscard.aspx?customerid=70d5a72d8c3a4d639b12eae73fefb126" border="0" alt="Join Me at InterSeC!"&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-4365754596302217275?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/zYGOtd68K72RXUHbVQwzKS4G5KQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/zYGOtd68K72RXUHbVQwzKS4G5KQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/zYGOtd68K72RXUHbVQwzKS4G5KQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/zYGOtd68K72RXUHbVQwzKS4G5KQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/krdQlfpOen8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/4365754596302217275/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=4365754596302217275" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4365754596302217275?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4365754596302217275?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/krdQlfpOen8/intersec-where-secure-minds-meet.html" title="InterSec: Where secure minds meet." /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/intersec-where-secure-minds-meet.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQHQnc5eyp7ImA9WxFbFUg.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-561866330875185575</id><published>2010-07-07T19:32:00.000-07:00</published><updated>2010-07-07T19:48:53.923-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-07T19:48:53.923-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="social networking" /><category scheme="http://www.blogger.com/atom/ns#" term="social engineer" /><category scheme="http://www.blogger.com/atom/ns#" term="Evil Twin" /><title>Evil Twin-ish: Who is Robin Sage</title><content type="html">I follow @secureideas on twitter and saw a posting for this Slashdot article:&lt;br /&gt;
&lt;a href="http://it.slashdot.org/story/10/07/07/1439228/"&gt;http://it.slashdot.org/story/10/07/07/1439228/&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
To sum up, an information security professional created a facebook profile for a Ms. Robin Sage and then commenced connecting to a variety of people. One military connection provided a little too much detail on their facebook photos and gave away their Afghanistan position. Check out the facebook profile here:&lt;br /&gt;
&lt;a href="http://www.facebook.com/robin.sage.641a"&gt;http://www.facebook.com/robin.sage.641a&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
The profile is fairly believable. This is an example of an Evil Twin in the wild. An&amp;nbsp;Evil Twin is a social&amp;nbsp;networking profile that is meant to impersonate another person (usually a real person but not in this instance. that is why this is Evil Twin-ish).&amp;nbsp;From what I'm gathering, this was done by a security professional who will be presenting at the Black Hat conference.I would be that this person did not read my article and that they just figured this out themselves. &lt;br /&gt;
&lt;br /&gt;
For more information about Evil Twin check out:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Previous post (&lt;a href="http://seccode.blogspot.com/2010/07/hakin9-birth-of-evil-twin.html"&gt;http://seccode.blogspot.com/2010/07/hakin9-birth-of-evil-twin.html&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Hakin9 Article about building an Evil Twin (&lt;a href="http://bit.ly/dBzP1J"&gt;http://bit.ly/dBzP1J&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.amazon.com/Deadliest-Social-Network-Attacks-Syngress/dp/159749545X?ie=UTF8&amp;amp;tag=seccode20&amp;amp;link_code=btl&amp;amp;camp=213689&amp;amp;creative=392969" target="_blank"&gt;Seven Deadliest Social Network Attacks (Syngress)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;br /&gt;
Social networking...if it looks like a person and talks like a person then...&lt;br /&gt;
&lt;table&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td&gt;&lt;iframe align="left" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" src="http://rcm.amazon.com/e/cm?t=seccode20&amp;amp;o=1&amp;amp;p=8&amp;amp;l=bpl&amp;amp;asins=159749545X&amp;amp;fc1=FFFFFF&amp;amp;IS2=1&amp;amp;lt1=_blank&amp;amp;m=amazon&amp;amp;lc1=8181FF&amp;amp;bc1=000000&amp;amp;bg1=000000&amp;amp;f=ifr" style="align: left; height: 245px; padding-right: 10px; padding-top: 5px; width: 131px;"&gt;&lt;/iframe&gt;&lt;/td&gt;&lt;td&gt;&lt;iframe align="left" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" src="http://rcm.amazon.com/e/cm?t=seccode20&amp;amp;o=1&amp;amp;p=8&amp;amp;l=bpl&amp;amp;asins=1597495433&amp;amp;fc1=FFFFFF&amp;amp;IS2=1&amp;amp;lt1=_blank&amp;amp;m=amazon&amp;amp;lc1=8181FF&amp;amp;bc1=000000&amp;amp;bg1=000000&amp;amp;f=ifr" style="align: left; height: 245px; padding-right: 10px; padding-top: 5px; width: 131px;"&gt;&lt;/iframe&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-561866330875185575?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/K-3eYLZEabkiL-VrjQaez6CrV0k/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/K-3eYLZEabkiL-VrjQaez6CrV0k/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/K-3eYLZEabkiL-VrjQaez6CrV0k/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/K-3eYLZEabkiL-VrjQaez6CrV0k/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/IbGNM7TB2zk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/561866330875185575/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=561866330875185575" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/561866330875185575?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/561866330875185575?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/IbGNM7TB2zk/evil-twin-ish-who-is-robin-sage.html" title="Evil Twin-ish: Who is Robin Sage" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/evil-twin-ish-who-is-robin-sage.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IBSX0zeip7ImA9WxFbEkQ.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-688078733648095499</id><published>2010-07-04T19:05:00.000-07:00</published><updated>2010-07-04T19:05:58.382-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-04T19:05:58.382-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="security q and a" /><category scheme="http://www.blogger.com/atom/ns#" term="privacy" /><title>Security Q&amp;A: Is it a bad idea to use my real name on my blog?</title><content type="html">A lot of people are concerned now a days about privacy and the web. I was recently sent this:&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;I changed my blog address to have my name in it so people could find my blog easier. Do you think that's a bad idea? I've seen a lot of&amp;nbsp;professional peers&amp;nbsp;use their name on their blog and in their address. I couldn't get&amp;nbsp;my original blog name&amp;nbsp;to work as my address so I had a weird address before I changed it. Let me know what you think.&lt;/blockquote&gt;&lt;br /&gt;
To answer this questions we need to analyze security and business.&amp;nbsp;My question here is what is the business goal of the blog? In this case, the business need is for the blog to be able to be found easily with the goal being to spread&amp;nbsp;this blogger's content/personal brand. The problem this person is facing&amp;nbsp;is&amp;nbsp;that the blog cannot be found because of a "weird name" that was used instead of the author's actual name. This is an example of "Security through Obscurity". The idea that something that cannot be found is secure.&lt;br /&gt;
&lt;br /&gt;
The answer to this question is Yes use your name with a "but". Security through obscurity does not last. Someone, some way will put the pieces together and uncover the secret. A better approach is risk analysis/risk management. Analyze what you put out there (on your blog) and determine what this could tell a possible attacker about you. Determine your exposure and be aware. Your business in this instance is furthering your personal brand/blog content so focus on that. Make sure your blog is 100% focused on that business goal and you will be fine.&lt;br /&gt;
&lt;br /&gt;
This is a great example of ISC2's quote: "Security transcends technology". Use your real name but&amp;nbsp;be mindful about what you put out there for the world.&amp;nbsp;Good luck with your blog!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-688078733648095499?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/yXxCHyVmDeYXTW5hLjoMpMaotcA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yXxCHyVmDeYXTW5hLjoMpMaotcA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/yXxCHyVmDeYXTW5hLjoMpMaotcA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yXxCHyVmDeYXTW5hLjoMpMaotcA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/7Do4-_aXhpA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/688078733648095499/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=688078733648095499" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/688078733648095499?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/688078733648095499?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/7Do4-_aXhpA/security-q-is-it-bad-idea-to-use-my.html" title="Security Q&amp;A: Is it a bad idea to use my real name on my blog?" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/security-q-is-it-bad-idea-to-use-my.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkIBRH05fip7ImA9WxFbEks.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-7588397182963128320</id><published>2010-07-03T21:11:00.000-07:00</published><updated>2010-07-04T09:22:35.326-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-04T09:22:35.326-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="application security" /><category scheme="http://www.blogger.com/atom/ns#" term="Bid Pal" /><category scheme="http://www.blogger.com/atom/ns#" term="iPod" /><category scheme="http://www.blogger.com/atom/ns#" term="apple" /><title>Weak authentication could have won Daily Show tickets</title><content type="html">I am a big supporter of the Maryland Food Bank. Recently, I went to the Blue Jean Ball fundraiser which is a black tie event above the waste and jeans below. Interesting concept and enjoyable evening. I felt like a lot of people were under dressed but I am&amp;nbsp;guessing those were the "my boss could not go so he/she gave me the tickets" and they didn't know how to dress (always research that).&lt;br /&gt;
&lt;br /&gt;
The food was excellent. I had too many Tuna on Cucumber things but other than that it was a great night. A silent auction is held with all kinds of interesting prizes like golf trips, beach vacations, tours of the Walters (Maria and I won that last year :) ), etc... This year, as you came into the event the staff handed you a device (&lt;span class="goog-spellcheck-word"&gt;iPod&lt;/span&gt; Touch) that you could use to place your bids for the silent auction or donate to the Food Bank. Using your device you entered the auction item number and then the amount you were bidding. Neat idea, makes it more interesting to have a bidding war. When heading into the dinner area, I put the device in my pocket to hold my wife's purse (yep, you read that correctly). Pulling the device from my pocket I accidentally hit the home button, which took me out of the Bid Pal software. The device was not locked down. I now had access to the &lt;span class="goog-spellcheck-word"&gt;iPod&lt;/span&gt; Touch, &lt;span class="goog-spellcheck-word"&gt;Wi&lt;/span&gt;-&lt;span class="goog-spellcheck-word"&gt;Fi&lt;/span&gt; of the Food Bank, and the few other applications that were on the device.&lt;br /&gt;
&lt;br /&gt;
I tried to reopen Bid Pal but could not, I needed an ID Number and password, neither of which I knew. So I went to the service desk for assistance. Told them my tale of woe and they said they could help. I needed to get back in to check on my bid for Daily Show tickets (I didn't win). The lady at the service desk asked me my phone number and then looked me up on a list. She said, 432 as she typed it in to the Bid Pal &lt;span class="goog-spellcheck-word"&gt;log in&lt;/span&gt; screen and handed me the device all set. She told me if it happens again, that my number is 432 and the password is my phone number.&lt;br /&gt;
&lt;br /&gt;
Walking back to the table I noticed at the top right of the screen, 432...my ID number was right on the screen. When I sat down at my table I peered over to my neighbor and saw their number was 433. The person to my right was 434. The table was sequential in ID numbers. My friend and web design guru Clint was sitting across the table so I asked him his ID number, 437. I knew his phone number so I exited the application and sure enough, was able to &lt;span class="goog-spellcheck-word"&gt;login&lt;/span&gt; to the Bid Pal device as Clint. As you might guess, I could have posed as someone else to outbid the winner of the Daily Show tickets, written a bogus&amp;nbsp;IOU&amp;nbsp;and walked away with the tickets.&lt;br /&gt;
&lt;br /&gt;
So how did Bid Pal allow this? They relied on two pieces of information to authenticate a user that could be found out by anyone. This event was targeted to business professionals. A simple guess that they used their work phone numbers (as many did...I asked) and a quick shoulder surf, I could have been anyone at that event.&lt;br /&gt;
&lt;br /&gt;
How do they fix this...use device serial number instead of ID number. So when the user comes to retrieve the device, the device activates Bid Pal with the user id detected from the device (I'm guessing you can do this with &lt;span class="goog-spellcheck-word"&gt;iPod&lt;/span&gt;, if not,&amp;nbsp;seriously Apple? That could be incredibly useful) and then the password is the phone number. This effectively builds dual factor authentication, something you have (the &lt;span class="goog-spellcheck-word"&gt;iPod&lt;/span&gt; Touch device) and something you know (the phone number). The iPhone 4 could even open up a biometric component to this but we won't go there. I would suggest Bid Pal updates their software because the next event, this might be discovered by someone not so &lt;span class="goog-spellcheck-word"&gt;unmalicious&lt;/span&gt; (is that a word?) as me. :)&lt;br /&gt;
&lt;br /&gt;
On a side note, the interface to Bid Pal was really nice. Kudos to them on application/interface design but please improve the security.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-7588397182963128320?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/sOvusGntW_JpdCGAp1QyRIowv5c/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/sOvusGntW_JpdCGAp1QyRIowv5c/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/sOvusGntW_JpdCGAp1QyRIowv5c/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/sOvusGntW_JpdCGAp1QyRIowv5c/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/Pq-YwN8y8Qg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/7588397182963128320/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=7588397182963128320" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/7588397182963128320?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/7588397182963128320?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/Pq-YwN8y8Qg/weak-authentication-could-have-won.html" title="Weak authentication could have won Daily Show tickets" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/weak-authentication-could-have-won.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkICSHo8fCp7ImA9WxFbEkw.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-4682326409556738551</id><published>2010-07-03T20:32:00.000-07:00</published><updated>2010-07-03T20:36:09.474-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-03T20:36:09.474-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Hakin9" /><category scheme="http://www.blogger.com/atom/ns#" term="social engineer" /><category scheme="http://www.blogger.com/atom/ns#" term="publication" /><category scheme="http://www.blogger.com/atom/ns#" term="article" /><category scheme="http://www.blogger.com/atom/ns#" term="Evil Twin" /><title>Hakin9: Birth of an Evil Twin</title><content type="html">How do I know you are who you say you are? In Facebook, Twitter, LinkedIn...I don't. My latest article (July 2010) in Hakin9 magazine examines this topic, the Evil Twin attack. We step through the actions and activities necessary to create an Evil Twin in the hopes that Information Security professionals can take this and educate their workforce.&lt;br /&gt;&lt;br /&gt;Let me know what you think. If you have a story about an Evil Twin experience, definately post that as well!&lt;br /&gt;&lt;br /&gt;&lt;a href="http://bit.ly/dBzP1J"&gt;http://bit.ly/dBzP1J&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-4682326409556738551?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/5cIWkRQST36PZ6hliSbRBnWT3Nw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/5cIWkRQST36PZ6hliSbRBnWT3Nw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/5cIWkRQST36PZ6hliSbRBnWT3Nw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/5cIWkRQST36PZ6hliSbRBnWT3Nw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/2co-Iy_QQp4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/4682326409556738551/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=4682326409556738551" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4682326409556738551?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/4682326409556738551?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/2co-Iy_QQp4/hakin9-birth-of-evil-twin.html" title="Hakin9: Birth of an Evil Twin" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/07/hakin9-birth-of-evil-twin.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUMRX07cSp7ImA9WxFbEkw.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-8502671870008261583</id><published>2010-06-23T21:31:00.000-07:00</published><updated>2010-07-03T20:14:44.309-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-03T20:14:44.309-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="baltimore" /><category scheme="http://www.blogger.com/atom/ns#" term="ISSA" /><category scheme="http://www.blogger.com/atom/ns#" term="maryland" /><category scheme="http://www.blogger.com/atom/ns#" term="information security" /><title>ISSA Baltimore meeting (June)</title><content type="html">This Wednesday I had off school so I decided to visit the local ISSA chapter here in Baltimore. The presentation was on XML Firewalls and how they can be used to help secure web service traffic. Adam Vincent from Layer 7 was the presenter. I found the topic interesting due to my background as a developer and saw lots of uses for such technology in a SOA environment.&lt;br /&gt;&lt;br /&gt;While the presentation was good, the food was excellent! This was my first ISSA meeting so I did not know what to expect. The people were friendly and welcoming, the refreshments were plentiful and I learned a lot in the process.&lt;br /&gt;&lt;br /&gt;I recommend checking out the next Baltimore ISSA meeting to any b-morians interested in Information Security. The next meeting is July 28th and is the topic of "Protecting Your Applications from Backdoors". If you are planning on attending, drop a comment and I'll keep an eye out for you there!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-8502671870008261583?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/lqgxVTkuXhX1_IDsVp7dvNNE-v0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lqgxVTkuXhX1_IDsVp7dvNNE-v0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/lqgxVTkuXhX1_IDsVp7dvNNE-v0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lqgxVTkuXhX1_IDsVp7dvNNE-v0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/BdNrysFGbm4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/8502671870008261583/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=8502671870008261583" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/8502671870008261583?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/8502671870008261583?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/BdNrysFGbm4/issa-baltimore-meeting-june.html" title="ISSA Baltimore meeting (June)" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/06/issa-baltimore-meeting-june.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkQARHc9eSp7ImA9WxFbEkw.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-8127860634996714621</id><published>2010-04-30T20:28:00.000-07:00</published><updated>2010-07-03T20:32:25.961-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-03T20:32:25.961-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Hakin9" /><category scheme="http://www.blogger.com/atom/ns#" term="threat modelling" /><category scheme="http://www.blogger.com/atom/ns#" term="publication" /><category scheme="http://www.blogger.com/atom/ns#" term="article" /><title>Hakin9: Threat Modeling Basics</title><content type="html">Is your software secure? How do you know? In this month's Hakin9 Magazine, I explore the concept of Threat Modeling which is decomposing an application to analyze attack vectors. This is a process done during the design phase of a project so threats are identified long before a single line of code is written.&lt;br /&gt;&lt;br /&gt;Drop me some comments and let me know what you think!&lt;br /&gt;&lt;br /&gt;&lt;a href="http://bit.ly/90u1V6"&gt;http://bit.ly/90u1V6&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-8127860634996714621?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/gNUZTzbRXSmbt5Y2iK6Cr6LkRX8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/gNUZTzbRXSmbt5Y2iK6Cr6LkRX8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/gNUZTzbRXSmbt5Y2iK6Cr6LkRX8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/gNUZTzbRXSmbt5Y2iK6Cr6LkRX8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/eWIHTVaKzCo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/8127860634996714621/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=8127860634996714621" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/8127860634996714621?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/8127860634996714621?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/eWIHTVaKzCo/hakin9-threat-modeling-basics.html" title="Hakin9: Threat Modeling Basics" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/04/hakin9-threat-modeling-basics.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEYDRns7fyp7ImA9WxBVGEw.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-1793694662647033257</id><published>2010-02-21T20:14:00.000-08:00</published><updated>2010-02-21T20:16:17.507-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-21T20:16:17.507-08:00</app:edited><title>Class Presentation</title><content type="html">We had to do a class presentation for one of my grad school classes. Here is my presentation. I tried a different kind of style in the slides, everything is hand drawn. Let me know what you think.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;iframe src="http://docs.google.com/present/embed?id=dj9fkqm_127dt8xtcfm" frameborder="0" width="410" height="342"&gt;&lt;/iframe&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-1793694662647033257?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/75R5ErkrQCWd-WPTQ-siYCnHODk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/75R5ErkrQCWd-WPTQ-siYCnHODk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/75R5ErkrQCWd-WPTQ-siYCnHODk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/75R5ErkrQCWd-WPTQ-siYCnHODk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/aDEKJG6OCNE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/1793694662647033257/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=1793694662647033257" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/1793694662647033257?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/1793694662647033257?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/aDEKJG6OCNE/class-presentation.html" title="Class Presentation" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/02/class-presentation.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C04GSXY6cCp7ImA9WxBVEE4.&quot;"><id>tag:blogger.com,1999:blog-7896440576153621946.post-6625844945498310877</id><published>2010-02-12T19:31:00.001-08:00</published><updated>2010-02-12T19:32:08.818-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-12T19:32:08.818-08:00</app:edited><title>New/Fun Technology</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_lKNGBJjZVpA/S3YdMr-_VrI/AAAAAAAAAF4/pD-Svpf6z1U/s1600-h/LinkedIn_Profile_201021332622.png"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 335px;" src="http://2.bp.blogspot.com/_lKNGBJjZVpA/S3YdMr-_VrI/AAAAAAAAAF4/pD-Svpf6z1U/s400/LinkedIn_Profile_201021332622.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5437565703899010738" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7896440576153621946-6625844945498310877?l=seccode.blogspot.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/6-jTQYSCyur83KzMv_I1_0q0T5o/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/6-jTQYSCyur83KzMv_I1_0q0T5o/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/6-jTQYSCyur83KzMv_I1_0q0T5o/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/6-jTQYSCyur83KzMv_I1_0q0T5o/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SeccodeSecuringTheWildWildWeb/~4/gKX6u7NS6Og" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://seccode.blogspot.com/feeds/6625844945498310877/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7896440576153621946&amp;postID=6625844945498310877" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/6625844945498310877?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7896440576153621946/posts/default/6625844945498310877?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/SeccodeSecuringTheWildWildWeb/~3/gKX6u7NS6Og/newfun-technology.html" title="New/Fun Technology" /><author><name>Tim Kulp</name><uri>https://profiles.google.com/104495724950668237153</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-SET4x5bUV1U/AAAAAAAAAAI/AAAAAAAAALg/FFGnusi4YLA/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_lKNGBJjZVpA/S3YdMr-_VrI/AAAAAAAAAF4/pD-Svpf6z1U/s72-c/LinkedIn_Profile_201021332622.png" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://seccode.blogspot.com/2010/02/newfun-technology.html</feedburner:origLink></entry></feed>

