Mixer Systems Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-02 | 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: Adobe Acrobat X Standard - English, Français, Deutsch Remediation Options: Update to version 3.1.32 or later; uninstall if not in use Target Machines: 10.15.20.85 (steved) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft SQL Server 2022 Setup (English) Remediation Options: Update to version 16.0.1190.2 or later; uninstall if not in use Target Machines: MSI-DT2025-UPS.int.mixersystems (shipping) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Java 8 Update 281 (64-bit) Remediation Options: Update to version 8.0.5030.1 or later; uninstall if not in use Target Machines: MIXER-ENG-7.int.mixersystems (labinoth) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Java 8 Update 291 Remediation Options: Update to version 8.0.5030.1 or later; uninstall if not in use Target Machines: MIXER-2017-10-B.int.mixersystems (mixer) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Java 8 Update 291 (64-bit) Remediation Options: Update to version 8.0.5030.1 or later; uninstall if not in use Target Machines: MIXER-2017-10-B.int.mixersystems (mixer) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 24.01 (x64 edition) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: MIXER-LT-MARKE.int.mixersystems (andyW) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 1.75 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top Ten vulnerabilities docx report - Ticket #1893425: Vulnerability Remediation - Windows 11 (all versions) - Updates 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 Nick to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
nickp@mixersystems.com
nickp@mixersystems.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Nick, 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 Nick, Following the quarterly vulnerability review for Mixer Systems, 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. Adobe Acrobat X Standard - English, Français, Deutsch Affected hosts: 10.15.20.85 (steved) - 10.15.20.85 What to do: Update Adobe Acrobat X Standard - English, Français, Deutsch 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. Microsoft SQL Server 2022 Setup (English) Affected hosts: MSI-DT2025-UPS.int.mixersystems (shipping) - 10.15.20.175 What to do: Update Microsoft SQL Server 2022 Setup (English) 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. Java 8 Update 281 (64-bit) Affected hosts: MIXER-ENG-7.int.mixersystems (labinoth) - 10.15.20.123 What to do: Update Java 8 Update 281 (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). 4. Java 8 Update 291 Affected hosts: MIXER-2017-10-B.int.mixersystems (mixer) - 10.15.20.134 What to do: Update Java 8 Update 291 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). 5. Java 8 Update 291 (64-bit) Affected hosts: MIXER-2017-10-B.int.mixersystems (mixer) - 10.15.20.134 What to do: Update Java 8 Update 291 (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). 6. 7-Zip 24.01 (x64 edition) Affected hosts: MIXER-LT-MARKE.int.mixersystems (andyW) - 10.15.20.224 What to do: Update 7-Zip 24.01 (x64 edition) 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: 13
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 (1208 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120240. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5121003. Apply the latest patch
- (1 end-of-life component notices omitted).
Affected Systems:
- 10.15.20.140 (steved) - 10.15.20.140 [1197 vulns]
- DESKTOP-7H3Q598.int.mixersystems (jhairston) - 192.168.1.5 [10.0.26100] [1046 vulns]
- MIXER-2018-02.int.mixersystems (darvins) - 10.15.20.135 [10.0.26100] [1046 vulns]
- 10.15.20.121 (steved) - 10.15.20.121 [1003 vulns]
- 10.15.20.232 (steved) - 10.15.20.232 [1002 vulns]
- MIXER-LTP-0124B.int.mixersystems (amandad) - 10.0.1.24 [10.0.26200] [859 vulns]
- 10.15.20.171 (steved) - 10.15.20.171 [671 vulns]
- 10.15.20.213 (steved) - 10.15.20.213 [671 vulns]
- MIXER-LT-0125B.int.mixersystems - 10.15.20.253 [10.0.26100] [671 vulns]
- MIXER-LTP-0124C.int.mixersystems (nickp) - 10.15.20.184 [10.0.26100] [671 vulns]
- 10.15.20.185 (steved) - 10.15.20.185 [572 vulns]
- 10.15.20.101 (steved) - 10.15.20.101 [565 vulns]
- 10.15.20.85 (steved) - 10.15.20.85 [565 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
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): ...\Mixer Systems\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Product/System: Windows 10 (all versions)
Affected Systems Count: 6
Finding summary:
Windows 10 (all versions) is missing required updates on the listed hosts.
Apply remaining quality/security updates for the current build via RMM or Windows Update.
Windows 10 is EOL. Do not force a Windows 11 upgrade from this ticket. After those updates, a Windows 11 / new workstation project is a Sales quote and vCIO conversation, then Security suppression of the current OS.
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 (1246 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120249. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted) (or the latest available).
Affected Systems:
- 10.15.20.159 (steved) - 10.15.20.159 [1247 vulns]
- MSI-SNELSON-21 (snelson) - 10.15.20.232 [10.0.19045] [913 vulns]
- MIXER-2017-10-B.int.mixersystems (mixer) - 10.15.20.134 [10.0.19045] [912 vulns]
- 10.15.20.119 (steved) - 10.15.20.119 [1 vulns]
- DESKTOP-BBFM0G4.int.mixersystems (shop) - 10.15.20.93 [10.0.26200] [1 vulns]
- SHOP9A.int.mixersystems (shop) - 10.15.20.112 [10.0.26100] [1 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
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
- Windows 10 is EOL: still apply any remaining quality/security updates first; for a Windows 11 / new workstation project, generate a quote (inform the client that you are doing so), contact vCIO so they can discuss it with the client, then escalate to Security for suppression of the current OS
===== 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): ...\Mixer Systems\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: 40
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 (88 more) are listed in the Client Folder report.
Affected Systems:
Sorry for the long host list below (40 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- ELEC24.int.mixersystems (jevans) - 10.15.20.197 [9.0.15] [315 vulns]
- MIXER-ENG-3.int.mixersystems (kevind) - 10.15.20.196 [9.0.16] [279 vulns]
- ELEC24.int.mixersystems (jevans) - 10.15.20.197 [8.0.26] [150 vulns]
- MIXER-ENG-3.int.mixersystems (kevind) - 10.15.20.196 [8.0.27] [130 vulns]
- ELEC24.int.mixersystems (jevans) - 10.15.20.197 [100 vulns]
- ELEC24.int.mixersystems (jevans) - 10.15.20.197 [8.0.10] [90 vulns]
- MIXER-ENG-3.int.mixersystems (kevind) - 10.15.20.196 [8.0.10] [90 vulns]
- MSI-DT2025-UPS.int.mixersystems (shipping) - 10.15.20.175 [8.0.26] [90 vulns]
- MIXER-ENG-3.int.mixersystems (kevind) - 10.15.20.196 [10.0.8] [76 vulns]
- MIXER-ENG-3.int.mixersystems (kevind) - 10.15.20.196 [68 vulns]
- MIXER-LT-0226B.int.mixersystems (carlo) - 10.15.20.183 [6.0.20] [48 vulns]
- 10.15.20.204 (steved) - 10.15.20.204 [3.1.11] [48 vulns]
- MIXER42.int.mixersystems (davidk) - 10.15.20.102 [3.1.11] [48 vulns]
- MIXER-ENG-10.int.mixersystems (kennethr) - 10.15.20.201 [3.1.11] [48 vulns]
- MSI-DT2025-07.int.mixersystems (jordanb) - 10.15.20.143 [3.1.11] [48 vulns]
- MSI-DT2025-UPS.int.mixersystems (shipping) - 10.15.20.175 [48 vulns]
- MSI-LT-0426A.int.mixersystems (fredb) - 192.168.0.39 [6.0.20] [24 vulns]
- MIXER-LT-0226B.int.mixersystems (carlo) - 10.15.20.183 [18 vulns]
- MSI-LT-0426A.int.mixersystems (fredb) - 192.168.0.39 [18 vulns]
- 10.15.20.85 (steved) - 10.15.20.85 [10.0.9] [18 vulns]
- 10.15.20.119 (steved) - 10.15.20.119 [5.0.17] [2 vulns]
- MIXER-ENG-3.int.mixersystems (kevind) - 10.15.20.196 [5.0.17] [2 vulns]
- MIXER-ENG-7.int.mixersystems (labinoth) - 10.15.20.123 [5.0.17] [2 vulns]
- SHOP9A.int.mixersystems (shop) - 10.15.20.112 [5.0.17] [2 vulns]
- 10.15.20.119 (steved) - 10.15.20.119 [6.0.36] [2 vulns]
- DESKTOP-BBFM0G4.int.mixersystems (shop) - 10.15.20.93 [6.0.36] [2 vulns]
- ELEC24.int.mixersystems (jevans) - 10.15.20.197 [6.0.36] [2 vulns]
- MIXER38.int.mixersystems (charliem) - 10.15.20.192 [6.0.36] [2 vulns]
- MIXER-ENG-3.int.mixersystems (kevind) - 10.15.20.196 [6.0.36] [2 vulns]
- MIXER-ENG-7.int.mixersystems (labinoth) - 10.15.20.123 [6.0.36] [2 vulns]
- SHOP9A.int.mixersystems (shop) - 10.15.20.112 [6.0.36] [2 vulns]
- 10.15.20.221 (steved) - 10.15.20.221 [3.1.32] [2 vulns]
- 10.15.20.85 (steved) - 10.15.20.85 [3.1.32] [2 vulns]
- 10.15.20.88 (steved) - 10.15.20.88 [3.1.32] [2 vulns]
- MIXER-ENG-3.int.mixersystems (kevind) - 10.15.20.196 [3.1.32] [2 vulns]
- MIXER-ENG-7.int.mixersystems (labinoth) - 10.15.20.123 [3.1.32] [2 vulns]
- MIXER-ENG-8.int.mixersystems (JohnO) - 10.15.20.149 [3.1.32] [2 vulns]
- MSI-ENG01.int.mixersystems (riverrun) - 10.15.20.17 [2 vulns]
- MIXER-ENG-8.int.mixersystems (JohnO) - 10.15.20.149 [1 vulns]
- 10.15.20.130 (steved) - 10.15.20.130 [1 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the redistributable/runtime is not present or is already at/above the minimum version to reach for that major version.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- .NET Framework and modern .NET (.NET 5+) are not interchangeable
- An app built on one major version is tied to that version - removing it will break the app.
- Update each runtime line via WU/vendor installer; uninstall only when unused and verified
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET Core 3.x: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 5: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 6: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 8 (LTS): update runtime to the reported target within the 8.x line (Windows Update or runtime installer)
- .NET 9 (non-LTS): update 9.x runtime via WU/vendor installer, or uninstall if unused
- .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): ...\Mixer Systems\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Acrobat X Standard - English, Français, Deutsch - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat X Standard - English, Français, Deutsch - Update Required - 3rd party application
Product/System: Adobe Acrobat X Standard - English, Français, Deutsch
Affected Systems Count: 1
Finding summary:
Adobe Acrobat X Standard - English, Français, Deutsch 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-2011-2462
https://nvd.nist.gov/vuln/detail/CVE-2011-2462
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (663 more) are listed in the Client Folder report.
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:
- 10.15.20.85 (steved) - 10.15.20.85 [665 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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): ...\Mixer Systems\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2022 Setup (English) - Update Required - 3rd party application
Vulnerability Remediation - Microsoft SQL Server 2022 Setup (English) - Update Required - 3rd party application
Product/System: Microsoft SQL Server 2022 Setup (English)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2022 Setup (English) is a database engine on the listed hosts.
Confirm the instance or cluster, then apply the matching engine update in a maintenance window with the DBA or app owner.
CVE references:
CVE-2026-54118
https://nvd.nist.gov/vuln/detail/CVE-2026-54118
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54118
Additional CVEs (122 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 16.0.1190.2 (or the latest available).
Affected Systems:
- MSI-DT2025-UPS.int.mixersystems (shipping) - 10.15.20.175 [123 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Mixer Systems\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Java 8 Update 281 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Java 8 Update 281 (64-bit) - Update Required - 3rd party application
Product/System: Java 8 Update 281 (64-bit)
Affected Systems Count: 1
Finding summary:
Java 8 Update 281 (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 (28 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:
- MIXER-ENG-7.int.mixersystems (labinoth) - 10.15.20.123 [29 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): ...\Mixer Systems\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Java 8 Update 291 - Update Required - 3rd party application
Vulnerability Remediation - Java 8 Update 291 - Update Required - 3rd party application
Product/System: Java 8 Update 291
Affected Systems Count: 1
Finding summary:
Java 8 Update 291 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 (26 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:
- MIXER-2017-10-B.int.mixersystems (mixer) - 10.15.20.134 [27 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): ...\Mixer Systems\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Java 8 Update 291 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Java 8 Update 291 (64-bit) - Update Required - 3rd party application
Product/System: Java 8 Update 291 (64-bit)
Affected Systems Count: 1
Finding summary:
Java 8 Update 291 (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 (26 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:
- MIXER-2017-10-B.int.mixersystems (mixer) - 10.15.20.134 [27 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): ...\Mixer Systems\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 24.01 (x64 edition) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 24.01 (x64 edition) - Update Required - 3rd party application
Product/System: 7-Zip 24.01 (x64 edition)
Affected Systems Count: 1
Finding summary:
7-Zip 24.01 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- MIXER-LT-MARKE.int.mixersystems (andyW) - 10.15.20.224 [15 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 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Mixer Systems\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):
- mixersystems.com
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.
=== mixersystems.com ===
DNS hosting: ns1.tigertech.net, ns2.tigertech.biz, ns3.tigertech.org. Confirm this is the DNS provider where TXT records for mixersystems.com are managed.
Issues:
- DMARC policy is weak (p=none).
- In the DNS hosting provider, open the existing DMARC TXT record at _dmarc.mixersystems.com (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@mixersystems.com
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 =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Mixer Systems\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 Nick,
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.