Skip to main content

The WiKID Blog

Viewing posts tagged Two Factor Authentication

Privacy concerns about SMS-based two-factor authentication

Imagine these conversations:

A whole bunch of Cisco Two-factor Tutorials

We've spent some time in our lab with a Cisco ASA 5500 series VPN and we have posted a few of tutorials:

Seven common misconceptions about two-factor authentication

We get a lot of questions from enterprises as they deploy two-factor authentication. There are a good number of misconceptions out there about how to do it. Here's are six that we see frequently as enterprises first start to think about two-factor authentication:

Belts and Suspenders Security

I continue to be astounded that one server without two-factor authentication caused the JP Morgan breach.  If a sophisticated organization like a major US financial institution can get hacked like that, what are the chances for everyone else? If you were an incoming CIO or CISO, what can you do to avoid such a disaster?

Obviously, JP Morgan is reviewing the status of all their servers (for a start).  As I mentioned before, automation and infrastructure as code will help create idempotent servers so you can be sure that they meet security requirements .  Any servers outside that level of management, should be segmented and brought in line eventually.  But I think it will increasingly make sense for servers to have two-factor authentication for remote access and administrator rights.  This is simple to do on *nix servers as services that use PAM - ie sshd, sudo, login etc can all easily require two-factor authentication.  Copying these configuration files via management tools is quite simple.  By using RADIUS as the authentication protocol, you can perform authorization in Active Directory or LDAP.  If I were going into Sony, I would require two-factor authentication for egress as well.

Certainly, this would break some things.  But that's the idea. The breaks should show you were you have issues. You need to address those issues.

J.P. Morgan caused by lack of two-factor authentication on one server

This story is interesting because it shows that two-factor authentication would have (most likely) worked to prevent this devastating attack.  However, it also shows how hard it is for large organizations to actually implement security controls, especially given the use of third parties and  growing through acquisitions.

Recent Posts







RSS / Atom