Fiebing Company Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-27 | Presenter: Chris Knospe | Export set: 9 in export (Top 9) | 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: Fiebing-Lab-919 (JacobEvans), HP-LT-08-2025B (ClaytonChase), HP-DT-08-2025A (Shipping), HP-LT-08-2025A (ClaytonChase), HP-LT-08-2025C (DavidHall), HP-08-2024 (JasonChase), FIEBING-MGMT-RR, HP-DT-08-2025B (DustinMoon), HP-LT-01-2023 (Shipping) Estimated Time of Remediation: 2 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft 365 Apps for business - en-us Remediation Options: Update to the current version; uninstall if not in use Target Machines: HP-LT-08-2025A (ClaytonChase), HP-LT-08-2025B (ClaytonChase), HP-LT-11-2025 (IanEvans), HP-LT-08-2025C (DavidHall), HP-DT-08-2025B (DustinMoon), FIEBING-MGMT-RR, HP-DT-08-2025A (Shipping) 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 10.0.12 or later; uninstall if not in use Target Machines: HP-LT-08-2025B (ClaytonChase) Estimated Time of Remediation: 0.5 hours Remediation Method: Deploy the matching runtime installer via RMM. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Mozilla Firefox Remediation Options: Update to version 156.0.1 or later; uninstall if not in use Target Machines: DESKTOP-2DHEHFT (Production3) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinVerifyTrust Signature Validation Vulnerability Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: DESKTOP-2DHEHFT (Production3), fb-ws-0326 (MikeHesprich), Fiebing-Lab-919 (JacobEvans), FIEBING-MGMT-RR, FIEBING-PC-220 (danWagner), HP-06-018 (ShafiqMonshi), HP-08-2024 (JasonChase), HP-DT-01-2023 (FiebingMaintenance), HP-DT-08-2025A (Shipping), HP-DT-08-2025B (DustinMoon), HP-LT-01-2023 (Shipping), HP-LT-08-2025A (ClaytonChase), HP-LT-08-2025B (ClaytonChase), HP-LT-08-2025C (DavidHall), HP-LT-11-2025 (IanEvans) Estimated Time of Remediation: 2 hours Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: Speculative Store Bypass Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: DESKTOP-2DHEHFT (Production3), fb-ws-0326 (MikeHesprich), Fiebing-Lab-919 (JacobEvans), FIEBING-MGMT-RR, FIEBING-PC-220 (danWagner), HP-06-018 (ShafiqMonshi), HP-08-2024 (JasonChase), HP-DT-01-2023 (FiebingMaintenance), HP-DT-08-2025A (Shipping), HP-DT-08-2025B (DustinMoon), HP-LT-01-2023 (Shipping), HP-LT-08-2025A (ClaytonChase), HP-LT-08-2025B (ClaytonChase), HP-LT-08-2025C (DavidHall), HP-LT-11-2025 (IanEvans) Estimated Time of Remediation: 2 hours Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: Intel(R) Rapid Storage Technology Remediation Options: Update to version 18.7.6.1010.3 or later; uninstall if not in use Target Machines: HP-06-018 (ShafiqMonshi) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: powershellv2 Remediation Options: Update to the current version; uninstall if not in use Target Machines: HP-06-018 (ShafiqMonshi) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Event-Log-Crasher Remediation Options: Update to the current version; uninstall if not in use Target Machines: HP-06-018 (ShafiqMonshi) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 9 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 9 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 Scott to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
skravetz@fiebing.com
skravetz@fiebing.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Scott, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 9): Open Top 9 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 Scott, Following the quarterly vulnerability review for Fiebing Company, 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: 9
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-60724
https://nvd.nist.gov/vuln/detail/CVE-2025-60724
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-60724
Additional CVEs (1839 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129195. Apply the latest patch
- (1 end-of-life component notices omitted).
Affected Systems:
- Fiebing-Lab-919 (JacobEvans) - 10.0.0.146 [10.0.26100] [1840 vulns]
- HP-LT-08-2025B (ClaytonChase) - 10.0.0.61 [10.0.26100] [1658 vulns]
- HP-DT-08-2025A (Shipping) - 10.0.0.62 [10.0.26100] [1658 vulns]
- HP-LT-08-2025A (ClaytonChase) - 192.168.12.124 [10.0.26100] [1658 vulns]
- HP-LT-08-2025C (DavidHall) - 10.0.0.143 [10.0.26100] [1658 vulns]
- HP-08-2024 (JasonChase) - 10.0.0.145 [10.0.26100] [1658 vulns]
- FIEBING-MGMT-RR - 10.0.0.165 [10.0.26100] [1658 vulns]
- HP-DT-08-2025B (DustinMoon) - 10.0.0.160 [10.0.26100] [1658 vulns]
- HP-LT-01-2023 (Shipping) - 10.0.0.6 [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): ...\Fiebing Company\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Update Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Update Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 7
Finding summary:
Microsoft 365 Apps for business - 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-21509
https://nvd.nist.gov/vuln/detail/CVE-2026-21509
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21509
Additional CVEs (206 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5129195. Apply the latest patch.
Affected Systems:
- HP-LT-08-2025A (ClaytonChase) - 192.168.12.124 [207 vulns]
- HP-LT-08-2025B (ClaytonChase) - 10.0.0.61 [200 vulns]
- HP-LT-11-2025 (IanEvans) - 10.0.0.137 [88 vulns]
- HP-LT-08-2025C (DavidHall) - 10.0.0.143 [88 vulns]
- HP-DT-08-2025B (DustinMoon) - 10.0.0.160 [88 vulns]
- FIEBING-MGMT-RR - 10.0.0.165 [88 vulns]
- HP-DT-08-2025A (Shipping) - 10.0.0.62 [88 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): ...\Fiebing Company\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: 1
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-71328
https://nvd.nist.gov/vuln/detail/CVE-2026-71328
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-71328
Additional CVEs (10 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.0.12 (or the latest available).
Affected Systems:
- HP-LT-08-2025B (ClaytonChase) - 10.0.0.61 [10.0.9] [33 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the redistributable/runtime is not present or is already at/above the minimum version to reach for that major version.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- .NET Framework and modern .NET (.NET 5+) are not interchangeable
- An app built on one major version is tied to that version - removing it will break the app.
- Update each runtime line via WU/vendor installer; uninstall only when unused and verified
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET 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): ...\Fiebing Company\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Mozilla Firefox - Update Required
Vulnerability Remediation - Mozilla Firefox - Update Required
Product/System: Mozilla Firefox
Affected Systems Count: 1
Finding summary:
Mozilla Firefox is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2011-3389
https://nvd.nist.gov/vuln/detail/CVE-2011-3389
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 156.0.1 (or the latest available).
Affected Systems:
- DESKTOP-2DHEHFT (Production3) - 10.0.0.54 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Firefox updates in background; relaunch may be needed to apply a downloaded update
- If still behind: check Firefox update settings / Maintenance Service
- ESR and release can both be present - update the channel that is installed
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Fiebing Company\Network Documentation\Vulnerability Scans\2026 - Q3
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: 15
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:
- DESKTOP-2DHEHFT (Production3) - 10.0.0.54 [1 vulns]
- fb-ws-0326 (MikeHesprich) - 10.0.0.75 [1 vulns]
- Fiebing-Lab-919 (JacobEvans) - 10.0.0.146 [1 vulns]
- FIEBING-MGMT-RR - 10.0.0.165 [1 vulns]
- FIEBING-PC-220 (danWagner) - 10.0.0.122 [1 vulns]
- HP-06-018 (ShafiqMonshi) - 10.0.0.163 [1 vulns]
- HP-08-2024 (JasonChase) - 10.0.0.145 [1 vulns]
- HP-DT-01-2023 (FiebingMaintenance) - 10.0.0.107 [1 vulns]
- HP-DT-08-2025A (Shipping) - 10.0.0.62 [1 vulns]
- HP-DT-08-2025B (DustinMoon) - 10.0.0.160 [1 vulns]
- HP-LT-01-2023 (Shipping) - 10.0.0.6 [1 vulns]
- HP-LT-08-2025A (ClaytonChase) - 192.168.12.124 [1 vulns]
- HP-LT-08-2025B (ClaytonChase) - 10.0.0.61 [1 vulns]
- HP-LT-08-2025C (DavidHall) - 10.0.0.143 [1 vulns]
- HP-LT-11-2025 (IanEvans) - 10.0.0.137 [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): ...\Fiebing Company\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Speculative Store Bypass - Updates Required
Vulnerability Remediation - Speculative Store Bypass - Configuration Change Required
Product/System: Speculative Store Bypass
Affected Systems Count: 15
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:
- DESKTOP-2DHEHFT (Production3) - 10.0.0.54 [1 vulns]
- fb-ws-0326 (MikeHesprich) - 10.0.0.75 [1 vulns]
- Fiebing-Lab-919 (JacobEvans) - 10.0.0.146 [1 vulns]
- FIEBING-MGMT-RR - 10.0.0.165 [1 vulns]
- FIEBING-PC-220 (danWagner) - 10.0.0.122 [1 vulns]
- HP-06-018 (ShafiqMonshi) - 10.0.0.163 [1 vulns]
- HP-08-2024 (JasonChase) - 10.0.0.145 [1 vulns]
- HP-DT-01-2023 (FiebingMaintenance) - 10.0.0.107 [1 vulns]
- HP-DT-08-2025A (Shipping) - 10.0.0.62 [1 vulns]
- HP-DT-08-2025B (DustinMoon) - 10.0.0.160 [1 vulns]
- HP-LT-01-2023 (Shipping) - 10.0.0.6 [1 vulns]
- HP-LT-08-2025A (ClaytonChase) - 192.168.12.124 [1 vulns]
- HP-LT-08-2025B (ClaytonChase) - 10.0.0.61 [1 vulns]
- HP-LT-08-2025C (DavidHall) - 10.0.0.143 [1 vulns]
- HP-LT-11-2025 (IanEvans) - 10.0.0.137 [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): ...\Fiebing Company\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Intel(R) Rapid Storage Technology - Update Required
Vulnerability Remediation - Intel(R) Rapid Storage Technology - Update Required
Product/System: Intel(R) Rapid Storage Technology
Affected Systems Count: 1
Finding summary:
Intel(R) Rapid Storage Technology 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-2021-0104
https://nvd.nist.gov/vuln/detail/CVE-2021-0104
Vendor security center:
https://www.intel.com/content/www/us/en/security-center/default.html
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 18.7.6.1010.3 (or the latest available).
Affected Systems:
- HP-06-018 (ShafiqMonshi) - 10.0.0.163 [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Fiebing Company\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - powershellv2 - Update Required
Vulnerability Remediation - powershellv2 - Update Required
Product/System: powershellv2
Affected Systems Count: 1
Finding summary:
powershellv2 is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
- Disable Windows PowerShell 2.0 on the system (or the latest available).
Affected Systems:
- HP-06-018 (ShafiqMonshi) - 10.0.0.163 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Fiebing Company\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Event-Log-Crasher - Update Required
Vulnerability Remediation - Event-Log-Crasher - Update Required
Product/System: Event-Log-Crasher
Affected Systems Count: 1
Finding summary:
Event-Log-Crasher is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
- Unofficial security patches (or the latest available).
Affected Systems:
- HP-06-018 (ShafiqMonshi) - 10.0.0.163 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Fiebing Company\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Scott,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 9):
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.