Vogel Consulting Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-11 | Presenter: Chris Knospe | Export set: Top 12 | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): No items are selected for this quote. Total Estimated Time: 0 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top 12 vulnerabilities docx report - Ticket #1896221: Vulnerability Remediation - Microsoft .NET (all versions) - Update Required - Ticket #1896222: Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required - Ticket #1896223: Vulnerability Remediation - Google Chrome - Update Required - Ticket created: Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required - Ticket #1896224: Vulnerability Remediation - Microsoft Edge - Updates Required - Ticket created: Vulnerability Remediation - Mozilla Firefox - Update Required - Ticket created: Vulnerability Remediation - 7-Zip - Update Required - Ticket #1896225: Vulnerability Remediation - linux-x64 - Update Required - Ticket created: Vulnerability Remediation - 7-Zip 26.02 (x64 edition) - Update Required - Ticket created: Vulnerability Remediation - Cisco Webex Meetings - Update Required - Ticket created: Vulnerability Remediation - TeamViewer - Update Required - Ticket #1896226: Vulnerability Remediation - MSTeams - Update Required - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with Victoria to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
victoriaw@vogelcg.com
victoriaw@vogelcg.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Victoria, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 12): Open Top 12 report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Chris Knospe
2026 Q4 Remaining remediations
Good evening Victoria, Following the quarterly vulnerability review for Vogel Consulting, there are no remaining remediations to report. Sincerely, Chris Knospe
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Product/System: Microsoft .NET (all versions)
Affected Systems Count: 40
Finding summary:
Microsoft .NET (all versions) is outdated on the listed hosts.
These runtimes update within the same major version. An app built on one major version is tied to that version - removing it will break the app.
CVE references:
CVE-2022-38013
https://nvd.nist.gov/vuln/detail/CVE-2022-38013
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-38013
Additional CVEs (40 more) are listed in the Client Folder report.
Affected Systems:
Sorry for the long host list below (40 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- 192.168.10.111 [9.0.17] [81 vulns]
- 192.168.10.126 [9.0.17] [81 vulns]
- 192.168.10.111 [8.0.28] [75 vulns]
- 192.168.10.126 [8.0.28] [75 vulns]
- 192.168.10.111 [8.0.25] [68 vulns]
- 192.168.10.111 [32 vulns]
- 192.168.10.126 [32 vulns]
- 192.168.10.111 [10.0.9] [18 vulns]
- VogelLaptop2025 (Rhona) - 192.168.68.58 [3.1.27] [15 vulns]
- 192.168.10.111 [6.0.36] [3 vulns]
- Vogel-04894.vogelcg.local - 192.168.10.116 [6.0.36] [3 vulns]
- 192.168.10.126 [6.0.36] [3 vulns]
- Vogel-04894.vogelcg.local - 192.168.10.116 [2 vulns]
- Vogel-04816.vogelcg - 192.168.10.132 [6.0.36]
- Vogel-04817.vogelcg (LWichmann) - 192.168.10.103 [6.0.36]
- Vogel-04823.vogelcg - 192.168.10.123 [6.0.36]
- Vogel-04824.vogelcg (Pdietzman) - 192.168.10.129 [6.0.36]
- Vogel-04830.vogelcg (TScholz) - 192.168.10.108 [6.0.36]
- Vogel-04880.vogelcg (rvogel) - 192.168.10.122 [6.0.36]
- Vogel-04888.vogelcg (szur) - 192.168.10.127 [6.0.36]
- Vogel-05401a-.vogelcg - 192.168.10.113 [6.0.36]
- Vogel-05401.vogelcg - 192.168.10.135 [6.0.36]
- Vogel-05402.vogelcg (LDempsey) - 192.168.10.112 [6.0.36]
- Vogel-05412.vogelcg - 192.168.10.104 [6.0.36]
- Vogel-05413.vogelcg (GGrosenick) - 192.168.10.102 [6.0.36]
- Vogel-Home2.vogelcg (rvogel) - 192.168.1.188 [6.0.36]
- Vogel-TrainingB.vogelcg - 192.168.10.134 [6.0.36]
- Vogel-04816.vogelcg - 192.168.10.132
- Vogel-04817.vogelcg (LWichmann) - 192.168.10.103
- Vogel-04824.vogelcg (Pdietzman) - 192.168.10.129
- Vogel-04830.vogelcg (TScholz) - 192.168.10.108
- Vogel-04880.vogelcg (rvogel) - 192.168.10.122
- Vogel-04888.vogelcg (szur) - 192.168.10.127
- Vogel-05401a-.vogelcg - 192.168.10.113
- Vogel-05401.vogelcg - 192.168.10.135
- Vogel-05402.vogelcg (LDempsey) - 192.168.10.112
- Vogel-05412.vogelcg - 192.168.10.104
- Vogel-05413.vogelcg (GGrosenick) - 192.168.10.102
- Vogel-Home2.vogelcg (rvogel) - 192.168.1.188
- Vogel-TrainingB.vogelcg - 192.168.10.134
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the redistributable/runtime is not present or is already at/above the minimum version to reach for that major version.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- .NET Framework and modern .NET (.NET 5+) are not interchangeable
- An app built on one major version is tied to that version - removing it will break the app.
- Update each runtime line via WU/vendor installer; uninstall only when unused and verified
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET Core 3.x: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 6: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 8 (LTS): update runtime to the reported target within the 8.x line (Windows Update or runtime installer)
- .NET 9 (non-LTS): update 9.x runtime via WU/vendor installer, or uninstall if unused
- .NET 10 (LTS): update runtime to the reported target within the 10.x line
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Product/System: Microsoft 365 Apps for enterprise - en-us
Affected Systems Count: 2
Finding summary:
Microsoft 365 Apps for enterprise - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-50665
https://nvd.nist.gov/vuln/detail/CVE-2026-50665
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50665
Additional CVEs (165 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5124008. Apply the latest patch.
Affected Systems:
- 192.168.10.111 [166 vulns]
- 192.168.10.126 [166 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Google Chrome - Update Required
Vulnerability Remediation - Google Chrome - Update Required
Product/System: Google Chrome
Affected Systems Count: 21
Finding summary:
Google Chrome is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-76036
https://nvd.nist.gov/vuln/detail/CVE-2026-76036
Vendor security center:
https://chromereleases.googleblog.com/
Additional CVEs (1528 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 152.0.4191.66 (or the latest available). Update to version 153.0.8010.37 (or the latest available)
- Update to version 153.0.8010.37 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.10.0.252.3 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (21 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- 192.168.10.126 [1529 vulns]
- 192.168.10.111 [1084 vulns]
- Vogel-04894.vogelcg.local - 192.168.10.116 [230 vulns]
- Vogel-Home2.vogelcg (rvogel) - 192.168.1.188 [222 vulns]
- VB-188 (SamuelHarmer) - 192.168.1.212
- VB-220 (JayMomberg) - 192.168.41.118
- Vogel-04816.vogelcg - 192.168.10.132
- Vogel-04817.vogelcg (LWichmann) - 192.168.10.103
- Vogel-04824.vogelcg (Pdietzman) - 192.168.10.129
- Vogel-04830.vogelcg (TScholz) - 192.168.10.108
- Vogel-04888.vogelcg (szur) - 192.168.10.127
- Vogel-05401a-.vogelcg - 192.168.10.113
- Vogel-05401.vogelcg - 192.168.10.135
- Vogel-05412.vogelcg - 192.168.10.104
- Vogel-05413.vogelcg (GGrosenick) - 192.168.10.102
- VOGEL-DC04.vogelcg - 192.168.10.45
- VOGEL-FILE01.vogelcg - 192.168.10.46
- Vogel-TrainingB.vogelcg - 192.168.10.134
- Vogel-04823.vogelcg - 192.168.10.123
- Vogel-04880.vogelcg (rvogel) - 192.168.10.122
- Vogel-05402.vogelcg (LDempsey) - 192.168.10.112
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Chrome updates via Google Update (background); relaunch may be needed to apply a downloaded update
- If still behind: check Chrome update policy / Google Update scheduled tasks
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required
Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required
Product/System: Adobe Acrobat (64-bit)
Affected Systems Count: 9
Finding summary:
Adobe Acrobat (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-34621
https://nvd.nist.gov/vuln/detail/CVE-2026-34621
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (23 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.002.21901 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.3.3.0 (or the latest available)
- Update to version 26.001.21789 (or the latest available). Update to version 26.002.21901 (or the latest available). Update to version 5.7.1 (or the latest available)
- Update to version 26.002.21901 (or the latest available). Update to version 50.2.1.1 (or the latest available). Update to version 5.7.1 (or the latest available)
- Update to version 10.26.14 (or the latest available). Update to version 26.002.21901 (or the latest available)
- Update to version 26.002.21901 (or the latest available). Update to version 5.1.1 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.3.3.0 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
- VB-444 - 192.168.44.137 [24 vulns]
- 192.168.10.111 [1 vulns]
- 192.168.10.126 [1 vulns]
- Vogel-05401a-.vogelcg - 192.168.10.113 [1 vulns]
- Vogel-TrainingB.vogelcg - 192.168.10.134 [1 vulns]
- VB-188 (SamuelHarmer) - 192.168.1.212
- VB-220 (JayMomberg) - 192.168.41.118
- Vogel-04817.vogelcg (LWichmann) - 192.168.10.103
- Vogel-05401.vogelcg - 192.168.10.135
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm Acrobat Pro vs Adobe Reader (and 32 vs 64) on each host before choosing an installer
- Update to the reported remediation target
- RMM/automated patching when deployed
- Versions 20.x and 21.x are EOL - full upgrade to a supported track, not a security patch on 20/21
- Backstage (CMD/PS): deploy matching Acrobat installer/package (Admin Console when enterprise)
- Live user session only if needed: Help > Check for Updates
- Verify version after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Edge - Updates Required
Vulnerability Remediation - Microsoft Edge - Updates Required
Product/System: Microsoft Edge
Affected Systems Count: 2
Finding summary:
Microsoft Edge is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-58289
https://nvd.nist.gov/vuln/detail/CVE-2026-58289
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58289
Additional CVEs (1228 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 152.0.4191.66 (or the latest available). Update to version 153.0.8010.37 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- 192.168.10.126 [1229 vulns]
- 192.168.10.111 [826 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Auto-updating software: verify first, patch only if stale
- Confirm installed version against the reported target on affected hosts
- Edge updates via Microsoft Edge Update (primary); WU may also apply updates
- Relaunch may be needed for a downloaded update to take effect
- Live user session only if needed: edge://settings/help > Download and install
- Backstage (CMD/PS): silent installer/script only - not the Edge UI
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Mozilla Firefox - Update Required
Vulnerability Remediation - Mozilla Firefox - Update Required
Product/System: Mozilla Firefox
Affected Systems Count: 1
Finding summary:
Mozilla Firefox is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-84119
https://nvd.nist.gov/vuln/detail/CVE-2026-84119
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (30 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 155.0.1 (or the latest available).
Affected Systems:
- Vogel-04823.vogelcg - 192.168.10.123
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Firefox updates in background; relaunch may be needed to apply a downloaded update
- If still behind: check Firefox update settings / Maintenance Service
- ESR and release can both be present - update the channel that is installed
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip - Update Required
Vulnerability Remediation - 7-Zip - Update Required
Product/System: 7-Zip
Affected Systems Count: 1
Finding summary:
7-Zip is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.03 (or the latest available).
Affected Systems:
- Vogel-04823.vogelcg - 192.168.10.123 [12 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - vcenter - Update Required
Vulnerability Remediation - vcsa - Update Required
Product/System: linux-x64
Affected Systems Count: 1
Finding summary:
linux-x64 is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2024-38812
https://nvd.nist.gov/vuln/detail/CVE-2024-38812
Additional CVEs (7 more) are listed in the Client Folder report.
Minimum version to reach:
- vCenter Server 8.0 Update 3k (or the latest available).
Affected Systems:
- VOGEL-VCSA.vogelcg - 192.168.10.8 [8 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Ticket created by Chris Knospe.
Vulnerability Remediation - 7-Zip 26.02 (x64 edition) - Update Required
Vulnerability Remediation - 7-Zip 26.02 (x64 edition) - Update Required
Product/System: 7-Zip 26.02 (x64 edition)
Affected Systems Count: 2
Finding summary:
7-Zip 26.02 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.03 (or the latest available).
Affected Systems:
- VB-220 (JayMomberg) - 192.168.41.118
- VogelLaptop2025 (Rhona) - 192.168.68.58
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Cisco Webex Meetings - Update Required
Vulnerability Remediation - Cisco Webex Meetings - Update Required
Product/System: Cisco Webex Meetings
Affected Systems Count: 1
Finding summary:
Cisco Webex Meetings is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-20184
https://nvd.nist.gov/vuln/detail/CVE-2026-20184
Vendor security center:
https://sec.cloudapps.cisco.com/security/center/publicationListing.x
Additional CVEs (7 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 45.6.4.8 (or the latest available).
Affected Systems:
- Vogel-04894.vogelcg.local - 192.168.10.116 [8 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm which client is installed (Webex App vs Webex Meetings Desktop App) and its About version on each host
- Auto-updating client: verify first against the reported target; relaunch and allow in-app update to finish before forcing a redeploy
- If still behind: RMM/automated patching when deployed
- Backstage (CMD/PS): deploy matching Cisco MSI from client Webex site / Admin downloads
- Live user session only if needed: in-app Check for Updates
- Enterprise mass deploy: use the MSI for the same product family already installed (do not mix App + Meetings + Store packages casually)
- Verify About version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - TeamViewer - Update Required
Vulnerability Remediation - TeamViewer - Update Required
Product/System: TeamViewer
Affected Systems Count: 1
Finding summary:
TeamViewer is a third-party remote-access tool on the listed hosts.
Confirm the client uses it and that it is authorized. If it is, update via the vendor installer or in-app update. If the client does not use it or it is not authorized, uninstall it.
CVE references:
CVE-2026-19042
https://nvd.nist.gov/vuln/detail/CVE-2026-19042
Vendor security center:
https://www.teamviewer.com/en/resources/trust-center/security-bulletins/
Additional CVEs (5 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 15.81.6 (or the latest available).
Affected Systems:
- Vogel-04888.vogelcg (szur) - 192.168.10.127 [6 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Client uses it and it is authorized - update (default)
- Confirm the client uses this tool and that it is authorized first.
- Then update to the version listed under Minimum version to reach (or the latest available) via the vendor installer or in-app update.
B. Client does not use it / not authorized - uninstall
- Uninstall and remove startup/tasks/services/firewall rules. Document unexpected installs.
C. Authorized but cannot update - escalate to Security for suppression
- You confirmed the client uses it, it is authorized, and it is still behind after the vendor update path.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm the client uses TeamViewer and that it is authorized
- Check asset inventory, approved software list, and River Run / client deployment records
- If the client does not use it or it is NOT authorized: uninstall and remove startup/tasks/services/firewall rules
- Document unexpected installs as potential unauthorized remote access
- If authorized and the client uses it: update TeamViewer to the reported remediation target
- TeamViewer: host in-app update settings or vendor full installer for the reported target
- Verify version on affected hosts after update
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - MSTeams - Update Required
Vulnerability Remediation - MSTeams - Update Required
Product/System: MSTeams
Affected Systems Count: 3
Finding summary:
MSTeams is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-53783
https://nvd.nist.gov/vuln/detail/CVE-2025-53783
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26213.1006.5014.9784 (or the latest available).
Affected Systems:
- 192.168.10.126 [2 vulns]
- 192.168.10.111 [1 vulns]
- VB-444 - 192.168.44.137
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Vogel Consulting\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Victoria,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 12):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical).
• All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity.
• Executive Summary Report - a high-level overview of your security posture and network information.
• External Scan - detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Chris Knospe
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.