E-S Plastic Products LLC Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-17 | Presenter: Andrew Harkins | Export set: 8 in export (Top 8) | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): No items are selected for this quote. Total Estimated Time: 0 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 8 vulnerabilities docx report - Ticket #1907263: Vulnerability Remediation - Windows 11 (all versions) - Updates Required - Ticket #1907268: Vulnerability Remediation - Windows Server 2025 - Updates Required - Ticket #1907269: Vulnerability Remediation - Windows Server 2019 - Updates Required - Ticket #1907270: Vulnerability Remediation - Windows Server 2022 - Updates Required - Ticket #1907264: Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required - Ticket #1907265: Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade) - Ticket #1907266: Vulnerability Remediation - Windows Server 2008 R2 - Updates Required - Ticket #1907267: Vulnerability Remediation - Microsoft Teams - Application Update Required - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with Kathy to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
kbower@esplastics.com
kbower@esplastics.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Kathy, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 8): Open Top 8 report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Andrew Harkins
2026 Q4 Remaining remediations
Good evening Kathy, Following the quarterly vulnerability review for E-S Plastic Products LLC, there are no remaining remediations to report. Sincerely, Andrew Harkins
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: 45
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-21298
https://nvd.nist.gov/vuln/detail/CVE-2025-21298
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298
Additional CVEs (3862 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5066793. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5127648. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5127648. Apply the latest patch. Upgrade to supported Operating System is recommended
- (3 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (45 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- 192.168.20.74 [2893 vulns]
- 192.168.20.60 [2820 vulns]
- ESP-D-012201 (jhampton) - 192.168.20.147 [10.0.26100] [2668 vulns]
- ESP-D-052925 - 192.168.20.133 [10.0.26100] [2668 vulns]
- ESP-D-082503 - 192.168.20.71 [10.0.26100] [2668 vulns]
- WF-SUPERVISORS-NEW - 192.168.20.70 [10.0.26100] [2668 vulns]
- ESP-111822-2 - 192.168.20.72 [10.0.26100] [2668 vulns]
- ESP-0207233 - 192.168.20.78 [10.0.26100] [2668 vulns]
- ESP-MAINTENANCE-01 - 192.168.20.91 [10.0.26100] [2668 vulns]
- ESP-D-052301 (sriemert) - 192.168.30.80 [10.0.26100] [2668 vulns]
- ESP-TimeClock-SV (timeclocksv) - 192.168.30.81 [10.0.26100] [2668 vulns]
- ESP-L-0425B (anemchek) - 192.168.30.87 [10.0.26100] [2668 vulns]
- ESP-D-102001 (qualitysv) - 192.168.30.90 [10.0.26100] [2668 vulns]
- SV-LT-0425 (rrobinson) - 192.168.30.92 [10.0.26100] [2668 vulns]
- ESP-0322-B (twood) - 192.168.7.181 [10.0.26100] [2668 vulns]
- 192.168.20.120 [2668 vulns]
- WF-CUSTOMERSERVICE - 192.168.20.113 [10.0.26100] [2668 vulns]
- WF-WHOUSE-2025 - 192.168.20.109 [10.0.26100] [2668 vulns]
- 192.168.20.68 [2362 vulns]
- 192.168.20.108 [2360 vulns]
- 192.168.20.79 [2195 vulns]
- 192.168.20.87 [2195 vulns]
- ES-Conf-2210 - 192.168.30.107 [10.0.26200] [2195 vulns]
- ESP-120822 (mhackman) - 192.168.20.83 [10.0.26100] [1633 vulns]
- ESP-111822 (ccampbell) - 192.168.20.98 [10.0.26100] [1633 vulns]
- ESP-D-082501 - 192.168.20.119 [10.0.26100] [1633 vulns]
- ESP-D-122201 - 192.168.20.141 [10.0.26200] [1631 vulns]
- ESP-L-032101 - 192.168.20.158 [10.0.26200] [1631 vulns]
- ESP-DT-0724A - 192.168.20.163 [10.0.26200] [1631 vulns]
- WF-M720T-2-2019 - 192.168.20.67 [10.0.26200] [1631 vulns]
- Desktop-16NP - 192.168.20.69 [10.0.26200] [1631 vulns]
- ESP-123124-B - 192.168.20.95 [10.0.26200] [1631 vulns]
- ESP-D-072101 (Ckrukowski) - 192.168.20.96 [10.0.26200] [1631 vulns]
- ESP-D-092501 - 192.168.30.116 [10.0.26200] [1631 vulns]
- ESP-S-Qual-2211 (qasv) - 192.168.30.118 [10.0.26200] [1631 vulns]
- ESP-D-121907 (shopfloor) - 192.168.30.121 [10.0.26200] [1631 vulns]
- ESP-L-022223 (cverran) - 192.168.30.124 [10.0.26200] [1631 vulns]
- CLINTS-DESKTOP - 192.168.30.74 [10.0.26200] [1631 vulns]
- ESP-L-0425A (dsparks) - 192.168.30.84 [10.0.26200] [1631 vulns]
- ESP-0324-A - 192.168.30.87 [10.0.26200] [1631 vulns]
- ESP-DT-0824B (danderson) - 192.168.30.95 [10.0.26200] [1631 vulns]
- ESP-D-052302 (tboesch) - 192.168.30.97 [10.0.26200] [1631 vulns]
- ESP-D-082502 - 192.168.20.127 [10.0.26200] [1631 vulns]
- ESP-101123 (kathyadmin) - 192.168.1.167 [10.0.22621] [1127 vulns]
- ESP-L-103024 - 192.168.20.169 [10.0.26200] [1008 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): ...\E-S Plastic Products, LLC - Waterford Division\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows Server 2025 - Updates Required
Vulnerability Remediation - Windows Server 2025 - Updates Required
Product/System: Windows Server 2025
Affected Systems Count: 6
Finding summary:
Windows Server 2025 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 (2616 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5126646 (or the latest available).
Affected Systems:
- ESP-L-122201 - 192.168.20.160 [10.0] [2617 vulns]
- ESP-123124-A - 192.168.20.137 [10.0] [2617 vulns]
- WF-M720T-2-2019 - 192.168.20.126 [Windows] [2617 vulns]
- ESP-D-062001 - 192.168.20.64 [10.0] [2617 vulns]
- ESP-D-052303 - 192.168.20.81 [10.0] [2617 vulns]
- ESP-020723 - 192.168.20.103 [10.0] [2617 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): ...\E-S Plastic Products, LLC - Waterford Division\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows Server 2019 - Updates Required
Vulnerability Remediation - Windows Server 2019 - Updates Required
Product/System: Windows Server 2019
Affected Systems Count: 3
Finding summary:
Windows Server 2019 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-47981
https://nvd.nist.gov/vuln/detail/CVE-2025-47981
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-47981
Additional CVEs (2685 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5126651 (or the latest available).
Affected Systems:
- 192.168.20.24 [2686 vulns]
- ESP-REPORTING - 192.168.20.231 [10.0.17763] [874 vulns]
- ESP-TRAINING - 192.168.20.232 [10.0.17763] [874 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): ...\E-S Plastic Products, LLC - Waterford Division\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows Server 2022 - Updates Required
Vulnerability Remediation - Windows Server 2022 - Updates Required
Product/System: Windows Server 2022
Affected Systems Count: 2
Finding summary:
Windows Server 2022 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 (2454 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5126655 (or the latest available).
Affected Systems:
- 192.168.20.30 [2439 vulns]
- ESP-DC2 - 192.168.20.40 [10.0.20348] [953 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): ...\E-S Plastic Products, LLC - Waterford Division\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 11
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-2025-53766
https://nvd.nist.gov/vuln/detail/CVE-2025-53766
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53766
Additional CVEs (460 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5127648. Apply the latest patch. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted).
Affected Systems:
- SV-LT-0425 (rrobinson) - 192.168.30.92 [461 vulns]
- WF-WHOUSE-2025 - 192.168.20.109 [298 vulns]
- WF-CUSTOMERSERVICE - 192.168.20.113 [298 vulns]
- WF-SUPERVISORS-NEW - 192.168.20.70 [298 vulns]
- ESP-D-082503 - 192.168.20.71 [298 vulns]
- 192.168.20.79 [298 vulns]
- 192.168.20.87 [298 vulns]
- ESP-D-092501 - 192.168.30.116 [298 vulns]
- ESP-L-0425B (anemchek) - 192.168.30.87 [298 vulns]
- ESP-DT-0824B (danderson) - 192.168.30.95 [298 vulns]
- Desktop-16NP - 192.168.20.69 [132 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) =====
- 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): ...\E-S Plastic Products, LLC - Waterford Division\Network Documentation\Vulnerability Scans\2026 - Q4
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: 1
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-2025-21298
https://nvd.nist.gov/vuln/detail/CVE-2025-21298
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298
Additional CVEs (2956 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5126657
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- 192.168.20.131 [2958 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): ...\E-S Plastic Products, LLC - Waterford Division\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows Server 2008 R2 - Updates Required
Vulnerability Remediation - Windows Server 2008 R2 - Updates Required
Product/System: Windows Server 2008 R2
Affected Systems Count: 1
Finding summary:
Windows Server 2008 R2 needs an infrastructure change on the listed hosts (upgrade, replace, or migrate).
When the fix needs a new server, OS, or workstation: generate a quote (inform the client that you are doing so), then contact vCIO.
Plan upgrade/retire with client approval. Coordinate maintenance windows.
Last browsers these hosts can run: Google Chrome 109.0.5414.120, Microsoft Edge 109.0.1518.78, Mozilla Firefox ESR 115 (latest 115.x). An OS upgrade is required to install a current browser.
CVE references:
CVE-2019-0708
https://nvd.nist.gov/vuln/detail/CVE-2019-0708
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0708
Additional CVEs (1988 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5037800
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- VISIONSCOPE - 192.168.20.92 [6.1] [2000 vulns] - OS upgrade required to update browsers
Quick-check each host first.
Confirm the OS build/SKU or migration scope matches this finding.
Even for EOL products, check whether a newer final build exists and apply it if the host is behind.
Then stop (escalate to Security as a false positive) if the host is already on a supported platform or is not present.
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. Complete the infrastructure remediation (default when approved)
- Upgrade, replace, or migrate per Technical guidance and client-approved plan.
- Even when the OS/software is EOL, check whether a newer final build still exists and apply the latest available first.
- When new servers, OS licenses, workstations, or similar are required: 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 asset.
B. Asset not needed - decommission
- Only if the host/service should not exist.
C. Keeping EOL / deferred - notify the client, then escalate to Security for suppression
- After confirming the host is on the latest available build for that EOL product (or no further update exists), notify the client of residual risk, record discussion notes to the client, then escalate to Security for suppression.
- Do not request suppression until latest-available was checked and the client was notified.
- 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 project scope, timing, and cutover with the client. If keeping EOL, notify the client before Security suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply the latest available updates for this OS if any exist (EOL releases often have none)
- Create a Sales quote for new hardware or an OS upgrade to a supported release - inform the client that you are doing so
- Contact vCIO so they can discuss the quote with the client
- Escalate to Security for suppression of the current host. Remediation occurs when the old device is retired, or when the purchased software/OS/license update is applied.
- Last browsers this OS can run (a newer browser needs an OS upgrade):
- Google Chrome 109.0.5414.120 - Chrome 110 and later will not install
- Microsoft Edge 109.0.1518.78 - Edge 110 and later will not install
- Mozilla Firefox ESR 115 - install the latest 115.x (115.43.0 as of Oct 13, 2026). Firefox 116 and later will not install
- If a host is already at those versions, stop browser patching. An OS upgrade is required.
===== 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): ...\E-S Plastic Products, LLC - Waterford Division\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 4
Finding summary:
Microsoft Teams is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2023-4863
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26260.1701.5139.3736 (or the latest available)
- Update to version 1.08.00.9760 (or the latest available). Update to version 26260.1701.5139.3736 (or the latest available).
Affected Systems:
- ESP-TimeClock-SV (timeclocksv) - 192.168.30.81 [7 vulns]
- ESP-D-052301 (sriemert) - 192.168.30.80 [7 vulns]
- ESP-101123 (kathyadmin) - 192.168.1.167 [4 vulns]
- WF-CUSTOMERSERVICE - 192.168.20.113 [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. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm flagged Teams version - Classic is not always the source
- Classic Teams is sometimes a per-user install
- A user who has not logged into this workstation in a while, or is not the primary user, can still have Classic leftover
- Run the RMM Teams Classic cleanup script for those leftover per-user installs
- Classic/duplicate suspected: R-Security - Teams Classic Cleanup Remediation (Scripts > RR Custom > RR Custom - R-Security Remediation > R-Security - Teams Classic Cleanup Remediation)
- Current Teams behind: automated patching/RMM first
- Live user session only if needed: three-dot menu > Settings > About Teams
- Backstage (CMD/PS): RMM script / installer only - not the Teams UI
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\E-S Plastic Products, LLC - Waterford Division\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Kathy,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 8):
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,
Andrew Harkins
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.