Guidelines on how to start with the Chef InSpec on the technical side.

To ensure compliance with sanctions imposed by the US and many more, we have decided we will cease to conduct business with new or existing customers in the areas covered by the sanctions.

The version number on releases of Chef Automate is changing from a daily build number to SemVer (major-minor) numbering to indicate recommended upgrade points for customers.

Guidance for users who completed the Chef Backend 2.2.0 migration and are still being alerted by scanning tools that Elastic Search may have a vulnerability.

Read how Chef enables IT teams to perform system hardening with the help of continuous security audits and remediation that detects and fixes vulnerabilities in diverse IT fleets.

An all-in-one solution for managing your Linux fleet

A developer’s guide to extending Chef InSpec through Ruby inheritance of core resources to re-use the core functionality in custom resources.

A new year is upon us, and with it comes a lot of new changes from the Chef team. First, you may have noticed that we’ve officially updated our branding to Progress Chef. Also, you’re about to witness a shift in how we stream.

Redefining endpoint compliance by codifying your fleet