<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>ClearNet Security: Tag assessments</title>
    <link>http://blog.clearnetsec.com/articles/tag/assessments</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Anything alert you?</title>
      <description>&lt;p&gt;There is nothing I&#8217;ve seen recently to promote a valuable exercise to do after receiving a security assessment.  That is, as the client, &lt;b&gt;&lt;i&gt;what did you see?&lt;/i&gt;&lt;/b&gt;  
&lt;/p&gt;
&lt;p&gt;
Did you have anything alert you?  If so, what did it suggest?  Did you have enough information to piece together what was happening?  &lt;i&gt;(Bonus:  do you know which tools were fired towards your IPs?)&lt;/i&gt;
&lt;/p&gt;
&lt;p&gt;
The majority of my clients have no clue if anything occurred.  That&#8217;s bad.  Businesses which have little to lose may decide to ignore investing in monitoring and detection, but for others it&#8217;s turning a blind eye.  
&lt;/p&gt;
&lt;p&gt;
I&#8217;m going to dig a little deeper on future exit calls to get more information.  I often ask clients if they detected any strange behavior, but there is definitely more room to expand the discussion.
&lt;/p&gt;

</description>
      <pubDate>Wed, 05 Sep 2007 19:37:00 -0600</pubDate>
      <guid isPermaLink="false">urn:uuid:24cb4f05-698b-44aa-8bef-cd848ee81b28</guid>
      <author>tate@ClearNetSec.com (Tate Hansen)</author>
      <link>http://blog.clearnetsec.com/articles/2007/09/05/anything-alert-you</link>
      <category>ClearNet Security</category>
      <category>Tate Hansen</category>
      <category>ClearNet</category>
      <category>security</category>
      <category>assessments</category>
      <category>penetration</category>
      <category>testing</category>
      <category>logs</category>
      <category>detection</category>
    </item>
  </channel>
</rss>
