Skip to main content

The WiKID Blog

Viewing posts tagged Two Factor Authentication

Law firms targeted for client's information

When we first started WiKID, back in the days of Nextel J2ME phones and Mobitex Blackberries, the concept of using a software token on a wireless device faced one crucial issue:  very few companies had broad, company-wide deployments of wireless devices.  We spoke to Bellsouth and Cingular, but met a lot of resistance.  The info sec people there didn't want to risk choosing a start-up with a new two-factor authentication technology.  The other failing effort we made was targeting law firms, where each partner carried a Blackberry.  We made the argument that law firms should adopt two-factor authentication because they would be targeted for their client's information and maintaining security would help keep customers.  At the same time, lawyers needed access to information.  Did they bite? Not so much.

VDI requires two-factor authentication

Users are increasingly connecting their own devices to the corporate network. despite policy that may forbid it.  CIOs are "embracing and extending" this movement by providing Virtual Desktop Infrastructure (VDI).  Essentially they are saying "You can have whatever device you pay for as long as it goes through our control system.   This article has a nice overview of the security requirements for rolling out VDI, including, of course, two-factor authentication.

Fraudsters defeat poor risk management, not two-factor authentication

SC Magazine's Australian edition recently published an article entitled $45k stolen in phone porting scam. This article was then rewritten on Help Net Security as "Fraudsters beat two-factor authentication, steal $45k"

Mozilla specifies two-factor authentication for CAs

The Mozilla team is cracking down on the lax security of certificate authorities.  They have sent an email to CAs requesting information confirming security practices including two-factor authentication:

Authentication as a Service - mixed incentives

In the past, we've commented on the 'Vendor-in-the-middle' issues in the past, in particular we've pointed out this weakness when using SMS as a one-time passcode delivery mechanism.  As always, such reliance may be ok based on your risk tolerance.  Another example of this risk occurred to me today when someone on twitter mentioned pointed to this Wordpress plugin that add two-factor authentication to Wordpress using Google's authenticator.   There is also one for SSH via a PAM module.  

Recent Posts







RSS / Atom