Museum of Wisconsin Art Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-08-31 | Presenter: Chris Knospe | Export set: 9 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: Chrome Remediation Options: Update to version 152.0.7977.65 or later; uninstall if not in use Target Machines: studioa Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Google Chrome Remediation Options: Update to version 152.0.7977.64 or later; uninstall if not in use Target Machines: CFO-Laptop (BrendaSchultz), MOWA12 (BruceWick), MOWA20 (Register2), MOWA-23 (GinaStockhausen), MOWA26, Thomas-LPT (ThomasSzolwinski) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Illustrator 2025 Remediation Options: Update to version 30.7 or later; uninstall if not in use Target Machines: Thomas-LPT (ThomasSzolwinski) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Photoshop 2025 Remediation Options: Update to version 27.10 or later; uninstall if not in use Target Machines: iMac-Registrar (Andrea) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 2 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 9 vulnerabilities docx report - Ticket #1892978: Vulnerability Remediation - Windows 11 (all versions) - Updates Required - Ticket #1892979: Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required - Ticket #1892980: Vulnerability Remediation - Microsoft Teams - Application Update Required - Ticket #1892981: Vulnerability Remediation - ScreenConnect Client - 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 Gina to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
ggustrowsky@wisconsinart.org
ggustrowsky@wisconsinart.org
2026 Q4 Vulnerability Scan Follow Up
Good evening Gina, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 9): Open Top 9 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 Gina, Following the quarterly vulnerability review for Museum of Wisconsin Art, 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. Chrome Affected hosts: studioa - 10.0.1.163 What to do: Update 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. Google Chrome Affected hosts: CFO-Laptop (BrendaSchultz) - 10.0.1.153, MOWA12 (BruceWick) - 10.0.1.186, MOWA20 (Register2) - 10.0.1.151, MOWA-23 (GinaStockhausen) - 10.0.1.155, MOWA26 - 10.0.1.161, Thomas-LPT (ThomasSzolwinski) - 172.20.10.2 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). 3. Adobe Illustrator 2025 Affected hosts: Thomas-LPT (ThomasSzolwinski) - 172.20.10.2 What to do: Update Adobe Illustrator 2025 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. Photoshop 2025 Affected hosts: iMac-Registrar (Andrea) - 10.0.1.185 What to do: Update Photoshop 2025 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: 4
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 (1282 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120240
- Apply Windows Update KB5121003 (or the latest available).
Affected Systems:
- MOWA12 (BruceWick) - 10.0.1.186 [10.0.26100] [1037 vulns]
- MOWA17 (JenniferArneson) - 10.0.1.131 [10.0.26100] [1037 vulns]
- Thomas-LPT (ThomasSzolwinski) - 172.20.10.2 [10.0.26100] [1037 vulns]
- MOWA09 (GraemeReid) - 10.0.1.184 [10.0.22631] [863 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): ...\Museum of Wisconsin Art\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Chrome - Update Required - 3rd party application
Vulnerability Remediation - Chrome - Update Required - 3rd party application
Product/System: Chrome
Affected Systems Count: 1
Finding summary:
Chrome 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-76036
https://nvd.nist.gov/vuln/detail/CVE-2026-76036
Additional CVEs (348 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 152.0.7977.65 (or the latest available).
Affected Systems:
- studioa - 10.0.1.163 [349 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) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Museum of Wisconsin Art\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: 1
Finding summary:
Microsoft 365 Apps for enterprise - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-70329
https://nvd.nist.gov/vuln/detail/CVE-2026-70329
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70329
Additional CVEs (87 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- MOWA21 (ShopRegister) - 10.0.1.139 [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): ...\Museum of Wisconsin Art\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: 6
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 (326 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 152.0.7977.64 (or the latest available).
Affected Systems:
- CFO-Laptop (BrendaSchultz) - 10.0.1.153 [327 vulns]
- MOWA12 (BruceWick) - 10.0.1.186 [327 vulns]
- MOWA20 (Register2) - 10.0.1.151 [327 vulns]
- MOWA-23 (GinaStockhausen) - 10.0.1.155 [327 vulns]
- MOWA26 - 10.0.1.161 [327 vulns]
- Thomas-LPT (ThomasSzolwinski) - 172.20.10.2 [327 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): ...\Museum of Wisconsin Art\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Illustrator 2025 - Update Required - 3rd party application
Vulnerability Remediation - Adobe Illustrator 2025 - Update Required - 3rd party application
Product/System: Adobe Illustrator 2025
Affected Systems Count: 1
Finding summary:
Adobe Illustrator 2025 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-48334
https://nvd.nist.gov/vuln/detail/CVE-2026-48334
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (46 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 30.7 (or the latest available).
Affected Systems:
- Thomas-LPT (ThomasSzolwinski) - 172.20.10.2 [47 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) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Museum of Wisconsin Art\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 4
Finding summary:
Microsoft Teams is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2023-4863
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
Additional CVEs (10 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26198.304.4946.9672 (or the latest available)
- Update to version 26198.202.4929.7171 (or the latest available)
- Update to version 16.112.2 (or the latest available). Update to version 26198.202.4929.7171 (or the latest available).
Affected Systems:
- MOWA06 (MariahSinclair) - 10.0.1.144 [7 vulns]
- studioa - 10.0.1.163 [5 vulns]
- CFO-Laptop (BrendaSchultz) - 10.0.1.153 [4 vulns]
- iMac-Registrar (Andrea) - 10.0.1.185 [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 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): ...\Museum of Wisconsin Art\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Photoshop 2025 - Update Required - 3rd party application
Vulnerability Remediation - Photoshop 2025 - Update Required - 3rd party application
Product/System: Photoshop 2025
Affected Systems Count: 1
Finding summary:
Photoshop 2025 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-52997
https://nvd.nist.gov/vuln/detail/CVE-2024-52997
Additional CVEs (8 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 27.10 (or the latest available).
Affected Systems:
- iMac-Registrar (Andrea) - 10.0.1.185 [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) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Museum of Wisconsin Art\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - ScreenConnect Client - Update Required
Vulnerability Remediation - ScreenConnect Client - Update Required
Product/System: ScreenConnect Client
Affected Systems Count: 1
Finding summary:
ScreenConnect Client is River Run ScreenConnect on the listed hosts.
Confirm the instance ID is a River Run ID, then update from Control. Do not treat our ScreenConnect as unauthorized remote access.
CVE references:
CVE-2025-3935
https://nvd.nist.gov/vuln/detail/CVE-2025-3935
Vendor security center:
https://www.connectwise.com/company/trust/security-bulletins
Minimum version to reach:
- Update to version 25.3.2.9271 (or the latest available).
Affected Systems:
- studioa - 10.0.1.163 [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. River Run ScreenConnect - update (default)
- Confirm the instance ID is a River Run ID first. Any other ID is unauthorized until proven otherwise.
- Then update from Control to the version listed under Minimum version to reach (or the latest available).
B. Finding does not apply - escalate false positive
- Not present, or this is only an unauthorized-remote-access finding and the ID is ours.
C. Cannot update - escalate to Security for suppression
- Authorized River Run instance that is still behind after the Control 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) =====
- ScreenConnect is River Run stack - do not treat it as unauthorized third-party software
- Check the ScreenConnect instance ID on the host (service command line: relay host + instance id)
- Authorized River Run IDs (our ScreenConnect - not unauthorized remote access):
- 8e1512c8736de3b9 - cloud-hosted
- fb310accf083cff0 - internally hosted ad-hoc sessions
- Then stop if the finding is only unauthorized remote access and the ID matches: escalate to Security as a false positive
- Any other instance ID: investigate - treat as unauthorized until proven otherwise
- If the ID is authorized and this is a version finding: still update
- Update ScreenConnect to the reported remediation target
- ScreenConnect/Control: update from Control server/cloud or deploy vendor MSI for the same build channel
- Verify version on affected hosts after update
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Museum of Wisconsin Art\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Email DNS - DNS Config Required
Vulnerability Remediation - Email DNS - DNS Config Required
Product/System: Email DNS - Mail authentication (SPF, DMARC, DKIM)
Affected Domains: 1
Finding summary:
Email authentication records are missing or incorrect for the listed domain(s) used for outbound email.
Confirm each domain is actually used for mail before changing DNS.
Publish or correct SPF, DMARC, and/or DKIM at the DNS provider.
Affected domain(s):
- wisconsinart.org
Quick-check each domain first.
Confirm the domain is used for outbound email (MX, Microsoft 365 accepted domains, known senders).
Then stop (escalate to Security as a false positive) if the domain is not used for mail, or SPF/DMARC/DKIM are already correct.
Include the domain list and reason.
Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Publish or correct DNS (default when the domain sends mail)
- After client discussion and sender inventory, publish or correct SPF, DMARC, and/or DKIM at the DNS provider for each listed domain, including authorized third-party and device senders.
B. Finding does not apply - escalate false positive
- Domain not used for mail, or records already correct. Document what you checked.
C. Accepted risk / client will not change DNS - escalate to Security
- Record client notification/acceptance in discussion notes to the client.
- These findings are assessed from public DNS, not ConnectSecure host scans - they cannot be suppressed in ConnectSecure. Security documents the accepted-risk exception.
- Client must accept or be notified; risk remains until records are corrected.
Client coordination - DISCUSS WITH THE CLIENT BEFORE ANY DNS CHANGE:
DNS changes for SPF, DMARC, or DKIM can cause legitimate client mail to be undelivered or quarantined.
Discuss timing and impact with the client first.
Confirm third-party senders and mail-capable devices (scanners/MFPs, fax-to-email, etc.) before tightening SPF or DMARC.
Do not publish or strengthen records until the client agrees.
===== TECHNICAL GUIDANCE (do this) =====
- Identify the DNS host / registrar for each domain (from ticket detail or Client Folder notes).
- Preferred access to the client's DNS host is delegated access to a River Run account.
- Before publishing or tightening SPF/DMARC/DKIM, inventory every system that sends as this domain:
- Primary mail platform (Microsoft 365 / Exchange, Google, etc.)
- Third parties that send on behalf of the domain (marketing, billing, CRM, ticketing, newsletters, payroll, etc.) - add SPF includes and enable DKIM when the vendor supports it
- Mail-capable devices (MFPs/scanners, fax-to-email, postage, alarm/notification appliances, LOB SMTP) - authorize in SPF or route through an approved relay
- Do not tighten SPF (-all) or DMARC policy until those senders are covered or intentionally retired
- Publish or correct SPF, DMARC, and/or DKIM per the missing records only after the client agrees and the sender inventory is covered.
- Preferred DMARC policy is p=quarantine. Use p=none only as a short monitor step if needed, then move to quarantine. Do not set p=reject unless the client asks for it.
- After change, verify public DNS shows the expected records; wait for TTL where needed
Scope: Email authentication (SPF, DMARC, DKIM) - DNS TXT/CNAME records at the domain's DNS provider.
IMPORTANT: First confirm each domain below is actually used for outbound email (MX records, Microsoft 365 accepted domains, marketing platforms, etc.). If a domain does not send mail, no remediation is needed for it - skip it.
Summary: 1 domain(s) flagged for DNS mail-authentication review.
=== wisconsinart.org ===
DNS hosting: GoDaddy (ns25.domaincontrol.com, ns26.domaincontrol.com). Publish SPF/DMARC/DKIM TXT records in this DNS provider for wisconsinart.org.
Issues:
- DMARC policy is weak (p=none).
- In the DNS hosting provider, open the existing DMARC TXT record at _dmarc.wisconsinart.org (host/name "_dmarc").
- Review aggregate reports (rua=) if configured and confirm legitimate mail passes SPF and/or DKIM alignment.
- Strengthen policy in stages when the client approves: p=none (monitor) → p=quarantine.
- Example interim record: v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@wisconsinart.org
Remediation: For each domain confirmed to send mail, work with the client's DNS provider to publish or correct the SPF, DMARC, and/or DKIM records needed to resolve the issues listed above, then verify with a public DNS lookup tool (for example MXToolbox or nslookup).
===== END TECHNICAL GUIDANCE =====
Tasks:
- DMARC should be p=quarantine. Review for scanners and/or 3rd party emailers like a web form before implementing. If not possible, note ticket and close.
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Museum of Wisconsin Art\Network Documentation\Vulnerability Scans\2026 - Q3
These email authentication findings are assessed from public DNS records, not ConnectSecure host scans. They cannot be suppressed in ConnectSecure.
Good evening Gina,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 9):
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.