Module, source code and design
Define boundaries, interfaces, security functions and high-level and detailed design.
Security & cloud
KCMVP validates cryptographic modules protecting non-classified operational information in Korean national and public networks. Using a cryptographic algorithm alone does not make a module validated.
Source record updated:
Discuss your certification →Korean cryptographic module security and implementation validation
Certain public procurement product categories require validated modules. Not every software product must develop and validate its own module; integration of an existing validated module may be possible.
Korean certification schemes and international standards are different. A translated guide does not extend a Korean certificate to other countries. Confirm the target market, product classification and current requirements with the relevant body.
Define boundaries, interfaces, security functions and high-level and detailed design.
Trace development and release configurations to security tests.
Prepare applicable algorithm validation, noise source assessment and test environments.
Distinguish new validation from integration of an existing validated module.
Submit materials, complete laboratory testing and address corrections.
Support result review and maintain the listed validated configuration.
Allow for module readiness, submissions, testing, corrections and national review. Platform or configuration changes may affect revalidation.
Individual testing contract and quotation
Module type, security level, algorithms, platforms and revalidation scope determine cost.
Sources and references ↗Document automation and management cost KRW 300,000 per month. Expert services and certification body testing or assessment fees are separate. Specify supports preparation; the relevant authority or certification body makes the final decision.
Pricing and certification costs →Expert review and consulting are optional, separately scoped services. Choose support for KCMVP Cryptographic Module Validation based on your team's readiness and the evidence or assessment preparation you need.
No. Algorithm implementation differs from satisfying module-level security and testing requirements.
Check validation number, status, hash, security policy, supported OS and validated operating mode.
Check product category requirements and whether an existing validated module can be licensed and integrated.