GITBOOK-8670: vc-Remove OS condition from the funnel view

docs/manage-risk/prioritize-issues-for-fixing/assets-and-risk-factors-for-snyk-apprisk/README.md

@@ -48,17 +48,17 @@ By understanding your images, packages, and Kubernetes resources as "application
 * [OS condition](risk-factor-os-condition.md)
 * [Public facing](risk-factor-public-facing.md)
 
-You can enable and disable all of these "application context" risk factors through the Group **Settings**, on the **Insights** UI tab. If you choose to disable a risk factor, a provider selection, or the Kubernetes cluster mapping, Snyk will no longer compute them. 
+You can enable and disable all of these "application context" risk factors through the Group **Settings**, on the **Issues** UI tab. If you choose to disable a risk factor, a provider selection, or the Kubernetes cluster mapping, Snyk will no longer compute them. 
 
 {% hint style="info" %}
 The Risk Factors are available only for Snyk AppRisk Pro.
 
-In the Snyk Web UI, the Insights tab in the Group Settings is available only for Snyk AppRisk Pro. 
+In the Snyk Web UI, the Issues tab in the Group Settings is available only for Snyk AppRisk Pro. 
 {% endhint %}
 
 Depending on the integration options enabled for your application, risk factors are applied differently. You can [prioritize your integrations](../set-up-insights-for-snyk-apprisk/#prioritize-your-integrations) by customizing the available Insights options from the Group settings.
 
-<figure><img src="../../../.gitbook/assets/image (457).png" alt="Snyk AppRisk Pro - Insights tab in the Group settings"><figcaption><p>Snyk AppRisk Pro - Insights tab in the Group settings</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (640).png" alt=""><figcaption><p>Snyk AppRisk - Insights tab in the Group settings</p></figcaption></figure>
 
 {% hint style="info" %}
 Risk factor settings may take up to four hours to take effect.

docs/manage-risk/prioritize-issues-for-fixing/assets-and-risk-factors-for-snyk-apprisk/risk-factor-os-condition.md

@@ -26,7 +26,7 @@ When an image is scanned by Snyk Container, the information about which operatin
 
 ## Kubernetes Connector integration
 
-The OS condition risk factor works with your Kubernetes Connector integrations. 
+The OS condition risk factor works with your [Kubernetes Connector](../set-up-insights-for-snyk-apprisk/set-up-insights-kubernetes-connector.md) integrations. 
 
 The Kubernetes Connector leverages the OS condition risk factors to enhance the identification of vulnerabilities within containerized applications. It continuously checks and compares the operating systems of running containers with the known risk factors from the Snyk database. This integration helps to detect potentially vulnerable packages or images in real-time based on the operating system conditions. It allows proactive security measures within Kubernetes environments.
 

docs/manage-risk/prioritize-issues-for-fixing/assets-and-risk-factors-for-snyk-apprisk/risk-factor-public-facing.md

@@ -15,7 +15,7 @@ The Snyk platform analyzes various data sources to compute the network connectiv
 Cloud-native solutions are deterministic in how network connectivity is configured. Snyk uses that knowledge to compute the answers based on the available information. For example,  to understand how the network connectivity can be configured, see Kubernetes [Services](https://kubernetes.io/docs/concepts/services-networking/service/) and [Ingresses](https://kubernetes.io/docs/concepts/services-networking/ingress/) documentation. 
 
 {% hint style="info" %}
-Snyk AppRisk Insights currently supports the following configurations: Kubernetes services and ingress, and Gloo.
+Snyk AppRisk Issues supports the following configurations: Kubernetes services and ingress, and Gloo.
 {% endhint %}
 
 Kubernetes Connector checks the images for ingress configuration. If not detected, the image is considered public facing.
@@ -32,7 +32,7 @@ The Kubernetes Connector continuously monitors the Kubernetes events. These even
 
 Every hour, the data pipeline performs a reconciliation of the state of the cluster to create a snapshot. This snapshot is used to compute the network relationship between various resources, such as services to pods and ingresses to services. The same snapshot is used to extrapolate which images are running at that time.
 
-The analysis is currently performed only based on the connectivity specification. The granularity of the analysis is performed on `port` and `http path` levels. Various constraints may be applied to configured paths, such as network policies, security groups, and firewalls. Snyk currently does not include the constraints in the computation. 
+The analysis is performed only based on the connectivity specification. The granularity of the analysis is performed on `port` and `http path` levels. Various constraints may be applied to configured paths, such as network policies, security groups, and firewalls. Snyk does not include the constraints in the computation. 
 
 At the same interval, the data pipeline takes a snapshot of all Snyk Projects and data sources and extrapolates packages and images. This snapshot is used to determine which images and packages are known to Snyk for any given customer. 
 

docs/manage-risk/prioritize-issues-for-fixing/set-up-insights-for-snyk-apprisk/README.md

@@ -125,7 +125,7 @@ When prioritizing issues, it is important to understand the available integratio
 Here are the integration options that you can choose from when setting up issues prioritization. You can customize the settings by navigating to the Group level [Snyk Web UI](../../../getting-started/snyk-web-ui.md), the Setting menu, and then the Insights option. 
 
 * [**Snyk Runtime Sensor**](../../snyk-apprisk/integrations-for-snyk-apprisk/snyk-runtime-sensor.md): Used for deeper runtime analysis, providing detailed insight into the actual usage and potential vulnerabilities of your applications during execution. This sensor helps in gathering live traffic data, identifying runtime vulnerabilities, and assessing potential risks based on real-time application behavior.
-* **Kubernetes Connector**: Offers comprehensive monitoring for your Kubernetes deployments. This integration helps identify vulnerabilities within Kubernetes clusters and provides data on workload vulnerabilities, infrastructure misconfigurations, and potential malicious activity.
+* [**Kubernetes Connector**](set-up-insights-kubernetes-connector.md): Offers comprehensive monitoring for your Kubernetes deployments. This integration helps identify vulnerabilities within Kubernetes clusters and provides data on workload vulnerabilities, infrastructure misconfigurations, and potential malicious activity.
 * [**Third-party Integrations**](../../snyk-apprisk/integrations-for-snyk-apprisk/connect-a-third-party-integration.md): These integrations, such as cloud providers or CI/CD tools, provide additional context and data sources for better vulnerability assessment. They help identify misconfigurations, exposure points, and integration-specific vulnerabilities.
 
 ### Risk factors mapped to integration options

docs/manage-risk/prioritize-issues-for-fixing/set-up-insights-for-snyk-apprisk/set-up-insights-user-permissions.md

@@ -4,7 +4,7 @@
 The Set up Insights option is available only with Snyk AppRisk Pro.
 {% endhint %}
 
-Currently, Snyk AppRisk is available at the Group level, so [grant relevant users the Group viewer or the Organization Collaborator role](../../../snyk-admin/user-roles/user-role-management.md#manage-roles). This is the minimum required permission, but Group Admins can also view Prioritization.
+Snyk AppRisk is available at the Group level, so [grant relevant users the Group viewer or the Organization Collaborator role](../../../snyk-admin/user-roles/user-role-management.md#manage-roles). This is the minimum required permission, but Group Admins can also view Prioritization.
 
 After you have the right permission, you will see a new **Issues UI** option in the left navigation at the Group level. On the Issues page, you can also see two tabs, one for viewing and customizing your **Issues**, and one to **Set up Insights**.
 

docs/manage-risk/prioritize-issues-for-fixing/using-the-issues-ui-with-snyk-apprisk/filter-your-issues.md

@@ -14,9 +14,11 @@ Snyk AppRisk operates at the Group level and provides a holistic view of all the
 The Funnel view is available only for Snyk AppRisk Pro users.
 {% endhint %}
 
-The funnel view is a visual representation of your application's issues and risk factors. It allows you to filter the list of issues by specific risk factors or a combination of them. The risk factors OS condition, Deployed, and Public facing are clickable filters.
+The funnel view is a visual representation of your application's issues and risk factors. It allows you to filter the list of issues by specific risk factors or a combination of them. The **Deployed** and **Public facing** risk factors are clickable filters.
 
-<figure><img src="../../../.gitbook/assets/image (468).png" alt="Snyk AppRisk Pro - Issues page, Funnel view"><figcaption><p>Snyk AppRisk Pro - Issues page, Funnel view</p></figcaption></figure>
+{% hint style="info" %}
+The OS Condition risk factor is now available only in the table view of the Issues UI.
+{% endhint %}
 
 ## Table view filters
 
@@ -39,7 +41,7 @@ The Risk Factor filter is available only for Snyk AppRisk Pro users.
 
 You can also add a variety of filters that you consider relevant for any particular scenario.
 
-Note that in an initial triage, you want to look at OS condition, Deployed, and Public facing, and choose both critical and high severity. Snyk Open Source finds critical vulnerabilities, while Snyk Code finds vulnerabilities up to high severity only. When you filter on the issues of greatest concern, filter for both critical and high severity.
+In an initial triage, you want to look at OS condition, Deployed, and Public facing, and choose both critical and high severity. Snyk Open Source finds critical vulnerabilities, while Snyk Code finds vulnerabilities up to high severity only. When you filter on the issues of greatest concern, filter for both critical and high severity.
 
 When you filter based on the Asset class and an issue is found in two different repositories with two different classes assigned, the class with the highest priority is displayed in Snyk AppRisk.
 

docs/manage-risk/prioritize-issues-for-fixing/using-the-issues-ui-with-snyk-apprisk/understand-your-issues.md

@@ -1,12 +1,12 @@
 # Understand your issues
 
-Snyk AppRisk Insights works by understanding your vulnerabilities within the context of your application. You can see all the gathered context in the list view of your issues. In the table view, you can see the following details:
+Snyk AppRisk Issues works by understanding your vulnerabilities within the context of your application. You can see all the gathered context in the list view of your issues. In the table view, you can see the following details:
 
 * Issue name, which redirects to the Projects page within that issue's Organization.
 * Identified risk factors together with the [evidence graph](evidence-graph.md).
 
 {% hint style="info" %}
-The Risk Factor and evidence graph information is available only for Snyk AppRisk Pro users.
+The Risk Factor and evidence graph information is available only to Snyk AppRisk Pro users.
 {% endhint %}
 
 * Exploit maturity
@@ -19,7 +19,3 @@ The Risk Factor and evidence graph information is available only for Snyk AppRis
 <figure><img src="../../../.gitbook/assets/image (467).png" alt="Snyk AppRisk Pro - Issues page, Table view of issues"><figcaption><p>Snyk AppRisk Pro - Issues page, Table view of issues</p></figcaption></figure>
 
 You can also sort the table of issues by these details.
-
-{% hint style="info" %}
-In the Issues UI, only IaC issues are supported. IaC+ issues are not supported, as IaC+ is  Closed Beta.
-{% endhint %}