• Home

  • Documents

  • Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation...
32
Cryptographic Module Validation Program Where security starts …. Randall J. Easter Director, NIST CMVP March 03, 2006

Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

  • Upload
    lenhu

  • View
    224

  • Download
    2

Embed Size (px)

Citation preview

Page 1: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Cryptographic Module Validation Program

Where security starts hellip

Randall J Easter Director NIST CMVP

March 03 2006

Agenda

bull FIPS 140-2 Security Requirements for Cryptographic Modules

bull Testing Cryptographic Modules bull Maintaining Validation Status bull Additional Information and Links

Cryptographic Module Validation Program (CMVP)

bull Purpose to test and validate cryptographic modules to FIPS 140-1 and FIPS 140-2 and other cryptographic algorithm standards

bull Established by NIST and the Communications Security Establishment (CSE) in 1995

bull Original FIPS 140-1 requirements and updated FIPS 140-2 requirements developed with industry input

bull FIPS 140-3 ndash under development

Applicability of FIPS 140-2 bull US Federal organizations must use validated

cryptographic modules bull GoC departments are recommended by CSE to use

validated cryptographic modules bull International recognition

ndash ISOIEC 19790 Security Requirements for Cryptographic Modules

bull With the passage of the Federal Information Security Management Act of 2002 there is no longer a statutory provision to allow for agencies to waive mandatory Federal Information Processing Standards ndash Also includes enforcement mechanisms

The Importance of Testing Buyer Beware

bull Does the product do what is claimed bull Does it conform to standards bull Was it independently tested bull Is the product secure

Benefits hellip Making a Difference bull Cryptographic Modules Surveyed (during testing)

ndash 488 Security Flaws discovered ndash 963 FIPS Interpretation and Documentation Errors

bull Algorithm Validations (during testing)(DES Triple-DES DSA and SHA-1)

ndash 265 Security Flaws ndash 651 FIPS Interpretation and Documentation Errors

bull Areas of Greatest Difficulty ndash Physical Security ndash Self Tests ndash Random Number Generation ndash Key Management

Using FIPS Validated Cryptographic Modules

bull Cryptographic modules may be embedded in other products ndash Applicable to hardware software and firmware cryptographic

modules ndash Must use the validated version and configuration ndash eg software applications cryptographic toolkits postage metering

devices radio encryption modules bull Does not require the validation of the larger product

ndash Larger product is deemed compliant to requirements of FIPS 140-2

Presenter
Presentation Notes
Can I take this validated module software hardware and firmware and use it in my larger product

CMVP Status

bull Continued record growth in the number of cryptographic modules validated ndash Over gt630 Validations representing over 1000 modules

bull All four security levels of FIPS 140-2 represented on the Validated Modules List

bull Over 150 participating vendors

bull New NVLAP accredited Cryptographic Module Testing Laboratories

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 2: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Agenda

bull FIPS 140-2 Security Requirements for Cryptographic Modules

bull Testing Cryptographic Modules bull Maintaining Validation Status bull Additional Information and Links

Cryptographic Module Validation Program (CMVP)

bull Purpose to test and validate cryptographic modules to FIPS 140-1 and FIPS 140-2 and other cryptographic algorithm standards

bull Established by NIST and the Communications Security Establishment (CSE) in 1995

bull Original FIPS 140-1 requirements and updated FIPS 140-2 requirements developed with industry input

bull FIPS 140-3 ndash under development

Applicability of FIPS 140-2 bull US Federal organizations must use validated

cryptographic modules bull GoC departments are recommended by CSE to use

validated cryptographic modules bull International recognition

ndash ISOIEC 19790 Security Requirements for Cryptographic Modules

bull With the passage of the Federal Information Security Management Act of 2002 there is no longer a statutory provision to allow for agencies to waive mandatory Federal Information Processing Standards ndash Also includes enforcement mechanisms

The Importance of Testing Buyer Beware

bull Does the product do what is claimed bull Does it conform to standards bull Was it independently tested bull Is the product secure

Benefits hellip Making a Difference bull Cryptographic Modules Surveyed (during testing)

ndash 488 Security Flaws discovered ndash 963 FIPS Interpretation and Documentation Errors

bull Algorithm Validations (during testing)(DES Triple-DES DSA and SHA-1)

ndash 265 Security Flaws ndash 651 FIPS Interpretation and Documentation Errors

bull Areas of Greatest Difficulty ndash Physical Security ndash Self Tests ndash Random Number Generation ndash Key Management

