-
Release to Manufacturing: Elements Agent for Windows 25.1
We have released a new version of the Elements Agent for Windows. Version 25.1 is available for first time installations, and existing installations will receive this automatically. The internal version number is 25.1.85. The endpoints automatically upgrade, without a reboot. No administrator action is required. This…
-
WithSecure Elements: Retention periods for Security Events
In the Elements Security Center, you can view Security Events under the Events menu. Security Events data is stored for a limited time, depending on event severity. The maximum retention period is 14 months, but it may range between 13 and 14 months. The exact retention period will vary depending on when the event…
-
Upcoming: New Elements organization management features
As part of our ongoing work to unify workflows in WithSecure Elements, we will be introducing changes to Organization Management during February. We will provide an update once the exact schedule has been confirmed. These changes will help our Elements Administrators to more effectively manage their environments. Key…
-
General Availability: WithSecure Elements Identity Security
We are happy to announce that our WithSecure Elements Identity Security is now officially in General Availability (GA). This means that it is available for all customers. WithSecure Elements Identity Security is an Identity Threat Detection and Response (ITDR) solution. It protects organizations against identity-based…
-
How to configure Elements Endpoint Detection and Response alert email ONLY to be sent when severe or high risk level happened?
Issue: Normally, the alert notification email from EDR will be sent when a detection with he risk level at "Severe", "High" and "Medium" has been added to the portal, but is it possible to configure the alert email that ONLY will be notified when "Severe" or "high" risk level has happened? Is it possible to filter the…
-
Email and Server Security- Scanning 'message' by WithSecure Spam Scanner was unsuccessful
Issue: Email and Server Security, the following message keeps occurring: Scanning 'message' by WithSecure Spam Scanner was unsuccessful. Scan result: Scan error: -1073741808 The message can be found in various logs, including the following: - email-scan.log - transportAgent.log Resolution: The error "WithSecure Spam…
-
Elements Vulnerability Management - User's "First and last name showing" as "_Not_SET__ __NOT_SET__" in Elements Portal.
Issue: When adding new users for Elements Vulnerability Management, you can no longer enter first and last names, only the email address. Consequently, when viewing the user information in the Elements Portal, the first and last name shows up as __NOT_SET__ __NOT_SET__ Resolution: It is normal for the username to be shown…
-
Spam email getting through even if Elements Collaboration Protection is in use
Issue: Why is spam / bulk / advertising / phishing email getting through even if Elements Collaboration Protection is in use? Shouldn't spam email be filtered by the spam filter? Resolution: Elements Collaboration Protection does not include a spam filter. Microsoft Office 365 has its own anti-spam policies, of which you…
-
What is "suspicious hidden inbox rules" option on inbox rule scanning feature in Collaboration Protection.
Issue: What is "suspicious hidden inbox rules" option on inbox rule scanning feature in Collaboration Protection. Resolution: Detect suspicious inbox rule where attacker tries to move content between hidden folders to remain undetected. Attackers use these kinds of rules to manipulate the original mailbox user, remain…
-
Elements Collaboration Protection: Breach detected time is recorded differently with actual occurred time in portal
Issue: Breach detected time is recorded differently with actual occurred time in portal. Resolution: Breach occurred shows when a breach happened. Breach detected is the date when our solution received an information about the breach. Depending on the case, it can take some time for breach database to realize they were…