MCM Platform — Single VM Deployment GuideCopy Anchor Link

Get MCM up and running in under 30 minutes. This guide provides the essential commands, network requirements, and validation steps for deploying the platform on a Single VM.

1. Prerequisites & VM SpecificationsCopy Anchor Link

Ensure your target virtual machine meets the following minimum specifications:

2. Network & Connectivity RequirementsCopy Anchor Link

Deploying the MCM platform on a Single VM requires provisioning the underlying hosting server. The instance should be configured with the operating system and resources specified in Prerequisites & VM Specifications (Ubuntu 24.04 LTS, 8 CPU, 32 GB RAM, 150 GB Disk).

3. Firewall & Security RulesCopy Anchor Link

To secure the single-node deployment, only administrative SSH and web traffic (HTTP/HTTPS) should be allowed inbound. Since the platform utilizes Docker Swarm internally, all cluster management ports (2377, 7946, 4789) must remain blocked from external inbound access to prevent unauthorized cluster probes.

Security Rule RationaleCopy Anchor Link

1. Port 22 (TCP): Used for administrative SSH access to the host.
2. Port 80 (TCP): Used for standard HTTP traffic. Port 80 automatically redirects incoming requests to secure HTTPS (port 443) so users do not experience connection errors if they access the site via http://.
3. Port 443 (TCP): Used for the primary secure application gateway access.
4. Ports 1514 & 1515 (TCP): Used internally by the Wazuh Security Agent for security event monitoring, log collection (port 1514), and agent registration/enrollment (port 1515) with the Wazuh Manager container (Required when the SecOps module is enabled).
5. Port 9098 (TCP): Used by the MCM Upgrade Agent service for automated platform upgrades and version management.

# 1. Set default policies
sudo ufw default deny incoming
sudo ufw default allow outgoing

# 2. Allow SSH, Web traffic, and Upgrade Agent
sudo ufw allow 22/tcp comment "SSH Administrative Access"
sudo ufw allow 80/tcp comment "HTTP Gateway Redirection"
sudo ufw allow 443/tcp comment "HTTPS Ingress Gateway"
sudo ufw allow 9098/tcp comment "MCM Upgrade Agent Service"

# 3. Allow SecOps Wazuh Agent ports (Optional - Required if SecOps module is enabled)
sudo ufw allow 1514/tcp comment "Wazuh Agent Log Collection (SecOps module)"
sudo ufw allow 1515/tcp comment "Wazuh Agent Enrollment (SecOps module)"

# 4. Enable the firewall
sudo ufw enable

Outbound Connection RequirementsCopy Anchor Link

The MCM platform requires outbound HTTPS (port 443) connectivity to the following main domains:

4. Installation ProcedureCopy Anchor Link

Step 1: Account Registration & Portal AccessCopy Anchor Link

Follow these steps on the MCM Nexus Portal to set up your account:

1. Visit MCM Portal Landing Page: Navigate to https://nexus.mcm.revdau.ai and click the Continue button.

   

2. Complete the Sign-Up Form: Fill in your organizational and contact details in the registration form to create your account.

   

3. Receive Verification & Credentials Email: Check your inbox for the welcome email containing your initial credentials and verification details.

   

4. Sign In to MCM Portal: Go to the login screen and sign in using your registered email and temporary password.

   

5. Set Your Account Password: On your first login, configure a secure password for your account.

   

Step 2: License Request & Approval WorkflowCopy Anchor Link

1. Access Portal Workspace Dashboard: After logging in, access your workspace dashboard.

   

2. Navigate to the Request Tab: Click on the Request tab in the top navigation bar.

   

3. Submit License Request & Wait for Approval: Fill out and submit your license entitlement request.

   
   Administrator Approval

   The MCM Administrator team reviews and approves submitted license requests. Once approved, the software package download and license entitlements become accessible under the License tab.

Step 3: Generate Download Command & Server DeploymentCopy Anchor Link

1. Open the License Tab: Navigate to the License tab (/license) to view your MCM App Credentials (Username and Token).

   

2. Select Release Version & Copy Download Command: Under Download installation package, select version 1.2.0 from the dropdown and click Copy to copy the pre-authenticated wget command.

   

3. Connect to the server via SSH:

   Copy Text

   ssh [VM_SSH_USER]@<SERVER_IP>

4. Execute the Copied Download Command:

   Copy Text

   wget --user="your_email@example.com" --password="your_mcm_app_password" \
     "https://nexus.mcm.revdau.ai/api/mcm-app/downloads/package?version=1.2.0" -O mcm_artifacts_1.2.0.tar.gz

5. Extract and Launch the Installer:

   Copy Text

   tar -xzf mcm_artifacts_1.2.0.tar.gz
   cd mcm_artifacts
   sudo chmod +x install.sh
   sudo bash install.sh --single-vm

Installation Details:

• Installation Time: Installation takes 15–30 minutes. Outbound internet access is required on the server during installation to install dependencies.
• Docker Permissions: The installer configures a docker user group and adds the current user to it. To execute Docker commands without sudo post-installation, run newgrp docker in your current terminal session, or log out and log back in.

Step 4: Platform Activation & Super Admin SetupCopy Anchor Link

Once deployment completes, navigate to https://<DOMAIN_OR_IP>/subscription in your browser:

1. Activate Subscription: Enter your registered Username and Password/Token received via email, then click Activate.

   

2. Create Organization Administrator: Enter the details for the primary platform super administrator and submit.

   

3. Log In to Platform: Log in with your administrator credentials and proceed to the Getting Started User Guide.

5. Operations & Health VerificationCopy Anchor Link

You can verify the status and health of all deployed services by executing the healthcheck script (Optional):

sudo bash /opt/mcm/scripts/healthcheck.sh

General Verification and ControlCopy Anchor Link

For verification steps, stack teardown commands, and utility control scripts (starting, stopping, restarting, or upgrading the platform components), please refer to the Helper Scripts and Commands Guide.

For custom domain configuration and SSL/TLS certificate management, please refer to the Domain and TLS Certificate Configuration Guide.

For troubleshooting configuration, certificate, or service initialization errors, refer to the Troubleshooting Guide.