Nevada Deadline on E-Mail Encryption Looming
What happens in Vegas, may stay locked down in Vegas. On Oct. 1, the state of Nevada will be requiring the encryption of all transmissions, such as e-mail, for all businesses that send personal, identifiable information over the Internet. The statute was signed into law in 2005 and is about to kick in as an enforceable law next month. Three years flies when you're raking in chips at casinos and enjoying the rising popularity of poker. The Nevada law is stated as such:
As with any law about to go in effect, this one could be bound to catch many Nevada businesses off guard. In parallel, a few IT security vendors that sell encryption software and hardware are lining up to tell the technology media about it. Think about all the hotels, resorts, golf courses, pawn shops, nightclubs, check cashing, ski lodges and small businesses this is going to effect. Not to mention all the businesses--the vice-ridden ones legal to Nevada only and otherwise--that incorporate in the tax-friendly state. Nevada is the West's version of Delaware (albeit a much sexier state, sorry Delaware). Beyond the infrastructure impact, the statute itself looks like swiss cheese. Bryce K. Earl, a Las Vegas-based attorney with Santoro, Driggs, Walch, Kearney, Holley & Thompson, has been following the issue closely and believes there are some problems with the statute as it is on the books right now, namely the broad definition of encryption, the lack of coordination with industry standards and the unclear nature of penalties both criminal and civil. "The statute's lack of specificity with regard to penalties will perhaps create the unintended consequence of opening up more liability," said Earl. That doesn't sound good, but again, nothing has happened just yet. Earl explained why the broad definition of "encryption" by the state is potentially problematic. Here is the definition from the state's Web site:
Earl said an argument could be made that a password-protected document sent in an e-mail might be good enough to hold up with the state's broad definition of encryption here. Is that good enough? Moreover, how the heck will Nevada enforce this? Earl said at this time it was unclear, but he thinks that the state--which holds legislative session every other year--could address the statute for more clarity next year when the Nevada state government reconvenes. A possible-pending lawsuit may also help to better define the law for clearer interpretation, but as Earl hinted, that doesn't necessarily mean it will help that potential lawsuit. The challenge for Nevada is that its intentions were good in trying to stem the tide of identity theft and criminal behavior online. But once again, the legal system and the IT industry are faced with potentially bigger compliance and liability issues than they probably intended. The disconnection is real. As of posting time, representatives of the state had not gotten back to me with comment. What should businesses do about this issue? UPDATE: A spokesman for the state has directed me to a state assemblyman (who I will follow up with), but more interestingly, has pointed out this provision in the law:
|

I don't see how this can possibly be enforced.
Typically when government starts trying to legislate the use of technology they just create more problems than they solve.
>I don't see how this can possibly be enforced.
It can't. But it does pose itself as being important. The only way that email encryption can be enforced is by Federally mandated legislation.
We enjoy the reliability of VPN technology. It wouldn't be a monumental technology challenge to impose encryption because standards are already available and free to use, e.g., GnuPG.
Making the process more transparent to the user and having ISPs check for the presence of signed key on the message header would be sufficient test and lacking a signed key would be cause to bounce the message back to its originator.