Publish complete Checkmk spool output before the agent reads it
Review complete-file publication, section boundaries and encoding before letting the agent consume custom spool data.
Read the guideDSE security knowledge hubNetworks & Infrastructure
Networks & Infrastructure
Knowledge
Guidance for resilient networks, Wi-Fi, firewalls, cabling, power, exposure reduction, and connected-device planning.
DSE-authoredOfficial sourcesReviewed guidance
Search the library Explore this topic
Start with the cornerstone guide Networks & Infrastructure knowledge center
Guidance for resilient networks, Wi-Fi, firewalls, cabling, power, exposure reduction, and connected-device planning.
Curated learning path
Open the planning path Plan Cloudflare TLS and origin changes in the right order.
Connect DNS inventory, origin trust, Full (strict), origin authentication, certificate renewal, and HSTS recovery across six source-backed checkpoints.
DSE post stream
1,594 articlesNetworks & Infrastructure
Choose a Checkmk data source program only when replacing agent output
Decide whether a custom collection path replaces or supplements the ordinary Checkmk agent response.
Read the guide
Review every matching Checkmk active-check rule before adding another
Review the complete active-rule set and resulting service population rather than assuming first-match handling.
Read the guide
Apply Checkmk piggyback name translation to the producing host
Review the producer’s translation rule and the exact monitored target name before diagnosing orphaned piggyback data.
Read the guide
Choose the Checkmk metric-backend site before sending OpenTelemetry metrics
Preserve the Checkmk Ultimate 2.5.0 backend’s site and retention limits when planning OpenTelemetry metrics.
Read the guide
Place Kubernetes projected-volume permissions at the right level
Separate a combined projected volume’s default permission setting from deliberate per-item mode overrides before reviewing application access.
Read the guide
Separate aggregation-proxy and ordinary-client CAs in Kubernetes
Review the two Kubernetes client-certificate trust paths before reusing a CA for an aggregation proxy and ordinary API clients.
Read the guide
Check missing custom readiness conditions before changing probes
A Kubernetes custom readiness gate needs its own condition handoff; review the missing-condition case separately from container readiness.
Read the guide
Review kubelet serving CSRs separately from client bootstrap approval
Separate kubelet client credentials from serving-certificate requests, and review node identity and requested names before approving a serving CSR.
Read the guide
Do not classify Kubernetes nodes proxy get permission as read-only
Review what nodes/proxy get authority can reach before relying on API-server admission or audit as the complete control boundary.
Read the guide