✅ Fixes in User Experience and Functions

🔧 Admin

Users: The "Department Manager" dropdown in Admin > Users now only displays active users during user creation or edits.

🛡️ Compliance

Compliance Assessment: Fixed an issue where marking a question as “Not Applicable” did not clear previous dropdown answers in the generated report.

Shadow IT: Enhanced Risk Profiles table layout and interaction for clearer risk visibility and smoother experience.

🌐 Dark Web

Setup Dark Web Monitor: Improved handling of company names with commas to prevent unintended name splitting.

📊 Main Dashboard

Target Risk Matrix: Fixed an issue where all vulnerability risk grades incorrectly appeared as "F" in the modal. Grades now correctly align with CSV export data.

📁 Mitigation

Create Mitigation & Sub-Mitigation: Disabled users are now excluded from the “Assign Plan To” dropdown to avoid invalid assignments.

My Mitigation Plans:

Resolved an issue preventing completion of Sensitive Data plans when no actions remained.

Fixed a bug where targets and root causes failed to load after switching to an Unauthenticated Vulnerability plan via the “Change Plan” dropdown.

The Risk Level filter in the Review & Perform an Action modal now correctly displays CVEs by severity level.

🧩 MSP

Central Vulnerability Manager: The Patch History modal now auto-refreshes after patch scheduling to reflect the latest status immediately.

📄 Report Builder

Vulnerability Scan Duration Report: Resolved a bug where remediated root causes appeared under Pending Remediations. Reports now show resolved items in the correct section based on latest scan data.

🔍 Vulnerability Scan

Dashboard: The Total CVE Count in the Vulnerability Summary by Target now excludes open ports, improving data clarity.

History:

CSV downloads from Internal Authenticated Notification Emails now show hostnames instead of IP addresses.

Fixed the Regenerate Notification feature for failed scans—notifications now send correctly with accurate status messages.

Schedule a Scan: Fixed a backend issue that caused continuously scheduled scans to push the “Next Scan Date” too far ahead. Dates now reflect the defined frequency.