Professional Documents
Culture Documents
ProofMark System
Technical Overview
Cryptographic Data Integrity Seal & Trusted Timestamp
Issuance, Preservation and Validation
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com
ProofSpace White Paper
Table of Contents
1. Introduction 3
1.1 What is a ProofMark? 4
1.2 What is the ProofMark System? 5
1.3 Integrating the ProofMark System into the Information Life Cycle 6
1. Introduction
With the rapid advances in information and communication technologies, more and
more business records are stored and transmitted electronically. Such advancement
has greatly reduced the need for storing documents in paper form, cutting costs and
making business transactions much more efficient. However, it has also become more
of a challenge to preserve and demonstrate the authenticity and integrity of records for
which there is now no paper “orginal”.
ProofSpace provides businesses with innovative solutions to prove the integrity of their
electronic records. To meet the demands of different organizations and computing
environments, ProofSpace delivers a variety of customized data integrity applications,
the basic building block of which is company’s cornerstone technology, the ProofMark™
System. The purpose of this whitepaper is to provide a technical overview of the
ProofMark System, including core constructs, system architecture, and functional
processes.
In a nutshell, the ProofMark System enables the creation of a “ProofMark”, a digital
tamper-detection seal and trusted timestamp that can be applied to any electronic
record. The ProofMark cryptographically binds the data with an ANSI ASC X9.95
standard trusted timestamp and can irrefutably prove that the data content has not
been tampered with since the ProofMark was issued. The ProofMark System as a whole
is composed of functional processes for issuing, preserving and validating ProofMarks.
These processes are built upon a system architecture consisting of ProofMark servers,
ProofMark clients and ProofMark forensic repositories, where all issued ProofMarks
are securely indexed and preserved. In addition, trusted times are provided by an
authentic time authority, and the overall system operations are further enhanced by
well-established cryptographic techniques (such as RSA public-key cryptography and
secure hashing algorithms) and distributed networking techniques that provide for
“widely-witnessed” transactions.
At the heart of the ProofMark System is ProofSpace’s patented transient key technology.
Building upon widely deployed and trusted digital signature mechanisms, the primary
advantage of the transient key technology is the elimination of the administrative
overhead and security risks associated with a private signing key in the conventional
X.509 digital signature applications. In particular, the private signing key in the
ProofMark system is bound to a brief time interval and destroyed at the end of the time
interval. This short-lived nature of the private key dramatically reduces the overall risk
profile of the ProofMark System when compared to competing approaches.
The ProofMark system has been designed for businesses to solidify their electronic
records management processes, withstand regulatory audits, minimize legal exposure
and mitigate risks. The ProofMark system can be seamlessly integrated into the
information life cycle within any business application and benefit a wide spectrum
of industries. In summary, the ProofMark System provides a complete, effective and
compelling solution for addressing modern data integrity issues in the enterprise.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 3
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 4
ProofSpace White Paper
At a very high level, the ProofMark System architecture consists of ProofMark servers,
ProofMark clients and ProofMark forensic repositories where all issued ProofMarks
are securely indexed and preserved.
The ProofMark System is composed of four core Processes:
1.3 Integrating the ProofMark System into the Information Life Cycle
The ProofMark System is a “call on demand” application that can be integrated into
the information life cycle within any business application. It enables the application to
request, receive, and validate ProofMarks.
Generally speaking, Information Life Cycles have two distinctive requirements:
• There are points in the process or transaction where the state and time of the
information (e.g., a “version”) must be captured and preserved (“frozen”) for future
reference; and
• At points of future reference, the information must be validated to show that it has
remained unchanged with respect to both its content and reference to time before
further usage can be sanctioned (for example, before the data can be admitted as
evidence in a court of law).
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 6
ProofSpace White Paper
The illustration below represents a simplified Information Life Cycle composed of three
main components defined as follows:
• “Create” is an active phase where data (e.g., records, files, etc) is either created or
amended through authorized methods.
• “Store” is a passive phase when the data generated is stored or archived without
change.
• “Use” is a passive phase where information is used (but not changed) for an intended/
authorized purpose.
The illustration shows how the ProofMark System can be integrated into systems
and processes to support both of the ILC requirements outlined above. Consider, for
example, a contract. When the contract gets signed by the parties (executed) it must
be stored and retained for a prescribed retention period. The Contract Management
System (CMS) would request a ProofMark at the time the contract is executed, which
the ProofMark System would generate and return to the CMS. (Requesting a ProofMark
is illustrated by the lower left side of the diagram.) The CMS then associates the
ProofMark with the contract in a persistent way.
Years later, in a legal dispute the contract must be brought forward and submitted to
court as evidence. The contract would be accompanied by its ProofMark. A precondition
of being admitted into evidence might be that the authenticity of the contract (i.e.,
request a validation of the ProofMark) be reasonably demonstrated. The authenticity
of the contract is then irrefutably shown by submitting the ProofMark to the ProofMark
ProofSpace System for validation and reviewing the results of the validation report. (Requesting a
900 Clancy Ave NE ProofMark validation is illustrated by the lower right side of the diagram.)
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 7
ProofSpace White Paper
If the validation report is positive then the contract is more likely to be admitted into
evidence, and the organization can proceed with the confidence that its corporate
records will be available to defend its interests. If the validation report is negative, then
the situation requires further investigation. The same basic scenario might play out
with respect to corporate purchasing agreements, real estate documents, employment
contracts or many other types of business documents where authenticity is crucial.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 8
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 9
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 10
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE 1 A cryptographic hash (also known as “message digest”) of data is a short digital string that serves as a “finger print” of the data.
Grand Rapids, MI 49503 A secure hash function, such as SHA-256, is used to compute the hash.
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 11
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 12
ProofSpace White Paper
• ProofMark Server ID: the identifier for the server that hosted the interval that issued
the ProofMark, referred to as the ProofMark Issuing Server.
• Interval Chain Start Time: the start time of the Interval chain (a set of contiguous
expired Intervals) that contains the Interval that the ProofMark was issued in.
• Interval Start and Stop Time: the start and end time of the Interval within the Interval
chain that the ProofMark was issued in.
• Cross Certifying Servers: the location information of the Cross Certification Servers
that performed certifications of the Interval (at the time of its activation) that the
ProofMark was issued in.
• Archive Tree: the location information of all servers within the ProofMark System
where copies of the Interval that the ProofMark was issued in have been replicated.
The second type of Interval data elements is Interval Verification Elements that are
necessary to perform ProofMark validation. These data elements include cryptographic
signatures, corresponding public keys and hashes as follows:
• Interval Transient Key Signature: a digital signature by the “on-duty” Interval’s
transient private key of the hash of the next Interval’s concatenated Interval public key
and Interval start and stop time. In this way, the “on-duty” current Interval vouches
for the essential elements of its successor — the next Interval. This signature is used
in the validation process to verify that a given interval is the one vouched for by its
immediate predecessor and that its Interval public key and Interval start and stop
time have not changed since the Interval was activated. This verification is important
step in the determining the integrity of the Forensic Repository.
• ProofMark Server Signature: a digital signature by the ProofMark Server’s PKI
private key of the hash of the next Interval’s concatenated data elements at the time
of activation. In this way, the ProofMark Issuing Server vouches for interval records
that it activates. This signature is used in the ProofMark validation process to verify
that a given interval was activated by a legitimate issuing server and that the Interval
data elements stored in the Forensic Repository have not changed since the Interval
was activated. This is an important step in the verification of the integrity of the
Forensic Repository.
• Interval public key: required to decrypt the ProofMark transient key signature, a
ProofMark data element used in ProofMark validation.
• Previous Interval public key: required to decrypt the Interval transient key signature,
an Interval data element used in ProofMark validation.
• Previous Meta Digest: the hash of the most recently expired Interval’s digest log.
As each ProofMark is issued during the current Interval, a hash of each ProofMark
is concatenated to a rolling “digest log”, and digest logs are stored permanently in
the interval record of the Forensic Repository. This Previous meta digest allows the
integrity of a prior interval’s digest log to be verified. This is an important step in the
verification of the integrity of the Forensic Repository.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 13
ProofSpace White Paper
• ProofMark Sequence Number: the sequence number of the ProofMark within the
digest log of the Current Interval it was issued in. This permits (along with other
identifiers) the corresponding ProofMark digest to be found at a later time in the
digest log of the issuing Interval in the Forensic Repository.
The full set of 20 data elements that create the complete ProofMark are illustrated
in the figure below. The data elements in red indicated cryptographic data elements
that are used in ProofMark validation. This will be covered in the ProofMark validation
section of this document.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 15
ProofSpace White Paper
The validation process involves two levels of verifications. The first level is performed
locally on the ProofMark itself, and the second level is performed remotely at the
Forensic Repository. The ProofMark local verifications may be performed by the client
application, and they determine the integrity of the ProofMark and the integrity of the
original data. Increased assurance of the ProofMark can be achieved by performing
verifications at the Forensic Repository. This includes the verification of the Interval
Record, the cross certification record, and the digest log records that are relevant to the
requested ProofMark.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 16
ProofSpace White Paper
These two levels of verification are illustrated in the figure below and will be discussed
in the next section.
2 The ProofMark Transient Key Signature is decrypted using the Interval public key yielding the hash of the concatenation of the
previous and issued ProofMark digests. The Previous ProofMark digest contained in the submitted ProofMark is concatenated
with the recalculated ProofMark digest from data elements contained in the ProofMark and hashed. The two digests are
compared and, if identical, the ProofMark data elements have not been changed.
ProofSpace 3 The Original Data digest and Original Data Reference are retrieved from the ProofMark Request contained in the ProofMark. The
Original Data Reference is used to retrieve the Original Data and recalculate a fresh Original Data digest. The recalculated digest
900 Clancy Ave NE is then compared to the one contained in the ProofMark Request and if identical, the ProofMark is of the Original Data and that
Grand Rapids, MI 49503 Original Data has not changed since it was sealed.
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 17
ProofSpace White Paper
4 First, the Interval Record located in the Forensic Repository is identified using identifiers contained in the ProofMark: ProofMark
Server ID, Interval chain start time and Interval start time. Second, the X.509 certificate for the ProofMark Server is validated.
Third, the ProofMark Server Signature contained in the ProofMark is decrypted using the public key stored in the verified X.509
certificate yielding the hash of the Interval data elements that existed at the time the Interval was activated. The Forensic
Repository Interval Record data elements are hashed and compared with the hash from the server signature. Finally, the public
keys from the ProofMark and from the Forensic Repository Interval Record are compared. If all the above checks produce
positive results, then it can be concluded that the Interval was activated by a legitimate issuing server, that the Interval Record
has not changed since it was activated and that the ProofMark was issued by the validated Interval when it was “on-duty”.
ProofSpace
5 The ProofMark digest contained in the ProofMark is compared to the ProofMark digest located in the Forensic Repository. The
900 Clancy Ave NE Interval’s meta digest log is first located using the Interval Identifier Elements: ProofMark Server ID, Interval chain start time,
Grand Rapids, MI 49503 Interval start and stop time. The ProofMark digest itself is then located using the ProofMark Sequence Number.
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 18
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 19
ProofSpace White Paper
A key challenge of any information system is not only to mitigate outside threats by
hackers but risks posed by trusted insiders with administrative access to critical
configuration and operational system parameters and the source data itself. In order
to mitigate these vulnerabilities and ensure a high assurance validation process the
Forensic Repository is designed to detect unauthorized alterations using cryptographic
mechanisms6 and mitigate these risks using a widely witnessed7 and redundant8 system
design. These Forensic Repository attributes create a ProofMark System that has no
single point of failure, vulnerability and attack and has multiple points of validation. This
is illustrated by the figure and discussed in more detail below.
6 Cryptographic: As discussed previously, the core data construct of the Repository is the time Interval. The Repository has
“forensic” characteristics as there are several cryptographic mechanisms designed to ensure the integrity of time Intervals and
the ProofMark data preserved in the Repository.
7 Witnessed: The Repository’s time Intervals are “widely witnessed” through a certification process at the time they are activated.
Certification is performed by one or more Cross Certification Servers, an independent server other than the server activating the
ProofSpace Interval. The Interval certification process provides independent proof of the existence of an Interval.
900 Clancy Ave NE 8 Redundant: Critical data within the Repository is maintained redundant. Each time Interval activated by a ProofMark Issuing
Grand Rapids, MI 49503 Server is replicated throughout the ProofMark System distributed archives.
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 20
ProofSpace White Paper
9 For a given interval within the Interval chain, the Cross Interval Verification is accomplished by using the Previous Interval public key to
decrypt the Interval Transient Key Signature yielding a hash of the Interval public key, Interval start time and Interval stop time. A fresh
hash of these data elements from the Interval Record is generated and compared. If equal, then it is known that the Interval public key and
ProofSpace times are unchanged since they were signed by the previous interval’s Transient private key during activation. The cross interval verification
process continues with the previous Interval until all Intervals in the Interval chain are verified. If all Intervals in the Interval chain verify
900 Clancy Ave NE successfully then it can be assured that no Interval Record in the Interval chain has changed (all have integrity with respect to their Interval
Grand Rapids, MI 49503 public keys and Interval times) since the initiation of the Interval chain by the ProofMark Issuing Server.
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 21
ProofSpace White Paper
Widely Witnessed
As a new Interval is prepared for activation by a ProofMark Issuing Server it first must
be “certified” by Cross Certification servers within the ProofMark System (if configured
to do so). The ProofMark Issuing Server of the Interval to be activated requests a
certification (i.e., ProofMark) from Cross Certification Server(s). However, before a
certification is issued the time between the two servers is compared to ensure they
are within a prescribed tolerance. If so, the digest of the Interval data elements is
ProofMarked.
Cross certifications create a “widely witnessed” independent network of proof of the
existence of an Interval and its public key at a verified point-in-time. Cross certifications
effectively make it impossible for a trusted insider to manipulate an Interval after it is
activated.
Redundancy
As in any information system, data redundancy is critical to data availability. Data
redundancy is achieved by the replication of the issuing server’s Interval Records to
other servers within the ProofMark System (e.g., Cross Certification Servers) at the
time of activation.
Replication occurs according to an Archive Tree, a “map” listing the host locations of
the archives where copies of the Expired Interval are to be replicated. The Archive Tree
is constructed by using the Issuing Server’s “local archive” as the Root Archive and
then combining “as branches” the Archive Trees of Cross Certification Servers. Each
ProofMark contains the Archive Tree as a data element allowing it to indicate to the
ProofMark System where validation can be performed.
To the degree that an enterprise has implemented data storage architectures involving
such resilient mechanisms as mirroring or alternate data center sites, the ProofMark
System can be implemented to take advantage of many of these facilities and services.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 22
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 23
ProofSpace White Paper
The ProofMark System performs the Repository level verifications of the ProofMark
validation process discussed previously against Expired Intervals first by locating the
relevant Interval chain, followed by issuing Interval and finally the ProofMark digest.
The ProofMark System also performs periodic system integrity checks such as Cross
Interval Verifications testing the integrity of all Expired Intervals within an Interval chain
The ProofMark System performs asynchronous Interval Record (Interval data elements,
ProofMark digest logs, Cross Certification ProofMarks) replications in order to provide
high availability and redundancy against loss. The Interval Records are replicated
throughout the ProofMark System distributed network of servers through an archive
tree as previously discussed.
Generate the Previous Meta Digest: As a Current Interval is about to expire (and
therefore the next Interval is about to be activated) the hash of the digest log
(concatenation of all ProofMark digests) of the most recently expired Interval is
generated, referred to as the previous meta digest, and placed as an Interval data
element of the next Interval. This effectively binds evidence of all ProofMarks issued
during one Interval into its (n+2) successor.
Create Archive Tree: A “map” listing the host locations where copies of the Interval
record are to be replicated. The archive tree is constructed by using the ProofMark
Issuing Server’s “local archive” as the root archive and then combining “as branches”
the archive trees of Cross Certification Servers and Publication Servers.
Obtain Interval Certifications: If the ProofMark System is configured to require
independent certifications of new Intervals as they come “on duty” before they can be
activated, the ProofMark Issuing Server will requests and must successfully receive
Interval certifications from Cross Certification Server(s). However, a precondition of
receiving an Interval certification from a Cross Certification Server is its time must
match that of the ProofMark Issuing Server within a specified tolerance.
Generate ProofMark Server Signature: the ProofMark Issuing Server activating the
next Interval signs using its PKI server certificate (i.e., private key) the Interval data
elements of the new Interval.
Publish Interval Record: The Interval Record is published to the ProofMark Issuing
Server “root” archive and at other archives as specified by the Archive Tree.
Destroy Transient Private Key: Core to the high assurance characteristic of the
ProofMark System is the short-lived nature of the transient private key. The last step
of activation process is the irreversible destruction of the Current Interval’s transient
private key.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 25
ProofSpace White Paper
Conclusion
The ProofMark system is an innovative solution for ensuring and proving the
authenticity of electronic data and implementing trusted timestamps. The primary
advancement of the ProofMark technology is to eliminate the administrative overhead
and security risks associated with a private signing key in conventional X.509 digital
signature applications. This is accomplished by combining patented transient key
technology with other well-established cryptographic mechanisms.
Some highlights of the system are summarized below:
1. The ProofMark system does not issue signing keys to humans, which eliminates
a primary failure-point common to traditional digital signature systems. Instead,
a transient private key is generated and bound to a short time interval, just a few
minutes long.
2. Any ProofMark request is processed within the time interval using cryptographic
mechanisms: first the data is hashed to produce a digest, and then the digest is
signed by the interval transient private key to produce the ProofMark.
3. All ProofMark requests to the system are accumulated by chaining the digest
logs together in a secure way, preventing any fraudulent insertion, deletion, or
manipulation of the issued ProofMarks by either outsiders or insiders in the future.
4. At the end of each time interval, the transient private key is destroyed, preventing it
from ever being disclosed. This eliminates another risk factor common to competing
digital signature systems, where high-level private keys persist (and are therefore
vulnerable to be hacked or stolen) for years at a time. Furthermore, the transient
private keys associated with different time intervals are generated independently,
providing both forward and backward security even in the event that a particular
private key is compromised.
For more information about ProofSpace and its patented ProofMark Transient Key
technology, please visit the company website at www.proofspace.com.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 26
ProofSpace White Paper
Bibliography
[1] ANSI X9.31. Digital Signatures Using Reversible Public Key Cryptography for the
Financial Industry. 1998.
[2] ANSI X9.95. Trusted Time Stamp Management and Security. 2005.
[3] IEFT RFC 3161. C. Adams etc. Internet X.509 Public Key Infrastructure Time Stamp
Protocol. August 2001. http://www.ietf.org/rfc/rfc3161.txt
[4] NIST FIPS 180-2. Secure Hash Standard. August 2002.
http://csrc.nist.gov/publications/fips/fips180-2/fips180-2withchangenotice.pdf
[5] NIST FIPS 186-2. Digital Signature Standard. January 2000.
http://csrc.nist.gov/publications/fips/fips186-2/fips186-2-change1.pdf
[6] RSA Laboratories. Crypto FAQ. http://www.rsa.com/rsalabs/node.asp?id=2152
[7] Bruce Schneier. Applied Cryptography. Second Edition. John Wiley & Sons. 1996.
http://www.schneier.com/book-applied.html
[8] US Patent #6,381,696. M. Doyle. Method and System for Transient Key Digital Time
Stamps. Issued on April 30, 2002.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 27
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 28
ProofSpace White Paper
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 29
ProofSpace White Paper
Ed Reed
Mr. Reed is Sr. Director of Development Services at Aesec, a developer of verifiably
secure computing platforms. Previously, he was the Security Tzar at Novell, responsible
for leading security product strategy, and worked to develop Novell’s enterprise-
oriented identity-based computing efforts. He is a frequent speaker at industry,
technology and analyst briefings and conferences. His standards activities have
included work with the IETF (LDAP, LDUP), DMTF, and OASIS. He is a graduate of
Purdue University (BS), and Rochester Institute of Technology (MSCS).
Dean Tribble
Mr. Tribble is a leader in creating secure, distributed systems who has founded
several technology companies. He is a Principal Architect at Microsoft, where he led
development of security and compliance features for Microsoft Exchange, and now is
incubating new operating systems technologies. He was founder and CTO for Agorics,
which developed security and ecommerce solutions for Fortune 500 companies;
his work was granted nine U.S. patents in electronic commerce, secure distributed
systems, and computer resource allocation. Previously, he pioneered secure,
distributed programming languages, hypermedia publishing systems (pre-Web), and
on-line information marketplaces at companies such as Xerox PARC and Autodesk.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 30
ProofSpace White Paper
Howard Schmidt
Howard is a leading expert on defense, law enforcement and corporate security. Most
recently he was the Chief Security Strategist for the US CERT Partners Program for
the National Cyber Security Division, Department of Homeland Security. He was the
CISO and Chief Security Strategist for eBay, and was appointed by President Bush in
2001 as Vice Chair of the President’s Critical Infrastructure Protection Board and as
the Special Adviser for Cyberspace Security for the White House. He was the chief
security officer for Microsoft, where his duties included CISO, CSO and forming the
Trustworthy Computing Security Strategies Group. He was a supervisory special
agent and director of the Air Force Office of Special Investigations (AFOSI) Computer
Forensic Lab and Computer Crime and Information Warfare Division; while there, he
established the first dedicated computer forensic lab in the government. He has worked
on computer security with the FBI and the Army, and serves on numerous international
organizations. He is a co-author of the Black Book on Corporate Security, and is regularly
featured on CNN, CNBC, and Fox TV talking about cyber-security. He holds a bachelor’s
degree in business and a master’s degree in organizational management from the
University of Phoenix.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
www.proofspace.com ProofMark System Technical Overview — Revised December 2007 31
ProofSpace White Paper
Ed Gaudet
Ed is currently Vice President of Product Management and Marketing for Liquid
Machines. Most recently, Ed was Vice President of Worldwide Marketing for IONA
Technologies, the leading e-business platform provider for Web services integration.
During his three-year tenure at IONA, Ed was responsible for overall corporate
branding; product, partner and field marketing; and corporate communications. As
a member of the senior management team, Ed contributed to the company’s overall
business and operating strategies, which generated more than $181 million in
revenue in 2001. Prior to this experience, Ed held several senior marketing, product
management and business development positions in various start-up and public
software companies, including Rational Software, a provider of an integrated enterprise
development environment, and SQA Inc., a leader in automated testing solutions. Ed
received his bachelor’s degree from Bentley College in Waltham, Mass.
Michael A. Aisenberg
Mr. Aisenberg is Counselor to the President of Information & Infrastructure
Technologies, Inc., the largest operating subsidiary of Electronic Warfare Associates
(EWA). EWA is a privately held technology consulting and management firm, with global
government and commercial clients in the defense, intelligence, security and critical
infrastructure communities. He supports work with the Department of Homeland
SSecurity on cyber security response and the implementation of sector security plans
in IT and communications, with the Department of Justice on network-based abuses
against financial, transportation, defense and other critical infrastructures, and with
DNI on reform of the national classification system. A member of the D.C. Bar, he is a
graduate of the University of Pennsylvania and the University of Maine School of Law,
and attended Georgetown University Law Center. He has taught Communications Law
at the University of Maryland, and has been published on topics including Y2 K Liability
and Authentication in the Domain Name System.
ProofSpace
900 Clancy Ave NE
Grand Rapids, MI 49503
(312) 933.8823
©2007 ProofSpace. All Rights Reserved. ProofSpace, Transient Key, the ProofSpace logo, ProofMark and the ProofMark
System are trademarks of ProofSpace Inc. All other trademarks are owned by their respective companies. 32