The Previant Law Firm, S.C. Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-08-17 | Presenter: Chris Knospe | Export set: 10 in export (Top 10) | Client type: RMIT/CMIT
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Windows 11 (all versions) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: 192.168.0.179 Estimated Time of Remediation: 0.5 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft 365 Apps for enterprise - en-us Remediation Options: Update to the current version; uninstall if not in use Target Machines: 192.168.0.32, PL-HP23-3.Previant (yh), PL-HP23-7.Previant (cps), PL-HP24-1.Previant (cmw) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft .NET (all versions) Remediation Options: Update to version 8.0.30 or later; uninstall if not in use Target Machines: PL-HP-22-6.Previant (snk), PL-HP24-4.Previant, PL-HP22-3.Previant, PL-HP-22-6.Previant (snk), PL-HP23-2.Previant, PL-HP23-3.Previant (yh), PL-HP24-4.Previant, PL-HP22-4.Previant (mjz), PL-HP23-5.Previant (ajs), PL-HP23-6.Previant, PL-HP23-7.Previant (cps), PL-HP23-8.Previant (djm), PL-HP23-9.Previant (ara), PL-HP24-8.Previant (hbl), PL-HP25-1.Previant (jh), PREV-L1021.Previant (jmr) Estimated Time of Remediation: 2 hours Remediation Method: Deploy the matching runtime installer via RMM. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Zoom Remediation Options: Update to version 7.1.5 or later; uninstall if not in use Target Machines: PL-HP17-3.Previant Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.12.6 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: COPITRAK.Previant (rradmin) Estimated Time of Remediation: 0.5 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: PL-HP22-1.Previant, PL-HP22-2.Previant (jat) 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: Python 3.13.12 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: COPITRAK.Previant (rradmin) Estimated Time of Remediation: 0.5 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: HP Support Assistant Remediation Options: Update to version 9.51.14.0 or later; uninstall if not in use Target Machines: PL-HP17-15.Previant Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: PL-HP23-3.Previant (yh) 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: 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: previant.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: 7 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top Ten vulnerabilities docx report - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with Christine to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
cmw@previant.com
cmw@previant.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Christine, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top Ten): Open Top Ten report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report – classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0–1.0, with 1.0 being most critical). • All Vulnerabilities Report – a comprehensive list of all detected vulnerabilities (internal and external), from critical to low severity. • Executive Summary Report – a high-level overview of your security posture and network information. • External Scan – detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report – vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: No remediation will begin without your approval. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Chris Knospe
2026 Q4 Remaining remediations
Good evening Christine, Following the quarterly vulnerability review for The Previant Law Firm, S.C., 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: 1
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-47291
https://nvd.nist.gov/vuln/detail/CVE-2026-47291
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47291
Additional CVEs (731 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5121003
- Apply Windows Update KB5120240. Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- 192.168.0.179 [1374 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Update Required
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Update Required
Product/System: Microsoft 365 Apps for enterprise - en-us
Affected Systems Count: 4
Finding summary:
Microsoft 365 Apps for enterprise - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-50387
https://nvd.nist.gov/vuln/detail/CVE-2026-50387
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50387
Additional CVEs (165 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120238. Apply the latest patch
- Apply the latest patch.
Affected Systems:
- 192.168.0.32 [1374 vulns]
- PL-HP23-3.Previant (yh) - 192.168.0.109
- PL-HP23-7.Previant (cps) - 192.168.0.111
- PL-HP24-1.Previant (cmw) - 192.168.0.118
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Product/System: Microsoft .NET (all versions)
Affected Systems Count: 16
Finding summary:
Microsoft .NET (all versions) is outdated on the listed hosts.
These runtimes update within the same major version. An app built on one major version is tied to that version - removing it will break the app.
CVE references:
CVE-2026-62898
https://nvd.nist.gov/vuln/detail/CVE-2026-62898
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62898
Additional CVEs (10 more) are listed in the Client Folder report.
Affected Systems:
- PL-HP-22-6.Previant (snk) - 192.168.0.161 [9.0.18] [33 vulns]
- PL-HP24-4.Previant - 192.168.0.103 [10.0.10] [15 vulns]
- PL-HP22-3.Previant - 192.168.0.173 [8.0.29]
- PL-HP-22-6.Previant (snk) - 192.168.0.161 [8.0.29]
- PL-HP23-2.Previant - 192.168.0.100 [8.0.29]
- PL-HP23-3.Previant (yh) - 192.168.0.109 [8.0.29]
- PL-HP24-4.Previant - 192.168.0.103 [8.0.29]
- PL-HP22-4.Previant (mjz) - 192.168.0.176 [9.0.18]
- PL-HP23-5.Previant (ajs) - 192.168.0.187 [10.0.10]
- PL-HP23-6.Previant - 192.168.0.113 [10.0.10]
- PL-HP23-7.Previant (cps) - 192.168.0.111 [10.0.10]
- PL-HP23-8.Previant (djm) - 192.168.0.188 [10.0.10]
- PL-HP23-9.Previant (ara) - 192.168.0.110 [10.0.10]
- PL-HP24-8.Previant (hbl) - 192.168.0.119 [10.0.10]
- PL-HP25-1.Previant (jh) - 192.168.0.192 [10.0.10]
- PREV-L1021.Previant (jmr) - 192.168.0.186 [10.0.10]
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 8 (LTS): update runtime to the reported target within the 8.x line (Windows Update or runtime installer)
- .NET 9 (non-LTS): update 9.x runtime via WU/vendor installer, or uninstall if unused
- .NET 10 (LTS): update runtime to the reported target within the 10.x line
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Zoom - Update Required
Vulnerability Remediation - Zoom - Update Required
Product/System: Zoom
Affected Systems Count: 1
Finding summary:
Zoom 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-2021-34423
https://nvd.nist.gov/vuln/detail/CVE-2021-34423
Vendor security center:
https://www.zoom.com/en/trust/security-bulletin/
Additional CVEs (61 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.1.5 (or the latest available).
Affected Systems:
- PL-HP17-3.Previant - 192.168.0.105 [62 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.
- MSI-managed Zoom often hides Check for Updates - prefer RMM or a silent installer
- 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): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.12.6 Executables (64-bit) - Update Required
Vulnerability Remediation - Python 3.12.6 Executables (64-bit) - Update Required
Product/System: Python 3.12.6 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.12.6 Executables (64-bit) 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-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (52 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- COPITRAK.Previant (rradmin) - 192.168.0.35
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm which Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip - Update Required
Vulnerability Remediation - 7-Zip - Update Required
Product/System: 7-Zip
Affected Systems Count: 2
Finding summary:
7-Zip 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 (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- PL-HP22-1.Previant - 192.168.0.178 [12 vulns]
- PL-HP22-2.Previant (jat) - 192.168.0.101
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): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.12 Executables (64-bit) - Update Required
Vulnerability Remediation - Python 3.13.12 Executables (64-bit) - Update Required
Product/System: Python 3.13.12 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.13.12 Executables (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-11940
https://nvd.nist.gov/vuln/detail/CVE-2026-11940
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (30 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- COPITRAK.Previant (rradmin) - 192.168.0.35
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm which Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - HP Support Assistant - Update Required
Vulnerability Remediation - HP Support Assistant - Update Required
Product/System: HP Support Assistant
Affected Systems Count: 1
Finding summary:
HP Support Assistant is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-38395
https://nvd.nist.gov/vuln/detail/CVE-2022-38395
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 9.51.14.0 (or the latest available).
Affected Systems:
- PL-HP17-15.Previant - 192.168.1.75 [15 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) =====
- HP Support Assistant is OEM support / driver utility software
- Prefer the vendor updater for that OEM, or leave a noisy companion service if it is not the real finding
- Do not push random Intel / NVIDIA driver packs from this ticket
- Uninstall only when unused and the client does not rely on that OEM tool
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip - Update Required
Vulnerability Remediation - 7-Zip - Update Required
Product/System: 7-Zip
Affected Systems Count: 1
Finding summary:
7-Zip 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 (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- PL-HP23-3.Previant (yh) - 192.168.0.109 [12 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): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
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):
- previant.com
Quick-check each domain first.
Confirm the domain is used for outbound email (MX, Microsoft 365 accepted domains, known senders).
Then stop (escalate to Security as a false positive) if the domain is not used for mail, or SPF/DMARC/DKIM are already correct.
Include the domain list and reason.
Otherwise choose change, false positive, or suppress 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 - 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 (do this) =====
- 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 per 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 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.
IMPORTANT: First confirm each domain below is actually used for outbound email (MX records, Microsoft 365 accepted domains, marketing platforms, etc.). If a domain does not send mail, no remediation is needed for it - skip it.
Summary: 1 domain(s) flagged for DNS mail-authentication review.
=== previant.com ===
DNS hosting: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com. Confirm this is the DNS provider where TXT records for previant.com are managed.
Issues:
- DMARC policy is weak (p=none).
- In the DNS hosting provider, open the existing DMARC TXT record at _dmarc.previant.com (host/name "_dmarc").
- Review aggregate reports (rua=) if configured and confirm legitimate mail passes SPF and/or DKIM alignment.
- Strengthen policy in stages when the client approves: p=none (monitor) → p=quarantine.
- Example interim record: v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@previant.com
Remediation: 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, then verify with a public DNS lookup tool (for example MXToolbox or nslookup).
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\The Previant Law Firm, S.C\Network Documentation\Vulnerability Scans\2026 - Q3
These email authentication findings are assessed from public DNS records, not ConnectSecure host scans. They cannot be suppressed in ConnectSecure.
Good evening Christine,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top Ten):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report – classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0–1.0, with 1.0 being most critical).
• All Vulnerabilities Report – a comprehensive list of all detected vulnerabilities (internal and external), from critical to low severity.
• Executive Summary Report – a high-level overview of your security posture and network information.
• External Scan – detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report – vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: No remediation will begin without your approval. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Chris Knospe
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.