FortiWeb (BYOL) Provisioning Workflow on MTN Cloud
Overview
This guide covers the automated deployment of a FortiWeb instance on the MTN Cloud Platform using the Bring Your Own License (BYOL) model. FortiWeb provides comprehensive web application firewall (WAF) and application security capabilities, protecting your web applications from OWASP Top 10 threats and other vulnerabilities.
Why it matters:
- Web Application Security: Protects your web applications from common threats including SQL injection, cross-site scripting (XSS), DDoS attacks, and other OWASP Top 10 vulnerabilities.
- Compliance Support: Helps meet regulatory compliance requirements (PCI-DSS, GDPR, HIPAA) by providing web application security controls and detailed logging.
- Bot Mitigation: Detects and blocks malicious bot traffic while allowing legitimate bots, protecting your applications from automated attacks and scraping.
- Application Delivery: Provides load balancing, SSL/TLS offloading, and caching capabilities to optimize application performance and availability.
- Flexible Licensing: The BYOL model allows you to leverage your existing Fortinet licenses, providing cost flexibility and integration with your existing Fortinet infrastructure.
Prerequisites
Before you begin, ensure you have:
- An active MTN Cloud Console login with appropriate permissions to view Provisioning and Infrastructure tabs.
- A Resource Pool (Project) already created.
- A Network already created.
- A Router already created with the network attached.
- A pre-configured Security Group to manage inbound and outbound traffic.
- A valid FortiAnalyzer license key or a FortiCloud free-trial license for initial activation.
- A planned deployment strategy, including:
- Resource specifications (CPU, RAM, storage).
- Target network for the instance.
- IP addressing requirements.
- Required inter-communication and associated Security Group rules.
- Whether a floating IP is needed.
- Number of devices to be managed.
Tip: If you do not see your networks or Security Groups during provisioning, refresh the portal or contact support.
Important Note: You must include inbound rules in your Security Group for the ports required by FortiWeb (e.g. Port 22 for SSH, Port 443 for the Management GUI, Port 161 for SNMP, and any application ports you wish to protect) to ensure the service is accessible.
Minimum System Requirements
The values below are Fortinet’s official published minimums for FortiWeb-VM (8.0). On MTN Cloud, select a Plan and Volume that meet or exceed these figures. The recommended MTN catalog plan is shown for convenience.
- vCPU: 2 vCPU (minimum).
- Memory (RAM): 8 GB (minimum 8 + GB recommended).
- Disk Storage: 70 GB dedicated disk (minimum).
- MTN Catalog Plan: G2S8 (2 vCPU / 8 GB).
- Interfaces: 1 interface minimum (up to 2 supported on the MTN cloud).
Important Note: Higher traffic volumes and more complex security policies require additional resources. The MTN catalog default root volume is 40 GB — increase to 70 GB+ for production workloads.
Phase 1 — Create Linux/Windows User
Purpose: Configure user credentials that will be used to access the FortiWeb instance via the console.
Navigate to User Settings
Navigate to User Settings by clicking the dropdown beside your name at the top-right corner of the screen.

Configure User Credentials
Locate the Linux Settings section and assign the following:
- Username: Enter a username for Linux access.
- Password: Enter a strong password.
- Confirm Password: Re-enter the password to confirm.
- SSH Key: Optionally, select an existing SSH key pair if you have one configured.
Repeat the same process for your Windows Settings if required. Once all details are entered, scroll to the bottom of the page and click Save.

Phase 2 — Define Security Groups
Purpose: Control network access to (ingress) and from (egress) your FortiWeb instance.
Navigate to Security Groups
Navigation: Infrastructure > Network > Security Groups

Create a Security Group
Click + Add and assign the following details:
- Name: Enter a descriptive name for your Security Group (e.g. fortiweb-sg).
- Description: Provide a brief description of the group’s purpose.
- Scoped Cloud: Select the appropriate cloud (e.g. MTNNG_CLOUD_AZ_1).

Configure Security Group Rules
- Click on the newly created Security Group.
- Navigate to the Rules tab.
- Click + Add Rules and assign the following:
- Name: Enter a descriptive rule name.
- Direction: Select either Ingress (inbound) or Egress (outbound).
- Rule Type: Select Custom Rule.
- Protocol: Choose TCP, UDP, or ICMP.
- Port Range: Specify the port range (e.g. 22 for SSH, 443 for HTTPS).
- Source Type: Define the source (e.g. Network, IP, or Security Group).
- Source: Enter the source IP or CIDR range.
- Destination Type: Define the destination.
- Destination Port Range: Specify the destination port range.
- Scroll down and click Save Changes.
- Navigate to the Location tab, click + Add Location, and select the cloud where the workload will be provisioned.
- Click Save Changes.

