<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Rossander's Security Reader &#187; Uncategorized</title>
	<atom:link href="http://rossander.org/infosec/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://rossander.org/infosec</link>
	<description>an Information Security blog for the rest of us</description>
	<lastBuildDate>Tue, 15 May 2012 11:40:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Security lessons from history</title>
		<link>http://rossander.org/infosec/2011/06/security-lessons-from-history/</link>
		<comments>http://rossander.org/infosec/2011/06/security-lessons-from-history/#comments</comments>
		<pubDate>Thu, 02 Jun 2011 01:30:28 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=715</guid>
		<description><![CDATA[Security lessons from ancient history]]></description>
			<content:encoded><![CDATA[<p>Here are a collection of articles about applying Bronze and Iron Age concepts to modern security.  Some of the ideas seem a bit radical but I think they are worth contemplating.</p>
<ul>
<li><a href=http://www.csoonline.com/article/220224/information-security-defense-in-depth-lessons-from-a-bronze-age-fort->Information Security Lessons from a Bronze Age Fort</a></li>
<li><a href=http://www.csoonline.com/article/221329/modern-crowd-control-lessons-from-ancient-pompeii->Crowd Control Lessons from Pompeii</a></li>
<li><a href=http://www.csoonline.com/article/217014/4-things-the-roman-aqueducts-can-teach-us-about-securing-the-power-grid>Infrastructure Security lessons from the Roman Aqueducts</a></li>
<li><a href=http://www.csoonline.com/article/329164/freedom-of-the-cyber-seas>Cyber-security Policy Lessons from Thomas Jefferson&#8217;s response to the Barbary Pirates</a></li>
<li><a href=http://www.csoonline.com/article/216892/the-dark-ages-of-identity-management>Identity Management Lessons from William the Conqueror</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2011/06/security-lessons-from-history/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lies, Damned Lies and Medical Statistics</title>
		<link>http://rossander.org/infosec/2010/10/lies-damned-lies-and-medical-statistics/</link>
		<comments>http://rossander.org/infosec/2010/10/lies-damned-lies-and-medical-statistics/#comments</comments>
		<pubDate>Mon, 25 Oct 2010 14:44:23 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=683</guid>
		<description><![CDATA[Dr John Ioannidis has published several influential papers on why you should not trust 90% of what you read.  His focus is on medical research but the findings are applicable across many fields.]]></description>
			<content:encoded><![CDATA[<p> This is a bit off the path of information security but I wanted to share an excellent article on why you should distrust 90% of what you read (including, unfortunately, much of the computer security advice out there).</p>
<p> <i>The Atlantic</i> published <a href=http://www.theatlantic.com/magazine/archive/2010/11/lies-damned-lies-and-medical-science/8269/1/>this interview</a> with Dr John Ioannidis, a medical researcher who has dedicated his career to showing that &#8220;much of what medical researchers conclude in their studies is misleading, exaggerated, or flat-out wrong.&#8221;  This is true even in the &#8216;gold-standard&#8217; peer-reviewed studies.  The biases of funding and publication pressure are too much to overcome.  Worse, even when the studies have been overturned, the medical community continues to rely on the old, disproven theories.</p>
<p> While his study and his research are based on medical journals and medical research, his findings are applicable to everything from physics to economics to computer science.</p>
<p> You can also read Dr Ioannidis&#8217; original paper at <a href=http://www.plosmedicine.org/article/info:doi/10.1371/journal.pmed.0020124>PLoS Medicine</a>.  He lays out a detailed mathematical proof that, &#8220;assuming modest levels of researcher bias, typically imperfect research techniques, and the well-known tendency to focus on exciting rather than highly plausible theories, researchers will come up with wrong findings most of the time.&#8221;  He wrote a follow-up article <a href=http://www.plosmedicine.org/article/info:doi/10.1371/journal.pmed.0050201>here</a> specifically discussing the distortion caused by publication practices.  I recommend both for anyone with an interest in the scientific method and/or an interest in sorting truth from rumor among the deluge of &#8220;good advice&#8221; on the internet.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2010/10/lies-damned-lies-and-medical-statistics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Small businesses bear the brunt of tort liabilities</title>
		<link>http://rossander.org/infosec/2010/07/small-businesses-bear-the-brunt-of-tort-liabilities/</link>
		<comments>http://rossander.org/infosec/2010/07/small-businesses-bear-the-brunt-of-tort-liabilities/#comments</comments>
		<pubDate>Tue, 13 Jul 2010 15:05:18 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=645</guid>
		<description><![CDATA[US Chamber report shows that small businesses are most badly hurt by our lack of tort reform.]]></description>
			<content:encoded><![CDATA[<p> Today&#8217;s post has nothing to do directly with information security but the article so caught my eye that I had to share it.  Feel free to skip today&#8217;s post if it doesn&#8217;t interest you.</p>
<p> The U.S. Chamber Institute for Legal Reform recently released a report on the <a href=http://www.instituteforlegalreform.com/images/stories/documents/pdf/research/ilr_small_business_2010.pdf>disproportionate share of U.S. litigation cost borne by small businesses</a>.  The full report is about 25 pages and well worth reading.  The short version is:</p>
<ul>
<li> Small businesses generate 64 percent of all new jobs and over half of non-farm GDP</li>
<li> Small businesses bore 81 percent of business litigation cost, yet represented only 22 percent of US business revenue</li>
<li> Small businesses pay more of their tort costs out-of-pocket rather than through insurance</li>
<li> More than one-third of surveyed small businesses had been sued &#8211; To put that number in perspective, think of any three local small businesses that you use, maybe your barber, hardware store and local laundry.  Do you really think that one of every three is so evil that the only way to resolve the complaint was to go to court?</li>
<li> 62% reported making business decisions in order to avoid lawsuits <b>and that these decisions made their products and services more expensive</b>.  45% pulled a product or service off the market just out of fear of lawsuits and 11% have had to lay off employees as a result of lawsuits</li>
<li> For medical businesses, it&#8217;s even worse.  Tort liability is 94 percent of all medical malpractice litigation for small medical practices and small medical labs.  This is driving the medical profession away from small practices and toward large hospital-based and health system-based groups.  In just three years, from 2005-2008, small groups dropped from two-thirds of all practices to less than half.</li>
<li> 66% of the general public agreed with this statement: “The fear of being sued is changing American society for the worse because it’s often having the effect of discouraging people from doing the right things.”</li>
</ul>
<p> Statistically, some few of those small businesses are bad apples who should be sued, maybe even into bankruptcy.  Sometimes, that is your only recourse.  But I do not believe that all businesses are inherently evil and am deeply suspicious of the way the legal <i>profession</i> has morphed into a legal <i>industry</i> over the past few decades.  The more I read, the more convinced I become that tort reform is desperately needed.  Some form of &#8220;loser pays&#8221; like they have in Europe would be a good first step.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2010/07/small-businesses-bear-the-brunt-of-tort-liabilities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Five Biggest Lies in Management</title>
		<link>http://rossander.org/infosec/2010/03/the-five-biggest-lies-in-management/</link>
		<comments>http://rossander.org/infosec/2010/03/the-five-biggest-lies-in-management/#comments</comments>
		<pubDate>Fri, 26 Mar 2010 04:45:28 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/2010/03/the-five-biggest-lies-in-management/</guid>
		<description><![CDATA[Recommended reading:  The Five Biggest Lies in HR]]></description>
			<content:encoded><![CDATA[<p> This post isn&#8217;t directly related to security but if you&#8217;ve never been out to workforce.com before, I recommend them.  The site uses buzzwords like they&#8217;re just for HR professionals but it&#8217;s good reading for any businessperson.</p>
<p> This post titled <a href=http://www.workforce.com/archive/feature/27/04/69/index.php>The Five Biggest Lies in HR</a> by Kris Dunn was fascinating, if a bit cynical.  It&#8217;s a painfully realistic view of where we really fit in the workforce.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2010/03/the-five-biggest-lies-in-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Allowable links on your website</title>
		<link>http://rossander.org/infosec/2009/12/allowable-links-on-your-website/</link>
		<comments>http://rossander.org/infosec/2009/12/allowable-links-on-your-website/#comments</comments>
		<pubDate>Mon, 07 Dec 2009 18:47:36 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=519</guid>
		<description><![CDATA[Links help readers but all links you make or allow on your website reflect back on you.  Be conservative in your linking.]]></description>
			<content:encoded><![CDATA[<p> I read an article this morning on a non-profit called the <a href=http://www.americanwidowsproject>American Widows Project</a> and thought it sounded like a very worthy cause.  In addition to helping them directly, I&#8217;d like to do my little part to get them some more publicity.</p>
<p> That reminded me of another recent article on <a href=http://www.bricker.com/legalservices/practice/litigation/ediscotech/eblog/details.aspx?id=212>allowable links on your website</a>.  That article specifically talks about the problems faced by public entities like school districts and whether they must allow links to private companies on their webpages.  It&#8217;s a difficult question for any governmental organization.  Under US law, they have an obligation to protect free speech but at the same time can not create the appearance of an unfair endorsement of a private opinion.</p>
<p> For a public entity, it depends on the exact nature of the page &#8211; if your township hosts a &#8220;forum&#8221; where citizens are allowed to express opinions and air grievances, there are very few allowable limits that can be placed on the free speech rights of the people participating in the forum.  On the other hand, even public entities have <u>non</u>-public forums &#8211; places where completely free speech would get in the way of the very mission that the agency is supposed to carry out.  Limits in those forums are more acceptable.  Regardless, any limits should be
<ol>
<li> clearly stated ahead of time</li>
<li> based on reasonable protections of other rights (for example, &#8216;no hate speech&#8217; or &#8216;stay on topic&#8217;) and </li>
<li> be enforced with ruthless consistency.</li>
</ol>
<p>If you work with a public entity with any online presence, I strongly urge you to read the eDiscoTech article.</p>
<p> As a private citizen, the calculations are different.  First, you have no obligation to allow others to say anything.  You are not required to let someone to take over your backyard to make their political rant even if the same speech would be strongly protected in the village square.  But you want to allow interaction and linking on your personal website.  That social contact is most of what makes the website valuable and brings in readers.  The challenge is that your credibility is directly linked to all those outsiders.  Anything you include or allow on your own website carries an implied endorsement.  If there&#8217;s bad content on the other side of a link, <b>it reflects back on you</b>.  So if you host a blog (whether Twitter or a more conventional blog like this one), you probably want to allow comments but you probably also want to keep some rights to control them if only to filter out the spam and other worthless content.  And you should be fairly conservative about who you link to.  Be sure they are the kind of people you want your reputation associated with.</p>
<p> Corporations have it hardest of all.  They are private and have no legal obligation to allow their site to be used for the free speech of others but attempts to suppress or censor negative comments almost always create more backlash and ill-will than the original complaint.  Corporations generally do best by enforcing clear rules (especially the &#8220;off-topic comments will be removed&#8221; rule) but otherwise allowing users to post whatever they really feel about the company&#8217;s products or services.</p>
<p> Ultimately, I decided to include a link to the American Widows Project &#8211; you can see it now in the blogroll on the right of the website.  Deciding who you should link to is an interesting question, though.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2009/12/allowable-links-on-your-website/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>10 rules for talking to a reporter</title>
		<link>http://rossander.org/infosec/2009/11/10-rules-for-talking-to-a-reporting/</link>
		<comments>http://rossander.org/infosec/2009/11/10-rules-for-talking-to-a-reporting/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 12:48:10 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=531</guid>
		<description><![CDATA[Think about how to talk to reporters ahead of time.  Be fact-based and don't be pressured into meeting their goals at the expense of your own.]]></description>
			<content:encoded><![CDATA[<p>How many times have you seen someone talking to a reporter and ask &#8220;did he really just say that?&#8221;  What was he possibly thinking?  Sometimes people do say stupid things but sometimes they just get caught because they are not used to speaking to reporters.  This is especially true when you are responding to a crisis.  Remember that the reporter has one set of goals &#8211; and they are not your goals.  </p>
<p>When you get into a crisis, it&#8217;s too late to be deciding who and how to talk to the media.  Have a plan and practice it <i>before</i> the crisis hits so you don&#8217;t get caught off guard.  The list below has some helpful thoughts about dealing with reporters.  It was originally developed at a crisis communications workshop at a Florida Beekeepers meeting in 1992 in response to scaremongering about africanized honey bees.  These rules are still relevant today and apply no matter what your crisis is.</p>
<ol>
<li> <b>Individual Rights</b> &#8211; No one from the press has the right to violate your individual rights.</li>
<li> <b>Honesty</b> &#8211; Never mislead or lie to a reporter. If the situation is under litigation, say this is so; if there is a question about profits, dollars or proprietary information, you can defer/refuse answering based on not informing competitors in the marketplace.</li>
<li> <b>Buzz Words</b> &#8211; Never repeat an expression or inflammatory statement made by a reporter. As an example, if you are asked to what do you attribute this catastrophe, do not repeat the word &#8220;catastrophe.&#8221; It then becomes attributable to you and you alone; you will &#8220;own&#8221; it.</li>
<li> <b>Hostility</b> &#8211; Never get angry; keep cool and remember the reporter always has the last word.</li>
<li> <b>Off the Record</b> &#8211; There is no such thing; if you don&#8217;t want it reported, don&#8217;t say it.</li>
<li> <b>Estimates</b> &#8211; Never make numerical estimates in time or dollars. Say that the incident is under investigation and you will provide accurate information when it becomes available.</li>
<li> <b>Reporter Verification</b> &#8211; Ask for identification, the purpose of a reporter&#8217;s activities, media affiliation and telephone number.</li>
<li> <b>Bridging</b> &#8211; Try to bridge the gap between a reporter&#8217;s wish to be negative and providing a positive statement about your activity.</li>
<li> <b>Statistics</b> &#8211; If you are not aware of statistics provided by a reporter, say so and ask for them in writing before commenting.</li>
<li> <b>Deadlines</b> &#8211; All reporters are on deadlines, but you are not. Take all the time necessary to avoid hasty comments. The fact that a microphone is stuck in your face doesn&#8217;t mean you have to say something. Dead air time is not likely to appear on television.</li>
</ol>
<div align=right><i><small>Excerpted with permission from <a href=http://www.beeculture.com/ target=_blank>Bee Culture magazine</a>, Jan 2007.</small></i></div>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2009/11/10-rules-for-talking-to-a-reporting/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Security is a Red Queen’s race</title>
		<link>http://rossander.org/infosec/2009/09/security-is-a-red-queen%e2%80%99s-race/</link>
		<comments>http://rossander.org/infosec/2009/09/security-is-a-red-queen%e2%80%99s-race/#comments</comments>
		<pubDate>Thu, 01 Oct 2009 01:30:52 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=521</guid>
		<description><![CDATA[Security is a Red Queen's race - perfect security is impossible.  It's also usually unnecessary.  Have security that's "good enough".]]></description>
			<content:encoded><![CDATA[<p><i>This was originally posted on 13 Sep 2009.  I accidentally deleted the post the next week.  Here it is again &#8220;for the record&#8221;.</i></p>
<p>These days, security is a Red Queen’s race where “it takes all the running you can do, to keep in the same place.” Hackers are constantly raising the bar and making old protections worth less than they were the day before.</p>
<p>The company that hosts this blog recently posted a <a href=http://wordpress.org/development/2009/09/keep-wordpress-secure/>very good article</a> on the problem. They recommend (and I strongly agree) that you need to keep your software fully up-to-date and patched. You might not be perfectly protected from every hacker attack but you’ll be protected from most and often that can be enough.</p>
<p>There’s an <a href=http://diveintomark.org/archives/2002/10/29/club_vs_lojack_solutions>old essay by Mike Pilgrim</a> comparing computer security to the Club and to Lojack. If you remember the club, it was a lock that fit on the steering wheel of the car, making it almost impossible for a thief to steer as he’s trying to get away. It wasn’t perfect security – a really determined thief who specifically wanted your car could drill the lock or just cut a section from the steering wheel. But it was pretty good protection from a thief who just wanted a car. As long as easier pickings are available, the thief will follow the path of least resistance.</p>
<p>A more grizzly way to say it is in the old joke about the two hikers who surprise a bear in the woods. They start running and the bear chases. One of them stops to change into sneakers and the other says “You’re crazy – even in sneakers you’ll never outrun a bear.” The other replies “I don’t have to be faster than the bear … I only have to be faster than you!”</p>
<p>That “faster than you” attitude can be enough to deflect the hacker to an easier target. On the other hand, if you don’t keep your software patched, you’re choosing to be the guy still in boots – the easy meat. Patch your software and keep it current. If you can, <a href=http://rossander.org/infosec/2009/02/patching-for-personal-computers/>use a tool</a> such as Secunia to help stay current. It’s a lot of work but it’s better than joining the bear for dinner.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2009/09/security-is-a-red-queen%e2%80%99s-race/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Security Theater</title>
		<link>http://rossander.org/infosec/2009/06/security-theater/</link>
		<comments>http://rossander.org/infosec/2009/06/security-theater/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 12:57:50 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/2009/06/security-theater/</guid>
		<description><![CDATA[Security theater is a danger to society and to your business.  Make sure your security policies make sense and have benefits which outweigh their negative consequences.]]></description>
			<content:encoded><![CDATA[<p>Security Theater is a difficult topic for any security person to talk about.  First what is it &#8211; Security Theater in my mind are those &#8216;security&#8217; restrictions that don&#8217;t actually improve security.  They&#8217;re put in place to make somebody feel better or to give the appearance of improved security regardless of their actual effect.  They may be well-intentioned but they are generally poorly thought out.</p>
<p>For example, the early restrictions imposed at the airports which attempted to stop people from bringing &#8220;weapons&#8221; on the plane used a definition of &#8216;weapons&#8217; that was so bad that all kinds of immaterial tools were confiscated.  Yes, a 10&#8243; screwdriver could conceivably be sharpened and used as a punch knife.  You&#8217;d need a file and a half-hour or so unobserved to sharpen it &#8211; not things likely to happen in any concourse I know of but it&#8217;s theoretically possible.  </p>
<p>The hypocrisy, though, is that they never banned pens or pencils.  A number 2 pencil is already sharper than most knives and just as dangerous.  </p>
<p>But even assuming the most liberal interpretation of &#8216;weapon&#8217;, what possible harm can an evildoer perpetrate with the miniature phillips head screwdrivers that many people carry to tighten the screws on their eyeglasses?  There simply is no defensible argument for that restriction.  Unless you think that no one will notice as the offender sits there for another half-hour and tried to take apart the plane?</p>
<p>The confiscations of those tools (which, while not perfectly safe, were as safe as other routine objects allowed through) represent an unjustified sacrifice of civil liberties.  Security is important.  But it is not the end desire of all life or of business.  Security is about managing risks and balancing the risks against the benefits.  </p>
<p>Security folks (including myself) often have a hard time with this concept.  Our job &#8211; our whole purpose in life &#8211; is often focused on thinking about security, increasing security and reducing risks.  We often don&#8217;t have the perspective to see the benefits or liberties that we&#8217;re infringing with our policies.  And we certainly don&#8217;t have the incentives to look for those benefits.  </p>
<p>This, unfortunately, is why security people should never be allowed to have the final say in the security policy.  If you have your own business, have someone who is responsible for security.  And listen to them carefully.  But make sure that you have both sides of the argument &#8211; the benefits from security <i>and</i> the consequences of the policy.  Remember that a risk-free environment is not possible.  Good security is about balance.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2009/06/security-theater/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sabbatical&#8217;s over</title>
		<link>http://rossander.org/infosec/2009/06/sabbaticals-over/</link>
		<comments>http://rossander.org/infosec/2009/06/sabbaticals-over/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 12:49:47 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/2009/06/sabbaticals-over/</guid>
		<description><![CDATA[Well, I finally took my exam. Have no idea how I did and it&#8217;s probably pointless guessing. I&#8217;ll know in 6-8 weeks. I&#8217;ll start working on tips again. See you soon.]]></description>
			<content:encoded><![CDATA[<p>Well, I finally took my exam.  Have no idea how I did and it&#8217;s probably pointless guessing.  I&#8217;ll know in 6-8 weeks.  I&#8217;ll start working on tips again.</p>
<p>See you soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2009/06/sabbaticals-over/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>On sabbatical</title>
		<link>http://rossander.org/infosec/2009/04/on-sabbatical/</link>
		<comments>http://rossander.org/infosec/2009/04/on-sabbatical/#comments</comments>
		<pubDate>Tue, 21 Apr 2009 16:48:46 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/2009/04/on-sabbatical/</guid>
		<description><![CDATA[I&#8217;ve got a couple of things going on right now and will be taking a sabbatical from the infosec tips for a while. Hope to be back soon.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve got a couple of things going on right now and will be taking a sabbatical from the infosec tips for a while.  Hope to be back soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2009/04/on-sabbatical/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

