Show simple item record

Integrating secure hardware into modern security systems: Authentication, secure storage, and secure bootstrap.

dc.contributor.authorItoi, Naomaru
dc.contributor.advisorHoneyman, Peter
dc.date.accessioned2016-08-30T15:12:09Z
dc.date.available2016-08-30T15:12:09Z
dc.date.issued2001
dc.identifier.urihttp://gateway.proquest.com/openurl?url_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:dissertation&res_dat=xri:pqm&rft_dat=xri:pqdiss:3000968
dc.identifier.urihttps://hdl.handle.net/2027.42/123147
dc.description.abstractModern computer systems have critical security problems because of two wrong assumptions security system developers make: that computers are trustworthy, and that users choose good passwords. First, personal computers and workstations are physically insecure: their hard disks can be taken out, and memories can be probed. Second, the software is not trustworthy because bugs introduce vulnerabilities, some of which lead to system administrative account (root) compromise. As software is growing so rapidly, it is very difficult to debug it completely. Third, network services require user authentication, and almost all systems rely on user chosen passwords for authentication. As the number of the applications and web sites that require passwords explodes, it is impossible for users to maintain a good, different password on every site. As a result, the authentication systems are vulnerable to password guessing attack. Secure hardware, e.g., smartcards and secure coprocessors, can solve these problems. First, it provides a physically secure storage and computational device. Second, it is a more security oriented, smaller and simpler device than workstations, making it more likely to be bug-free. Third, it can store a randomly generated key to replace a password. However, this has not happened yet; secure hardware is not used widely today because secure hardware based security systems tend to introduce new user interfaces and expensive migration cost. I solve these problems by taking an experimental approach, namely, integrating secure hardware into existing security infrastructures: authentication, secure storage, and secure bootstrap process. The integration improves the security of the current systems, while maintaining the same user interfaces. To prove this method possible and cost effective, I implement the following systems: (1) Kerberos client/smartcard integration; (2) Kerberos server/secure coprocessor integration; (3) Remote extension of Kerberos smartcard; (4) Smartcard Filesystem; (5) Smartcard Secured Cryptographic File System; (6) Smartcard Based Personal Secure Booting. These projects successfully improve the security of the existing systems. Performance overhead introduced by secure hardware integration is not significant in some project, but it is in the others. The performance issue is discussed in detail.
dc.format.extent170 p.
dc.languageEnglish
dc.language.isoEN
dc.subjectAuthentication
dc.subjectBootstrap
dc.subjectIntegrating
dc.subjectModern
dc.subjectSecure Hardware
dc.subjectSecurity Systems
dc.subjectSmartcard
dc.subjectStorage
dc.titleIntegrating secure hardware into modern security systems: Authentication, secure storage, and secure bootstrap.
dc.typeThesis
dc.description.thesisdegreenamePhDen_US
dc.description.thesisdegreedisciplineApplied Sciences
dc.description.thesisdegreedisciplineComputer science
dc.description.thesisdegreedisciplineElectrical engineering
dc.description.thesisdegreegrantorUniversity of Michigan, Horace H. Rackham School of Graduate Studies
dc.description.bitstreamurlhttp://deepblue.lib.umich.edu/bitstream/2027.42/123147/2/3000968.pdf
dc.owningcollnameDissertations and Theses (Ph.D. and Master's)


Files in this item

Show simple item record

Remediation of Harmful Language

The University of Michigan Library aims to describe library materials in a way that respects the people and communities who create, use, and are represented in our collections. Report harmful or offensive language in catalog records, finding aids, or elsewhere in our collections anonymously through our metadata feedback form. More information at Remediation of Harmful Language.

Accessibility

If you are unable to use this file in its current format, please select the Contact Us link and we can modify it to make it more accessible to you.