← Index
Wireframe In Progress

Brief / Posture

Round 1 Created 2026-05-23 Section Home Product Ultra v1 (conceptual)
Desktop

Tuesday posture

2026 · 05 · 23 · meridian-prod · 11 devices · 8 zones

Lifecycle
Phase 1 Discover 11 devices · synced 2h
Phase 2 Model 8 zones · 22 policies
Phase 3 Analyze 7 gaps · 2 crit
Phase 4 Implement 3 CRs in flight
Phase 5 Verify 12 verified · 0 failed
Phase 6 Monitor 2 drift events 24h
Compliance posture SOC2 + NIST 800-171
94.2%
141 of 150 controls satisfied · 6 partial · 3 violated
Open gaps 2 critical
7
2 missing · 3 excessive · 1 shadowed · 1 conflicting
CRs in flight 1 awaiting approval
3
1 pending · 1 applying · 1 in verification
Risk score · avg stable 7d
0.34
GNN policy-attention · 11 devices scored
Drift events · 24h 2 new
2
Both auto-remediated · audit trail recorded

What changed since you last visited

8 of 14
42m ago Drift detected · core-fw-01 · rule 142 modified externally monitor · auto · rolled back to baseline SYS
2h ago Discovery re-run · 3 new interfaces on dist-sw-04 discover · ARP + SNMP · zone unassigned SYS
3h ago New gap surfaced · server zone → dmz allows TCP/3306 (MySQL) analyze · gap-241 · risk 0.72 SYS
5h ago CR-184 applied · MFA enforcement extended to admin zone implement · 4 devices · 0 errors G.F
yesterday NIST 800-171 framework refresh · v3.1 published compliance · 4 controls re-evaluated · 1 new gap SYS
yesterday GNN risk model retrained · monthly cadence risk · v4 · avg score 0.34 → 0.36 SYS

Gap queue

7 open · sorted by risk
Crit server → dmz · TCP/3306 allowed missing · gap-241 · 3h old 0.92 →
Crit user → server · TCP/22 (SSH) excessive excessive · gap-232 · 1d 0.84 →
High iot → server · UDP/161 (SNMP) shadowed shadowed · gap-228 · 2d 0.71 →
High vpn → admin · conflicting rules (3 vs 1) conflicting · gap-218 · 3d 0.68 →
Med dmz → wan · excessive egress on port range excessive · gap-204 · 5d 0.51 →
Med admin → vpn · missing inbound ICMP rule missing · gap-188 · 6d 0.42 →
Med user → vpn · orphan rule (no zone match) orphan · gap-174 · 8d 0.38 →

Change requests in flight

3 active · 12 closed last 30d
CR-186 · Close MySQL exposure to DMZ addresses gap-241 · 1 rule add · core-fw-01 Pending risk 0.92 →
CR-185 · Restrict SSH from user to server addresses gap-232 · 1 rule modify · 4 devices Applying risk 0.84 →
CR-184 · MFA enforcement on admin zone addresses gap-221 · pushed 5h ago · verifying Verifying risk 0.61 →
Suggested next action

Gap-241 needs your decision (critical · risk 0.92)

Server zone is allowing inbound MySQL (TCP/3306) from DMZ — direct violation of zero-trust posture. Auto-generated CR-186 is ready for approval; will close the gap in 4 minutes once pushed to core-fw-01.