Latest Stories

puzzle_blog_Small

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

Akshay Parvatikar

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.

Progress Chef

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.

Brian Loomis
Blog-Delivery_100x385_Small

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.

Brian Loomis
Blog-L_News_2_1283x494_Small

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.

Anugraha Benjamin
Blog-Infrastructure_100x385_Small

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

Sudeep Charles
Blog-Infrastructure_100x385_Small

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

Vasundhara Jagdale

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.

Kiah Tolliver
Blog-Infrastructure_100x385_Small

Redefining endpoint compliance by codifying your fleet

Sudeep Charles