Product and configuration specification
Align names, versions, hardware, configuration and hashes.
Security & cloud
This procedure tests implemented security functions and issues a verification document. The delivered product's name, version and hardware must match the verified configuration.
Source record updated:
Discuss your certification →Korean public procurement security function testing and verification
Korean public procurement routes can include security function verification, CC or other security conformity checks depending on product type. This is not a blanket requirement for all software.
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.
Align names, versions, hardware, configuration and hashes.
Map implemented functions to applicable national or testing criteria.
Provide reproducible configuration, operation and administration instructions.
Check current procurement requirements and laboratory acceptance.
Compare documented security functions with the real product.
Complete verification and manage delivery versions and subsequent changes.
Readiness, testing queues and defect correction determine timing. Check validity conditions for the relevant route under the 2026-05-01 guidance.
Individual laboratory quotation
Pricing depends on product type, test scope and corrective work.
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 Security Function Verification based on your team's readiness and the evidence or assessment preparation you need.
The actual product must match the verified name, version and hardware requirements.
Also check category-specific rules, operating environments and contract requirements.
Different product types may follow different procurement routes. Confirm the currently required route first.