This occurs when configuration files are altered during transfer. Re-run the audit phase with --preserve-permissions and ensure no antivirus software is intercepting the export directory. Verify file integrity using sha256sum against the manifest.
Platform Migration Guide
Overview
This guide walks you through migrating your existing security infrastructure to the CyberVault platform. Whether you're transitioning from a legacy SIEM, consolidating fragmented tools, or onboarding a new environment, this standardized process ensures zero data loss, minimal downtime, and immediate threat visibility.
Before beginning, ensure your migration window is scheduled outside peak operational hours. CyberVault's automated rollback feature guarantees safe reversion if any anomalies are detected during cutover.
Prerequisites
Complete the following checklist before initiating the migration pipeline. Missing any item may cause validation failures or telemetry gaps.
Root or sudo privileges on all target endpoints
Outbound TLS 1.3 to api.cybevauld.io:443 and agents.cybevauld.io:8443
Active API keys from your current security stack
Valid X.509 certs for mutual TLS authentication
Migration Phases
Generate a complete configuration snapshot from your current environment. CyberVault's migration CLI will parse rules, policies, and asset inventories automatically.
cv-migrate audit --source legacy-siem \
--export-dir ./migration-backup/ \
--format json \
--verbose
Do not modify the exported JSON files manually. The validation engine relies on cryptographic checksums to ensure configuration integrity during import.
Create a dedicated migration workspace in the CyberVault console. This isolates your transition environment from production until validation is complete.
cv-migrate init-workspace \
--name "prod-migration-2025" \
--region us-east-1 \
--tier enterprise \
--auto-scale
Deploy lightweight telemetry agents across your fleet. Agents will run in passive shadow mode first, validating packet capture and event correlation before taking over traffic routing.
# Install agent (Linux/macOS)
curl -fsSL https://agents.cybevauld.io/install.sh | sh
# Configure shadow mode
cv-agent config set mode=shadow \
api-key=YOUR_WORKSPACE_KEY \
buffer-size=4GB \
retention=7d
Run the automated validation suite to compare detection rates, latency, and rule coverage between source and target. Once the score reaches âĨ98%, execute the live cutover.
cv-migrate validate --workspace prod-migration-2025
# If validation passes:
cv-migrate cutover \
--confirm \
--rollback-window 4h \
--notify-on-call
Cutover is approved when all detection rules map correctly, packet loss is <0.1%, and SOC analysts confirm alert fidelity matches baseline benchmarks.
Troubleshooting
Common migration issues and their resolutions. If your scenario isn't listed, contact our migration engineering team via the console or support@cybevauld.io.
Migration CLI returns "Checksum Mismatch" on import
Agents fail to establish TLS handshake
Outbound proxy or strict firewall rules are likely blocking port 8443. Add an allow rule for agents.cybevauld.io and ensure your system clock is synchronized via NTP. TLS 1.3 requires accurate timestamp validation.
Validation score stalls at 94%
Usually indicates unmapped legacy detection rules. Run cv-migrate diff-rules --verbose to identify gaps. Use the auto-mapping feature: cv-migrate auto-map --threshold medium to convert deprecated signatures to CyberVault's threat ontology.
Rollback fails after cutover
Rollback relies on the 4-hour safety window defined during cutover. If expired, trigger manual restoration: cv-migrate restore --snapshot latest --force. Notify your CISO as production routing will temporarily revert to legacy infrastructure.
Need Assistance?
Our Migration Engineering team provides dedicated support for enterprise transitions. Schedule a guided migration session or join our real-time Slack channel for immediate expert assistance.