Retail Fixture, LLC and Associates Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-12 | 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: RF-HP-05-2024.retailfixture, RF-WKS-09.retailfixture (jcwoodward), RF-WKS-11.retailfixture (redwards) Estimated Time of Remediation: 2 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Windows 10 (all versions) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: RF-WKS-04.retailfixture Estimated Time of Remediation: 1 hour 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: jacks-workpc.retailfixture (jcwoodward) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: qnap Remediation Options: Update firmware to the current vendor release, or replace the device if it is out of support Target Machines: RF-QNAP1 Estimated Time of Remediation: 1 hour Remediation Method: Update firmware from the vendor during a maintenance window. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Google Chrome Remediation Options: Update to version 155.0.8059.40 or later; uninstall if not in use Target Machines: RF-WKS-04.retailfixture, RF-CAD4-LT.retailfixture (mlewis), RF-WKS-12.retailfixture (swarner), HEATHER-W10-HP.retailfixture (hmitchell), RF-WKS-05.retailfixture (dhaschker), RF-WKS-06.retailfixture (smitchell), RF-HP11-WIN10.retailfixture (dmeyer), RF-DELL-002.retailfixture (jkirkorian) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat X Standard - English, Français, Deutsch Remediation Options: Update to the current version; uninstall if not in use Target Machines: RF-HP11-WIN10.retailfixture (dmeyer) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Teams Remediation Options: Update to version 26260.1701.5139.3736 or later; uninstall if not in use Target Machines: RF-WKS-04.retailfixture, HEATHER-W10-HP.retailfixture (hmitchell), RF-WKS-06.retailfixture (smitchell), RF-WKS-05.retailfixture (dhaschker), RF-DELL-002.retailfixture (jkirkorian) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Defender Remediation Options: Update to version 4.18.26060.3008 or later; uninstall if not in use Target Machines: RF-WKS-15.retailfixture, RF-WKS-14.retailfixture, RF-WKS-13.retailfixture 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: HEATHER-W10-HP.retailfixture (hmitchell), jacks-workpc.retailfixture (jcwoodward), OPENCNC-56DE1RN.retailfixture (onsrud2), RF-CAD1-LT.retailfixture (BVermilyer), RF-CAD2-LT.retailfixture (mjarmuskiewicz), RF-CAD4-LT.retailfixture (mlewis), RF-DC01.retailfixture (rradmin), RF-DC02.retailfixture (rradmin), RF-DELL-002.retailfixture (jkirkorian), RF-FILE01.retailfixture (rradmin), RF-HOST-01 (Administrator), RF-HP-05-2024.retailfixture, RF-HP11-WIN10.retailfixture (dmeyer), RFKatieWork.retailfixture (kkupper), RF-SQL.retailfixture (rradmin), RF-SW-01.retailfixture, RF-UTIL.retailfixture, RF-WKS-04.retailfixture, RF-WKS-05.retailfixture (dhaschker), RF-WKS-06.retailfixture (smitchell), RF-WKS-08.retailfixture (cpanyk), RF-WKS-09.retailfixture (jcwoodward), RF-WKS-10.retailfixture (arichter), RF-WKS-11.retailfixture (redwards), RF-WKS-12.retailfixture (swarner), RF-WKS-13.retailfixture, RF-WKS-14.retailfixture, RF-WKS-15.retailfixture Estimated Time of Remediation: 4 hours Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: WinVerifyTrust Signature Validation Vulnerability Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: jacks-workpc.retailfixture (jcwoodward), OPENCNC-56DE1RN.retailfixture (onsrud2), RF-CAD1-LT.retailfixture (BVermilyer), RF-CAD2-LT.retailfixture (mjarmuskiewicz), RF-CAD4-LT.retailfixture (mlewis), RF-DC01.retailfixture (rradmin), RF-DC02.retailfixture (rradmin), RF-DELL-002.retailfixture (jkirkorian), RF-FILE01.retailfixture (rradmin), RF-HOST-01 (Administrator), RF-HP11-WIN10.retailfixture (dmeyer), RFKatieWork.retailfixture (kkupper), RF-SQL.retailfixture (rradmin), RF-SW-01.retailfixture, RF-UTIL.retailfixture, RF-WKS-05.retailfixture (dhaschker), RF-WKS-06.retailfixture (smitchell), RF-WKS-08.retailfixture (cpanyk), RF-WKS-09.retailfixture (jcwoodward), RF-WKS-10.retailfixture (arichter), RF-WKS-11.retailfixture (redwards), RF-WKS-12.retailfixture (swarner), RF-WKS-13.retailfixture, RF-WKS-14.retailfixture, RF-WKS-15.retailfixture Estimated Time of Remediation: 4 hours Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Total Estimated Time: 16 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 Rhonda to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
redwards@retailfixture.com
redwards@retailfixture.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Rhonda, 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 Rhonda, Following the quarterly vulnerability review for Retail Fixture, LLC and Associates, 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: 3
Finding summary:
Windows 11 (all versions) is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2025-21298
https://nvd.nist.gov/vuln/detail/CVE-2025-21298
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298
Additional CVEs (2346 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129242. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5129195 (or the latest available).
Affected Systems:
- RF-HP-05-2024.retailfixture - 192.168.100.111 [10.0.22631] [1901 vulns]
- RF-WKS-09.retailfixture (jcwoodward) - 192.168.0.122 [10.0.26100] [1658 vulns]
- RF-WKS-11.retailfixture (redwards) - 192.168.0.131 [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): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Product/System: Windows 10 (all versions)
Affected Systems Count: 1
Finding summary:
Windows 10 (all versions) is missing required updates on the listed hosts.
Apply remaining quality/security updates for the current build via RMM or Windows Update.
Windows 10 is EOL. Do not force a Windows 11 upgrade from this ticket. After those updates, a Windows 11 / new workstation project is a Sales quote and vCIO conversation, then Security suppression of the current OS.
CVE references:
CVE-2025-60724
https://nvd.nist.gov/vuln/detail/CVE-2025-60724
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-60724
Additional CVEs (1472 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5122878 (or the latest available).
Affected Systems:
- RF-WKS-04.retailfixture - 192.168.0.158 [10.0.19045] [1473 vulns]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
- Windows 10 is EOL: still apply any remaining quality/security updates first; for a Windows 11 / new workstation project, generate a quote (inform the client that you are doing so), contact vCIO so they can discuss it with the client, then escalate to Security for suppression of the current OS
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
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: 1
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-2025-53766
https://nvd.nist.gov/vuln/detail/CVE-2025-53766
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53766
Additional CVEs (385 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- jacks-workpc.retailfixture (jcwoodward) - 192.168.1.132 [387 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) =====
- 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): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - qnap - Firmware Update Required
Vulnerability Remediation - qnap - Firmware Update Required
Product/System: qnap
Affected Systems Count: 1
Finding summary:
qnap firmware/software may be outdated on the listed device(s).
Confirm the real vendor, model, and firmware build on the device first.
Check the vendor security advisory for this CVE and model.
If the vendor documents not affected or already fixed: escalate to Security as a false positive with details and the vendor documentation link.
Otherwise apply manufacturer firmware via the vendor tool or device admin.
Coordinate an outage/reboot window.
CVE references:
CVE-2024-48859
https://nvd.nist.gov/vuln/detail/CVE-2024-48859
Vendor advisory:
https://www.qnap.com/en/security-advisory/qsa-24-49
Additional CVEs (112 more) are listed in the Client Folder report.
Affected Systems:
- RF-QNAP1 - 192.168.0.230 [113 vulns]
Quick-check each device first.
Then stop (escalate to Security as a false positive) if:
- the device is not present
- already at/above the minimum version to reach
- the finding does not match the installed model/firmware
- the vendor documents this CVE as not applicable or already fixed
Include details and the vendor documentation link.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply firmware / device software (default when keeping the device)
- Apply manufacturer firmware to the version listed under Minimum version to reach (or the latest available for that model).
- If the product line is EOL, still check for and apply the latest available final firmware for that model before anything else.
B. Device not needed - retire / replace / remove from service
- Only if the device should not remain on the network.
C. EOL / no secure path - notify the client, then escalate to Security for suppression
- After confirming the device is on the latest available firmware for that model (or no further update exists), notify the client of residual risk, record discussion notes to the client, then escalate to Security for suppression.
- Document model, current firmware, and that latest-available was checked.
- Do not request suppression until latest-available was checked and the client was notified.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree an outage window with the client before applying firmware - the device reboots.
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) =====
- If a support contract has lapsed, do not apply a software or firmware update.
- Notify the client that updates cannot proceed until support is renewed or a replacement is approved
- Create a Sales quote for support renewal, or for replacement/upgrade if the product is also EOL
- Open a vendor case after entitlement is in place (or to confirm support status)
- 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
NVD / advisory context:
https://www.qnap.com/en/security-advisory/qsa-24-49 | An improper authentication vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers to compromise the security of the system.
We have already fixed the vulnerability in the following versions:
QTS 5.1.9.2954 build 20241120 and later
QTS 5.2.2.2950 build 20241114 and later
QuTS hero h5.1.9.2954 build 20241120 and… | https://www.qnap.com/en/security-advisory/…
===== 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): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Google Chrome - Update Required
Vulnerability Remediation - Google Chrome - Update Required
Product/System: Google Chrome
Affected Systems Count: 8
Finding summary:
Google Chrome 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-103626
https://nvd.nist.gov/vuln/detail/CVE-2026-103626
Vendor security center:
https://chromereleases.googleblog.com/
Additional CVEs (257 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 155.0.8059.40 (or the latest available).
Affected Systems:
- RF-WKS-04.retailfixture - 192.168.0.158 [258 vulns]
- RF-CAD4-LT.retailfixture (mlewis) - 192.168.0.121 [130 vulns]
- RF-WKS-12.retailfixture (swarner) - 192.168.100.107 [130 vulns]
- HEATHER-W10-HP.retailfixture (hmitchell) - 192.168.0.132 [60 vulns]
- RF-WKS-05.retailfixture (dhaschker) - 192.168.0.133 [60 vulns]
- RF-WKS-06.retailfixture (smitchell) - 192.168.100.109 [60 vulns]
- RF-HP11-WIN10.retailfixture (dmeyer) - 192.168.0.118 [60 vulns]
- RF-DELL-002.retailfixture (jkirkorian) - 192.168.0.124 [60 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- 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.
- Chrome updates via Google Update (background); relaunch may be needed to apply a downloaded update
- If still behind: check Chrome update policy / Google Update scheduled tasks
- 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): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Adobe Acrobat X Standard - English, Français, Deutsch - Update Required
Vulnerability Remediation - Adobe Acrobat X Standard - English, Français, Deutsch - Update Required
Product/System: Adobe Acrobat X Standard - English, Français, Deutsch
Affected Systems Count: 1
Finding summary:
Adobe Acrobat X Standard - English, Français, Deutsch 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-2017-11293
https://nvd.nist.gov/vuln/detail/CVE-2017-11293
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (68 more) are listed in the Client Folder report.
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:
- RF-HP11-WIN10.retailfixture (dmeyer) - 192.168.0.118 [70 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm Acrobat Pro vs Adobe Reader (and 32 vs 64) on each host before choosing an installer
- Update to the reported remediation target
- RMM/automated patching when deployed
- Versions 20.x and 21.x are EOL - full upgrade to a supported track, not a security patch on 20/21
- Backstage (CMD/PS): deploy matching Acrobat installer/package (Admin Console when enterprise)
- Live user session only if needed: Help > Check for Updates
- Verify version 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): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 5
Finding summary:
Microsoft Teams is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2023-4863
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26260.1701.5139.3736 (or the latest available).
Affected Systems:
- RF-WKS-04.retailfixture - 192.168.0.158 [7 vulns]
- HEATHER-W10-HP.retailfixture (hmitchell) - 192.168.0.132 [7 vulns]
- RF-WKS-06.retailfixture (smitchell) - 192.168.100.109 [7 vulns]
- RF-WKS-05.retailfixture (dhaschker) - 192.168.0.133 [7 vulns]
- RF-DELL-002.retailfixture (jkirkorian) - 192.168.0.124 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm flagged Teams version - Classic is not always the source
- Classic Teams is sometimes a per-user install
- A user who has not logged into this workstation in a while, or is not the primary user, can still have Classic leftover
- Run the RMM Teams Classic cleanup script for those leftover per-user installs
- Classic/duplicate suspected: R-Security - Teams Classic Cleanup Remediation (Scripts > RR Custom > RR Custom - R-Security Remediation > R-Security - Teams Classic Cleanup Remediation)
- Current Teams behind: automated patching/RMM first
- Live user session only if needed: three-dot menu > Settings > About Teams
- Backstage (CMD/PS): RMM script / installer only - not the Teams UI
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Defender - Update Required
Vulnerability Remediation - Microsoft Defender - Update Required
Product/System: Microsoft Defender
Affected Systems Count: 3
Finding summary:
Microsoft Defender is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-33825
https://nvd.nist.gov/vuln/detail/CVE-2026-33825
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33825
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.18.26060.3008 (or the latest available).
Affected Systems:
- RF-WKS-15.retailfixture - 192.168.100.112 [3 vulns]
- RF-WKS-14.retailfixture - 192.168.100.113 [3 vulns]
- RF-WKS-13.retailfixture - 192.168.100.114 [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)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Check Windows Security on each host: is another EDR/AV active (SentinelOne, Huntress, Webroot, Bitdefender, or similar)?
- If yes and Defender real-time protection is off: that is expected. This finding is a Defender version, not the live AV
- Do not turn Defender real-time protection back on next to that EDR
- If Defender is still the AV, or the platform/service is still running: update platform/signatures via Windows Update or Defender management policy
- Check RMM patch status if patch management is deployed
- Confirm engine/platform version after update
- Then stop if:
- Another EDR is healthy and Defender RTP is off (version/signature age only): notify the client, record discussion notes, escalate to Security for suppression
- Update failed because Defender is fully disabled: same path - the EDR is the control; escalate to Security for suppression
- If the CVE is in a Defender driver or service that is still loaded: update the Defender platform anyway
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Speculative Store Bypass - Updates Required
Vulnerability Remediation - Speculative Store Bypass - Configuration Change Required
Product/System: Speculative Store Bypass
Affected Systems Count: 28
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:
Sorry for the long host list below (28 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- HEATHER-W10-HP.retailfixture (hmitchell) - 192.168.0.132 [1 vulns]
- jacks-workpc.retailfixture (jcwoodward) - 192.168.1.132 [1 vulns]
- OPENCNC-56DE1RN.retailfixture (onsrud2) - 192.168.0.135 [1 vulns]
- RF-CAD1-LT.retailfixture (BVermilyer) - 10.0.0.2 [1 vulns]
- RF-CAD2-LT.retailfixture (mjarmuskiewicz) - 192.168.0.129 [1 vulns]
- RF-CAD4-LT.retailfixture (mlewis) - 192.168.0.121 [1 vulns]
- RF-DC01.retailfixture (rradmin) - 192.168.0.30 [1 vulns]
- RF-DC02.retailfixture (rradmin) - 192.168.0.35 [1 vulns]
- RF-DELL-002.retailfixture (jkirkorian) - 192.168.0.124 [1 vulns]
- RF-FILE01.retailfixture (rradmin) - 192.168.0.40 [1 vulns]
- RF-HOST-01 (Administrator) - 192.168.0.50 [1 vulns]
- RF-HP-05-2024.retailfixture - 192.168.100.111 [1 vulns]
- RF-HP11-WIN10.retailfixture (dmeyer) - 192.168.0.118 [1 vulns]
- RFKatieWork.retailfixture (kkupper) - 192.168.100.106 [1 vulns]
- RF-SQL.retailfixture (rradmin) - 192.168.0.41 [1 vulns]
- RF-SW-01.retailfixture - 192.168.0.42 [1 vulns]
- RF-UTIL.retailfixture - 192.168.0.43 [1 vulns]
- RF-WKS-04.retailfixture - 192.168.0.158 [1 vulns]
- RF-WKS-05.retailfixture (dhaschker) - 192.168.0.133 [1 vulns]
- RF-WKS-06.retailfixture (smitchell) - 192.168.100.109 [1 vulns]
- RF-WKS-08.retailfixture (cpanyk) - 192.168.0.137 [1 vulns]
- RF-WKS-09.retailfixture (jcwoodward) - 192.168.0.122 [1 vulns]
- RF-WKS-10.retailfixture (arichter) - 192.168.100.108 [1 vulns]
- RF-WKS-11.retailfixture (redwards) - 192.168.0.131 [1 vulns]
- RF-WKS-12.retailfixture (swarner) - 192.168.100.107 [1 vulns]
- RF-WKS-13.retailfixture - 192.168.100.114 [1 vulns]
- RF-WKS-14.retailfixture - 192.168.100.113 [1 vulns]
- RF-WKS-15.retailfixture - 192.168.100.112 [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): ...\Retail Fixture, LLC and Associates\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: 25
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:
Sorry for the long host list below (25 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- jacks-workpc.retailfixture (jcwoodward) - 192.168.1.132 [1 vulns]
- OPENCNC-56DE1RN.retailfixture (onsrud2) - 192.168.0.135 [1 vulns]
- RF-CAD1-LT.retailfixture (BVermilyer) - 10.0.0.2 [1 vulns]
- RF-CAD2-LT.retailfixture (mjarmuskiewicz) - 192.168.0.129 [1 vulns]
- RF-CAD4-LT.retailfixture (mlewis) - 192.168.0.121 [1 vulns]
- RF-DC01.retailfixture (rradmin) - 192.168.0.30 [1 vulns]
- RF-DC02.retailfixture (rradmin) - 192.168.0.35 [1 vulns]
- RF-DELL-002.retailfixture (jkirkorian) - 192.168.0.124 [1 vulns]
- RF-FILE01.retailfixture (rradmin) - 192.168.0.40 [1 vulns]
- RF-HOST-01 (Administrator) - 192.168.0.50 [1 vulns]
- RF-HP11-WIN10.retailfixture (dmeyer) - 192.168.0.118 [1 vulns]
- RFKatieWork.retailfixture (kkupper) - 192.168.100.106 [1 vulns]
- RF-SQL.retailfixture (rradmin) - 192.168.0.41 [1 vulns]
- RF-SW-01.retailfixture - 192.168.0.42 [1 vulns]
- RF-UTIL.retailfixture - 192.168.0.43 [1 vulns]
- RF-WKS-05.retailfixture (dhaschker) - 192.168.0.133 [1 vulns]
- RF-WKS-06.retailfixture (smitchell) - 192.168.100.109 [1 vulns]
- RF-WKS-08.retailfixture (cpanyk) - 192.168.0.137 [1 vulns]
- RF-WKS-09.retailfixture (jcwoodward) - 192.168.0.122 [1 vulns]
- RF-WKS-10.retailfixture (arichter) - 192.168.100.108 [1 vulns]
- RF-WKS-11.retailfixture (redwards) - 192.168.0.131 [1 vulns]
- RF-WKS-12.retailfixture (swarner) - 192.168.100.107 [1 vulns]
- RF-WKS-13.retailfixture - 192.168.100.114 [1 vulns]
- RF-WKS-14.retailfixture - 192.168.100.113 [1 vulns]
- RF-WKS-15.retailfixture - 192.168.100.112 [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): ...\Retail Fixture, LLC and Associates\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Rhonda,
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.