JEL Manufacturing, LLC Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-08-28 | Presenter: Chris Knospe | Export set: Top 12 | Client type: RMIT/CMIT
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Microsoft 365 Apps for business - en-us Remediation Options: Update to the current version; uninstall if not in use Target Machines: 192.168.35.41, JEL-SALES01.JELMFG, saleslaptop2.JELMFG 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 3.1.32 or later; uninstall if not in use Target Machines: JEL-App.JELMFG, JEL-LEGACY-SFT.JELMFG (erikacolorado), JEL-Main.JELMFG, MikeAlphinHome.JELMFG, JEL-App.JELMFG, MikeAlphinHome.JELMFG, JEL-Main.JELMFG, JEL-Main.JELMFG, JEL-LEGACY-SFT.JELMFG (erikacolorado), BurnTable.JELMFG (BurnTable) Estimated Time of Remediation: 1 hour Remediation Method: Deploy the matching runtime installer via RMM. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Google Chrome Remediation Options: Update to version 152.0.7977.64 or later; uninstall if not in use Target Machines: saleslaptop2.JELMFG, JoeyCain.JELMFG (joeycain), MikeAlphinHome.JELMFG, RogerGladen.JELMFG (RogerGladen), DrawingViewer1.JELMFG (Shop), DrawingViewer2.JELMFG (Shop), DrawingViewer3.JELMFG (Shop), DrawingViewer6.JELMFG (Shop), 192.168.35.41, DrawingViewer5.JELMFG (Shop), Engineering6.JELMFG, FreddieGarcia.JELMFG (FreddieGarcia), Jackie.JELMFG (JacquelynDufor), jasonjacobs25.JELMFG (jasonjacobs), JEL-App.JELMFG, JEL-Main.JELMFG, JEL-SALES01.JELMFG, KaylaJones.JELMFG, MattGladen.JELMFG (matthewgladen), MikeAlphin1.JELMFG (MichaelAlphin), Rogerlaptop26.JELMFG (RogerGladen) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat (64-bit) Remediation Options: Update to version 26.001.21789 or later; uninstall if not in use Target Machines: DrawingViewer1.JELMFG (Shop), DrawingViewer2.JELMFG (Shop), DrawingViewer3.JELMFG (Shop), DrawingViewer4.JELMFG (Shop), DrawingViewer5.JELMFG (Shop), DrawingViewer6.JELMFG (Shop), JEL-SALES01.JELMFG, Engineering6.JELMFG, JEL-LEGACY-SFT.JELMFG (erikacolorado), lucasholl.JELMFG, MikeAlphinHome.JELMFG Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Edge Remediation Options: Update to version 151.0.4129.107 or later; uninstall if not in use Target Machines: saleslaptop2.JELMFG, JoeyCain.JELMFG (joeycain), MikeAlphinHome.JELMFG, RogerGladen.JELMFG (RogerGladen) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Teams Remediation Options: Update to version 26198.304.4946.9672 or later; uninstall if not in use Target Machines: JEL-LAPTOP.JELMFG (holson), JEL-LEGACY-SFT.JELMFG (erikacolorado), MikeAlphinHome.JELMFG, saleslaptop2.JELMFG Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Mozilla Firefox Remediation Options: Update to version 154.0.1 or later; uninstall if not in use Target Machines: MikeAlphinHome.JELMFG, JEL-Main.JELMFG Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Java 8 Update 301 (64-bit) Remediation Options: Update to version 8.0.5030.1 or later; uninstall if not in use Target Machines: JEL-Main.JELMFG Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: VMware Tools Remediation Options: Update to version 13.1.0 or later; uninstall if not in use Target Machines: 192.168.35.41, JEL-SALES01.JELMFG, JEL-SOLIDWORKS.JELMFG, JEL-App.JELMFG, JEL-Main.JELMFG Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: vmnix-x86 Remediation Options: Update firmware to the current vendor release, or replace the device if it is out of support Target Machines: 192.168.35.7 Estimated Time of Remediation: 1 hour Remediation Method: Update firmware from the vendor during a maintenance window. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft SQL Server 2022 Setup (English) Remediation Options: Update to version 16.0.1190.2 or later; uninstall if not in use Target Machines: JEL-SOLIDWORKS.JELMFG Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: SonicWall NetExtender Remediation Options: Update to version 10.3.5 or later; uninstall if not in use Target Machines: JEL-Main.JELMFG Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 6.75 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 - 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 Matt to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
matt@jelmanufacturing.com
matt@jelmanufacturing.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Matt, 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 – 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 Matt, Following the quarterly vulnerability review for JEL Manufacturing, LLC, there are no remaining remediations to report. Sincerely, Chris Knospe
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Update Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Update Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 3
Finding summary:
Microsoft 365 Apps for business - 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-21509
https://nvd.nist.gov/vuln/detail/CVE-2026-21509
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21509
Additional CVEs (230 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5120249. Apply the latest patch.
Affected Systems:
- 192.168.35.41 [231 vulns]
- JEL-SALES01.JELMFG - 192.168.35.40 [181 vulns]
- saleslaptop2.JELMFG - 192.168.35.116 [88 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): ...\JEL Manufacturing, LLC\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: 10
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-23267
https://nvd.nist.gov/vuln/detail/CVE-2022-23267
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-23267
Additional CVEs (49 more) are listed in the Client Folder report.
Affected Systems:
- JEL-App.JELMFG - 192.168.35.6 [3.1.11] [96 vulns]
- JEL-LEGACY-SFT.JELMFG (erikacolorado) - 192.168.35.59 [8.0.28] [75 vulns]
- JEL-Main.JELMFG - 192.168.35.5 [8.0.28] [75 vulns]
- MikeAlphinHome.JELMFG - 192.168.1.128 [9.0.18] [33 vulns]
- JEL-App.JELMFG - 192.168.35.6 [30 vulns]
- MikeAlphinHome.JELMFG - 192.168.1.128 [8.0.29] [30 vulns]
- JEL-Main.JELMFG - 192.168.35.5 [18 vulns]
- JEL-Main.JELMFG - 192.168.35.5 [6.0.36] [6 vulns]
- JEL-LEGACY-SFT.JELMFG (erikacolorado) - 192.168.35.59 [6.0.36] [3 vulns]
- BurnTable.JELMFG (BurnTable) - 192.168.35.160 [1 vulns]
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
===== 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): ...\JEL Manufacturing, LLC\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-78935
https://nvd.nist.gov/vuln/detail/CVE-2026-78935
Vendor security center:
https://chromereleases.googleblog.com/
Additional CVEs (353 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 152.0.7977.64 (or the latest available)
- Update to version 151.0.4129.107 (or the latest available). Update to version 152.0.7977.64 (or the latest available).
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.
- saleslaptop2.JELMFG - 192.168.35.116 [354 vulns]
- JoeyCain.JELMFG (joeycain) - 192.168.35.70 [349 vulns]
- MikeAlphinHome.JELMFG - 192.168.1.128 [349 vulns]
- RogerGladen.JELMFG (RogerGladen) - 192.168.35.146 [349 vulns]
- DrawingViewer1.JELMFG (Shop) - 192.168.35.120 [302 vulns]
- DrawingViewer2.JELMFG (Shop) - 192.168.35.94 [302 vulns]
- DrawingViewer3.JELMFG (Shop) - 192.168.35.76 [302 vulns]
- DrawingViewer6.JELMFG (Shop) - 192.168.35.137 [302 vulns]
- 192.168.35.41 [295 vulns]
- DrawingViewer5.JELMFG (Shop) - 192.168.35.127 [295 vulns]
- Engineering6.JELMFG - 192.168.35.153 [295 vulns]
- FreddieGarcia.JELMFG (FreddieGarcia) - 192.168.35.151 [295 vulns]
- Jackie.JELMFG (JacquelynDufor) - 192.168.35.102 [295 vulns]
- jasonjacobs25.JELMFG (jasonjacobs) - 192.168.35.66 [295 vulns]
- JEL-App.JELMFG - 192.168.35.6 [295 vulns]
- JEL-Main.JELMFG - 192.168.35.5 [295 vulns]
- JEL-SALES01.JELMFG - 192.168.35.40 [295 vulns]
- KaylaJones.JELMFG - 192.168.35.108 [295 vulns]
- MattGladen.JELMFG (matthewgladen) - 192.168.35.123 [295 vulns]
- MikeAlphin1.JELMFG (MichaelAlphin) - 192.168.35.154 [295 vulns]
- Rogerlaptop26.JELMFG (RogerGladen) - 192.168.35.105 [295 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): ...\JEL Manufacturing, LLC\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: 11
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 (24 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.001.21789 (or the latest available)
- Update to version 10.1.20658.8883 (or the latest available). Update to version 26.001.21789 (or the latest available). Update to version 266.4.3911 (or the latest available)
- Update to version 10.1.20658.8883 (or the latest available). Update to version 26.001.21789 (or the latest available). Update to version 26.2.1 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- DrawingViewer1.JELMFG (Shop) - 192.168.35.120 [25 vulns]
- DrawingViewer2.JELMFG (Shop) - 192.168.35.94 [25 vulns]
- DrawingViewer3.JELMFG (Shop) - 192.168.35.76 [25 vulns]
- DrawingViewer4.JELMFG (Shop) - 192.168.35.124 [25 vulns]
- DrawingViewer5.JELMFG (Shop) - 192.168.35.127 [25 vulns]
- DrawingViewer6.JELMFG (Shop) - 192.168.35.137 [25 vulns]
- JEL-SALES01.JELMFG - 192.168.35.40 [22 vulns]
- Engineering6.JELMFG - 192.168.35.153 [1 vulns]
- JEL-LEGACY-SFT.JELMFG (erikacolorado) - 192.168.35.59 [1 vulns]
- lucasholl.JELMFG - 192.168.35.104 [1 vulns]
- MikeAlphinHome.JELMFG - 192.168.1.128 [1 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 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): ...\JEL Manufacturing, LLC\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: 4
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-76035
https://nvd.nist.gov/vuln/detail/CVE-2026-76035
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-76035
Additional CVEs (17 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 151.0.4129.107 (or the latest available). Update to version 152.0.7977.64 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- saleslaptop2.JELMFG - 192.168.35.116 [18 vulns]
- JoeyCain.JELMFG (joeycain) - 192.168.35.70 [12 vulns]
- MikeAlphinHome.JELMFG - 192.168.1.128 [12 vulns]
- RogerGladen.JELMFG (RogerGladen) - 192.168.35.146 [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)
- 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): ...\JEL Manufacturing, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 4
Finding summary:
Microsoft Teams 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-2023-4863
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26198.304.4946.9672 (or the latest available).
Affected Systems:
- JEL-LAPTOP.JELMFG (holson) - 192.168.1.20 [7 vulns]
- JEL-LEGACY-SFT.JELMFG (erikacolorado) - 192.168.35.59 [7 vulns]
- MikeAlphinHome.JELMFG - 192.168.1.128 [7 vulns]
- saleslaptop2.JELMFG - 192.168.35.116 [7 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 flagged Teams version - Classic is not always the source
- Classic Teams is sometimes a per-user install
- A user who has not logged into this workstation in a while, or is not the primary user, can still have Classic leftover
- Run the RMM Teams Classic cleanup script for those leftover per-user installs
- Classic/duplicate suspected: R-Security - Teams Classic Cleanup Remediation (Scripts > RR Custom > RR Custom - R-Security Remediation > R-Security - Teams Classic Cleanup Remediation)
- Current Teams behind: automated patching/RMM first
- Live user session only if needed: three-dot menu > Settings > About Teams
- Backstage (CMD/PS): RMM script / installer only - not the Teams 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): ...\JEL Manufacturing, LLC\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: 2
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-74943
https://nvd.nist.gov/vuln/detail/CVE-2026-74943
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (59 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 154.0.1 (or the latest available).
Affected Systems:
- MikeAlphinHome.JELMFG - 192.168.1.128 [60 vulns]
- JEL-Main.JELMFG - 192.168.35.5 [2 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)
- 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): ...\JEL Manufacturing, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Java 8 Update 301 (64-bit) - Update Required
Vulnerability Remediation - Java 8 Update 301 (64-bit) - Update Required
Product/System: Java 8 Update 301 (64-bit)
Affected Systems Count: 1
Finding summary:
Java 8 Update 301 (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-34169
https://nvd.nist.gov/vuln/detail/CVE-2022-34169
Vendor security center:
https://www.oracle.com/security-alerts/
Additional CVEs (34 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 8.0.5030.1 (or the latest available).
Affected Systems:
- JEL-Main.JELMFG - 192.168.35.5 [35 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 Java runtime is installed (vendor + major version, e.g. Oracle 8 / Temurin 11) on each host
- Inventory apps that require that major version before changing anything
- Primary: update within the same major version line to the Minimum version to reach target (or latest security update for that line)
- Oracle Java: Oracle installer / Java Update / enterprise package per client license
- OpenJDK / Temurin-style: Adoptium Temurin or the distro already in use (do not switch vendors without app vendor approval)
- Prefer RMM/automated patching when deployed; else vendor MSI via ScreenConnect
- If unused after dependency check: uninstall that runtime
- Verify java -version / Programs and Features and dependent app startup after change
- Java 8: stay on the existing 8u line unless the app vendor requires a newer major
===== 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): ...\JEL Manufacturing, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - VMware Tools - Update Required
Vulnerability Remediation - VMware Tools - Update Required
Product/System: VMware Tools
Affected Systems Count: 5
Finding summary:
VMware Tools 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-2021-21999
https://nvd.nist.gov/vuln/detail/CVE-2021-21999
Vendor security center:
https://www.broadcom.com/support/vmware-security-advisories
Additional CVEs (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 13.1.0 (or the latest available).
Affected Systems:
- 192.168.35.41 [11 vulns]
- JEL-SALES01.JELMFG - 192.168.35.40 [11 vulns]
- JEL-SOLIDWORKS.JELMFG - 192.168.35.56 [11 vulns]
- JEL-App.JELMFG - 192.168.35.6 [2 vulns]
- JEL-Main.JELMFG - 192.168.35.5 [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) =====
- WARNING: VMware Tools updates require a guest VM reboot. Plan for after hours or approved maintenance window
- Updating VMware Tools triggers automatic reboot of the guest VM - do not run during business hours
- Schedule updates for after hours or approved maintenance window
- Coordinate with client or application owner before applying
- Update via RMM script (ConnectWise Automate) or vSphere Update Manager
- Verify VM compatibility with ESXi host version before patching
===== 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): ...\JEL Manufacturing, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - vmnix-x86 - Firmware Update Required
Vulnerability Remediation - vmnix-x86 - Firmware Update Required
Product/System: vmnix-x86
Affected Systems Count: 1
Finding summary:
vmnix-x86 firmware/software may be outdated on the listed device(s).
Confirm the real vendor, model, and firmware build on the device first.
Check the vendor security advisory for this CVE and model.
If the vendor documents not affected or already fixed: escalate to Security as a false positive with details and the vendor documentation link.
Otherwise apply manufacturer firmware via the vendor tool or device admin.
Coordinate an outage/reboot window.
CVE references:
CVE-2024-22252
https://nvd.nist.gov/vuln/detail/CVE-2024-22252
Vendor security center:
https://www.broadcom.com/support/vmware-security-advisories
Additional CVEs (17 more) are listed in the Client Folder report.
Minimum version to reach:
- VMware ESXi 8.0k (or the latest available).
Affected Systems:
- 192.168.35.7 [18 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 device first.
Then stop (escalate to Security as a false positive) if:
- the device is not present
- already at/above the minimum version to reach
- the finding does not match the installed model/firmware
- the vendor documents this CVE as not applicable or already fixed
Include details and the vendor documentation link.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply firmware / device software (default when keeping the device)
- Apply manufacturer firmware to the version listed under Minimum version to reach (or the latest available for that model).
- If the product line is EOL, still check for and apply the latest available final firmware for that model before anything else.
B. Device not needed - retire / replace / remove from service
- Only if the device should not remain on the network.
C. EOL / no secure path - notify the client, then escalate to Security for suppression
- After confirming the device is on the latest available firmware for that model (or no further update exists), notify the client of residual risk, record discussion notes to the client, then escalate to Security for suppression.
- Document model, current firmware, and that latest-available was checked.
- Do not request suppression until latest-available was checked and the client was notified.
- 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:
Agree an outage window with the client before applying firmware - the device reboots.
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) =====
- If a support contract has lapsed, do not apply a software or firmware update.
- Notify the client that updates cannot proceed until support is renewed or a replacement is approved
- Create a Sales quote for support renewal, or for replacement/upgrade if the product is also EOL
- Open a vendor case after entitlement is in place (or to confirm support status)
- Broadcom / VMware support check:
- Do not apply ESXi, vSphere, vCenter, or vmnix (ESXi VMkernel) patches without Broadcom support entitlement
- If support is expired: notify the client, create a Sales quote for Broadcom support renewal (or replacement/upgrade if the product is also EOL), then open a Broadcom case after entitlement is in place
- If another vendor manages this host: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression
- vmnix is the ESXi VMkernel scan name - VMware / vSphere host, not a Linux or Windows package
- Same Broadcom support requirement as ESXi / vSphere
- Download patches from Broadcom Support Portal
- Apply via vSphere Lifecycle Manager (recommended) or manual offline bundle/ISO
- Host reboot required; migrate or shut down VMs before patching
===== 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): ...\JEL Manufacturing, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2022 Setup (English) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2022 Setup (English) - Update Required
Product/System: Microsoft SQL Server 2022 Setup (English)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2022 Setup (English) is a database engine on the listed hosts.
Confirm the instance or cluster, then apply the matching engine update in a maintenance window with the DBA or app owner.
CVE references:
CVE-2026-54118
https://nvd.nist.gov/vuln/detail/CVE-2026-54118
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54118
Additional CVEs (9 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 16.0.1190.2 (or the latest available).
Affected Systems:
- JEL-SOLIDWORKS.JELMFG - 192.168.35.56 [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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\JEL Manufacturing, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - SonicWall NetExtender - Update Required
Vulnerability Remediation - SonicWall NetExtender - Update Required
Product/System: SonicWall NetExtender
Affected Systems Count: 1
Finding summary:
SonicWall NetExtender is a VPN client on the listed hosts.
If the site has a SonicWall firewall, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it.
CVE references:
CVE-2024-29014
https://nvd.nist.gov/vuln/detail/CVE-2024-29014
Vendor security center:
https://psirt.global.sonicwall.com/
Additional CVEs (8 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.3.5 (or the latest available).
Affected Systems:
- JEL-Main.JELMFG - 192.168.35.5 [9 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. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has a SonicWall firewall: update to the version listed under Minimum version to reach (or the latest available) via RMM or the vendor installer.
- If the site does not have a SonicWall firewall: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the 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) =====
- NetExtender is an endpoint VPN client - not SonicWall / SonicOS firmware
This VPN is expected if the site has a SonicWall firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it.
- Update via RMM or the vendor installer on the Windows host
- Verify the client version after install
===== END TECHNICAL GUIDANCE =====
Tasks:
- **Uninstall - this is not in use <-- they have a Fortigate***
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\JEL Manufacturing, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Matt,
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 – 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.