Using FIPS Validated Cryptographic Modules

bull Cryptographic modules may be embedded in other products ndash Applicable to hardware software and firmware cryptographic

modules ndash Must use the validated version and configuration ndash eg software applications cryptographic toolkits postage metering

devices radio encryption modules bull Does not require the validation of the larger product

ndash Larger product is deemed compliant to requirements of FIPS 140-2

Presenter
Presentation Notes
Can I take this validated module software hardware and firmware and use it in my larger product

CMVP Status

bull Continued record growth in the number of cryptographic modules validated ndash Over gt630 Validations representing over 1000 modules

bull All four security levels of FIPS 140-2 represented on the Validated Modules List

bull Over 150 participating vendors

bull New NVLAP accredited Cryptographic Module Testing Laboratories

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 3: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Cryptographic Module Validation Program (CMVP)

bull Purpose to test and validate cryptographic modules to FIPS 140-1 and FIPS 140-2 and other cryptographic algorithm standards

bull Established by NIST and the Communications Security Establishment (CSE) in 1995

bull Original FIPS 140-1 requirements and updated FIPS 140-2 requirements developed with industry input

bull FIPS 140-3 ndash under development

Applicability of FIPS 140-2 bull US Federal organizations must use validated

cryptographic modules bull GoC departments are recommended by CSE to use

validated cryptographic modules bull International recognition

ndash ISOIEC 19790 Security Requirements for Cryptographic Modules

bull With the passage of the Federal Information Security Management Act of 2002 there is no longer a statutory provision to allow for agencies to waive mandatory Federal Information Processing Standards ndash Also includes enforcement mechanisms

The Importance of Testing Buyer Beware

bull Does the product do what is claimed bull Does it conform to standards bull Was it independently tested bull Is the product secure

Benefits hellip Making a Difference bull Cryptographic Modules Surveyed (during testing)

ndash 488 Security Flaws discovered ndash 963 FIPS Interpretation and Documentation Errors

bull Algorithm Validations (during testing)(DES Triple-DES DSA and SHA-1)

ndash 265 Security Flaws ndash 651 FIPS Interpretation and Documentation Errors

bull Areas of Greatest Difficulty ndash Physical Security ndash Self Tests ndash Random Number Generation ndash Key Management

Using FIPS Validated Cryptographic Modules

bull Cryptographic modules may be embedded in other products ndash Applicable to hardware software and firmware cryptographic

modules ndash Must use the validated version and configuration ndash eg software applications cryptographic toolkits postage metering

devices radio encryption modules bull Does not require the validation of the larger product

ndash Larger product is deemed compliant to requirements of FIPS 140-2

Presenter
Presentation Notes
Can I take this validated module software hardware and firmware and use it in my larger product

CMVP Status

bull Continued record growth in the number of cryptographic modules validated ndash Over gt630 Validations representing over 1000 modules

bull All four security levels of FIPS 140-2 represented on the Validated Modules List

bull Over 150 participating vendors

bull New NVLAP accredited Cryptographic Module Testing Laboratories

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 4: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Applicability of FIPS 140-2 bull US Federal organizations must use validated

cryptographic modules bull GoC departments are recommended by CSE to use

validated cryptographic modules bull International recognition

ndash ISOIEC 19790 Security Requirements for Cryptographic Modules

bull With the passage of the Federal Information Security Management Act of 2002 there is no longer a statutory provision to allow for agencies to waive mandatory Federal Information Processing Standards ndash Also includes enforcement mechanisms

The Importance of Testing Buyer Beware

bull Does the product do what is claimed bull Does it conform to standards bull Was it independently tested bull Is the product secure

Benefits hellip Making a Difference bull Cryptographic Modules Surveyed (during testing)

ndash 488 Security Flaws discovered ndash 963 FIPS Interpretation and Documentation Errors

bull Algorithm Validations (during testing)(DES Triple-DES DSA and SHA-1)

ndash 265 Security Flaws ndash 651 FIPS Interpretation and Documentation Errors

bull Areas of Greatest Difficulty ndash Physical Security ndash Self Tests ndash Random Number Generation ndash Key Management

Using FIPS Validated Cryptographic Modules

bull Cryptographic modules may be embedded in other products ndash Applicable to hardware software and firmware cryptographic

modules ndash Must use the validated version and configuration ndash eg software applications cryptographic toolkits postage metering

devices radio encryption modules bull Does not require the validation of the larger product

ndash Larger product is deemed compliant to requirements of FIPS 140-2

