Precision Rail and Mfg, Inc. Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-12 | Presenter: Chris Knospe | Export set: 10 in export (Top 10) | Client type: RMIT/CMIT
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Windows 10 (all versions) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: TERM-ElecAssy2 (User), PRAM-WS-0922-B.aaase (TylerWurtinger), TWEBBER.aaase (Pete Thorson), PRAM-WS-0922-A.aaase (KateRath), PRAM-WS-0322-B.aaase (Robert Woods), DBYKLUM (AnthonyMilewski), PRAM-WS-1222-A.aaase (scottstevens), PRAM-WS-0322-A.aaase (TylerWurtinger), m-balcer.aaase (JulieKupper), PRAM-MOLEARY.aaase (RyanFlitsch), HP-05-2023C.aaase (BobLetterle), HP-05-2023A.aaase (KevinKonieczka), DESKTOP-BVTQT35.aaase (Jim Braatz), PRAM-WS-0522-A.aaase (JoshuaStockton), Dell-11-2021A.aaase (shipping), President-CFO.aaase (Dean Cimpl), CMM-2GO4QMP.aaase (Steve Mosley), HP-Z2-03-20A.aaase (cmm), HP-Z2-03-20B.aaase (cmm), WBOYLE-2021.aaase (Wayne Boyle), HP-05-2023B.aaase (TimMurphy), PRAM-WS-0622-B.aaase Estimated Time of Remediation: 4 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Windows 11 (all versions) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: HP-11-2024.aaase (kevin mazur), PRAM-WS-0125-B.aaase (AntoinetteLingford), PRAM-WS-0825-A.aaase (vincentherff), PRAM-WS-0125-A.aaase (Brianhofmann), PRAM-WS-0125-C.aaase (SLTraining), Z2-06-2024.aaase, HP-Mini-04-2024.aaase (wirelessdnc), HP-12-2023A.aaase (marciacollins) Estimated Time of Remediation: 0 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft .NET (all versions) Remediation Options: Update to version 8.0.31 or later; uninstall if not in use Target Machines: PRAM-VAULT01.aaase (riverrun), HP-Z2-03-20A.aaase (cmm), PRAM-VAULT01.aaase (riverrun), PRAM-VAULT01.aaase (riverrun), HP-Z2-03-20A.aaase (cmm), PRMEngineering (Joshua), Z2-06-2024.aaase, WBOYLE-2021.aaase (Wayne Boyle), HP-Z2-03-20B.aaase (cmm), PRAM-WS-0126B.aaase (robertbornheimer), HP-Z2-03-20A.aaase (cmm), TWEBBER.aaase (Pete Thorson), TWEBBER.aaase (Pete Thorson), Dell-11-2021A.aaase (shipping), PRAM-WS-0922-A.aaase (KateRath), TWEBBER.aaase (Pete Thorson) Estimated Time of Remediation: 0 hours Remediation Method: Deploy the matching runtime installer via RMM. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft 365 Apps for business - en-us Remediation Options: Update to the current version; uninstall if not in use Target Machines: HP-05-2023C.aaase (BobLetterle), HP-Mini-04-2024.aaase (wirelessdnc), HP-05-2023A.aaase (KevinKonieczka), HP-05-2023B.aaase (TimMurphy) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat X Pro - English, Français, Deutsch Remediation Options: Update to version 3.1.32 or later; uninstall if not in use Target Machines: DBYKLUM (AnthonyMilewski), TWEBBER.aaase (Pete Thorson) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: FortiClient VPN Remediation Options: Update to version 7.4.5 or later; uninstall if not in use Target Machines: PRAM-WS-0622-A.aaase, HP-12-2023A.aaase (marciacollins), HP-05-2023B.aaase (TimMurphy), HP-05-2023A.aaase (KevinKonieczka), DESKTOP-BVTQT35.aaase (Jim Braatz), HP-05-2023C.aaase (BobLetterle), m-balcer.aaase (JulieKupper), HP-11-2024.aaase (kevin mazur), PRAM-WS-0125-A.aaase (Brianhofmann), DESKTOP-7Q3MCHP (Owner) Estimated Time of Remediation: 2 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Google Chrome Remediation Options: Update to version 155.0.8059.40 or later; uninstall if not in use Target Machines: CMM-2GO4QMP.aaase (Steve Mosley), PRAM-WS-0322-B.aaase (Robert Woods), HP-05-2023B.aaase (TimMurphy), DBYKLUM (AnthonyMilewski), Dell-11-2021A.aaase (shipping), PRAM-WS-0825-A.aaase (vincentherff), PRAM-VEEAM (admin), HP-05-2023C.aaase (BobLetterle) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Wireshark 4.6.6 x64 Remediation Options: Update to version 4.6.9 or later; uninstall if not in use Target Machines: PRAM-RDS01.aaase (term-b) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Autodesk AutoCAD Performance Feedback Tool Remediation Options: Update to version 2024.24.3.610 or later; uninstall if not in use Target Machines: PRAM-MOLEARY.aaase (RyanFlitsch), PRAM-WS-0622-A.aaase, Z2-06-2024.aaase, PRMEngineering (Joshua), DESKTOP-BVTQT35.aaase (Jim Braatz) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Defender Remediation Options: Update to version 4.18.26060.3008 or later; uninstall if not in use Target Machines: CMM-2GO4QMP.aaase (Steve Mosley), TERM-ElecAssy2 (User) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 9 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 - 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 Dean to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
dcimpl@precisionrailandmfg.com
dcimpl@precisionrailandmfg.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Dean, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top Ten): Open Top Ten report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report – classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0–1.0, with 1.0 being most critical). • All Vulnerabilities Report – a comprehensive list of all detected vulnerabilities (internal and external), from critical to low severity. • Executive Summary Report – a high-level overview of your security posture and network information. • External Scan – detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report – vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: No remediation will begin without your approval. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Chris Knospe
2026 Q4 Remaining remediations
Good evening Dean, Following the quarterly vulnerability review for Precision Rail and Mfg, Inc., there are no remaining remediations to report. Sincerely, Chris Knospe
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: 22
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-2022-21907
https://nvd.nist.gov/vuln/detail/CVE-2022-21907
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-21907
Additional CVEs (3691 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129238
- Apply Windows Update KB5122878. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5122878. Apply the latest patch
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (22 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- TERM-ElecAssy2 (User) - 10.0.60.70 [10.0.17763] [3546 vulns]
- PRAM-WS-0922-B.aaase (TylerWurtinger) - 10.0.60.98 [10.0.19044] [2755 vulns]
- TWEBBER.aaase (Pete Thorson) - 10.0.60.90 [10.0.19045] [1474 vulns]
- PRAM-WS-0922-A.aaase (KateRath) - 10.0.60.78 [10.0.19045] [1474 vulns]
- PRAM-WS-0322-B.aaase (Robert Woods) - 10.0.60.65 [10.0.19045] [1474 vulns]
- DBYKLUM (AnthonyMilewski) - 10.0.60.104 [10.0.19045] [1474 vulns]
- PRAM-WS-1222-A.aaase (scottstevens) - 10.0.60.107 [10.0.19045] [1474 vulns]
- PRAM-WS-0322-A.aaase (TylerWurtinger) - 10.0.60.116 [10.0.19045] [1474 vulns]
- m-balcer.aaase (JulieKupper) - 192.168.0.24 [10.0.19045] [1474 vulns]
- PRAM-MOLEARY.aaase (RyanFlitsch) - 10.0.60.77 [10.0.19045] [1473 vulns]
- HP-05-2023C.aaase (BobLetterle) - 10.0.0.128 [10.0.19045] [1473 vulns]
- HP-05-2023A.aaase (KevinKonieczka) - 10.0.60.100 [10.0.19045] [1473 vulns]
- DESKTOP-BVTQT35.aaase (Jim Braatz) - 10.0.60.101 [10.0.19045] [1473 vulns]
- PRAM-WS-0522-A.aaase (JoshuaStockton) - 10.0.60.105 [10.0.19045] [1473 vulns]
- Dell-11-2021A.aaase (shipping) - 10.0.60.108 [10.0.19045] [1473 vulns]
- President-CFO.aaase (Dean Cimpl) - 10.0.60.109 [10.0.19045] [1473 vulns]
- CMM-2GO4QMP.aaase (Steve Mosley) - 10.0.60.40 [10.0.19045] [1473 vulns]
- HP-Z2-03-20A.aaase (cmm) - 10.0.60.43 [10.0.19045] [1473 vulns]
- HP-Z2-03-20B.aaase (cmm) - 10.0.60.62 [10.0.19045] [1473 vulns]
- WBOYLE-2021.aaase (Wayne Boyle) - 10.0.60.120 [10.0.19045] [1473 vulns]
- HP-05-2023B.aaase (TimMurphy) - 192.168.1.134 [10.0.19045] [1473 vulns]
- PRAM-WS-0622-B.aaase - 10.0.60.93 [10.0.19044] [1472 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
- 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): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
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: 8
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-2025-50165
https://nvd.nist.gov/vuln/detail/CVE-2025-50165
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-50165
Additional CVEs (1944 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129195
- Apply Windows Update KB5129242. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted) (or the latest available).
Affected Systems:
- HP-11-2024.aaase (kevin mazur) - 10.0.60.3 [10.0.26100] [1917 vulns]
- PRAM-WS-0125-B.aaase (AntoinetteLingford) - 10.0.60.34 [10.0.26100] [1658 vulns]
- PRAM-WS-0825-A.aaase (vincentherff) - 10.0.60.47 [10.0.26100] [1658 vulns]
- PRAM-WS-0125-A.aaase (Brianhofmann) - 10.0.60.60 [10.0.26100] [1658 vulns]
- PRAM-WS-0125-C.aaase (SLTraining) - 10.0.60.87 [10.0.26100] [1658 vulns]
- Z2-06-2024.aaase - 10.0.60.212 [10.0.22631] [1226 vulns]
- HP-Mini-04-2024.aaase (wirelessdnc) - 10.0.60.48 [10.0.22631] [1226 vulns]
- HP-12-2023A.aaase (marciacollins) - 192.168.20.171 [10.0.22631] [706 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): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
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: 16
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 (91 more) are listed in the Client Folder report.
Affected Systems:
- PRAM-VAULT01.aaase (riverrun) - 10.0.10.17 [9.0.9] [138 vulns]
- HP-Z2-03-20A.aaase (cmm) - 10.0.60.43 [9.0.13] [117 vulns]
- PRAM-VAULT01.aaase (riverrun) - 10.0.10.17 [72 vulns]
- PRAM-VAULT01.aaase (riverrun) - 10.0.10.17 [10.0.17763] [50 vulns]
- HP-Z2-03-20A.aaase (cmm) - 10.0.60.43 [10.0.19045] [40 vulns]
- PRMEngineering (Joshua) - 10.0.60.15 [34 vulns]
- Z2-06-2024.aaase - 10.0.60.212 [30 vulns]
- WBOYLE-2021.aaase (Wayne Boyle) - 10.0.60.120 [18 vulns]
- HP-Z2-03-20B.aaase (cmm) - 10.0.60.62 [18 vulns]
- PRAM-WS-0126B.aaase (robertbornheimer) - 10.0.60.57 [18 vulns]
- HP-Z2-03-20A.aaase (cmm) - 10.0.60.43 [18 vulns]
- TWEBBER.aaase (Pete Thorson) - 10.0.60.90 [10.0.11] [15 vulns]
- TWEBBER.aaase (Pete Thorson) - 10.0.60.90 [10.0.19045] [5 vulns]
- Dell-11-2021A.aaase (shipping) - 10.0.60.108 [4 vulns]
- PRAM-WS-0922-A.aaase (KateRath) - 10.0.60.78 [4 vulns]
- TWEBBER.aaase (Pete Thorson) - 10.0.60.90 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the redistributable/runtime is not present or is already at/above the minimum version to reach for that major version.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- .NET Framework and modern .NET (.NET 5+) are not interchangeable
- An app built on one major version is tied to that version - removing it will break the app.
- Update each runtime line via WU/vendor installer; uninstall only when unused and verified
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET 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): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Update Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Update Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 4
Finding summary:
Microsoft 365 Apps for business - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2024-21413
https://nvd.nist.gov/vuln/detail/CVE-2024-21413
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21413
Additional CVEs (426 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5122878. Apply the latest patch.
Affected Systems:
- HP-05-2023C.aaase (BobLetterle) - 10.0.0.128 [428 vulns]
- HP-Mini-04-2024.aaase (wirelessdnc) - 10.0.60.48 [411 vulns]
- HP-05-2023A.aaase (KevinKonieczka) - 10.0.60.100 [315 vulns]
- HP-05-2023B.aaase (TimMurphy) - 192.168.1.134 [193 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): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Adobe Acrobat X Pro - English, Français, Deutsch - Update Required
Vulnerability Remediation - Adobe Acrobat X Pro - English, Français, Deutsch - Update Required
Product/System: Adobe Acrobat X Pro - English, Français, Deutsch
Affected Systems Count: 2
Finding summary:
Adobe Acrobat X Pro - 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-2017-11293
https://nvd.nist.gov/vuln/detail/CVE-2017-11293
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (68 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:
- DBYKLUM (AnthonyMilewski) - 10.0.60.104 [72 vulns]
- TWEBBER.aaase (Pete Thorson) - 10.0.60.90 [71 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm Acrobat Pro vs Adobe Reader (and 32 vs 64) on each host before choosing an installer
- Update to the reported remediation target
- RMM/automated patching when deployed
- Versions 20.x and 21.x are EOL - full upgrade to a supported track, not a security patch on 20/21
- Backstage (CMD/PS): deploy matching Acrobat installer/package (Admin Console when enterprise)
- Live user session only if needed: Help > Check for Updates
- Verify version after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - FortiClient VPN - Update Required
Vulnerability Remediation - FortiClient VPN - Update Required
Product/System: FortiClient VPN
Affected Systems Count: 10
Finding summary:
FortiClient VPN is a VPN client on the listed hosts.
If the site has a FortiGate / Fortinet firewall, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it. Use the vendor installer from support.fortinet.com. Automated / RMM updates have failed for FortiClient VPN in the past.
CVE references:
CVE-2024-3661
https://nvd.nist.gov/vuln/detail/CVE-2024-3661
Vendor security center:
https://fortiguard.fortinet.com/psirt
Additional CVEs (23 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.4.5 (or the latest available)
- Update to version 7.2.14 (or the latest available)
- Update to version 7.4.3.4726 (or the latest available).
Affected Systems:
- PRAM-WS-0622-A.aaase - 10.0.60.28 [19 vulns]
- HP-12-2023A.aaase (marciacollins) - 192.168.20.171 [16 vulns]
- HP-05-2023B.aaase (TimMurphy) - 192.168.1.134 [15 vulns]
- HP-05-2023A.aaase (KevinKonieczka) - 10.0.60.100 [15 vulns]
- DESKTOP-BVTQT35.aaase (Jim Braatz) - 10.0.60.101 [15 vulns]
- HP-05-2023C.aaase (BobLetterle) - 10.0.0.128 [10 vulns]
- m-balcer.aaase (JulieKupper) - 192.168.0.24 [10 vulns]
- HP-11-2024.aaase (kevin mazur) - 10.0.60.3 [8 vulns]
- PRAM-WS-0125-A.aaase (Brianhofmann) - 10.0.60.60 [7 vulns]
- DESKTOP-7Q3MCHP (Owner) - 192.168.4.72 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has a FortiGate / Fortinet firewall: download from support.fortinet.com and run the vendor installer to the version listed under Minimum version to reach (or the latest available). Do not rely on RMM for FortiClient VPN.
- Coordinate the FortiClient version with site FortiGate firmware before upgrading.
- If the site does not have a FortiGate / Fortinet firewall: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the update path.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- FortiClient VPN: manual vendor installer recommended
This VPN is expected if the site has a FortiGate / Fortinet firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it.
- Automated / RMM updates have failed for FortiClient VPN in the past - do not rely on them until a better path exists
- Do not use winget or automated patching for this product
- Download updated installer from support.fortinet.com
- Transfer via ScreenConnect file transfer
- CMD console (SYSTEM OK): FortiClientVPNSetup_x.x.x.exe /quiet /norestart
- Coordinate version with site FortiGate firmware before upgrading
- Verify version after install
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Google Chrome - Update Required
Vulnerability Remediation - Google Chrome - Update Required
Product/System: Google Chrome
Affected Systems Count: 8
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-106227
https://nvd.nist.gov/vuln/detail/CVE-2026-106227
Vendor security center:
https://chromereleases.googleblog.com/
Additional CVEs (257 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 155.0.8059.40 (or the latest available).
Affected Systems:
- CMM-2GO4QMP.aaase (Steve Mosley) - 10.0.60.40 [247 vulns]
- PRAM-WS-0322-B.aaase (Robert Woods) - 10.0.60.65 [247 vulns]
- HP-05-2023B.aaase (TimMurphy) - 192.168.1.134 [247 vulns]
- DBYKLUM (AnthonyMilewski) - 10.0.60.104 [247 vulns]
- Dell-11-2021A.aaase (shipping) - 10.0.60.108 [247 vulns]
- PRAM-WS-0825-A.aaase (vincentherff) - 10.0.60.47 [130 vulns]
- PRAM-VEEAM (admin) - 10.0.60.49 [130 vulns]
- HP-05-2023C.aaase (BobLetterle) - 10.0.0.128 [60 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- 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): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Wireshark 4.6.6 x64 - Update Required
Vulnerability Remediation - Wireshark 4.6.6 x64 - Update Required
Product/System: Wireshark 4.6.6 x64
Affected Systems Count: 1
Finding summary:
Wireshark 4.6.6 x64 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-76879
https://nvd.nist.gov/vuln/detail/CVE-2026-76879
Vendor security center:
https://www.wireshark.org/security/
Additional CVEs (57 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.6.9 (or the latest available).
Affected Systems:
- PRAM-RDS01.aaase (term-b) - 10.0.10.180 [58 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): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Autodesk AutoCAD Performance Feedback Tool - Update Required
Vulnerability Remediation - Autodesk AutoCAD Performance Feedback Tool - Update Required
Product/System: Autodesk AutoCAD Performance Feedback Tool
Affected Systems Count: 5
Finding summary:
Autodesk AutoCAD Performance Feedback Tool 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-25795
https://nvd.nist.gov/vuln/detail/CVE-2022-25795
Vendor security center:
https://www.autodesk.com/trust/security-advisories
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 2024.24.3.610 (or the latest available)
- Update to version 15.3.0.5 (or the latest available). Update to version 2024.24.3.610 (or the latest available).
Affected Systems:
- PRAM-MOLEARY.aaase (RyanFlitsch) - 10.0.60.77 [7 vulns]
- PRAM-WS-0622-A.aaase - 10.0.60.28 [7 vulns]
- Z2-06-2024.aaase - 10.0.60.212 [7 vulns]
- PRMEngineering (Joshua) - 10.0.60.15 [7 vulns]
- DESKTOP-BVTQT35.aaase (Jim Braatz) - 10.0.60.101 [7 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Defender - Update Required
Vulnerability Remediation - Microsoft Defender - Update Required
Product/System: Microsoft Defender
Affected Systems Count: 2
Finding summary:
Microsoft Defender is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2023-36422
https://nvd.nist.gov/vuln/detail/CVE-2023-36422
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36422
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.18.26060.3008 (or the latest available).
Affected Systems:
- CMM-2GO4QMP.aaase (Steve Mosley) - 10.0.60.40 [5 vulns]
- TERM-ElecAssy2 (User) - 10.0.60.70 [5 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Check Windows Security on each host: is another EDR/AV active (SentinelOne, Huntress, Webroot, Bitdefender, or similar)?
- If yes and Defender real-time protection is off: that is expected. This finding is a Defender version, not the live AV
- Do not turn Defender real-time protection back on next to that EDR
- If Defender is still the AV, or the platform/service is still running: update platform/signatures via Windows Update or Defender management policy
- Check RMM patch status if patch management is deployed
- Confirm engine/platform version after update
- Then stop if:
- Another EDR is healthy and Defender RTP is off (version/signature age only): notify the client, record discussion notes, escalate to Security for suppression
- Update failed because Defender is fully disabled: same path - the EDR is the control; escalate to Security for suppression
- If the CVE is in a Defender driver or service that is still loaded: update the Defender platform anyway
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Precision Rail and Mfg, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Dean,
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 – a comprehensive list of all detected vulnerabilities (internal and external), from critical to low severity.
• Executive Summary Report – a high-level overview of your security posture and network information.
• External Scan – detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report – vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: No remediation will begin without your approval. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Chris Knospe
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.