The good we secure for ourselves is precarious and uncertain until it is secured for all of us and incorporated into our common life. How often do you verify your compliance? Once or twice a year? Have you considered reporting on compliance continually?
The usual suspects, Cody Valle (Head of community), Criag Comstock (Digger), and Nick Anderson (Doer of Things) see how CFEngine Enterprise can be used to implement and report on compliance, specifically the Ubuntu 20.04 Security Technical Implementation Guide (STIG). Nick shows how tagging variables for inventory and Mission Portals compliance reports can be used to implement compliance reporting that is continually verified.
Video
The video recording is available on YouTube:
At the end of every webinar, we stop the recording for a nice and relaxed, off-the-record chat with attendees. Join the next webinar to not miss this discussion.
Links
- CFEngine Build and vagrant projects
- Ubuntu 20.04 Security Technical Implementation Guide (STIG)
- Connect on LinkedIn w/ Cody, Craig, or Nick
- All Episodes
Further work
Help Nick implement Ubuntu 20.04 STIG inventory by opening pull requests here. Share your own compliance inventory policy and reports with other users by publishing a module on build.cfengine.com.