Presenter
Presentation Notes
Can I take this validated module software hardware and firmware and use it in my larger product

CMVP Status

bull Continued record growth in the number of cryptographic modules validated ndash Over gt630 Validations representing over 1000 modules

bull All four security levels of FIPS 140-2 represented on the Validated Modules List

bull Over 150 participating vendors

bull New NVLAP accredited Cryptographic Module Testing Laboratories

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 5: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

The Importance of Testing Buyer Beware

bull Does the product do what is claimed bull Does it conform to standards bull Was it independently tested bull Is the product secure

Benefits hellip Making a Difference bull Cryptographic Modules Surveyed (during testing)

ndash 488 Security Flaws discovered ndash 963 FIPS Interpretation and Documentation Errors

bull Algorithm Validations (during testing)(DES Triple-DES DSA and SHA-1)

ndash 265 Security Flaws ndash 651 FIPS Interpretation and Documentation Errors

bull Areas of Greatest Difficulty ndash Physical Security ndash Self Tests ndash Random Number Generation ndash Key Management

Using FIPS Validated Cryptographic Modules

bull Cryptographic modules may be embedded in other products ndash Applicable to hardware software and firmware cryptographic

modules ndash Must use the validated version and configuration ndash eg software applications cryptographic toolkits postage metering

devices radio encryption modules bull Does not require the validation of the larger product

ndash Larger product is deemed compliant to requirements of FIPS 140-2

Presenter
Presentation Notes
Can I take this validated module software hardware and firmware and use it in my larger product

CMVP Status

bull Continued record growth in the number of cryptographic modules validated ndash Over gt630 Validations representing over 1000 modules

bull All four security levels of FIPS 140-2 represented on the Validated Modules List

bull Over 150 participating vendors

bull New NVLAP accredited Cryptographic Module Testing Laboratories

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 6: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Benefits hellip Making a Difference bull Cryptographic Modules Surveyed (during testing)

ndash 488 Security Flaws discovered ndash 963 FIPS Interpretation and Documentation Errors

bull Algorithm Validations (during testing)(DES Triple-DES DSA and SHA-1)

ndash 265 Security Flaws ndash 651 FIPS Interpretation and Documentation Errors

bull Areas of Greatest Difficulty ndash Physical Security ndash Self Tests ndash Random Number Generation ndash Key Management

Using FIPS Validated Cryptographic Modules

bull Cryptographic modules may be embedded in other products ndash Applicable to hardware software and firmware cryptographic

modules ndash Must use the validated version and configuration ndash eg software applications cryptographic toolkits postage metering

devices radio encryption modules bull Does not require the validation of the larger product

ndash Larger product is deemed compliant to requirements of FIPS 140-2

Presenter
Presentation Notes
Can I take this validated module software hardware and firmware and use it in my larger product

CMVP Status

bull Continued record growth in the number of cryptographic modules validated ndash Over gt630 Validations representing over 1000 modules

bull All four security levels of FIPS 140-2 represented on the Validated Modules List

bull Over 150 participating vendors

bull New NVLAP accredited Cryptographic Module Testing Laboratories

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 7: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Using FIPS Validated Cryptographic Modules

bull Cryptographic modules may be embedded in other products ndash Applicable to hardware software and firmware cryptographic

modules ndash Must use the validated version and configuration ndash eg software applications cryptographic toolkits postage metering

devices radio encryption modules bull Does not require the validation of the larger product

ndash Larger product is deemed compliant to requirements of FIPS 140-2

Presenter
Presentation Notes
Can I take this validated module software hardware and firmware and use it in my larger product

CMVP Status

bull Continued record growth in the number of cryptographic modules validated ndash Over gt630 Validations representing over 1000 modules

bull All four security levels of FIPS 140-2 represented on the Validated Modules List

bull Over 150 participating vendors

bull New NVLAP accredited Cryptographic Module Testing Laboratories

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 8: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

CMVP Status

bull Continued record growth in the number of cryptographic modules validated ndash Over gt630 Validations representing over 1000 modules

bull All four security levels of FIPS 140-2 represented on the Validated Modules List

bull Over 150 participating vendors

bull New NVLAP accredited Cryptographic Module Testing Laboratories

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 9: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level

(January 31 2006)

0

20

40

60

80

100

120

140

Projected Level 4 Level 3 Level 2 Level 1

1995 1997 1999 2001 2003 2005

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 10: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Participating Vendors(December 31 2005 ndash 157 Total)

