We are thrilled to announce the launch of Multifactor Authentication (MFA) support for local  BlueXP users who are not federated and are not NetApp support site users. This step aims at enhancing the security of NetApp's data estate in BlueXP. As a primary gateway to our customers’ NetApp data estate, BlueXP plays a pivotal role in orchestrating and managing our customers’ data estate securely. Our customers depend on the NetApp storage to store their health records, employee records, online transaction data and video streaming. This means the stakes for protecting the access to our customers’ data estate via BlueXP has never been more critical.   What is MFA: Multifactor Authentication (MFA) is a security feature that requires you to provide two or more forms of evidence to prove your identity when accessing an online service such as BlueXP. These evidence may include something you know (a password or a PIN), something you have (a one-time-password aka OTP) security key, or a mobile phone), or something you are (a fingerprint or a face scan). By requiring the local BlueXP users to provide additional verification methods beyond their passwords, MFA significantly reduces the risk of unauthorized access to the customer’s data estate, even if their credentials are compromised.   The Risks of Password-only Authentication: According to Data Breach Investigation Report of Verizon, the majority of data breaches were attributed to compromised passwords. Although email-password based authentication has become the de-facto method for authentication, it remains highly vulnerable to attacks. Traditional authentication methods can be exploited through phishing, keylogging or simple brute-force attacks, leading to unauthorized access to BlueXP local user account. To address this risk, we are introducing native MFA support for local BlueXP users.   Time based OTP as a second factor:   We have implemented Time-based One-Time passwords (TOTP), a secure and user-friendly method that works with any authenticator App, as a second factor. Recommended authenticator apps include Google Authenticator and Microsoft Authenticator, though any app supporting TOTP protocol is suitable.           Our partners and admins travel globally and have need to register and login to the BlueXP service from anywhere with or without access to the SMS. TOTP codes are generated locally on your mobile device within the Authenticator App, providing great convenience as it does not require internet or network access.   Benefits: Enhanced Security – Prevent unauthorized access to your BlueXP account, even in the event of compromised local user credentials. Compliance Ready – Support strong authentication to meet the requirements of the auditors and security teams. User experience – The second authentication factor for the MFA doesn’t depend on SMS or email, which can be intercepted or delayed. It functions offline and is ideal for remote or traveling teams.   Setup MFA on your BlueXP account using the following simple steps Login into BlueXP and click configure Multifactor authentication from the user’s settings page Enter your BlueXP password and scan the QR code generated via your authenticator App (Google Authenticator or Microsoft Authenticator apps are recommended)     Click continue to enter the code generated on your Authenticator App   You are now successfully enrolled to MFA. Save the recovery code, which comes in handy when you don’t have access to the Authenticator App.   With this, you will now see that MFA is configured on User Settings page       When logging into BlueXP, a user who has configured MFA is presented with the following screen prompting the user to enter a one-time password.    Controls for the BlueXP Org admin: The Org admin of BlueXP can assist users who need help accessing their accounts if they lose their mobile device or MFA recovery code. To facilitate this, we now provide tools for the Org admin to disable MFA for users for 8 hours or completely delete their MFA settings. These tools are available as actions on a BlueXP user   Clicking the manage Multifactor authentication button allows the BlueXP admin to remove or disable MFA for a BlueXP user.   We understand that you need flexibility and control when implementing new security measures like MFA. That's why we're not making it mandatory at this point of time. Enabling of MFA in BlueXP is optional for now. What’s Next on MFA: Support for more admin controls to make MFA mandatory for the Org MFA user Analytics Call for action: A Microsoft study found that enabling MFA has reduced the risk of account compromise by 99%. Take action now to protect your account by setting up MFA on all your local users of your BlueXP organization. ... View more

We are thrilled to announce that NetApp® BlueXP™ has successfully achieved Texas Risk and Authorization Management Program (TX-RAMP) Level 2 Certification, marking a significant milestone in our commitment to delivering secure, compliant, and resilient solutions for our customers. This certification underscores NetApp’s dedication to supporting the needs of regulated entities, including Texas state agencies, institutions of higher education, and public community colleges. ... View more

We are excited to announce the launch of BlueXP Backup and Recovery version 4.0.4! This release introduces a range of enhancements and new features—many of which have been inspired by feedback from our customers—to improve performance and expand functionality. What’s New in BlueXP Backup and Recovery v4.0.4 High Performance Indexing for AWS, Azure, and GCP (Green Field Customers) In February 2025, we debuted our updated indexing feature (Indexed Catalog v2), which significantly improved data indexing performance in on-premise environments. In current release, we’ve extended Indexed Catalog v2 support to all major hyperscalers (AWS, Azure and GCP) Note: New Customers: This feature is enabled by default. Existing Customers: A full re-index of your environment is required to adopt Catalog v2. Use existing Azure Private Link Endpoints/Service Endpoints Typically, Backup and Recovery establishes a private endpoint with the cloud provider to handle various protection tasks. This release introduces an optional setting that lets customers enable/disable CBS from automatically creating a private endpoint. Organizations looking for higher control can utilizing this option. Note: If you opt out of CBS creating a private endpoint, managing network connectivity becomes your responsibility. Without proper connectivity, operations may fail. Support for SnapMirror to Cloud Resync – ONTAP S3 Our previous release introduced the SnapMirror to Cloud Resync (SM-C Resync) feature, designed to streamline data protection during volume migrations in NetApp environments. This update adds support for SM-C Resync on ONTAP S3 as well as other S3-compatible providers such as Wasabi and MinIO. Bring your own bucket for StorageGRID When you create backup files in object storage for a working environment, by default, the backup and recovery service creates the container (bucket or storage account) for the backup files in the object storage account that you have configured. Customers can override this and specify their own container for Amazon S3, Azure Blob Storage and Google Cloud Storage. Now, with this release, StorageGRID customers can also bring their own object storage container. For additional details and guidance on the new features, please refer to the documentation or contact our support team. ... View more

NetApp's BlueXP disaster recovery solution, now features robust support for Amazon Elastic VMware Service (Amazon EVS) with Amazon FSx for NetApp ONTAP. This integration marks a significant milestone in simplifying disaster recovery processes and optimizing costs for enterprises leveraging hybrid cloud infrastructures. ... View more

Find out about all the new features for BlueXP disaster recovery such as support for Amazon Elastic VMware Service, dynamic subnet-based IP address assignment and datatore-scoped replication groups. You can do more with BlueXP disaster recovery. ... View more