Date: Wed, 9 Feb 2022 15:00:00 +0000
<p>The recent log4j fiasco reminded us that not only is it important to stay updated and current with security news, but it's also critical to have safe ways to deploy configuration updates or orchestrate reporting/remediation scripts across your infrastructure as quickly as possible. Jeremy and Nick join us today to share best practices and automation suggestions.</p><p><strong>Learn more:</strong></p><ul><li>Join our community at <a href="https://slack.puppet.com">https://slack.puppet.com</a></li><li>Contribute to the module at <a href="https://github.com/puppetlabs/log4jscanner">https://github.com/puppetlabs/log4jscanner</a></li><li>Download the module from its Forge page: <a href="http://forge.puppet.com/puppetlabs/log4jscanner">http://forge.puppet.com/puppetlabs/log4jscanner</a></li><li>Read about Puppet's security response policies <a href="https://puppet.com/security/">https://puppet.com/security/</a></li><li>Reach Jeremy Mill on Twitter at <a href="https://twitter.com/living_syn">@living_syn</a></li></ul><p><i>Update: the GI Joe quote our hapless host massacred was – "Now you know; and knowing is half the battle."</i></p>
