# System Archaeology through Testing

**URL:** <https://discourse.chef.io/t/system-archaeology-through-testing/6585>\
**Category:** Chef Infra (archive)\
**Created:** [May 15, 2015, 9:45pm UTC](https://discourse.chef.io/t/system-archaeology-through-testing/6585 "2015-05-15T21:45:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jtimberman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jtimberman/32/8_2.png) [@jtimberman](https://discourse.chef.io/u/jtimberman)\
**Post date:** [May 15, 2015, 9:45pm UTC](https://discourse.chef.io/t/system-archaeology-through-testing/6585/1 "2015-05-15T21:45:23Z")

</div>

Ohai Chefs!

I wrote a blog post that you all may be interested in reading. It's an  
exploration of some discoveries I made while doing CIS[0](http://cisecurity.org) testing with  
audit-mode. The associated cookbook, libuuid-user, has a README[1](https://supermarket.chef.io/cookbooks/libuuid-user)  
that further illustrates and explains the subtle difference of intent  
for audit mode vs "plain" Serverspec.

> **[System Archaeology Through Testing - Chef Blog](https://blog.chef.io/system-archaeology-through-testing/)**
>
> As you may be aware, I have been working on a Chef audit-mode cookbook that implements the CIS Benchmarks. I recently added coverage for Ubuntu 14.04. In this post, I want to share a discovery about OS-level configuration that is inherently against...

Enjoy!  
Joshua