Gauthier Biomedical 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: 10 in export (Top 10) | Client type: RMIT/CMIT
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Google Chrome Remediation Options: Update to version 153.0.8010.37 or later; uninstall if not in use Target Machines: cbrown-wx.gbi, 192.168.2.166 (RBlock), SGAUTHIER-HP-WX.gbi.local (SGauthier), GAnzia-NB-WX.gbi.local (GAnzia), 192.168.2.119 (RBlock), 192.168.2.153 (RBlock), 192.168.2.154 (RBlock), 192.168.2.159 (RBlock), 192.168.2.212 (RBlock), 192.168.2.78 (RBlock), ABRAGANZA-WX-25.gbi (ABraganza), MRICHTER-WX.gbi (MRichter), VLINZMEYER-WX.gbi (vgilhams), 192.168.2.183 (RBlock), ENG-SWDEV-WX.gbi (clewandowski), HP-WKS26-2.gbi (vgilhams), MSCHWARTZ-WX23 (MSchwartz), RBLOCK-WX.gbi (RBlock), SHOP-DELL3-WX.gbi (pvd) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft .NET (all versions) Remediation Options: Update to version 8.0.29 or later; uninstall if not in use Target Machines: 192.168.2.153 (RBlock), 192.168.2.153 (RBlock), 192.168.2.195 (RBlock), 192.168.2.212 (RBlock), DWALLAC-WX-1124.gbi (dwallace), ENG-SW-WX.gbi (TWollner), SHIPPING-WX.gbi (Shipping), 192.168.2.153 (RBlock), 192.168.2.153 (RBlock), SHOP-DELL3-WX.gbi (pvd), MRICHTER-WX.gbi (MRichter), SHOP-DELL3-WX.gbi (pvd) Estimated Time of Remediation: 2 hours Remediation Method: Deploy the matching runtime installer via RMM. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinVerifyTrust Signature Validation Vulnerability Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: 192.168.2.110 (BVoskuil), 192.168.2.113 (RBlock), SGAUTHIER-HP-WX.gbi.local (SGauthier), 192.168.2.119 (RBlock), 192.168.2.141 (RBlock), GAnzia-NB-WX.gbi.local (GAnzia), 192.168.2.145 (RBlock), HP-WKS26-1.gbi.local (BBond), 192.168.2.149 (RBlock), DWALLAC-WX-1124.gbi.local (dwallace), 192.168.2.153 (RBlock), 192.168.2.154 (RBlock), 192.168.2.159 (RBlock), 192.168.2.166 (RBlock), 192.168.2.168 (MGauthier), 192.168.2.177 (RBlock), 192.168.2.179 (RBlock), 192.168.2.183 (RBlock), 192.168.2.184 (RBlock), 192.168.2.190 (RBlock), 192.168.2.195 (RBlock), 192.168.2.199 (RBlock), 192.168.2.212 (RBlock), 192.168.2.243 (RBlock), 192.168.2.32 (RBlock), 192.168.2.33 (RBlock), 192.168.2.42 (RBlock), 192.168.2.75 (RBlock), 192.168.2.77 (RBlock), 192.168.2.78 (RBlock), ABRAGANZA-WX-25.gbi (ABraganza), accountant-wx.gbi, BPEIFFER-0924.gbi (BPeiffer), BRIANMILLER-WX.gbi (BrianMiller), CBROWN-WX-1024.gbi (CBrown), CKUEHL-1224.gbi, DWALLAC-WX-1124.gbi (dwallace), ENGCONF-WX.gbi, ENG-SWDEV-WX.gbi (clewandowski), ENG-SW-WX.gbi (TWollner), GAnzia-NB-WX.gbi (GAnzia), GB-AD-01.gbi (riverrun), GB-AD-02.gbi (riverrun), GB-AD1.gbi, GB-FS-01.gbi, GB-FS-02.gbi (riverrun), GB-HyperV-01 (Administrator), HP-WKS26-1.gbi (BBond), HP-WKS26-2.gbi (vgilhams), HP-WKS26-3.gbi (SGauthier), HP-WKS26-4.gbi (thorn), INSLAB2-WX.gbi (gshop), JEDWARDS-WX.gbi (jedwards), JPEIFFER-WX.gbi (JPeiffer), LBECKER-WX.gbi (LBecker), MOLDING-NB-WX.gbi (PSeifert), MOLDING-NUC-W7.gbi (Assembly), MRICHTER-WX.gbi (MRichter), NVANESS-WX.gbi (NVanEss), PROG-NE-0624.gbi (JTernes), PSeifert-WX.gbi, QUALITY-NUC-W7.gbi (gshop), RBAST-WX.gbi, RBLOCK-WX.gbi (RBlock), RWOLLNER-26.gbi (RWollner), SALES-NB-WX.gbi (MNikolic), SGAUTHIER-HP-WX.gbi (SGauthier), SHIPPING-WX.gbi (Shipping), SHOP-DELL3-WX.gbi (pvd), SWINDISCH-WX.gbi, TRAINCONF-WX.gbi, VLINZMEYER-WX.gbi (vgilhams) Estimated Time of Remediation: 2 hours Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Edge Remediation Options: Update to version 152.0.4191.66 or later; uninstall if not in use Target Machines: cbrown-wx.gbi, 192.168.2.141 (RBlock), 192.168.2.166 (RBlock), SGAUTHIER-HP-WX.gbi.local (SGauthier), GAnzia-NB-WX.gbi.local (GAnzia) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Foxit PhantomPDF Remediation Options: Update to version 14.0.5.33580 or later; uninstall if not in use Target Machines: 192.168.2.177 (RBlock) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Visual Studio Code Remediation Options: Update to version 1.136.1 or later; uninstall if not in use Target Machines: SGAUTHIER-HP-WX.gbi.local (SGauthier), 192.168.2.141 (RBlock), GAnzia-NB-WX.gbi.local (GAnzia), 192.168.2.145 (RBlock), 192.168.2.153 (RBlock), 192.168.2.195 (RBlock) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.10.11 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: 192.168.2.153 (RBlock), ENG-SWDEV-WX.gbi (clewandowski) Estimated Time of Remediation: 0.5 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.10.5 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: 192.168.2.195 (RBlock) Estimated Time of Remediation: 0.5 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.10.7 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: PSeifert-WX.gbi Estimated Time of Remediation: 0.5 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: GPL Ghostscript Remediation Options: Update to version 10.07.0 or later; uninstall if not in use Target Machines: 192.168.2.153 (RBlock) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 8.5 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 Ten vulnerabilities docx report - 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 Michael to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
michael.gauthier@gauthierbiomedical.com
michael.gauthier@gauthierbiomedical.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Michael, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top Ten): Open Top Ten 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 – a comprehensive list of all detected vulnerabilities (internal and external), 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: No remediation will begin without your approval. 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 Michael, Following the quarterly vulnerability review for Gauthier Biomedical, there are no remaining remediations to report. Sincerely, Chris Knospe
Vulnerability Remediation - Google Chrome - Update Required
Vulnerability Remediation - Google Chrome - Update Required
Product/System: Google Chrome
Affected Systems Count: 19
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-87438
https://nvd.nist.gov/vuln/detail/CVE-2026-87438
Vendor security center:
https://chromereleases.googleblog.com/
Additional CVEs (232 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 16.0.4849.1000 (or the latest available). Update to version 6.0.9780.1 (or the latest available)
- Update to version 153.0.8010.37 (or the latest available). Update to version 15.81.6 (or the latest available). Update to version 6.0.9780.1 (or the latest available). Update to version 7.1.2.31 (or the latest available)
- Update to version 153.0.8010.37 (or the latest available). Update to version 6.0.9780.1 (or the latest available)
- Update to version 1.2.99.317 (or the latest available). Update to version 153.0.8010.37 (or the latest available). Update to version 6.0.9780.1 (or the latest available). Update to version 7.1.0 (or the latest available)
- (1 additional unique targets omitted - see affected systems above and ConnectSecure scan exports in the client quarterly folder).
Affected Systems:
- cbrown-wx.gbi - 192.168.2.222 [232 vulns]
- 192.168.2.166 (RBlock) - 192.168.2.166 [224 vulns]
- SGAUTHIER-HP-WX.gbi.local (SGauthier) - 192.168.2.117 [141 vulns]
- GAnzia-NB-WX.gbi.local (GAnzia) - 192.168.2.144 [141 vulns]
- 192.168.2.119 (RBlock) - 192.168.2.119 [57 vulns]
- 192.168.2.153 (RBlock) - 192.168.2.153 [57 vulns]
- 192.168.2.154 (RBlock) - 192.168.2.154 [57 vulns]
- 192.168.2.159 (RBlock) - 192.168.2.159 [57 vulns]
- 192.168.2.212 (RBlock) - 192.168.2.212 [57 vulns]
- 192.168.2.78 (RBlock) - 192.168.2.78 [57 vulns]
- ABRAGANZA-WX-25.gbi (ABraganza) - 192.168.2.160 [57 vulns]
- MRICHTER-WX.gbi (MRichter) - 192.168.2.226 [57 vulns]
- VLINZMEYER-WX.gbi (vgilhams) - 192.168.2.156 [57 vulns]
- 192.168.2.183 (RBlock) - 192.168.2.183 [56 vulns]
- ENG-SWDEV-WX.gbi (clewandowski) - 192.168.2.218 [56 vulns]
- HP-WKS26-2.gbi (vgilhams) - 192.168.2.187 [56 vulns]
- MSCHWARTZ-WX23 (MSchwartz) - 192.168.2.146 [56 vulns]
- RBLOCK-WX.gbi (RBlock) - 192.168.2.140 [56 vulns]
- SHOP-DELL3-WX.gbi (pvd) - 192.168.2.74 [56 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) =====
- 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
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: 12
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-2025-55315
https://nvd.nist.gov/vuln/detail/CVE-2025-55315
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-55315
Affected Systems:
- 192.168.2.153 (RBlock) - 192.168.2.153 [13 vulns]
- 192.168.2.153 (RBlock) - 192.168.2.153 [6.0.36] [6 vulns]
- 192.168.2.195 (RBlock) - 192.168.2.195 [6.0.36] [6 vulns]
- 192.168.2.212 (RBlock) - 192.168.2.212 [6.0.36] [6 vulns]
- DWALLAC-WX-1124.gbi (dwallace) - 192.168.2.150 [6.0.36] [6 vulns]
- ENG-SW-WX.gbi (TWollner) - 192.168.2.163 [6.0.36] [6 vulns]
- SHIPPING-WX.gbi (Shipping) - 192.168.2.224 [6.0.36] [6 vulns]
- 192.168.2.153 (RBlock) - 192.168.2.153 [7.0.20] [6 vulns]
- 192.168.2.153 (RBlock) - 192.168.2.153 [8.0.14] [5 vulns]
- SHOP-DELL3-WX.gbi (pvd) - 192.168.2.74 [6.0.36] [3 vulns]
- MRICHTER-WX.gbi (MRichter) - 192.168.2.226 [6.0.36] [3 vulns]
- SHOP-DELL3-WX.gbi (pvd) - 192.168.2.74 [5.0.17] [3 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 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 5: 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 7: out of support since May 14, 2024 - 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)
===== 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Product/System: WinVerifyTrust Signature Validation Vulnerability
Affected Systems Count: 72
Finding summary:
WinVerifyTrust Signature Validation Vulnerability is a configuration / hardening finding.
Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2013-3900
https://nvd.nist.gov/vuln/detail/CVE-2013-3900
Affected Systems:
Sorry for the long host list below (72 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- 192.168.2.110 (BVoskuil) - 192.168.2.110 [1 vulns]
- 192.168.2.113 (RBlock) - 192.168.2.113 [1 vulns]
- SGAUTHIER-HP-WX.gbi.local (SGauthier) - 192.168.2.117 [1 vulns]
- 192.168.2.119 (RBlock) - 192.168.2.119 [1 vulns]
- 192.168.2.141 (RBlock) - 192.168.2.141 [1 vulns]
- GAnzia-NB-WX.gbi.local (GAnzia) - 192.168.2.144 [1 vulns]
- 192.168.2.145 (RBlock) - 192.168.2.145 [1 vulns]
- HP-WKS26-1.gbi.local (BBond) - 192.168.2.147 [1 vulns]
- 192.168.2.149 (RBlock) - 192.168.2.149 [1 vulns]
- DWALLAC-WX-1124.gbi.local (dwallace) - 192.168.2.150 [1 vulns]
- 192.168.2.153 (RBlock) - 192.168.2.153 [1 vulns]
- 192.168.2.154 (RBlock) - 192.168.2.154 [1 vulns]
- 192.168.2.159 (RBlock) - 192.168.2.159 [1 vulns]
- 192.168.2.166 (RBlock) - 192.168.2.166 [1 vulns]
- 192.168.2.168 (MGauthier) - 192.168.2.168 [1 vulns]
- 192.168.2.177 (RBlock) - 192.168.2.177 [1 vulns]
- 192.168.2.179 (RBlock) - 192.168.2.179 [1 vulns]
- 192.168.2.183 (RBlock) - 192.168.2.183 [1 vulns]
- 192.168.2.184 (RBlock) - 192.168.2.184 [1 vulns]
- 192.168.2.190 (RBlock) - 192.168.2.190 [1 vulns]
- 192.168.2.195 (RBlock) - 192.168.2.195 [1 vulns]
- 192.168.2.199 (RBlock) - 192.168.2.199 [1 vulns]
- 192.168.2.212 (RBlock) - 192.168.2.212 [1 vulns]
- 192.168.2.243 (RBlock) - 192.168.2.243 [1 vulns]
- 192.168.2.32 (RBlock) - 192.168.2.32 [1 vulns]
- 192.168.2.33 (RBlock) - 192.168.2.33 [1 vulns]
- 192.168.2.42 (RBlock) - 192.168.2.42 [1 vulns]
- 192.168.2.75 (RBlock) - 192.168.2.75 [1 vulns]
- 192.168.2.77 (RBlock) - 192.168.2.77 [1 vulns]
- 192.168.2.78 (RBlock) - 192.168.2.78 [1 vulns]
- ABRAGANZA-WX-25.gbi (ABraganza) - 192.168.2.160 [1 vulns]
- accountant-wx.gbi - 192.168.2.191 [1 vulns]
- BPEIFFER-0924.gbi (BPeiffer) - 192.168.2.169 [1 vulns]
- BRIANMILLER-WX.gbi (BrianMiller) - 192.168.2.192 [1 vulns]
- CBROWN-WX-1024.gbi (CBrown) - 192.168.2.114 [1 vulns]
- CKUEHL-1224.gbi - 192.168.2.185 [1 vulns]
- DWALLAC-WX-1124.gbi (dwallace) - 192.168.2.150 [1 vulns]
- ENGCONF-WX.gbi - 192.168.2.173 [1 vulns]
- ENG-SWDEV-WX.gbi (clewandowski) - 192.168.2.218 [1 vulns]
- ENG-SW-WX.gbi (TWollner) - 192.168.2.163 [1 vulns]
- GAnzia-NB-WX.gbi (GAnzia) - 192.168.2.144 [1 vulns]
- GB-AD-01.gbi (riverrun) - 192.168.2.36 [1 vulns]
- GB-AD-02.gbi (riverrun) - 192.168.2.35 [1 vulns]
- GB-AD1.gbi - 192.168.2.31 [1 vulns]
- GB-FS-01.gbi - 192.168.2.34 [1 vulns]
- GB-FS-02.gbi (riverrun) - 192.168.2.38 [1 vulns]
- GB-HyperV-01 (Administrator) - 192.168.2.5 [1 vulns]
- HP-WKS26-1.gbi (BBond) - 192.168.2.147 [1 vulns]
- HP-WKS26-2.gbi (vgilhams) - 192.168.2.187 [1 vulns]
- HP-WKS26-3.gbi (SGauthier) - 192.168.2.121 [1 vulns]
- HP-WKS26-4.gbi (thorn) - 192.168.2.172 [1 vulns]
- INSLAB2-WX.gbi (gshop) - 192.168.2.237 [1 vulns]
- JEDWARDS-WX.gbi (jedwards) - 192.168.2.174 [1 vulns]
- JPEIFFER-WX.gbi (JPeiffer) - 192.168.2.217 [1 vulns]
- LBECKER-WX.gbi (LBecker) - 192.168.2.210 [1 vulns]
- MOLDING-NB-WX.gbi (PSeifert) - 192.168.2.198 [1 vulns]
- MOLDING-NUC-W7.gbi (Assembly) - 192.168.2.236 [1 vulns]
- MRICHTER-WX.gbi (MRichter) - 192.168.2.226 [1 vulns]
- NVANESS-WX.gbi (NVanEss) - 192.168.2.167 [1 vulns]
- PROG-NE-0624.gbi (JTernes) - 192.168.2.111 [1 vulns]
- PSeifert-WX.gbi - 192.168.2.178 [1 vulns]
- QUALITY-NUC-W7.gbi (gshop) - 192.168.2.118 [1 vulns]
- RBAST-WX.gbi - 192.168.2.235 [1 vulns]
- RBLOCK-WX.gbi (RBlock) - 192.168.2.140 [1 vulns]
- RWOLLNER-26.gbi (RWollner) - 192.168.2.72 [1 vulns]
- SALES-NB-WX.gbi (MNikolic) - 192.168.2.161 [1 vulns]
- SGAUTHIER-HP-WX.gbi (SGauthier) - 192.168.2.117 [1 vulns]
- SHIPPING-WX.gbi (Shipping) - 192.168.2.224 [1 vulns]
- SHOP-DELL3-WX.gbi (pvd) - 192.168.2.74 [1 vulns]
- SWINDISCH-WX.gbi - 192.168.2.204 [1 vulns]
- TRAINCONF-WX.gbi - 192.168.2.164 [1 vulns]
- VLINZMEYER-WX.gbi (vgilhams) - 192.168.2.156 [1 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/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
Include details.
Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- 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 CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture:
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 make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- WinVerifyTrust / CVE-2013-3900 is Authenticode hardening - not a software install or Windows Update
- Set EnableCertPaddingCheck=1 under HKLM\Software\Microsoft\Cryptography\Wintrust\Config
- On 64-bit hosts also set the Wow6432Node\...\Wintrust\Config copy
- Prefer domain GPO (or Intune) over one-off registry edits
- Verify signed installers and vendor tools still launch after the change
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
===== 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Edge - Update Required
Vulnerability Remediation - Microsoft Edge - Update Required
Product/System: Microsoft Edge
Affected Systems Count: 5
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-78985
https://nvd.nist.gov/vuln/detail/CVE-2026-78985
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-78985
Additional CVEs (161 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:
- cbrown-wx.gbi - 192.168.2.222 [162 vulns]
- 192.168.2.141 (RBlock) - 192.168.2.141 [154 vulns]
- 192.168.2.166 (RBlock) - 192.168.2.166 [83 vulns]
- SGAUTHIER-HP-WX.gbi.local (SGauthier) - 192.168.2.117 [71 vulns]
- GAnzia-NB-WX.gbi.local (GAnzia) - 192.168.2.144 [71 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Foxit PhantomPDF - Update Required
Vulnerability Remediation - Foxit PhantomPDF - Update Required
Product/System: Foxit PhantomPDF
Affected Systems Count: 1
Finding summary:
Foxit PhantomPDF 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-2020-13804
https://nvd.nist.gov/vuln/detail/CVE-2020-13804
Vendor security center:
https://www.foxit.com/support/security-bulletins.html
Additional CVEs (24 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 14.0.5.33580 (or the latest available).
Affected Systems:
- 192.168.2.177 (RBlock) - 192.168.2.177 [25 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) =====
- Confirm Foxit PDF Reader vs Foxit PDF Editor on each host
- Update via RMM or the matching Foxit installer
- Do not use Adobe Reader winget IDs for Foxit
- Verify Help > About 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Visual Studio Code - Update Required
Vulnerability Remediation - Microsoft Visual Studio Code - Update Required
Product/System: Microsoft Visual Studio Code
Affected Systems Count: 6
Finding summary:
Microsoft Visual Studio Code 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-47281
https://nvd.nist.gov/vuln/detail/CVE-2026-47281
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47281
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.136.1 (or the latest available).
Affected Systems:
- SGAUTHIER-HP-WX.gbi.local (SGauthier) - 192.168.2.117 [2 vulns]
- 192.168.2.141 (RBlock) - 192.168.2.141 [2 vulns]
- GAnzia-NB-WX.gbi.local (GAnzia) - 192.168.2.144 [2 vulns]
- 192.168.2.145 (RBlock) - 192.168.2.145 [2 vulns]
- 192.168.2.153 (RBlock) - 192.168.2.153 [2 vulns]
- 192.168.2.195 (RBlock) - 192.168.2.195 [2 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) =====
- 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.10.11 (64-bit) - Update Required
Vulnerability Remediation - Python 3.10.11 (64-bit) - Update Required
Product/System: Python 3.10.11 (64-bit)
Affected Systems Count: 2
Finding summary:
Python 3.10.11 (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-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (8 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- 192.168.2.153 (RBlock) - 192.168.2.153 [9 vulns]
- ENG-SWDEV-WX.gbi (clewandowski) - 192.168.2.218 [9 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) =====
- Confirm which Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.10.5 Executables (64-bit) - Update Required
Vulnerability Remediation - Python 3.10.5 Executables (64-bit) - Update Required
Product/System: Python 3.10.5 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.5 Executables (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-2022-37454
https://nvd.nist.gov/vuln/detail/CVE-2022-37454
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (9 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- 192.168.2.195 (RBlock) - 192.168.2.195 [10 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) =====
- Confirm which Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.10.7 (64-bit) - Update Required
Vulnerability Remediation - Python 3.10.7 (64-bit) - Update Required
Product/System: Python 3.10.7 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.7 (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-2022-37454
https://nvd.nist.gov/vuln/detail/CVE-2022-37454
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (9 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- PSeifert-WX.gbi - 192.168.2.178 [10 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 Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - GPL Ghostscript - Update Required
Vulnerability Remediation - GPL Ghostscript - Update Required
Product/System: GPL Ghostscript
Affected Systems Count: 1
Finding summary:
GPL Ghostscript 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-27831
https://nvd.nist.gov/vuln/detail/CVE-2025-27831
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.07.0 (or the latest available).
Affected Systems:
- 192.168.2.153 (RBlock) - 192.168.2.153 [5 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) =====
- 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): ...\Gauthier Biomedical\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Michael,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top Ten):
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 – a comprehensive list of all detected vulnerabilities (internal and external), 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: No remediation will begin without your approval. 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.