You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/manage-assets/assets-inventory-components.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,8 +144,9 @@ Click a Controls logo to see **Last test** details and the **Issues** count, spl
144
144
145
145
Asset tags are metadata labels applied to repository assets and build artifacts. You can use asset tags to tag based on predefined values, manage and apply security policies, and group assets based on common characteristics. The following asset types are available:
146
146
147
+
***GitHub custom properties** - lists the GitHub custom properties associated with your GitHub repository as a tag.
148
+
***User-defined tags** are customizable, as you can define their logic through Assets Policies. For example, you can set tags to label a repository that comes from a specific source, such as GitHub. Tags associated with assets are identified in the UI with the **Asset policy tags** name.
147
149
***System tags** are automatically assigned by Snyk based on asset names or detected keywords (for example, `codeowners`).
148
-
***User-defined tags** are customizable, as you can define their logic through Assets Policies. For example, you can set tags to label a repository that comes from a specific source, such as GitHub.
149
150
150
151
A repository asset tag can be added through Policies or be system-generated by Snyk Essentials to provide more context. Click on a tags field to view all tags.
151
152
@@ -170,6 +171,12 @@ A system-generated tag includes the following information:
170
171
171
172
### Tag rules overview
172
173
174
+
Tags are organized into three main categories:
175
+
176
+
* GitHub custom properties
177
+
* Asset policy tags
178
+
* System tags
179
+
173
180
System tags are automatically generated from the SCM repositories. System tags can be classified into three main categories:
Copy file name to clipboardExpand all lines: docs/manage-assets/assets-inventory-features.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,9 +76,6 @@ You can filter the information for all the inventory layouts and can use the fol
76
76
***Inactive**: The last commits were made in the last 3 - 6 months.
77
77
***Dormant**: No commits in the last 6 months.
78
78
***N/A**: There are no commits detected by Snyk Essentials.
79
-
***Source** - specify the asset source.
80
-
***Tags** - information about the detected languages and repository update status.
81
-
***Title\*** - represents the name of the component for which the application context catalog was configured.
82
79
83
80
{% hint style="info" %}
84
81
N/A indicates that the repository was detected through a Snyk scan but not directly from the SCM. To detect SCM repositories, you must set up SCM integration at the Group level.
Copy file name to clipboardExpand all lines: docs/manage-risk/policies/assets-policies/README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,8 +46,9 @@ Classify repository assets according to their business criticality from A (most
46
46
47
47
Categorize and label repository assets with [asset tags](../../../manage-assets/assets-inventory-components.md#asset-tags) to filter the asset inventory. 
48
48
49
-
***System tags** - are automatically assigned by Snyk according to recognized keywords. 
50
-
***User-defined tags** - are customizable, as you can define the logic governing them through [Assets Policies](./). 
49
+
***GitHub custom properties** - lists the GitHub custom properties associated with your GitHub repository as a tag
50
+
***User-defined tags** are customizable, as you can define their logic through [Assets Policies](./). For example, you can set tags to label a repository that comes from a specific source, such as GitHub. Tags associated with assets are identified in the UI with the **Asset policy tags** name.
51
+
***System tags** are automatically assigned by Snyk based on asset names or detected keywords (for example, `codeowners`).
Copy file name to clipboardExpand all lines: docs/manage-risk/policies/assets-policies/create-policies.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,6 +65,7 @@ Each property contains different options for conditions and values:
65
65
| Catalog name\*| <ul><li>Is one of</li><li>Is not one of</li></ul> | the list of names of your application context. |
66
66
| Category | <ul><li>Is one of</li><li>Is not one of</li></ul> | the list of the available categories of a repository asset |
67
67
| Class | <ul><li>Is one of</li><li>Is not one of</li></ul> | A, B, C, D |
68
+
| Clusters | <ul><li>containing one or more of</li><li>containing all of</li><li>not containing one or more of</li><li>not containing all of</li></ul> | the list of the available clusters |
68
69
| Coverage | <ul><li>containing one or more of</li><li>containing all of</li><li>not containing one or more of</li><li>not containing all of</li></ul> | Snyk Code, Container, IaC, Open Source |
69
70
| Coverage gap | <ul><li>containing one or more of</li><li>containing all of</li><li>not containing one or more of</li><li>not containing all of</li></ul> | Snyk Code, Container, IaC, Open Source |
70
71
| Developers | <ul><li>is</li><li>is not</li><li>contains</li><li>does not contain</li><li>starts with</li><li>ends with</li></ul> |\[string]|
@@ -75,6 +76,7 @@ Each property contains different options for conditions and values:
75
76
| Lifecycle\*| <ul><li>Is one of</li><li>Is not one of</li></ul> | the available list of the lifecycle states of the application context component |
76
77
| Locked attributes | <ul><li>is one of</li><li>is not one of</li></ul> | <ul><li>Class</li></ul> |
77
78
| Owner\*| <ul><li>is one of</li><li>is not one of</li></ul> | the list of teams owning the repository for which the application context was configured. |
79
+
| Related package | <ul><li>is</li><li>is not</li><li>contains</li><li>does not contain</li><li>starts with</li><li>ends with</li></ul> |\[string]|
78
80
| Risk factors | <ul><li>containing one or more of</li><li>containing all of</li><li>not containing one or more of</li><li>not containing all of</li></ul> | the list of available risk factors |
0 commit comments