diff --git a/docs/cnspec/cnspec-adv-install/windows.mdx b/docs/cnspec/cnspec-adv-install/windows.mdx index e9f06511..9257912a 100644 --- a/docs/cnspec/cnspec-adv-install/windows.mdx +++ b/docs/cnspec/cnspec-adv-install/windows.mdx @@ -29,7 +29,7 @@ import Partial from "./_providers-note.mdx"; :::info -If your organization's [region](/platform/start/organize/regions/) (in the Mondoo Console) is US, you must be able to access to us.api.mondoo.com. If your region is EU, you must be able to access to eu.api.mondoo.com. +If your organization's [region](/platform/start/organize/regions/) (in the Mondoo Console) is US, you must be able to access us.api.mondoo.com. If your region is EU, you must be able to access eu.api.mondoo.com. ::: @@ -54,9 +54,9 @@ Be sure you have access to these systems from PowerShell or CMD Terminal: ```powershell title="Check the Internet connectivity" install.mondoo.com Port 443/https releases.mondoo.com Port 443/https -eu.api.mondoo.com Port 443/https -us.api.mondoo.com Port 443/https -registry.api.mondoo.com Port 443/https +eu.api.mondoo.com Port 443/https +us.api.mondoo.com Port 443/https +registry.api.mondoo.com Port 443/https ``` To check connectivity, follow the approach in the previous section. @@ -89,9 +89,9 @@ Make sure TLS 1.2 is enabled (it's enabled by default in modern Windows systems) Install cnspec by downloading a PowerShell script to memory and running it: -If you wish later the scan happens by loading the configured Policy from your Mondoo Console space, you need to register by having a Registration Token which will be given to you during Integration from https://console.mondoo.com/. +If you wish later the scan happens by loading the configured Policy from your Mondoo Console space, you need to register by having a registration token which will be given to you during integration from https://console.mondoo.com/. -Without RegistrationToken, the policies will be automatically loaded from our Registry (https://mondoo.com/registry). It is only included the Open Source policies. +Without RegistrationToken set, the policies will be automatically loaded from our registry of open source policies. ```powershell title="Automated installation script" # $MONDOO_REGISTRATION_TOKEN="YOUR_TOKEN_HERE" @@ -131,7 +131,7 @@ If you enter a registration token during the installation wizard, cnspec registe You can also register by token later if needed: ```powershell title="CMD Terminal" -start /wait msiexec /i mondoo_8.9.1_windows_amd64.msi REGISTRATIONTOKEN="XXXXXXXXXXXXXXXXX" +start /wait msiexec /i mondoo_10.9.1_windows_amd64.msi REGISTRATIONTOKEN="XXXXXXXXXXXXXXXXX" ``` ## Test and troubleshoot @@ -172,7 +172,7 @@ Scan the local system: cnspec scan local ``` -Here the cnspec will automatically load the policies from Mondoo Console spaces provided you have registered the mondoo with the Token. Otherwise, the policies will be loaded from our Registry. +Here the cnspec will automatically load the policies from Mondoo Console spaces provided you have registered the mondoo with the token. Otherwise, the policies will be loaded from our registry. You can also force the cnspec to load the policies only from registry: diff --git a/docusaurus.config.js b/docusaurus.config.js index f5117a2b..3a672a7b 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -277,7 +277,7 @@ module.exports = { { to: "releases", label: "Releases" }, { label: "Blog", - href: "https://blog.mondoo.com/", + href: "https://mondoo.com/blog", }, ], }, diff --git a/releases/2023-08-14-mondoo-8.23-is-out.md b/releases/2023-08-14-mondoo-8.23-is-out.md index a9c1405c..bbe8def6 100644 --- a/releases/2023-08-14-mondoo-8.23-is-out.md +++ b/releases/2023-08-14-mondoo-8.23-is-out.md @@ -19,7 +19,7 @@ Get this release: [Installation Docs](/cnspec/) | [Package Downloads](https://re Are you struggling to achieve compliance with frameworks such as SOC 2, HIPAA, BSI, or PCI? Let the new Mondoo Compliance Hub do the heavy lifting for you. It automatically maps all of your existing security scans into the top compliance frameworks, allowing you to quickly view your progress towards compliance. And best of all, you'll never have to take a screenshot for manual evidence gathering again. -Learn more in our [Simplifying Compliance: Introducing the Mondoo Compliance Hub](https://blog.mondoo.com/simplifying-compliance-introducing-the-mondoo-compliance-hub) blog post. +Learn more in our [Simplifying Compliance: Introducing the Mondoo Compliance Hub](https://mondoo.com/blog/simplifying-compliance-introducing-the-mondoo-compliance-hub) blog post. ## 🧹 IMPROVEMENTS diff --git a/releases/2023-11-14-mondoo-9.7-is-out.md b/releases/2023-11-14-mondoo-9.7-is-out.md index 3fd2aac9..106c87f8 100644 --- a/releases/2023-11-14-mondoo-9.7-is-out.md +++ b/releases/2023-11-14-mondoo-9.7-is-out.md @@ -71,7 +71,7 @@ Atlassian admin, Jira, Confluence, and SCM assets scanned with cnspec are now gr ### Ubuntu 23.10 EOL/CVE detection -Ubuntu 23.10 is out, and Mondoo is ready with EOL reporting and CVE detection now available for this latest Ubuntu release. See our blog post [What's New in Security for Ubuntu 23.10](https://blog.mondoo.com/whats-new-in-security-for-ubuntu-23.10) to learn more about this release's great new security features. +Ubuntu 23.10 is out, and Mondoo is ready with EOL reporting and CVE detection now available for this latest Ubuntu release. See our blog post [What's New in Security for Ubuntu 23.10](https://mondoo.com/blog/whats-new-in-security-for-ubuntu-23-10) to learn more about this release's great new security features. ### Raspbian 11 and 12 CVE detection