Report files for this session are not in the quarterly folder yet. Export writes them, then you can paste OneDrive links and send the client email.
Export client reports
PEARLS for Teen Girls, Inc. Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-30 | Presenter: Josh Valin | Export set: 5 in export (Top 5) | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): No items are selected for this quote. Total Estimated Time: 0 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 5 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 Yvonne to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
Yvonne.Coleman@pearlsforteengirls.com
Yvonne.Coleman@pearlsforteengirls.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Yvonne, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 5): Complete report package: The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Josh Valin
2026 Q4 Remaining remediations
Good evening Yvonne, Following the quarterly vulnerability review for PEARLS for Teen Girls, Inc., there are no remaining remediations to report. Sincerely, Josh Valin
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: 5
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 (1364 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5094126 (or the latest available).
Affected Systems:
- PFTG-0226C (MollyPrater) - 192.168.1.12 [10.0.26100] [1365 vulns]
- PFTG-LT-22DY (HayaKhateeb) - 192.168.2.107 [10.0.26100] [741 vulns]
- PFTG-LT-2240 (KiarraRussell) - 192.168.2.117 [10.0.26100] [638 vulns]
- PFTG-LT-226F (YvonneColeman) - 192.168.2.105 [10.0.26100] [478 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [10.0.26100] [478 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): ...\PEARLS for Teen Girls\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 2
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-2024-21413
https://nvd.nist.gov/vuln/detail/CVE-2024-21413
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21413
Additional CVEs (252 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- DESKTOP-480ROGE (BeeBiloff) - 192.168.2.164 [254 vulns]
- PRTG-9204CA8 (LindseyFischer) - 192.168.2.151 [253 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): ...\PEARLS for Teen Girls\Network Documentation\Vulnerability Scans\2026 - Q3
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-2026-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (454 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5094127
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- PRTG-9204CA8 (LindseyFischer) - 192.168.2.151 [10.0.19045] [456 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): ...\PEARLS for Teen Girls\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates 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-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 (64 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- PFTG-LT-22DW (FatimaRios) - 192.168.2.136 [65 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): ...\PEARLS for Teen Girls\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Visual C++ (all versions) - Update Required
Vulnerability Remediation - Microsoft Visual C++ (all versions) - Update Required
Product/System: Microsoft Visual C++ (all versions)
Affected Systems Count: 36
Finding summary:
Microsoft Visual C++ (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.
Affected Systems:
Sorry for the long host list below (36 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- PRTG-9204CA8 (LindseyFischer) - 192.168.2.151 [12.0.40664] [6 vulns]
- DESKTOP-480ROGE (BeeBiloff) - 192.168.2.164 [12.0.40664] [6 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [11.0.51106] [6 vulns]
- PFTG-0226C (MollyPrater) - 192.168.1.12 [11.0.51106] [6 vulns]
- PFTG-LT-22F1 (AmyZwart) - 192.168.1.103 [11.0.51106] [6 vulns]
- PFTG-LT-0PJ9 (ByaBradley) - 192.168.2.116 [11.0.51106] [6 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [12.0.21005] [4 vulns]
- PFTG-0226C (MollyPrater) - 192.168.1.12 [12.0.21005] [4 vulns]
- PFTG-LT-22F1 (AmyZwart) - 192.168.1.103 [12.0.21005] [4 vulns]
- PFTG-LT-0PJ9 (ByaBradley) - 192.168.2.116 [12.0.21005] [4 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [2 vulns]
- PFTG-0226C (MollyPrater) - 192.168.1.12 [2 vulns]
- PFTG-LT-22F1 (AmyZwart) - 192.168.1.103 [2 vulns]
- PFTG-LT-0PJ9 (ByaBradley) - 192.168.2.116 [2 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [9.0.30729.6161] [2 vulns]
- PFTG-0226C (MollyPrater) - 192.168.1.12 [9.0.30729.6161] [2 vulns]
- PFTG-LT-22F1 (AmyZwart) - 192.168.1.103 [9.0.30729.6161] [2 vulns]
- PFTG-LT-0PJ9 (ByaBradley) - 192.168.2.116 [9.0.30729.6161] [2 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [10.0.40219] [2 vulns]
- PFTG-0226C (MollyPrater) - 192.168.1.12 [10.0.40219] [2 vulns]
- PFTG-LT-22F1 (AmyZwart) - 192.168.1.103 [10.0.40219] [2 vulns]
- PFTG-LT-0PJ9 (ByaBradley) - 192.168.2.116 [10.0.40219] [2 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [12.0.30501] [2 vulns]
- PFTG-0226C (MollyPrater) - 192.168.1.12 [12.0.30501] [2 vulns]
- PFTG-LT-22F1 (AmyZwart) - 192.168.1.103 [12.0.30501] [2 vulns]
- PFTG-LT-0PJ9 (ByaBradley) - 192.168.2.116 [12.0.30501] [2 vulns]
- PFTG-LT-226F (YvonneColeman) - 192.168.2.105 [12.0.21005] [2 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [9.0.30729.17] [1 vulns]
- PFTG-0226C (MollyPrater) - 192.168.1.12 [9.0.30729.17] [1 vulns]
- PFTG-LT-22F1 (AmyZwart) - 192.168.1.103 [9.0.30729.17] [1 vulns]
- PFTG-LT-0PJ9 (ByaBradley) - 192.168.2.116 [9.0.30729.17] [1 vulns]
- PFTG-LT-22GP (MaliyahBrown) - 192.168.2.110 [9.0.30729.4148] [1 vulns]
- PFTG-0226C (MollyPrater) - 192.168.1.12 [9.0.30729.4148] [1 vulns]
- PFTG-LT-22F1 (AmyZwart) - 192.168.1.103 [9.0.30729.4148] [1 vulns]
- PFTG-LT-0PJ9 (ByaBradley) - 192.168.2.116 [9.0.30729.4148] [1 vulns]
- PFTG-LT-226F (YvonneColeman) - 192.168.2.105 [12.0.30501] [1 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) =====
- Visual C++ redistributables are side-by-side - do not upgrade everything to the latest year
- An app built on one major version is tied to that version - removing it will break the app.
- Only remove a year if no app is using it.
- Patch each major version seen below with the matching vc_redist or Windows Update package
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Verify the update was successful
- 2008 (9.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2010 (10.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2012 (11.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2013 (12.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
===== 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): ...\PEARLS for Teen Girls\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Yvonne,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 5):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical).
• All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity.
• Executive Summary Report - a high-level overview of your security posture and network information.
• External Scan - detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Josh Valin
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.