Hello, my name is Shelley Gu and I am a Program Manager on the Trustworthy Computing Security team. I’d like to introduce some new features we have added to digital signatures in Office 2010. First I’ll briefly explain what digital signatures are and how to use them, and then I’ll dive into the details about how they work in Office 2010.
More and more business transactions are being conducted electronically. Consequently, digital signatures are being used increasingly to legally bind relying parties to their transactions. A digital signature is used to verify the identity of the person who signed the document, and confirms that the content was not modified after the digital signature was applied to the document. Digital signatures provide security based in encryption technologies and help mitigate risk associated with electronic business transactions. With improvements to digital signing, Office aims to meet the information security needs of enterprises and public sector entities worldwide.
To create a digital signature, you must have a digital certificate, which proves your identity to relying parties, and should be obtained from a reputable certificate authority (CA). If you do not have a digital certificate, Microsoft has partners that provide digital certificates as well as other advanced signature services that are integrated into Office at the Office Marketplace.
In Word, Excel and PowerPoint 2010, a digital signature can be added by going to the Office Backstage View:
A signature line or signature stamp can be added in Word, Excel, and InfoPath by going to the Insert Tab:
A signature line looks like this:
A signature stamp (more commonly used in Eastern Asia) looks like this:
Office 2007, and later versions, use an open signing standard called XML-DSig that replaces the less advanced binary signatures from Office 2003 and earlier versions. XML-DSig represents a signature in a mostly human-readable XML format. For more information on XML-DSig, see http://www.w3.org/Signature.
Office 2010 digital signatures are able to use advanced algorithms (like the elliptic curve public key algorithm) supported by Windows Vista and later. All supported operating systems also allow the use of more robust hashing algorithms, like SHA-512.
The most immediate problem with digital signatures is that the certificate you use will expire – usually in as little as one year. After the certificate has expired, no one should trust the signature. If you want to be able to trust a signature over a longer period, then you must keep copies of the information needed to validate the certificate. You might also need to worry about the cryptography becoming obsolete.
Fortunately, a solution to these problems is available in an extension to the XML-DSig standard called XAdES.
XAdES (XML Advanced Electronic Signatures) is a set of tiered extensions to XML-DSig, the levels of which build upon the previous to provide more and more reliable digital signatures.
By implementing XAdES, Office complies with the European Union Advanced Electronic Signature Criteria in Directive 1999/93/EC as well as a new Brazilian government directive which defines XAdES as the accepted standard for digital signing in Brazil.
Office 2010 can create different levels of XAdES signatures on top of XML-DSig signatures:
The Office 2010 Beta only creates up to and including XAdES-T signatures, but Office 2010 RTM will be able to create all the signatures in the above table.
Time stamping digital signatures (XAdES-T signatures) is an important scenario we focused on in Office 2010. In order to create a time stamped signature, you’ll need to:
Once everything is configured, you can just create signatures like you normally would. A timestamp from a trusted timestamp server extends the life of your signature, because even after the certificate expires, the timestamp proves that the certificate had not expired at the time of signing. As a result, time stamping protects against certificate expiration, and if the certificate was revoked after the signature was applied, the signature is still valid.
By default, Office 2010 creates XAdES-EPES signatures. Registry settings are used to specify the level of signatures to create. There are two registry settings to control the type of signature Office creates, XAdESLevel and MinXAdESLevel.
The MinXAdESLevel setting allows you to ensure that created signatures meet your required XAdES level. A XAdES-T or higher signature will fail if the timestamp server isn’t available, and a XAdES-C or higher signature will fail if revocation information isn’t available. Having a minimum setting allows scenarios where you could attempt a XAdES-X-L signature, but fall back to XAdES-EPES if the timestamp server is down.
To create XAdES-T signatures and above you will need to provide Office with a time stamp server to query for time stamps:
If you want to create XAdES signatures, we recommend using one of three levels:
Sam wants to create XAdES-X-L signatures. If this is not possible, he is willing to accept any signature that is at least a XAdES-T signature. He sets:
In this case, Office attempts to create a signature up to the –X-L level. If Office is unable to create a XAdES-X-L signature, Office falls back to the last successful XAdES level provided that the level is not lower than MinXAdESLevel. In this case, XAdES-T, XAdES-C, and XAdES-X signatures would be acceptable if Office is unable to create a XAdES-X-L signature. Otherwise, Office does not add a signature.
As mentioned previously, Office 2010 Beta is only able to create up to XAdES-T signatures because we added the rest of the XAdES work in after the Beta. The XAdESLevel registry setting we explained above still applies, but the maximum level is 2 (XAdES-T). TheMinXAdESLevel setting isn’t present, but you can only create two types of XAdES signatures – with and without a timestamp, which is controlled by the TimestampRequired setting (which isn’t present in the RTM version).
To create a XAdES-T signature, you will additionally need to set TimestampRequired (below) and TSALocation (see explanation above):
The XAdES feature is one of many security enhancements we have made to Office 2010. Thanks for reading, and we look forward to hearing your feedback!
I think it is great that Microsoft is improving support for digital signatures in Office! If everyone would use digital signatures spam email would be cirtually eliminated.
Is there any chance Microsoft could start using digital signatures on email being sent to customers? Often I get emails claiming to be from Microsoft, but I have no way currently to know if they are genuine or phishing emails.
Any chance for more posts on using digital signatures? For example can one sign a blog post using Windows Live Writer?
Hiya, the title of the story has a typo "Signatures" not "Signitures".
This seems alot like the digital signatures already present in Adobe Reader. Will Office 2010 be compatible with PDF documents signed via Adobe Reader or other software?(Maybe through XAdES?)
Hey, it's called Signatures not Signitures. Check your title first. :)
These are excellent news. We are a Microsoft partner in Spain, highly specialized in electronic signature. probably we can help each other testing signatures. We have been participating in several ETSI XAdES Plugtests
Thanks Peter! Great catch and thanks for the comment. We've fixed it up.
If you need to authenticate a document past one year, why not just mail the signed piece of paper?
Are you looking into providing Xades signature capabilities also via .NET API that support dealing with OPC packages (System.IO.Packaging)?
It would be great if creation of Xades-* signatures and their validation capabilities would be avaialble in .NET platform as well.
Just curious, have there been any advances to support some common requirements for regulated industries to do things like a just-in-time reauthentication request?
We currently have our own certificate manager running on Server 2008. We use these certificates to create digital signatures for our adobe forms.
Can we use the users existing certificates from the certificate server to create their digital signatures in Office 2010?
Great news, also it would be great to have API for .NET, I guess that will be the case.
Would it be 'qualified' digital signature in European union?
'qualified' - meaning to be in accordance with EU laws
What about support for encrypted ODF documents that's been missing in 2007? And 64-bit XP support please.
Thanks for all the comments!
@John Tarbox – It is really up to the sender to digitally sign their emails, and there is little incentive for spammers to do this. Just make sure you keep good spam filters. :) Also, right now there are no plans for more posts on digital signatures, but this could always change!
@Daniel Anthony – Office 2010 is not able to timestamp PDF documents. PDF signatures in Acrobat are handled by Adobe.
@Andrew Brandt – When you digitally sign a document, the idea is that you do not need any hard copies of the document and signature. Everything is electronic.
@Curious – As of this time, we don’t have XAdES digital signature APIs in .NET, but this is a great idea! I will follow up with the .NET team.
@Jason Dossett – We do not currently support the ability to timestamp a signature right before its cert expires (if this is what you mean).
@Trudy Hutzler – Office is able to use any valid X.509 certificate to create signatures, so yes, your users should be able to use their existing X.509 certificates to create Office digital signatures.
@Marko – The EU supports Advanced Electronic Signatures (AES) and Qualified Electronic Signatures (QES). XAdES signatures are classified as AES and are legally binding in the EU.