Assets and risk factors for Snyk AppRisk
Last updated
Last updated
More information
Snyk privacy policy© 2024 Snyk Limited | All product and company names and logos are trademarks of their respective owners.
The capabilities of the Snyk AppRisk Issues menu rely on understanding your application context to help you better prioritize your security issues. It does that by understanding how your application is configured and relying on that information to provide you with triage and prioritization of your assets and issues for the Snyk AppRisk Essentials plan, and it also adds specific risk factors and evidence graph information for the Snyk AppRisk Pro plan.
Assets are analyzed using Snyk insights, focusing on images, Kubernetes resources, and packages to understand how they all interact with each other.
Risk factors are analyzed using Snyk insights and grouped into four main categories:
The following video presents the main functionalities that you can find in the Snyk AppRisk Issues UI:
Snyk AppRisk insights analyzes the assets described on this page.
Images are assets that represent a Docker image. Snyk Container performs security scans on the Docker images. Images can be mapped one to many with the Snyk Projects created by the scans performed by Snyk Container. Docker images have natural IDs, which are represented by SHAs. Snyk uses this natural ID to correlate the same images even if they are mapped to different Snyk Projects.
Kubernetes resources are assets that represent a Kubernetes object. The Kubernetes Connector collects resource information from the Kubernetes clusters.
Kubernetes resources do not map to the Snyk Projects. These are internal entities used to compute certain risk factors, further detailed on the rest of this page. These risk factors can be related to the packages and images.
Packages are assets that represent a software package. Snyk Open Source and Snyk Code products perform security scans on files. These files represent the package manager declaration and the source code of a software package, respectively. A package is a representation of that software package.
Packages can be mapped one to one with the Snyk Projects created by the scans performed by Snyk Open Source and Snyk Code. All the issues identified by these products and attributed to these Projects will be mapped to the package entity.
The term Package is a very coarse abstraction. It does not have versions. It is a representation of the current state of the software package at a point in time. The point in time is determined by the time when the Snyk processing pipeline is completed and the state of Snyk Projects at that time.
Snyk Open Source uses the word package to refer to the third-party dependencies declared in the package dependency manifest. Snyk does not currently expose the granularity of the third-party dependencies. However, from the prioritization data model point of view, there is no distinction between third-party and first-party packages. These would be represented as a package object at that point in time.
By understanding your images, packages, and Kubernetes resources as "application context", Snyk can compute the following risk factors:
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.
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.
Depending on the integration options enabled for your application, risk factors are applied differently. You can prioritize your integrations by customizing the available Insights options from the Group settings.
Risk factor settings may take up to four hours to take effect.
