Report files for this session are not in the quarterly folder yet. Export writes them, then you can paste OneDrive links and send the client email.
Export client reports
Ellenbecker Investment Group, Inc. Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-22 | Presenter: Josh Valin | Export set: 10 in export (Top 10) | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Google Chrome Remediation Options: Update to version 151.0.4129.78 or later; uninstall if not in use Target Machines: DESKTOP-JBR4QMM (FaithReiter), EIG-2025-17 (JillEconomou), EIG-2020-A (JulieEllenbecker-Lip), EIG-2024-02 (ShellyJones), EIG-2025-07 (ColinOquist), EIG-2025-10R (NikKibardin), EIG-2025-20 (moneysense), EIG-2025-23 (AlyssaGriffin), EIG-2025-24 (GinaTegge), EIG-LT2022-11 (TammyNiemann) Estimated Time of Remediation: 0.25 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: EIG-2025-08 (KyleeHeck), DESKTOP-9O4Q05R (Education Room), DESKTOP-JBR4QMM (FaithReiter), EIG-Jump-5 (JustinBertzyk), EIG-LT2022-11 (TammyNiemann), EIG-LT21-7 Estimated Time of Remediation: 0.75 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 1 hour
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top Ten vulnerabilities docx report - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with IT to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
itcontacts@ellenbecker.com
itcontacts@ellenbecker.com
2026 Q4 Vulnerability Scan Follow Up
Good evening IT, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top Ten): Complete report package: The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Josh Valin
2026 Q4 Remaining remediations
Good evening IT, Following the quarterly vulnerability review for Ellenbecker Investment Group, Inc., the items below still need remediation. These are typically third-party products or other remaining work that was not included in ticketed first-party remediations. 1. Google Chrome Affected hosts: DESKTOP-JBR4QMM (FaithReiter) - 192.168.1.11, EIG-2025-17 (JillEconomou) - 192.168.0.165, EIG-2020-A (JulieEllenbecker-Lip) - 192.168.7.136, EIG-2024-02 (ShellyJones) - 192.168.0.130, EIG-2025-07 (ColinOquist) - 192.168.0.147, EIG-2025-10R (NikKibardin) - 192.168.0.178, EIG-2025-20 (moneysense) - 192.168.0.57, EIG-2025-23 (AlyssaGriffin) - 192.168.86.22, EIG-2025-24 (GinaTegge) - 192.168.0.128, EIG-LT2022-11 (TammyNiemann) - 192.168.1.145 What to do: Update Google Chrome to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 2. Adobe Acrobat (64-bit) Affected hosts: EIG-2025-08 (KyleeHeck) - 192.168.0.91, DESKTOP-9O4Q05R (Education Room) - 192.168.0.57, DESKTOP-JBR4QMM (FaithReiter) - 192.168.1.11, EIG-Jump-5 (JustinBertzyk) - 192.168.0.54, EIG-LT2022-11 (TammyNiemann) - 192.168.1.145, EIG-LT21-7 - 10.0.0.8 What to do: Update Adobe Acrobat (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). If you would like us to quote this work, or if you will handle it internally, reply to this email. If an item cannot be remediated for business reasons, let me know and I can suppress it from further scan reports. Sincerely, Josh Valin
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Product/System: Windows 11 (all versions)
Affected Systems Count: 29
Finding summary:
Windows 11 (all versions) 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-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (1591 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5121003. Apply the latest patch
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (29 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- EIG-2025-27 (KateMurphy) - 192.168.0.134 [10.0.26100] [1583 vulns]
- EIG-2020-A (JulieEllenbecker-Lip) - 192.168.7.136 [10.0.26100] [1548 vulns]
- EIG-LT21-7 - 10.0.0.8 [10.0.26100] [1449 vulns]
- EIG-2025-18 (AmyAnderson) - 192.168.0.134 [10.0.26100] [1070 vulns]
- EIG-2025-24 (GinaTegge) - 192.168.0.128 [10.0.26100] [1070 vulns]
- EIG-2022-3 (PamPeterson) - 192.168.0.76 [10.0.26100] [1036 vulns]
- EIG-2022-7 - 192.168.0.189 [10.0.26100] [1036 vulns]
- EIG-2023-6 (KateLind) - 192.168.0.89 [10.0.26100] [1036 vulns]
- EIG-2024-03 (MicheleBrehm) - 192.168.0.124 [10.0.26100] [1036 vulns]
- EIG-2024-05 (ChristineRemmers) - 10.0.4.91 [10.0.26100] [1036 vulns]
- EIG-2024-06 (MarinaZiolkowski) - 192.168.0.111 [10.0.26100] [1036 vulns]
- EIG-2024-11 (StacyMelichar) - 192.168.0.81 [10.0.26100] [1036 vulns]
- EIG-2025-01 (AmyBremmer) - 192.168.0.44 [10.0.26100] [1036 vulns]
- EIG-2025-03 (MattSlifka) - 192.168.1.233 [10.0.26100] [1036 vulns]
- EIG-2025-07 (ColinOquist) - 192.168.0.147 [10.0.26100] [1036 vulns]
- EIG-2025-13 - 192.168.0.140 [10.0.26100] [1036 vulns]
- EIG-2025-17 (JillEconomou) - 192.168.0.165 [10.0.26100] [1036 vulns]
- EIG-ADMIN-PC1 (RiverRunSupport) - 192.168.0.61 [10.0.26100] [1036 vulns]
- EIG-LT2022-08 (JillEconomou) - 192.168.0.168 [10.0.26100] [1036 vulns]
- EIG-LT21-4 (KarenEllenbecker) - 192.168.4.44 [10.0.26100] [1036 vulns]
- EIG-JUMP2 (HaleyFuhrmann) - 192.168.0.209 [10.0.26100] [917 vulns]
- EIG-2025-23 (AlyssaGriffin) - 192.168.86.22 [10.0.26100] [738 vulns]
- EIG-2024-09 (DebbieJust) - 192.168.1.27 [10.0.26100] [729 vulns]
- EIG-2023-5 (KristinaSchnuckelCFP) - 192.168.50.101 [10.0.26100] [564 vulns]
- EIG-2025-11 (ElenaAviles) - 192.168.0.201 [10.0.26200] [564 vulns]
- EIG-2025-16 (LexieBrown) - 192.168.0.145 [10.0.26100] [564 vulns]
- EIG-2025-22 (SandraGeisler) - 192.168.0.176 [10.0.26100] [564 vulns]
- EIG-Jump-5 (JustinBertzyk) - 192.168.0.54 [10.0.26200] [564 vulns]
- EIG-LT-0625A (BrettEngelking) - 192.168.0.78 [10.0.26100] [564 vulns]
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): ...\Ellenbecker Investment Group, Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 43
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-40364
https://nvd.nist.gov/vuln/detail/CVE-2026-40364
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40364
Additional CVEs (180 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5121003. Apply the latest patch.
Affected Systems:
Sorry for the long host list below (43 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- EIG-2023-5 (KristinaSchnuckelCFP) - 192.168.50.101 [181 vulns]
- EIG-2022-7 - 192.168.0.189 [166 vulns]
- EIG-2023-4 (MichelePawlak) - 192.168.0.100 [166 vulns]
- EIG-2022-3 (PamPeterson) - 192.168.0.76 [88 vulns]
- EIG2023-A (JeanRangeCFP®) - 192.168.0.75 [88 vulns]
- EIG-2024-01 (CatherineWatson) - 192.168.1.11 [88 vulns]
- EIG-2024-04 (RichardWolosek) - 192.168.50.34 [88 vulns]
- EIG-2024-05 (ChristineRemmers) - 10.0.4.91 [88 vulns]
- EIG-2024-06 (MarinaZiolkowski) - 192.168.0.111 [88 vulns]
- EIG-2024-07 (BreannaJones) - 192.168.68.100 [88 vulns]
- EIG-2024-08 (JamieWilliams) - 192.168.0.190 [88 vulns]
- EIG-2024-09 (DebbieJust) - 192.168.1.27 [88 vulns]
- EIG-2024-11 (StacyMelichar) - 192.168.0.81 [88 vulns]
- EIG-2025-10R (NikKibardin) - 192.168.0.178 [88 vulns]
- EIG-2025-18 (AmyAnderson) - 192.168.0.134 [88 vulns]
- EIG-2025-19 (EdwardHenning) - 192.168.0.87 [88 vulns]
- EIG-2025-22 (SandraGeisler) - 192.168.0.176 [88 vulns]
- EIG-2025-23 (AlyssaGriffin) - 192.168.86.22 [88 vulns]
- EIG-2025-24 (GinaTegge) - 192.168.0.128 [88 vulns]
- EIG-2025-25 (SammyMaples) - 192.168.0.121 [88 vulns]
- EIG-2025-27 (KateMurphy) - 192.168.0.134 [88 vulns]
- EIG-Jump-5 (JustinBertzyk) - 192.168.0.54 [88 vulns]
- EIG-LT-0625A (BrettEngelking) - 192.168.0.78 [88 vulns]
- EIG-LT2022-08 (JillEconomou) - 192.168.0.168 [88 vulns]
- EIG-LT2022-11 (TammyNiemann) - 192.168.1.145 [88 vulns]
- EIG-LT2022-12 (SageSchmidt) - 192.168.0.160 [88 vulns]
- EIG-LT21-4 (KarenEllenbecker) - 192.168.4.44 [88 vulns]
- EIG-LT21-7 - 10.0.0.8 [88 vulns]
- DESKTOP-JBR4QMM (FaithReiter) - 192.168.1.11 [78 vulns]
- EIG-2020-A (JulieEllenbecker-Lip) - 192.168.7.136 [78 vulns]
- EIG-2024-02 (ShellyJones) - 192.168.0.130 [78 vulns]
- EIG-2024-03 (MicheleBrehm) - 192.168.0.124 [78 vulns]
- EIG-2025-01 (AmyBremmer) - 192.168.0.44 [78 vulns]
- EIG-2025-02 (JustinBertzyk) - 192.168.0.69 [78 vulns]
- EIG-2025-04 (TravisWalters) - 192.168.0.81 [78 vulns]
- EIG-2025-05 (JanetOtten) - 192.168.0.73 [78 vulns]
- EIG-2025-08 (KyleeHeck) - 192.168.0.91 [78 vulns]
- EIG-2025-13 - 192.168.0.140 [78 vulns]
- EIG-2025-14 (CourtneyWitthuhn) - 192.168.10.101 [78 vulns]
- EIG-2025-16 (LexieBrown) - 192.168.0.145 [78 vulns]
- EIG-2025-17 (JillEconomou) - 192.168.0.165 [78 vulns]
- EIG-2025-21 (HaleyFuhrmann) - 192.168.10.100 [78 vulns]
- eig-2025-26 (KarenEllenbecker) - 192.168.0.54 [78 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) =====
- 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): ...\Ellenbecker Investment Group, Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Product/System: Microsoft 365 Apps for enterprise - en-us
Affected Systems Count: 7
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-2024-21413
https://nvd.nist.gov/vuln/detail/CVE-2024-21413
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21413
Additional CVEs (426 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- EIG-2023-3 - 192.168.0.138 [428 vulns]
- DESKTOP-JBR4QMM (FaithReiter) - 192.168.1.11 [166 vulns]
- EIG-JUMP1 - 192.168.0.178 [88 vulns]
- EIG-JUMP2 (HaleyFuhrmann) - 192.168.0.209 [88 vulns]
- EIG-JUMP4 - 192.168.0.210 [88 vulns]
- EIG-Jump-6 (JeanRangeCFP®) - 192.168.0.111 [88 vulns]
- EIG-Jump-7 (MicheleBrehm) - 192.168.0.143 [88 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) =====
- 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): ...\Ellenbecker Investment Group, Inc\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: 33
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-2026-62898
https://nvd.nist.gov/vuln/detail/CVE-2026-62898
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62898
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.0.11 (or the latest available).
Affected Systems:
Sorry for the long host list below (33 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- DESKTOP-9O4Q05R (Education Room) - 192.168.0.57 [10.0.10] [15 vulns]
- EIG-2022-3 (PamPeterson) - 192.168.0.76 [10.0.10] [15 vulns]
- EIG-2023-3 - 192.168.0.138 [10.0.10] [15 vulns]
- EIG-2023-4 (MichelePawlak) - 192.168.0.100 [10.0.10] [15 vulns]
- EIG-2023-5 (KristinaSchnuckelCFP) - 192.168.50.101 [10.0.10] [15 vulns]
- EIG-2023-6 (KateLind) - 192.168.0.89 [10.0.10] [15 vulns]
- EIG-2024-02 (ShellyJones) - 192.168.0.130 [10.0.10] [15 vulns]
- EIG-2024-03 (MicheleBrehm) - 192.168.0.124 [10.0.10] [15 vulns]
- EIG-2024-04 (RichardWolosek) - 192.168.50.34 [10.0.10] [15 vulns]
- EIG-2024-05 (ChristineRemmers) - 10.0.4.91 [10.0.10] [15 vulns]
- EIG-2024-06 (MarinaZiolkowski) - 192.168.0.111 [10.0.10] [15 vulns]
- EIG-2024-07 (BreannaJones) - 192.168.68.100 [10.0.10] [15 vulns]
- EIG-2024-08 (JamieWilliams) - 192.168.0.190 [10.0.10] [15 vulns]
- EIG-2024-09 (DebbieJust) - 192.168.1.27 [10.0.10] [15 vulns]
- EIG-2024-10 (JulieEllenbecker-Lip) - 192.168.0.244 [10.0.10] [15 vulns]
- EIG-2024-11 (StacyMelichar) - 192.168.0.81 [10.0.10] [15 vulns]
- EIG-2025-01 (AmyBremmer) - 192.168.0.44 [10.0.10] [15 vulns]
- EIG-2025-02 (JustinBertzyk) - 192.168.0.69 [10.0.10] [15 vulns]
- EIG-2025-03 (MattSlifka) - 192.168.1.233 [10.0.10] [15 vulns]
- EIG-2025-04 (TravisWalters) - 192.168.0.81 [10.0.10] [15 vulns]
- EIG-2025-05 (JanetOtten) - 192.168.0.73 [10.0.10] [15 vulns]
- EIG-2025-07 (ColinOquist) - 192.168.0.147 [10.0.10] [15 vulns]
- EIG-2025-08 (KyleeHeck) - 192.168.0.91 [10.0.10] [15 vulns]
- EIG-2025-10R (NikKibardin) - 192.168.0.178 [10.0.10] [15 vulns]
- EIG-2025-11 (ElenaAviles) - 192.168.0.201 [10.0.10] [15 vulns]
- EIG-2025-12 (LaurenDuimstra) - 192.168.0.63 [10.0.10] [15 vulns]
- EIG-2025-13 - 192.168.0.140 [10.0.10] [15 vulns]
- EIG-2025-14 (CourtneyWitthuhn) - 192.168.10.101 [10.0.10] [15 vulns]
- EIG-2025-15 (BenL''Empereur) - 192.168.0.86 [10.0.10] [15 vulns]
- EIG-2025-16 (LexieBrown) - 192.168.0.145 [10.0.10] [15 vulns]
- EIG-2025-17 (JillEconomou) - 192.168.0.165 [10.0.10] [15 vulns]
- EIG-2025-23 (AlyssaGriffin) - 192.168.86.22 [10.0.10] [15 vulns]
- EIG-ADMIN-PC1 (RiverRunSupport) - 192.168.0.61 [10.0.10] [15 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 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): ...\Ellenbecker Investment Group, Inc\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: 12
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 26183.1903.4892.4448 (or the latest available).
Affected Systems:
- DESKTOP-9O4Q05R (Education Room) - 192.168.0.57 [7 vulns]
- EIG-2022-3 (PamPeterson) - 192.168.0.76 [7 vulns]
- EIG-2022-7 - 192.168.0.189 [7 vulns]
- EIG-2023-3 - 192.168.0.138 [7 vulns]
- EIG-2023-5 (KristinaSchnuckelCFP) - 192.168.50.101 [7 vulns]
- EIG-2023-6 (KateLind) - 192.168.0.89 [7 vulns]
- EIG2023-A (JeanRangeCFP®) - 192.168.0.75 [7 vulns]
- EIG-LT2022-08 (JillEconomou) - 192.168.0.168 [7 vulns]
- EIG-LT2022-11 (TammyNiemann) - 192.168.1.145 [7 vulns]
- EIG-LT2022-12 (SageSchmidt) - 192.168.0.160 [7 vulns]
- EIG-LT21-4 (KarenEllenbecker) - 192.168.4.44 [7 vulns]
- EIG-LT21-7 - 10.0.0.8 [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): ...\Ellenbecker Investment Group, Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Visual C++ (all versions) - Update Required
Vulnerability Remediation - Microsoft Visual C++ (all versions) - Update Required
Product/System: Microsoft Visual C++ (all versions)
Affected Systems Count: 47
Finding summary:
Microsoft Visual C++ (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.
Affected Systems:
Sorry for the long host list below (47 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- EIG-2022-7 - 192.168.0.189 [11.0.61030] [6 vulns]
- EIG-2023-3 - 192.168.0.138 [11.0.61030] [6 vulns]
- EIG-2023-4 (MichelePawlak) - 192.168.0.100 [11.0.61030] [6 vulns]
- EIG-LT2022-08 (JillEconomou) - 192.168.0.168 [11.0.61030] [6 vulns]
- EIG-2022-7 - 192.168.0.189 [12.0.40664] [6 vulns]
- EIG-2023-3 - 192.168.0.138 [12.0.40664] [6 vulns]
- EIG-2023-4 (MichelePawlak) - 192.168.0.100 [12.0.40664] [6 vulns]
- EIG-LT2022-08 (JillEconomou) - 192.168.0.168 [12.0.40664] [6 vulns]
- EIG-2024-04 (RichardWolosek) - 192.168.50.34 [12.0.21005] [4 vulns]
- EIG-2024-05 (ChristineRemmers) - 10.0.4.91 [12.0.21005] [4 vulns]
- EIG-LT2022-12 (SageSchmidt) - 192.168.0.160 [12.0.21005] [4 vulns]
- EIG-2024-05 (ChristineRemmers) - 10.0.4.91 [11.0.50727] [3 vulns]
- EIG-2025-11 (ElenaAviles) - 192.168.0.201 [11.0.50727] [3 vulns]
- EIG-2024-04 (RichardWolosek) - 192.168.50.34 [12.0.30501] [2 vulns]
- EIG-2024-05 (ChristineRemmers) - 10.0.4.91 [12.0.30501] [2 vulns]
- EIG-LT2022-12 (SageSchmidt) - 192.168.0.160 [12.0.30501] [2 vulns]
- EIG-2022-3 (PamPeterson) - 192.168.0.76 [12.0.21005] [2 vulns]
- EIG-2023-6 (KateLind) - 192.168.0.89 [12.0.21005] [2 vulns]
- EIG-2024-11 (StacyMelichar) - 192.168.0.81 [12.0.21005] [2 vulns]
- EIG-2025-02 (JustinBertzyk) - 192.168.0.69 [12.0.21005] [2 vulns]
- EIG-2025-03 (MattSlifka) - 192.168.1.233 [12.0.21005] [2 vulns]
- EIG-2025-07 (ColinOquist) - 192.168.0.147 [12.0.21005] [2 vulns]
- EIG-LT-0625A (BrettEngelking) - 192.168.0.78 [12.0.21005] [2 vulns]
- EIG-LT21-7 - 10.0.0.8 [12.0.21005] [2 vulns]
- EIG-2022-7 - 192.168.0.189 [10.0.40219] [2 vulns]
- EIG-2025-11 (ElenaAviles) - 192.168.0.201 [12.0.21005] [2 vulns]
- EIG-2022-3 (PamPeterson) - 192.168.0.76 [12.0.30501] [1 vulns]
- EIG-2023-3 - 192.168.0.138 [12.0.30501] [1 vulns]
- EIG-2023-6 (KateLind) - 192.168.0.89 [12.0.30501] [1 vulns]
- EIG-2024-11 (StacyMelichar) - 192.168.0.81 [12.0.30501] [1 vulns]
- EIG-2025-02 (JustinBertzyk) - 192.168.0.69 [12.0.30501] [1 vulns]
- EIG-2025-03 (MattSlifka) - 192.168.1.233 [12.0.30501] [1 vulns]
- EIG-2025-07 (ColinOquist) - 192.168.0.147 [12.0.30501] [1 vulns]
- EIG-LT-0625A (BrettEngelking) - 192.168.0.78 [12.0.30501] [1 vulns]
- EIG-LT21-7 - 10.0.0.8 [12.0.30501] [1 vulns]
- EIG-2024-04 (RichardWolosek) - 192.168.50.34 [9.0.30729.17] [1 vulns]
- EIG-2024-05 (ChristineRemmers) - 10.0.4.91 [9.0.30729.17] [1 vulns]
- EIG-2025-11 (ElenaAviles) - 192.168.0.201 [9.0.30729.17] [1 vulns]
- EIG-LT2022-12 (SageSchmidt) - 192.168.0.160 [9.0.30729.17] [1 vulns]
- EIG-2024-04 (RichardWolosek) - 192.168.50.34 [9.0.30729.6161] [1 vulns]
- EIG-2024-05 (ChristineRemmers) - 10.0.4.91 [9.0.30729.6161] [1 vulns]
- EIG-2025-11 (ElenaAviles) - 192.168.0.201 [9.0.30729.6161] [1 vulns]
- EIG-LT2022-12 (SageSchmidt) - 192.168.0.160 [9.0.30729.6161] [1 vulns]
- EIG-2025-11 (ElenaAviles) - 192.168.0.201 [12.0.30501] [1 vulns]
- EIG-2025-12 (LaurenDuimstra) - 192.168.0.63 [1 vulns]
- EIG-2025-13 - 192.168.0.140 [1 vulns]
- EIG-LT21-7 - 10.0.0.8 [10.0.30319] [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) =====
- Visual C++ redistributables are side-by-side - do not upgrade everything to the latest year
- An app built on one major version is tied to that version - removing it will break the app.
- Only remove a year if no app is using it.
- Patch each major version seen below with the matching vc_redist or Windows Update package
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Verify the update was successful
- 2008 (9.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2010 (10.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2012 (11.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2013 (12.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless 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): ...\Ellenbecker Investment Group, Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Defender - Update Required
Vulnerability Remediation - Microsoft Defender - Update Required
Product/System: Microsoft Defender
Affected Systems Count: 6
Finding summary:
Microsoft Defender 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-50656
https://nvd.nist.gov/vuln/detail/CVE-2026-50656
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50656
Additional CVEs (3 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.18.26060.3008 (or the latest available).
Affected Systems:
- EIG-2024-01 (CatherineWatson) - 192.168.1.11 [4 vulns]
- EIG-2023-4 (MichelePawlak) - 192.168.0.100 [3 vulns]
- EIG-2023-5 (KristinaSchnuckelCFP) - 192.168.50.101 [3 vulns]
- EIG-2025-02 (JustinBertzyk) - 192.168.0.69 [3 vulns]
- EIG-2025-08 (KyleeHeck) - 192.168.0.91 [3 vulns]
- EIG-LT2022-12 (SageSchmidt) - 192.168.0.160 [3 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) =====
- Check Windows Security on each host: is another EDR/AV active (SentinelOne, Huntress, Webroot, Bitdefender, or similar)?
- If yes and Defender real-time protection is off: that is expected. This finding is a Defender version, not the live AV
- Do not turn Defender real-time protection back on next to that EDR
- If Defender is still the AV, or the platform/service is still running: update platform/signatures via Windows Update or Defender management policy
- Check RMM patch status if patch management is deployed
- Confirm engine/platform version after update
- Then stop if:
- Another EDR is healthy and Defender RTP is off (version/signature age only): notify the client, record discussion notes, escalate to Security for suppression
- Update failed because Defender is fully disabled: same path - the EDR is the control; escalate to Security for suppression
- If the CVE is in a Defender driver or service that is still loaded: update the Defender platform anyway
===== 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): ...\Ellenbecker Investment Group, Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Google Chrome - Update Required - 3rd party application
Vulnerability Remediation - Google Chrome - Update Required - 3rd party application
Product/System: Google Chrome
Affected Systems Count: 10
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-17651
https://nvd.nist.gov/vuln/detail/CVE-2026-17651
Vendor security center:
https://chromereleases.googleblog.com/
Additional CVEs (415 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 151.0.4129.78 (or the latest available). Update to version 151.0.7922.138 (or the latest available)
- Update to version 151.0.7922.138 (or the latest available). Update to version 26.3 (or the latest available)
- Update to version 151.0.7922.138 (or the latest available). Update to version 26.001.21789 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- DESKTOP-JBR4QMM (FaithReiter) - 192.168.1.11 [416 vulns]
- EIG-2025-17 (JillEconomou) - 192.168.0.165 [416 vulns]
- EIG-2020-A (JulieEllenbecker-Lip) - 192.168.7.136 [46 vulns]
- EIG-2024-02 (ShellyJones) - 192.168.0.130 [1 vulns]
- EIG-2025-07 (ColinOquist) - 192.168.0.147 [1 vulns]
- EIG-2025-10R (NikKibardin) - 192.168.0.178 [1 vulns]
- EIG-2025-20 (moneysense) - 192.168.0.57 [1 vulns]
- EIG-2025-23 (AlyssaGriffin) - 192.168.86.22 [1 vulns]
- EIG-2025-24 (GinaTegge) - 192.168.0.128 [1 vulns]
- EIG-LT2022-11 (TammyNiemann) - 192.168.1.145 [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)
- 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): ...\Ellenbecker Investment Group, Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required - 3rd party application
Product/System: Adobe Acrobat (64-bit)
Affected Systems Count: 6
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 (17 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 151.0.7922.138 (or the latest available). Update to version 26.001.21789 (or the latest available).
Affected Systems:
- EIG-2025-08 (KyleeHeck) - 192.168.0.91 [18 vulns]
- DESKTOP-9O4Q05R (Education Room) - 192.168.0.57 [1 vulns]
- DESKTOP-JBR4QMM (FaithReiter) - 192.168.1.11 [1 vulns]
- EIG-Jump-5 (JustinBertzyk) - 192.168.0.54 [1 vulns]
- EIG-LT2022-11 (TammyNiemann) - 192.168.1.145 [1 vulns]
- EIG-LT21-7 - 10.0.0.8 [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): ...\Ellenbecker Investment Group, Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft.Microsoft3DViewer - Update Required
Vulnerability Remediation - Microsoft.Microsoft3DViewer - Update Required
Product/System: Microsoft.Microsoft3DViewer
Affected Systems Count: 9
Finding summary:
Microsoft.Microsoft3DViewer 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.
Minimum version to reach:
Multiple bundled scanner entries report end-of-life components; patch within each runtime line per remediation guidance (or the latest available).
Affected Systems:
- DESKTOP-9O4Q05R (Education Room) - 192.168.0.57 [1 vulns]
- EIG-2022-7 - 192.168.0.189 [1 vulns]
- EIG-2023-3 - 192.168.0.138 [1 vulns]
- EIG-2023-4 (MichelePawlak) - 192.168.0.100 [1 vulns]
- EIG-2023-5 (KristinaSchnuckelCFP) - 192.168.50.101 [1 vulns]
- EIG-2023-6 (KateLind) - 192.168.0.89 [1 vulns]
- EIG-LT2022-08 (JillEconomou) - 192.168.0.168 [1 vulns]
- EIG-LT2022-12 (SageSchmidt) - 192.168.0.160 [1 vulns]
- EIG-LT21-4 (KarenEllenbecker) - 192.168.4.44 [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) =====
- Microsoft Store apps are per-user
- Backstage CMD / Command Prompt runs as SYSTEM
- winget as SYSTEM is not supported and may only update the SYSTEM profile - not the signed-in user's Store apps
- Use Backstage user-context terminal (logged-on user) or a live user session
- ScreenConnect Backstage: CMD/PS/scripts only (installer/winget) - not in-app GUI menus
- In-app Check for Updates / Help > About needs a live user session
- CMD console runs as SYSTEM; winget is not supported as SYSTEM
- Microsoft Store apps are per-user - winget from Backstage CMD may only update the SYSTEM profile, not the signed-in user's Store apps
- Use Backstage user-context terminal (logged-on user) or a live user session for Store apps / per-user winget
===== 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): ...\Ellenbecker Investment Group, Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening IT,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top Ten):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical).
• All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity.
• Executive Summary Report - a high-level overview of your security posture and network information.
• External Scan - detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Josh Valin
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.