3Com Corporation 3e Technologies International Inc 3S Group Incorporated ActivCard ActivCard Inc Atmel Inc and MartSoft Inc Admiral Secure Products Ltd AEP Systems Airespace Inc AirMagnet Inc AKCode LLC Aladdin Knowledge Systems Ltd Alcatel Algorithmic Research Ltd Altarus Corporation Aruba Wireless Networks Inc Atalla Security Products of Hewlett Packard

Corporation Attachmate Corp Axalto Avaya Inc Backbone Securitycom Inc Blue Ridge Networks Bluefire Security Technologies Bluesocket Inc Bodacion Technolgies C4 Technology Inc Carrier Access Corporation and TeamF1 Caymas Systems Inc Certicom Corp Check Point Software Technologies Ltd Chunghwa Telecom Co Ltd

Telecommunications Labs

CipherOptics Inc Cisco Systems Inc Colubris Networks Inc Communications Devices Inc Control Break International Corp Corsec Security Inc Cranite Systems Inc Credant Technologies Corporation Cryptek Inc CTAM Inc CyberGuard Corporation DrsquoCrypt Pte Ltd Dallas Semiconductor Inc Decru Inc Dreifus Associates Limited Inc ECI Systems amp Engineering EF Johnson Co Encotone Ltd Entrasys Networks Entrust Inc Entrust CygnaCom Eracom Technologies Group Eracom

Technologies Australia Pty Ltd F-Secure Corporation Fortinet Inc Fortress Technologies Inc Forum Systems Inc Francotyp-Postalia Funk Software Inc Gemplus Corp Gemplus Corp and ActiveCard Inc

General Dynamics Decision Systems Giesecke amp Devrient Good Technology GTE Internetworking Hasler Inc High Density Devices AS IBMreg Corporation iDirect Technologies IMAG Technologies Inc Information Security Corporation Intel Network Systems Inc IP Dynamics Inc ITServ Inc ITT JP Mobile Inc Juniper Networks Inc Kasten Chase Applied Research L-3 Communication Systems Lipman Electronic Engineering Ltd Litronic Inc Lucent Technologies MA-Com Inc Meganet Corporation Microsoft Corporation Mitsubishi Electric Corporation Motorola Inc Mykotronx Inc National Semiconductor Corp nCipher Corporation Ltd Neopost Neopost Industrie

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 11: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Participating Vendors(December 31 2005 ndash 157 Total)

Neopost Ltd Neopost Online NeoScale Systems Inc Netscape Communications CorpNetScreen Technologies Inc Network Security Technology (NST) Co Nokia Enterprise Mobility SystemsNortel Networks Novell Inc Oberthur Card SystemsOceana Sensor Technologies IncOracle CorporationPalm Solutions GroupPalmSource Inc PC Guardian Technologies IncPGP CorporationPhaos Technology CorporationPitney Bowes IncPointsec Mobile TechnologiesPrism Payment Technologies (Pty) LtdPriva Technologies IncPrivyLink Pte LtdPSI Systems IncReal Time Logic IncRealia Technolgies SLRedCannon SecurityRedCreek Communications ReefEdge IncRELM Wireless CorporationResearch In Motion Rockwell Collins Inc RSA Security IncSafeNet Inc SafeNet Inc and Cavium Networks SchlumbergerSema

Schweitzer Engineering Laboratories IncSecure Systems Limited Security-e-Doc IncSigaba CorporationSimple Access IncSkyTel CorpSnapshield Ltd SonicWall Inc SPYRUS Inc SSH Communications Security Corp Stampscom Standard Networks Inc StoneSoft Corporation Sun Microsystems Inc Symantec Corporation Symbol (Columbitech) Technical Communications Corp Telkonet Communications Inc Thales e-Security TimeStep Corporation Transcrypt International Tricipher Inc Trust Digital LLC Tumbleweed Communications Corp Utimaco Safeware AG Voltage Security Inc V-ONE Corporation Inc Vormetric Inc Wei Dai WinMagic Incorporated WRQ Inc

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 12: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

FIPS 140-2 Security Areas 1 Cryptographic Module Specification

2 Cryptographic Module Ports and Interfaces

3 Roles Services and Authentication

4 Finite State Model

5 Physical Security

6 Operational Environment

7 Cryptographic Key Management

8 EMIEMC requirements

9 Self Tests

10 Design Assurance

11 Mitigation of Other Attacks

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 13: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

FIPS 140-2 Security Levels Security Spectrum

