DesertHail MSG — Setup Walkthrough: Installation to First Scan
1. Pre-installation checklist
- System requirements: Ensure server meets CPU, RAM, disk, and OS version (assume a modern Linux distribution; e.g., 64-bit Ubuntu/CentOS).
- Network: Static IP or reserved DHCP, DNS resolving for management and update endpoints, required ports open (SMTP, HTTPS, admin ports).
- Credentials: Admin account for the appliance, SSH key or password, license key or activation token.
- Backups & change window: Snapshot or backup of critical systems and a maintenance window.
2. Obtain software and license
- Download the DesertHail MSG installer or VM image from the vendor portal.
- Retrieve license/activation token and any proxy/update server settings.
3. Deployment options (choose one)
- Virtual Appliance: Import OVA/VMX into VMware, Hyper-V, or KVM.
- Cloud image: Launch vendor-provided AMI/marketplace image in AWS/Azure/GCP.
- Bare metal: Install using ISO on physical hardware.
4. Initial installation steps
- Deploy the image and power on the VM/appliance.
- Complete first-boot configuration: set hostname, timezone, admin password, and network interface (IP, gateway, DNS).
- Apply license/activation in the web console or CLI.
- Update the appliance to the latest available software/definitions.
5. Basic configuration
- Admin access: Configure role-based admin accounts and enable secure access (HTTPS, disable default accounts).
- Certificates: Install an internal CA or public TLS certificate for the web UI and SMTP TLS.
- Time sync: Enable NTP to maintain correct timestamps.
- Logging/monitoring: Point logs to SIEM or syslog server; enable health alerts.
6. Mail flow integration
- Choose deployment mode: inbound only, outbound only, or full mail gateway.
- Update MX records or configure smart host routing so mail flows through DesertHail MSG.
- Configure SMTP listeners and relay destinations (internal mail servers or smart hosts).
- Set connection/relay restrictions and authentication as needed.
7. Policies and scanning
- Default policy: Enable basic malware scanning, spam filtering, and attachment handling.
- Custom rules: Create rules for quarantine, blocklists, allowlists, and content disarm & reconstruction (CDR) if available.
- Data Loss Prevention (DLP): Enable or import DLP templates for sensitive data patterns (SSNs, PCI, PHI).
- Outbound filtering: Apply encryption and DLP on outbound mail.
8. Threat intelligence & updates
- Configure automatic updates for malware definitions, reputation feeds, and engine patches.
- Integrate threat intelligence feeds or the vendor’s managed feed.
9. Test plan — verification checklist
- Send a benign test email through the gateway to confirm delivery and headers.
- Send an EICAR test file attachment to validate malware detection and quarantine.
- Send a sample spam or phishing-like message to test spam scoring and actions.
- Verify TLS connections, certificate validation, and STARTTLS negotiation.
- Confirm logs show events and alerts are generated; check SIEM ingestion.
- Test admin access, role permissions, and failover if HA is configured.
10. First scan: perform and validate
- Initiate a full mailbox or inbound queue scan depending on deployment.
- Monitor CPU, memory, and throughput; adjust scanning concurrency and thresholds.
- Review quarantine, false positives, and policy hits; refine rules to reduce noise.
11. Post-deployment actions
- Schedule regular updates, backups, and test scans.
- Document configuration, policies, and change control.
- Train ops staff on incident response, quarantine handling, and user notifications.
12. Troubleshooting quick tips
- If mail delays occur, check queue depths, DNS, and SMTP relay settings.
- For missed detections, verify definitions are up to date and engines loaded.
- Use logs and packet captures to trace SMTP sessions.
If you want, I can produce a tailored step-by-step installer script, sample SMTP routing configs for Postfix/Exchange, or a checklist formatted for your change window—tell me which one.
Leave a Reply