אודות פרק זה
So your organization failed a compliance audit and got slapped with fines and penalties. Bummer! You pay the fine, spend a few days fixing your configurations, run a scan, and get ready to do it again come the next audit. But that approach doesn’t work anymore: The risks are too high, and fixing months of configuration drift at the drop of a hat (let alone hunting down all the paperwork for auditors) certainly isn’t your team’s favorite thing to do.
Demo Puppet Comply + CEM for cross-department visibility and automated compliance
The broad scope of today’s compliance management requires a coordinated effort from more than just the security team. In this episode of Pulling the Strings, two Puppet compliance experts make the case for cooperation among security, compliance, ops, and just about everyone else in your organization. They discuss the crumbling walls between security, compliance, and ops, as well as tools organizations use to ensure continuous compliance.
Highlights:
- Why organizations always wait until something goes wrong to pay attention to compliance + security
- The simple micro-adjustments that prevent massive corrections come audit time
- Working toward better alignment between teams so that they’re making compliance easier
- The point and benefits of continuous compliance – and why ‘cowboy compliance’ isn’t enough
- Why compliance frameworks matter across security, compliance, and ops
Speakers:
- Ben Ford, Community Lead at Puppet by Perforce
- Claire McDyre, Senior Product Manager at Puppet by Perforce
- Robin Tatam, Senior Director of Product Marketing, Puppet by Perforce
Links:
- Try Puppet Comply + CEM to give your whole team the power to tackle compliance
- Read Claire’s content on the Puppet blog
- Read Robin’s content on the Puppet blog
- Read the episode transcript
Find Us Online:
