Skip to main content

The WiKID Blog

The WiKID Blog, musings on two-factor authentication, information security and some other stuff.

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)."

New server update

The latest release of our two-factor authentication server is a strong one.  We focused on speed enhancements and usability for some of our large (meaning multi-thousand users) enterprise customers.  It is capable of performing close to 500 authentications per minute in replication mode and well over 1000 per minute in stand-alone mode.

Two take-aways from the Great Snow Storm of '14

There's been a lot of criticism leveled at government officials regarding the response to the recent snow storm in Atlanta.  I support criticizing the government, but I'm always amazed that anyone expects anything of their government.  Here's my question: did your company do better than your government?  If not, why not?

iPhone token woes

Last night Apple published what we thought was a minor update to our iPhone/iPad software token.  This morning we started getting reports of trouble.  We pulled the software token from the app store as soon as possible.  The apple store has no option to revert to the old binary, sadly.  If you had the token set to auto-update, then you may no longer be able to get an one-time passcode from your WiKID server.   There are two options: You can delete the domain on your token and re-register or you can wait for an update, which we are feverishly working on.

Recent Posts







RSS / Atom