RSA Via Solution Catching Fire…Here’s Why

RSA’s latest announcement highlights how the RSA Via portfolio of identity products, and specifically RSA Via Access, is gaining momentum in the marketplace. What’s more:  customers, partners, technology integrators and analysts are loudly voicing their support. This enthusiasm in a crowded field leads to the question: how does RSA do it? Here are three ways:

Identities Stay Home, Hybrid Cloud Style

Every breach has an identity component. It’s no wonder that having identities synced into cloud platforms, as offered by many of our competitors, is the #1 objection to moving to an Identity-as-a-Service model, and RSA Via Access is designed to solve the problem with its hybrid-cloud approach. Simply put, sensitive user credentials remain safely ensconced on premises, while benefiting from the efficiency and scale of an as-a-service solution.  An on-premises Identity Router (IDR) is engineered to keep sensitive information within the organization, where it belongs, and offers centralized management while successfully brokering authentication events from the cloud between LDAP, on-premises apps and cloud aVia Momentum_EMC Pulse Imagepps.

This hybrid approach can also utilize customers’ RSA SecurID deployment, leveraging the IDR to extend their world-class token technology to support SaaS and web applications.

To help secure identities, RSA Via Access is bolstered by the full RSA Via portfolio, RSA Via Lifecycle and Governance.  Together, they offer an end-to-end solution that is built to provide a single, central view of identity, resources, entitlements and access to help organizations regain control over identities and benefit from global access. They know who has access to what, can securely manage access, and can pinpoint anomalies/unauthorized access changes. Check out the demo.

Enterprise-Class Scale

Faced with a proliferation of SaaS applications around the organization, many enterprises settle for quick, band-aid solutions.. As a result, they build separate identity infrastructures, or “Islands of Identity,” that create a chasm between these apps and other legacy systems. This limits visibility into – and management of — these infrastructures.  Nirvana for most companies would be to manage access to all SaaS, legacy, customer applications and on-premise web apps from a central platform. RSA Via Access helps support this, with newly introduced localization features designed to offer portal access in a variety of languages for global scale.

 Balanced Security and Convenience

There no longer has to be a tradeoff between security, convenience and cost. Many organizations think they can only optimize one of these variables at the expense of the others. Organizations really need a spectrum of authentication options. Not one size fits all. RSA’s commitment to easier and better authentication is demonstrated by our growing ecosystem of authentication methods. In addition to Apple’s TouchID fingerprint verification, Tap or Shake to Approve an authentication request, and one-time passcode prompts, users will also be able to confirm push notifications on an Apple Watch –further improving a user’s experience, and helping enable quick and secure authenticate.  Additionally, the integration of RSA Via Access with RSA SecurID authentication helps increase the number of authentication methods to cloud apps, enabling further optimization of convenience and security.

RSA Via Access is engineered to offer a set of mobile-optimized authentication methods that deliver convenience to users combined with contextual level of authentication that provides as much strength (ex. biometric, RSA SecurID token) as needed. After all, not all applications are the same.

For more information on RSA Via, visit

This blog contains forward-looking information about EMC Corporation and the proposed transaction that is intended to be covered by the safe harbor for “forward-looking statements” provided by the Private Securities Litigation Reform Act of 1995. Actual results could differ materially from those projected in the forward-looking statements as a result of certain risk factors, including but not limited to: (i) the failure to obtain the approval of EMC shareholders in connection with the proposed transaction; (ii) the failure to consummate or delay in consummating the proposed transaction for other reasons; (iii) the risk that a condition to closing of the proposed transaction may not be satisfied or that required financing for the proposed transaction may not be available or may be delayed; (iv) the risk that a regulatory approval that may be required for the proposed transaction is delayed, is not obtained, or is obtained subject to conditions that are not anticipated; (v) risk as to the trading price of Class V Common Stock to be issued by Denali Holding Inc. in the proposed transaction relative to the trading price of shares of VMware, Inc.’s common stock; (vi) the effect of the proposed transaction on VMware’s business and operating results and impact on the trading price of shares of Class V Common Stock of Denali Holding Inc. and shares of VMware common stock; (vii) the diversion of management time on transaction-related issues; (viii) adverse changes in general economic or market conditions; (ix) delays or reductions in information technology spending; (x) the relative and varying rates of product price and component cost declines and the volume and mixture of product and services revenues; (xi) competitive factors, including but not limited to pricing pressures and new product introductions; (xii) component and product quality and availability; (xiii) fluctuations in VMware’s operating results and risks associated with trading of VMware common stock; (xiv) the transition to new products, the uncertainty of customer acceptance of new product offerings and rapid technological and market change; (xv) the ability to attract and retain highly qualified employees; (xvi) insufficient, excess or obsolete inventory; (xvii) fluctuating currency exchange rates; (xiii) threats and other disruptions to our secure data centers or networks; (xix) our ability to protect our proprietary technology; (xx) war or acts of terrorism; and (xxi) other one-time events and other important factors disclosed previously and from time to time in the filings of EMC, the parent company of RSA, with the U.S. Securities and Exchange Commission (the “SEC”). EMC and RSA disclaim any obligation to update any such forward-looking statements after the date of this press release.

About the Author: Jim Ducharme