From MediaWiki
Jump to navigation Jump to search

Division 1 Supplemental Information

General Information

According to the Code of Federal Regulation, electronic signatures are defined as a computer data compilation of any symbol or series of symbols executed, adopted, or authorized by an individual to be the legally binding equivalent of the individual's handwritten signature. A specific type of electronic signature is digital signatures. Digital signatures are defined as an electronic signature based upon cryptographic methods of originator authentication, computed by using a set of rules and a set of parameters such that the identity of the signer and the integrity of the data can be verified.

An entity such as a computer user can be assigned a unique digital identification. This digital identification is composed of a public key, a private key, and a digital certificate. As their names suggest, the public key should be shared amongst users who wish to carry out transactions amongst themselves, while the private key should be only known by its user. The digital certificate is used within a public-key infrastructure to allow a third-party certificate authority to verify that the digital certificate is correctly associated with that particular public key.

As public keys are shared amongst a group of users, someone’s public key can be used to encrypt a document and their respective private key can be used to decrypt that document. Confidentiality and data integrity of the sent document can be practically guaranteed assuming if the recipient is the only one who knows their private key. Similarly, someone’s private key can be ‘embedded’ into a document to constitute an electronic signature, and the identity of the electronic signature may be verified by using that user’s public key.

[top of page]

Adoption at MDOT and Acceptable Uses

The Michigan Attorney General’s office, in concurrence of the Federal Highway Administration, issued a decision in 2011 authorizing the Michigan Department of Transportation (MDOT) to use and accept digital signatures.

There are many standards available for digital signatures, but MDOT currently authorizes the use of PKCS#12 files for digital identification. This cryptographic standard requires the signer to enter their unique password each time they digitally sign a document. To digitally sign a document, you must first have a digital identification (ID). This ID can be obtained from MDOT by following the instructions on the MDOT esign page at [1]

You may have multiple digital signature format styles configured for different purposes. It is even possible to configure a digital signature with an “Imported Graphic” containing an image of your professional license stamp.

It is important to note that for records retention and archiving purposes whenever digital signatures are used on documents, the electronic file (usually PDF) is considered the original legal document. Printouts of the document containing digital signatures are considered copies, so the signed electronic file must be retained and follow the relevant approved records retention procedures. MDOT will address the records storage issue through the requirement that all electronic documents must be placed in the project directory in the ProjectWise document management program. The E-construction wiki page contains more information regarding ProjectWise.

[top of page]

Guidance for Non-MDOT Users

An individual’s digital signature must be validated before MDOT can accept the signature. Form 5600 for contractors and Form 5600A for consultants allows an individual to submit their digital signature to MDOT. When you select the signature box when filling out these forms, you can use an existing digital ID or you can create a new ID. There are many ways an individual can obtain a digital ID, but the preferred way is to use Adobe software. These forms will be on file with MDOT until the individual’s digital signature certificate expires or until such time as the individual needs to create a new digital signature.

[top of page]

Digital Electronic Signature (DES) Validation Procedures

[top of page]

What is digital Signature Validation and why does it matter?

All signatures must be authenticated to determine the identity of the document signer(s) and it is the legal requirement that anyone receiving a signature from an external party must authenticate the signature on the document they receive (paper or electronic). While handwritten signatures have visual indicators that help us determine someone’s real signature, the digital signature process is much faster and more secure. However, digital signatures can also be falsely created by other parties and made to look very similar to the authentic digital signatures, so care must be taken to determine the true identity of the signers. The process to determine the authenticity of digital signatures is referred to as signature validation.

Validation is the process that authenticates the electronic signature on a document and compares it to the known validated signature on file.

In general, the electronic signature validation process occurs primarily in the background of the software and only requires us to take action the first time a signature is received. A valid digital signature proves that the message was created by a known sender; such that the sender cannot deny having sent the message (authentication and non-repudiation) and that the message was not altered in transit (integrity). This is accomplished by the use of an algorithm that creates unique encrypted codes associated with the digital signature for the user. In general, each digital signature has two main components. The first is a private key code that is encrypted into the signature which is essentially the user’s password used to affix their signature. The second component is called the public key code which is a unique complex code embedded into the signature that allows other parties to easily authenticate the true identity of the signer. Each digital signatures public code is unique to the digital signature, not the person, thus if you have two digital signatures each has its own unique code, they are not the same. When a sender signs a document their private key remains with them, but the public key is embedded into the signature on the document. When the document is sent to the recipient, the recipient’s computer compares the unique public code in the signature to the list of known validated signature codes. If the codes match then the signature is considered valid and proves the signature was made by the sender. If the codes do not match, the software indicates the signature has not been validated. If this occurs the recipient is required to perform the validation process as described in the next section of this BOH IM. (Note the graphic process describing the validation process is presented in Attachment 1; e-Signature Validation Process Overview of this BOH IM.)

