# Testing Laboratories

### NIST Cost Recovery

At the beginning of each fiscal year (FY), NIST CMVP prepares a budget justification for the NIST Cost Recovery fees for the following fiscal year. The NIST Budget office reviews the information and is the approver for the final NIST Cost Recovery fees for the following fiscal year.

• FY17: begins October 1, 2016; ends September 30, 2017.
• FY18: begins October 1, 2017; ends September 30, 2018.

The NIST Cost Recovery fees for FY17 and FY18 are (see Implementation Guidance (IG) G.8 for an explanation of the different scenarios):

 FY17 FY18 CR ECR CR ECR 5SUB Level 1 $6,000$3,000 $6,000$3,000 5SUB Level 2 $8,000$4,000 $8,000$4,000 5SUB Level 3 $11,000$5,000 $8,000$4,000 5SUB Level 4 $15,000$6,000 $8,000$4,000 4SUB - $1,000 -$1,000 3SUB $3,000$1,500 $3,000$1,500 2SUB - $1,000 -$1,000 1A/1B SUB $1,500$1,000 $1,500$1,000 1SUB - $1,000 -$1,000

CR=Cost Recovery: for new module submissions.
ECR=Extended Cost Recovery: for reports that are deficient. Report deficiencies vary in severity; some are due to technicalities, such as incompleteness or missing documentation, while more serious deficiencies are due to security-related nonconformities.

NIST Cost Recovery (CR) is levied on all 1A, 1B, 3 and 5 submissions. IG G.16 allows laboratories the option to request an invoice while they are finalizing the report for submission to CMVP. Once the CR processes begins, changes to the overall security level and submission type will not be accepted. Only unpaid invoices can be cancelled. When the invoice is paid, there are no refunds.

If a report has not been received by 90 days after the invoice request was accepted, the module will be moved to On Hold and removed from the Implementation Under Test (IUT) list. The module can be automatically removed from On Hold and placed on the Modules In Process (MIP) list by sending the report. No additional fees are invoiced to remove the module from On Hold.

NVLAP Inquiries
nvlap@nist.gov

#### Group

Computer Security Division

#### Topics

Security and Privacy: testing & validation

#### Related Projects

Created February 16, 2017, Updated June 22, 2020