mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-21 17:57:22 +00:00
removed the word as meeting
as per the user report #5646 . I removed the following word which written two times as meeting
This commit is contained in:
parent
36bc97a8e2
commit
217842d691
@ -57,7 +57,7 @@ The cadence for starting module validation aligns with the feature updates of Wi
|
||||
|
||||
### What is the difference between “FIPS 140 validated” and “FIPS 140 compliant”?
|
||||
|
||||
“FIPS 140 validated” means that the cryptographic module, or a product that embeds the module, has been validated (“certified”) by the CMVP as meeting as meeting the FIPS 140-2 requirements. “FIPS 140 compliant” is an industry term for IT products that rely on FIPS 140 validated products for cryptographic functionality.
|
||||
“FIPS 140 validated” means that the cryptographic module, or a product that embeds the module, has been validated (“certified”) by the CMVP as meeting the FIPS 140-2 requirements. “FIPS 140 compliant” is an industry term for IT products that rely on FIPS 140 validated products for cryptographic functionality.
|
||||
|
||||
### I need to know if a Windows service or application is FIPS 140-2 validated.
|
||||
|
||||
@ -7191,4 +7191,4 @@ Version 6.3.9600</p></td>
|
||||
|
||||
\[[SP 800-57](http://csrc.nist.gov/publications/pubssps.html#800-57-part1)\] - Recommendation for Key Management – Part 1: General (Revised)
|
||||
|
||||
\[[SP 800-131A](http://csrc.nist.gov/publications/nistpubs/800-131a/sp800-131a.pdf)\] - Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths
|
||||
\[[SP 800-131A](http://csrc.nist.gov/publications/nistpubs/800-131a/sp800-131a.pdf)\] - Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths
|
||||
|
Loading…
x
Reference in New Issue
Block a user