Method-specific laboratory competence and QMS scope; never treated as a blanket cybersecurity certification.

ACVTS Demo proficiency is developed now; production validation requires the applicable accreditation and access.

Cryptographic-module testing readiness is developed now; official testing depends on the applicable laboratory accreditation.

Non-invasive/side-channel testing requires programme-specific competence and scope.

Entropy-source validation eligibility and third-party restrictions are evaluated per current programme rules.

PIV validation readiness follows current FIPS 201/SP 800-73 programme requirements.

A separate programme/business line from CST accreditation.

Scheme recognition is pursued only under current FIDO laboratory requirements.

Targets are selected from current active payment-device/software programmes.

Laboratory recognition and product categories are scheme-specific.

UK pathway evaluated independently of the NVLAP CST application pause.

Consumer-IoT CyberLAB recognition requires ISO/IEC 17025 accreditation covering the FCC programme scope plus programme recognition.

Official NFC certification test results require an authorized lab, approved test tools and current certification-release controls.

BQTF recognition is facility and test-scope specific and must be renewed under current Bluetooth SIG rules.

Official certification testing uses authorized test houses; target scope is selected from current Alliance programmes.

SESIP governance defines evaluation-laboratory competence and accreditation requirements for IoT platform security evaluation.

Platform/Root-of-Trust evaluation is pursued only under the current approved-laboratory scheme requirements.

Industrial product/security testing and certification use scheme-specific ISO/IEC 17025 and ISO/IEC 17065 structures.