Novannet, LLC LogoThe 10-10-EDISM of B2B Transport


Privacy is the notion of protecting you and your information. Trust, on the other hand, is assurance that the entity at "the other end" is really who they say they are. Generally, authentication and identity are enforced with digital signatures buttressed by a Public Key Infrastructure (PKI) (PDF: 162k). A trusted third-party certification authority (CA) - such as Verisign - digitally signs your partner's public-key digital certificate. The digital certificate can be used to prove your partner's identity and to assure you that transactions have indeed come from him.

So how does the CA manage to accept liability for trade backed by certificates that they issued?

Well the straight answer is that they don't. If you examine the contracts they have on offer they will not accept any liability for anything at all and leave all the parties in the state of "caveat emptor" or let the buyer beware.

So how does the CA know who your partner is? Traditionally, applicant companies present their credentials to the CA. These credentials are what you would expect: D-U-N-S numbers, officer signatures on official letterhead, photo ID, employee ID, notarized statements, and so on. This cumbersome and manual vetting process, depending on how elaborate it is, accounts for the greater part of the expense of CA-signed certificates. The CA does assume some liability depending on its policies. But this protection is usually only intended for the benefit of its customer, and not for the one actually depending on the reliability or authenticity of the certificate: you!

Though 10-10-EDISM fully supports certificates issued by most of the third-party certification authorities, their great expense is naturally an impediment to frictionless e-commerce. That's why Novannet offers CommerceTrustSM, a unique and novel way of assuring identity and authentication on the 10-10-EDI network. Novannet is a Certification Authority itself, and our signed certificates are used like those of any other CA.

Valid XHTML 1.0!