<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Information Security</title>
      <link>http://blog.vcu.edu/infosec/</link>
      <description></description>
      <language>en</language>
      <copyright>Copyright 2009</copyright>
      <lastBuildDate>Mon, 04 Aug 2008 16:12:02 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

      
      <item>
         <title>Think before you click &quot;send&quot;</title>
         <description><![CDATA[The Internet is littered with countless stories of individuals who sent emails they <a href="http://www.latimes.com/business/la-forbes-email9-2008jul09,0,888776.story">shouldn't have</a> or sent emails to <a href="http://articles.latimes.com/2008/may/21/business/fi-mozilo21">unintended recipients</a>.  Before you send an email, ensure that it's only going to go to the intended recipients and think twice about sending it if it could have a negative impact if it was read by an unintended recipient.

And if you are planning on sharing confidential VCU data with someone via email be sure to encrypt it or to utilize a different secure method to share it instead.  VCU's <a href="http://www.ts.vcu.edu/security/ismanagement/VCUSecurityStandardforEmail.pdf">Securty Standard for Transmission of Confidential Data Through Email</a> prohibits transmission of confidential data via email unless it's encrypted.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/08/think-before-you-click-send.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/08/think-before-you-click-send.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">email</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">encryption</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">policy</category>
        
         <pubDate>Mon, 04 Aug 2008 16:12:02 -0500</pubDate>
         
      </item>
      
      <item>
         <title>GIFAR attack - it looks like an image, but it has a malicious paylod</title>
         <description><![CDATA[At this week's Black Hat security conference, researchers will discuss an attack which they've coined the <a href="http://blogs.zdnet.com/security/?p=1619">GIFAR attack</a>.  The attack involves combining a JAR (Java Archive) file with another file, such as a GIF image file (GIF + JAR = GIFAR).  The user's browser would consider the file a valid image file and display it properly, but the Java Virtual Machine (JVM) on the user's computer would also treat it as a JAR file, executing the 2nd part of the file as a Java applet.  And for clarity, the JAR files can be combined with other file types, such as JPEG images or Word documents.

Why is this a problem?  It's a problem because many websites allow users to upload content and most of them are not doing a sufficient job of sanitizing the content.  Those websites which do perform input validation (sanitization) typically do little more than confirm that the uploaded file has an acceptable file extension.  And though some media coverage implies specific widely used websites such as Facebook, MySpace and Google may be vulnerable, this has the potential to impact any website which does insufficient user content sanitization.

As a users, you don't know which websites you interact with do sufficient sanitization. And if you're tricked into running a malicious Java applet, it will run with the same context of the website it was loaded from.  That means that the attacker could do things like hijack the user's session (gain unauthorized access to the website, masquerading as the target user).

And if a system has really bad security controls, it may even be possible to target a user on a trusted system behind the same firewall as the website in order to perform <a href="http://www.gnucitizen.org/blog/java-jar-attacks-and-features/ ">attacks against the server hosting the website</a>.

One of the researchers, Nathan McFeters, mentioned that this isn't the first such attack vector, and that even if Sun patches the JVM, <a href="http://blogs.zdnet.com/security/?p=1635">new attack vectors will arise</a>.  The lesson?  Don't trust content from users.  And properly sanitize it.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/08/gifar-attack-it-looks-like-an.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/08/gifar-attack-it-looks-like-an.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">input validation</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">vulnerability</category>
        
         <pubDate>Sat, 02 Aug 2008 09:33:10 -0500</pubDate>
         
      </item>
      
      <item>
         <title>SANS web application security course</title>
         <description><![CDATA[The SANS Institute is offering their Web Applications Security Essentials course (<a href="http://www.sans.org/training/description.php?mid=1042">SEC422</a>) via their @Home (webcast) program.  There's a 40% discount for those who attended their now defunct Web Application Security Workshop in the last 18 months.  VCU <a href="http://www.pubinfo.vcu.edu/web/sans/default.htm">hosted that course</a> last June and numerous VCU staff attended it.

<a href="https://www.sans.org/athome/about.php">@Home</a> consists of live webcasts, though if you miss any they're available via their archive.  The course is being taught by <a href="http://www.sans.org/training/instructors.php#Baccam">Tanya Baccam</a>.  For the lowest price, <a href=" https://www.sans.org/athome/details.php?nid=13124&utm_source=e-mail&utm_medium=invite&utm_content=20080611_@Home_SEC522_0908&utm_campaign=SANS_@Home&ref=29544">register</a> by August 6th.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/sans-web-application-security.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/sans-web-application-security.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">training</category>
        
         <pubDate>Thu, 31 Jul 2008 16:09:15 -0500</pubDate>
         
      </item>
      
      <item>
         <title>Application feature - alerting user of concurrent sessions</title>
         <description><![CDATA[Earlier this month Google's Gmail added several <a href="http://gmailblog.blogspot.com/2008/07/remote-sign-out-and-info-to-help-you.html">new security features</a> to the latest version of Gmail.

A user can now see a list of current open sessions associated with the user's account.  See an open session from an IP address you don't recognize or an access type you don't use (Mobile for example)?  It may be indicative of a compromised account.  Perhaps your password has been compromised or perhaps you accessed Gmail from a friend's laptop.  You can change your password (which you could already do, obviously), then click the "Sign out all other sessions" button.

Like web systems at many financial institutions, recent activity is also listed.  However, unlike most I've seen, Gmail shows activity from more than just the last login - the last 5 logins in fact.

When designing web apps, consider incorporating features like these.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/application-feature-alerting-u.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/application-feature-alerting-u.html</guid>
        
          <category domain="http://www.sixapart.com/ns/types#category">Information Security</category>
        
        
         <pubDate>Wed, 30 Jul 2008 14:58:29 -0500</pubDate>
         
      </item>
      
      <item>
         <title>Companies collect and share your data - check it for free</title>
         <description><![CDATA[Numerous private organizations collect data about you and share it with your creditors, employers and insurers.  The Fair Credit Reporting Act <a href="http://www.ftc.gov/bcp/conline/edcams/freereports/index.html">requires</a> that the 3 national consume reporting companies (Equifax, Experian and TransUnion) each provide you a free copy of your credit report at your request once every 12 months.  You can request all 3 at the same time or you can stagger them.  It's your choice.  The only authorized online source is <a href="https://www.annualcreditreport.com/">annualcreditreport.com</a>.  Some of the information in these reports may be inaccurate.  Fortunately, you have the right to dispute the information in order to get it corrected.

But other organizations have your information as well.  For example, ChoicePoint has 3 separate companies which maintain information on you - insurance claims, employment history and tenant history.  You can <a href="http://www.choicepoint.com/factact.html">request copies</a> of these reports for free as well.  However, if you're concerned about what may appear in a background check, it'll likely cost you since they often conduct research by contacting past employers, courts, and colleges you attended and they're not required to conduct that research for free.  And plenty of <a href="http://www.businessweek.com/magazine/content/08_23/b4087054129334.htm">background check horror stories </a>have been published.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/companies-collect-and-share-yo.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/companies-collect-and-share-yo.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">integrity</category>
        
         <pubDate>Mon, 28 Jul 2008 17:37:50 -0500</pubDate>
         
      </item>
      
      <item>
         <title>&quot;Spam King&quot; sentenced, but another spammer escapes</title>
         <description><![CDATA[In a victory for email recipients everywhere, "Spam King" Robert Soloway was <a href="http://www.scmagazineus.com/Spam-King-sentenced-to-47-months/article/112808/">sentenced</a> to 47 months in federal prison.  Soloway had been accused of violating the federal <a href="http://www.ftc.gov/bcp/conline/pubs/buspubs/canspam.shtm">CAN-SPAM Act</a>.  In loosely related news, convicted spammer Edward "Eddie" Davidson <a href="http://www.scmagazineus.com/Convicted-spammer-escapes-from-prison/article/112810/">escaped</a> from a minimum security federal prison camp in Colorado after serving 5 weeks of a 21 month sentence.  Perhaps the Spam King will be serve time in a facility that's a little more secure.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/spam-king-sentenced-but-anothe.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/spam-king-sentenced-but-anothe.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">legal</category>
        
         <pubDate>Fri, 25 Jul 2008 16:32:09 -0500</pubDate>
         
      </item>
      
      <item>
         <title>SSN exposure at University of Maryland</title>
         <description><![CDATA[The University of Maryland mailed parking brochures to about 24,000 students on July 1st.  Each student's Social Security number was <a href="http://chronicle.com/wiredcampus/article/3183/social-security-numbers-of-u-of-maryland-students-exposed">included on a mailing label</a> attached to the brochure.  The school discovered the problem on the 8th.  It's recommending that recipients place a free 90 day fraud alert on their consumer credit and the school is offering a <a href="http://www.transportation.umd.edu/parkingmailer/">free year of credit monitoring</a> with Equifax.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/ssn-exposure-at-university-of.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/ssn-exposure-at-university-of.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">breach</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">confidentiality</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">highered</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">ssn</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">unauthorized disclosure</category>
        
         <pubDate>Thu, 24 Jul 2008 10:59:33 -0500</pubDate>
         
      </item>
      
      <item>
         <title>The cat&apos;s out of the bag - DNS flaw details revealed</title>
         <description><![CDATA[On July 9th security researcher Dan Kaminsky <a href="http://www.doxpara.com/?p=1162">announced a serious flaw in DNS</a>.  Dan had been <a href="http://securosis.com/2008/07/08/dan-kaminsky-discovers-fundamental-issue-in-dns-massive-multivendor-patch-released/">working with vendors</a> to address it, but he refused to share the details until <a href="http://www.blackhat.com/html/bh-usa-08/bh-us-08-main.html">Black Hat USA 2008</a> in August.  But now the cat's out of the bag.  Halvar Flake <a href="http://addxorrol.blogspot.com/2008/07/on-dans-request-for-no-speculation.html">took a stab at it</a>, then Matsano Chargen accidentally posted <a href="<a href="http://thefrozenfire.com/data/dnspoisoning.html">full details about it</a>, then <a href="http://www.doxpara.com/?p=1176#comments">Dan cryptically acknowledged</a> it had been disclosed.

The flaw makes it possible to perform <a href="http://www.kb.cert.org/vuls/id/800113">DNS cache poisoning attacks</a>.  DNS (Domain Name System) is analogous to a phone book.  Your computer sends a hostname to a DNS server and it returns a numeric IP address, in the same way that you look up a name in a phone book to find out a phone number.  If a DNS cache poisoning attack is performed successfully, your computer is returned an IP address that belongs to the attacker instead of the correct IP address.

This is serious since all Internet services (web, email, IM, etc.) rely on DNS.  You could think you're logging into Bank of America, but really be logging into the attacker's website.  Same with your email.  Then the attacker would have your login credentials and any other information you entered.

If you manage a DNS server, patch it ASAP.

To check if the DNS server you use is vulnerable, visit <a href="http://www.doxpara.com/">DoxPara</a> and click "Check My DNS".  If you're checking from your home Internet connection, this is likely your ISP's DNS server.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/the-cats-out-of-the-bag.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/the-cats-out-of-the-bag.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">DNS</category>
        
          <category domain="http://www.sixapart.com/ns/types#tag">vulnerability</category>
        
         <pubDate>Wed, 23 Jul 2008 13:19:56 -0500</pubDate>
         
      </item>
      
      <item>
         <title>Distance education required to play Big Brother?</title>
         <description><![CDATA[There's a bill in Congress related to the Higher Education Act, which has implications for schools with distance education programs.  <a href="http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=110_cong_bills&docid=f:h4137rfs.txt">The bill</a> includes a single sentence that states that such institutions must implement processes to verify that a student who registers for a course (or program) is the same as the one who participates in it.  Here's what it says:

<blockquote>the agency or association requires an institution that offers 
distance education to have processes through which the institution 
establishes that the student who registers in a distance education course 
or program is the same student who participates in and completes the 
program and receives the academic credit</blockquote>

And the bill goes to great lengths to define distance education, but it boils down to any course in which the instructor and students are separated.  VCU offers <a href="http://www.ts.vcu.edu/faq/dist_ed/distance_ed.html">such courses</a>.

An article in <a href="http://chronicle.com/free/v54/i46/46a00103.htm">The Chronicle of Higher Education</a> explores some of the technologies which are available to help with user authentication.  These include tried and true technologies like fingerprint readers and challenge questions, as well as keystroke pattern analysis and webcams photos reviewed by remote proctors.  With authentication there are 3 categories of choices - methods that rely on something the user has, something the user knows and something the user is.  When the risk to mitigate involves willful deceit by the user, the first method is useless and the second is difficult to implement effectively since it's trivial for a person to share basic information that could be asked.  So it's likely that the types of technologies adopted will consist of biometrics (such as fingerprint scans, retina scans and <a href="http://www.newscientist.com/blog/invention/2007/06/digit-saving-biometrics.html">subdermal capillary patterns</a>) and visual comparison of the student to a baseline image.

Of course, technology like this has a cost.  In addition to a financial component there are privacy and usability concerns.  But there are some larger issues that need to be considered.

1. Is cheating more rampant in a distance education course than in a traditional classroom environment?

2. How is the authenticity of the baseline sample being ensured?

If a school needs to collect a photo of the student or digitize a fingerprint as part of the enrollment process to use for authentication, the school needs to be sure the individual who submits that information is in fact who they claim to be.  If a person masquerades as another throughout the entire process, a person could conceivably earn a degree without completing any work.  To close the gap the person's identity needs to be verified during enrollment.  A less effective control would be to publish sufficient information from a student's academic record and a photo online.  But an individual's appearance changes over time and if two people resemble each other enough, they can still defeat the system.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/news-distance-education-requir.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/news-distance-education-requir.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">news</category>
        
         <pubDate>Tue, 22 Jul 2008 08:57:12 -0500</pubDate>
         
      </item>
      
      <item>
         <title>San Francisco&apos;s rogue network admin</title>
         <description><![CDATA[The lead network engineer for the city of San Francisco was arrested a week ago and charged with 4 counts of computer tampering.  He is being held on $5 million bail for <a href="http://blog.wired.com/27bstroke6/2008/07/sf-city-charged.html">refusing to hand over the administrative password</a> to the WAN, FiberWAN, which carried more than 60% of the city government traffic.  Yes, $5 million.  As of today he still hasn't handed it over.  The password is needed to make changes to the configuration of network equipment like routers and switches.

This is a fascinating story.  He's being accused of all sorts of behavior - facilitating remote network access so confidential data could be destroyed, covertly reading coworkers emails, and taking pictures of the female head of security during a password audit.  However it seems that there's <a href="http://www.infoworld.com/article/08/07/18/30FE-sf-network-lockout_1.html">a lot more to this story</a>.

There are some key lessons.

1. Ensure that at least 2 people have access to all administrative passwords.

2. Backup all system configuration files on a regular basis to storage media with restricted access.

3. Ensure that at least 2 people can perform every business function.

4. Document all systems and processes.

5. Establish a written information security policy.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/news-san-franciscos-rogue-netw.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/news-san-franciscos-rogue-netw.html</guid>
        
        
          <category domain="http://www.sixapart.com/ns/types#tag">news</category>
        
         <pubDate>Mon, 21 Jul 2008 10:37:26 -0500</pubDate>
         
      </item>
      
      <item>
         <title>Only 41% of web browsers are fully patched</title>
         <description><![CDATA[According to a <a href="http://www.pcworld.com/businesscenter/article/147776/study_unpatched_web_browsers_prevalent_on_the_internet.html">study</a> published on July 1st, on any given day only 41% of web browsers are fully patched.  The data came from visits to Google websites worldwide between January 2007 and June 2008.

Not surprisingly, Firefox came out on top because of its single click auto-update technology which alerts users of new versions and then allows them to upgrade with a single click.

The percentage of users using the latest version of their browser:

Firefox -  83%
Safari - 65%
Opera - 56%
Internet Explorer - 48%

More details can be found in the <a href="http://www.techzoom.net/publications/insecurity-iceberg/">full research paper</a>.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/only-41-of-web-browsers-are-fu.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/only-41-of-web-browsers-are-fu.html</guid>
        
          <category domain="http://www.sixapart.com/ns/types#category">Information Security</category>
        
        
         <pubDate>Thu, 10 Jul 2008 17:44:10 -0500</pubDate>
         
      </item>
      
      <item>
         <title>Vulnerability in Word</title>
         <description><![CDATA[A vulnerability has been <a href="http://secunia.com/advisories/30975/">reported</a> in Microsoft Word, which can be exploited by malicious people to compromise a user's system.  It's known to affect Word 2002 SP3 and is not believed to affect other versions.  No patch has been released.  Microsoft suggests viewing Word documents using their Viewer software instead.]]></description>
         <link>http://blog.vcu.edu/infosec/2008/07/alert-vulnerability-in-word.html</link>
         <guid>http://blog.vcu.edu/infosec/2008/07/alert-vulnerability-in-word.html</guid>
        
        
         <pubDate>Thu, 10 Jul 2008 10:09:09 -0500</pubDate>
         
      </item>
      
   </channel>
</rss> 