<?xml version="1.0" encoding="UTF-8"?>

  <rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns="http://purl.org/rss/1.0/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
  >

  <channel rdf:about="http://ciscoarticles.com/rss/rss.php">
    <title>Cisco Articles</title>
    <link>http://ciscoarticles.com/rss/rss.php</link>
    <description></description>
    <dc:language>en-us</dc:language>
    <dc:rights>Copyright 2010, </dc:rights>
    <dc:publisher>rhifat@gmail.com</dc:publisher>
    <dc:creator>rhifat@gmail.com</dc:creator>
    <dc:title>Cisco Articles</dc:title>
    <dc:source>http://ciscoarticles.com/rss/rss.php</dc:source>
    <dc:type>Collection</dc:type>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>4</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Severity.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Types.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Classes.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Implementations.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Series.html" />
        
        
        
        
        
        
        
        
        
        
                
      </rdf:Seq>
    </items>
  </channel>
  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Severity.html">
<title>Signature Severity</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Severity.html</link>
<description>
&lt;a name=&quot;1949&quot; /&gt;&lt;a name=&quot;wbp30ch26P91&quot; /&gt;
The &lt;i class=&quot;emphasis&quot;&gt;signature severity&lt;/i&gt; represents the 
probability that the matched signature represents a real and immediate security 
threat to your systems and network. Each signature has a default severity 
assigned to it by Cisco security engineers and these default severities are 
normally adequate for most network ...</description>
<dc:language>en-us</dc:language>
<dc:title>Signature Severity</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4343</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-10T00:00:00+00:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Types.html">
<title>Signature Types</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Types.html</link>
<description>
&lt;a name=&quot;1946&quot; /&gt;&lt;a name=&quot;wbp30ch26P72&quot; /&gt;
The &lt;i class=&quot;emphasis&quot;&gt;signature types&lt;/i&gt; describe the type 
of network traffic the signature is used to match. Some signatures detect 
intrusions by examining the TCP connection requests or UDP connections. Other 
signature types examine the protocol information in the IP headers or the 
protocol-dependant application commands located ...</description>
<dc:language>en-us</dc:language>
<dc:title>Signature Types</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4342</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-10T00:00:00+00:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Classes.html">
<title>Signature Classes</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Classes.html</link>
<description>
&lt;a name=&quot;1944&quot; /&gt;&lt;a name=&quot;wbp30ch26P57&quot; /&gt;
CIDS signatures fall into four classes. Signatures belong to 
one of the four classes, based on the type of attack the signature was designed 
to detect. As discussed in &lt;a target=&quot;_parent&quot; href=&quot;LiB0184.html#1713&quot; class=&quot;chapterjump&quot;&gt;Chapter 23&lt;/a&gt;, there are three types of attacks: Reconnaissance, 
Access, and Denial of Service ...</description>
<dc:language>en-us</dc:language>
<dc:title>Signature Classes</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4341</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-10T00:00:00+00:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Implementations.html">
<title>Signature Implementations</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Implementations.html</link>
<description>
&lt;a name=&quot;1939&quot; /&gt;&lt;a name=&quot;wbp30ch26P40&quot; /&gt;
The signature implementations of CIDS signatures come in two 
types: every signature is either context based or content based. Each of these 
two types of signature implementations describes which part of the TCP/IP packet 
is examined.&lt;a name=&quot;1940&quot; /&gt;&lt;a name=&quot;IDX-925&quot; /&gt; 

Context-Based Signatures
&lt;i class=&quot;emphasis&quot;&gt;Context-based signatures &lt;/i&gt;are triggered ...</description>
<dc:language>en-us</dc:language>
<dc:title>Signature Implementations</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4340</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-10T00:00:00+00:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Series.html">
<title>Signature Series</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Signature-Series.html</link>
<description>
&lt;a name=&quot;1936&quot; /&gt;&lt;a name=&quot;wbp30ch26P11&quot; /&gt;
CIDS organizes all the signatures into a series. When an 
alarm is sent, the signature that generated the alarm is also sent. The Event 
Viewer displays not only the alarm, but also the signature ID. While recognizing 
every signature ID that could generate an alarm would ...</description>
<dc:language>en-us</dc:language>
<dc:title>Signature Series</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4339</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-10T00:00:00+00:00</dc:date>
<dc:type>text</dc:type>
</item>

  
  
  
  
  
  
  
  
  
  
  
</rdf:RDF>
