MSP-FAQ: Remote-Access-Governance nach Priority-1-Client-CVE

Governance-Sequel zum ScreenConnect-Pack: Rollen, MFA, Audit, Tenant-Grenzen. Kein GDAP- oder Login≠Isolation-Restamp.

MSP-FAQ: Remote-Access-Governance-Checkliste nach Priority-1-Client-CVE

· RADAR 2026-09-20 18:00 Europe/Rome · Publish = Mensch (Nao).

Hook: Nach einer Priority-1 Remote-Access-/RMM-Client-CVE (siehe Sibling screenconnect-cve-2026-84869-msp-advisory) — welche Governance-Checkliste soll ein MSP über Technikerrollen, MFA, Audit-Logs und Kundentenant-Grenzen fahren?

Governance-Sequel — kein Restamp bereits gestagter GDAP- oder Login≠Isolation-Packs.

# MSP remote-access governance after P1 client CVE (defensive; NO PoC)
1. Patch/reinstall clients to vendor min build; verify fleet strings
2. Role audit: who has TransferFiles / shell / admin on which customers
3. Enforce MFA or SSO on all technician consoles; kill stale sessions
4. Per-customer tenant boundaries: no shared break-glass across estates
5. Audit log retention + alert on anomalous file-transfer / elevation
6. Change window docs + customer notice template ready before next P1
# Distinct from GDAP and login≠isolation FAQs already staged

ScreenConnect-Advisory für Patch-Fakten verlinken; dieses Pack ist Prozess. Soft Lodestar übersprungen (403).

Nur Entwurf.