Jump Host vs Distribution Server
Dinesh
Last Update 2 bulan yang lalu
Overview
SecOps Solution supports Relay Server deployments to enable asset management across segmented networks, restricted environments, branch offices, and geographically distributed infrastructures.
Throughout this guide, the term SecOps Management Platform refers to either the SecOps Cloud Platform (SaaS) or the SecOps Central Server (On-Premises), depending on the deployment model being used.
A Relay Server acts as an intermediary between the SecOps Management Platform and managed assets, allowing organizations to maintain centralized visibility and control while complying with network segmentation and security requirements.
Relay Servers can operate in one of two modes:
- Jump Host Mode
- Distribution Server Mode
Both modes provide connectivity between the SecOps Management Platform and managed assets. However, a Distribution Server extends the capabilities of a Jump Host by additionally maintaining a local patch cache and providing optimized patch distribution capabilities.
Understanding the Difference
Jump Host
A Jump Host acts as a communication bridge between the SecOps Management Platform and assets located within isolated or restricted network segments.
The Jump Host forwards management traffic between the SecOps platform and managed assets but does not maintain a local patch cache.
Typical Activities
- Asset Discovery
- Vulnerability Assessments
- Configuration Audits
- Patch Management Operations where assets can directly access the required patch source
Common Deployment Scenarios
- Segmented VLANs
- Restricted network zones
- Remote data centers
- Isolated server networks
Workflow
The primary purpose of a Jump Host is to provide connectivity where direct communication between the SecOps Management Platform and managed assets is not possible.
Distribution Server
A Distribution Server performs all functions of a Jump Host while additionally maintaining a local cache of patch content.
Managed assets retrieve patch content from the Distribution Server rather than repeatedly downloading the same content across WAN links or external networks.
Typical Activities
- Asset Discovery
- Vulnerability Assessments
- Configuration Audits
- Patch Deployment
- Local Patch Distribution
Common Deployment Scenarios
- Branch offices
- Remote sites
- Large distributed environments
- Low-bandwidth WAN connections
- Internet-restricted environments
- Air-gapped asset networks
- Large-scale patch deployment environments
Workflow
This deployment model improves patch deployment performance while reducing network utilization.
Choosing the Right Deployment Model
Choose a Jump Host When
- Connectivity is the primary requirement.
- You primarily perform vulnerability scanning, compliance monitoring, and configuration audits.
- Managed assets already have access to required patch sources.
- Patch deployment optimization is not required.
Choose a Distribution Server When
- Patch deployment is a primary requirement.
- Managed assets do not have direct internet access.
- Patch content must be distributed from an internal source.
- WAN bandwidth is limited.
- Multiple assets require access to the same patch content.