<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[[SecurityRatty] tag: oversee]]></title>
    <link>http://securityratty.com/tag/oversee</link>
    <description></description>
    <pubDate>Wed, 26 Dec 2007 13:14:25 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Colorado Division of Motor Vehicles cited in audit report]]></title>
      <link>http://securityratty.com/article/dbed3997c39ebff2c2a793a72849fb6e</link>
      <guid>http://securityratty.com/article/dbed3997c39ebff2c2a793a72849fb6e</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
7/9/08

Organization
State of Colorado

Contractor/Consultant/Branch
Department of Revenue
Division of Motor Vehicles

Victims
Residents

Number...]]></description>
      <content:encoded><![CDATA[Technorati Tag: <a href="http://technorati.com/tag/security+breach" rel="tag">Security Breach</a><br><br>
<img src="http://breachblog.com/images/95781-88451/coloradodmv.jpg" width="200" align="right" height="101"><font size="2"><strong>Date Reported: </strong><br>7/9/08<br><br><strong>Organization: </strong><br><a href="http://www.colorado.gov/">State of Colorado</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.revenue.state.co.us/main/home.asp">Department of Revenue</a> <br><a href="http://www.revenue.state.co.us/mv_dir/home.asp">Division of Motor Vehicles</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Residents<br><br><span style="font-weight: bold;">Number Affected:</span><br>~3,400,000<br><br><span style="font-weight: bold;">Types of Data:</span><br>"names, addresses, dates of birth and Social Security numbers"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"The Division of Motor Vehicles put 3.4 million Coloradans at risk of identity theft due to flaws in the way driver's-license information is handled, lawmakers learned Tuesday at an interim transportation committee hearing."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://origin.denverpost.com/headlines/ci_9822063">The Denver Post</a> <br><a href="http://www.leg.state.co.us/OSA/coauditor1.nsf/All/2732807492E26F3387257464005FCB5D/$FILE/1912%20DriverLicense%20Perf%20May%202008.pdf">Report of The State Auditor, Driver's License and Identification (ID) Card Security</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Jessica Fender, The Denver Post - Brought to the attention of The Breach Blog by an informed reader.<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above:<br><br>The Division of Motor Vehicles put 3.4 million Coloradans at risk of identity theft due to flaws in the way driver's-license information is handled, lawmakers learned Tuesday at an interim transportation committee hearing.<br><br>The DMV regularly sends large batches of personal information over the Internet without encryption and has failed to properly limit access to its database, according to a recent audit.<br><em>[Evan] The audit report is <a href="http://www.leg.state.co.us/OSA/coauditor1.nsf/All/2732807492E26F3387257464005FCB5D/$FILE/1912%20DriverLicense%20Perf%20May%202008.pdf">here</a>.</em><br><br>At one point, 33 former DMV employees could access names, addresses, dates of birth and Social Security numbers — some workers more than a year after their departure<br><br>Revenue Department leaders who oversee the division say they are working to hire internal watchdogs and build up their technological defenses.<br><span style="font-style: italic;">[Evan] This is putting the cart before the horse.&nbsp; After reading some of the audit results it is clear to me that there is no information security strategy, no effective information security management, and no formal information security program.&nbsp; These administrative issues need to be addressed well before "technological defenses" should be.&nbsp; Addressing "technological defenses" first is often times wasteful and disjointed.</span><br><br>But the state, facing a budget shortfall, will have no additional money in the foreseeable future for new computer systems.<br><span style="font-style: italic;">[Evan] Then get creative!&nbsp; No or little money is a poor excuse for not doing the right thing.&nbsp; Many times, we find that an organization actually saves money through effective information security management.&nbsp; Fix the administrative issues and formalize the information security program first.&nbsp; I don't know much about the Colorado state government, but I do know that other state governments are wasteful and disorganized.&nbsp; Information security, when aligned with organizational goals and objectives (not IT) can help organize and cut waste.</span><br><br>Cyber security alone is a $1.5 million problem that will be tough to solve, said Roxy Huber, Revenue Department executive director.<br><span style="font-style: italic;">[Evan] I wonder where the $1.5 million dollar figure comes from.&nbsp; We can secure a heckuva lot of infrastructure (and information) with that kind of money.&nbsp; I get a kick out of "Cyber security".</span><br><br>"To tell you that I'm going to have the tools to do what I need to do, I don't know where they're going to come from," Huber said. "But we will continue to do the best with the tools that we have."<br><span style="font-style: italic;">[Evan] Where do I start with this comment?&nbsp; The first tool to use is the one between your ears.</span><br><br>Colorado ranks eighth in the nation in identity-theft complaints per person and first in the nation when it comes to general fraud reports.<br><span style="font-style: italic;">[Evan] This should tell you something!&nbsp; It is even more troubling if your own state government contributes to the problem.</span><br><br>On average, those frauds cost victims $4,041 each for a total of $41.3 million in 2007<br><br>Auditors said the DMV's method for handling sensitive information was "fragmented, disorganized and poorly planned," <br><span style="font-style: italic;">[Evan] Yeah, ya think?</span><br><br>No one person is responsible for security<br><span style="font-style: italic;">[Evan] Or is it no one is responsible for security?</span><br><br>High turnover - 60 percent of entry-level workers leave during their first year - and low, $26,280-a-year starting salaries make fraud more attractive and management more difficult, DMV officials said.<br><span style="font-style: italic;">[Evan] This is another problem that contributes significantly to the risk.</span><br><br>While employees have been caught issuing hundreds of fraudulent licenses, there are no known instances of identity theft or information security breaches, said Department of Revenue spokesman Mark Couch.<br><span style="font-style: italic;">[Evan] Come on.&nbsp; Not that we know of anyway.&nbsp; Don't you think that the risk is much higher if a person has already demonstrated that he/she is willing to step over the line?</span><br><br>"It's not like we have a completely defenseless system," Couch said. The audit "says that we need to take more steps."<br><span style="font-style: italic;">[Evan] Not completely defenseless, but like protecting a bicycle with a rope.</span><br><br>"Without the appropriate resources, there's no way we can hold you accountable for doing some of the things you're expected to do," said Sen. Nancy Spence, R-Centennial.<br><span style="font-style: italic;">[Evan] This kind of talk does not help the cause and does little to serve constituents.&nbsp; I am not close to this issue, but so many of the things I have read about this breach point to mismanagement more than a lack of appropriate resources.</span><br><br>Some problems already have been fixed.<br><br>The 33 former employees with database access immediately had their passwords deactivated once auditors identified them, and the DMV now compiles monthly lists of departed workers to prevent future lapses<br><br>The division has a long-standing policy of redacting the last four digits of Social Security numbers before they're transmitted, and the division plans to encrypt all transmitted information by June 2009. <br><span style="font-style: italic;">[Evan] What?&nbsp; A year?&nbsp; This exposure is now public knowledge and will continue for a year?</span><br><br><span style="font-weight: bold;">Commentary:</span><br>Due to the fact that I was a little more critical in my comments above, I should express that these are my opinions and beliefs based on my experiences and knowledge.&nbsp; Take the comments for what they are worth.<br><br>There seems like there is a lot of work that needs to be done at the Colorado Department of Revenue and Division of Motor Vehicles.&nbsp; The work must start at the top.&nbsp; Somebody needs to step up and fill the role as the "person responsible for security". <br><br><span style="font-weight: bold;">Past Breaches:</span><br><span style="font-weight: bold;">State of Colorado:</span><br>April, 2008 - <a href="http://breachblog.com/2008/04/30/collegeinvest.aspx">CollegeInvest external hard drive goes missing </a><br></font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/07/11/coloradodmv.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Fri, 11 Jul 2008 05:18:07 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/information security breaches">information security breaches</category>
      <category domain="http://securityratty.com/tag/sensitive information">sensitive information</category>
      <category domain="http://securityratty.com/tag/information security strategy">information security strategy</category>
      <category domain="http://securityratty.com/tag/information security program">information security program</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/cyber security">cyber security</category>
      <source url="http://breachblog.com/2008/07/11/coloradodmv.aspx">Colorado Division of Motor Vehicles cited in audit report</source>
    </item>
    <item>
      <title><![CDATA[NSA Monitoring U.S. Government Internet Traffic]]></title>
      <link>http://securityratty.com/article/4c99e3c25ea9be5bac7d3e8f5f29e803</link>
      <guid>http://securityratty.com/article/4c99e3c25ea9be5bac7d3e8f5f29e803</guid>
      <description><![CDATA[I have mixed feeling about this , but in general think it is a good idea: President Bush signed a directive this month that expands the intelligence community's role in monitoring Internet traffic to...]]></description>
      <content:encoded><![CDATA[<p>I have mixed feeling about <a href="http://www.washingtonpost.com/wp-dyn/content/article/2008/01/25/AR2008012503261.html">this</a>, but in general think it is a good idea:</p>

<blockquote>President Bush signed a directive this month that expands the intelligence community's role in monitoring Internet traffic to protect against a rising number of attacks on federal agencies' computer systems.

<p>The directive, whose content is classified, authorizes the intelligence agencies, in particular the National Security Agency, to monitor the computer networks of all federal agencies -- including ones they have not previously monitored.</p>

<p>[...]</p>

<p>The classified joint directive, signed Jan. 8 and called the National Security Presidential Directive 54/Homeland Security Presidential Directive 23, has not been previously disclosed. Plans to expand the NSA's role in cyber-security were reported in the Baltimore Sun in September.</p>

<p>According to congressional aides and former White House officials with knowledge of the program, the directive outlines measures collectively referred to as the "cyber initiative," aimed at securing the government's computer systems against attacks by foreign adversaries and other intruders. It will cost billions of dollars, which the White House is expected to request in its fiscal 2009 budget.</p>

<p>[...]</p>

<p>Under the initiative, the NSA, CIA and the FBI's Cyber Division will investigate intrusions by monitoring Internet activity and, in some cases, capturing data for analysis, sources said.</p>

<p>The Pentagon can plan attacks on adversaries' networks if, for example, the NSA determines that a particular server in a foreign country needs to be taken down to disrupt an attack on an information system critical to the U.S. government. That could include responding to an attack against a private-sector network, such as the telecom industry's, sources said.</p>

<p>Also, as part of its attempt to defend government computer systems, the Department of Homeland Security will collect and monitor data on intrusions, deploy technologies for preventing attacks and encrypt data. It will also oversee the effort to reduce Internet portals across government to 50 from 2,000, to make it easier to detect attacks.</blockquote></p>

<p>My concern is that the NSA is doing the monitoring.  I simply don't like them monitoring domestic traffic, even domestic government traffic.</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=0W2sJwE"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=0W2sJwE" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=51318hE"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=51318hE" border="0"></img></a>
</div>]]></content:encoded>
      <pubDate>Mon, 04 Feb 2008 03:30:10 +0000</pubDate>
      <category domain="http://securityratty.com/tag/government">government</category>
      <category domain="http://securityratty.com/tag/nsa">nsa</category>
      <category domain="http://securityratty.com/tag/detect attacks">detect attacks</category>
      <category domain="http://securityratty.com/tag/attacks">attacks</category>
      <category domain="http://securityratty.com/tag/domestic government traffic">domestic government traffic</category>
      <category domain="http://securityratty.com/tag/plan attacks">plan attacks</category>
      <category domain="http://securityratty.com/tag/white house officials">white house officials</category>
      <category domain="http://securityratty.com/tag/white house">white house</category>
      <category domain="http://securityratty.com/tag/data">data</category>
      <source url="http://www.schneier.com/blog/archives/2008/02/nsa_monitoring.html">NSA Monitoring U.S. Government Internet Traffic</source>
    </item>
    <item>
      <title><![CDATA[Who says Politics doesn't pay and why can't I find clients with pockets this deep?]]></title>
      <link>http://securityratty.com/article/72ce20f130c78da874e849da0a3491a9</link>
      <guid>http://securityratty.com/article/72ce20f130c78da874e849da0a3491a9</guid>
      <description><![CDATA[I have never drank the political coolaid. I have little faith in big party politics. Give me an independent politician who does not have to toe a party line and I'll show you a politician who has half...]]></description>
      <content:encoded><![CDATA[<a href="http://bp0.blogger.com/_1UFxC-OgSnA/R5UUuLmhiBI/AAAAAAAAADc/ODAIe-i9zzE/s1600-h/Fotolia_3032426_S.jpg"><img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;" src="http://bp0.blogger.com/_1UFxC-OgSnA/R5UUuLmhiBI/AAAAAAAAADc/ODAIe-i9zzE/s320/Fotolia_3032426_S.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5158051731843680274" /></a><br />I have never drank the political coolaid.  I have little faith in big party politics.  Give me an independent politician who does not have to toe a party line and I'll show you a politician who has half a chance of being a decent advocate of the people.    <br /><span id="fullpost"><br />I think one of the greatest wrongs that politicans commit is in their thinking of voters as idiots.  I use the Washington Post article of 1/17/08 as a prime example.  Staff writer Carrie Johnson writes in the Business section that GAO investigators will look into "NO-BID Contracts" irregularities  involving the Justice Department.<br /><br />This all came about when a firm led by the former Attorney General, John D. Ashcroft, drew attention for receiving lucrative (more like outrageous) contracts to oversee companies accused of fraud and other wrong doings.  One firm in particular, Zimmer (famous for their "Zimmer Frames"), agreed to pay Mr. Ashcroft's firm between $28 and $52 million dollars to resolve kickback allegations.  <br /><br />Two questions spring to mind; 1) How much was the original "kickback" amount when they can now afford to pay out $28,000,000.00 to $52,000,000.00? and 2) Does the recieving of (as much as) $52 million dollars by a former high ranking politician from a company with it's back up against a wall not sound like a "kickback" in of itself?<br /><br />What does Mr. Ashcroft's firm deliver as a result of this outlandish payment?  Well, as a "monitor", they will make sure that Zimmer stops making illicit payment to doctors for using Zimmer products.  There's got to be more than that, surely?  Kind of.  Ashcroft said that he has already made several trips to Indiana to "understand Zimmer's troubles."  Several trips to Indiana for $52 million dollars?  Did they buy their own luxury jet just for those trips?<br /><br />Private investigation firms all across America conducts similar services on a daily basis, only for a mere fraction of what Zimmer has paid to this former Government official.  As a private security business owner I can attest to the fact that a typical investigation company would be delighted and thrilled to receive 2% - 3% of this amount and in so doing would employ highly skilled investigators with backgrounds and certifications such as Certified Fraud examiner in the FBI, United Nations and other Govt. and corporate investigative agencies.  <br /><br />You can be sure that Mr. Ashccroft is not the only former government offical riding the gravy train.  The article states that several other former government officials with ties to the Bush administration have been awarded similar contracts since 2001.<br />      <br /></span><div class="blogger-post-footer">Visit Sexton Executive Security at www.sextonsecurity.com</div>]]></content:encoded>
      <pubDate>Mon, 21 Jan 2008 18:10:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/zimmer">zimmer</category>
      <category domain="http://securityratty.com/tag/zimmer products">zimmer products</category>
      <category domain="http://securityratty.com/tag/zimmer frames">zimmer frames</category>
      <category domain="http://securityratty.com/tag/million dollars">million dollars</category>
      <category domain="http://securityratty.com/tag/firm">firm</category>
      <category domain="http://securityratty.com/tag/firm deliver">firm deliver</category>
      <category domain="http://securityratty.com/tag/zimmer stops">zimmer stops</category>
      <category domain="http://securityratty.com/tag/resolve kickback allegations">resolve kickback allegations</category>
      <category domain="http://securityratty.com/tag/contracts">contracts</category>
      <source url="http://www.thebulletproofblog.com/2008/01/who-says-politics-doesnt-pay-and-why.html">Who says Politics doesn't pay and why can't I find clients with pockets this deep?</source>
    </item>
    <item>
      <title><![CDATA[House committee issues report and finds fault with TSA web site]]></title>
      <link>http://securityratty.com/article/1365ead8771d4a0c8ff5da4a55363ea2</link>
      <guid>http://securityratty.com/article/1365ead8771d4a0c8ff5da4a55363ea2</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
1/13/08

Organization
U.S. Government

Contractor/Consultant/Branch
Transportation Security Administration (TSA
Desyne Web Services

Victims
Certain...]]></description>
      <content:encoded><![CDATA[Technorati Tag: <a href="http://technorati.com/tag/security+breach" rel="tag">Security Breach</a><br><br>
<img src="http://breachblog.com/images/95781-88451/tsa.jpg" align="right" height="68" width="198"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>1/13/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.usa.gov/" target="_blank"> U.S. Government</a><br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.tsa.gov/" target="_blank"> Transportation Security Administration (TSA)</a><br><a href="http://www.desyne.com/" target="_blank"> Desyne Web Services</a><br><br><span style="font-weight: bold;">Victims:</span><br>Certain people that used the TSA traveler redress website between October 6, 2006 and February 13, 2007.<br><br><span style="font-weight: bold;">Number Affected:</span><br>"thousands"<br><br><span style="font-weight: bold;">Types of Data:</span><br>Name, Social Security number, birth date, birth place, sex, height, weight, hair color, eye color, address, and home and work telephone number.<br><br><span style="font-weight: bold;">Breach Description:</span><br>According to the January, 2008 United States House of Representatives Committee on Oversight and Government Reform report titled <span style="font-style: italic;">INFORMATION SECURITY BREACH AT TSA: THE TRAVELER REDRESS WEBSITE</span>;<br>"In October 2006, the Transportation Security Administration launched a website to help travelers whose names were erroneously listed on airline watch lists. This redress website had multiple security vulnerabilities: it was not hosted on a government domain; its homepage was not encrypted; one of its data submission pages was not encrypted; and its encrypted pages were not properly certified. These deficiencies exposed thousands of American travelers to potential identity theft."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://oversight.house.gov/documents/20080111092648.pdf" target="_blank"> The official Committee on Oversight and Government Reform report</a> <br><a href="http://www2.csoonline.com/blog_view.html?CID=33452" target="_blank"> The CSO Online Story</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The United States House of Representatives Committee on Oversight and Government Reform, and special credit to Chris "Boarding Pass Hacker" Soghoian.<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>At the request of Chairman Henry Waxman, Committee staff have been investigating how TSA could have launched a website that violated basic operating standards of web security and failed to protect travelers’ sensitive personal information.<br><em>[Evan] For those who don't know, Henry Waxman represents </em></font><em><font size="-1">the 30th District of California in the House.</font></em><br><font size="2"><br>As this report describes, these security breaches can be traced to TSA’s poor acquisition practices, conflicts of interest, and inadequate oversight. <br><br>The report finds: <br></font><br><ul><li><font size="2">TSA awarded the website contract without competition.</font> </li></ul><br>TSA gave a small, Virginia-based contractor called Desyne Web Services a no-bid contract to design and operate the redress website. According to an internal TSA investigation, the “Statement of Work” for the contract was “written such that Desyne Web was the only vendor that could meet program requirements.”<br><br><ul><li>The TSA official in charge of the project was a former employee of the contractor.&nbsp;&nbsp;&nbsp;&nbsp; </li></ul><br>The TSA official who was the “Technical Lead” on the website project and acted as the point of contact with the contractor had an apparent conflict of interest. He was a former employee of Desyne Web Services and regularly socialized with Desyne’s owner.<br><br><ul><li>TSA did not detect the website’s security weaknesses for months.&nbsp;&nbsp;&nbsp;&nbsp; </li></ul><br>The redress website was launched on October 6, 2006, and was not taken down until after February 13, 2007, when an internet blogger exposed the security vulnerabilities. During this period, TSA Administrator Hawley testified before Congress that the agency had assured “the privacy of users and the security of the system” before its launch. Thousands of individuals used the insecure website, including at least 247 travelers who submitted large amounts of personal information through an insecure webpage.<br><br><ul><li>TSA did not provide sufficient oversight of the website and the contractor.&nbsp;&nbsp;&nbsp;&nbsp; </li></ul><br>The internal TSA investigation found that there were problems with the “planning, development, and operation” of the website and that the program managers were “overly reliant on contractors for information technology expertise” and had failed to properly oversee the contractor, which as a result, “made TSA vulnerable to non-performance and poor quality work by the contractor.” <br><font size="2"><br>Neither Desyne nor the Technical Lead on the traveler redress website has been sanctioned by TSA for their roles in the deployment of an insecure website. TSA continues to pay Desyne to host and maintain two major web-based information systems: TSA’s claims management system and a government-wide traveler redress program. TSA has taken no steps to discipline the Technical Lead, who still holds a senior program management position at TSA. <br><br>After conducting a detailed security accreditation review of the traveler redress website, TSA’s Chief Information Security Officer (CISO) granted the website a 12-month “Authority to Operate” in September 2006. The CISO did not detect a number of glaring security problems affecting the website when it went live on October 6, 2006.<br><span style="font-style: italic;">[Evan] The TSA CISO is </span><a style="font-style: italic;" href="http://www.publicsectorinstitute.net/ELetters/EGovernment/v5n2/CyberArticles.lsp#Trust" target="_blank"> Patti Titus</a><span style="font-style: italic;">.&nbsp; I don't know how these security issues could have been missed!</span><br><br>The security vulnerabilities of the website included the following: <br></font><ul><li><font size="2">The Site Was Not Hosted on a Government Domain.</font></li></ul><font size="2">Instead of being hosted on a government web domain (e.g., “tsa.gov”), the redress system was hosted on a commercial domain operated by the contractor (http//rms.desyne.com). When they left the government domain, visitors to the redress management site lost any assurance they were visiting a legitimate government website<br><br></font><ul><li><font size="2">The Home Page Was Not Encrypted</font></li></ul><font size="2">The website home page did not have an encrypted “secure socket layer” (SSL) with an “https” protocol identifier. As a result, every time travelers visited the site to check on the status of their applications, the control numbers they entered to access their files were vulnerable to theft. Once they obtained these numbers, attackers would have access to travelers’ personal information.<br><br></font><ul><li><font size="2">The Submission Page Was Not Encrypted</font></li></ul><font size="2">One of the site’s links that allowed travelers to submit personal information was also unsecured. Although travelers could access an encrypted page to submit personal information, a link reading “file your application online” transferred users to an unsecured site. Travelers submitting their name, address, Social Security numbers, eye color, place of birth, and other sensitive personal information through this link had no protection from attack<br><br></font><ul><li><font size="2">Encrypted Pages Were Not Properly Certified</font></li></ul><font size="2">Although other web pages within the site were SSL-protected, they were not properly certified. Under standard web security practices, operators of SSL-protected websites obtain third-party certifications to assure users that an outside party has approved the web site’s security measures. Instead of the proper third-party certification, the site had only an expired certification that Desyne itself had generated.<br><br><span style="font-weight: bold;">Chris Soghoian's Comments:</span><br>"the appearance of the site was so poor that he first suspected it was a “phishing” site"<br><br>"Incredible that they would take the site live using a self-signed certificate. It shows major incompetence (elementary oversight should have caught this) and at Desyne, Inc. Someone is either too stupid or too cheap to purchase a real SSL certificate before putting up a site that asks for personal data. This is Web Development 101. Anyone who has ever worked on an ecommerce site should [be] aware of the issues."<br><br>After Mr. Soghoian posted his analysis of the security vulnerabilities affecting the traveler redress website, TSA moved quickly to transfer the site to a more secure Department of Homeland Security domain. <br><br>TSA also contacted the individuals who had submitted their personal information through the unsecured “file your application online” link to inform them that they were at a heightened risk of identity theft.<br><br>To date, TSA has awarded Desyne almost $500,000 worth of no-bid contracts to provide web services to TSA and DHS<br><span style="font-style: italic;">[Evan] $500,000!?&nbsp; As a taxpayer, I am miffed.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>The investigation and report by the House Committee on Oversight and Government Reform is excellent.&nbsp; A very good read.<br><br>Interesting, from the <a href="http://www.tsa.gov/research/privacy/faqs.shtm" target="_blank"> TSA Privacy FAQs</a>:<br><span style="font-weight: bold;">Question</span>: How can TSA ensure the security of personal information it collects?<br><br><span style="font-weight: bold;">Answer</span>: TSA takes a number of steps to ensure the security of personal information it collects about individuals.&nbsp; TSA’s Office of Privacy Policy &amp; Compliance collaborates with the Chief Information Security Office (CISO) to work with program offices during the design and implementation of systems to ensure compliance with the Federal Information Security Management Act (FISMA) and the Privacy Act, 5 U.S.C. §552a.&nbsp; In addition to design and implementation standards, the CISO ensures that the systems are secured against unauthorized use through the use of a layered, defense-in-depth security approach involving procedural and information security safeguards as mandated by FISMA following National Institute of Standards and Technology (NIST) guidance.<br><br>Am I missing something? <br><br><span style="font-weight: bold;">Past Breaches:</span><br>October, 2007 - <a href="http://breachblog.com/2007/10/18/tsa.aspx" target="_blank"> Stolen laptops contained sensitive TSA information</a></font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/01/15/tsa2.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 15 Jan 2008 06:35:53 +0000</pubDate>
      <category domain="http://securityratty.com/tag/tsa">tsa</category>
      <category domain="http://securityratty.com/tag/website">website</category>
      <category domain="http://securityratty.com/tag/website contract">website contract</category>
      <category domain="http://securityratty.com/tag/traveler redress website">traveler redress website</category>
      <category domain="http://securityratty.com/tag/tsa moved quickly">tsa moved quickly</category>
      <category domain="http://securityratty.com/tag/security breach">security breach</category>
      <category domain="http://securityratty.com/tag/information security breach">information security breach</category>
      <category domain="http://securityratty.com/tag/security vulnerabilities">security vulnerabilities</category>
      <category domain="http://securityratty.com/tag/multiple security vulnerabilities">multiple security vulnerabilities</category>
      <source url="http://breachblog.com/2008/01/15/tsa2.aspx">House committee issues report and finds fault with TSA web site</source>
    </item>
    <item>
      <title><![CDATA[Risky by association]]></title>
      <link>http://securityratty.com/article/aa23c1fb2c5a1e123395dd987271457a</link>
      <guid>http://securityratty.com/article/aa23c1fb2c5a1e123395dd987271457a</guid>
      <description><![CDATA[The holiday season gave media and industry one more opportunity to discuss Mattels massive product recalls this year, and admittedly, I still find myself interested in the story. In this case, it was...]]></description>
      <content:encoded><![CDATA[<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span face="Times New Roman">The holiday season gave media and industry one more opportunity to discuss Mattel’s massive product recalls this year, and admittedly, I still find myself interested in the story.<span style="mso-spacerun: yes"> </span>In this case, it was the World Business Council for Sustainable Development’s article calling out Mattel’s </span><a href="http://www.wbcsd.org/plugins/DocSearch/details.asp?type=DocDet&amp;ObjectId=Mjc4NjA"><span face="Times New Roman">“Epiphany at Christmas”</span></a><span face="Times New Roman">.<span style="mso-spacerun: yes">&nbsp; </span></span></p>

<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"></p>





<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span face="Times New Roman">The revelation: “If it's got your company's name on it, it's your problem.”</span></p>

<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"></p>





<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span face="Times New Roman">At least, that’s according to the expert interviewed about taking responsibility when things go poorly.<span style="mso-spacerun: yes">&nbsp; </span>In reality however, Mattel has received praise in the past for its </span><a href="http://www.thecro.com/node/454"><span face="Times New Roman">responsible supply chain management</span></a><span face="Times New Roman"> — this is not an epiphany.<span style="mso-spacerun: yes">&nbsp; </span></span></p>

<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"></p>





<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span face="Times New Roman">Still, the company is taking steps to demonstrate its ongoing commitment with a new quality checking system and a responsibility organization to oversee product quality, labor standards, and sustainability...moves that CEO Robert Eckert calls “evolutionary, not revolutionary.”</span></p>

<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"></p>





<p class="MsoNormal" style="MARGIN: 0in 0in 1.5pt; mso-outline-level: 3"><span face="Times New Roman">But the lesson is a good one. It’s not just about managing outsourcers... it’s making sure they manage their outsourcers, and so on down the complex chain.<span style="mso-spacerun: yes">&nbsp; </span>Whether it’s product safety, social responsibility, or information security issues, supply chain management is getting more in-depth, and necessarily so, as the number and potential imapct of risks increase.<span style="mso-spacerun: yes">&nbsp; </span>For more on risk management with supply chain partners, check out </span><a href="http://www.forrester.com/Research/Document/0,7211,41884,00.html"><span face="Times New Roman">Best Practices: Successfully Managing Security And Risk In A Global Supply Chain.</span></a></p>]]></content:encoded>
      <pubDate>Wed, 26 Dec 2007 13:14:25 +0000</pubDate>
      <category domain="http://securityratty.com/tag/responsibility">responsibility</category>
      <category domain="http://securityratty.com/tag/responsibility organization">responsibility organization</category>
      <category domain="http://securityratty.com/tag/oversee product quality">oversee product quality</category>
      <category domain="http://securityratty.com/tag/information security issues">information security issues</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/quality">quality</category>
      <category domain="http://securityratty.com/tag/supply chain partners">supply chain partners</category>
      <category domain="http://securityratty.com/tag/social responsibility">social responsibility</category>
      <category domain="http://securityratty.com/tag/epiphany">epiphany</category>
      <source url="http://blogs.forrester.com/srm/2007/12/risky-by-associ.html">Risky by association</source>
    </item>
  </channel>
</rss>
