Summary: <p><em>Today's episode is brought to you by <strong>ITProTV</strong>. Visit <a href="https://itpro.tv/7ms" rel="nofollow noreferrer noopener" target="_blank">itpro.tv/7ms</a> and use code <strong>7MS</strong> to get a FREE 7-day trial and 30% off a monthly membership for the lifetime of your active subscription.</em></p> <hr><p>This week I sat down with Lane Roush of <a href="https://arcticwolf.com/" rel="nofollow noreferrer noopener" target="_blank">Arctic Wolf</a> to discuss the big hairy beast that is...(<em>insert dramatic music here</em>) logging and alerting! I work with a lot of clients (and you probably do too) who want answers to these questions:</p> <ul> <li>What in the world is going on in my network?</li> <li>How will I know if bad stuff is happening?</li> <li>If I <em>do</em> identify the bad stuff and attempt to eradicate it, how will I know if I've exorcised all the demons?</li> </ul><p>So Lane and I sat down to discuss this conundrum, and explore answers to other burning questions like:</p> <ul> <li>Why is it so hard to separate the signal from noise when trying to figure out what's happening in the bowels of your network?</li> <li>Should logging/alerting be a full-time job for one or more people?</li> <li>When does it make sense to outsource these responsibilities?</li> </ul><p>Check out today's interview to learn more, and also reach out to Arctic Wolf on their <a href="https://twitter.com/awnetworks?lang=en" rel="nofollow noreferrer noopener" target="_blank">Twitter</a> or <a href="https://www.linkedin.com/company/arctic-wolf-networks/" rel="nofollow noreferrer noopener" target="_blank">LinkedIn</a> for more information.</p>
