Skip to content

πŸ”—

DSX-Connect

Any file. Anywhere.

DSX-Connect is a modular, event-driven orchestration framework that extends Deep Instinct’s DSX for Applications to protect files across cloud, SaaS, and on-prem repositories.

It standardizes how files are discovered, scanned, and remediated β€” enabling deep-learning malware prevention against zero-day and AI-generated threats wherever data resides.

DSX-Connect Architecture


What DSX-Connect Provides

  • A reusable, event-driven scanning core built for predictable scale
  • Pluggable connectors for cloud storage, SaaS platforms, and filesystems
  • Support for on-demand and event-driven scanning workflows
  • Fault-tolerant execution with durable queues and retry handling
  • Portable deployment via Docker Compose or Kubernetes (Helm)
  • Seamless integration with DSX for Applications’ deep-learning malware detection

Whether protecting cloud buckets, enterprise SaaS data, or on-prem filesystems, DSX-Connect enables consistent malware prevention β€” any file, anywhere.

Who This Is ForπŸ”—

This documentation is intended for:

  • Security engineers deploying file scanning across repositories
  • Platform engineers operating DSX-Connect at scale
  • DevOps teams integrating DSX-Connect into CI/CD or cloud workflows
  • Architects evaluating deployment models

About the DocumentationπŸ”—

The DSX-Connect documentation is organized by role and lifecycle stage.

If you are new to DSX-Connect:

  • Start with Getting Started for a quick deployment.
  • Review Core Concepts to understand architecture, connectors, and performance.

If you are deploying:

  • Use Deployment for Docker Compose or Kubernetes (Helm).
  • See Choosing Your Deployment to understand the trade-offs.

If you are operating at scale:

  • Use Operations for performance tuning, logging, monitoring, and upgrades.
  • Refer to Scaling & Performance (Kubernetes) for infrastructure-level scaling.

If you need configuration details:

  • Use Reference for environment variables, Helm values, and API definitions.

This structure separates:

  • System concepts
  • Deployment mechanics
  • Operational procedures
  • Reference material

So you can quickly find what you need.


πŸš€ Getting StartedπŸ”—

🧠 Core ConceptsπŸ”—

βš™οΈ DeploymentπŸ”—

πŸ”§ OperationsπŸ”—

πŸ‘©β€πŸ’» Developer's GuideπŸ”—

πŸ“š ReferenceπŸ”—

πŸ“¦ ReleasesπŸ”—