Skip to main content

Mondoo 11.13 is out!

· 4 min read
Tim Smith
Tim Smith
Mondoo Core Team

🥳 Mondoo 11.13 is out! This release includes support for additional workflows, advanced scoring mechanisms, notifications on failing integrations, and more!​

Get this release: Installation Docs | Package Downloads | Docker Container

🎉 NEW FEATURES​

Exceptions for vendor advisories​

You can now set exceptions on advisories, not just checks. To set an exception on an advisory, navigate to an asset's Advisories tab and select the advisories to snooze or disable.

To learn more, read the Mondoo documentation.

Selecting advisories to create exceptions

Choose the security scoring system for each policy in a space​

Mondoo policies support several different scoring systems, depending on how you want to weight the results of the policy. While the recommended scoring mechanism for each policy is built into the policy itself, you can now override the scoring mechanism used directly from the Mondoo console.

Selecting a scoring system for a policy

Failing integration notification​

Tokens may expire and accounts might change. Now you can quickly spot when integrations stop scanning as they should. Space owners will notice a new icon in the integrations menu whenever an issue arises. Plus, any failing integrations are highlighted on the Integrations page, so you can identify the problem type at a glance without diving into each page.

Integrations showing failures

Updated asset tables on individual checks​

The table of affected assets on each individual check page is now much more informative, showing last update time, additional risk factors, risk score, and asset name. It also supports multi-select for building targeted cases.

Integrations showing failures

Create cases directly from policy check pages​

Cases are a new feature of Mondoo that allow you to turn security findings into tasks to complete. They integrate with Atlassian Jira to fit into your existing workflow.

Mondoo Case Management Screen

When you see a security finding that requires fixing, you create a case for that finding. Mondoo automatically includes the details of the finding, information on the asset(s) that contain the finding, and instructions for fixing it. When you save the case, Mondoo automatically creates an issue containing all the same information in your Jira project.

To create cases from failing checks, simply open a check and click the 'Create Case' button. To learn more, read the Mondoo documentation.

🧹 IMPROVEMENTS​

Updated CIS Windows 10 / 11 benchmark policies​

Secure Windows endpoints with the latest CIS Windows 10 and 11 benchmark policies: version 3.0. This major version bump includes a large refactoring of the recommendations for securing Windows hosts, including new and updated recommendations, improved descriptions and remediation text, and overall improvements to queries to ensure you always have the best output to work with.

🐛 BUG FIXES AND UPDATES​

  • Immediately refresh asset check overview statistics when exceptions are set.
  • Fix incorrect check impact scores displayed on assets.
  • Ensure editors can't create API tokens with higher privileges.
  • Allow sorting by blast radius in tables.
  • Fix policy check pages not showing all affected assets.
  • Don't include checks with exceptions in check counts.
  • Expand the data included in data exports to include space metadata, base score, and risk score.
  • Fix backwards sorting in risk score table columns.
  • Allow sorting by last updated time in affected asset tables.
  • Fix incorrect scores on versioned software pages.
  • Don't scan Azure Storage containers as part of the --discover all command line option.
  • Use fully qualified Kubernetes names to ensure assets are unique.
  • Show cnspec status output when the client fails to communicate with the platform.
  • Substantially improve the reliability of multiple Linux CIS benchmark queries.
  • Fix format changes introduced to the CSV data export that were not backwards compatible.
  • Fix some CI scan results failing to load in the console.
  • Use more consistent names for out-of-the-box data pack queries.