GITBOOK-8785: vc-Update image description

docs/manage-risk/policies/assets-policies/create-policies.md

@@ -88,7 +88,7 @@ Each property contains different options for conditions and values:
 You can specify more than one filter component with an **And** or **Or** operator.\
 
 
-<figure><img src="../../../.gitbook/assets/Create policy New UI.png" alt="AppRisk - Create new policy"><figcaption><p>Snyk Essentials - Create new policy</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/Create policy New UI.png" alt="AppRisk - Create new policy"><figcaption><p>Snyk Web UI Policies - Create new policy</p></figcaption></figure>
 
 The following video explains the use of filters and the use of the **And**, **Or** operator.&#x20;
 
@@ -106,8 +106,8 @@ After defining filter components, you need to define the actions that the policy
 * **Set Asset Tag** - Sets a tag on the matched assets. Removing the policy or turning in off will remove the tags of this policy from the relevant assets.
 * **Set Coverage Control Policy** - Sets a control on filtered assets that checks whether selected security products are scanning assets, optionally within a given timeframe. Assets that fail this control will be marked accordingly on inventory pages. This control applies the OR logic across products.
 
-<figure><img src="../../../.gitbook/assets/Policy - Nwe UI.png" alt="AppRisk - Set a policy action"><figcaption><p>Snyk Essentials - Set a policy action </p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/Policy - Nwe UI.png" alt="AppRisk - Set a policy action"><figcaption><p>Snyk Web UI Policies - Set a policy action </p></figcaption></figure>
 
 The editor supports multiple flows for the same policy. The flows can be independent or intersect.
 
-<figure><img src="../../../.gitbook/assets/Multiple actions - New UI.png" alt="AppRisk - Set multiple policy actions "><figcaption><p>Snyk Essentials- Set multiple policy actions </p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/Multiple actions - New UI.png" alt="AppRisk - Set multiple policy actions "><figcaption><p>Snyk Web UI Policies- Set multiple policy actions </p></figcaption></figure>

docs/manage-risk/policies/assets-policies/implement-policies.md

@@ -17,7 +17,7 @@ You can hover over a policy to gain access to extra details:
 * **Clone** - Duplicates the policy.
 * **Delete** - Removes the policy.
 
-<figure><img src="../../../.gitbook/assets/Policies-New UI.png" alt="AppRisk - Policies overview screen"><figcaption><p>Snyk Essentials or Snyk AppRisk - Policies overview screen</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/Policies-New UI.png" alt="AppRisk - Policies overview screen"><figcaption><p>Snyk Web UI Policies - Overview screen</p></figcaption></figure>
 
 ## Customize a policy
 
@@ -27,7 +27,7 @@ Click any available policies to view them on the full screen and access all thei
 
 You can run a simulation to get an overview of how the policy is working. A number is displayed above the policy, indicating the total of assets found matching the criteria you added to the policy.&#x20;
 
-<figure><img src="../../../.gitbook/assets/Simulate Policies -New UI.png" alt="AppRisk - Policy simulation"><figcaption><p>Snyk Essentials - Policy simulation</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/Simulate Policies -New UI.png" alt="AppRisk - Policy simulation"><figcaption><p>Snyk Web UI Policies  - Policy simulation</p></figcaption></figure>
 
 ### Run the policy
 

docs/manage-risk/policies/assets-policies/use-cases-for-policies/classification-policy-use-case.md

@@ -17,13 +17,12 @@ If you just started using the classification policy, the recommendation is to fo
 
 The following example filters the assets that contain `sandbox`, `test`, and `to-delete` in their names. In Snyk Essentials, GitHub and GitLab topics are pulled in from the SCM integration and applied to repository assets, so if topics like `PCI-Compliance` have been added to repos in the SCM, Snyk can take those tags in Snyk Essentials and classify those assets as Class A.
 
-<figure><img src="../../../../.gitbook/assets/Create policy.png" alt="AppRisk - Setting up filters for a classification policy"><figcaption><p>Snyk Essentials or Snyk AppRisk - Setting up filters for a classification policy</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/Create policy.png" alt="AppRisk - Setting up filters for a classification policy"><figcaption><p>Snyk Web UI Policies  - Setting up filters for a classification policy</p></figcaption></figure>
 
 After you set up the filters, you need to apply a Class D asset classification to those assets.
 
-<figure><img src="../../../../.gitbook/assets/Set action.png" alt="AppRisk - Setting up actions for a classification policy"><figcaption><p>Snyk Essentials - Setting up actions for a classification policy</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/Set action.png" alt="AppRisk - Setting up actions for a classification policy"><figcaption><p>Snyk Web UI Policies - Setting up actions for a classification policy</p></figcaption></figure>
 
 You can apply a similar pattern and create actions for Class A, B, and C assets, within the same policy.
 