Effective immediately, the process for validating Digital Electronic Signature (DES) received by MDOT from any external party will be as follows:

1. External Parties:
a. All external parties (non-MDOT/FHWA), intending to use DES on any documents to be submitted to MDOT, must submit form 5600 Statement of Digital Electronic Signature Validation to the local MDOT office for validation of the DES prior to (or concurrent with) the DES being used on any documents submitted to MDOT.
b. Form 5600 must be submitted for each individual DES the first time the signature is used on a project. This can be submitted concurrently with a document; however, the document will not be accepted until the validation process has been completed.
c. Most DES certificates expire after four (4) years from the initial date of the DES creation. It is the responsibility of the signature creator to maintain their DES and create a new DES when their current DES expires. Form 5600, once validated, will allow the use of the DES on other documents submitted to MDOT until the DES expires (including on other projects or in other offices).
d. If the DES owner changes employment, position, responsibilities, forgets the DES password, or loses the DES file, this will require that a new form 5600 be submitted for the new signature.
2. MDOT Office:

Any document received by MDOT containing a DES must be checked for proper validation prior to acceptance. This can be confirmed via the blue signature panel validation process at the top of the document in Adobe Acrobat (Figure 1).

Figure 1: Screen showing blue signature panel in Adobe Standard XI

Figure 1

If the digital electronic signatures on the document have already been authenticated, the software will clearly confirm this with the green checkmark as shown below in Figure 2.

Figure 2

If electronic documents come into the office with a non-validated DES, (figure 3 below),

Figure 3

then the office must determine the validity of the document signers. If the signature does not match the previously validated signature codes on file the office must reject the document until a new form 5600 is submitted and the DES can be validated. It is the legal responsibility of the first person who receives any signature to verify the validity of the signature before accepting any documents. After the signature has been validated and added to the trusted list of validated signatures, the software will re-validate and display the green check mark. The completion of the form 5600 is only required when a signature is first used, subsequent documents will be validated automatically for that user. It may take a while for the central office database updates to be distributed to all other users, so until that occurs a signer can send along a copy of the fully completed form 5600 to the new office where they can manually add the validated signature to their trusted identities.

In the case of multiple signatures on the same document, the software clearly identifies the signatures that have not been validated as shown in figure 4 below.

Figure 4

The software also automatically tracks all changes made to the document. This is important because by the very act of signing a document, the document has changed from the version the first person saw. Any major changes to the document that affect the integrety of the encrypted digital signatures will invalidate or delete the signatures, but minor changes like multiple signers will just be noted.

Should an office receive a document or form 5600 that requries them to validate the digital signature the process is simple and straightforeward.

The validation process is detailed on form 5600 and the receiver must verify at least two (2) of the four (4) federal signature authentication requirements outlined below:

a. The name of the sender is the same name expected.
b. E-mail from a company domain e-mail address.
c. Direct contact with sender verifying they sent the document with signature.
d. Verification via another method with provided details.

The MDOT recipient of the document is then required to indicate which two methods were used to verify the signature is actually from the recipient and then confirm their validation efforts by placing their own digital signature on the form. This form is then routed to the central office for archiving and a copy of the completed form returned to the sender for their records or for submission to other offices until the central database is updated.

a. MDOT office staff that receives form 5600 will go through and complete the validation steps per the form instructions.
b. Once the DES is validated, the validating MDOT office staff will countersign form 5600.
c. MDOT office staff will then add the validated signature to their trusted identities. Instructions for manually adding a validated signature to your trusted identities can be found on the MDOT WIKI Construction Manual in Division 1 Supplemental Information, e-Sign section.


d. MDOT office staff will then submit the completed form 5600 to

MDOT-eSign@michigan.gov and also back to the submitting applicant.

3. MDOT-Central Office:
a. MDOT Central Office staff will receive form 5600 via the

MDOT-eSign@michigan.gov e-mail address. MDOT Central Office staff will then maintain these 5600 forms in a centralized server for archiving purposes, update export files of all previously validated DES, and send these validated DES out to MDOT staff periodically.

If you have any questions, contactMDOT-eSign@michigan.gov. Please share this information with consultants and local agencies within your area.

Figure 5

[top of page]


File Name Description
Setting Up an Electronic Signature Creating a Digital Identity with Adobe Acrobat
How To Add A Digital Signature Via iPhone Creating a Digital Signature on any iOS smart device
E-sign brochure A brief outline concering various facets of E-signatures
How to Digitally Sign a document with Adobe Reader A YouTube video published by Adobe about how to digitally sign a PDF file with the free Adobe Reader
Applying an Image To Digital Signature How to import and insert an image to a digital signature
Trusting and Validating a Digital Siganture How to trust and validate a signature in Adobe Acrobat