Authentic Third-Party Data Publication

  • Premkumar Devanbu
  • Michael Gertz
  • Charles Martel
  • Stuart G. Stubblebine
Part of the IFIP International Federation for Information Processing book series (IFIPAICT, volume 73)


Integrity critical databases, such as financial data used in high-value decisions, are frequently published over the Internet. Publishers of such data must satisfy the integrity, authenticity, and non-repudiation requirements of clients. Providing this protection over public networks is costly.

This is partly because building and running secure systems is hard. In practice, large systems can not be verified to be secure and are frequently penetrated. The consequences of a system intrusion at the data publisher can be severe. This is further complicated by data and server replication to satisfy availability and scalability requirements.

We aim to reduce the trust required of the publisher of large, infrequently updated databases. To do this, we separate the roles of owner and publisher. With a few trusted digital signatures from the owner, an untrusted publisher can use techniques based on Merkle hash trees to provide authenticity and non-repudiation of the answer to a database query. We do not require a key to be held in an on-line system, thus reducing the impact of system penetrations. By allowing untrusted publishers, we also allow more scalable publication of large databases.


Leaf Node Range Query Query Evaluation Application Security Selection Query 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. [1]
    M. Bellare. Practice-oriented Provable Security. In G. Davida E. Okamoto and M. Mambo (eds.), Proceedings of First International Workshop on Information Security (ISW 97), LNCS 1396, Springer Verlag, 1997.Google Scholar
  2. [2]
    C.J. Date. An Introduction to Database Systems, Addison-Wesley, 1999.Google Scholar
  3. [3]
    P. Devanbu and S.G. Stubblebine. Software Engineering for Security: a roadmap. In The Future of Software Engineering, Special volume published in conjunction with ICSE 2000, ACM Press, 2000.Google Scholar
  4. [4]
    P. Devanbu, M. Gertz, C. Martel, and S.G¿ Stubblebine. Authentic Third-party Data Publication. Technical Report,, 2000.Google Scholar
  5. [5]
    M. D. Berg, M. V. Kreveld, M. Overmars and O. Schwarzkopf. Computational Geometry. Springer-Verlag, New York, 2000.Google Scholar
  6. [6]
    R.C. Merkle. A Certified Digital Signature. In Advances in Cryptology (Crypto’ 89), LNCS Vol. 435, Springer Verlag, 218–238, 1989.MathSciNetGoogle Scholar
  7. [7]
    M. Naor, K. Nissim. Certificate Revocation and Certificate Update. Proceedings of the 7th USENIX Security Symposium, 1998.Google Scholar
  8. [8]
    A. Silberschatz, H. Korth, S. Sudarshan. Database System Concepts, (3rd edition), McGraw-Hill, 1997.Google Scholar
  9. [9]
    S. G. Stubblebine. Recent-secure authentication: Enforcing Revocations in distributed systems. IEEE Computer Society Symp. on Security and Privacy, 1995.Google Scholar
  10. [10]
    J. D. Tygar Open Problems in Electronic Commerce. In Proc. SIGACTSIGMOD-SIGART Symp. on Principles of Database Systems, ACM, 101, 1999.Google Scholar

Copyright information

© Kluwer Academic Publishers 2002

Authors and Affiliations

  • Premkumar Devanbu
    • 1
  • Michael Gertz
    • 1
  • Charles Martel
    • 1
  • Stuart G. Stubblebine
    • 2
  1. 1.Department of Computer ScienceUniversity of CaliforniaDavis
  2. 2.CertCoNew York

Personalised recommendations