Broesch & Co., S.C. Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-19 | Presenter: Andrew Harkins | Export set: 6 in export (Top 6) | 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 6 vulnerabilities docx report - Ticket #1907403: Vulnerability Remediation - Windows 11 (all versions) - Updates Required - Ticket #1907404: Vulnerability Remediation - Microsoft .NET (all versions) - Update Required - Ticket #1907405: Vulnerability Remediation - Microsoft Teams - Application Update Required - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with Mike to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
mike@broeschcpa.com
mike@broeschcpa.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Mike, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 6): Open Top 6 report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Andrew Harkins
2026 Q4 Remaining remediations
Good evening Mike, Following the quarterly vulnerability review for Broesch & Co., S.C., there are no remaining remediations to report. Sincerely, Andrew Harkins
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: 13
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 (2695 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5127648. Update to version 8.0.32 (or the latest available)
- Apply Windows Update KB5127648. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5127648. Apply the latest patch. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted).
Affected Systems:
- BROESCH-AVD (CareyStruebing) - 10.250.0.4 [10.0.26200] [2693 vulns]
- Bro-DT-32076 - 10.0.10.77 [10.0.26100] [2660 vulns]
- BRO-LT-29052 (CareyStruebing) - 192.168.60.102 [10.0.26100] [2660 vulns]
- HP80AC56 - 10.0.10.67 [Not Available] [2660 vulns]
- BAC-5CD61213CX - 10.0.10.69 [10.0.26200] [1631 vulns]
- BAC-1H86153MDP (MikeHammond) - 10.0.10.75 [10.0.26200] [999 vulns]
- BAC-1H86153M85 (AnthonyPaulis) - 10.0.10.76 [10.0.26200] [999 vulns]
- BAC-1H86153MDH (PaulBroesch) - 192.168.0.142 [10.0.26200] [999 vulns]
- BAC-1H86153MDN (RachelleKnudtson) - 192.168.0.55 [10.0.26200] [999 vulns]
- BAC-1H86153MDW (TeriMacGuire) - 192.168.1.25 [10.0.26200] [999 vulns]
- BAC-SCAN - 10.0.10.60 [10.0.26200] [999 vulns]
- BAC-5CD61213F2 (CareyStruebing) - 10.0.10.63 [10.0.26200] [999 vulns]
- bac-5cd61212tq - 10.0.10.64 [10.0] [999 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): ...\Broesch & Co., S.C\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Product/System: Microsoft .NET (all versions)
Affected Systems Count: 7
Finding summary:
Microsoft .NET (all versions) is outdated on the listed hosts.
These runtimes update within the same major version. An app built on one major version is tied to that version - removing it will break the app.
CVE references:
CVE-2023-36049
https://nvd.nist.gov/vuln/detail/CVE-2023-36049
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36049
Additional CVEs (74 more) are listed in the Client Folder report.
Affected Systems:
- BAC-1H86153MDW (TeriMacGuire) - 192.168.1.25 [6.0.10] [108 vulns]
- BAC-1H86153MDP (MikeHammond) - 10.0.10.75 [6.0.10] [108 vulns]
- BAC-5CD61213F2 (CareyStruebing) - 10.0.10.63 [10.0.26200] [40 vulns]
- BROESCH-AVD (CareyStruebing) - 10.250.0.4 [10.0.26200] [40 vulns]
- BRO-LT-29052 (CareyStruebing) - 192.168.60.102 [3.1.32] [3 vulns]
- BRO-LT-29052 (CareyStruebing) - 192.168.60.102 [6.0.36] [3 vulns]
- HP80AC56 - 10.0.10.67 [6.0.36] [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the redistributable/runtime is not present or is already at/above the minimum version to reach for that major version.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- .NET Framework and modern .NET (.NET 5+) are not interchangeable
- An app built on one major version is tied to that version - removing it will break the app.
- Update each runtime line via WU/vendor installer; uninstall only when unused and verified
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET Core 3.x: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 6: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 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): ...\Broesch & Co., S.C\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: 1
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.1717.5229.7049 (or the latest available).
Affected Systems:
- BRO-LT-29052 (CareyStruebing) - 192.168.60.102 [7 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): ...\Broesch & Co., S.C\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: 1
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)
- Update to version 1.1.26080.3 (or the latest available). Update to version 4.18.26060.3008 (or the latest available).
Affected Systems:
- BAC-5CD61213CX - 10.0.10.69 [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): ...\Broesch & Co., S.C\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - FortiClient VPN - Update Required
Vulnerability Remediation - FortiClient VPN - Update Required
Product/System: FortiClient VPN
Affected Systems Count: 1
Finding summary:
FortiClient VPN is a VPN client on the listed hosts.
If the site has a FortiGate / Fortinet firewall, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it. Use the vendor installer from support.fortinet.com. Automated / RMM updates have failed for FortiClient VPN in the past.
CVE references:
CVE-2024-3661
https://nvd.nist.gov/vuln/detail/CVE-2024-3661
Vendor security center:
https://fortiguard.fortinet.com/psirt
Additional CVEs (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.4.5 (or the latest available).
Affected Systems:
- HP80AC56 - 10.0.10.67 [12 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has a FortiGate / Fortinet firewall: download from support.fortinet.com and run the vendor installer to the version listed under Minimum version to reach (or the latest available). Do not rely on RMM for FortiClient VPN.
- Coordinate the FortiClient version with site FortiGate firmware before upgrading.
- If the site does not have a FortiGate / Fortinet firewall: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the update path.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- FortiClient VPN: manual vendor installer recommended
This VPN is expected if the site has a FortiGate / Fortinet firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it.
- Automated / RMM updates have failed for FortiClient VPN in the past - do not rely on them until a better path exists
- Do not use winget or automated patching for this product
- Download updated installer from support.fortinet.com
- Transfer via ScreenConnect file transfer
- CMD console (SYSTEM OK): FortiClientVPNSetup_x.x.x.exe /quiet /norestart
- Coordinate version with site FortiGate firmware before upgrading
- Verify version after install
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Broesch & Co., S.C\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Office Access database engine 2007 (English) - Updates Required
Vulnerability Remediation - Microsoft Office Access database engine 2007 (English) - Updates Required
Product/System: Microsoft Office Access database engine 2007 (English)
Affected Systems Count: 6
Finding summary:
Microsoft Office Access database engine 2007 (English) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
Multiple bundled scanner entries report end-of-life components; patch within each runtime line per remediation guidance (or the latest available).
Affected Systems:
- BAC-1H86153MDW (TeriMacGuire) - 192.168.1.25 [1 vulns]
- BRO-LT-29052 (CareyStruebing) - 192.168.60.102 [1 vulns]
- BAC-5CD61213F2 (CareyStruebing) - 10.0.10.63 [1 vulns]
- HP80AC56 - 10.0.10.67 [1 vulns]
- BAC-5CD61213CX - 10.0.10.69 [1 vulns]
- BAC-1H86153MDP (MikeHammond) - 10.0.10.75 [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) =====
- 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): ...\Broesch & Co., S.C\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Mike,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 6):
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,
Andrew Harkins
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.