<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Times New Roman","serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=WordSection1>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Andy Berryman
[mailto:aberryman@...14765...] <br>
<b>Sent:</b> Wednesday, October 13, 2010 10:00 AM<br>
<b>To:</b> snort-users@lists.sourceforge.net<br>
<b>Subject:</b> [Snort-users] Building a host attribute table?<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p> </o:p></p>

<p class=MsoNormal>Is it worth building a host attribute table when you only
have the operating system? Basically, is it worth the hassle? Let’s say I
only have the OS for about 100 machines on 3 class B subnets. Most of them are
Windows XP, 2k8 or win7 boxes. There are about 20-30 that are SunOS, linux, or
DRAC. <o:p></o:p></p>

<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>

<p class=MsoNormal><span style='font-family:"Times New Roman","serif";
color:#1F497D'>If all you are using the HAT for is to define OS, then it’s
probably easier to setup a new stream5, and frag3 policy and define the IPs
there.  <o:p></o:p></span></p>

<p class=MsoNormal><span style='font-family:"Times New Roman","serif";
color:#1F497D'><o:p> </o:p></span></p>

<p class=MsoNormal>My stream5 is setup like this. <o:p></o:p></p>

<p class=MsoNormal><o:p> </o:p></p>

<p class=MsoNormal>preprocessor stream5_global: max_tcp 1048576, memcap
1073741824, track_tcp yes, track_udp no<o:p></o:p></p>

<p class=MsoNormal>preprocessor stream5_tcp: policy windows,
use_static_footprint_sizes, dont_store_large_packets, ports client 21 22 23 25
42 53 79 80 109 110 111 113 119 135 136 137 139 143 110 111 161 445 513 514 691
1433 1521 2100 2301 3128 3306 6665 6666 6667 6668 6669 7000 8000 8080 8180 8888
32770 32771 32772 32773 32774 32775 32776 32777 32778 32779, ports both 443 465
563 636 989 992 993 994 995 7801 7702 7900 7901 7902 7903 7904 7905 7906 6907
7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920<o:p></o:p></p>

<p class=MsoNormal><o:p> </o:p></p>

<p class=MsoNormal>So with that said, it seems like it’d be pointless to
set it up for anything that’s a Windows machine, right? <o:p></o:p></p>

<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>

<p class=MsoNormal><span style='font-family:"Times New Roman","serif";
color:#1F497D'>Depends on if you’re going to use the HAT to also define
ports, services, applications… if you are running services on
non-standard ports, I say by all means, add in the Windows boxes so that you
get coverage via the metadata service tags in rules, otherwise you’re
going to be missing a bit of data. (bit is relative here, in my environment, I
would miss a lot).<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-family:"Times New Roman","serif";
color:#1F497D'><o:p> </o:p></span></p>

<p class=MsoNormal>Thanks,<o:p></o:p></p>

<p class=MsoNormal>Andy Berryman<o:p></o:p></p>

<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>

<hr size=2 width="100%" align=center>

</span></div>

<div>

<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>This
message from Cymtec Systems, Inc. contains confidential information and is
solely for the use of the recipient(s) named above. If you are not the intended
recipient or an agent responsible for delivering it to the intended recipient,
you are hereby notified that you have received this message in error and that
any review, disclosure, copying, distribution or use of the contents of this
message is strictly prohibited. If you have received this message in error,
please destroy it immediately and notify Cymtec Systems, Inc. by telephone at
+1.314.993.8700 or by return e-mail.</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>

</div>

<div>

<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>

<hr size=2 width="100%" align=center>

</span></div>

<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'> </span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>

</div>

</div>

</div>

</body>

</html>