The VanderBloemen Group, LLC Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-21 | Presenter: Andrew Harkins | Export set: 5 in export (Top 5) | 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 5 vulnerabilities docx report - Ticket #1899098: Vulnerability Remediation - Windows 11 (all versions) - Updates Required - Ticket #1899099: Vulnerability Remediation - Windows Server 2016 - Updates Required - Ticket #1899100: Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade) - Ticket #1899101: Vulnerability Remediation - Microsoft Defender - Update Required - Ticket #1899102: Vulnerability Remediation - Java 8 Update 201 - 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 Laura to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
lcg@constcpa.com
lcg@constcpa.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Laura, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 5): Open Top 5 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 Laura, Following the quarterly vulnerability review for The VanderBloemen Group, LLC, the items below still need remediation. These are typically third-party products or other remaining work that was not included in ticketed first-party remediations. 1. Java 8 Update 201 Affected hosts: ED2013 (user) - 192.168.1.50 What to do: Update Java 8 Update 201 to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). If you would like us to quote this work, or if you will handle it internally, reply to this email. If an item cannot be remediated for business reasons, let me know and I can suppress it from further scan reports. Sincerely, 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: 20
Finding summary:
Windows 11 (all versions) is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (2103 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129242
- Apply Windows Update KB5129195. Apply the latest patch
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (20 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- VB-406 (LauraAJohnson) - 192.168.86.27 [10.0.26100] [2071 vulns]
- VB-443 (NolanieMDengel) - 192.168.44.124 [10.0.26100] [1658 vulns]
- VB-420 - 192.168.1.43 [10.0.26100] [1658 vulns]
- 192.168.1.123 [1470 vulns]
- VB-469 (StephenVanderBloemen) - 10.80.72.13 [10.0.26200] [1364 vulns]
- VB-195 (StephenVanderBloemen) - 10.0.4.38 [10.0.22631] [1239 vulns]
- VB-424 (GretchenSLast) - 192.168.20.30 [10.0.22631] [1239 vulns]
- 192.168.1.27 [1186 vulns]
- 192.168.1.26 [1185 vulns]
- VB-468 - 192.168.1.16 [10.0.26200] [813 vulns]
- VBG-AVD-QB1 - 10.10.10.5 [10.0.26200] [627 vulns]
- VB-196 - 192.168.1.17 [10.0.26200] [622 vulns]
- VB-436 - 192.168.1.19 [10.0.26200] [622 vulns]
- VB-419 (AmandaRLaubenstein) - 192.168.1.23 [10.0.26200] [622 vulns]
- VB-464 (StephenVanderBloemen) - 192.168.1.31 [10.0.26200] [622 vulns]
- VB-403 (BethBrillowski) - 192.168.1.37 [10.0.26200] [622 vulns]
- VB-458 (AntonioEvans) - 192.168.1.40 [10.0.26200] [622 vulns]
- VB-188 (SamuelHarmer) - 192.168.1.47 [10.0.26200] [622 vulns]
- VB-220 (JayMomberg) - 192.168.41.118 [10.0.26200] [622 vulns]
- VB-192 (IsabelZimmerling) - 192.168.41.117 [10.0.26200] [621 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): ...\The VanderBloemen Group, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows Server 2016 - Updates Required
Vulnerability Remediation - Windows Server 2016 - Updates Required
Product/System: Windows Server 2016
Affected Systems Count: 2
Finding summary:
Windows Server 2016 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-41089
https://nvd.nist.gov/vuln/detail/CVE-2026-41089
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-41089
Additional CVEs (1300 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129239 (or the latest available).
Affected Systems:
- MOMBERG-VH.AD.MOMBERGCPA (Administrator) - 192.168.41.98 [10.0.14393] [1296 vulns]
- MOMBERG-DC.AD.MOMBERGCPA (Administrator) - 192.168.41.99 [10.0.14393] [1195 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): ...\The VanderBloemen Group, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Product/System: Windows 10 (all versions)
Affected Systems Count: 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-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 (1472 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5122878
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- ED2013 (user) - 192.168.1.50 [10.0.19045] [1474 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): ...\The VanderBloemen Group, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Defender - Update Required
Vulnerability Remediation - Microsoft Defender - Update Required
Product/System: Microsoft Defender
Affected Systems Count: 4
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-2026-50656
https://nvd.nist.gov/vuln/detail/CVE-2026-50656
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50656
Additional CVEs (3 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:
- 192.168.1.27 [4 vulns]
- VB-192 (IsabelZimmerling) - 192.168.41.117 [4 vulns]
- VB-406 (LauraAJohnson) - 192.168.86.27 [4 vulns]
- VB-195 (StephenVanderBloemen) - 10.0.4.38 [4 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)
- 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): ...\The VanderBloemen Group, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Java 8 Update 201 - Update Required
Vulnerability Remediation - Java 8 Update 201 - Update Required
Product/System: Java 8 Update 201
Affected Systems Count: 1
Finding summary:
Java 8 Update 201 is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-34169
https://nvd.nist.gov/vuln/detail/CVE-2022-34169
Vendor security center:
https://www.oracle.com/security-alerts/
Additional CVEs (59 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 8.0.5030.1 (or the latest available).
Affected Systems:
- ED2013 (user) - 192.168.1.50 [60 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm which Java runtime is installed (vendor + major version, e.g. Oracle 8 / Temurin 11) on each host
- Inventory apps that require that major version before changing anything
- Primary: update within the same major version line to the Minimum version to reach target (or latest security update for that line)
- Oracle Java: Oracle installer / Java Update / enterprise package per client license
- OpenJDK / Temurin-style: Adoptium Temurin or the distro already in use (do not switch vendors without app vendor approval)
- Prefer RMM/automated patching when deployed; else vendor MSI via ScreenConnect
- If unused after dependency check: uninstall that runtime
- Verify java -version / Programs and Features and dependent app startup after change
- Java 8: stay on the existing 8u line unless the app vendor requires a newer major
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\The VanderBloemen Group, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Laura,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 5):
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.