Frequently Asked Questions

QILAHK is a Cybersecurity Trust Authority built to verify cybersecurity evidence, issue TrustMarks, and publish trusted verification outcomes.

Traditional cybersecurity often focuses on finding weaknesses. QILAHK focuses on proving trust through evidence collection, independent verification, governance, and registry-backed accountability.

QILAHK is pronounced “Key-Lock.” The Key represents evidence collection. The Lock represents verification and trust authority.

A TrustMark is a signed trust credential issued after QILAHK verifies qualifying cybersecurity evidence.

No cybersecurity mark can guarantee immunity from attack. A QILAHK TrustMark confirms that defined evidence and controls were verified under the applicable trust program.

Yes. TrustMarks may be revoked if evidence fails, changes materially, expires, or no longer meets QILAHK trust requirements.

Attestation is the process of collecting and verifying evidence about the state of a device, system, user, application, or organization.

QILAHK may verify Secure Boot, TPM status, disk encryption, patch level, configuration posture, application inventory, supply chain evidence, and security control status.

Evidence may be submitted manually through the member portal or automatically through the QILAHK Key Agent where supported.

The Trust Registry is a public or private record of verification outcomes, TrustMarks, revocations, and trust-chain events.

Registry publication creates transparency, auditability, accountability, and market confidence.

Registry history should not be silently rewritten. Corrections are handled through new trust events, updates, or revocation records.