Governance & Program Info
5G MEC Latency-Critical Inference — Governance
Cross-builder institution context and per-item ownership, due dates, status, and next actions for the governance-relevant checklist items in this builder.
Institution context
Program info
Applies across every builder in the app. Stored locally; nothing leaves the browser.
Checklist governance
Items (0 of 12 marked complete)
Annotate ownership, due date, status, and next action. Items on the left come from the builder's governance / compliance phases.
05 · Governance & Compliance
Align to GSMA NESAS assurance
GSMA Network Equipment Security Assurance Scheme defines the security baseline for telco equipment.
05 · Governance & Compliance
Apply ENISA 5G Toolbox recommendations
EU ENISA 5G security toolbox prescribes supplier diversity, sensitive-asset controls, and architectural hardening.
05 · Governance & Compliance
Align to NIST SP 800-53 / SP 800-207 (Zero Trust)
Federal tenant workloads (FirstNet, federal agencies) require 800-53 controls and a Zero Trust architecture.
05 · Governance & Compliance
SOC 2 Type II for the inference plane
Enterprise tenants will request SOC 2 Type II on the operator-managed inference tier. Scope the audit to include the inference plane.
05 · Governance & Compliance
Confirm FCC Part 15 / Part 90 / Part 96 compliance per site
MEC inference is hosted on site gear — the site must be in compliance for the hosting operator to transmit.
05 · Governance & Compliance
SAS registration for CBRS sites hosting inference
Every CBRS-hosted enterprise site must be SAS-registered with PAL/GAA tier and frequency coordination current.
05 · Governance & Compliance
FirstNet / public-safety pre-emption handling
Sites hosting FirstNet Band 14 tenants are subject to public-safety pre-emption. Confirm the inference plane honors it.
05 · Governance & Compliance
Per-tenant data-handling agreement
Contractually specify what the operator may and may not do with inference payloads — no training reuse without consent.
05 · Governance & Compliance
Tenant-scoped audit log with immutability
Each tenant must be able to audit their own inference calls without seeing other tenants' data.
05 · Governance & Compliance
Model provenance and signing
Every deployed model artifact has a signed provenance chain — source, training lineage, tenant approver, deployment window.
05 · Governance & Compliance
Board / executive SLA and revenue reporting
Inference-tier revenue, SLA compliance, and incident rate roll up into the MEC P&L and executive dashboards.
05 · Governance & Compliance
Incident response playbook for inference-plane failures
SLA-impacting inference failures are revenue incidents — document detection, escalation, communication, and credit triggers.