# QILAHK assessment example

Version 0.1 • 15 October 2026 • SYNTHETIC EXAMPLE — NOT A CUSTOMER ASSESSMENT

This is a completed illustrative report, not a redacted real engagement. No customer evidence was supplied. All device labels, findings and outcomes below are invented test fixtures. It must be displayed with this disclosure if published. A real redacted report requires an authorized engagement, completed technical review and publication permission.

## Executive decision

Example scope: three fictional Windows workstations, Secure Boot state, TPM readiness, volume-encryption status and evidence freshness only. Evidence observation time: 2026-10-15T12:00:00Z. Review time: 2026-10-15T13:00:00Z. Proposed criteria version: QK-PILOT-0.1, supplied in document 03.

Outcome: NOT ELIGIBLE for a fleet-wide approval. One device passes the example checks, one fails, and one has insufficient evidence. No TrustMark is issued. No claim is made about malware absence, resilience, identity controls, regulatory compliance or overall organizational security.

| Device alias | Secure Boot | TPM | Encryption | Evidence age | Result |
|---|---|---|---|---|---|
| DEMO-001 | Enabled | Ready | Enabled | 1 hour | Meets example criteria |
| DEMO-002 | Disabled | Ready | Enabled | 1 hour | Fails SB-01 |
| DEMO-003 | Unknown | Unknown | Unknown | 48 hours | Insufficient evidence |

Unknown values are not treated as passes. Evidence absence is recorded separately from a confirmed control failure. These are supplied values, not measurements from QILAHK Key.

## Findings and remediation

| Finding | Basis | Impact | Owner role | Action | Closure evidence |
|---|---|---|---|---|---|
| F-01: Boot control disabled on DEMO-002 | E-002.secureBootEnabled=false | Required boot condition not established | Customer endpoint administrator | Confirm hardware compatibility and vendor-supported procedure; validate recovery readiness; schedule change; recollect evidence | Fresh device-bound evidence showing enabled state plus authorized change record |
| F-02: DEMO-003 evidence stale and incomplete | E-003 collected 48 hours before review; required fields absent | Current posture cannot be determined | Customer endpoint administrator | Restore authorized collection and supply missing fields | Complete device-bound evidence within the agreed freshness window |

Priorities: resolve F-01 before relying on that device's boot trust; resolve F-02 before any favorable decision for DEMO-003. Owners, dates, effort and downtime must be agreed in the real engagement. No remote configuration changes are authorized by this example.

## Evidence package

The companion demonstration contains synthetic JSON evidence, SHA-256 manifests, a sandbox credential, signed lifecycle events and a public verification key. Its signatures prove integrity within this sandbox only; they do not prove real device state or QILAHK production issuance.

Evidence references: E-001 (DEMO-001), E-002 (DEMO-002), E-003 (DEMO-003). Collection source: fabricated fixture. Chain of custody: local generation, hash calculation, example review. Reviewer: automated example generation; no human authority approval.

## Reassessment

After remediation, collect a new observation with identity, collection method, collector version and timestamp; preserve the prior evidence; run the same criteria; record the new result and reviewer. Do not silently modify this report. A successful reassessment would change only the explicitly reviewed scope. Fees and included reassessment rounds must be settled in the signed scope.

## Real-report publication procedure

1. Obtain written customer permission and identify intended audience.
2. Copy the completed report and retain an access-controlled original.
3. Remove customer names, hostnames, IP addresses, user identifiers, serial numbers, tenant IDs, secrets and sensitive architecture details; inspect metadata and embedded attachments.
4. Replace identifiers consistently and preserve the meaning of findings.
5. Have a second reviewer check for disclosure and misleading omissions.
6. Publish the authorized redacted version with scope, criteria, observation date, outcome and limitations; preserve its hash and approval record.

Status: example completed; actual customer assessment and redacted publication pending real evidence and permission.