bull Level 1 is the lowest Level 4 most stringent bull Requirements are primarily cumulative by level bull Overall rating is lowest rating in all sections bull Validation is applicable when a module is configured and operated in

accordance with the level to which it was tested and validated

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 14: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Physical Security

bull Single-Chip Cryptographic Module bull Testing

ndash Level 1 Production Grade ndash Level 2 Evidence of Tampering ndash Level 3 Hard Opaque Tamper-Evident Coating

ndash Level 4 Hard Opaque Removal Resistant Coating

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 15: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

CMVP Testing and Validation Flow

Vendor

Designs and Produces

Hardware bull Software bull Firmware

Define Boundary

Define Approved Mode of Operation

Security Policy

CMT Lab

Tests for Conformance

Derived Test Requirements

Algorithm Testing

Documentation Review

Source Code Review

Operational and Physical Testing

CMVP NIST and CSE

Validates

Review Test Results

Ongoing NVLAP Assessment

Issue Certificates

NIST Cost Recovery Fee

User

Specifies and Purchases

Security and Assurance

Applications or products with embedded modules

Presenter
Presentation Notes
Program goal such that even a Level 4 complex module should take lt year and lt $100k to test and validate13Goal is 6-9 weeks for validation by the CMVP

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 16: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Cryptographic Module Specification

bull Define the Cryptographic Module Boundary ndash Integrated Circuit ndash Integrated Circuit Plus Plastic Housing

bull Define Approved Mode of Operation bull Provide Description of the Module

ndash Hardware ndash Software ndash Firmware

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 17: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

FIPS 140-2 boundary defined Any modification as the single chip Includes addition andor deletion of bullHardware a component or part

invalidates the validated bullFirmware module

bullSoftwareApplets

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 18: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

CMVP Testing Process bull CMVP

ndash Conformance testing of cryptographic modules using the Derived Test Requirements (DTR)

ndash Not evaluation of cryptographic modules Not required are bull Vulnerability assessment bull Design analysis etc

bull Laboratories ndash Test submitted cryptographic modules

bull NISTCSE ndash Validate tested cryptographic modules

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 19: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

FIPS140-2 Testing Primary Activities bull Documentation Review

minus (eg Security Policy Finite State Model Key Management Document)

bull Source code Analysis

minus Annotated Source Code

minus Link with Finite State Model

bull Testing

minus Physical Testing

minus FCC EMIEMC conformance

minus Operational Testing

minus Algorithms and RNG Testing

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 20: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Derived Test Requirements

bull Cryptographic module testing is performed using the Derived Test Requirements (DTR)

bull Assertions in the DTR are directly traceable to requirements in FIPS 140-2

bull All FIPS 140-2 requirements are included in the DTR as assertions ndash Provides for one-to-one correspondence between the FIPS and the DTR

bull Each assertion includes requirements levied on the ndash Cryptographic module vendor ndash Tester of the cryptographic module

Presenter
Presentation Notes
The DTR is a separate document from the FIPS 140-2 standard The DTR is an essential document to both the testing lab and as a starting point for the vendor All assertions in the DTR are directly traceable to requirements in FIPS 140-2 The DTR for the FIPS 140-1 standard did not have directly traceable assertions and therefore in some areas there was ambiguity in the requirements The one-to-one correspondence with the FIPS 140-2 DTR will reduce this ambiguity as much as possible 13The DTR will be available 6 months after the FIPS 140-2 standard has been signed However I am in the process of updating and reviewing the document and hope to have it out sooner We will post it on the CMVP web pages as soon as possible

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 21: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Derived Test Requirements

FIPS PUB 140-2

Requirements

DTR Test

Assertions

Vendor Tester Requirements Requirements

Implementation Guidance Document

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 22: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Cryptographic Module Testing (CMT) Laboratories

bull Twelve National Voluntary Laboratory Accreditation Program (NVLAP) shyaccredited testing laboratories ndash True independent 3rd party accredited testing laboratories ndash Cannot test and provide design assistance

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 23: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

CMT Accredited Laboratories

InfoGard

CEAL

COACT

EWA Domus

Atlan

LogicaCMG

BT

BKP

TUumlViT

ICSA

atsec

7th CMT Laboratory added in 2002 8th CMT Laboratory added in 2003 9th CMT Laboratory added in 2004

10th 11th and 12th CMT Laboratories added in 2005

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 24: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Revalidation No Security Relevant Changes

bull FIPS 140-2 An updated version of a previously validated cryptographic module ndash Change to module does not affect FIPS 140-2 security relevant

