Deployment Options
Deployment Options
KYRA MDR supports multiple deployment models to fit your organization’s infrastructure and compliance requirements.
Platform Deployment
The KYRA MDR platform is delivered as a fully managed SaaS service. Your organization connects to the platform through:
- Log Collector Agents: Deployed on-premises in your network
- Cloud Sensors: Deployed in your cloud environments (AWS, GCP, Azure, NCP)
- Management Console: Accessed via web browser — no installation required
Collector Agent Deployment
Supported Methods
| Method | Target | Time to Deploy |
|---|---|---|
| Interactive Installer | Individual servers | < 5 minutes |
| Silent Install | Automated deployment | < 2 minutes |
| Configuration Management | Fleet deployment (Ansible, Chef, Puppet) | Varies |
| Container | Container environments | < 5 minutes |
System Requirements
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 2 cores | 4 cores |
| RAM | 256 MB | 512 MB |
| Disk | 1 GB | 10 GB |
| OS | Linux (x86_64, ARM64), Windows Server 2016+ | Linux |
| Network | Outbound HTTPS (port 443) | Dedicated interface |
Installation Steps
- Download the collector binary for your platform from the KYRA MDR console
- Run the installer with your gateway URL and license key
- Configure data sources (syslog, Windows Events, EDR channels, file paths)
- Verify connectivity and data flow in the management console
Cloud Sensor Deployment
Supported Methods
| Method | Target | Time to Deploy | Cloud Support |
|---|---|---|---|
| Single-command installer | Ops engineers | < 5 min | All (auto-detect) |
| Infrastructure-as-Code | Platform teams | < 15 min | AWS, GCP, Azure, NCP |
| Container orchestration | Container operators | < 10 min | All |
| Marketplace image | Enterprise procurement | < 30 min | AWS, GCP, Azure |
Cloud-Specific Setup
AWS: Configure VPC Traffic Mirroring to send traffic to the sensor instance. Requires Nitro-based instances.
GCP: Set up Packet Mirroring with region-scoped configuration pointing to the sensor VM.
Azure: Configure Virtual Network TAP (public preview) to mirror traffic to the sensor.
NCP: Use Packet Mirroring via SFC with VPC Peering to route traffic to the sensor.
Network Requirements
Collector → Platform Communication
| Direction | Protocol | Port | Purpose |
|---|---|---|---|
| Outbound | HTTPS | 443 | Event streaming, management commands |
- No inbound ports required — collectors initiate all connections
- Mutual TLS authentication between collectors and platform
- Supports proxy and PAC file configurations
Management Console
| Direction | Protocol | Port | Purpose |
|---|---|---|---|
| Outbound | HTTPS | 443 | Web console access |
Standard web browser access — no plugins, extensions, or desktop software required.
High Availability
The KYRA MDR platform is designed for high availability:
- Multi-zone deployment with automatic failover
- Zero-downtime platform updates
- Collector agents buffer events during connectivity interruptions
- Automatic reconnection and data replay after network recovery
Data Residency
KYRA MDR supports regional data residency requirements:
| Region | Primary Location |
|---|---|
| Asia Pacific | Seoul (ap-northeast-2) |
| Asia Pacific | Tokyo (ap-northeast-1) |
| North America | Virginia (us-east-1) |
Additional regions available on request for Enterprise customers.