Skip to main content

The WiKID Blog

Viewing posts by admin

Heartbleed, Two-factor authentication and cascading failure

For the record, we use java for certificates, not openssl, so the WiKIDAdmin server interface (which should not be Internet-facing anyway) is not vulnerable to Heartbleed.

Our big list of two-factor authentication tutorials

There's a great new site promoting the use of two-factor authentication by various web services: http://twofactorauth.org/.

Risks from poorly managed SSH Keys

Read Computerworld's article about a Ponemon study discussing SSH key management issues:

Consortiums and Standards in Authentication

The FIDO Alliance published their standards recently.  I was amazed to find  out from Eve Maler  that the license does not include any implementation rights.  You just get to look at them.  I find this fascinating in today's world of prolific coding.  Verisign, on the other hand, published the Oauth protocol as an IETF standard, which Google made popular.  WiKID is not in danger of becoming a market-dominating standard (yet), but we have an open-source version that mitigates many of risks of choosing WiKID.  This led me to think about what's really important from a buyer's perspective.

Buyers like standards (either industry-chosen or market-created) because of:

Providing Vendors and 3rd parties with two-factor authentication

Krebs on Security is pointing a finger to a third-party vendor with remote access as the entry point for the Target hackers.   PCI requirement  8.3 states that you must incorporate two-factor authentication for remote network access by all personnel and all "third parties, (including vendor access for support or maintenance)."

Recent Posts

Archive

2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008

Categories

Tags

Authors

Feeds

RSS / Atom