Shoreview Pediatrics Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-08-29 | Presenter: Chris Knospe | 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: Mozilla Firefox Remediation Options: Update to version 154.0.1 or later; uninstall if not in use Target Machines: BILLINGRIGHT.int.shoreviewpediatrics, SakhnoLaptop.int.shoreviewpediatrics (Bsakhno), IntergyServer.int.shoreviewpediatrics, SVP-APP02.int.shoreviewpediatrics (rradmin) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Java 8 Update 201 (64-bit) Remediation Options: Update to version 8.0.5030.1 or later; uninstall if not in use Target Machines: IntergyServer.int.shoreviewpediatrics Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: PostgreSQL 14 Remediation Options: Update to version 16.1 or later; uninstall if not in use Target Machines: IntergyServer.int.shoreviewpediatrics Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinRAR 5.80 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: BILLINGRIGHT.int.shoreviewpediatrics Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 2.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 Ten vulnerabilities docx report - Ticket #1892047: Vulnerability Remediation - Windows 11 (all versions) - Updates Required - Ticket #1892048: Vulnerability Remediation - Microsoft Office Home and Business 2019 - en-us - Updates Required - Ticket #1892049: Vulnerability Remediation - Microsoft .NET (all versions) - Update Required - Ticket #1892050: Vulnerability Remediation - Google Chrome - Update Required - Ticket #1892051: Vulnerability Remediation - Microsoft Edge - Updates Required - Ticket #1892052: Vulnerability Remediation - FortiClient - Update Required - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with Tiffanie to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
office@shoreviewpediatrics.com
office@shoreviewpediatrics.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Tiffanie, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top Ten): Open Top Ten report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Chris Knospe
2026 Q4 Remaining remediations
Good evening Tiffanie, Following the quarterly vulnerability review for Shoreview Pediatrics, 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. Mozilla Firefox Affected hosts: BILLINGRIGHT.int.shoreviewpediatrics - 172.16.16.183, SakhnoLaptop.int.shoreviewpediatrics (Bsakhno) - 172.16.16.110, IntergyServer.int.shoreviewpediatrics - 172.16.16.10, SVP-APP02.int.shoreviewpediatrics (rradmin) - 172.16.16.26 What to do: Update Mozilla Firefox 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. Java 8 Update 201 (64-bit) Affected hosts: IntergyServer.int.shoreviewpediatrics - 172.16.16.10 What to do: Update Java 8 Update 201 (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). 3. PostgreSQL 14 Affected hosts: IntergyServer.int.shoreviewpediatrics - 172.16.16.10 What to do: Update PostgreSQL 14 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). 4. WinRAR 5.80 (64-bit) Affected hosts: BILLINGRIGHT.int.shoreviewpediatrics - 172.16.16.183 What to do: Update WinRAR 5.80 (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, Chris Knospe
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: 1
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 (1456 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5121003 (or the latest available).
Affected Systems:
- LaureeKlees.int.shoreviewpediatrics (lklees) - 172.16.16.103 [10.0.26100] [1450 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): ...\Shoreview Pediatrics\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Office Home and Business 2019 - en-us - Updates Required
Vulnerability Remediation - Microsoft Office Home and Business 2019 - en-us - Updates Required
Product/System: Microsoft Office Home and Business 2019 - en-us
Affected Systems Count: 5
Finding summary:
Microsoft Office Home and Business 2019 - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-21509
https://nvd.nist.gov/vuln/detail/CVE-2026-21509
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21509
Additional CVEs (241 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5120249. Apply the latest patch
- (2 end-of-life component notices omitted).
Affected Systems:
- BILLINGRIGHT.int.shoreviewpediatrics - 172.16.16.183 [1155 vulns]
- Kathy-Laptop.int.shoreviewpediatrics (kbesgrove) - 172.16.16.167 [167 vulns]
- Frontcenter.int.shoreviewpediatrics (jmarinello) - 172.16.16.149 [1 vulns]
- FRONTLEFT - 172.16.16.139 [1 vulns]
- Jenofficeandhome.int.shoreviewpediatrics (jtwente) - 192.168.1.152 [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 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): ...\Shoreview Pediatrics\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: 7
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 (38 more) are listed in the Client Folder report.
Affected Systems:
- Yesi.int.shoreviewpediatrics (Tmeeks) - 172.16.16.184 [8.0.16] [117 vulns]
- SVP-0324-A - 172.16.16.171 [6.0.36] [75 vulns]
- SVP-0324-A - 172.16.16.171 [8.0.28] [75 vulns]
- OBrien.int.shoreviewpediatrics (bobrien) - 192.168.0.110 [6.0.36]
- Perry-Office.int.shoreviewpediatrics (pkrumenacher) - 172.16.16.142 [6.0.36]
- SVP-0924-B.int.shoreviewpediatrics (pfuller) - 172.16.16.151 [6.0.36]
- JULIEF2025.int.shoreviewpediatrics (jfuller) - 172.16.16.148 [8.0.29]
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 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)
===== 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): ...\Shoreview Pediatrics\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: 14
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 (830 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:
- SVP-0324-A - 172.16.16.171 [1636 vulns]
- JILLBRESNAHANSPARE.int.shoreviewpediatrics - 192.168.0.13 [628 vulns]
- Yesi.int.shoreviewpediatrics (Tmeeks) - 172.16.16.184 [327 vulns]
- Anna.int.shoreviewpediatrics (abublitz) - 172.16.16.165
- BRENDA-DESKTOP.int.shoreviewpediatrics (bhach) - 172.16.16.156
- DESKTOP-L4E8C4H.int.shoreviewpediatrics (kpezzi) - 172.16.16.133
- FRONTLEFT - 172.16.16.139
- Kathy-Laptop.int.shoreviewpediatrics (kbesgrove) - 172.16.16.167
- LaureeKlees.int.shoreviewpediatrics (lklees) - 172.16.16.103
- NORA-LAPTOP.int.shoreviewpediatrics (nvalle) - 172.16.16.137
- OBrien.int.shoreviewpediatrics (bobrien) - 192.168.0.110
- Rylie.int.shoreviewpediatrics (bsakhno) - 172.16.16.146
- SakhnoLaptop.int.shoreviewpediatrics (Bsakhno) - 172.16.16.110
- SVP-0924-B.int.shoreviewpediatrics (pfuller) - 172.16.16.151
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): ...\Shoreview Pediatrics\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Mozilla Firefox - Update Required - 3rd party application
Vulnerability Remediation - Mozilla Firefox - Update Required - 3rd party application
Product/System: Mozilla Firefox
Affected Systems Count: 4
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 (207 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 154.0.1 (or the latest available).
Affected Systems:
- BILLINGRIGHT.int.shoreviewpediatrics - 172.16.16.183 [208 vulns]
- SakhnoLaptop.int.shoreviewpediatrics (Bsakhno) - 172.16.16.110 [2 vulns]
- IntergyServer.int.shoreviewpediatrics - 172.16.16.10
- SVP-APP02.int.shoreviewpediatrics (rradmin) - 172.16.16.26
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): ...\Shoreview Pediatrics\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Java 8 Update 201 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Java 8 Update 201 (64-bit) - Update Required - 3rd party application
Product/System: Java 8 Update 201 (64-bit)
Affected Systems Count: 1
Finding summary:
Java 8 Update 201 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-34169
https://nvd.nist.gov/vuln/detail/CVE-2022-34169
Vendor security center:
https://www.oracle.com/security-alerts/
Additional CVEs (59 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 8.0.5030.1 (or the latest available).
Affected Systems:
- IntergyServer.int.shoreviewpediatrics - 172.16.16.10 [60 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm which Java runtime is installed (vendor + major version, e.g. Oracle 8 / Temurin 11) on each host
- Inventory apps that require that major version before changing anything
- Primary: update within the same major version line to the Minimum version to reach target (or latest security update for that line)
- Oracle Java: Oracle installer / Java Update / enterprise package per client license
- OpenJDK / Temurin-style: Adoptium Temurin or the distro already in use (do not switch vendors without app vendor approval)
- Prefer RMM/automated patching when deployed; else vendor MSI via ScreenConnect
- If unused after dependency check: uninstall that runtime
- Verify java -version / Programs and Features and dependent app startup after change
- Java 8: stay on the existing 8u line unless the app vendor requires a newer major
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Shoreview Pediatrics\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - PostgreSQL 14 - Update Required - 3rd party application
Vulnerability Remediation - PostgreSQL 14 - Update Required - 3rd party application
Product/System: PostgreSQL 14
Affected Systems Count: 1
Finding summary:
PostgreSQL 14 is a database engine on the listed hosts.
Confirm the instance or cluster, then apply the matching engine update in a maintenance window with the DBA or app owner.
CVE references:
CVE-2022-1552
https://nvd.nist.gov/vuln/detail/CVE-2022-1552
Vendor security center:
https://www.postgresql.org/support/security/
Additional CVEs (27 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 16.1 (or the latest available).
Affected Systems:
- IntergyServer.int.shoreviewpediatrics - 172.16.16.10 [28 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) =====
- PostgreSQL is a database engine - not a desktop app
- Confirm major version and cluster on each host
- Apply the matching minor/security update for that major in a maintenance window
- Do not use winget; coordinate before restarting the service
===== 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): ...\Shoreview Pediatrics\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Edge - Updates Required
Vulnerability Remediation - Microsoft Edge - Updates Required
Product/System: Microsoft Edge
Affected Systems Count: 2
Finding summary:
Microsoft Edge is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-17651
https://nvd.nist.gov/vuln/detail/CVE-2026-17651
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-17651
Additional CVEs (503 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:
- SVP-0324-A - 172.16.16.171 [1636 vulns]
- BILLINGRIGHT.int.shoreviewpediatrics - 172.16.16.183
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): ...\Shoreview Pediatrics\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - WinRAR 5.80 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - WinRAR 5.80 (64-bit) - Update Required - 3rd party application
Product/System: WinRAR 5.80 (64-bit)
Affected Systems Count: 1
Finding summary:
WinRAR 5.80 (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-2023-38831
https://nvd.nist.gov/vuln/detail/CVE-2023-38831
Additional CVEs (8 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.23 (or the latest available).
Affected Systems:
- BILLINGRIGHT.int.shoreviewpediatrics - 172.16.16.183 [9 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. 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 WinRAR to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Backstage (CMD/PS): download latest from rarlabs.com; run installer over existing
- Verify version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Shoreview Pediatrics\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - FortiClient - Update Required
Vulnerability Remediation - FortiClient - Update Required
Product/System: FortiClient
Affected Systems Count: 1
Finding summary:
FortiClient is a VPN client on the listed hosts.
If the site has a FortiGate / Fortinet firewall, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it. Use the vendor installer from support.fortinet.com. Automated / RMM updates have failed for FortiClient VPN in the past.
CVE references:
CVE-2024-3661
https://nvd.nist.gov/vuln/detail/CVE-2024-3661
Vendor security center:
https://fortiguard.fortinet.com/psirt
Additional CVEs (9 more) are listed in the Client Folder report.
Minimum version to reach:
- null (or the latest available).
Affected Systems:
- Yesi.int.shoreviewpediatrics (Tmeeks) - 172.16.16.184 [10 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has a FortiGate / Fortinet firewall: download from support.fortinet.com and run the vendor installer to the version listed under Minimum version to reach (or the latest available). Do not rely on RMM for FortiClient VPN.
- Coordinate the FortiClient version with site FortiGate firmware before upgrading.
- If the site does not have a FortiGate / Fortinet firewall: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the update path.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- FortiClient VPN: manual vendor installer recommended
This VPN is expected if the site has a FortiGate / Fortinet firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it.
- Automated / RMM updates have failed for FortiClient VPN in the past - do not rely on them until a better path exists
- Do not use winget or automated patching for this product
- Download updated installer from support.fortinet.com
- Transfer via ScreenConnect file transfer
- CMD console (SYSTEM OK): FortiClientVPNSetup_x.x.x.exe /quiet /norestart
- Coordinate version with site FortiGate firmware before upgrading
- Verify version after install
===== 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): ...\Shoreview Pediatrics\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Tiffanie,
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,
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.