
Consent-Gated Household LAN Discovery
Passive metadata collection across DHCP, mDNS and Matter with strict privacy filtering rejecting all camera RTSP streams and audio.
Consent-verified household passive LAN discovery, firmware lifecycle tracking, and privacy-first alerts (UK PSTI & ETSI EN 303 645).

Requires verified household ownership and privacy notice acceptance before any passive LAN discovery runs.
Observes DHCP, ARP, mDNS, SSDP and Matter/Thread metadata via optional Linux/OpenWrt gateway or authorised router API.
Matches vendor, model and firmware EOL lifecycle with explicit confidence scores (0.0–1.0).
Unrecognised devices are strictly labelled 'unknown' rather than giving false assurances of security.
Strictly rejects camera RTSP video streams, microphone audio, smart lock PIN codes and plaintext Wi-Fi passwords.
Optional home gateway buffers metadata locally if cloud connectivity drops and verifies Ed25519-signed firmware updates.

Passive metadata collection across DHCP, mDNS and Matter with strict privacy filtering rejecting all camera RTSP streams and audio.

Transparent posture classification where unsupported devices are labelled 'unknown' instead of giving false security.
CSH-RULE-001..004) mapped to MITRE ATT&CK (T1110.001, T1098.003, T1048, T1190) with idempotent dedupe_key ingestion and SHA-256 immutable event hashes.[REDACTED_SECRET], [REDACTED_PII]), explicit per-agent Model Context Protocol (MCP) tool allowlists, and indirect prompt-injection blocking.ENABLE / FORCE ROW LEVEL SECURITY across all 20 tenant tables bound to transaction-local current_tenant_id(); cross-tenant queries fail closed with HTTP 403.isolate_host) and credential revocation require named human step-up approval recorded in an append-only audit trail.DNS TXT or HTTP ownership token required before scanning. Continuous evidence aligned with Krajowy System Cyberbezpieczeństwa (KSC), Dyrektywa NIS2 Polska, RODO.ML-KEM / ML-DSA), and 2035 full PQC completion.FORCE ROW LEVEL SECURITY on all 20 tenant tables.ALTER TABLE security_events ENABLE ROW LEVEL SECURITY; ALTER TABLE security_events FORCE ROW LEVEL SECURITY; CREATE POLICY tenant_isolation_policy ON security_events FOR ALL TO csh_app_role USING (organization_id = current_tenant_id()) WITH CHECK (organization_id = current_tenant_id());
Nie. Detekcja opiera się na regułach deterministycznych, a każda akcja wymaga zatwierdzenia przez człowieka.
Podczas wdrożenia wybierasz rezydencję danych w UE (Frankfurt) lub Wielkiej Brytanii (Londyn).
Tak, CSH Compliance automatycznie przypisuje dowody techniczne do wymagań ISO/IEC 27001, NIS2 i RODO.
Tylko zasoby, których własność została potwierdzona rekordem DNS TXT lub tokenem HTTP.
Tak, oferujemy delegowane zarządzanie klientami i wspólne pule licencji.

30 minut z inżynierem bezpieczeństwa. Bez slajdów.