Highland Memorial Park Inc Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-01 | Presenter: Chris Knospe | Export set: Top 13 | Client type: RMIT/CMIT
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Windows 11 (all versions) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: WIN11-01-2024.hmpi (egp), win11-08-2024.hmpi (pap), WIN11-03-2024.hmpi (egp), win11-07-2024.hmpi (frontdesk), WIN11-04-2024.hmpi (shop), win11-06-2024.hmpi (bookkeeping), win11-05-2024.hmpi (dsr) Estimated Time of Remediation: 2 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2025 Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: HMPI-HYPERV (Administrator) Estimated Time of Remediation: 1 hour 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: HMPI-HYPERV (Administrator), HMPI-HYPERV (Administrator), HMPI-HYPERV (Administrator) Estimated Time of Remediation: 1 hour Remediation Method: Deploy the matching runtime installer via RMM. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: PostgreSQL 10 Remediation Options: Update to version 16.1 or later; uninstall if not in use Target Machines: HMPI-HYPERV (Administrator) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Edge Remediation Options: Update to version 154.0.4258.48 or later; uninstall if not in use Target Machines: WIN11-01-2023.hmpi (egp), WIN11-01-2024.hmpi (egp) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Teams Remediation Options: Update to version 26225.1806.5074.1452 or later; uninstall if not in use Target Machines: WIN11-01-2023.hmpi (egp), Win11-08-2026 (EGP) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Speculative Store Bypass Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: HMPI-APPSRV.hmpi, HMPI-DC-01.hmpi (rradmin), HMPI-FS-01.hmpi (rradmin), HMPI-HYPERV (Administrator), WIN11-01-2024.hmpi (egp), WIN11-02-2024.hmpi (egp), WIN11-03-2024.hmpi (egp), WIN11-04-2024.hmpi (shop), win11-05-2024.hmpi (dsr), win11-06-2024.hmpi (bookkeeping), win11-07-2024.hmpi (frontdesk), win11-08-2024.hmpi (pap), Win11-08-2026 (EGP), WIN-11-VAULT.hmpi (Administrator) Estimated Time of Remediation: 2 hours Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: WinVerifyTrust Signature Validation Vulnerability Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: HMPI-APPSRV.hmpi, HMPI-DC-01.hmpi (rradmin), HMPI-FS-01.hmpi (rradmin), WIN11-01-2023.hmpi (egp), WIN11-01-2024.hmpi (egp), WIN11-02-2024.hmpi (egp), Win11-08-2026 (EGP), WIN-11-VAULT.hmpi (Administrator) Estimated Time of Remediation: 2 hours Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: powershellv2 Remediation Options: Update to the current version; uninstall if not in use Target Machines: HMPI-APPSRV.hmpi, WIN11-03-2024.hmpi (egp), WIN11-04-2024.hmpi (shop), win11-05-2024.hmpi (dsr), win11-06-2024.hmpi (bookkeeping), win11-07-2024.hmpi (frontdesk) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Branch Target Injection (Spectre-v2) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: HMPI-APPSRV.hmpi, HMPI-DC-01.hmpi (rradmin), HMPI-FS-01.hmpi (rradmin), HMPI-HYPERV (Administrator) Estimated Time of Remediation: 1 hour Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: ssl-enum-ciphers_TLSv1.0_3389 Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: HMPI-APPSRV.hmpi, HMPI-DC-01.hmpi (rradmin), WIN11-01-2024.hmpi (egp), WIN11-03-2024.hmpi (egp), win11-07-2024.hmpi (frontdesk), WIN11-02-2024.hmpi (egp), win11-05-2024.hmpi (dsr), win11-06-2024.hmpi (bookkeeping), win11-08-2024.hmpi (pap) Estimated Time of Remediation: 1 hour Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: ssl-enum-ciphers_TLSv1.1_3389 Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: HMPI-APPSRV.hmpi, HMPI-DC-01.hmpi (rradmin), WIN11-01-2024.hmpi (egp), WIN11-03-2024.hmpi (egp), win11-07-2024.hmpi (frontdesk), WIN11-02-2024.hmpi (egp), win11-05-2024.hmpi (dsr), win11-06-2024.hmpi (bookkeeping), win11-08-2024.hmpi (pap) Estimated Time of Remediation: 1 hour Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: Email DNS - Mail authentication (SPF, DMARC, DKIM) Remediation Options: Publish or correct SPF, DMARC, and DKIM for the listed domains after confirming each domain sends mail Target Machines: highlandmemorial.com Estimated Time of Remediation: 1 hour Remediation Method: Update SPF, DMARC, and DKIM after confirming the domain sends mail. Verify the records after the change. -------------------------------------------------------------------------------------------- Total Estimated Time: 14.5 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 13 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 Glen to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
egporter@highlandmemorial.com
egporter@highlandmemorial.com
2026 Q4 Vulnerability Scan Follow Up
Good morning Glen, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top Ten + 12): 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 Glen, Following the quarterly vulnerability review for Highland Memorial Park Inc, there are no remaining remediations to report. Sincerely, Chris Knospe
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Vulnerability Remediation - Windows 11 (all versions) - Updates Required Product/System: Windows 11 (all versions) Affected Systems Count: 7 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-53766 https://nvd.nist.gov/vuln/detail/CVE-2025-53766 Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53766 Additional CVEs (1906 more) are listed in the Client Folder report. Minimum version to reach: - Apply Windows Update KB5129242. Upgrade to supported Operating System is recommended - Apply Windows Update KB5129195 (or the latest available). Affected Systems: - WIN11-01-2024.hmpi (egp) - 192.168.199.52 [10.0.26100] [1658 vulns] - win11-08-2024.hmpi (pap) - 192.168.199.67 [10.0.22631] [1461 vulns] - WIN11-03-2024.hmpi (egp) - 192.168.199.54 [10.0.22631] [1461 vulns] - win11-07-2024.hmpi (frontdesk) - 192.168.199.60 [10.0.22631] [1461 vulns] - WIN11-04-2024.hmpi (shop) - 192.168.1.12 [10.0.22631] [1461 vulns] - win11-06-2024.hmpi (bookkeeping) - 192.168.199.66 [10.0.22631] [1461 vulns] - win11-05-2024.hmpi (dsr) - 192.168.199.65 [10.0.22631] [1448 vulns] Quick-check each host first: Confirm the OS/build on the host matches this finding. Then stop and escalate to Security (false positive or no further action) if any of these apply: - The host is already at or above the minimum version to reach (build/KB) - The host is already on the latest quality/security updates for its current Windows version - The vendor documents this CVE as not applicable or already fixed In the escalation, 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 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. - The 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: - Apply missing Windows updates via RMM or Windows Update (or Intune) - If the host is a VM, take a pre-update snapshot so you can revert if there are issues. - Reboot if Windows Update requires it - After the update, confirm the host has the latest quality/security updates for its current Windows version - If the host is already fully updated and still flagged, escalate to Security as no further action. Do not force a feature upgrade. Source material: Full scan exports and Top N reports are in the Client Folder under Reports location below. Reports location (Client Folder): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4 Ticket created by Chris Knospe.
Vulnerability Remediation - Windows Server 2025 - Updates Required
Vulnerability Remediation - Windows Server 2025 - Updates Required
Product/System: Windows Server 2025
Affected Systems Count: 1
Finding summary:
Windows Server 2025 is missing required updates on the listed host.
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-70296
https://nvd.nist.gov/vuln/detail/CVE-2026-70296
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70296
Additional CVEs (818 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129235 (or the latest available).
Affected Systems:
- HMPI-HYPERV (Administrator) - 192.168.199.40 [10.0.26100] [819 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:
- the host is already at or above the minimum version to reach (build/KB)
- the host is 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:
- 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 the 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.
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.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: 3 Finding summary: Microsoft .NET (all versions) is outdated on the listed hosts. Runtimes update within the same major version. An app built on one major version is tied to that version, and 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 (45 more) are listed in the Client Folder report. Minimum version to reach: - Update to version 8.0.31 (or the latest available). Affected Systems: - HMPI-HYPERV (Administrator) - 192.168.199.40 [8.0.15] [135 vulns] - HMPI-HYPERV (Administrator) - 192.168.199.40 [62 vulns] - HMPI-HYPERV (Administrator) - 192.168.199.40 [10.0.26100] [45 vulns] Quick-check each host first: Stop and escalate to Security as a false positive if the redistributable/runtime is not present, or is already at or 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, and residual risk stays until a real fix. - The 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 it 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: - .NET Framework and modern .NET (.NET 5+) are not interchangeable. - 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 8 (LTS): update the runtime to the reported target within the 8.x line (Windows Update or runtime installer). - .NET 10 (LTS): update the runtime to the reported target within the 10.x line. Source material: Full scan exports and Top N reports are in the Client Folder under the Reports location below. Reports location (Client Folder): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4 Ticket created by Chris Knospe.
Vulnerability Remediation - PostgreSQL 10 - Update Required
Vulnerability Remediation - PostgreSQL 10 - Update Required
Product/System: PostgreSQL 10
Affected Systems Count: 1
Finding summary:
PostgreSQL 10 is a database engine on the listed hosts.
Confirm the instance or cluster, then apply the matching engine update in a maintenance window with the DBA or app owner.
CVE references:
CVE-2019-9193
https://nvd.nist.gov/vuln/detail/CVE-2019-9193
Vendor security center:
https://www.postgresql.org/support/security/
Additional CVEs (23 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 16.1 (or the latest available).
Affected Systems:
- HMPI-HYPERV (Administrator) - 192.168.199.40 [24 vulns]
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or 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) =====
- PostgreSQL is a database engine - not a desktop app
- Confirm major version and cluster on each host
- Apply the matching minor/security update for that major in a maintenance window
- Do not use winget; coordinate before restarting the service
===== 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): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Microsoft Edge - Update Required
Vulnerability Remediation - Microsoft Edge - Update Required
Product/System: Microsoft Edge
Affected Systems Count: 2
Finding summary:
Microsoft Edge 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, and a reboot is usually not required.
CVE references:
CVE-2026-78904
https://nvd.nist.gov/vuln/detail/CVE-2026-78904
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-78904
Additional CVEs (550 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 154.0.4258.48 (or the latest available).
Affected Systems:
- WIN11-01-2023.hmpi (egp) - 100.73.120.141 [551 vulns]
- WIN11-01-2024.hmpi (egp) - 192.168.199.52 [211 vulns]
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or 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: the OS cannot support the secure release, or the 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, and 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 it 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) =====
- Auto-updating software: verify first, patch only if stale
- Confirm installed version against the reported target on affected hosts
- Edge updates via Microsoft Edge Update (primary); WU may also apply updates
- Relaunch may be needed for a downloaded update to take effect
- Live user session only if needed: edge://settings/help > Download and install
- Backstage (CMD/PS): silent installer/script only - not the Edge 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): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Microsoft Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 2
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 26225.1806.5074.1452 (or the latest available).
Affected Systems:
- WIN11-01-2023.hmpi (egp) - 100.73.120.141 [7 vulns]
- Win11-08-2026 (EGP) - 192.168.4.4 [6 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): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Speculative Store Bypass - Updates Required
Vulnerability Remediation - Speculative Store Bypass - Configuration Change Required
Product/System: Speculative Store Bypass
Affected Systems Count: 14
Finding summary:
Speculative Store Bypass is a configuration / hardening finding. Correct the listed setting(s) per the Technical guidance.
CVE references:
CVE-2018-3639
https://nvd.nist.gov/vuln/detail/CVE-2018-3639
Affected Systems:
- HMPI-APPSRV.hmpi - 192.168.199.21 [1 vulns]
- HMPI-DC-01.hmpi (rradmin) - 192.168.199.5 [1 vulns]
- HMPI-FS-01.hmpi (rradmin) - 192.168.199.30 [1 vulns]
- HMPI-HYPERV (Administrator) - 192.168.199.40 [1 vulns]
- WIN11-01-2024.hmpi (egp) - 192.168.199.52 [1 vulns]
- WIN11-02-2024.hmpi (egp) - 192.168.199.64 [1 vulns]
- WIN11-03-2024.hmpi (egp) - 192.168.199.54 [1 vulns]
- WIN11-04-2024.hmpi (shop) - 192.168.1.12 [1 vulns]
- win11-05-2024.hmpi (dsr) - 192.168.199.65 [1 vulns]
- win11-06-2024.hmpi (bookkeeping) - 192.168.199.66 [1 vulns]
- win11-07-2024.hmpi (frontdesk) - 192.168.199.60 [1 vulns]
- win11-08-2024.hmpi (pap) - 192.168.199.67 [1 vulns]
- Win11-08-2026 (EGP) - 192.168.4.4 [1 vulns]
- WIN-11-VAULT.hmpi (Administrator) - 192.168.199.69 [1 vulns]
First, quick-check each host/domain. If the configuration is already correct or the finding does not apply, stop and escalate to Security as a false positive, and include details. Otherwise, choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in the Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked. Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record the client notification/acceptance in the discussion notes to the client: who, what, which hosts, and that risk remains.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- The client must accept or be notified.
Client coordination - READ BEFORE CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture, schedule it after hours or contact the client first.
If another vendor manages this application, device, workstation, or server, that vendor or the service owner must make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Speculative Store Bypass (CVE-2018-3639) is a Windows CPU-mitigation registry setting - not a software install
- Apply the latest Windows quality/security updates first - the registry setting does nothing without those KBs
- Enable the OS mitigation: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
- If FeatureSettingsOverride is missing: set FeatureSettingsOverride=8 and FeatureSettingsOverrideMask=3
- If Override already has a value: add bit 8 (SSB) per Microsoft KB4072698 - do not wipe other Spectre bits already in use
- Prefer domain GPO (or Intune) over one-off registry edits
- Reboot, then verify: Install-Module SpeculationControl; Get-SpeculationControlSettings
- If already patched and mitigations show enabled: escalate to Security as a false positive with hostname, build, and the cmdlet output - then stop
- These mitigations can slow a busy server - discuss with the client if users will notice
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2018-3639
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under the Reports location below.
Reports location (Client Folder): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Product/System: WinVerifyTrust Signature Validation Vulnerability
Affected Systems Count: 8
Finding summary:
WinVerifyTrust Signature Validation Vulnerability is a configuration / hardening finding. Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2013-3900
https://nvd.nist.gov/vuln/detail/CVE-2013-3900
Affected Systems:
- HMPI-APPSRV.hmpi - 192.168.199.21 [1 vulns]
- HMPI-DC-01.hmpi (rradmin) - 192.168.199.5 [1 vulns]
- HMPI-FS-01.hmpi (rradmin) - 192.168.199.30 [1 vulns]
- WIN11-01-2023.hmpi (egp) - 100.73.120.141 [1 vulns]
- WIN11-01-2024.hmpi (egp) - 192.168.199.52 [1 vulns]
- WIN11-02-2024.hmpi (egp) - 192.168.199.64 [1 vulns]
- Win11-08-2026 (EGP) - 192.168.4.4 [1 vulns]
- WIN-11-VAULT.hmpi (Administrator) - 192.168.199.69 [1 vulns]
Quick-check each host/domain first. If the configuration is already correct or the finding does not apply, stop and escalate to Security as a false positive. Include details.
Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- 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 CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture, 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 make the change. If they are unable or unwilling, escalate to Security for suppression.
TECHNICAL GUIDANCE (do this):
- WinVerifyTrust / CVE-2013-3900 is Authenticode hardening - not a software install or Windows Update.
- Set EnableCertPaddingCheck=1 under HKLM\Software\Microsoft\Cryptography\Wintrust\Config
- On 64-bit hosts also set the Wow6432Node\...\Wintrust\Config copy
- Prefer domain GPO (or Intune) over one-off registry edits
- Verify signed installers and vendor tools still launch after the change
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - powershellv2 - Update Required
Vulnerability Remediation - powershellv2 - Update Required Product/System: powershellv2 Affected Systems Count: 6 Finding summary: powershellv2 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. Minimum version to reach: - Disable Windows PowerShell 2.0 on the system (or the latest available). Affected Systems: - HMPI-APPSRV.hmpi - 192.168.199.21 [1 vulns] - WIN11-03-2024.hmpi (egp) - 192.168.199.54 [1 vulns] - WIN11-04-2024.hmpi (shop) - 192.168.1.12 [1 vulns] - win11-05-2024.hmpi (dsr) - 192.168.199.65 [1 vulns] - win11-06-2024.hmpi (bookkeeping) - 192.168.199.66 [1 vulns] - win11-07-2024.hmpi (frontdesk) - 192.168.199.60 [1 vulns] Quick-check each host first: Stop and escalate to Security as a false positive if the product is not installed or is already at or 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: - 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 the host is a VM, take a pre-update snapshot so you can revert if there are issues. - Identify the 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 the CVE/product from this ticket and the vendor security advisory. Document the version applied. - Verify the update was successful. - If the installer/firmware indicates a reboot or service restart, coordinate with the client first. Source material: Full scan exports and Top N reports are in the Client Folder under Reports location below. Reports location (Client Folder): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4 Ticket created by Chris Knospe.
Vulnerability Remediation - Branch Target Injection (Spectre-v2) - Updates Required
Vulnerability Remediation - Branch Target Injection (Spectre-v2) - Updates Required Product/System: Branch Target Injection (Spectre-v2) Affected Systems Count: 4 Finding summary: Branch Target Injection (Spectre-v2) 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-2017-5715 https://nvd.nist.gov/vuln/detail/CVE-2017-5715 Minimum version to reach: - Install BIOS/firmware update and enable Windows support (or the latest available). Affected Systems: - HMPI-APPSRV.hmpi - 192.168.199.21 [1 vulns] - HMPI-DC-01.hmpi (rradmin) - 192.168.199.5 [1 vulns] - HMPI-FS-01.hmpi (rradmin) - 192.168.199.30 [1 vulns] - HMPI-HYPERV (Administrator) - 192.168.199.40 [1 vulns] Quick-check each host first: Confirm the OS/build on the host matches this finding. Then stop and escalate to Security (false positive or no further action) if any of these apply: - The host is already at or above the minimum version to reach (build/KB). - The host is already on the latest quality/security updates for its current Windows version. - The vendor documents this CVE as not applicable or already fixed. In the escalation, 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 or RMM broken after troubleshooting, client defers patching after verification, or no approved path yet. - Do not 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, and residual risk stays until a real fix. - The 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: - This is a CPU speculative-execution issue (Meltdown / Spectre / Speculative Store Bypass), not a desktop installer. - Apply the latest Windows quality/security updates or Linux vendor kernel updates. - Apply OEM BIOS / microcode if the vendor advisory requires it (Dell / HP / Lenovo / Intel / AMD). - Enable OS mitigations if they are off (Windows speculative-execution guidance). - If the host is already fully patched and mitigations are on, escalate to Security as no-further-action with hostname, build, and what you verified, then stop. - Coordinate a reboot. Discuss performance impact with the client if users will notice. Source material: Full scan exports and Top N reports are in the Client Folder under Reports location below. Reports location (Client Folder): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4 Ticket created by Chris Knospe.
Vulnerability Remediation - ssl-enum-ciphers_TLSv1.0_3389 - Configuration Change Required
Vulnerability Remediation - ssl-enum-ciphers_TLSv1.0_3389 - Configuration Change Required
Product/System: ssl-enum-ciphers_TLSv1.0_3389
Affected Systems Count: 9
Finding summary:
ssl-enum-ciphers_TLSv1.0_3389 is a configuration / hardening finding. Correct the listed setting(s) per Technical guidance.
Affected Systems:
- HMPI-APPSRV.hmpi - 192.168.199.21 [1 vulns]
- HMPI-DC-01.hmpi (rradmin) - 192.168.199.5 [1 vulns]
- WIN11-01-2024.hmpi (egp) - 192.168.199.52 [1 vulns]
- WIN11-03-2024.hmpi (egp) - 192.168.199.54 [1 vulns]
- win11-07-2024.hmpi (frontdesk) - 192.168.199.60 [1 vulns]
- WIN11-02-2024.hmpi (egp) - 192.168.199.64 [1 vulns]
- win11-05-2024.hmpi (dsr) - 192.168.199.65 [1 vulns]
- win11-06-2024.hmpi (bookkeeping) - 192.168.199.66 [1 vulns]
- win11-08-2024.hmpi (pap) - 192.168.199.67 [1 vulns]
First steps:
Quick-check each host/domain first. If the configuration is already correct or the finding does not apply, stop and escalate to Security as a false positive, including details. Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- For legacy network protocols: research and test dependents first. Do not change production until that is done.
- Then apply the hardening/setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked. Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Client must accept or be notified. Record client notification/acceptance in discussion notes to the client (who, what, hosts, and that risk remains).
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
Client coordination - READ BEFORE CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture, 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 make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- WARNING: research and testing required. Removing or disabling legacy network protocols can break software and/or network functions.
- Removal can break legacy apps, devices, integrations, shares, printers/MFPs, mail, partner APIs, and other functions that still need this protocol.
- Inventory dependents; research vendor/client requirements; test on non-production before any production change.
- Plan a maintenance window; prefer a modern replacement protocol before removing the legacy one.
- Enable TLS 1.2 or 1.3 before removing TLS 1.0/1.1.
- ssl-enum-ciphers is a TLS / SSL configuration finding, not a software install.
- Read protocol/cipher and port from the product name (ssl-enum-ciphers_TLSv1.0_3389 = TLS 1.0 on 3389/RDP).
- Identify that listener first: 443/8443 web or admin UI; 3389 RDP; 25/465/587/993/995 mail; 636 LDAPS; otherwise Get-NetTCPConnection or the vendor service on that port.
- If the name includes TLSv1.0 or TLSv1.1: disable that protocol only. Do not disable TLS 1.2 or 1.3.
- Windows (IIS, RDP, LDAPS, other Schannel services): prefer GPO or Intune over one-off registry edits.
- Disable TLS 1.0 and 1.1: HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server and Client - Enabled=0, DisabledByDefault=1 (same for TLS 1.1)
- Confirm TLS 1.2 or 1.3 already works before disabling 1.0/1.1.
- Non-Windows: change that product's TLS settings (Apache/nginx ssl_protocols, appliance TLS page).
- Restart the service or reboot, then verify the port no longer offers TLS 1.0/1.1.
- If the name includes Sweet32, 3DES, RC4, or WeakCipher: disable those ciphers and leave TLS 1.2/1.3 on.
- Sweet32 / 3DES: HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\Triple DES 168\Enabled=0
- If RC4 is listed: disable the RC4 keys under the same Ciphers key.
- Non-Windows: remove 3DES/RC4 from that product's cipher list (Apache/nginx ssl_ciphers, appliance TLS page).
- Restart the service or reboot, then verify the port no longer offers 3DES or RC4.
- If already hardened or the vendor documents not affected: escalate to Security as a false positive with hostname, service, port, and what you verified, then stop.
- After the change, re-scan or verify the service no longer offers the weak protocol or cipher.
===== 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): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - ssl-enum-ciphers_TLSv1.1_3389 - Configuration Change Required
Vulnerability Remediation - ssl-enum-ciphers_TLSv1.1_3389 - Configuration Change Required
Product/System: ssl-enum-ciphers_TLSv1.1_3389
Affected Systems Count: 9
Finding summary:
ssl-enum-ciphers_TLSv1.1_3389 is a configuration / hardening finding (TLS 1.1 on 3389/RDP). Correct the listed setting(s) per Technical guidance.
Affected Systems:
- HMPI-APPSRV.hmpi - 192.168.199.21 [1 vulns]
- HMPI-DC-01.hmpi (rradmin) - 192.168.199.5 [1 vulns]
- WIN11-01-2024.hmpi (egp) - 192.168.199.52 [1 vulns]
- WIN11-03-2024.hmpi (egp) - 192.168.199.54 [1 vulns]
- win11-07-2024.hmpi (frontdesk) - 192.168.199.60 [1 vulns]
- WIN11-02-2024.hmpi (egp) - 192.168.199.64 [1 vulns]
- win11-05-2024.hmpi (dsr) - 192.168.199.65 [1 vulns]
- win11-06-2024.hmpi (bookkeeping) - 192.168.199.66 [1 vulns]
- win11-08-2024.hmpi (pap) - 192.168.199.67 [1 vulns]
First step:
Quick-check each host/domain. If the configuration is already correct or the finding does not apply, stop and escalate to Security as a false positive, and include details. Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- For legacy network protocols: research and test dependents first. Do not change production until that is done.
- Then apply the hardening/setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked. Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client (who, what, hosts, and that risk remains).
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- The client must accept or be notified.
Client coordination - READ BEFORE CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture, schedule it after hours or contact the client first.
If another vendor manages this application, device, workstation, or server, that vendor or the service owner must make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- WARNING: research and testing required. Removing or disabling legacy network protocols can break software and/or network functions.
- Removal can break legacy apps, devices, integrations, shares, printers/MFPs, mail, partner APIs, and other functions that still need this protocol.
- Inventory dependents, research vendor/client requirements, and test on non-production before any production change.
- Plan a maintenance window. Prefer a modern replacement protocol before removing the legacy one.
- Enable TLS 1.2 or 1.3 before removing TLS 1.0/1.1.
- ssl-enum-ciphers is a TLS / SSL configuration finding, not a software install.
- Read protocol/cipher and port from the product name (ssl-enum-ciphers_TLSv1.0_3389 = TLS 1.0 on 3389/RDP).
- Identify that listener first: 443/8443 web or admin UI; 3389 RDP; 25/465/587/993/995 mail; 636 LDAPS; otherwise Get-NetTCPConnection or the vendor service on that port.
- If the name includes TLSv1.0 or TLSv1.1: disable that protocol only. Do not disable TLS 1.2 or 1.3.
- Windows (IIS, RDP, LDAPS, other Schannel services): prefer GPO or Intune over one-off registry edits.
- Disable TLS 1.0 and 1.1: HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server and Client - Enabled=0, DisabledByDefault=1 (same for TLS 1.1).
- Confirm TLS 1.2 or 1.3 already works before disabling 1.0/1.1.
- Non-Windows: change that product's TLS settings (Apache/nginx ssl_protocols, appliance TLS page).
- Restart the service or reboot, then verify the port no longer offers TLS 1.0/1.1.
- If the name includes Sweet32, 3DES, RC4, or WeakCipher: disable those ciphers and leave TLS 1.2/1.3 on.
- Windows Schannel: prefer GPO or Intune over one-off registry edits.
- Sweet32 / 3DES: HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\Triple DES 168\Enabled=0
- If RC4 is listed: disable the RC4 keys under the same Ciphers key.
- Non-Windows: remove 3DES/RC4 from that product's cipher list (Apache/nginx ssl_ciphers, appliance TLS page).
- Restart the service or reboot, then verify the port no longer offers 3DES or RC4.
- If already hardened or the vendor documents not affected: escalate to Security as a false positive with hostname, service, port, and what you verified, then stop.
- After the change, re-scan or verify the service no longer offers the weak protocol or cipher.
===== 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): ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Email DNS - DNS Config Required
Vulnerability Remediation - Email DNS - DNS Config Required Product/System: Email DNS - Mail authentication (SPF, DMARC, DKIM) Affected Domains: 1 Finding summary: Email authentication records are missing or incorrect for the listed domain(s) used for outbound email. Confirm each domain is actually used for mail before changing DNS. Publish or correct SPF, DMARC, and/or DKIM at the DNS provider. Affected domain(s): - highlandmemorial.com Quick-check each domain first: Confirm the domain is used for outbound email (MX, Microsoft 365 accepted domains, known senders, marketing platforms). Stop and escalate to Security as a false positive if the domain is not used for mail, or if SPF/DMARC/DKIM are already correct. Include the domain list and reason. Otherwise choose change, false positive, or accepted risk below and document it in the ticket. Remediation (pick the most appropriate option): A. Publish or correct DNS (default when the domain sends mail) - After client discussion and sender inventory, publish or correct SPF, DMARC, and/or DKIM at the DNS provider for each listed domain, including authorized third-party and device senders. B. Finding does not apply - escalate false positive - Domain not used for mail, or records already correct. Document what you checked. C. Accepted risk / client will not change DNS - escalate to Security - Record client notification/acceptance in discussion notes to the client. - These findings are assessed from public DNS, not ConnectSecure host scans, so they cannot be suppressed in ConnectSecure. Security documents the accepted-risk exception. - Client must accept or be notified. Risk remains until records are corrected. Client coordination - DISCUSS WITH THE CLIENT BEFORE ANY DNS CHANGE: DNS changes for SPF, DMARC, or DKIM can cause legitimate client mail to be undelivered or quarantined. Discuss timing and impact with the client first. Confirm third-party senders and mail-capable devices (scanners/MFPs, fax-to-email, etc.) before tightening SPF or DMARC. Do not publish or strengthen records until the client agrees. Technical guidance: - Identify the DNS host / registrar for each domain (from ticket detail or Client Folder notes). - Preferred access to the client's DNS host is delegated access to a River Run account. - Before publishing or tightening SPF/DMARC/DKIM, inventory every system that sends as this domain: - Primary mail platform (Microsoft 365 / Exchange, Google, etc.) - Third parties that send on behalf of the domain (marketing, billing, CRM, ticketing, newsletters, payroll, etc.). Add SPF includes and enable DKIM when the vendor supports it. - Mail-capable devices (MFPs/scanners, fax-to-email, postage, alarm/notification appliances, LOB SMTP). Authorize in SPF or route through an approved relay. - Do not tighten SPF (-all) or DMARC policy until those senders are covered or intentionally retired. - Publish or correct SPF, DMARC, and/or DKIM for the missing records only after the client agrees and the sender inventory is covered. - Preferred DMARC policy is p=quarantine. Use p=none only as a short monitor step if needed, then move to quarantine. Do not set p=reject unless the client asks for it. - After the change, verify public DNS shows the expected records. Wait for TTL where needed. Scope: Email authentication (SPF, DMARC, DKIM) - DNS TXT/CNAME records at the domain's DNS provider. Summary: 1 domain(s) flagged for DNS mail-authentication review. highlandmemorial.com DNS hosting: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com. Confirm this is the DNS provider where TXT records for highlandmemorial.com are managed. Issues: - DKIM not detected (common selectors probed via TXT/CNAME; confirm selector names with the mail platform if DKIM may already be enabled). - Obtain DKIM selector hostnames from the client's mail platform. Selectors can be named anything, and this scan only probes common selector names. - If the mail platform already shows DKIM enabled, a missing result here may be a false negative. Confirm the exact selector._domainkey.highlandmemorial.com names in public DNS (TXT with v=DKIM1 or CNAME). - Publish the selector DNS records (TXT with v=DKIM1 or CNAME at selector._domainkey.highlandmemorial.com). - Send a test message and confirm dkim=pass in Authentication-Results. Remediation: After the client agrees, and for each domain confirmed to send mail, work with the client's DNS provider to publish or correct the SPF, DMARC, and/or DKIM records needed to resolve the issues listed above (including authorized third-party and device senders). Then verify with a public DNS lookup tool (for example MXToolbox or nslookup). Source material: Full scan exports and Top N reports are in the Client Folder under Reports location: ...\Highland Memorial Park Inc\Network Documentation\Vulnerability Scans\2026 - Q4 These email authentication findings are assessed from public DNS records, not ConnectSecure host scans. They cannot be suppressed in ConnectSecure. Ticket created by Chris Knospe.
Good morning Glen,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top Ten + 12):
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.