items ndash Cryptographic Module Testing (CMT) laboratory verifies vendor

claims and submits letter to validation authorities (NIST and CSE) ndash CMVP updates website and no certificate is issued

bull Assumes same CMT laboratory performed the original full testing

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 25: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Revalidation Security Relevant Changes (lt30)

bull Modifications to hardware software firmware affect less than 30 of the operational security relevant requirements

bull The laboratory tests ndash The changed assertions (requirements) ndash All assertions listed in the regression test suite ndash New and updated assertions

bull Revised documentation (eg security policy) also submitted bull Assumes same CMT laboratory performed the original full

testing

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 26: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

Revalidation Security Relevant Changes (gt30)

bull Modifications to hardware software firmware affect greater than 30 of the security relevant assertions ndash The CMT laboratory performs full validation testing

bull Full validation required forhellip ndash Overall security level change ndash Physical embodiment change

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 27: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

NVLAP Accredited FIPS 140-2 CMT Lab

Cryptographic Module Vendor 1

NISTCSE

Issue validation certificate (via lab to the vendor)

CMT Test Report to NISTCSE for validation Module Review Pending

Test for conformance To FIPS 140-2 Writes test report

Vendor selects a lab Submits module for testing Module IUT

Lab submits questions for guidance and clarification

Modulersquos Test Report

NISTCSE issue testing and Implementation Guidance

List of Validated FIPS 140-2 Modules

1a

3 2

5a

5 Finalization NIST adds module to validated modules list at wwwnistgovcmvp

Reviewer Assigned Module Under Review

4 Module Coordination

Cost Recovery Fee Received Prior to Validation

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 28: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

The Cryptographic Algorithm Validation System

bull Designed and developed by NIST bull Supplied to NVLAP accredited testing laboratories bull Provides uniform validation testing for Approved cryptographic

algorithms bull Provides thorough testing of the implementation bull Types of errors found by CAVS range from pointer problems to

incorrect behavior of the algorithm implementation

Presenter
Presentation Notes
The NVLAP accredited testing laboratories validate vendors algorithm implementations using NISTrsquos Cryptographic Algorithm Validation System (CAVS) supplied to them by NIST 1313The CAVS tool designed and developed by NIST provides uniform validation testing for all the Approved cryptographic algorithms1313The validation testing is designed to test all facets of the algorithm to provide greater assurance that it has been implemented correctly1313Since using the CAVS too the laboratories have reported that the majority of the implementations that are tested by the CAVS tool fail the first time As previously stated out of these tests 25 of the failures were caused by implementation flaws such as pointer problems insufficient allocation of space improper error handling andor incorrect behavior of the algorithm implementation 1313The laboratories work with the vendor to correct the implementation before testing it with the CAVS tool again

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 29: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

CAVS Testing Currently provides validation testing for bull Data Encryption Standard (DES) bull Triple Data Encryption Standard (TDES) bull Advanced Encryption Standard (AES) bull Digital Signature Standard (DSS) bull SHA1 SHA224 SHA256 SHA384 SHA512 bull Random Number Generator (RNG) bull RSA Signature Algorithm bull Keyed Hash Message Authentication Code (HMAC) bull Counter with Cipher Block Chaining (CBC) MAC (CCM) bull Elliptic Curve Digital Signature Algorithm (ECDSA)

Presenter
Presentation Notes
The CAVS tool currently provides validation testing for all of these algorithms which include symmetric algorithms asymmetric algorithms hashing algorithms random number generation algorithms and MACing algorithms1313SHOW CAVS DEMO

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 30: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

httpwwwnistgovcmvp

bull FIPS 140-1 and FIPS 140-2 bull Derived Test Requirements (DTR) bull Annexes to FIPS 140-2 bull Implementation Guidance bull Points of Contact bull Laboratory Information bull Validated Modules List bull Special Publication 800-23

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32
Page 31: Cryptographic Module Validation Program - NIST ·  · 2016-11-17Cryptographic Module Validation Program (CMVP) • Purpose: ... certificate (via lab to the vendor) CMT Test Report

NIST

bull Randall J Easter ndash Director CMVP NIST reasternistgov

bull Sharon Keller ndash Director CAVP NIST skellernistgov

CSE bull Jean Campbell ndash Technical Authority CMVP CSE

