<?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>Joe's Amazing Technicolor Weblog &#187; security</title>
	<atom:link href="http://slagwerks.com/blog/index.php/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://slagwerks.com/blog</link>
	<description></description>
	<lastBuildDate>Fri, 23 Jul 2010 22:31:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Does 201 CMR 17 apply to VOIP?</title>
		<link>http://slagwerks.com/blog/index.php/2010/05/13/does-201-cmr-17-apply-to-voip/</link>
		<comments>http://slagwerks.com/blog/index.php/2010/05/13/does-201-cmr-17-apply-to-voip/#comments</comments>
		<pubDate>Thu, 13 May 2010 17:46:58 +0000</pubDate>
		<dc:creator>joe</dc:creator>
				<category><![CDATA[Massachusetts]]></category>
		<category><![CDATA[Tech Stuff]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://slagwerks.com/blog/?p=368</guid>
		<description><![CDATA[Background: looking at going to a Voice Over IP phone system at work. Wondering if Massachusetts&#8217; new law about information security&#160;applies. Why it might not: a potential (MA based) vendor we&#8217;re talking to&#160;says We&#8217;ve not been asked this before and about 201 CMR 17 Compliance and I don&#8217;t particularly think it applies to our VoIP, or [...]]]></description>
			<content:encoded><![CDATA[<p>Background: looking at going to a Voice Over <span class="caps">IP</span> phone system at work. Wondering if Massachusetts&#8217; new law about information security&nbsp;applies.</p>
<p><strong>Why it might not:</strong> a potential (<span class="caps">MA</span> based) vendor we&#8217;re talking to&nbsp;says</p>
<blockquote><p>We&#8217;ve not been asked this before and about 201 <span class="caps">CMR</span> 17 Compliance and I don&#8217;t particularly think it applies to our VoIP, or VoIP in&nbsp;general</p></blockquote>
<p><strong>Why it might:</strong> Section 17.04 qualifies the applicability of the rule&nbsp;to</p>
<blockquote><p>Every person that owns or licenses personal information about a resident of the Commonwealth and electronically stores or transmits such information shall include&#8230;a security system covering its computers, including any wireless&nbsp;system</p></blockquote>
<p>Like just about any business, we definitely transmit personal information over our phone system, so I think the technical / legal question is whether an electronic phone system of the type in question is covered under the &#8220;its computers&#8221;&nbsp;phrase.</p>
<p>Stepping back from the legal to the practical, however, it seems fair to expect reasonable information security from our communications systems, including <span class="caps">VOIP</span>. At least in its intent, I think that&#8217;s what 201 <span class="caps">CMR</span> 17 is after. <span class="caps">VOIP</span> is still new enough that I suspect many prospective customers (like us!) aren&#8217;t quite sure what constitutes a reasonably secure installation, though we sense that there are all kinds of potential attack vectors not present in&nbsp;<span class="caps">POTS</span>.</p>
]]></content:encoded>
			<wfw:commentRss>http://slagwerks.com/blog/index.php/2010/05/13/does-201-cmr-17-apply-to-voip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>latest 201 CMR 17 hotness</title>
		<link>http://slagwerks.com/blog/index.php/2010/01/15/latest-201-cmr-17-hotness/</link>
		<comments>http://slagwerks.com/blog/index.php/2010/01/15/latest-201-cmr-17-hotness/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 13:54:48 +0000</pubDate>
		<dc:creator>joe</dc:creator>
				<category><![CDATA[Massachusetts]]></category>
		<category><![CDATA[Tech Stuff]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://slagwerks.com/blog/?p=342</guid>
		<description><![CDATA[You could be excused for having missed the news, but the 201 CMR 17 that was just about to go into effect over a year ago&#8230; is now just about to go into&#160;effect! some&#160;tidbits: 201 CMR may even apply to entities entirely outside of MA, as long as they have any data about Massholes in [...]]]></description>
			<content:encoded><![CDATA[<p>You could be excused for having missed the news, but the 201 <span class="caps">CMR</span> 17 that was just about to go into effect <a href="http://slagwerks.com/blog/index.php/2008/10/22/looking-further-into-ma-regulation-201-cmr-1700/">over a year ago</a>&#8230; is now <a href="http://www.hklaw.com/id24660/PublicationId2727/ReturnId31/contentid54375/">just about to go into&nbsp;effect</a>!</p>
<p>some&nbsp;tidbits:</p>
<ul>
<li>201 <span class="caps">CMR</span> may even <a href="http://arielsilverstone.com/library/201-cmr/">apply to entities entirely outside of <span class="caps">MA</span></a>, as long as they have any data about Massholes in their systems. So don&#8217;t get all smirky in Texas or&nbsp;wherever.</li>
<li>Who knew? Martha Coakley, as <span class="caps">AG</span>, gets credit for helping adjust 201 <span class="caps">CMR</span> to <a href="http://privacylaw.proskauer.com/tags/201-cmr-1700/">work better with business&#8217; realities</a>. That, and her Harpoon preference, really ought to be pushed more strongly by the&nbsp;campaign.</li>
<li>A useful collection of info can be found at <a href="http://201cmr17.com/">one of the ugliest websites in recent&nbsp;memory</a>.</li>
</ul>
<p>Fortunately, there doesn&#8217;t seem to be anything particularly unreasonable in the requirements, so organizations following good data security procedures shouldn&#8217;t have to do much work (if any) to be&nbsp;compliant.</p>
<ul></ul>
]]></content:encoded>
			<wfw:commentRss>http://slagwerks.com/blog/index.php/2010/01/15/latest-201-cmr-17-hotness/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Looking further into MA regulation 201 CMR 17.00</title>
		<link>http://slagwerks.com/blog/index.php/2008/10/22/looking-further-into-ma-regulation-201-cmr-1700/</link>
		<comments>http://slagwerks.com/blog/index.php/2008/10/22/looking-further-into-ma-regulation-201-cmr-1700/#comments</comments>
		<pubDate>Wed, 22 Oct 2008 18:11:10 +0000</pubDate>
		<dc:creator>joe</dc:creator>
				<category><![CDATA[Massachusetts]]></category>
		<category><![CDATA[Politics]]></category>
		<category><![CDATA[Tech Stuff]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://slagwerks.com/blog/?p=150</guid>
		<description><![CDATA[Thanks to MSCPA, I finally tracked down the Governor&#8217;s press release which, at first glance, has a reasonably clear description of the regulation&#8217;s intent. Also came across an analysis by Beth Israel&#8217;s CIO, a positive blurb from a Maine consultancy, and a brief mention by a MA payroll&#160;company. As for me, I still need to [...]]]></description>
			<content:encoded><![CDATA[<p>Thanks to <a href="http://www.mscpaonline.org/news/news_detail.php?news_id=118"><span class="caps">MSCPA</span></a>, I finally tracked down the <a href="http://www.mass.gov/?pageID=gov3pressrelease&amp;L=1&amp;L0=Home&amp;sid=Agov3&amp;b=pressrelease&amp;f=090822_identity_theft_prevention_executive_order&amp;csid=Agov3">Governor&#8217;s press release</a> which, at first glance, has a reasonably clear description of the regulation&#8217;s intent. Also came across <a href="http://geekdoctor.blogspot.com/2008/10/massachusetts-data-protection.html">an analysis by Beth Israel&#8217;s <span class="caps">CIO</span></a>, <a href="http://pdxmsp.typepad.com/my_weblog/2008/10/following-oregons-lead---massachusetts-201-cmr-1700.html">a positive blurb from a Maine consultancy</a>, and <a href="https://www.visionpayroll.com/kb/tag/201-cmr-1700/">a brief mention by a <span class="caps">MA</span> payroll&nbsp;company</a>.</p>
<p>As for me, I still need to do my official audit of our procedures vs. those specified by the&nbsp;regulation.</p>
]]></content:encoded>
			<wfw:commentRss>http://slagwerks.com/blog/index.php/2008/10/22/looking-further-into-ma-regulation-201-cmr-1700/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>new Massachusetts personal info requirements</title>
		<link>http://slagwerks.com/blog/index.php/2008/09/25/new-massachusetts-personal-info-requirements/</link>
		<comments>http://slagwerks.com/blog/index.php/2008/09/25/new-massachusetts-personal-info-requirements/#comments</comments>
		<pubDate>Thu, 25 Sep 2008 21:30:47 +0000</pubDate>
		<dc:creator>joe</dc:creator>
				<category><![CDATA[Massachusetts]]></category>
		<category><![CDATA[Tech Stuff]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://slagwerks.com/blog/?p=74</guid>
		<description><![CDATA[Networks Unlimited just sent out a note (thanks!) about the Mass Office of Consumer Affairs&#8217; new Standards for The Protection of Personal Information of Residents of the Commonwealth, aka 201 CMR 17.00: M.G.L. c. 93H. It outlines the responsibilities of anyone who gathers personal information on Mass residents. At a glance, they look pretty reasonable. [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://networksunlimited.com">Networks Unlimited</a> just sent out a note (thanks!) about the Mass Office of Consumer Affairs&#8217; new<br />
<a href="http://www.mass.gov/?pageID=ocamodulechunk&amp;L=1&amp;L0=Home&amp;sid=Eoca&amp;b=terminalcontent&amp;f=idtheft_201cmr17&amp;csid=Eoca">Standards for The Protection of Personal Information of Residents of the Commonwealth</a>, aka 201 <span class="caps">CMR</span> 17.00: <span class="caps">M.G.L.</span> c. 93H. It outlines the responsibilities of anyone who gathers personal information on Mass residents. At a glance, they look pretty reasonable. From the&nbsp;intro:</p>
<blockquote><p>Every person that owns, licenses, stores or maintains personal information about a resident of the Commonwealth shall develop, implement, maintain and monitor a comprehensive, written information security program applicable to any records containing such personal&nbsp;information.</p></blockquote>
<p>It&#8217;ll be interesting to sit down with this <span class="amp">&amp;</span> see how our policies <span class="amp">&amp;</span> procedures match&nbsp;up.</p>
]]></content:encoded>
			<wfw:commentRss>http://slagwerks.com/blog/index.php/2008/09/25/new-massachusetts-personal-info-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Whoops &#8212; my rails app was open to a common vulnerability</title>
		<link>http://slagwerks.com/blog/index.php/2008/09/23/whoops-my-rails-app-was-open-to-a-common-vulnerability/</link>
		<comments>http://slagwerks.com/blog/index.php/2008/09/23/whoops-my-rails-app-was-open-to-a-common-vulnerability/#comments</comments>
		<pubDate>Tue, 23 Sep 2008 20:36:17 +0000</pubDate>
		<dc:creator>joe</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Ruby on Rails]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://slagwerks.com/blog/?p=70</guid>
		<description><![CDATA[Thanks to Hacker News for bringing this common problem with Rails apps to my attention. Nobody seems to have taken advantage of it on my app, but still, it&#8217;s a drag having insecure applications, and a little disappointing that there aren&#8217;t more heads-up about this, or a more secure default as Merb apparently&#160;has.]]></description>
			<content:encoded><![CDATA[<p>Thanks to Hacker News for bringing this <a href="http://news.ycombinator.com/item?id=311345">common problem with Rails apps</a> to my attention. Nobody seems to have taken advantage of it on my app, but still, it&#8217;s a drag having insecure applications, and a little disappointing that there aren&#8217;t more heads-up about this, or a more secure default as <a href="http://merbivore.com/">Merb</a> apparently&nbsp;has.</p>
]]></content:encoded>
			<wfw:commentRss>http://slagwerks.com/blog/index.php/2008/09/23/whoops-my-rails-app-was-open-to-a-common-vulnerability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Planning soekris project</title>
		<link>http://slagwerks.com/blog/index.php/2008/06/25/planning-soekris-project/</link>
		<comments>http://slagwerks.com/blog/index.php/2008/06/25/planning-soekris-project/#comments</comments>
		<pubDate>Wed, 25 Jun 2008 13:07:50 +0000</pubDate>
		<dc:creator>joe</dc:creator>
				<category><![CDATA[Tech Stuff]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[OpenBSD]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[soekris]]></category>

		<guid isPermaLink="false">http://slagwerks.com/blog/?p=61</guid>
		<description><![CDATA[In the market for a reliable, cheap, low power firewall, and already familiar with OpenBSD &#38; PF, I&#8217;ve been eying the Soekris line of products. This project looks like it&#8217;ll be just a little more involved than buying something off the shelf, but way more flexible, and have more parts in common with other stuff [...]]]></description>
			<content:encoded><![CDATA[<p>In the market for a reliable, cheap, low power firewall, and already familiar with OpenBSD <span class="amp">&amp;</span> <span class="caps">PF</span>, I&#8217;ve been eying the <a href="https://www.soekris.com/">Soekris</a> line of products. This project looks like it&#8217;ll be just a little more involved than buying <a href="http://www.newegg.com/Product/Product.aspx?Item=N82E16833122081">something off the shelf</a>, but way more flexible, and have more parts in common with other stuff I&#8217;m already&nbsp;using.</p>
<p>From my research, it looks like the necessary pieces&nbsp;are:</p>
<ul>
<li><a href="https://www.soekris.com/shop/product_info.php?products_id=75">Soekris 4501 <span class="amp">&amp;</span> case</a> -&nbsp;$173</li>
<li><a href="https://www.soekris.com/shop/product_info.php?products_id=131">power supply</a> -&nbsp;$11</li>
<li><a href="http://www.newegg.com/Product/Product.aspx?Item=N82E16820171353">2 <span class="caps">GB</span> SanDisk <span class="caps">CF</span></a> -&nbsp;$26</li>
<li><a href="http://www.newegg.com/Product/Product.aspx?Item=N82E16820401803"><span class="caps">USB</span> card reader</a> - $12 (to write to the <span class="caps">CF</span> card,&nbsp;naturally)</li>
<li><a href="http://www.amazon.com/Cables-Go-26886-Serial-Adapter/dp/B000067RVJ/ref=pd_bxgy_e_text_b">Null Modem <span class="amp">&amp;</span> <span class="caps">USB</span> &lt;-&gt; <span class="caps">DB9</span> cable</a> - $27 (no hardware with <span class="caps">DB9</span>&nbsp;around)</li>
</ul>
<p>So, for about $250 + some shipping, and a bit of fiddling around time, this could be a pretty robust solution. I&#8217;m not sure I&#8217;d care to work out all the installation and configuration details myself, but there are <a href="http://michiel.vanbaak.info/soekrisobsdcarp.htm">a couple</a> <a href="http://glozer.net/soekris/soekris.html">guides</a> to getting everything up <span class="amp">&amp;</span> running. I&#8217;ll certainly add my own notes if I go through with&nbsp;this.</p>
]]></content:encoded>
			<wfw:commentRss>http://slagwerks.com/blog/index.php/2008/06/25/planning-soekris-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Data Connectors Tech-Security Conference</title>
		<link>http://slagwerks.com/blog/index.php/2008/06/24/data-connectors-tech-security-conference/</link>
		<comments>http://slagwerks.com/blog/index.php/2008/06/24/data-connectors-tech-security-conference/#comments</comments>
		<pubDate>Tue, 24 Jun 2008 13:23:52 +0000</pubDate>
		<dc:creator>joe</dc:creator>
				<category><![CDATA[Boston]]></category>
		<category><![CDATA[conferences]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://slagwerks.com/blog/?p=59</guid>
		<description><![CDATA[I spent part of last Wednesday at the Boston Tech-Security Conference, held at lovely UMass Boston. Getting me there was a triumph of email marketing by hosts Data Connectors, as I hadn&#8217;t heard of this series and couldn&#8217;t really find any 3rd party accounts on the web. That, and it was free. Since I&#8217;m newly [...]]]></description>
			<content:encoded><![CDATA[<p>I spent part of last Wednesday at the <a href="http://www.dataconnectors.com/events/2008/06boston/agenda.asp">Boston Tech-Security Conference</a>, held at lovely UMass Boston. Getting me there was a triumph of email marketing by hosts Data Connectors, as I hadn&#8217;t heard of this series and couldn&#8217;t really find any 3rd party accounts on the web. That, and it was free. Since I&#8217;m newly back in a higher-level <span class="caps">IT</span> administrative capacity after years of just focusing on web application security, I decided to give the conference a&nbsp;try.</p>
<p>First impressions (after noting how unfriendly the UMass campus is to bicycles) were of an absence of buzz. Many vendors hanging around in one room, and then a vendor representative giving a traditional one-way presentation in the next room. After attending a few <a href="http://www.barcampboston.org/">barcamps</a>, it really seems to me that a more interactive format would benefit everyone involved. This conference was clearly driven by the vendors, but it seems to me that it&#8217;d be in their best interests to learn more about their potential customers&#8217;  interests and concerns, rather than broadcasting a sales&nbsp;message.</p>
<p>Despite the one-to-manyness, the presentations I made it to varied quite a bit. A few did a good survey of some aspect of security, and then tied that discussion into the vendor&#8217;s offerings right at the end. Others were basically just sales pitches. Guess which kind lost more of the&nbsp;audience?</p>
<h2>new concepts to&nbsp;me</h2>
<p><a href="http://en.wikipedia.org/wiki/Network_Access_Control"><span class="caps">NAC</span></a> - Network Admission Control. Folks will sell you systems that go beyond requiring just a username / password combo to get on a given network, by combining checks on device <span class="caps">MAC</span> / <span class="caps">IP</span>, allowed hours of operation, and presence and activity of specified software. <a href="http://packetfence.org/">Packetfence</a> looks like a promising open source&nbsp;<span class="caps">NAC</span>.</p>
<p><a href="http://en.wikipedia.org/wiki/Intrusion-prevention_system"><span class="caps">IPS</span></a> - Intrusion Prevention System. If I&#8217;m understanding correctly, these go beyond IDSes by taking some action such as updating firewall rules when naughtiness is detected. It looks like <a href="http://www.snort.org/">Snort</a> has been able to do this sort of thing for a while, also <a href="http://www.openbsd.org/faq/pf/"><span class="caps">PF</span> has</a> some related&nbsp;capabilities.</p>
<h2>notable&nbsp;speakers</h2>
<p>Ming Fu of <a href="http://www.lumension.com/">Lumension</a> introduced me to the concept of <a href="http://neologasm.org/neologasm/2007/07/thumbsuck.html">thumbsucking</a>&thinsp;&#8212;&thinsp;apparently the new hotness in social engineering attacks is to leave <span class="caps">USB</span> drives with said software lying about in parking lots, expecting that some percentage will be picked up <span class="amp">&amp;</span> plugged in&#8230; nasty! Lumension&#8217;s tie-in is that they have a product that allows strictly defined device access controls for windows boxes, so you could set up rules that would prevent employee accounts from mounting any <span class="caps">USB</span> devices, and only allow admins to mount <span class="caps">USB</span> devices already encrypted with your organization&#8217;s&nbsp;key.</p>
<p>Ken Pappas of <a href="http://toplayer.com/">Top Layer Networks</a> gave a high-level rundown on the overall tech security situation, and managed to do it with not an ounce of sales pitch. Authentic confidence is an excellent marketing tool, and Ken&#8217;s got that. His early remarks included a shout-out to the Boston chapter of the <a href="http://blogs.villagevoice.com/runninscared/archives/2008/02/hunter_students.php">possibly shooting-to-kill InfraGard</a>. He then went on to summarize the state of security in &#8216;08, which is basically: not that great. Incidence rates are going up, the range of attackers is increasing in professionalism and skill at the top end <em>and</em> becoming even less sophisticated (i.e. lower barrier to entry) on the low-end with easily available point-and-click tools for launching mail bombs, etc. Those of us responsible for computers attached to networks definitely need to be budgeting some of our time to keep up with the evolving threats, regardless of whether we&#8217;re aware of any particular adversary that&#8217;s out to get us or our&nbsp;data.</p>
<h2>takeaway</h2>
<p>It&#8217;s important to get away from the daily stream of projects periodically, to think about things from a higher level. Vendory as this conference was, it did give me that opportunity, and I did re-prioritize my <span class="caps">TODO</span> list at the end of the&nbsp;day.</p>
<p>The downside: I hadn&#8217;t thought through how many calls <span class="amp">&amp;</span> emails I was setting myself up for receiving from the conference vendors. <span class="caps">FYI</span>, I am 100% of the time never going to spend money with someone who calls me out of the blue and interrupts whatever I&#8217;m working on. Send me an email, and I&#8217;ll file it for processing at an appropriate&nbsp;time.</p>
]]></content:encoded>
			<wfw:commentRss>http://slagwerks.com/blog/index.php/2008/06/24/data-connectors-tech-security-conference/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>cross another shared host off the list</title>
		<link>http://slagwerks.com/blog/index.php/2008/02/08/cross-another-shared-host-off-the-list/</link>
		<comments>http://slagwerks.com/blog/index.php/2008/02/08/cross-another-shared-host-off-the-list/#comments</comments>
		<pubDate>Fri, 08 Feb 2008 22:23:33 +0000</pubDate>
		<dc:creator>joe</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[ISPs]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://slagwerks.com/blog/index.php/2008/02/08/cross-another-shared-host-off-the-list/</guid>
		<description><![CDATA[Just opened my first support ticket with the shared host Site5, and was shocked to see that every email generated by the process includes my username and password. Granted, these credentials only apply to their helpdesk site, but this is still so fundamentally stupid that I feel completely justified in avoiding them in the future.&#160;WTF.]]></description>
			<content:encoded><![CDATA[<p>Just opened my first support ticket with the shared host Site5, and was shocked to see that every email generated by the process includes my username <strong>and password</strong>. Granted, these credentials only apply to their helpdesk site, but this is still so fundamentally stupid that I feel completely justified in avoiding them in the future.&nbsp;<span class="caps">WTF</span>.</p>
]]></content:encoded>
			<wfw:commentRss>http://slagwerks.com/blog/index.php/2008/02/08/cross-another-shared-host-off-the-list/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
