<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>CERT/CC Blog</title>
        <link>https://www.cert.org/blogs/certcc/</link>
        <description></description>
        <language>en</language>
        <copyright>Copyright 2012</copyright>
        <lastBuildDate>Thu, 05 Jan 2012 16:15:00 -0500</lastBuildDate>
        <generator>http://www.sixapart.com/movabletype/</generator>
        <docs>http://www.rssboard.org/rss-specification</docs>
        
        <item>
            <title>CNAME flux</title>
            <description><![CDATA[<p>Hello this is Jonathan Spring. Recently, Leigh Metcalf and I uncovered some interesting results in our continuing work on properties of the Domain Name System (DNS). Our work involves an unconventional use of CNAME (canonical name) records.&nbsp; Besides an IP address, CNAME records are the only other location a domain may have in the DNS. Instead of an IP address, a CNAME record is a redirection or alias service that points to another name.&nbsp;</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2012/01/cname_flux.html</link>
            <guid>https://www.cert.org/blogs/certcc/2012/01/cname_flux.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Research</category>
            
            
            <pubDate>Thu, 05 Jan 2012 16:15:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Challenges in Network Monitoring above the Enterprise</title>
            <description><![CDATA[<p>Recently George Jones, Jonathan Spring, and I attended <a href="http://www.usenix.org/events/sec11/">USENIX Security '11</a>. We hosted an evening Birds of a Feather (BoF) session where we asked a question of some significance to our <a href="http://www.cert.org/netsa/">CERT<sup>&reg;</sup> Network Situational Awareness (NetSA)</a> group:</p> <p style="margin-left: 40px;"><em><strong>Is Large-Scale Network Security Monitoring Still Worth Effort?</strong></em></p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2011/09/challenges_in_network_monitori.html</link>
            <guid>https://www.cert.org/blogs/certcc/2011/09/challenges_in_network_monitori.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Fri, 23 Sep 2011 10:06:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Signed Java and Cisco AnyConnect</title>
            <description><![CDATA[<p>A few years ago, I published a blog entry called <a href="http://www.cert.org/blogs/certcc/2008/06/signed_java_security_worse_tha.html">Signed Java Applet Security: Worse than ActiveX?</a> In that entry, I explained the problems that arise when a vulnerability is discovered in a signed Java applet. Let's see how the Cisco AnyConnect vulnerability is affected.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2011/06/signed_java_and_cisco_anyconne.html</link>
            <guid>https://www.cert.org/blogs/certcc/2011/06/signed_java_and_cisco_anyconne.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Web</category>
            
            
            <pubDate>Thu, 09 Jun 2011 13:35:13 -0500</pubDate>
        </item>
        
        <item>
            <title>Effectiveness of Microsoft Office File Validation</title>
            <description><![CDATA[<p>Microsoft recently released a component for Office called Office File Validation that is supposed to help protect against attacks using malformed files. Because I recently performed file fuzzing tests on Microsoft Office, I decided to test the effectiveness of Office File Validation.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2011/05/effectiveness_of_microsoft_off.html</link>
            <guid>https://www.cert.org/blogs/certcc/2011/05/effectiveness_of_microsoft_off.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
            
            <pubDate>Thu, 19 May 2011 14:26:00 -0500</pubDate>
        </item>
        
        <item>
            <title>A Security Comparison: Microsoft Office vs. Oracle Openoffice</title>
            <description><![CDATA[<p>Recently, Dan Kaminsky published a <a href="http://dankaminsky.com/2011/03/11/fuzzmark/">blog entry</a> that compared the fuzzing resiliency of Microsoft Office and Oracle OpenOffice. This blog entry contains the results from a similar test that I performed in November 2010. Also included are some other aspects of the Office suites that can affect the software's security.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2011/04/office_shootout_microsoft_offi.html</link>
            <guid>https://www.cert.org/blogs/certcc/2011/04/office_shootout_microsoft_offi.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
            
            <pubDate>Wed, 13 Apr 2011 14:52:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Announcing the CERT Basic Fuzzing Framework 2.0</title>
            <description><![CDATA[<p>Version 2.0 of the CERT Basic Fuzzing Framework (BFF) made its debut on Valentine's Day at the 2011 CERT Vendor Meeting in San Francisco. This new edition has a lot of cool features that we'll be describing in more detail in future posts, but we wanted to let you know that it's available so that you can <a href="http://www.cert.org/download/bff">download</a> and try it.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2011/02/cert_basic_fuzzing_framework_b.html</link>
            <guid>https://www.cert.org/blogs/certcc/2011/02/cert_basic_fuzzing_framework_b.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
            
            <pubDate>Mon, 28 Feb 2011 15:53:00 -0500</pubDate>
        </item>
        
        <item>
            <title>&quot;Network Monitoring for Web-Based Threats&quot; released</title>
            <description><![CDATA[<p>The <a href="http://www.cert.org/netsa/">CERT Network Situational Awareness (NetSA)</a> team, specifically our talented and hard-working intern Matthew Heckathorn under <a href="http://www.sei.cmu.edu/about/people/sfaber.cfm">Sid Faber</a>'s guidance, has published an <a href="http://www.sei.cmu.edu/library/abstracts/reports/11tr005.cfm">SEI Technical Report</a> on monitoring web-based threats.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2011/02/network_monitoring_for_web-bas.html</link>
            <guid>https://www.cert.org/blogs/certcc/2011/02/network_monitoring_for_web-bas.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Web</category>
            
            
            <pubDate>Mon, 14 Feb 2011 13:32:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Blog reorganization</title>
            <description><![CDATA[<p>Hi, folks. As you can see, we've changed the name of the Vulnerability Analysis Blog to the CERT/CC Blog. With this name change, we're expanding the focus of the blog to include content from other technical teams.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2011/02/blog_reorganization.html</link>
            <guid>https://www.cert.org/blogs/certcc/2011/02/blog_reorganization.html</guid>
            
            
            <pubDate>Fri, 11 Feb 2011 15:01:00 -0500</pubDate>
        </item>
        
        <item>
            <title>CERT Basic Fuzzing Framework Update</title>
            <description><![CDATA[<p>Hi, folks. We've recently updated the CERT<sup>&reg;</sup> Basic Fuzzing Framework (BFF). The new BFF 1.1 contains new functionality and improves performance.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2010/09/cert_basic_fuzzing_framework_u.html</link>
            <guid>https://www.cert.org/blogs/certcc/2010/09/cert_basic_fuzzing_framework_u.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
            
            <pubDate>Wed, 22 Sep 2010 11:26:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Study of Malicious Domain Names: TLD Distribution</title>
            <description><![CDATA[<p>Hello, folks.  This post comes to you courtesy of Aaron Shelmire from the <a href="http://www.cert.org/netsa/">Network Situational Awareness</a> team. Aaron writes:</p> <p>Recently the Network Situational Awareness team at CERT has been researching the characteristics of malicious network touchpoints. The findings of this initial research are very telling as to the true state of security on the internet.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2010/08/malicious_domain_names_the_tld.html</link>
            <guid>https://www.cert.org/blogs/certcc/2010/08/malicious_domain_names_the_tld.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Research</category>
            
            
            <pubDate>Tue, 31 Aug 2010 14:28:00 -0500</pubDate>
        </item>
        
        <item>
            <title>CERT Basic Fuzzing Framework</title>
            <description><![CDATA[<p>Hi folks. I've been involved in a fuzzing effort at CERT. One of the ways that I've been able to discover vulnerabilities is through &quot;dumb&quot;&nbsp;or mutational <a href="http://en.wikipedia.org/wiki/Fuzz_testing">fuzzing</a>. We have developed a framework for performing automated <a href="http://msdn.microsoft.com/en-us/library/cc162782.aspx#Fuzzing_topic4">dumb fuzzing</a>. Today we are releasing a simplified version of automated dumb fuzzing, called the Basic Fuzzing Framework (BFF).</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2010/05/cert_basic_fuzzing_framework.html</link>
            <guid>https://www.cert.org/blogs/certcc/2010/05/cert_basic_fuzzing_framework.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
            
            <pubDate>Wed, 26 May 2010 14:00:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Top-10 Top Level and Second Level Domains found in Malicious Software</title>
            <description><![CDATA[<p>Hello folks.&nbsp; This post comes to you courtesy of Ed Stoner and Aaron Shelmire from the <a href="http://www.cert.org/netsa/">Network  Situational Awareness</a> group at CERT.&nbsp; They write:</p> <p>Recently there have been some <a href="http://blog.damballa.com/?p=575">statistics  published</a> on botnet Command &amp; Control (C2) channels. These  statistics claim that 94.58% of botnet C2 channels are under the .com  top level domain (TLD). While it's impossible to accurately comment on  those statistics without knowing the methodology used to arrive at them,   we at CERT have been doing research concerning malicious domain names  that arrives at a different result.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2010/03/top-10_top_level_and_second_le.html</link>
            <guid>https://www.cert.org/blogs/certcc/2010/03/top-10_top_level_and_second_le.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Web</category>
            
            
            <pubDate>Fri, 05 Mar 2010 14:10:32 -0500</pubDate>
        </item>
        
        <item>
            <title>Plain Text Email in Outlook Express</title>
            <description><![CDATA[<p>Reading email messages in plain text seems like a reasonable thing to do to improve the security of your email client. Plain text takes less processing than HTML, which should help minimize your attack surface, right? As it turns out, Outlook Express (and its derivatives) is doing more than you think when it is configured with the &quot;Read all messages in plain text&quot;&nbsp;option enabled.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2009/11/plain_text_email_in_outlook_ex.html</link>
            <guid>https://www.cert.org/blogs/certcc/2009/11/plain_text_email_in_outlook_ex.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Fri, 13 Nov 2009 09:23:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Managing IPv6 - Part 2</title>
            <description><![CDATA[<p>Past entries have addressed both securing and disabling IPv6. This entry describes ways that administrators can secure their networks and generate test cases to test those settings.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2009/10/managing_ipv6_-_part_2.html</link>
            <guid>https://www.cert.org/blogs/certcc/2009/10/managing_ipv6_-_part_2.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Tue, 06 Oct 2009 15:44:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Managing IPv6 - Part 1</title>
            <description><![CDATA[<p>This entry is the first in a series about securely configuring the <a href="http://en.wikipedia.org/w/index.php?title=IPv6&amp;oldid=306038060">IPv6</a> protocol on selected operating systems. Although this entry focuses on how to disable IPv6, we are not recommending that everyone immediately disable IPv6. However, if critical parts of your infrastructure (firewall, IDS, etc.) do not yet fully support the IPv6 protocol, consider disabling IPv6 until those components can be upgraded.</p>]]></description>
            <link>https://www.cert.org/blogs/certcc/2009/08/managing_ipv6_part_i.html</link>
            <guid>https://www.cert.org/blogs/certcc/2009/08/managing_ipv6_part_i.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Wed, 19 Aug 2009 10:07:00 -0500</pubDate>
        </item>
        
    </channel>
</rss>