-<figure><img src="../../../../.gitbook/assets/Set Class.png" alt="AppRisk - Setting up multiple actions for a classification policy"><figcaption><p>Snyk Essentials - Setting up multiple actions for a classification policy</p></figcaption></figure>
-
+<figure><img src="../../../../.gitbook/assets/Set Class.png" alt="AppRisk - Setting up multiple actions for a classification policy"><figcaption><p>Snyk Web UI Policies - Setting up multiple actions for a classification policy</p></figcaption></figure>

docs/manage-risk/policies/assets-policies/use-cases-for-policies/coverage-control-policy-use-case.md

@@ -6,7 +6,7 @@ Identifying and setting coverage policies allows your team to define where certa
 
 The following example filters out assets that should have Snyk Open Source and Snyk Code security controls in place and then sets the coverage policies.
 
-<figure><img src="../../../../.gitbook/assets/image (2) (10).png" alt="AppRisk - Setting up a Coverage Control policy"><figcaption><p>Snyk Essentials - Setting up a Coverage Control policy</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (2) (10).png" alt="AppRisk - Setting up a Coverage Control policy"><figcaption><p>Snyk Web UI Policies  - Setting up a Coverage Control policy</p></figcaption></figure>
 
 To follow the example, these are the filters you need to apply:
 

docs/manage-risk/policies/assets-policies/use-cases-for-policies/notification-policy-use-case.md

@@ -30,15 +30,15 @@ If you want to set a **Send Slack Message** action, then you can generate the Sl
 
 Customize the Send Email action to notify you with a link to the assets impacted by the set policy. You can do this by typing "/" inside the **Body** field of the **Send Email** action and selecting **Link to Assets**. After you save the policy, every notification received will list all the assets impacted by the policy. 
 
-<figure><img src="../../../../.gitbook/assets/image (509).png" alt="Snyk AppRisk - Set up the Links to Assets option from the Send Email action "><figcaption><p>Snyk Essentials or Snyk AppRisk - Set up the Links to Assets option from the Send Email action </p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (509).png" alt="Snyk AppRisk - Set up the Links to Assets option from the Send Email action "><figcaption><p>Snyk Web UI Policies - Set up the Links to Assets option from the Send Email action </p></figcaption></figure>
 
 This is how your policy should look after all filters and actions are set.
 
-<figure><img src="../../../../.gitbook/assets/image (508).png" alt="Snyk AppRisk - Setting up a Notification policy"><figcaption><p>Snyk Essentials or Snyk AppRisk - Setting up a Notification policy</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (508).png" alt="Snyk AppRisk - Setting up a Notification policy"><figcaption><p>Snyk Web UI Policies - Setting up a Notification policy</p></figcaption></figure>
 
 You will receive an email notification after including the **Link to Assets** option in the Body field. You can access the assets from the notification individually, or view them in an aggregated form by clicking the **Click Here** link. The list of assets displayed in the email notification is automatically generated.
 
-<figure><img src="../../../../.gitbook/assets/image (510).png" alt="Snyk AppRisk - notification example from the Send Email action"><figcaption><p>Snyk Essentials or Snyk AppRisk - notification example from the Send Email action</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (510).png" alt="Snyk AppRisk - notification example from the Send Email action"><figcaption><p>Snyk Web UI Policies - notification example from the Send Email action</p></figcaption></figure>
 
 {% hint style="info" %}
 After an email notification policy is created, it is run in a maximum of 3 hours after creation, then once every 3 hours.&#x20;

docs/manage-risk/policies/assets-policies/use-cases-for-policies/tagging-policy-use-case.md

@@ -6,10 +6,10 @@ You can use the **Set Asset Tag** action to mark the repositories to which the f
 
 Snyk AppRisk has a number of pre-defined system tags that can be used for filtering and setting tags with policies. User-defined custom tags can be created using policies. You can create a Set Asset Tag policy action and define a custom tag by typing your tag in the tag search bar and selecting **Create new: `tag_name`**, for this example the `tag_name` being payment.
 
-<figure><img src="../../../../.gitbook/assets/image (10).png" alt="AppRisk - Creating a new tag" width="375"><figcaption><p>Snyk Essentials or Snyk AppRisk - Creating a new tag</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (10).png" alt="AppRisk - Creating a new tag" width="375"><figcaption><p>Snyk Web UI Policies - Creating a new tag</p></figcaption></figure>
 
 The following use case demonstrates how to apply the custom-defined `backend` tag to assets that match certain naming conventions. This allows a quick filter for backend assets from the Inventory view.
 
 This is how the policy should look after you finish setting up all filters and actions.
 
-<figure><img src="../../../../.gitbook/assets/Set tag.png" alt="AppRisk - Setting up a Set Asset Tag policy"><figcaption><p>Snyk Essentials - Setting up a Set Asset Tag policy</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/Set tag.png" alt="AppRisk - Setting up a Set Asset Tag policy"><figcaption><p>Snyk Web UI Policies - Setting up a Set Asset Tag policy</p></figcaption></figure>