FortiGate Remote Management via HTTPS from Internet
An administrator needs to configure a FortiGate to allow remote management via HTTPS from the internet. Which configuration step is required?
Quick Answer
The correct configuration step is to enable HTTPS access on the WAN interface and create a firewall policy allowing inbound HTTPS from any to the FortiGate's IP. This two-part requirement exists because enabling HTTPS on the interface only tells the FortiGate to listen for management traffic, but without an explicit firewall policy, the implicit deny rule will still drop all incoming HTTPS packets from the internet. On the Fortinet NSE 4 exam, this question tests your understanding that interface-level service control and firewall policies are independent layers of security; a common trap is assuming that enabling HTTPS on the WAN interface alone is sufficient. Remember the memory tip: “Listen on the interface, allow through the policy”—the interface opens the door, but the policy lets traffic walk through.
⚠ Common exam trap
Test-takers frequently assume enabling HTTPS on the interface alone is sufficient, forgetting that FortiGate still requires an explicit firewall policy to permit inbound traffic to its own IP, as the implicit deny rule blocks all traffic not matched by a policy.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable HTTPS access on the WAN interface and create a firewall policy allowing inbound HTTPS from any to the FortiGate's IP.
Remote HTTPS management of a FortiGate from the internet requires two steps: enabling HTTPS access on the WAN interface (under config system interface) and creating a firewall policy that allows inbound HTTPS traffic (TCP/443) from any source to the FortiGate's own IP address. Without the explicit policy, the traffic is dropped by the implicit deny rule, even if the interface is configured to listen for HTTPS.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a firewall policy from WAN to LAN with HTTPS service and set action to ACCEPT.
Why it's wrong here
Management access is enabled on the interface itself via allowaccess, not through a firewall policy; WAN-to-LAN policies govern transit traffic, not administrative sessions terminating on the FortiGate. It is tempting because firewall policies do control most traffic, and a policy would be required for a separate internal server hosting HTTPS.
- ✗
Enable SSH access on the WAN interface instead of HTTPS.
Why it's wrong here
The stem specifies HTTPS, and SSH is a different protocol on TCP 22, so enabling it does not satisfy the requirement. It is tempting because SSH is also a valid administrative access protocol, and enabling it would be the right step if secure command-line remote management were the actual goal.
- ✓
Enable HTTPS access on the WAN interface and create a firewall policy allowing inbound HTTPS from any to the FortiGate's IP.
Why this is correct
HTTPS management requires two things: administrative access enabled on the WAN interface itself, plus an explicit firewall policy permitting inbound TCP 443 to the FortiGate's IP. Without the policy, the implicit deny drops the traffic even when HTTPS access is enabled.
- ✗
Configure a port forwarding rule to redirect HTTPS from WAN to the internal management IP.
Why it's wrong here
Destination NAT forwards traffic through the FortiGate to a separate internal host; it does not enable HTTPS administration on the FortiGate itself, which terminates on its own interface. It is tempting because VIPs are the standard mechanism for publishing an internal web server to the internet.
Go deeper
Related to this question
About these practice questions
One of 773 original NSE4 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on NSE4
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A FortiGate administrator needs to allow remote management of a FortiGate from the internet. Which administrative access protocols should be enabled on the WAN interface? (Choose the best single answer.)
easy- A.Ping and SNMP
- B.HTTP and Telnet
- C.FTP and TFTP
- ✓ D.HTTPS and SSH
Why D: HTTPS (port 443) and SSH (port 22) are the only secure administrative access protocols that provide encrypted communication for remote management over the internet. HTTP and Telnet transmit credentials and data in plaintext, making them unsuitable for WAN-facing interfaces. FortiGate best practices mandate disabling all insecure protocols on external interfaces and enabling only HTTPS and SSH for administrative access.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This NSE4 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE4 exam.