Ace:Main: Difference between revisions
From Adapt
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
| Installation Guide || System Documentation | | Installation Guide || System Documentation | ||
|- | |- | ||
| User Guide || IMS Witness Google Goup | | User Guide || [[http://groups.google.com/group/ace-ims-witness?hl=en|IMS Witness Google Goup]] | ||
|- | |- | ||
| || IMS Witness UMIACS listserv | | || [[http://mailman.umiacs.umd.edu/mailman/listinfo/ims-witness|IMS Witness UMIACS listserv]] | ||
|} | |} | ||
Revision as of 19:19, 9 September 2008
ACE (Auditing Control Environment) is a prototype system that incorporates a new methodology to address the integrity of long term archives using rigorous cryptographic techniques. ACE continuously audits the contents of the various objects according to the policy set by the archive, and provides mechanisms for an independent third-party auditor to certify the integrity of any object.
Our approach will allow an independent auditor to verify the integrity of every version of an archived digital object as well as link the current version to the original form of the object when it was ingested into the archive. Also, ACE is very cost effective and scalable while making no assumptions about the archive architecture.
ACE consists of two components, the first an Audit Manager(AM) that checks files locally to ensure they have not been compromised. The second part, the Integrity Management Service (IMS), issues tokens that the AM can use to verify that its local store of file digests has not been tampered with. In addition the IMS published a daily witness that can be used to ensure the IMS has not acted maliciously or been compromised.
| Audit Manager | Integrity Management Service |
| Installation Guide | System Documentation |
| User Guide | [Witness Google Goup] |
| [Witness UMIACS listserv] |
