Fortinet FortiGate Support & Management

Is This the Right Service for Your Business?

• Organizations with locally managed or FortiManager-managed FortiGate appliances
• Businesses experiencing VPN instability, policy drift, subscription confusion, or upgrade risk
• Multi-site teams standardizing branch connectivity, SD-WAN, logging, backup, and support ownership

A useful engagement begins with the environment that exists today. BCT does not assume every listed product is installed, that every system should remain, or that replacing a platform is automatically an improvement. The first objective is to make ownership, dependencies, risk, support, and the next decision clear.

Systems and Platforms in Scope

• FortiGate physical and virtual firewalls.
• FortiOS policy, objects, interfaces, zones, routing, NAT, and VIPs.
• FortiManager and FortiAnalyzer where deployed.
• IPsec VPN, SSL VPN, remote access, and site-to-site connectivity.
• SD-WAN, WAN failover, high availability, subscriptions, firmware, and logging.

The scope can cover one urgent platform, a mixed-vendor environment, a migration, or ongoing co-managed administration. Specialized database, application, security, legal, or compliance work can be coordinated with a qualified specialist while BCT owns the surrounding infrastructure, documentation, change process, and support handoff.

Common Problems This Service Helps Resolve

• Policy and address objects have grown without consistent naming, descriptions, ownership, or review dates.
• VPN, routing, DNS, application access, or branch failover issues recur without a complete dependency map.
• Firmware and signature updates are delayed because compatibility, maintenance, validation, and rollback are unclear.
• FortiManager, local administration, support access, MFA, and emergency access responsibilities are not explicit.
• Configuration backups exist, but restoration and device-replacement procedures have not been proven.

What BCT Can Deliver

• A FortiGate inventory covering model, serial, role, site, firmware, subscriptions, support, administrators, circuits, and dependencies.
• A policy review covering source, destination, service, application, security profile, NAT, logging, owner, and expiration.
• A VPN, SD-WAN, routing, DNS, DHCP, certificate, remote-client, and branch-connectivity review.
• A firmware and lifecycle plan with compatibility checks, maintenance steps, validation, and rollback.
• Verified configuration exports, logging destinations, alert ownership, support contacts, and recovery notes.

How the Engagement Works

1. Discover the Business Impact

BCT identifies the affected users, locations, applications, data, deadlines, support history, recent changes, vendors, and business processes. The scope states what is included, what is excluded, and where a product vendor or specialist may be required. This prevents a broad technology project from hiding the specific result the business needs.

2. Capture a Reliable Current-State Baseline

Before material changes, BCT records relevant configuration, access, versions, licenses, support coverage, subscriptions, monitoring, logs, backups, recovery information, network paths, integrations, and owners. Existing configuration is preserved or exported when the platform supports it. The baseline gives troubleshooting, migration, and rollback a defensible starting point.

3. Separate Immediate Risk From Longer-Term Work

Findings are grouped into urgent exposure or outage risk, reliability work, lifecycle deadlines, access and documentation gaps, cost or licensing decisions, and optional improvements. Leadership can approve the smallest useful next step instead of buying an undefined transformation. Working systems are preserved unless evidence supports a change.

4. Implement With Change Control

Approved work receives a named owner, maintenance plan, communication path, configuration backup or export, representative test cases, rollback criteria, and post-change validation. BCT coordinates internal staff, carriers, software vendors, security providers, developers, and specialists when the issue crosses boundaries.

5. Verify From the User and Business Perspective

Technical health is not enough. BCT verifies the affected application, user workflow, branch, remote user, device, report, communication path, or business process. Documentation is updated, remaining risk is recorded, recurring reviews are scheduled, and the escalation path is made explicit.

Decisions You Should Be Able to Make

• Which policy entries should be removed, narrowed, renamed, or time-limited
• Whether FortiManager or local administration should own the configuration
• Whether firmware, subscription, or hardware work should precede policy cleanup
• How branch and remote-access tests will prove success

Evidence Worth Keeping

Keep the approved inventory, architecture or dependency diagram, administrator and access record, relevant configuration exports, screenshots, logs, test results, backup or recovery evidence, vendor cases, change notes, approvals, validation, renewal dates, and remaining-risk list. Store credentials and secrets only in the approved protected system rather than in general documentation.

Related BCT Services

• Multi-Vendor Firewall Management & Migration — Manage, document, review, and migrate business firewalls across Fortinet, Palo Alto, SonicWall, Sophos, WatchGuard, Barracuda, Cisco, and Juniper.
• Palo Alto Firewall Support & Management — Support PAN-OS, Panorama, GlobalProtect, App-ID, User-ID, VPN, logging, upgrades, backups, high availability, and firewall lifecycle planning.
• SonicWall Firewall Support & Management — Support SonicWall policy, VPN, NAT, licensing, firmware, Capture ATP, logging, backups, failover, branch connectivity, and migration planning.
• Platform & Systems Administration for Business IT — Coordinate cloud, network, security, server, device, productivity, creative, and remote-access platforms through one documented business IT support plan.

Frequently Asked Questions

Can BCT help with a FortiGate that another provider installed?

Yes. BCT begins with a configuration and ownership baseline, confirms access and support boundaries, and avoids material changes until backups, dependencies, test cases, and rollback are understood.

Does BCT require FortiManager?

No. The right management model depends on the number of devices, change volume, internal skill, support responsibility, and consistency requirements. BCT can document either local or centralized administration.

Does mentioning a platform mean BCT is endorsed or certified by that vendor?

No. Product names identify systems BCT can help support. A certification, reseller relationship, endorsement, or formal partnership is stated only when separately verified and current.

What should we bring to the first review?

Bring the platform names, current administrators, known vendors, recent incidents, upcoming renewals or deadlines, and one example of a difficult change. BCT can begin with incomplete information and identify the safest evidence to collect next.

Request a Platform Review

Bring one current problem, renewal, migration question, support gap, or difficult change related to Fortinet FortiGate support. BCT will help define the first bounded review, the evidence needed, the safest next step, and the result that will prove completion.

Start the Platform Review

Product and company names identify systems BCT can support. They do not by themselves claim a customer relationship, endorsement, reseller status, certification, or formal partnership.