mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-07-03 03:03:43 +00:00
new images
This commit is contained in:
Binary file not shown.
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
After Width: | Height: | Size: 41 KiB |
Binary file not shown.
After Width: | Height: | Size: 49 KiB |
Binary file not shown.
After Width: | Height: | Size: 57 KiB |
Binary file not shown.
After Width: | Height: | Size: 38 KiB |
@ -38,6 +38,8 @@ Once a zero-day vulnerability has been found, information about it will be conve
|
|||||||
|
|
||||||
Find recommendations with a zero-day tag in the “Top security recommendation” card.
|
Find recommendations with a zero-day tag in the “Top security recommendation” card.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
## Weaknesses page
|
## Weaknesses page
|
||||||
|
|
||||||
Find the named zero-day vulnerability along with a description and details.
|
Find the named zero-day vulnerability along with a description and details.
|
||||||
@ -46,23 +48,29 @@ Find the named zero-day vulnerability along with a description and details.
|
|||||||
|
|
||||||
- If this vulnerability has no CVE-ID assigned, you will find it under an internal, temporary name that looks like “TVM-XXXX-XXXX”. The name will be updated once an official CVE-ID has been assigned, but the previous internal name will still be searchable and found in the side-panel.
|
- If this vulnerability has no CVE-ID assigned, you will find it under an internal, temporary name that looks like “TVM-XXXX-XXXX”. The name will be updated once an official CVE-ID has been assigned, but the previous internal name will still be searchable and found in the side-panel.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
## Software inventory page
|
## Software inventory page
|
||||||
|
|
||||||
Find software with the zero-day tag.
|
Find software with the zero-day tag.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
## Software page
|
## Software page
|
||||||
|
|
||||||
Find a zero-day tag for each software that has been affected by the zero–day vulnerability.
|
Find a zero-day tag for each software that has been affected by the zero–day vulnerability.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
## Security recommendations page
|
## Security recommendations page
|
||||||
|
|
||||||
Clear suggestions regarding remediation and mitigation options, including workarounds if exist.
|
Clear suggestions regarding remediation and mitigation options, including workarounds if exist.
|
||||||
|
|
||||||
When there is an application with associated zero-day vulnerability and additional vulnerabilities to address , you will get one recommendation regarding both.
|
When there is an application with associated zero-day vulnerability and additional vulnerabilities to address , you will get one recommendation regarding both.
|
||||||
|
|
||||||
When a patch is released for the zero-day, the recommendation will be changed to “Update” and a blue label next to it that says “New security update for zero day.”
|

|
||||||
|
|
||||||

|
When a patch is released for the zero-day, the recommendation will be changed to “Update” and a blue label next to it that says “New security update for zero day.”
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user