jeancampbellCSE-CSTGCCA

  • Slide Number 1
  • Agenda
  • Cryptographic Module Validation Program (CMVP)
  • Applicability of FIPS 140-2
  • The Importance of TestingBuyer Beware
  • Benefits hellip Making a Difference
  • Using FIPS Validated Cryptographic Modules
  • CMVP Status
  • FIPS 140-1 and FIPS 140-2 Validation Certificates by Year and Level(January 31 2006)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • Participating Vendors(December 31 2005 ndash 157 Total)
  • FIPS 140-2 Security Areas
  • FIPS 140-2 Security Levels
  • Physical Security
  • CMVP Testing and Validation Flow
  • Cryptographic Module Specification
  • Slide Number 17
  • CMVP Testing Process
  • FIPS140-2 Testing Primary Activities
  • Derived Test Requirements
  • Slide Number 21
  • Cryptographic Module Testing (CMT) Laboratories
  • CMT Accredited Laboratories
  • RevalidationNo Security Relevant Changes
  • Revalidation SecurityRelevant Changes (lt30)
  • Revalidation SecurityRelevant Changes (gt30)
  • Slide Number 27
  • Slide Number 28
  • CAVS Testing
  • httpwwwnistgovcmvp
  • Slide Number 31
  • Slide Number 32

Cryptographic Module Validation Program (CMVP) Presentation · 2018-09-27 · Cryptographic Module Validation Program (CMVP) Randall J. Easter, Director reaster@nist.gov 301.975.4641

Cryptographic Module Validation Program (CMVP) Presentation · 2018-09-27 · Cryptographic Module Validation Program (CMVP) Randall J. Easter, Director [email protected] 301.975.4641

Documents
Module 7: Validating User Input. Overview Overview of User Input Validation Using Validation Controls Page Validation

Module 7: Validating User Input. Overview Overview of User Input Validation Using Validation Controls Page Validation

Documents
FIPS 140-3 Section 5 – Physical Security Randall J. Easter Director, NIST CMVP Ken Lu CSE CMVP

FIPS 140-3 Section 5 – Physical Security Randall J. Easter Director, NIST CMVP Ken Lu CSE CMVP

Documents
Joshua R. New, Ph.D., C.E.M., PMP, CMVP, CSM, IREE

Joshua R. New, Ph.D., C.E.M., PMP, CMVP, CSM, IREE

Documents
Validation and Optimization of Front End Cooling Module for Commercial Vehicle … · 2012-10-09 · Validation and Optimization of Front End Cooling Module for Commercial Vehicle

Validation and Optimization of Front End Cooling Module for Commercial Vehicle … · 2012-10-09 · Validation and Optimization of Front End Cooling Module for Commercial Vehicle

Documents
UI Data Validation Technical Clinic · Module 2: Data Element Validation 11 Data element validation (DEV) assesses the accuracy of data in the validation files by reviewing samples

UI Data Validation Technical Clinic · Module 2: Data Element Validation 11 Data element validation (DEV) assesses the accuracy of data in the validation files by reviewing samples

Documents
The Cryptographic Module Validation Program and FIPS 140-2

The Cryptographic Module Validation Program and FIPS 140-2

Documents
Development and Validation of Tiling Craft Training Module

Development and Validation of Tiling Craft Training Module

Documents
Vortex-Lattice Module with Validation

Vortex-Lattice Module with Validation

Documents
Process Validation Module - WordPress.com€¦ · Process Validation Module Challenge: Miss Wormwood fell and broke her hip and has to have surgery. Due to her age, cigarette smoking

Process Validation Module - WordPress.com€¦ · Process Validation Module Challenge: Miss Wormwood fell and broke her hip and has to have surgery. Due to her age, cigarette smoking

Documents
Leading by Example Philip Gates, CEM, CMVP, EIT Energy Manager 1

Leading by Example Philip Gates, CEM, CMVP, EIT Energy Manager 1

Documents
MODULE #6 COMMISSIONING, VALIDATION, … and manufacturer/vendor subcontractors. ... Identify Required Testing MODULE 6 | COMMISSIONING, VALIDATION AND CERTIFICATIONS Zone Controls

MODULE #6 COMMISSIONING, VALIDATION, … and manufacturer/vendor subcontractors. ... Identify Required Testing MODULE 6 | COMMISSIONING, VALIDATION AND CERTIFICATIONS Zone Controls

Documents
02. input validation module v5

02. input validation module v5

Internet
Draft FIPS-140-3-CMVP Management Manual 09-18-2020

Draft FIPS-140-3-CMVP Management Manual 09-18-2020

Documents
How to Module validation - ofoifa.belgium.be

How to Module validation - ofoifa.belgium.be

