<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Realtime Community | Messaging and Web Security | Digital Library</title>
      <link>http://www.realtime-websecurity.com/digital_library/</link>
      <description></description>
      <language>en</language>
      <copyright>Copyright 2007</copyright>
      <lastBuildDate>Fri, 09 Mar 2007 17:50:28 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <item>
         <title>Configuration Management and Security</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Information security is commonly described through the adage &ldquo;as strong as the weakest link&rdquo;&mdash;and too often the weakest link is in systems configurations. Regardless of all the time and money poured into anti-malware, intrusion prevention, content filtering, and all the other measures we deploy, if configuration is not controlled, our networks and systems will be vulnerable.

Configuration management is one of the areas of information security that often falls on systems managers and network administrators. Many of the security-oriented tasks are also applicable to good systems management practices; this fact just adds weight to the notion that good systems management is good security. Much has been written about effective configuration management practices and comprehensive best practices are readily available. Rather than delve into the details of these broad frameworks, this article will focus on several basic functions and areas that are critical to leveraging the benefits of configuration management to improve security.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/03/configuration_management_and_s.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/03/configuration_management_and_s.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">access controls</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">auditing</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">configuration management</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">operatin system hardening</category>
        
         <pubDate>Fri, 09 Mar 2007 17:50:28 -0500</pubDate>
      </item>
            <item>
         <title>Web Services Security</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Web services are an established method for building distributed and federated applications. Using Web services protocols, developers can provide access to application functions by publishing the interface to the service using the Web Services Definition Language (WSDL), providing data in XML structures, and transmitting data between applications using the Simple Object Access Protocol (SOAP). Service consumers can discover Web services that have been registered using the Universal description, discovery, and integration (UDDI) protocol. As with any application, questions of authentication, authorization, and trust must be addressed in the Web services architecture.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/02/web_services_security.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/02/web_services_security.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">application security</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">SAML</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">Security Assertion Markup Language</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">Web Services</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">WS-Security</category>
        
         <pubDate>Mon, 26 Feb 2007 21:49:06 -0500</pubDate>
      </item>
            <item>
         <title>Web Application Testing</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Testing is an important part of any software development methodology, but testing security features is essential for Web applications. Those who come from a software development background are familiar with functional testing: start with required functions, formulate test plans, and define test cases for each feature. Ideally, these steps are automated in a regression test that is run routinely to make sure you do not lose ground as you correct errors. Just as important, and more important if you have to answer to auditors, is testing a key non-functional requirement&mdash;security.

]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/02/web_application_testing.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/02/web_application_testing.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">compliance</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">security</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">testing</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">vulnerability testing</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">Web application</category>
        
         <pubDate>Mon, 26 Feb 2007 21:44:24 -0500</pubDate>
      </item>
            <item>
         <title>Vulnerability Scanning 101</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Vulnerability scanners have come a long way. When tools like SATAN first came out, there was a lot of discussion about the wisdom of having vulnerability scanners. After all, these were tools for hackers to employ to attempt an attack on your network and servers. Proponents of the tools argued that it was better to learn about your vulnerabilities with a tool rather than through an attack. The debate about the relative value of vulnerability scanners is essentially over&mdash;they are useful tools for network and systems administrators in spite of the fact that they could be used for malicious purposes.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/02/vulnerability_scanning_101.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/02/vulnerability_scanning_101.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">asset management</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">remediation</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">threats</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">vulnerability management</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">vulnerability scanning</category>
        
         <pubDate>Mon, 26 Feb 2007 21:40:10 -0500</pubDate>
      </item>
            <item>
         <title>Physical and Digital Security Convergence</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Security management entails a number of dimensions, including logical security over information in whatever form it takes; electronic security over networks, servers, and other devices that store, manage, and transmit information; and physical security, which addresses the protection of persons and property. Not surprisingly, logical and electronic security are tightly coupled. Information residing on a server is dependent on the access controls and other security measures of the server. Encryption can protect data when it is transmitted across insecure channels, such as the Internet, but it can also provide additional protection against information theft. For example, the use of full disk encryption can reduce the chance of information theft when a mobile device is lost or stolen.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/02/physical_and_digital_security.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/02/physical_and_digital_security.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">access controls</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">digital security</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">electronic security</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">physical security</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">security management</category>
        
         <pubDate>Fri, 16 Feb 2007 19:28:40 -0500</pubDate>
      </item>
            <item>
         <title>Email Authentication</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Spam and phishing continue to plague email systems. Estimates of the amount of spam clogging the email infrastructure reach as high as 75 to 80 percent of all email messages. Techniques such as blocking lists, content filters, and reputation filters all help to identify spam and phishing lures. The problem of unwanted email is so challenging that no single technique will work in all cases, and the effectiveness of techniques will vary. Part of the problem is that spammers are quick to adapt to new blocking technologies. Blocking based on content is not the only option, though.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/02/email_authentication.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/02/email_authentication.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">blocking</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">content filters</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">email</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">email authentication</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">phishing</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">spam</category>
        
         <pubDate>Fri, 09 Feb 2007 17:42:19 -0500</pubDate>
      </item>
            <item>
         <title>IT Audits: What to Expect</title>
         <description><![CDATA[<p><strong>ARTICLE &gt;&gt;</strong>&nbsp;The section of the Sarbanes-Oxley Act (SOX) known as SOX 404 has gotten much attention from IT management. This is not a passing fad; there will not be any regulatory equivalent of a dot com bust&mdash;compliance with SOX 404 is here to stay in some form or another. In fact, even if SOX 404 is changed, as many have argued for, other regulatory schemes are in place that influence how IT does its job. With these regulations come requirements for verification&mdash;and that means auditing.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/01/it_audits_what_to_expect.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/01/it_audits_what_to_expect.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">COBIT</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">compliance</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">IT audit</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">SOX</category>
        
         <pubDate>Mon, 29 Jan 2007 18:05:56 -0500</pubDate>
      </item>
            <item>
         <title>Host Intrusion Detection and Prevention</title>
         <description><![CDATA[<p><strong>ARTICLE &gt;&gt;</strong>&nbsp;In the defense-in-depth security framework, host intrusion prevention systems (IPSs) are one of the last lines of defense. Host IPSs reside on the devices that they protect. These systems use a combination of signature- and behavior-based analysis to detect attacks and mitigate the impact of those attacks.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/01/host_intrusion_detection_and_p.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/01/host_intrusion_detection_and_p.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">intrusion detection</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">intrusion preventions</category>
        
         <pubDate>Thu, 18 Jan 2007 19:15:00 -0500</pubDate>
      </item>
            <item>
         <title>FISMA and Messaging Security</title>
         <description><![CDATA[<p><strong>ARTICLE &gt;&gt;</strong>&nbsp;The Federal Information Security Management Act (FISMA) is a broad set of regulations that addresses the management and control of information resources within the federal government and is applicable to many federal agencies. The high-level objectives of the act include:</p>
                    <ul>
                      <li>Ensuring information is appropriately categorized according to security objectives and the impact of a security breach</li>
                      <li>Setting standards for minimal security requirements for federal information systems</li>
                      <li>Selecting and implementing appropriate security controls based on a risk assessment model</li>
</ul>


]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2007/01/fisma_and_messaging_security.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2007/01/fisma_and_messaging_security.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">compliance</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">security awareness</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">security management</category>
        
         <pubDate>Tue, 09 Jan 2007 18:46:22 -0500</pubDate>
      </item>
            <item>
         <title>Rootkit Challenges</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Rootkits are one of the threats that can keep security professionals up at night. Viruses and worms are real threats but can be reasonably well controlled. Trojan horses, keyloggers, and other information-stealing programs are growing threats but, if detected, can usually be removed. In fact, the first step in many security countermeasures, such as antivirus solutions, is detecting the presence of malicious and unwanted programs. The role of rootkits is to hide them.

Rootkits use a number of techniques to hide themselves and other malicious programs. Rootkits alter the process list so that executing malware does not appear with other running programs. They might alter the information returned by operating system (OS) functions; for example, a function call to get the size of an altered file may return the original size, not the new size after alteration, effectively masking the file tampering. Rootkits can also prevent OS functions from listing files, such as files for a Trojan horse or a program designed to launch a Denial of Service (DoS) attack. Several types of techniques are used to implement rootkits, and each attacks at a different level of the OS.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2006/12/rootkit_challenges.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2006/12/rootkit_challenges.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">malware</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">rootkits</category>
        
         <pubDate>Wed, 20 Dec 2006 14:53:29 -0500</pubDate>
      </item>
            <item>
         <title>Content Filtering Technologies</title>
         <description><![CDATA[<p><strong>ARTICLE &gt;&gt;</strong>&nbsp;Content filtering is a term that is often used to refer to a collection of technologies that can be applied at client, server, and network levels. This article discusses the various types of content-filtering technologies and their uses. The technologies addressed include:</p>
                    <ul>
                      <li>URL blocking</li>
                      <li>Content scanning</li>
                      <li>Bayesian filtering</li>
                      <li>Collaborative filtering</li>
                    </ul>
                    <p>These are complementary and sometimes overlapping technologies, but they are distinct approaches to the problem of blocking unwanted content.</p>]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2006/12/content_filtering_technologies.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2006/12/content_filtering_technologies.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">URL blocking</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">vulnerabilities</category>
        
         <pubDate>Fri, 15 Dec 2006 14:58:14 -0500</pubDate>
      </item>
            <item>
         <title>Botnet Threats</title>
         <description><![CDATA[<p><strong>ARTICLE &gt;&gt;</strong>&nbsp;Cybercrime seems to continue on its evolution toward greater sophistication in techniques. You see it in higher rates of infections of Trojan horses, more targeted phishing attacks (aka <em>spear phishing</em>), and perhaps most disturbingly, the increasingly robust nature of botnets. Bots are tools for taking control of computers, and a collection of computers compromised by bots is known as a botnet. The botnet herder manages the botnet and issues commands directing the operation of the botnet. The herder may or may not be the person who originally created the botnet&mdash;it seems cybercriminals are not above stealing botnets from one another (no honor among thieves).</p>
 <strong><em>Botnets at Your Service</em></strong>
 <p>So what good is a collection of compromised machines? Botnets may be used for:</p>
 <ul>
   <li>Conducting distributed denial of service (DDoS) attacks</li>
   <li>Distributing spam</li>
   <li>Launching phishing attacks</li>
   <li>Conducting click fraud</li>
   <li>Stealing personal information</li>
 </ul>]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2006/12/botnet_threats.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2006/12/botnet_threats.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">botnets</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">cybercrime</category>
        
         <pubDate>Thu, 07 Dec 2006 21:23:16 -0500</pubDate>
      </item>
            <item>
         <title>Instant Messaging Worms and Other IM Threats</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;As email systems are becoming more difficult to penetrate with viruses and worms, it is not surprising that malware writers are turning to other communication channels to push worms, Trojan horses, and botnet software. Instant messaging (IM) services have become an ideal mechanism for malware developers for the following reasons:

 - Malware can be spread quickly over IM, especially with users with large numbers of contacts
 - Users are not necessarily as cautious with IM as they are with email, especially when dealing with a message from an apparent friend or colleague
 - The activities carried out by malware delivered by IM can be relatively low profile (for example, opening an IRC channel and listening for commands)
 - Rootkits can be sent along with worms and Trojans to hide the presences of the malware

IM communications are relatively short, so it is easier to create a message that appears legitimate in a wide range of circumstances

This article will examine some examples of IM worms and related threats, identify general principles of underlying IM threats, and discuss tips for minimizing the impact of these threats.
]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2006/11/instant_messaging_worms_and_ot.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2006/11/instant_messaging_worms_and_ot.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">instant message</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">malware</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">worms</category>
        
         <pubDate>Thu, 30 Nov 2006 23:05:28 -0500</pubDate>
      </item>
            <item>
         <title>When Patching Is Not Enough: Zero-Day Threats</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Zero-day threats were in the press over the past month as previously unknown vulnerabilities were exploited in Microsoft Office products. Zero-day attacks get their name from the fact that there are zero days between the time a vulnerability becomes known to software developers, security researchers, and application users and the time the vulnerability is exploited on fully patched and updated devices. The problem is not limited to Microsoft products, and it would be unwise to assume that using alternative products alleviates the zero-day vulnerability problems.

This article will examine zero-day threats from three perspectives:

<ul>
<li>What kind of zero-day threats have occurred?</li>
<li>What can be done to minimize the problem in the short term?</li>
<li>What are the longer-term challenges to mitigating the risk of zero-day threats?</li>
</ul>]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2006/11/when_patching_is_not_enough_ze.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2006/11/when_patching_is_not_enough_ze.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">Microsoft Office</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">patching</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">security</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">vulnerabilities</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">zero-day threat</category>
        
         <pubDate>Thu, 09 Nov 2006 19:30:06 -0500</pubDate>
      </item>
            <item>
         <title>Essential Policies for Messaging Security</title>
         <description><![CDATA[<strong>ARTICLE &gt;&gt;</strong>&nbsp;Securing a messaging infrastructure is a multi-faceted challenge that begins with balancing functionality and security. It is often said that there is a tradeoff between the usefulness of a system and its level of security. This is not to say that reasonably secured systems are unusable or that feature-rich, user-friendly applications are inherently insecure. It does mean that as networks and applications become more complex, the potential security risks increase.

Messaging is a prime example. As email clients began to include improved functionality with features such as macros, malware developers took advantage of those features. Worms can threaten instant messaging (IM). Flaws in Internet phone services, such as buffer overflows, can provide entry points to attackers. In spite of these types of vulnerabilities, the cost/benefit ratio of messaging can be substantially in favor of the benefits, as long as certain protections are in place. A coordinated response to threats to messaging depends on a set of essential policies governing the use and implementation of messaging services.]]></description>
         <link>http://www.realtime-websecurity.com/digital_library/2006/10/essential_policies_for_messagi.asp</link>
         <guid>http://www.realtime-websecurity.com/digital_library/2006/10/essential_policies_for_messagi.asp</guid>
                  <category domain="http://www.sixapart.com/ns/types#category">The Messaging and Web Security Essentials Series</category>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">messaging policies</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">messaging security</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">risk tolerence</category>
        
         <pubDate>Mon, 23 Oct 2006 12:47:09 -0500</pubDate>
      </item>
      
   </channel>
</rss>
