Information Technology @ Johns Hopkins recently switched to this approach in order to make the Hopkins computing environment safer and more secure.

Wikipedia definition: multi-factor authentication (also MFA, two-factor authentication, two-step verification, TFA, T-FA or 2FA) is an approach to authentication, which requires the presentation of two or more of the following three authentication factors: a knowledge factor (something only the user knows), a possession factor (something only the user has), and an inherent factor (something only the user is). After presentation, each factor must be validated by the other party for authentication to occur.

Wow.  What does MFA mean to me?  Let me try to break that down into something we can all relate to.  Do you use JHPulse VPN to access secured applications in the Hopkins computing environment, such as SAP and other CloudApps?  Do you conduct online banking?  Do you have a Paypal account?  These are just a few applications/environments that have switched to this type of authentication.  To make it simple, after you enter your username and password these MFA sites will ask for additional  information that only you know the answer to.  Usernames and passwords are just not enough anymore so IT@JH has enabled another layer of security, Enterprise Step-up Authentication, ESA.

For this article, we will focus on the MFA in the Hopkins computing environment.  IT@JH has sent out communications and posted information in MyJHU about the implementation of ESA in the Hopkins computing environment.  They’re using it to protect your JHED identity and diminish the risk of your JHED credentials being compromised.  This new method process is effective as of June 10, 2014.

I really like the thought of using a more secured method to access the information I need to access for my position.

For information on Installation, Supported Platforms, and Frequently Asked Questions about JHPulse VPN,  please go to: .

The Enterprise Step-up Authentication help document is located at: