fips 201 framework: special pubs 800-73,76,78 jim dray hspd-12 workshop may 4/5, 2005
TRANSCRIPT
![Page 1: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/1.jpg)
FIPS 201 Framework:FIPS 201 Framework:Special Pubs 800-73,76,78Special Pubs 800-73,76,78
Jim Dray
HSPD-12 Workshop
May 4/5, 2005
![Page 2: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/2.jpg)
Special Publication 800-73Special Publication 800-73
• PIV card application definitiono NOT a general purpose card platform spec!
• Part 1: Common data model and migration• Part 2: Transition card interfaces• Part 3: End point specification
![Page 3: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/3.jpg)
Part 1: Mandatory Data ObjectsPart 1: Mandatory Data Objects
• PIV credential element objectso Card Capability Container: Discoveryo Cardholder Unique Identifier: PACS 2.2o PIV Authentication Keyo Fingerprint Buffers (2)o Security Object
![Page 4: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/4.jpg)
Part 1: Optional Data ObjectsPart 1: Optional Data Objects
• Optional PIV credential element objectso Printed Informationo Facial Imageo Digital Signature Keyo Key Management Keyo Card Authentication Key
![Page 5: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/5.jpg)
Part 1: Migration IssuesPart 1: Migration Issues
• Some agencies have smart card deployments• Government Smart Card Interoperability
Specification (NISTIR 6887)• Migration path is based on continuity of the PIV
data model• Legacy agencies MAY use Part 2 transition
specification
![Page 6: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/6.jpg)
SP800-73 Part 2SP800-73 Part 2
• Essentially a PIV profile of GSC-IS• Maintains the GSC-IS dual card interfaces
o File systemo Virtual Machine
• Developed by the Government Smart Card Interagency Advisory Board
• Part 2 is informative
![Page 7: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/7.jpg)
SP800-73 Part 3SP800-73 Part 3
• Unified card command interface• Compliant with existing international
standards (ISO 7816)• Technology neutrality: Implementable on
any card platform• Essential features for:
o High degree of PIV card interoperabilityo Future-proofing PIV framework
![Page 8: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/8.jpg)
Part 3: Data ModelPart 3: Data Model
• Data model is common to both Parts 2 and 3
• Different identifiers (BER-TLV) used at the card edge in Part 3
![Page 9: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/9.jpg)
Part 3: Standard NamespacesPart 3: Standard Namespaces
• ASN.1 Object Identifiers in the PIV arc of the Computer Security Object Register at the Client Application Programming Interface
• PIV RID is the root of card Application Identifiers(AIDs)
• BER-TLV tags for data objects at the card interface
![Page 10: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/10.jpg)
Part 3: PIV Card ApplicationPart 3: PIV Card Application
• AID is ‘A0 00 00 xx xx 00 00 10 00 01 00’• Full PIV RID to be published by NIST• Access Control Rules applied to PIV
credential objects• Provides a set of 8 ISO compliant card
interface commands• Restricted functionality in contactless mode
![Page 11: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/11.jpg)
Part 3: Client Application Part 3: Client Application Programming InterfaceProgramming Interface
• Equivalent to GSC-IS Basic Services Interface
• Provides 9 higher level commands• Implemented by middleware• PIV middleware is MUCH simpler than
GSC-IS middleware because card command mapping is not required
![Page 12: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/12.jpg)
Part 3: Reference Part 3: Reference ImplementationImplementation
• Part 3 compliant implementation• PIV card application running in a card
simulator• Middleware• Publicly available• Basis for conformance tests• Estimated completion date June 25
![Page 13: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/13.jpg)
SP800-73 SummarySP800-73 Summary
• PIV II card application and client application programming interface spec
• Informative Part 2 transition specification for migrating legacy GSC-IS deployments
• Normative Part 3 end point specification• All agencies are to reach full deployment of Part 3
PIV cards by the end of their PIV II Phase, regardless of the migration path chosen.
![Page 14: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/14.jpg)
Special Publication 800-78 Special Publication 800-78 OverviewOverview
• FIPS 201 relies on cryptographyo To protect objects stored on the PIV cardo To authenticate the PIV card or cardholdero To authenticate the source and integrity of
status information
![Page 15: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/15.jpg)
Cryptographic Strength Cryptographic Strength RequirementsRequirements
• SP 800-78 mandates a transition from 80 bit strength to 112 bits of strength by 1/1/2011o Cryptographic keys that provide long term data
protection transition by 1/1/2009 to provide two years “forward security”
• Elliptic Curve Cryptography is specified with a minimum of 112 bits of strength (224 bit keys)o Avoid transition issues
![Page 16: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/16.jpg)
Cryptographic Objects Stored on Cryptographic Objects Stored on the PIV Cardthe PIV Card
• FIPS 201 specifiedo Cryptographic keyso Digitally signed objects
• CHUID
• Biometrics
• X.509 Certificates
• SP 800-073 specifiedo Authentication/Integrity Object
![Page 17: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/17.jpg)
Cryptographic keysCryptographic keys
• Asymmetric private keyso PIV Authentication key (Mandatory)o Digital Signature key (Optional)o Key Management key (Optional)
• May support key transport or key agreement
• Card Management Key (Optional)o Symmetric key
• PIV Cardholder Authentication Key (Optional)o May be symmetric or asymmetric
![Page 18: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/18.jpg)
Asymmetric Algorithms for Asymmetric Algorithms for Cryptographic KeysCryptographic Keys
• SP 800-78 limits asymmetric keys to RSA and ECCo RSA must be 1024/2048/3072
• 1024 bit keys phased out by 1/1/2011• Digital signature and key management keys transition by
1/1/2008 to provide for forward security• Authentication keys transition by 1/1/2011 since forward
security is not an issue
o ECC must use a recommended curve from FIPS 186-2• 224 through 283 bit keys• No phase out specified
![Page 19: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/19.jpg)
Symmetric Algorithms for Symmetric Algorithms for Cryptographic KeysCryptographic Keys
• SP 800-78 limits symmetric keys to Triple DES (TDEA) and AESo TDEA must be two key or three key
• Two key TDEA phased out by 1/1/2011
o AES may be 128, 192, or 256 bit keys• No phase out specified
![Page 20: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/20.jpg)
Digitally Signed ObjectsDigitally Signed Objects
• Signatures may be generated using RSA or ECDSAo RSA may use PKCS #1 or PSS padding
schemeso SHA-1, SHA-224, and SHA-256 hash
algorithms• SHA-1 phased out by 1/1/2011
• Phase out depends on card expiration, not signature generation date
![Page 21: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/21.jpg)
SP 800-73 Security ObjectSP 800-73 Security Object
• ICAO Authentication/Integrity Object• Digitally signed hash table
o The table includes a message digest for each of the objects (CHUID, keys, etc.) stored on the card
o Message digests are generated using SHA-1, SHA-224, or SHA-256
• SHA-1 phased out by 1/1/2011o Signature requirements from previous slide
![Page 22: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/22.jpg)
Status InformationStatus Information
• FIPS 201 relies upon digitally signed X.509 CRLs and OCSP responses to distribute status information
• Signatures may be generated using RSA or ECDSAo RSA may use PKCS #1 or PSS padding schemeso SHA-1, SHA-224, and SHA-256 hash algorithms
• SHA-1 phased out by 1/1/2011
• Phase out depends on signature generation date
![Page 23: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/23.jpg)
Special Publication 800-76Special Publication 800-76
• Biometric Data Specification for Personal Identity Verification
• Major issue: Minutia vs. full imageo File sizeo Interoperabilityo Privacy
• Still in draft form
![Page 24: FIPS 201 Framework: Special Pubs 800-73,76,78 Jim Dray HSPD-12 Workshop May 4/5, 2005](https://reader036.vdocuments.net/reader036/viewer/2022062511/55175648550346176e8b45de/html5/thumbnails/24.jpg)
Contact InformationContact Information
Curt Barker ([email protected]): PIV Program Manager
Jim Dray ([email protected] ): SP800-73
Terry Schwarzhoff ([email protected]): NIST Smart Card Program Manager, Standards Lead
NIST PIV Website: http://csrc.nist.gov/piv-project