Documents
Silverlight Business Apps: Module 3 - Authentication, Validation

Silverlight Business Apps: Module 3 - Authentication, Validation

Documents
CMVP Approved Security Functions

CMVP Approved Security Functions

Documents
Module-E- Libraries1/49 Module E- Standard Libraries Input and Validation Formatted Output Library Functions

Module-E- Libraries1/49 Module E- Standard Libraries Input and Validation Formatted Output Library Functions

Documents
FIPS 140-3 Derived Test Requirements (DTR)NIST Special Publication 800-140 . FIPS 140-3 Derived Test Requirements (DTR): CMVP Validation Authority Updates to ISO/IEC 24759 . Kim Schaffer

FIPS 140-3 Derived Test Requirements (DTR)NIST Special Publication 800-140 . FIPS 140-3 Derived Test Requirements (DTR): CMVP Validation Authority Updates to ISO/IEC 24759 . Kim Schaffer

Documents
FIPS 140-3 Section 5 Physical Security - NIST · FIPS 140-3 Section 5 – Physical Security Randall J. Easter Director, NIST CMVP Ken Lu CSE CMVP September 28, 2005

FIPS 140-3 Section 5 Physical Security - NIST · FIPS 140-3 Section 5 – Physical Security Randall J. Easter Director, NIST CMVP Ken Lu CSE CMVP September 28, 2005

Documents
FIPS 140-2 Cryptographic Module Validation Program

FIPS 140-2 Cryptographic Module Validation Program

Documents
Synchro-Phasor Data Validation and Conditioning Project ... Validation & Conditioning... · 4. Module 4 – Quality Flags: This module utilizes all the flags available in the C37.118

Synchro-Phasor Data Validation and Conditioning Project ... Validation & Conditioning... · 4. Module 4 – Quality Flags: This module utilizes all the flags available in the C37.118

Documents
A Contribution to the Validation of the Electromagnetism Module in

A Contribution to the Validation of the Electromagnetism Module in

Documents
SWMM LID Module Validation Study

SWMM LID Module Validation Study

Documents
Field data requirements for the validation of PV module ...€¦ · Field data requirements for the validation of PV module performance models 4th PV Performance Modelling and Monitoring

Field data requirements for the validation of PV module ...€¦ · Field data requirements for the validation of PV module performance models 4th PV Performance Modelling and Monitoring

Documents
Amazon Linux 2 Kernel Crypto API Cryptographic Module · 2020. 8. 9. · FIPS 140-2 testing lab. The Cryptographic Module Validation Program (CMVP). Customers using or considering

Amazon Linux 2 Kernel Crypto API Cryptographic Module · 2020. 8. 9. · FIPS 140-2 testing lab. The Cryptographic Module Validation Program (CMVP). Customers using or considering

Documents
Cisco Firepower Management Center (FMC) … › groups › STM › cmvp › documents › 140-1 › ...Cisco Firepower Management Center (FMC) Cryptographic Module FIPS 140-2 Non Proprietary

Cisco Firepower Management Center (FMC) … › groups › STM › cmvp › documents › 140-1 › ...Cisco Firepower Management Center (FMC) Cryptographic Module FIPS 140-2 Non Proprietary

Documents
FIPS 140-2 Validation Certificate No. 0019 · FIPS 140-2 Validation Certificate No. 0019 Author: Cryptographic Module Validation Program (NIST and CSEC) Keywords: FIPS 140-2 Validation

FIPS 140-2 Validation Certificate No. 0019 · FIPS 140-2 Validation Certificate No. 0019 Author: Cryptographic Module Validation Program (NIST and CSEC) Keywords: FIPS 140-2 Validation

Documents
Philips Optical Heart Rate Monitoring Module Validation … ·  · 2016-12-30Philips Optical Heart Rate Monitoring Module Validation Study G Valenti, ... Human Biology 4 Population

Philips Optical Heart Rate Monitoring Module Validation … ·  · 2016-12-30Philips Optical Heart Rate Monitoring Module Validation Study G Valenti, ... Human Biology 4 Population

Documents
FIPS 140-2 Validation Certificate No. 1051 - NIST · PDF fileAny deviation from specified verification, ... FIPS 140-2 Validation Certificate No. 1051, FIPS 140-1, FIPS 140-2, CMVP,

FIPS 140-2 Validation Certificate No. 1051 - NIST · PDF fileAny deviation from specified verification, ... FIPS 140-2 Validation Certificate No. 1051, FIPS 140-1, FIPS 140-2, CMVP,

Documents