North Central HIDTA 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 11 | Client type: RMIT/CMIT
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2025 Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: HIDTA-HV-02 (Administrator) Estimated Time of Remediation: 0.5 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2022 Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: MKEMCFS01.milwaukeehidta Estimated Time of Remediation: 1 hour Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Apache Remediation Options: Update to the current version; uninstall if not in use Target Machines: 192.168.95.100, 192.168.95.12, 192.168.95.13, 192.168.95.14, 192.168.95.15, 192.168.95.16, 192.168.95.17, 192.168.95.18, 192.168.95.19, 192.168.99.12, 192.168.99.15, 192.168.99.17, 192.168.99.18, 192.168.99.19, 192.168.99.23, 192.168.99.24, 192.168.99.25, 192.168.99.31, 192.168.99.32, 192.168.99.33, 192.168.99.34, 192.168.99.35, 192.168.99.36, 192.168.99.37 Estimated Time of Remediation: 2 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: HIDTA-VEEAM, HIDTA-PLX-01, HIDTA-VEEAM, ISC-UFED24-01 (UFEDTech), HIDTA-PLX-01, ISC-UFED24-01 (UFEDTech), HIDTA-PLX-01, ISC-UFED24-01 (UFEDTech), ISC-UFED24-01 (UFEDTech), HIDTA-PLX-01, ISC-PESK24 Estimated Time of Remediation: 0 hours 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: DESKTOP-ETR055N (RandallKwasinski), ISC-SCHI26, A-ALBR25 (ScottAlbrecht), DESKTOP-PRBQORG (Enforcement), isc-chin25 (ElijahAChinavare), ISC-KULI25 (JulieAKuligowski), ISC-INTERN25-B (NatalieGuelzow), A-SANF26 (JimSanfilippo), A-SHOG25 (RyanShogren), DESKTOP-25MRHLB, DESKTOP-NBSNV3N (Cellhawk1), ISC-FISC24 (AlexanderJFischer), ISC-GUEL25, ISC-HAIG25 (EzraJHaight), ISC-HANS25 (CatherineHansen), ISC-HENG25 (GarrettHeng), ISC-LESA25L (SheaLaSage), ISC-MAHM25 (YousifMahmoud), ISC-NESP25 (ErikNespoli), ISC-PESK24, ISC-RUTT25 (FredRutter), ISC-SAYP25 (CelineCSaypanya), ISC-SKEL25 (BrennaSkelton), ISC-UFED24-01 (UFEDTech), ISC-UNGE25 (BrantUngerer) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft 365 Apps for enterprise - en-us Remediation Options: Update to the current version; uninstall if not in use Target Machines: ISC-PESK24 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: ISC-MAHM25 (YousifMahmoud), HuskyX8.milwaukeehidta 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: HuskyX8.milwaukeehidta, ISC-NESP25 (ErikNespoli), ISC-PESK24 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: ISC-HANS25 (CatherineHansen), ISC-LESA25L (SheaLaSage), ISC-MAHM25 (YousifMahmoud), ISC-WEBS25 (MichaelWebster), ISC-PESK24 Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 23.01 (x64 edition) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: ISC-PESK24 Estimated Time of Remediation: 0.25 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: VMware Tools Remediation Options: Update to version 13.1.0 or later; uninstall if not in use Target Machines: MKEAXIS-01.milwaukeehidta, MKEMCFS01.milwaukeehidta Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 7.25 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 11 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 Ryan to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
rshogren@northcentralhidta.org
mwebster@northcentralhidta.org; salbrecht@northcentralhidta.org
rshogren@northcentralhidta.org; mwebster@northcentralhidta.org; salbrecht@northcentralhidta.org
2026 Q4 Vulnerability Scan Follow Up
Good evening Ryan, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 11): Open Top 11 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 Ryan, Following the quarterly vulnerability review for North Central HIDTA, there are no remaining remediations to report. Sincerely, Chris Knospe
mwebster@northcentralhidta.org
salbrecht@northcentralhidta.org
Vulnerability Remediation - Windows Server 2025 - Updates Required
Vulnerability Remediation - Windows Server 2025 - Updates Required
Product/System: Windows Server 2025
Affected Systems Count: 1
Finding summary:
Windows Server 2025 is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-41089
https://nvd.nist.gov/vuln/detail/CVE-2026-41089
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-41089
Additional CVEs (950 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120233 (or the latest available).
Affected Systems:
- HIDTA-HV-02 (Administrator) - 10.100.177.7 [10.0.26100]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- 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 a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, 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) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
===== 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): ...\North Central HIDTA\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows Server 2022 - Updates Required
Vulnerability Remediation - Windows Server 2022 - Updates Required
Product/System: Windows Server 2022
Affected Systems Count: 1
Finding summary:
Windows Server 2022 is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2025-21298
https://nvd.nist.gov/vuln/detail/CVE-2025-21298
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298
Additional CVEs (1704 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120242 (or the latest available).
Affected Systems:
- MKEMCFS01.milwaukeehidta - 192.168.10.40 [10.0.20348]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- 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 a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, 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) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
===== 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): ...\North Central HIDTA\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Apache - Update Required
Vulnerability Remediation - Apache - Update Required
Product/System: Apache
Affected Systems Count: 24
Finding summary:
Apache is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2024-38475
https://nvd.nist.gov/vuln/detail/CVE-2024-38475
Additional CVEs (79 more) are listed in the Client Folder report.
Minimum version to reach:
- Check Remediation Script (or the latest available).
Affected Systems:
Sorry for the long host list below (24 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- 192.168.95.100 [1300 vulns]
- 192.168.95.12 [1300 vulns]
- 192.168.95.13 [1300 vulns]
- 192.168.95.14 [1300 vulns]
- 192.168.95.15 [1300 vulns]
- 192.168.95.16 [1300 vulns]
- 192.168.95.17 [1300 vulns]
- 192.168.95.18 [1300 vulns]
- 192.168.95.19 [1300 vulns]
- 192.168.99.12 [1300 vulns]
- 192.168.99.15 [1300 vulns]
- 192.168.99.17 [1300 vulns]
- 192.168.99.18 [1300 vulns]
- 192.168.99.19 [1300 vulns]
- 192.168.99.23 [1300 vulns]
- 192.168.99.24 [1300 vulns]
- 192.168.99.25 [1300 vulns]
- 192.168.99.31 [1300 vulns]
- 192.168.99.32 [1300 vulns]
- 192.168.99.33 [1300 vulns]
- 192.168.99.34 [1300 vulns]
- 192.168.99.35 [1300 vulns]
- 192.168.99.36 [1300 vulns]
- 192.168.99.37 [1300 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) =====
Remediation: AXIS A1601 Door Controllers (192.168.95.x / 192.168.99.x)
Update firmware via AXIS Device Manager (or AXIS Companion, depending on deployment) — pull each controller's current firmware version and update to latest stable release per Axis's published firmware notes.
Standard OS/software patch tooling does not apply — these are embedded appliances, not patchable servers.
Change default admin credentials on each controller if not already done.
Restrict management interface access to a dedicated access-control/physical-security VLAN; do not expose to general IT network segments.
Confirm ownership/administration with client — may sit outside River Run's standard managed scope if a third-party access-control integrator manages these.
===== 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): ...\North Central HIDTA\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: 11
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
Additional CVEs (85 more) are listed in the Client Folder report.
Affected Systems:
- HIDTA-VEEAM - 192.168.33.150 [294 vulns]
- HIDTA-PLX-01 - 10.100.177.100 [8.0.20] [228 vulns]
- HIDTA-VEEAM - 192.168.33.150 [8.0.21] [216 vulns]
- ISC-UFED24-01 (UFEDTech) - 10.100.130.82 [6.0.16] [118 vulns]
- HIDTA-PLX-01 - 10.100.177.100 [8.0.13] [84 vulns]
- ISC-UFED24-01 (UFEDTech) - 10.100.130.82 [3.1.18] [36 vulns]
- HIDTA-PLX-01 - 10.100.177.100 [10.0.9] [36 vulns]
- ISC-UFED24-01 (UFEDTech) - 10.100.130.82 [18 vulns]
- ISC-UFED24-01 (UFEDTech) - 10.100.130.82 [6.0.36] [3 vulns]
- HIDTA-PLX-01 - 10.100.177.100
- ISC-PESK24 - 192.168.99.212 [6.0.36]
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 10 (LTS): update runtime to the reported target within the 10.x line
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\North Central HIDTA\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: 25
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 (348 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 (25 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- DESKTOP-ETR055N (RandallKwasinski) - 192.168.66.73 [358 vulns]
- ISC-SCHI26 - 10.100.130.116 [37 vulns]
- A-ALBR25 (ScottAlbrecht) - 192.168.99.112 [11 vulns]
- DESKTOP-PRBQORG (Enforcement) - 192.168.66.106 [11 vulns]
- isc-chin25 (ElijahAChinavare) - 10.100.130.5 [11 vulns]
- ISC-KULI25 (JulieAKuligowski) - 10.100.130.8 [11 vulns]
- ISC-INTERN25-B (NatalieGuelzow) - 10.100.130.17 [1 vulns]
- A-SANF26 (JimSanfilippo) - 192.168.0.177
- A-SHOG25 (RyanShogren) - 192.168.0.8
- DESKTOP-25MRHLB - 192.168.0.160
- DESKTOP-NBSNV3N (Cellhawk1) - 10.100.177.36
- ISC-FISC24 (AlexanderJFischer) - 192.168.99.224
- ISC-GUEL25 - 192.168.15.151
- ISC-HAIG25 (EzraJHaight) - 192.168.2.8
- ISC-HANS25 (CatherineHansen) - 10.100.130.4
- ISC-HENG25 (GarrettHeng) - 10.100.130.85
- ISC-LESA25L (SheaLaSage) - 10.100.130.86
- ISC-MAHM25 (YousifMahmoud) - 192.168.5.119
- ISC-NESP25 (ErikNespoli) - 10.100.130.103
- ISC-PESK24 - 192.168.99.212
- ISC-RUTT25 (FredRutter) - 10.100.130.104
- ISC-SAYP25 (CelineCSaypanya) - 192.168.99.87
- ISC-SKEL25 (BrennaSkelton) - 10.100.130.6
- ISC-UFED24-01 (UFEDTech) - 10.100.130.82
- ISC-UNGE25 (BrantUngerer) - 10.100.130.14
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): ...\North Central HIDTA\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Update Required
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Update Required
Product/System: Microsoft 365 Apps for enterprise - en-us
Affected Systems Count: 1
Finding summary:
Microsoft 365 Apps for enterprise - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-70329
https://nvd.nist.gov/vuln/detail/CVE-2026-70329
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70329
Additional CVEs (87 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- ISC-PESK24 - 192.168.99.212
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): ...\North Central HIDTA\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-16353
https://nvd.nist.gov/vuln/detail/CVE-2026-16353
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (166 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 154.0.1 (or the latest available).
Affected Systems:
- ISC-MAHM25 (YousifMahmoud) - 192.168.5.119 [196 vulns]
- HuskyX8.milwaukeehidta - 192.168.10.220
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): ...\North Central HIDTA\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: 3
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 (11 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:
- HuskyX8.milwaukeehidta - 192.168.10.220
- ISC-NESP25 (ErikNespoli) - 10.100.130.103
- ISC-PESK24 - 192.168.99.212
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): ...\North Central HIDTA\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: 5
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 (27 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 5.1.16.194 (or the latest available)
- Update to version 15.81.5 (or the latest available). Update to version 26.001.21789 (or the latest available). Update to version 5.1.16.194 (or the latest available). Update to version 8.9.8 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
- ISC-HANS25 (CatherineHansen) - 10.100.130.4 [27 vulns]
- ISC-LESA25L (SheaLaSage) - 10.100.130.86 [1 vulns]
- ISC-MAHM25 (YousifMahmoud) - 192.168.5.119 [1 vulns]
- ISC-WEBS25 (MichaelWebster) - 10.100.130.105 [1 vulns]
- ISC-PESK24 - 192.168.99.212
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): ...\North Central HIDTA\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 23.01 (x64 edition) - Update Required
Vulnerability Remediation - 7-Zip 23.01 (x64 edition) - Update Required
Product/System: 7-Zip 23.01 (x64 edition)
Affected Systems Count: 1
Finding summary:
7-Zip 23.01 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (16 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- ISC-PESK24 - 192.168.99.212
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\North Central HIDTA\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: 2
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 (10 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 13.1.0 (or the latest available).
Affected Systems:
- MKEAXIS-01.milwaukeehidta - 192.168.10.50
- MKEMCFS01.milwaukeehidta - 192.168.10.40
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): ...\North Central HIDTA\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Ryan,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 11):
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.