centre for applied cryptographic research workshop, nov. 8, 1999

©1999 InfoGard Laboratories, Inc

Centre for Applied Cryptographic Research workshop, Nov. 8, 1999

Third party evaluations of CA cryptographic implementations

Speakers: Les Biggs

Pat Lareau November 8, 1999


What a cryptomodule provides the CA

• Secure, trusted cryptographic services

• Key and certificate management services

• Physical protection of: > sensitive data (e.g. keys)> cryptographic and certificate management functions

• Enforcement of the CA’s security policy


What FIPS 140-1 certification provides the CA: Assurance

• That the cryptomodule implements its security policy

• That sound cryptographic processes are employed

• That cryptographic processes are correctly implemented

• That Non-cryptographic processes are implemented as specified (Optional)


Critical areas addressed by FIPS 140-1

• Key generation and management services

• Algorithm security

• Access control

• Interface control

• Physical protection for data and functions

• "Health" monitoring mechanisms

• EM emanations

• Assurance that the design implements the spec


Level 1 Basic security requirements

Level 2 Tamper evidence, role-based authentication

Level 3 Enhanced physical security, identity-based authentication

Level 4-Envelope protectionEnvironmental protection, Formal Modeling

Increasin

g Secu

rity

FIPS 140-1 Security Levels


Evaluation Vs Verification Vs Certification

• Evaluation > A self-guided examination of device characteristics by

a tester with credentials acceptable to the sponsor

• Verification > A self-guided process for verifying compliance to a

standard by a tester with credentials acceptable to the sponsor

• Certification> A formal, standardized testing process, performed by

an accredited laboratory, to validate claimed compliance to an official standard


Validation Process Steps

ModuleDocumentation

Physical Product

ValidationTesting

ValidationPlan

Report Generation

Submit Report to NIST/CSE


Validation Process Steps

Module Documentation

Physical Product

ValidationTesting

ValidationPlan

Report Generation

Submit Report to NIST/CSE


Relative roles and positioning of FIPS 140-1 and CC in CA evaluations

FIPS is a detailed specification CC provides a language for developing

specifications

FIPS is a specific, detailed testing process CC provides a process for developing test

requirements


Relative roles and positioning, cont’

FIPS addresses core cryptographic requirements

CC addresses system wide security objectives (may reference FIPS in the protection profile)

FIPS is mandated as an outgrowth of US federal law

CC is voluntary on an international scale


Other critical CA processes may also be protected by the cryptomodule

Cryptomodule can be at the center of the CA, enforcing security rules Cert database protection from modification and

substitution Secure, strong database access control Secure database management secure, authenticated CA and database

communications/exchanges


FIPS 140-1 naturally extends to non-federal sectors

• USPS

• DOD

• Banking

• Point of sale/credit card

• International support


Snapshot program status

• Number of certifications

• Certifications by Level

• Certification levels Vs Time

• Physical configurations


FIPS 140-1 Certifications

0

10

20

30

40

50

60

70

Nov-95Jan-96Mar-96May-96Jul-96Sep-96Nov-96Jan-97Mar-97May-97Jul-97Sep-97Nov-97Jan-98Mar-98May-98Jul-98Sep-98Nov-98Jan-99Mar-99May-99Jul-99Sep-99


0

5

10

15

20

25

30

35

Level 1 Level 2 Level 3 Level 4

Certifications by Level


Certification Level Vs Time


Physical Configuration


Module cost

• Levels 1 thru 3 gradually increase in cost> $100 to $ 800 range

• Big jump at level 4> $2,000 range

• Security levels should scale with CA’s level in the PKI


What we want to leave with you today

FIPS is not just crypto, it is a way of thinking about a problem

FIPS cryptomodules can implement and protect more than crypto

What distinguishes FIPS from other processes

centre for applied cryptographic research workshop, nov. 8, 1999

Documents