A User Centric Security Model for Tamper-Resistant Devices

More documents

Recommendations

Info

C.4 Secure and Trusted Channel Protocol Service Provider 295 temp . length , this . SignedData . getValueBytes ( ) , 0 , 296 SCVerificationKey , 297 P r o t o c o l H e l p e r C l a s s .SIGN_MODE_VERIFICATION) ) {} 298 else { 299 System . out . p r i n t l n ( 300 " S i g n a t u r e V e r i f i c a t i o n F a i l e d . . . . . . Check code " ) ; 301 } 302 } 303 } catch ( Exception cE ) { 304 System . out . p r i n t l n ( 305 " Error i n ProtocolHandler . inMessageProcessing : " + cE . g e t C l a s s ( ) . getName ( ) ) ; 306 } 307 return true ; 308 } 309 public s t a t i c S t r i n g byteToString ( byte [ ] inArray ) { 310 byte [ ] HEX_CHAR_TABLE = { 311 ( byte ) ' 0 ' , ( byte ) ' 1 ' , ( byte ) ' 2 ' , ( byte ) ' 3 ' , ( byte ) ' 4 ' , ( byte ) 312 ' 5 ' , ( byte ) ' 6 ' , ( byte ) ' 7 ' , ( byte ) ' 8 ' , ( byte ) ' 9 ' , ( byte ) ' a ' , 313 ( byte ) ' b ' , ( byte ) ' c ' , ( byte ) ' d ' , ( byte ) ' e ' , ( byte ) ' f ' 314 } ; 315 byte [ ] hex = new byte [ 2 ∗ inArray . l e n g t h ] ; 316 int index = 0 ; 317 for ( byte b : inArray ) { 318 int v = b & 0xFF ; 319 hex [ index++] = HEX_CHAR_TABLE[ v >>> 4 ] ; 320 hex [ index++] = HEX_CHAR_TABLE[ v & 0xF ] ; 321 } 322 try { 323 return new S t r i n g ( hex , "ASCII" ) ; 324 } catch ( Exception cE ) { 325 System . out . p r i n t l n ( " Exception in bytesToString : " + 326 cE . getMessage ( ) ) ; 327 } 328 return " Error " ; 329 } 330 void childExtractionFromCTLV ( ConstructedTLV inCTLV) { 331 try { 332 int c h i l d s = inCTLV . getChildNumbers ( ) ; 333 PrimitiveTLV pTemp = null ; 334 ConstructedTLV cTemp = null ; 335 while ( c h i l d s > 0) { 336 switch (inCTLV . nextType ( ) ) { 337 case 1 : 338 pTemp = ( PrimitiveTLV )inCTLV . getNext ( ) ; 339 i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 340 this . SCDHChallenge . getTagName ( ) ) ) { 341 this . SCDHChallenge = pTemp ; 342 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 343 this . SCRandomNumber . getTagName ( ) ) ) { 310
C.4 Secure and Trusted Channel Protocol Service Provider 344 this . SCRandomNumber = pTemp ; 345 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 346 this . MACedData . getTagName ( ) ) ) { 347 this . MACedData = pTemp ; 348 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 349 this . SPCookie . getTagName ( ) ) ) { 350 i f ( Arrays . e q u a l s (pTemp . getBytesTlvRepresentation ( ) , 351 this . SPCookie . getBytesTlvRepresentation ( ) ) ) {} 352 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 353 this . SCIdentity . getTagName ( ) ) ) { 354 this . SCIdentity = pTemp ; 355 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 356 this . SignedData . getTagName ( ) ) ) { 357 this . SignedData = pTemp ; 358 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 359 this . PublicExponent . getTagName ( ) ) ) { 360 this . PublicExponent = pTemp ; 361 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 362 this . PublicModulus . getTagName ( ) ) ) { 363 this . PublicModulus = pTemp ; 364 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 365 this . PlatformHash . getTagName ( ) ) ) { 366 this . PlatformHash = pTemp ; 367 } else i f ( Arrays . e q u a l s (pTemp . getTagName ( ) , 368 this . U s e r I d e n t i t y . getTagName ( ) ) ) { 369 this . U s e r I d e n t i t y = pTemp ; 370 } 371 break ; 372 case 0 : cTemp = ( ConstructedTLV )inCTLV . getNext ( ) ; 373 i f ( Arrays . e q u a l s (cTemp . getTagName ( ) , 374 this . EncryptedData . getTagName ( ) ) ) { 375 this . EncryptedData = cTemp ; 376 } else i f ( Arrays . e q u a l s (cTemp . getTagName ( ) , 377 S C U s e r C e r t i f i c a t e . getTagName ( ) ) ) { 378 this . S C U s e r C e r t i f i c a t e = cTemp ; 379 } 380 else 381 i f ( Arrays . e q u a l s (cTemp . getTagName ( ) , 382 S C C e r t i f i c a t e . getTagName ( ) ) ) { 383 this . S C C e r t i f i c a t e = cTemp ; 384 } 385 break ; 386 default : 387 System . out . p r i n t l n ( " Error In Parsing Input Message " ) ; 388 } 389 c h i l d s −−; 390 } 391 } catch ( Exception e ) { 392 System . out . p r i n t l n ( 393 " Error i n ProtocolHanlder . ChildExtractionMethod : " + e . g e t C l a s s ( ) . getName ( ) ) ; 311
Page 1 and 2:
A User Centric Security Model for T
Page 3 and 4:
Declaration These doctoral studies
Page 5 and 6:
R. N. Akram, K. Markantonakis, and
Page 7 and 8:
Abstract In this thesis we propose
Page 9 and 10:
CONTENTS 3.4.1 Supplier . . . . . .
Page 11 and 12:
CONTENTS 7 Application Sharing Mech
Page 13 and 14:
CONTENTS C.4 Secure and Trusted Cha
Page 15 and 16:
LIST OF FIGURES 8.6 Control ow diag
Page 17 and 18:
List of Abbreviations AAC Applicati
Page 19 and 20:
1.1 Setting the Scene 1.1 Setting t
Page 21 and 22:
1.2 A Brief History of Smart Cards
Page 23 and 24:
1.3 Motivation and Challenges Over
Page 25 and 26:
1.3 Motivation and Challenges compu
Page 27 and 28:
1.4 Contributions the UCTD manufact
Page 29 and 30:
1.5 Structure of the Thesis traditi
Page 31 and 32:
Chapter 2 User Centric Tamper-Resis
Page 33 and 34:
2.2 Rationale for a User Centric Ta
Page 35 and 36:
2.2 Rationale for a User Centric Ta
Page 37 and 38:
2.3 Candidates for User Centric Tam
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Businesses Governments Privacy Pres
Page 45 and 46:
2.4 The User Centric Tamper-Resista
Page 47 and 48:
2.5 Case Studies an enrolment proce
Page 49 and 50:
2.5 Case Studies issued the applica
Page 51 and 52:
Chapter 3 Smart Card Ownership Mode
Page 53 and 54:
3.2 Issuer Centric Smart Card Owner
Page 55 and 56:
3.2 Issuer Centric Smart Card Owner
Page 57 and 58:
3.3 Frameworks for the ICOM which i
Page 59 and 60:
3.3 Frameworks for the ICOM Applica
Page 61 and 62:
3.3 Frameworks for the ICOM which i
Page 63 and 64:
3.3 Frameworks for the ICOM Element
Page 65 and 66:
3.4 User Centric Smart Card Ownersh
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
3.5 Security and Operational Requir
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Service Provider 3.6 Coopetitive Ar
Page 79 and 80:
Chapter 4 User Centric Smart Card A
Page 81 and 82:
4.2 Platform Architecture Platform
Page 83 and 84:
4.2 Platform Architecture manager c
Page 85 and 86:
4.3 Trusted Environment & Execution
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
4.4 Security Assurance and Validati
Page 93 and 94:
4.5 Attestation Mechanisms 4.5 Atte
Page 95 and 96:
4.5 Attestation Mechanisms rational
Page 97 and 98:
4.5 Attestation Mechanisms otherwis
Page 99 and 100:
4.6 Device Ownership 4.6.2 User Own
Page 101 and 102:
4.7 Attestation Protocol can succes
Page 103 and 104:
4.7 Attestation Protocol an adversa
Page 105 and 106:
4.7 Attestation Protocol SC i ′ a
Page 107 and 108:
4.8 Protocol Analysis CasperFDR app
Page 109 and 110:
4.9 Summary whereas the online atte
Page 111 and 112:
5.1 Introduction 5.1 Introduction E
Page 113 and 114:
5.2 GlobalPlatform Card Management
Page 115 and 116:
5.3 Multos Card Management Framewor
Page 117 and 118:
5.4 Proposed Smart Card Management
Page 119 and 120:
5.4 Proposed Smart Card Management
Page 121 and 122:
5.5 Card Management-Related Issues
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Chapter 6 Secure and Trusted Channe
Page 129 and 130:
6.2 Secure Channel Protocols 6.2 Se
Page 131 and 132:
6.2 Secure Channel Protocols smart
Page 133 and 134:
6.2 Secure Channel Protocols SOG-16
Page 135 and 136:
6.2 Secure Channel Protocols Notati
Page 137 and 138:
6.3 Secure and Trusted Channel Prot
Page 139 and 140:
6.4 Secure and Trusted Channel Prot
Page 141 and 142:
6.5 Application Acquisition and Con
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
6.6 Analysis of the Proposed Protoc
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
6.7 Summary For the STCP ACA , we n
Page 157 and 158:
Chapter 7 Application Sharing Mecha
Page 159 and 160:
7.2 Application Sharing Mechanism 7
Page 161 and 162:
7.2 Application Sharing Mechanism I
Page 163 and 164:
7.2 Application Sharing Mechanism a
Page 165 and 166:
7.3 UCTD Firewall utilises CDAM to
Page 167 and 168:
7.3 UCTD Firewall application. Ther
Page 169 and 170:
7.3 UCTD Firewall 7.3.6 Cross-Devic
Page 171 and 172:
7.3 UCTD Firewall and asynchronous
Page 173 and 174:
7.3 UCTD Firewall Table 7.2: Protoc
Page 175 and 176:
7.4 Application Binding Protocol L
Page 177 and 178:
7.5 Platform Binding Protocol The r
Page 179 and 180:
7.6 Application Binding Protocol D
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Chapter 8 Smart Card Runtime Enviro
Page 189 and 190:
8.2 Smart Card Runtime Environment
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
8.3 Runtime Protection Mechanism In
Page 197 and 198:
8.3 Runtime Protection Mechanism it
Page 199 and 200:
8.3 Runtime Protection Mechanism er
Page 201 and 202:
8.3 Runtime Protection Mechanism id
Page 203 and 204:
8.3 Runtime Protection Mechanism Th
Page 205 and 206:
8.4 Analysis of the Runtime Protect
Page 207 and 208:
8.4 Analysis of the Runtime Protect
Page 209 and 210:
8.5 Summary representation; the abs
Page 211 and 212:
Chapter 9 Backup, Migration, and De
Page 213 and 214:
9.2 Backup and Migration Framework
Page 215 and 216:
9.2 Backup and Migration Framework
Page 217 and 218:
9.3 Application Deletion tion of th
Page 219 and 220:
9.3 Application Deletion The deleti
Page 221 and 222:
9.3 Application Deletion authorises
Page 223 and 224:
9.5 Summary 9.5 Summary In this cha
Page 225 and 226:
10.1 Summary and Conclusions 10.1 S
Page 227 and 228:
10.1 Summary and Conclusions giving
Page 229 and 230:
10.2 Recommendations for Future Wor
Page 231 and 232:
Appendix A Description of Protocols
Page 233 and 234:
A.3 Aziz-Die (AD) Protocol on the p
Page 235 and 236:
A.5 Just-Fast-Keying (JFK) Protocol
Page 237 and 238:
A.8 Markantonakis-Mayes (MM) Protoc
Page 239 and 240:
A.9 Sirett-Mayes-Markantonakis (SM)
Page 241 and 242:
B.1 Brief Introduction to the Caspe
Page 243 and 244:
B.3 Secure and Trusted Channel Prot
Page 245 and 246:
B.4 Secure and Trusted Channel Prot
Page 247 and 248:
B.6 Application Binding Protocol L
Page 249 and 250:
B.7 Platform Binding Protocol B.7 P
Page 251 and 252:
B.8 Application Binding Protocol D
Page 253 and 254:
C.1 Oine Attestation Mechanism C.1
Page 255 and 256:
C.1 Oine Attestation Mechanism 93 (
Page 257 and 258:
C.1 Oine Attestation Mechanism 194
Page 259 and 260: C.1 Oine Attestation Mechanism 47 (
Page 261 and 262: C.1 Oine Attestation Mechanism 148
Page 263 and 264: C.2 Online Attestation Mechanism C.
Page 265 and 266: C.2 Online Attestation Mechanism 10
Page 273 and 274: C.3 Attestation Protocol 15 import
Page 275 and 276: C.3 Attestation Protocol 112 f a l
Page 277 and 278: C.3 Attestation Protocol 214 } 215
Page 279 and 280: C.3 Attestation Protocol 312 inLeng
Page 281 and 282: C.3 Attestation Protocol 410 this .
Page 283 and 284: C.3 Attestation Protocol 7 import j
Page 285 and 286: C.3 Attestation Protocol 107 this .
Page 287 and 288: C.3 Attestation Protocol 204 ( this
Page 289 and 290: C.3 Attestation Protocol 302 } 303
Page 291 and 292: C.4 Secure and Trusted Channel Prot
Page 309: C.4 Secure and Trusted Channel Prot
Page 333 and 334: C.6 Application Acquisition and Con
Page 361 and 362:
C.6 Application Acquisition and Con
Page 363 and 364:
C.6 Application Acquisition and Con
Page 365 and 366:
C.7 Application Binding Protocol -
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
C.9 Platform Binding Protocol 17 im
Page 407 and 408:
C.9 Platform Binding Protocol 119 p
Page 409 and 410:
C.9 Platform Binding Protocol 221 i
Page 411 and 412:
C.9 Platform Binding Protocol 323 c
Page 413 and 414:
C.9 Platform Binding Protocol 424 +
Page 415 and 416:
C.9 Platform Binding Protocol 524 S
Page 417 and 418:
Page 419 and 420:
C.9 Platform Binding Protocol 47 (
Page 421 and 422:
C.9 Platform Binding Protocol 149 J
Page 423 and 424:
Page 425 and 426:
C.9 Platform Binding Protocol 350 +
Page 427 and 428:
C.9 Platform Binding Protocol 451 p
Page 429 and 430:
C.9 Platform Binding Protocol 552 r
Page 431 and 432:
C.10 Abstract Virtual Machine 42 "
Page 433 and 434:
C.11 Implementation Helper Classes
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
BIBLIOGRAPHY August 2009, pp. 2035.
Page 453 and 454:
BIBLIOGRAPHY Available: http://www.
Page 455 and 456:
BIBLIOGRAPHY Institute of Technolog
Page 457 and 458:
BIBLIOGRAPHY ing, vol. 2, pp. 42342
Page 459 and 460:
BIBLIOGRAPHY Available: http://csrc
Page 461 and 462:
BIBLIOGRAPHY Group_TRUST/PubsPDF/CA
Page 463 and 464:
BIBLIOGRAPHY [161] D. A. Basin, S.
Page 465 and 466:
BIBLIOGRAPHY pp. 1414. [186] R. N.
Page 467 and 468:
BIBLIOGRAPHY [208] T. S. Messerges,
Page 469:
BIBLIOGRAPHY Science, P. Samarati,
show all

A User Centric Security Model for Tamper-Resistant Devices

Create successful ePaper yourself

Delete template?

Save as template?