What's New for Console?

Current updates are highlighted here.

September 2024

Reference the "News Archives for Console" for previously published updates.

Egress Monitor for Ransomware Protection

Wasabi has made it difficult to get locked out of your data, mitigating a ransomware attack. Unfortunately, "bad actors" may blatantly attempt to steal your data. The most straightforward way to steal data from Wasabi is to download it.

Wasabi's egress monitor reviews historical usage data, determines typical egress for the given account, and compares the daily egress. When the egress monitor email notification feature is enabled, an email is sent to the Root account if the monitor detects abnormal egress activity (such as if the number spikes). This lets you review your daily egress for suspicious activity such as abnormal quantities of data leaving your account.

To receive email alerts about egress monitor activity, enable the Egress Monitor Email Notification toggle in Settings.

Data Integrity Validation

When you are uploading an object, it is important to check the data integrity of the object. The Wasabi data integrity validation feature lets you validate data integrity to be sure your data has not been altered or corrupted when it is uploaded. Click Additional Checksums to specify a checksum when the object is uploaded.

By default, Wasabi applies an MD5 checksum to every newly uploaded object. You can apply an additional checksum for extra object integrity verification. This generates a checksum value that is available in the object details. You can compare this value to a checksum calculated locally to verify the integrity of the upload. If you are uploading a single object under 96 MB, you can enter your checksum value and Wasabi will compare it for you. If the values do not match, Wasabi will reject the upload.

Cross-Origin Resource Sharing (CORS)

CORS defines a way for client web applications loaded in one domain to interact with resources in a different domain. This lets you utilize resources in different buckets across Wasabi accounts for your web applications. Wasabi maintains a default CORS configuration. Alternatively, you can define a CORS configuration within the Permissions tab of the Bucket Settings.

If you define a CORS configuration, the default configuration is overwritten. If you delete a custom CORS configuration, the default configuration is used.

Root User Ability to Force MFA for a Sub-User

Multi-factor authentication (MFA) encourages users to adopt safer online practices. A significant security gap occurs when MFA is configured for the Root account but not for other users (sub-users) on an account. With Wasabi, a Root user can require that sub-users enable MFA when they enter the Console or authenticate a CLI session for the first time. 

The option to require MFA is enabled either when a user is created:

Or on an individual user’s profile:

There are two types of Wasabi users: Console and Programmatic. This MFA feature impacts both types of users. A Console user can configure MFA, as described in Multi-Factor Authentication (MFA) Settings. An Admin will need to help a Programmatic user configure MFA.

Replication Emails

To improve communication about object replication, you can enable a feature to receive email notifications for all of your replication jobs, including:

To receive emails about your replication jobs, enable the Object Replication Email Notification toggle in Settings.

Single Sign-On (SSO) for Trials

SSO V2, which was previously available only for paid customers, is now available for all customers, trial and paid. There are no changes to Wasabi Console functionality.

Italian Language Support

Wasabi Console now includes Italian language support. As for other languages, this option is available on the language drop-down on the login screen and Wasabi Console (top right of the screen).