Use Case — Restricting Access to Only My Laptop
Scenario: You want only your laptop (with public IP 200.200.113.15) to be able to access your FortiWeb instance. All other devices should be blocked.
Steps:
- Navigate to Infrastructure > Network > Security Groups.
- Click + Add and assign:
- Name: Laptop-Access-Only
- Description: Allow secure remote access only from my laptop
- Scoped Cloud: Select the specific Availability Zone (e.g. MTNNG_CLOUD_AZ_1).
- Select the Laptop-Access-Only group.
- Go to the Rules tab and add the rules described below.
Security Group Rules
Each rule uses Direction: Ingress, Rule Type: Custom Rule, Source Type: Network, Source: 200.200.113.15/32 and Destination Type: Instance.
- Rule 1 — Allow-SSH-From-Laptop: Protocol TCP, Port Range 22, Destination Port Range 22.
- Rule 2 — Allow-GUI-From-Laptop: Protocol TCP, Port Range 443, Destination Port Range 443.
- Rule 3 — Allow-SNMP-From-Laptop: Protocol UDP, Port Range 161, Destination Port Range 161.
- Rule 4 — Allow-ICMP-From-Laptop: Protocol ICMP.

- Click Save Changes.
- Attach the Laptop-Access-Only group to your FortiWeb instance in addition to the default Security Group.
Result: Only your laptop can successfully access the FortiWeb instance on the open ports. All other attempts are denied.
Phase 3 — Provision the FortiWeb Instance (BYOL)
Purpose: Deploy a FortiWeb Web Application Firewall instance with your configured Security Groups and network settings.
Navigate to Catalog
- Navigate to Provisioning > Catalog.

- Search for and click MTN FortiWeb (BYOL).
- Click Order to begin provisioning.

Configure Deployment
Fill in the following details in the order form:
General Configuration:
- Group & Cloud: Select your assigned group and cloud (e.g. MTNNG_CLOUD_AZ_1).
- Name: Provide a unique name for your FortiWeb instance.
- Environment: Select the appropriate environment (e.g. Development, Staging, Production).
- Labels: Optionally, add labels for organizational purposes.
Instance Configuration:
- Resource Pool: Choose the appropriate Resource Pool (Project).
- Plan: Select a plan that meets the minimum CPU/memory requirements (minimum 2 vCPU & 8 GB RAM). Recommended: G2S8 (2 vCPU / 8 GB) or a larger plan based on the number of devices to be managed.
- Volume: Select the required volume capacity. The MTN catalog default root volume is 40 GB — increase to 70 GB+ for production workloads.
- Network(s): Assign your Network.
- Floating IP: Assign a floating IP if required.
- Security Groups: Select both the Default Security Group and the custom Security Group created earlier.

Click Order Now to initiate the deployment. MTN Cloud will provision and display the instance status once deployment is complete.

Access the FortiWeb Management GUI
Once provisioning is complete, you can access the FortiWeb Management GUI:
- Navigate to the Addresses section of the instance details.
- Use the public IP or floating IP assigned to the instance.
- Access the GUI via HTTPS: https://<floating-ip>
Default Credentials:
Username: admin
Password: pAssword@123

Important: It is highly recommended to change the default password immediately upon first login and store the new credentials securely.
Important Tips and Notes
- License Activation: This is a Bring Your Own License (BYOL) instance. On first login, the FortiWeb will prompt for a license. Use a valid FortiWeb license key or a FortiCloud free-trial license to unlock full functionality.
- Web Application Protection: After licensing, configure web protection profiles, security policies, and application firewall rules to protect your web applications. Start with the built-in security policies and customize based on your application requirements.
- Storage Planning: The MTN catalog default root volume is 40 GB. For production workloads, increase to at least 70 GB to accommodate logs, security event data, and system files. Higher traffic volumes require additional storage.
- Naming Conventions: Use consistent names for keys, networks, and instances to simplify management.
- Documentation: Keep a record of IP addresses, credentials, and assigned resources for future reference.
- Security Groups: Regularly review and update rules to follow the principle of least privilege.
- Reusability: You may reuse Security Groups and username/password configurations for subsequent Fortinet deployments based on your security considerations.
- System Requirements: Ensure that the selected Plan meets or exceeds the minimum system requirements. Under-provisioning may result in performance issues, especially during traffic spikes.
- Application Traffic: If you are using FortiWeb to protect web applications, ensure that the appropriate application ports (e.g. 80 for HTTP, 443 for HTTPS) are included in your Security Group rules.
- High Availability: For production environments, consider deploying FortiWeb in an active-passive cluster to ensure application continuity. Contact MTN Cloud Support for assistance with cluster configuration.