| NEO-18624 |
Resolved misleading rule summaries caused by adding exclusions. |
| NEO-18623 |
Fixed the Alert Activity Filter to display the correct list of values and allow filtering by rule. |
| NEO-18587 |
Resolved a user interface crash that occurred when generating an alert related to “No Match” and attempting to unmask forensics data. |
| NEO-18544 |
Fixed an issue where notification emails were sent for rules even when an exception condition was met. |
| NEO-18536 |
Corrected the match count displayed in the Classifiers section when multiple classifiers were triggered by the same rule. |
| NEO‑18520 |
DPS resource resolver stability: Corrected an issue in the DPS resource resolver that occasionally caused errors during full resource updates. Resource updates now complete
reliably. |
| NEO‑18490 |
Profile distribution issue: Resolved a problem where profiles were not properly distributed when a custom endpoint application was configured to monitor screen capture. Profiles
now propagate correctly in this scenario. |
| NEO‑18486 |
Profile name length: Fixed a problem that prevented profiles with long names from being updated. Profiles can now be updated regardless of name length. |
| NEO-18482 |
Fixed an issue where no alerts were displayed for complex classifiers since the classifier was reported as null. |
| NEO‑18414 |
Addressed incorrect data shown in the Unique Value field by hiding it when Cloud DLP returns either total or unique match counts based on policy configuration. |
| NEO‑18389 |
Resolved a problem where multiple file names were incorrectly displayed for the same transaction in alert details. |
| NEO-18374 |
Fixed an issue where changes to referenced Endpoint Application Groups in Policy Elements did not trigger a profile update. |
| NEO-18370 |
DLPaaS now supports local users for source-user-based policy criteria. |
| NEO-18330 |
Incident CSV exports now include AM/PM time indicators |
| NEO-18317 |
Agent downloads now function properly in Cloud WEB portal |
| NEO-18273 |
Email domain validation now accepts valid domain formats correctly |
| NEO-18248 |
Forensic data now displays correctly when processing multiple simultaneous alerts |
| NEO-18199 |
Cloud portal no longer incorrectly reports missing forensic data |
| NEO-17630 |
Source is not populated properly in email notifications |
| NEO-17273 |
Email address is displayed in the incident instead of the user full name |
| NEO-16859 |
Agents can now be removed from deleted tenants |
| NEO-16580 |
Email Settings: Certificate configurations now persist correctly after loading |
| NEO-16785 |
File types can now be successfully removed from File Types Classifier lists. |
| NEO-16705 |
Provided a tool to remove Endpoints when DLP tenant is unavailable or deleted. |
| NEO-16670 |
Fixed an issue where Forensics and Incident Management were incorrectly unavailable for customers without endpoint DLP licenses, and resolved an SSO sign-in error message. |
| NEO-16650 |
Removed unnecessary API calls causing errors when a specific license is missing. |
| NEO-16624 |
Imported users can now be successfully removed by administrators. |
| NEO-16016 |
Fixed an issue where forensics were not available for incidents that were caused by a rule that is already deleted. |
| NEO-16580 |
Added visual confirmation when email settings certificates are successfully uploaded. |
| NEO-16072 |
Incident Management Workflows: Resolved multiple issues related to the Status field, including missing CSV export data and user interface display
problems. |
| NEO-14760 |
Profile | General | Endpoint Connectivity to Forcepoint: Proxy settings changes affect all profiles, not just the current profile. |