On-Premise Deployment Prerequisites & System Requirements
Hardware Requirements
The SecOps On-Prem solution requires specific hardware configurations to ensure optimal performance and reliability. Below are the recommended hardware specifications for the SecOps Central Server and the assets to be managed.
SecOps Central Server
The SecOps Central Server acts as the core platform for managing all vulnerability management and patching operations across the infrastructure.
Customers need to provision a clean Ubuntu Server 24.04 LTS virtual machine in their environment. Customer can download the Ubuntu Server 24.04 ISO from the official link. Once the VM is ready, the SecOps team will handle the complete installation and configuration.
This approach ensures flexibility across different virtualization platforms and typically takes 10–15 minutes to complete.
Recommended Hardware Specifications:
Customers need to provision a clean Ubuntu Server 24.04 LTS virtual machine in their environment. Customer can download the Ubuntu Server 24.04 ISO from the official link. Once the VM is ready, the SecOps team will handle the complete installation and configuration.
This approach ensures flexibility across different virtualization platforms and typically takes 10–15 minutes to complete.
Recommended Hardware Specifications:
- CPU: 4 vCPUs (2.4 GHz or higher)
- RAM: 8 GB
- Disk Space: Minimum 200 GB (SSD strongly recommended for optimal performance)
Disk Partitioning Note
A total of 200 GB storage is required for the SecOps Central Server. It is recommended to assign the entire 200 GB to the root (/) partition for a simpler setup and smoother maintenance.
If your environment uses separate partitions (like /var or /home), make sure to provide sufficient space based on usage:
If your environment uses separate partitions (like /var or /home), make sure to provide sufficient space based on usage:
- /var - around 120 GB (for logs and temporary files)
- /home - around 80 GB (for user data)
Ubuntu Server Configuration
Before starting the SecOps installation, configure the Ubuntu Server as follows:
Operating System: Ubuntu Server 24.04 LTS (clean installation)
Create a Primary User Account
- Run - sudo adduser ubuntu
- When prompted:
- Password: Secops@2024
- Full Name: SecOps Solution
- Leave other fields blank and press Enter.
- Confirm by typing y when asked “Is the information correct?”.
- Grant admin privileges: sudo usermod -aG sudo ubuntu
- Verify sudo access: su - ubuntu then sudo -v
- Update the system to confirm connectivity: sudo apt update and sudo apt upgrade -y
After completing these steps, the Ubuntu Server will be ready for the SecOps installation.
Network Connectivity
Port & Protocol Configuration
- Inbound Ports (within local network):
- 49430, 49431, 58080, 58443, 5679, 5680
- Static IP – The Central Server must have a static IP to ensure consistent access within the network.
Internet Access Requirements (SecOps Central server)
- Initial Setup
- If your environment restricts outbound internet access, the following Master Whitelist Domains must be allowed only during the initial installation and configuration of the SecOps On-Premises solution.
- If unrestricted internet is available during setup, manual whitelisting is not required.
- Proxy Configuration Considerations: If your environment uses a custom proxy for outbound internet access, please ensure that system-wide proxy settings are properly configured and applied to all network services. This ensures that the SecOps services and internal components can reliably access the required domains and URLs mentioned in this document. Improper or partial proxy configuration may cause connectivity or update failures during installation or runtime.
- Domains (HTTPS – Port 443):
- api.app.secopsolution.com
- *.archive.ubuntu.com
- security.ubuntu.com
- apt.postgresql.org
- dl.min.io
- download.docker.com
- github.com
- objects.githubusercontent.com
- dl.google.com
- api.app.secopsolution.com
- esm.ubuntu.com
- release-assets.githubusercontent.com/
- optimizationguide-pa.googleapis.com/
- connectivity-check.ubuntu.com/
- storage.googleapis.com
- Post-Installation
- After the initial setup is complete, the SecOps On-Premises solution does not include any built-in VPN adapter or background connection to external networks for updates.
- To keep vulnerability definitions, patch metadata, and product updates current, customers can choose one of the following approaches:
- Scheduled Internet Access - Permit outbound internet access from the SecOps Central Server at specific intervals (e.g., weekly or monthly) to allow updates.
- Permanent Whitelisting - Whitelist api.app.secopsolution.com (port 443) for ongoing updates.
- For environments using Patch Management, additional patching domains must be whitelisted mentioned in this doc. Note: If Patch Management is not in use, only api.app.secopsolution.com (port 443) is required after installation.
Bandwidth and Network Performance
- Internet Bandwidth to Central Server
- The SecOps Central Server, deployed on-premises, requires stable outbound internet connectivity to periodically fetch vulnerability definitions, product updates, and patch metadata from the SecOps SaaS platform.
| Bandwidth Tier | Recommended Bandwidth | Description |
| Minimum (All environments) | 5 - 10 Mbps | Supports regular syncs and patch downloads, even in enterprise setups |
| Recommended | 20 - 50 Mbps | Faster syncs for larger patch sets and environments with frequent updates |
- Endpoint Connectivity
Each managed endpoint must maintain reliable connectivity to the SecOps Central Server delivering patches and scan instructions.
- Recommended Bandwidth (per Endpoint): 10 Mbps (minimum)
- Stable network connectivity is required to ensure reliable patching and scanning operations. This is especially critical in low-bandwidth environments, where there is minimal tolerance for delays, retries, or communication interruptions
- Endpoints should not enter idle or sleep states during scheduled scans or patch deployments, as this may interrupt communication and cause job failures.
- Ensure that endpoint power management settings (especially on Windows devices) are configured to allow background activity during deployment windows.
Next Steps
Once all prerequisites have been completed, validate the environment by following the On-Prem Setup Validation Guide.
This validation process helps ensure that:
- Hardware requirements are met
- Network connectivity is configured correctly
- Required ports are accessible
- DNS resolution is functioning properly
- Internet connectivity requirements are satisfied
- The environment is ready for deployment
After successfully completing the validation steps and confirming that all prerequisite checks pass, please contact the SecOps Solution Support team.
Our team will review the environment and assist you with the remaining On-Prem deployment and configuration process.
📧 support@secopsolution.com
Note: Completing the prerequisite validation before scheduling the deployment helps ensure a faster and smoother implementation experience.