diff --git a/docs/platform/cases/advisories.mdx b/docs/platform/cases/advisories.mdx index 6e3551be..a9e80172 100644 --- a/docs/platform/cases/advisories.mdx +++ b/docs/platform/cases/advisories.mdx @@ -1,16 +1,14 @@ --- title: Create Cases from Advisories sidebar_label: Create Cases from Advisories -sidebar_position: 5 +sidebar_position: 70 description: Cases, which integrate with your ticket system, allow you to track remediation of important security findings. Create a case from an advisory to track work on that advisory within your existing workflow. image: /img/featured_img/mondoo-feature.jpg --- Use cases to track the work of fixing advisories in your existing workflow. When a Mondoo space has the [cases feature configured](/platform/cases/overview/), any team member can create a case from an advisory. Creating a case can: -- Create a new a Jira issue - -- Create a new Zendesk ticket +- Directly create a new a Jira issue, GitHub issue, GitLab issue, or Zendesk ticket - Send an email message to the recipient of your choice, such as a listener for your ticket, issue tracking, or project management software @@ -38,20 +36,20 @@ import Partial from "../partials/_editor-owner.mdx"; ![Create a new case in Mondoo](/img/platform/cases/new-case.png) -6. In the **Integration** box, select the where you want Mondoo to add or send the case information and provide a specific destination: - - - If you select a direct Jira integration, in the **Project** box, select the name of the project where you want to create an issue. - - - If you select an email integration, in the **Recipient** box, select where to send an email message with the case details. +6. In the **Integration** box, specify where you want Mondoo to add or send the case information. -7. Edit the issue summary as you wish and select the **CREATE CASE** button. +7. Edit the issue summary or title as you wish and select the **CREATE CASE** button. - Mondoo creates a new case in the space and then creates a corresponding Jira issue or Zendesk ticket or sends email to the selected recipient. + Mondoo creates a new case in the space and then creates a corresponding issue or ticket in your ticket system, or sends email to the selected recipient. ## Learn more - [Track and Fix Findings with Cases and Your Ticket System](/platform/cases/overview/) +- [Set up Cases and GitHub](/platform/cases/setup-github/) + +- [Set up Cases and GitLab](/platform/cases/setup-gitlab/) + - [Set up Cases and Jira](/platform/cases/setup/) - [Set up Cases and Zendesk](/platform/cases/setup-zendesk/) diff --git a/docs/platform/cases/checks.mdx b/docs/platform/cases/checks.mdx index bbd8d829..ff27ba24 100644 --- a/docs/platform/cases/checks.mdx +++ b/docs/platform/cases/checks.mdx @@ -1,16 +1,14 @@ --- title: Create Cases from Checks sidebar_label: Create Cases from Checks -sidebar_position: 6 +sidebar_position: 80 description: Cases, which integrate with your ticket system, allow you to track remediation of important security findings. Create a case from a check to track work on that check within your existing workflow. image: /img/featured_img/mondoo-feature.jpg --- Use cases to track the work of fixing failed checks in your existing workflow. When a Mondoo space has the [cases feature configured](/platform/cases/overview/), any team member can create a case from an advisory. Creating a case can either: -- Create a new a Jira issue - -- Create a new Zendesk ticket +- Directly create a new a Jira issue, GitHub issue, GitLab issue, or Zendesk ticket - Send an email message to the recipient of your choice, such as a listener for your ticket, issue tracking, or project management software @@ -38,20 +36,20 @@ import Partial from "../partials/_editor-owner.mdx"; ![Create a new case in Mondoo](/img/platform/cases/new-case-check.png) -6. In the **Integration** box, select the where you want Mondoo to add or send the case information and provide a specific destination: - - - If you select a direct Jira integration, in the **Project** box, select the name of the project where you want to create an issue. - - - If you select an email integration, in the **Recipient** box, select where to send an email message with the case details. +6. In the **Integration** box, specify where you want Mondoo to add or send the case information. -7. Edit the issue summary as you wish and select the **CREATE CASE** button. +7. Edit the issue summary or title as you wish and select the **CREATE CASE** button. - Mondoo creates a new case in the space and then creates a corresponding Jira issue or Zendesk ticket or sends email to the selected recipient. + Mondoo creates a new case in the space and then creates a corresponding issue or ticket in your ticket system, or sends email to the selected recipient. ## Learn more - [Track and Fix Findings with Cases and Your Ticket System](/platform/cases/overview/) +- [Set up Cases and GitHub](/platform/cases/setup-github/) + +- [Set up Cases and GitLab](/platform/cases/setup-gitlab/) + - [Set up Cases and Jira](/platform/cases/setup/) - [Set up Cases and Zendesk](/platform/cases/setup-zendesk/) diff --git a/docs/platform/cases/manage.mdx b/docs/platform/cases/manage.mdx index 70b1a517..1ff443a8 100644 --- a/docs/platform/cases/manage.mdx +++ b/docs/platform/cases/manage.mdx @@ -1,7 +1,7 @@ --- title: Manage Cases sidebar_label: Manage Cases -sidebar_position: 7 +sidebar_position: 90 description: Cases, which integrate with Atlassian Jira, allow you to track remediation of important security findings. View cases and close them in Mondoo or Jira. Change cases settings in the Mondoo space settings. image: /img/featured_img/mondoo-feature.jpg --- @@ -68,19 +68,80 @@ import Partial from "../partials/_editor-owner.mdx"; :::note -Closing an ticket or issue in your ticket system or does not close the corresponding case in Mondoo. If you create cases using a direct Jira or Zendesk integration, a space-wide setting controls whether closing a case in Mondoo automatically closes the corresponding issue in Jira. To learn more, read the section below. +Closing an ticket or issue in your ticket system or does not close the corresponding case in Mondoo. If you create cases using a direct integration with your ticket system, a space-wide setting controls whether closing a case in Mondoo automatically closes the corresponding issue/ticket in your ticket system. To learn more, read the section below. ::: -### Choose whether to closes tickets/issues when you close cases +## Automatically create cases on drift + +Drift occurs when, instead of improving security, an asset becomes _more_ vulnerable to attack: + +- An asset previously passed a check in a policy but is now failing that check + +- Mondoo previously did not detect a vulnerability on an asset, but now does detect that vulnerability + +It's important to catch drift quickly. Mondoo makes that possible with automatic drift detection. When an asset becomes less secure, Mondoo can automatically create a case to alert you of the change and track the work on resolving the problem. + +The space setting **Automatically create cases on drift** controls whether Mondoo creates a case when it detects drift. + +![Cases space settings in Mondoo](/img/platform/cases/space-settings.png) + +To enable or disable automatic drift cases: + +{" "} + +1. Navigate to the space where you want to change the drift setting. + +2. In the navigation sidebar, select **Settings** and then select the **Cases** tab. + +3. Enable or disable **Automatically create cases on drift**. + + +### Choose a destination for drift cases + +Like all cases, Mondoo can share automatically created drift cases with your ticket system. When you add a new ticket integration for cases, you choose whether to create drift issues/tickets. You can also change this option any time in the space settings: Enable or disable **Create drift issues in this integration**. For direct integrations, you also specify the default destination for drift tickets/issues. + +To choose a destination for automatic drift cases: + +{" "} + +1. Navigate to the space where you want to change the drift setting. + +2. In the navigation sidebar, select **Settings** and then select the **Cases** tab. + +3. Locate the settings for your integration and enable or disable **Create drift issues/tickets in this integration**. + +4. For direct integrations, specify where to create drift issues/tickets. + +### Group similar drift occurrences into one case + +If the same drift occurs on multiple assets, you may not want a separate case for each asset. Mondoo can group the drift detection of multiple assets into a single case. To do this, it waits a configurable period of time before finalizing a case and creating an issue or ticket in your ticket system. + +For example, suppose you configure Mondoo to create a new case and a corresponding Jira issue whenever it detects drift. You also configure Mondoo to wait four hours to group multiple instances of the same drift into one case. Mondoo scans asset 1, which fails check X. Mondoo identifies that asset 1 previously passed check X. This is drift, so Mondoo generates a case. However, Mondoo doesn't immediately save the case or create a Jira issue. Instead, Mondoo waits four hours to determine if any other assets also have incurred drift on check X. During these four hours, asset 5 and asset 6, which previously passed check X, now fail check X. Instead of creating new cases for assets 5 and 6, Mondoo adds information about assets 5 and 6 to the case initially created for asset 1. Now there is a single case with information about the three assets that incurred drift on check X. When four hours have passed, Mondoo creates a single Jira issue with the details about asset 1, asset 5, and asset 6 all incurring drift on check X. + +The **Aggregation window** space setting controls how long Mondoo waits to group similar drift occurrences in a single case. You either choose a time period or choose **No aggregation** to create a unique case (and corresponding issue or ticket) for each asset that incurs the same drift. + +To automatically group similar drift occurrences into one case: + +{" "} + +1. Navigate to the space where you want to change the drift settings. + +2. In the navigation sidebar, select **Settings** and then select the **Cases** tab. + +3. In the **Aggregation window** drop-down list, choose how long to wait to detect the same drift on other assets before finalizing a case and creating an issue/ticket in your ticket system. + +## Choose whether to close tickets/issues when you close cases ![Space-wide cases settings](/img/platform/cases/space-settings.png) -You can choose whether to close the corresponding Jira issue or Zendesk ticket when you close a case in the Mondoo Console. This setting applies only to direct Jira or Zendesk integrations, not to email integrations. +You can choose whether to close the corresponding issue or ticket in your ticket system when you close a case in the Mondoo Console. This setting applies only to direct integrations, not to email integrations. + +{" "} 1. Navigate to the space where you want to change the closing behavior. -2. In the navigation sidebar, select **Settings**. +2. In the navigation sidebar, select **Settings** and then select the **Cases** tab. 3. Enable or disable **Automatically close tickets**. @@ -89,6 +150,10 @@ You can choose whether to close the corresponding Jira issue or Zendesk ticket w - [Track and Fix Findings with Cases and Your Ticket System](/platform/cases/overview/) +- [Set up Cases and GitHub](/platform/cases/setup-github/) + +- [Set up Cases and GitLab](/platform/cases/setup-gitlab/) + - [Set up Cases and Jira](/platform/cases/setup/) - [Set up Cases and Zendesk](/platform/cases/setup-zendesk/) diff --git a/docs/platform/cases/overview.mdx b/docs/platform/cases/overview.mdx index 144d1e86..f5fe394e 100644 --- a/docs/platform/cases/overview.mdx +++ b/docs/platform/cases/overview.mdx @@ -2,37 +2,52 @@ title: Track and Fix Findings with Cases and Your Ticket System sidebar_label: Overview sidebar_position: 1 -description: Cases allow you to track remediation of important security findings in your Ticket system of choice, such as Jira or Zendesk. +description: Cases allow you to track remediation of important security findings in your Ticket system of choice, such as Jira, GitHub, GitLab, or Zendesk. image: /img/featured_img/mondoo-feature.jpg --- +import casesDirectDiagram from "/img/platform/cases/cases-direct-diagram.png"; +import casesEmailDiagram from "/img/platform/cases/cases-email-diagram.png"; + The work of improving your security posture can be daunting. Mondoo finds security issues in your infrastructure and prioritizes them so you know what problems to fix first. But how do you track the fixes and ensure that the work is completed? How do you communicate the most important tasks to your team? -*Cases* allow you to turn security findings into tasks to complete. They integrate with your ticket system (issue tracking software), such as Zendesk or Atlassian Jira, to fit into your existing workflow. +*Cases* allow you to turn security findings into tasks to complete. They integrate with your ticket system (issue tracking software), such as Zendesk, GitHub, GitLab, or Atlassian Jira, to fit into your existing workflow. + +When you see a security finding that requires fixing, you create a case for that finding. In the new case, Mondoo automatically includes the details of the finding, information on the asset(s) containing the finding, and instructions for fixing it. When you save the case, Mondoo can do any of these actions: + +- Directly create a GitHub issue -When you see a security finding that requires fixing, you create a case for that finding.In the new case, 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 can do any of these actions: +- Directly create a GitLab issue - Directly create a Jira issue + - Directly create a Zendesk ticket + - Send an email message to your ticket system (or any destination) -## Directly integrate cases with Jira +## Directly integrate cases with your ticket system + +If you directly configure cases with your ticket system, Mondoo creates a corresponding issue or ticket for every new case. Then you can plan, schedule, and track remediation work within your team's existing project workflow. -If you directly configure cases with your Jira instance, Mondoo creates a corresponding Jira issue for every new case. Once Mondoo creates an issue in Jira, you can plan, schedule, and track remediation work within your team's existing project workflow. + -![Cases in Mondoo and issues in Jira](/img/platform/cases/cases-jira-diagram.png) +Get started with a direct integration: -## Directly integrate cases with Zendesk +- [GitHub](/platform/cases/setup-github/) -If you directly configure cases with your Zendesk account, Mondoo creates a corresponding Zendesk ticket for every new case. Once Mondoo creates a ticket in Zendesk, you can plan, schedule, and track remediation work within your team's existing project workflow. +- [GitLab](/platform/cases/setup-gitlab/) -![Cases in Mondoo and tickets in Zendesk](/img/platform/cases/cases-zendesk-diagram.png) +- [Jira](/platform/cases/setup/) + +- [Zendesk](/platform/cases/setup-zendesk/) ## Integrate cases with your ticket system using email If you configure cases to send email to your ticket system, each time you create a new case, Mondoo sends an email message to the recipient you choose. Typically, this is the email address set up as a listener (or similar service) for your ticket, project management, or issue tracking software. Some examples are the Zendesk email channel, ServiceNow inbound email, and the Jira incoming mail handler. -![Cases in Mondoo and issues in Jira](/img/platform/cases/cases-email-diagram.png) + + +Get started with an [email integration](/platform/cases/setup-email/). ## Track and fix findings @@ -42,9 +57,7 @@ You can view and close cases in the Mondoo Console. When you set up cases in a M The email messages or Jira issues that Mondoo creates based on cases include all the details necessary for infrastructure owners to remediate findings. This gives all team members the information they need to address security issues, even if they don't have access to Mondoo. -Tracking and fixing findings with cases and your Ticket system involve: - -- Setting up cases with a [direct Jira integration](/platform/cases/setup/), a [direct Zendesk integration](/platform/cases/setup-zendesk/), or an [email integration](/platform/cases/setup-email/) +Tracking and fixing findings with cases and your ticket system involve: - [Creating cases from advisories](/platform/cases/advisories/) @@ -52,4 +65,8 @@ Tracking and fixing findings with cases and your Ticket system involve: - [Viewing and closing cases and managing cases settings](/platform/cases/manage/) +## Automatically create cases when drift is detected + +If an asset has become more exposed to attack since the last time Mondoo scanned it, that's _drift_. Mondoo can create a case when it detects drift. It can even group together multiple instances of the same drift on different assets. To learn more, read [Automatically create cases on drift](/platform/cases/manage#automatically-create-cases-on-drift). + --- diff --git a/docs/platform/cases/setup-email.mdx b/docs/platform/cases/setup-email.mdx index c00f7bb4..ccd39ff3 100644 --- a/docs/platform/cases/setup-email.mdx +++ b/docs/platform/cases/setup-email.mdx @@ -1,7 +1,7 @@ --- title: Set up Cases to Email Your Ticket System sidebar_label: Set up Cases with Email -sidebar_position: 4 +sidebar_position: 30 description: Mondoo cases, which you can integrate with your ticket, issue tracking, or project management software, allow you to track remediation of important security findings. Set up an integration to start using cases and include Mondoo data in your regular project workflow. image: /img/featured_img/mondoo-feature.jpg --- @@ -44,7 +44,9 @@ You can set up multiple recipients for case email messages. When you create a ne 6. To add another option for where to send case email messages, select ***ADD A RECIPIENT** and provide the details for Recipient 2, 3, and so on. -7. Select the **CREATE INTEGRATION** button. +7. To create a case and send email when an asset becomes more exposed to attack, enable **Create drift email to this recipient** and choose the recipient. To learn more, read [Automatically create cases on drift](/platform/cases/manage#automatically-create-cases-on-drift). + +8. Select the **CREATE INTEGRATION** button. ## Learn more diff --git a/docs/platform/cases/setup-github.mdx b/docs/platform/cases/setup-github.mdx new file mode 100644 index 00000000..0578aa02 --- /dev/null +++ b/docs/platform/cases/setup-github.mdx @@ -0,0 +1,94 @@ +--- +title: Set up Cases and GitHub Issues +sidebar_label: Set up Cases and GitHub Issues +sidebar_position: 22 +description: Mondoo cases, which you can directly integrate with GitHub Issues, allow you to track remediation of important security findings. Set up an integration with GitHub to start using cases and include Mondoo data in your GitHub issues. +image: /img/featured_img/mondoo-feature.jpg +--- + +Set up cases in a space to allow users in the space to keep track of security tasks and add GitHub issues directly from within the Mondoo Console. Cases setup involves configuring Mondoo to integrate with GitHub. + +For an overview of cases, read [Track and Fix Findings with Cases and Your Ticket System](/platform/cases/overview/). + +## Prerequisites + +- Owner or Editor access to the Mondoo space + +- A GitHub account with access to the project where you want Mondoo to add issues + +- Access to a GitHub organization or repository + +## Create a GitHub personal access token to give Mondoo access to the repository + +A _personal access token_ gives Mondoo the ability to create GitHub issues on your behalf. A token can grant access to an entire GitHub organization or only to specific repositories. Once + you share the token with Mondoo, any new cases created in the [space](/platform/start/organize/spaces/) can write new GitHub issues using that token. + +To learn more about personal access tokens, read [Managing your personal access tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) in the GitHub documentation. + +1. Log into GitHub. If you haven't verified your email address with GitHub, do that now. + +2. In the upper-right corner of any GitHub page, select your profile photo and then select Settings. + +3. In the left sidebar, select **Developer settings**. + +4. In the left sidebar, under **Personal access tokens**, select **Fine-grained tokens**. + +5. Near the top-right corner of the page, select the **Generate new token** button. + +6. In the **Token name** box, enter an easily identifiable name, such as `Mondoo cases integration`. + +7. In the **Resource owner** drop-down list, select the organization that owns the repository or repositories where you want Mondoo to create issues. + +8. In the **Expiration** drop-down list, select the number of days before the token expires. (Be sure to note the expiration date so that, as it approaches, you can create a new one without interrupting the Mondoo-GitHub integration.) + +9. Under **Repository access**, select **All repositories** to give Mondoo access to all the repositories in the chosen organization, or select **Only select repositories** and add the repositories you want to give Mondoo access to. + +10. Select **Repository permissions** and, in the **Issues** drop-down list, select **Read and write**. + +11. Select the **Generate token** button. + +12. Copy the token that GitHub generates. You need it in the next steps. + +:::note + +If your GitHub organization requires approval for personal access tokens, Mondoo can't use your token until a GitHub organization administrator approves the token. + +::: + +## Add a GitHub integration + +1. In the Mondoo Console, navigate to the space where you want to set up cases and, in the side navigation bar, select **Cases**. + + ![Configure cases in Mondoo](/img/platform/cases/cases-blank.png) + +2. Select the **ADD INTEGRATION** button. + + ![Configure cases in Mondoo](/img/platform/cases/cases-integrations.png) + +3. Select **GitHub Issues**. + + ![Configure cases in Mondoo](/img/platform/cases/cases-add-gh.png) + +4. In the **Choose an integration name** box, enter a name for the integration. Make it a name that clearly shows this is a GitHub integration. + +5. If you have a GitHub Enterprise account, in the **Provide GitHub Enterprise URL** box, type the URL for the account. This is the URL you use to access the home page for your GitHub account. An example is `https://github.mycompany.com`. + +6. In the **Provide your personal access token** box, paste the token you copied from GitHub in the steps above. + +7. To close a case in Mondoo when the corresponding GitHub issue closes, enable **Automatically close cases**. + +8. To create a case and a corresponding GitHub issue when an asset becomes more exposed to attack, enable **Create drift issues in this integration** and enter the GitHub organization and repository where you want to create new issues. To learn more, read [Automatically create cases on drift](/platform/cases/manage#automatically-create-cases-on-drift). + +9. Select the **CREATE INTEGRATION** button. + +## Learn more + +- [Create Cases from Advisories](/platform/cases/advisories/) + +- [Create Cases from Checks](/platform/cases/checks/) + +- [Manage Cases](/platform/cases/manage/) + +- [Track and Fix Findings with Cases and Your Ticket System](/platform/cases/overview/) + +--- diff --git a/docs/platform/cases/setup-gitlab.mdx b/docs/platform/cases/setup-gitlab.mdx new file mode 100644 index 00000000..841c977a --- /dev/null +++ b/docs/platform/cases/setup-gitlab.mdx @@ -0,0 +1,79 @@ +--- +title: Set up Cases and GitLab Issues +sidebar_label: Set up Cases and GitLab Issues +sidebar_position: 25 +description: Mondoo cases, which you can directly integrate with GitLab Issues, allow you to track remediation of important security findings. Set up an integration with GitLab to start using cases and include Mondoo data in your GitLab issues. +image: /img/featured_img/mondoo-feature.jpg +--- + +Set up cases in a space to allow users in the space to keep track of security tasks and add GitLab issues directly from within the Mondoo Console. Cases setup involves configuring Mondoo to integrate with GitLab. + +For an overview of cases, read [Track and Fix Findings with Cases and Your Ticket System](/platform/cases/overview/). + +## Prerequisites + +- A Mondoo account with Owner or Editor access to the space where you want to add the GitLab integration + +- Access to a GitLab group + +## Create a personal access token to give Mondoo access to GitLab + +A _personal access token_ gives Mondoo the ability to access GitLab resources on your behalf. For Mondoo to continuously monitor your GitLab groups, you must create a personal access token. + +1. Log into GitLab. + +2. In the upper-left corner of any GitLab page, select your profile photo and then select **Edit Profile**. + +3. In the left sidebar, select **Access tokens**. + +4. Select the **Add new token** button. + +5. In the **Token name** box, enter a name for the token, such as `mondoo-frontend-repo`. + +6. Under **Expiration date**, specify the date on which to expire the token. (Be sure to note the expiration date so that, as it approaches, you can create a new one without interrupting the Mondoo-GitLab integration.) + +7. Under **Select scopes**, check the **api** box. + +8. Select the **Create a personal access token** button. + +9. When GitLab finishes creating the token, it displays this message: "Your new personal access token has been created." Below the message, locate the **Your new personal access token** box. Use the copy icon to the right of the box to copy the token. + +To learn more, read [Create a personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token) in the GitLab documentation. + +## Add a GitLab integration + +1. In the Mondoo Console, navigate to the space where you want to set up cases and, in the side navigation bar, select **Cases**. + + ![Configure cases in Mondoo](/img/platform/cases/cases-blank.png) + +2. Select the **ADD INTEGRATION** button. + + ![Configure cases in Mondoo](/img/platform/cases/cases-integrations.png) + +3. Select **GitLab Issues**. + + ![Configure cases in Mondoo](/img/platform/cases/cases-add-gh.png) + +4. In the **Choose an integration name** box, enter a name for the integration. Make it a name that clearly shows this is a GitLab integration. + +5. If you self-host GitLab, enter your custom GitLab URL in the **Provide a GitLab base URL** box. This is the URL you use to access GitLab. If you don't self-host GitLab, leave the box empty. + +6. In the **Provide your personal access token** box, paste the token you copied from GitLab in the steps above. + +7. To close a case in Mondoo when the corresponding GitLab issue closes, enable **Automatically close cases**. + +8. To create a case and a corresponding GitLab issue when an asset becomes more exposed to attack, enable **Create drift issues in this integration** and enter the GitLab project where you want to create new issues. To learn more, read [Automatically create cases on drift](/platform/cases/manage#automatically-create-cases-on-drift). + +9. Select the **CREATE INTEGRATION** button. + +## Learn more + +- [Create Cases from Advisories](/platform/cases/advisories/) + +- [Create Cases from Checks](/platform/cases/checks/) + +- [Manage Cases](/platform/cases/manage/) + +- [Track and Fix Findings with Cases and Your Ticket System](/platform/cases/overview/) + +--- diff --git a/docs/platform/cases/setup-zendesk.mdx b/docs/platform/cases/setup-zendesk.mdx index 3f9eccc0..33415542 100644 --- a/docs/platform/cases/setup-zendesk.mdx +++ b/docs/platform/cases/setup-zendesk.mdx @@ -1,7 +1,7 @@ --- title: Set up Cases and Zendesk sidebar_label: Set up Cases and Zendesk -sidebar_position: 3 +sidebar_position: 29 description: Mondoo cases, which you can directly integrate with Zendesk, allow you to track remediation of important security findings. Set up an integration with Zendesk to start using cases and include Mondoo data in your Zendesk tickets. image: /img/featured_img/mondoo-feature.jpg --- @@ -52,7 +52,9 @@ Mondoo offers an alternative method for sharing cases with Zendesk: an email int 9. To close a case in Mondoo when the corresponding Zendesk ticket closes, enable **Automatically close cases**. -10. Select the **FINALIZE UPDATE** button. +10. To create a case and a corresponding Zendesk ticket when an asset becomes more exposed to attack, enable **Create drift issues in this integration**. To learn more, read [Automatically create cases on drift](/platform/cases/manage#automatically-create-cases-on-drift). + +11. Select the **FINALIZE UPDATE** button. ## Learn more diff --git a/docs/platform/cases/setup.mdx b/docs/platform/cases/setup.mdx index 1a00c144..851e65b0 100644 --- a/docs/platform/cases/setup.mdx +++ b/docs/platform/cases/setup.mdx @@ -1,7 +1,7 @@ --- title: Set up Cases and Jira sidebar_label: Set up Cases and Jira -sidebar_position: 2 +sidebar_position: 27 description: Mondoo cases, which you can directly integrate with Atlassian Jira, allow you to track remediation of important security findings. Set up an integration with Jira to start using cases and include Mondoo data in your Jira issues. image: /img/featured_img/mondoo-feature.jpg --- @@ -54,7 +54,9 @@ Mondoo offers an alternative method for sharing cases with Jira: an email integr 9. To close a case in Mondoo when the corresponding Jira issue closes, enable **Automatically close cases**. -10. Select the **FINALIZE UPDATE** button. +10. To create a case and a corresponding Jira issue when an asset becomes more exposed to attack, enable **Create drift issues in this integration** and choose the destination project. To learn more, read [Automatically create cases on drift](/platform/cases/manage#automatically-create-cases-on-drift). + +11. Select the **FINALIZE UPDATE** button. ## Learn more diff --git a/docs/platform/infra/saas/github.mdx b/docs/platform/infra/saas/github.mdx index 00f6b227..adf709b0 100644 --- a/docs/platform/infra/saas/github.mdx +++ b/docs/platform/infra/saas/github.mdx @@ -48,7 +48,7 @@ To learn more about personal access tokens, read [Managing your personal access 9. Select the **Generate token** button. -10. Copy the token that GitHub generates. You need in in the next steps. +10. Copy the token that GitHub generates. You need it in the next steps. ## Set up a GitHub integration diff --git a/docs/platform/infra/saas/gitlab.mdx b/docs/platform/infra/saas/gitlab.mdx index edca0e61..c256a3bc 100644 --- a/docs/platform/infra/saas/gitlab.mdx +++ b/docs/platform/infra/saas/gitlab.mdx @@ -29,11 +29,13 @@ A _personal access token_ gives Mondoo the ability to access GitLab resources on 3. In the left sidebar, select **Access Tokens**. -4. In the **Token name** box, enter a name for the token, such as `mondoo-frontend-repo`. +4. Select the **Add new token** button. -5. Under **Expiration date**, specify the date on which to expire the token. +5. In the **Token name** box, enter a name for the token, such as `mondoo-frontend-repo`. -6. Under **Select scopes**, check these scopes: +6. Under **Expiration date**, specify the date on which to expire the token. (Be sure to note the expiration date so that, as it approaches, you can create a new one without interrupting the Mondoo-GitHub integration.) + +7. Under **Select scopes**, check these scopes: - read_api @@ -43,13 +45,9 @@ A _personal access token_ gives Mondoo the ability to access GitLab resources on - read_registry -7. Select the **Create a personal access token** button. - -8. Scroll to the top of the page. - -9. When GitLab finishes creating the token, it displays this message: "Your new personal access token has been created." Below the message, locate the **Your new personal access token** box. +8. Select the **Create a personal access token** button. -10. Use the copy icon to the right of the box to copy **Your new personal access token**. +9. When GitLab finishes creating the token, it displays this message: "Your new personal access token has been created." Below the message, locate the **Your new personal access token** box. Use the copy icon to the right of the box to copy the token. To learn more, read [Create a personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token) in the GitLab documentation. diff --git a/static/img/platform/cases/cases-add-gh.png b/static/img/platform/cases/cases-add-gh.png new file mode 100644 index 00000000..770b26c7 Binary files /dev/null and b/static/img/platform/cases/cases-add-gh.png differ diff --git a/static/img/platform/cases/cases-add-gl.png b/static/img/platform/cases/cases-add-gl.png new file mode 100644 index 00000000..a7abaf59 Binary files /dev/null and b/static/img/platform/cases/cases-add-gl.png differ diff --git a/static/img/platform/cases/cases-direct-diagram.png b/static/img/platform/cases/cases-direct-diagram.png new file mode 100644 index 00000000..f1e4ac40 Binary files /dev/null and b/static/img/platform/cases/cases-direct-diagram.png differ diff --git a/static/img/platform/cases/cases-email-diagram.png b/static/img/platform/cases/cases-email-diagram.png index 2ff97f1f..b38dcd63 100644 Binary files a/static/img/platform/cases/cases-email-diagram.png and b/static/img/platform/cases/cases-email-diagram.png differ diff --git a/static/img/platform/cases/cases-integrations.png b/static/img/platform/cases/cases-integrations.png index 260b2cd0..8b0cda9c 100644 Binary files a/static/img/platform/cases/cases-integrations.png and b/static/img/platform/cases/cases-integrations.png differ diff --git a/static/img/platform/cases/cases-jira-diagram.png b/static/img/platform/cases/cases-jira-diagram.png deleted file mode 100644 index 50a24196..00000000 Binary files a/static/img/platform/cases/cases-jira-diagram.png and /dev/null differ diff --git a/static/img/platform/cases/cases-zendesk-diagram.png b/static/img/platform/cases/cases-zendesk-diagram.png deleted file mode 100644 index c1d2f130..00000000 Binary files a/static/img/platform/cases/cases-zendesk-diagram.png and /dev/null differ