"Deploy smart. Don't just do it," Erik Johnson, a secure messaging executive at Bank of America, said in a presentation at thehere Wednesday. "If you just do it, you may just break it."
For the past two years, the technology industry has been advocating the use of systems to guarantee the identity of e-mail senders. It sees such authentication as key to the, as it should help improve mail filters and make it harder for senders to forge their addresses. The industry also likes to advertise that .
Organizations have been buying into the promise of restoring trust in e-mail. The number of Fortune 500 companies that sent authenticated mail has increased, from 7 percent in July last year to 20 percent at the end of March 2006, according to Microsoft. The software giant is the main backer of a.
"Setting aside rewriting SMTP, e-mail authentication is the best thing we have today," Johnson said, referring to the Simple Mail Transfer Protocol, the basic technology behind e-mail. Yet adopting sender authentication and managing it is not simple, he said. It took Bank of America six months to deploy the technology.
"It really is not easy to deploy sender authentication right. If you are in a large organization, you really can't just push the easy button," Johnson said. "This requires pretty much constant attention and activity...or else it will break and it will hurt you."
There are two main ways of authenticating e-mail: Sender ID and DomainKeys Identified Mail, or DKIM. Backed by Yahoo and Cisco Systems, DKIM relies on public key cryptography. It attaches a digital signature to outgoing e-mail, so recipients can verify that the message comes from its claimed source.
Sender ID is further along in adoption than DKIM. It requires Internet service providers, companies and other Internet domain holders to publish SPF (Sender Policy Framework) records to . This usually does not require new hardware or software; the most arduous part is doing an inventory of mail servers and the subsequent maintenance of that record.
"The story is that (this type of sender authentication) is cheap to do. That is not true," said David Crocker, the principal at Brandenburg InternetWorking and author of one of the early e-mail standards. "The ongoing IT cost is huge."
The key problem for large companies is figuring out all the systems that send e-mail on their behalf, said Paul Judge, chief technology officer at e-mail security company CipherTrust. "If you are a large multinational organization, you may have e-mail gateways in 10 countries, you may have marketing companies that send e-mail on your behalf," he said.