<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Keeping the noise down in your security log</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx</link><description>I commonly hear the complaint that "there's too much noise in the security log". As I mentioned, that's one of the key things we're working on for Longhorn- we have a new audit policy mechanism prototyped. But here are some tips to keep your noise level</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Keeping the noise down in your security log</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#350965</link><pubDate>Tue, 11 Jan 2005 22:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:350965</guid><dc:creator>petal</dc:creator><description>Damn useful - thanks very much. I can see myself implementing some of these recommendations tomorrow. My current level of paranoia renders the security log very unfriendly without 3rd party tools.&lt;br&gt;&lt;br&gt;Slightly OT, but do you know if the Microsoft Audit Collection System will allow agents to selectively ignore certain event types? Or is this no longer being developed? Or is a different solution envisaged for Longhorn?</description></item><item><title>re: Keeping the noise down in your security log</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#351032</link><pubDate>Wed, 12 Jan 2005 00:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:351032</guid><dc:creator>Eric Fitzgerald</dc:creator><description>ACS currently does not have filtering on the agent, however that is being considered prior to RTM.&lt;br&gt;&lt;br&gt;The reason that we haven't implemented that is that it is a management feature, not a security feature.  From a security perspective we want all events so that we can detect gaps in the event stream- there's no way for us to tell the difference at the collector whether the forwarder filtered an event, or whether the admin tampered with the log and deleted an event.&lt;br&gt;&lt;br&gt;Two other mitigating factors:&lt;br&gt;1) If you don't want an event, don't generate it- use audit policy.  Yes, I know that there are limits to this.&lt;br&gt;2) ACS uses a streaming compression algorithm (SLDC), which compresses extremely well.  We've seen event streams which take only 11 bytes per event on the wire, including protocol overhead (YMMV).&lt;br&gt;&lt;br&gt;For those of you unfamiliar with ACS, we'll publish news on it shortly.  It's in a private beta state right now, I'll blog an entry when we open up the beta.&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;Eric</description></item><item><title>MIA Bloggers</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#352722</link><pubDate>Fri, 14 Jan 2005 08:59:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:352722</guid><dc:creator>bmonday(dot)com</dc:creator><description /></item><item><title>re: Keeping the noise down in your security log</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#353735</link><pubDate>Sat, 15 Jan 2005 22:50:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:353735</guid><dc:creator>joe</dc:creator><description>I think something else that would be useful would be an event viewer that was more flexible in terms of what you want to view. Ability to filter out specific events and ability to have it highlight certain events you are concerned about or even pull them into a &amp;quot;watch these&amp;quot; separate display panel. &lt;br&gt;&lt;br&gt;Personally I like a lot of information because you never know what little thing may make you realize something isn't right. However, the current state of event viewer is sort of like dir compared to explorer when looking at file listings only event viewer isn't even as flexible as dir.&lt;br&gt;&lt;br&gt;  joe&lt;br&gt;</description></item><item><title>re: Keeping the noise down in your security log</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#354241</link><pubDate>Mon, 17 Jan 2005 06:30:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:354241</guid><dc:creator>Eric</dc:creator><description>Thanks for the feedback, Joe.  I've pretty much said the same thing to the event viewer team; I'll pass along your comments!&lt;br&gt;&lt;br&gt;Eric</description></item><item><title>What happened to my nice quiet audit logs?</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#357016</link><pubDate>Thu, 20 Jan 2005 10:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:357016</guid><dc:creator>E-Bitz - SBS MVP the Official Blog of the SBS </dc:creator><description /></item><item><title>re: Keeping the noise down in your security log</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#359768</link><pubDate>Mon, 24 Jan 2005 21:35:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:359768</guid><dc:creator>Ashish (Logmaster)</dc:creator><description>I turn on &amp;quot;failure&amp;quot; logging, when trying to understand what a app is doing when its not working. Just did it today trying to get SQL Report Serivces to run. Its a pain to install it on a nonstandard system, especially when you run IIS in a very secure mode. </description></item><item><title>re: Keeping the noise down in your security log</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#367528</link><pubDate>Sat, 05 Feb 2005 01:46:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:367528</guid><dc:creator>Eric</dc:creator><description>Failure logging will probably always be yucky.  We're working on some changes for longhorn that should make success auditing much more useful and less voluminous for object access, but all I can do for failures is log them.  It's pretty common for apps to request more privilege than they need, trap the failure case so they can re-attempt open with less privilege, and trash my log.&lt;br&gt;&lt;br&gt;I actually am having a discussion now with several teams on whether there is anything we think we can do.  However no brainstorms yet.&lt;br&gt;&lt;br&gt;Eric</description></item><item><title>Keeping the noise down in your security log</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#394281</link><pubDate>Sat, 12 Mar 2005 01:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:394281</guid><dc:creator>Dana Epp's ramblings at the Sanctuary</dc:creator><description>Eric posted an interesting article on how to cut down the noise of the security log in Windows Server. He points out a lot of interesting tidbits. I don't agree with them all, but that's just me. I'd rather wrestle with a little more noise on a hardened server and have to MUCH logs rather than not enough when doing a forensic audit. Of course, most people aren't even LOOKING at their logs, so its a moot point. Overall though, a very useful article on how to cut down the noise in your security logs on some areas of the system which are not that beneficial for you. Worth checking out. Happy reading....</description></item><item><title>Multiple Events for Successful Account Creation</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#459096</link><pubDate>Thu, 01 Sep 2005 18:55:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:459096</guid><dc:creator>Windows Security Logging and Other Esoterica</dc:creator><description>Here is the pattern you should expect to see when creating a local account.&amp;amp;amp;nbsp; For domain accounts,...</description></item><item><title>Parolele Windows şi recomandări în rapoarte de audit. Dileme din practică</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#2163413</link><pubDate>Tue, 17 Apr 2007 17:02:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2163413</guid><dc:creator>Adrian Munteanu - Jurnal de optimist</dc:creator><description>&lt;p&gt;Deşi subiectul este destul de sensibil, risc. Mă frăm&amp;#238;ntă de vreo c&amp;#238;teva zile unele lucruri descoperite&lt;/p&gt;
</description></item><item><title>Minimizing Directory Service Audit Event Noise</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#8925693</link><pubDate>Fri, 05 Sep 2008 04:20:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8925693</guid><dc:creator>Windows Security Logging and Other Esoterica</dc:creator><description>&lt;p&gt;I've written before on noise reduction in the Windows security event log. I've also written to describe&lt;/p&gt;
</description></item><item><title> Windows Security Logging and Other Esoterica Keeping the noise down | Quick Diets</title><link>http://blogs.msdn.com/ericfitz/archive/2005/01/11/350848.aspx#9745451</link><pubDate>Sat, 13 Jun 2009 17:19:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9745451</guid><dc:creator> Windows Security Logging and Other Esoterica Keeping the noise down | Quick Diets</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://quickdietsite.info/story.php?id=4374"&gt;http://quickdietsite.info/story.php?id=4374&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>