
OpenAPI 3.1 & Idempotent Ingestion Pipeline
Strictly typed REST contracts with client dedupe_key idempotency, RFC 9457 Problem Details and SHA-256 hashed collector tokens.
A versioned REST API with OpenAPI 3.1, scoped keys and signed webhooks.

Strongly typed REST endpoints with machine-readable schemas served at /openapi.yaml.
Collector and API tokens are displayed once on creation and stored exclusively as SHA-256 hashes.
Signed webhook delivery with 300-second replay window enforcement and event-id idempotency.
Every event ingestion call accepts a client dedupe_key so network retries never create duplicate alerts.
Standardized application/problem+json error responses across all authentication and validation boundaries.
Pluggable provider interface supporting deterministic mock testing and live mTLS inference.

Strictly typed REST contracts with client dedupe_key idempotency, RFC 9457 Problem Details and SHA-256 hashed collector tokens.

Delivers real-time alert and approval events with 300-second replay window enforcement across regional data residency boundaries.
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 Agenzia per la Cybersicurezza Nazionale (ACN), Direttiva NIS2 Italia, GDPR.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());
No. Il rilevamento usa regole deterministiche. ARYA SAI produce solo riepiloghi consultivi e ogni contenimento richiede approvazione umana.
Scegliete tra UE (Francoforte) o Regno Unito (Londra) in fase di attivazione.
Sì, CSH Compliance collega automaticamente le prove tecniche ai controlli ISO/IEC 27001:2022, NIS2 e GDPR.
Solo gli asset di cui avete verificato la proprietà tramite DNS TXT o token HTTP.
Sì, con tenant delegati e licenze condivise.

30 minuti con un security engineer. Niente slide.