Cleary Management Corporation Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-13 | Presenter: Chris Knospe | Export set: Top 12 | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Mozilla Firefox Remediation Options: Update to version 157.0.1 or later; uninstall if not in use Target Machines: CMC-2025-TOM.cmclax (tom), CMC-2025-FRONTDESK.cmclax (frontdesk), CMC-2025-MAINT.cmclax (jwhite), CMC-2025-HALEY.cmclax (hondell), ELECTRICALROOM (doorcontrol), HVP-HVAC01, cmc-2025-kris (kcleary) Estimated Time of Remediation: 1 hour 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: CMC-2019-SANDY.cmclax, CMC-2023-CHRISTINE.cmclax (sdohnalik), CMC-2024-BETHANY.cmclax (bbowman), CMC-2024-PENNY.cmclax (pammerman), CMC-2025-FRONTDESK.cmclax (frontdesk), CMC-2025-MAINT.cmclax (jwhite), CMC-2025-TOM.cmclax (tom), CMC-DC1.cmclax (rrc), CMC-DoorControl.cmclax (DoorControl), ELECTRICALROOM (doorcontrol), HVP-HVAC01, Landmarkloftpc2 (Landmark Lofts) Estimated Time of Remediation: 1 hour 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: CMC-2019-SANDY.cmclax, CMC-2023-CHRISTINE.cmclax (sdohnalik), CMC-2024-BETHANY.cmclax (bbowman), CMC-2024-PENNY.cmclax (pammerman), CMC-2025-FRONTDESK.cmclax (frontdesk), CMC-2025-HALEY.cmclax (hondell), cmc-2025-kris (kcleary), CMC-2025-MAINT.cmclax (jwhite), CMC-2025-TOM.cmclax (tom), CMC-DoorControl.cmclax (DoorControl), ELECTRICALROOM (doorcontrol) Estimated Time of Remediation: 1 hour Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 26.03 (x64 edition) Remediation Options: Update to version 26.04 or later; uninstall if not in use Target Machines: Landmarkloftpc2 (Landmark Lofts), CMC-2019-SANDY.cmclax Estimated Time of Remediation: 0.5 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft SQL Server 2012 Native Client Remediation Options: Update to version 5.0.17 or later; uninstall if not in use Target Machines: CMC-DoorControl.cmclax (DoorControl), CMC-DC1.cmclax (rrc), CMC-2023-CHRISTINE.cmclax (sdohnalik) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 4.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 12 vulnerabilities docx report - Ticket #1905707: Vulnerability Remediation - Windows 11 (all versions) - Updates Required - Ticket #1905709: Vulnerability Remediation - Microsoft .NET (all versions) - Update Required - Ticket #1905710: Vulnerability Remediation - Microsoft Edge - Updates Required - Ticket #1905712: Vulnerability Remediation - FortiClient VPN - Update Required - Ticket #1905711: Vulnerability Remediation - powershellv2 - Update Required - Ticket #1905713: Vulnerability Remediation - ssl-enum-ciphers_TLSv1.0_3389 - Configuration Change Required - Ticket #1905714: Vulnerability Remediation - ssl-enum-ciphers_TLSv1.1_3389 - Configuration Change 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 Sarah to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
sdohnalik@cmclax.com
sdohnalik@cmclax.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Sarah, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 12): Open Top 12 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, Chris Knospe
2026 Q4 Remaining remediations
Good evening Sarah, Following the quarterly vulnerability review for Cleary Management Corporation, 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. Mozilla Firefox Affected hosts: CMC-2025-TOM.cmclax (tom) - 172.31.254.2, CMC-2025-FRONTDESK.cmclax (frontdesk) - 10.10.10.63, CMC-2025-MAINT.cmclax (jwhite) - 10.10.10.66, CMC-2025-HALEY.cmclax (hondell) - 10.10.10.74, ELECTRICALROOM (doorcontrol) - 192.168.100.10, HVP-HVAC01 - 192.168.100.151, cmc-2025-kris (kcleary) - 192.168.4.156 What to do: Update Mozilla Firefox to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 2. Speculative Store Bypass Affected hosts: CMC-2019-SANDY.cmclax - 10.10.10.61, CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54, CMC-2024-BETHANY.cmclax (bbowman) - 10.10.10.71, CMC-2024-PENNY.cmclax (pammerman) - 10.10.10.70, CMC-2025-FRONTDESK.cmclax (frontdesk) - 10.10.10.63, CMC-2025-MAINT.cmclax (jwhite) - 10.10.10.66, CMC-2025-TOM.cmclax (tom) - 172.31.254.2, CMC-DC1.cmclax (rrc) - 10.10.10.5, CMC-DoorControl.cmclax (DoorControl) - 10.20.1.10, ELECTRICALROOM (doorcontrol) - 192.168.100.10, HVP-HVAC01 - 192.168.100.151, Landmarkloftpc2 (Landmark Lofts) - 10.20.2.7 What to do: Apply missing OS updates for Speculative Store Bypass to the minimum version to reach (or the latest available), decommission the host if it is not needed, or suppress / accept residual risk when patching is not possible (client must be notified or accept; risk remains until a real fix). 3. WinVerifyTrust Signature Validation Vulnerability Affected hosts: CMC-2019-SANDY.cmclax - 10.10.10.61, CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54, CMC-2024-BETHANY.cmclax (bbowman) - 10.10.10.71, CMC-2024-PENNY.cmclax (pammerman) - 10.10.10.70, CMC-2025-FRONTDESK.cmclax (frontdesk) - 10.10.10.63, CMC-2025-HALEY.cmclax (hondell) - 10.10.10.74, cmc-2025-kris (kcleary) - 192.168.4.156, CMC-2025-MAINT.cmclax (jwhite) - 10.10.10.66, CMC-2025-TOM.cmclax (tom) - 172.31.254.2, CMC-DoorControl.cmclax (DoorControl) - 10.20.1.10, ELECTRICALROOM (doorcontrol) - 192.168.100.10 What to do: Correct the listed configuration for WinVerifyTrust Signature Validation Vulnerability, or suppress / accept residual risk when the client will not change it (client must be notified or accept; risk remains until a real fix). 4. 7-Zip 26.03 (x64 edition) Affected hosts: Landmarkloftpc2 (Landmark Lofts) - 10.20.2.7, CMC-2019-SANDY.cmclax - 10.10.10.61 What to do: Update 7-Zip 26.03 (x64 edition) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 5. Microsoft SQL Server 2012 Native Client Affected hosts: CMC-DoorControl.cmclax (DoorControl) - 10.20.1.10, CMC-DC1.cmclax (rrc) - 10.10.10.5, CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 What to do: Update Microsoft SQL Server 2012 Native Client 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, 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: 4
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 (1670 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129195. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5129242. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted) (or the latest available).
Affected Systems:
- Landmarkloftpc2 (Landmark Lofts) - 10.20.2.7 [10.0.26100] [1658 vulns]
- CMC-DoorControl.cmclax (DoorControl) - 10.20.1.10 [10.0.26200] [1658 vulns]
- CMC-2025-FRONTDESK.cmclax (frontdesk) - 10.10.10.63 [10.0.26100] [1658 vulns]
- ELECTRICALROOM (doorcontrol) - 192.168.100.10 [10.0.26100] [1658 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): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Product/System: Microsoft .NET (all versions)
Affected Systems Count: 7
Finding summary:
Microsoft .NET (all versions) is outdated on the listed hosts.
These runtimes update within the same major version. An app built on one major version is tied to that version - removing it will break the app.
CVE references:
CVE-2023-36049
https://nvd.nist.gov/vuln/detail/CVE-2023-36049
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36049
Additional CVEs (24 more) are listed in the Client Folder report.
Affected Systems:
- CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 [53 vulns]
- CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 [7.0.7] [52 vulns]
- CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 [5.0.17] [3 vulns]
- CMC-2019-SANDY.cmclax - 10.10.10.61 [5.0.17] [3 vulns]
- CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 [6.0.36] [3 vulns]
- CMC-2019-SANDY.cmclax - 10.10.10.61 [6.0.36] [3 vulns]
- CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 [7.0.20] [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the redistributable/runtime is not present or is already at/above the minimum version to reach for that major version.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- .NET Framework and modern .NET (.NET 5+) are not interchangeable
- An app built on one major version is tied to that version - removing it will break the app.
- Update each runtime line via WU/vendor installer; uninstall only when unused and verified
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET 5: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 6: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 7: out of support since May 14, 2024 - uninstall if unused and verified, or escalate cannot-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): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Mozilla Firefox - Update Required - 3rd party application
Vulnerability Remediation - Mozilla Firefox - Update Required - 3rd party application
Product/System: Mozilla Firefox
Affected Systems Count: 7
Finding summary:
Mozilla Firefox 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-84134
https://nvd.nist.gov/vuln/detail/CVE-2026-84134
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (179 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 157.0.1 (or the latest available).
Affected Systems:
- CMC-2025-TOM.cmclax (tom) - 172.31.254.2 [180 vulns]
- CMC-2025-FRONTDESK.cmclax (frontdesk) - 10.10.10.63 [2 vulns]
- CMC-2025-MAINT.cmclax (jwhite) - 10.10.10.66 [2 vulns]
- CMC-2025-HALEY.cmclax (hondell) - 10.10.10.74 [2 vulns]
- ELECTRICALROOM (doorcontrol) - 192.168.100.10 [2 vulns]
- HVP-HVAC01 - 192.168.100.151 [2 vulns]
- cmc-2025-kris (kcleary) - 192.168.4.156 [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)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Firefox updates in background; relaunch may be needed to apply a downloaded update
- If still behind: check Firefox update settings / Maintenance Service
- ESR and release can both be present - update the channel that is installed
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Edge - Updates Required
Vulnerability Remediation - Microsoft Edge - Updates Required
Product/System: Microsoft Edge
Affected Systems Count: 1
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. A reboot is usually not required.
CVE references:
CVE-2026-58289
https://nvd.nist.gov/vuln/detail/CVE-2026-58289
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58289
Additional CVEs (1547 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 155.0.4283.45 (or the latest available).
Affected Systems:
- CMC-2023-MTech2.cmclax (msanford) - 10.10.10.69 [1548 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Speculative Store Bypass - Updates Required - 3rd party application
Vulnerability Remediation - Speculative Store Bypass - Configuration Change Required - 3rd party application
Product/System: Speculative Store Bypass
Affected Systems Count: 12
Finding summary:
Speculative Store Bypass is a configuration / hardening finding.
Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2018-3639
https://nvd.nist.gov/vuln/detail/CVE-2018-3639
Affected Systems:
- CMC-2019-SANDY.cmclax - 10.10.10.61 [1 vulns]
- CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 [1 vulns]
- CMC-2024-BETHANY.cmclax (bbowman) - 10.10.10.71 [1 vulns]
- CMC-2024-PENNY.cmclax (pammerman) - 10.10.10.70 [1 vulns]
- CMC-2025-FRONTDESK.cmclax (frontdesk) - 10.10.10.63 [1 vulns]
- CMC-2025-MAINT.cmclax (jwhite) - 10.10.10.66 [1 vulns]
- CMC-2025-TOM.cmclax (tom) - 172.31.254.2 [1 vulns]
- CMC-DC1.cmclax (rrc) - 10.10.10.5 [1 vulns]
- CMC-DoorControl.cmclax (DoorControl) - 10.20.1.10 [1 vulns]
- ELECTRICALROOM (doorcontrol) - 192.168.100.10 [1 vulns]
- HVP-HVAC01 - 192.168.100.151 [1 vulns]
- Landmarkloftpc2 (Landmark Lofts) - 10.20.2.7 [1 vulns]
Quick-check each host/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
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) =====
- Speculative Store Bypass (CVE-2018-3639) is a Windows CPU-mitigation registry setting - not a software install
- Apply latest Windows quality/security updates first - the registry 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 Reports location below.
Reports location (Client Folder): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
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: 11
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:
- CMC-2019-SANDY.cmclax - 10.10.10.61 [1 vulns]
- CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 [1 vulns]
- CMC-2024-BETHANY.cmclax (bbowman) - 10.10.10.71 [1 vulns]
- CMC-2024-PENNY.cmclax (pammerman) - 10.10.10.70 [1 vulns]
- CMC-2025-FRONTDESK.cmclax (frontdesk) - 10.10.10.63 [1 vulns]
- CMC-2025-HALEY.cmclax (hondell) - 10.10.10.74 [1 vulns]
- cmc-2025-kris (kcleary) - 192.168.4.156 [1 vulns]
- CMC-2025-MAINT.cmclax (jwhite) - 10.10.10.66 [1 vulns]
- CMC-2025-TOM.cmclax (tom) - 172.31.254.2 [1 vulns]
- CMC-DoorControl.cmclax (DoorControl) - 10.20.1.10 [1 vulns]
- ELECTRICALROOM (doorcontrol) - 192.168.100.10 [1 vulns]
Quick-check each host/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
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
===== 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): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - FortiClient VPN - Update Required
Vulnerability Remediation - FortiClient VPN - Update Required
Product/System: FortiClient VPN
Affected Systems Count: 4
Finding summary:
FortiClient VPN is a VPN client on the listed hosts.
If the site has a FortiGate / Fortinet firewall, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it. Use the vendor installer from support.fortinet.com. Automated / RMM updates have failed for FortiClient VPN in the past.
CVE references:
CVE-2026-70465
https://nvd.nist.gov/vuln/detail/CVE-2026-70465
Vendor security center:
https://fortiguard.fortinet.com/psirt
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.4.3.4726 (or the latest available).
Affected Systems:
- CMC-2019-SANDY.cmclax - 10.10.10.61 [7 vulns]
- CMC-2025-MAINT.cmclax (jwhite) - 10.10.10.66 [2 vulns]
- Landmarkloftpc2 (Landmark Lofts) - 10.20.2.7 [2 vulns]
- cmc-2025-kris (kcleary) - 192.168.4.156 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has a FortiGate / Fortinet firewall: download from support.fortinet.com and run the vendor installer to the version listed under Minimum version to reach (or the latest available). Do not rely on RMM for FortiClient VPN.
- Coordinate the FortiClient version with site FortiGate firmware before upgrading.
- If the site does not have a FortiGate / Fortinet firewall: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the update path.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- FortiClient VPN: manual vendor installer recommended
This VPN is expected if the site has a FortiGate / Fortinet firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it.
- Automated / RMM updates have failed for FortiClient VPN in the past - do not rely on them until a better path exists
- Do not use winget or automated patching for this product
- Download updated installer from support.fortinet.com
- Transfer via ScreenConnect file transfer
- CMD console (SYSTEM OK): FortiClientVPNSetup_x.x.x.exe /quiet /norestart
- Coordinate version with site FortiGate firmware before upgrading
- Verify version after install
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - 7-Zip 26.03 (x64 edition) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 26.03 (x64 edition) - Update Required - 3rd party application
Product/System: 7-Zip 26.03 (x64 edition)
Affected Systems Count: 2
Finding summary:
7-Zip 26.03 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.04 (or the latest available).
Affected Systems:
- Landmarkloftpc2 (Landmark Lofts) - 10.20.2.7 [3 vulns]
- CMC-2019-SANDY.cmclax - 10.10.10.61 [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft SQL Server 2012 Native Client - Update Required - 3rd party application
Vulnerability Remediation - Microsoft SQL Server 2012 Native Client - Update Required - 3rd party application
Product/System: Microsoft SQL Server 2012 Native Client
Affected Systems Count: 3
Finding summary:
Microsoft SQL Server 2012 Native Client 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:
Multiple bundled scanner entries report end-of-life components; patch within each runtime line per remediation guidance (or the latest available).
Affected Systems:
- CMC-DoorControl.cmclax (DoorControl) - 10.20.1.10 [1 vulns]
- CMC-DC1.cmclax (rrc) - 10.10.10.5 [1 vulns]
- CMC-2023-CHRISTINE.cmclax (sdohnalik) - 10.10.10.54 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - powershellv2 - Update Required
Vulnerability Remediation - powershellv2 - Update Required
Product/System: powershellv2
Affected Systems Count: 2
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:
- CMC-2023-MTech2.cmclax (msanford) - 10.10.10.69 [1 vulns]
- CMC-DC1.cmclax (rrc) - 10.10.10.5 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
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: 2
Finding summary:
ssl-enum-ciphers_TLSv1.0_3389 is a configuration / hardening finding.
Correct the listed setting(s) per Technical guidance.
Affected Systems:
- CMC-2024-PENNY.cmclax (pammerman) - 10.10.10.70 [1 vulns]
- DESKTOP-VCN5G2E - 10.20.1.54 [1 vulns]
Quick-check each host/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
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.
- 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) =====
- 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 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; 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 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 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): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
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: 2
Finding summary:
ssl-enum-ciphers_TLSv1.1_3389 is a configuration / hardening finding.
Correct the listed setting(s) per Technical guidance.
Affected Systems:
- CMC-2024-PENNY.cmclax (pammerman) - 10.10.10.70 [1 vulns]
- DESKTOP-VCN5G2E - 10.20.1.54 [1 vulns]
Quick-check each host/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
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.
- 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) =====
- 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 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; 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 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 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): ...\Cleary Management Corporation\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Sarah,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 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 - 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,
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.