HK Enterprise · GRP
Global Release Payload Screening
This verifier executes every required screening domain against the live deployed package. Deployment identity is obtained directly from Cloudflare through the server-side verifier; there are no manual Deployment ID or Deployment URL entry fields.
Current global screening manual: Manual Draft Three (HTML) · PDF copy
Deployment Identity
Only the three policy-approved identity values appear here.
| Identity Value | Verified Value |
|---|---|
| Build ID | HK-ENTERPRISE-V4.2.0-20260827 |
| Cloudflare Deployment ID | Not verified |
| Cloudflare Deployment URL | Not verified |
Screening Run
Manual launch, automated testing, manual review.
Ready. No screening has been run in this browser session.
Screening Domains
| Layer | Status | Evidence |
|---|---|---|
| 1. Primary Integrity Screening | NOT RUN | — |
| 2. Runtime Assurance Screening | NOT RUN | — |
| 3. Deployment Identity Screening | NOT RUN | — |
Runtime Screening Detail
Tests operate the real deployed controls inside same-origin frames.
No screening records have run.
Server-side identity verifier setup
Automatic identity screening requires a Cloudflare Pages Read API token stored as an encrypted project secret. Required runtime values:
Automatic identity screening requires a Cloudflare Pages Read API token stored as an encrypted project secret. Required runtime values:
CF_ACCOUNT_ID and encrypted CF_PAGES_READ_TOKEN. Optional CF_PAGES_PROJECT_NAME overrides the default hk-enterprise.
The token is never included in the browser package or screening receipt.