Scribd
Upload
21 views10 pages

FortiGate Migration Professional Presentation v2

Uploaded by

sudarshanks

Copyright:

© All Rights Reserved
Download as PPTX, PDF, TXT or read online from Scribd
Download as pptx, pdf, or txt

FortiGate Migration Professional Presentation v2

Uploaded by

sudarshanks
21 views10 pages

Copyright

© © All Rights Reserved

Available Formats

PPTX, PDF, TXT or read online from Scribd

Did you find this document useful?

Is this content inappropriate?

Copyright:

© All Rights Reserved
Download as PPTX, PDF, TXT or read online from Scribd
Download as pptx, pdf, or txt
21 views10 pages

FortiGate Migration Professional Presentation v2

Uploaded by

sudarshanks

Copyright:

© All Rights Reserved
Download as PPTX, PDF, TXT or read online from Scribd
Download as pptx, pdf, or txt
You are on page 1/ 10

FortiGate Migration and Core

Integration Plan
Prepared for: [Client Name]
By: [Your Company]
Date: [Insert Date]
Agenda
• 1. Introduction
• 2. Project Overview
• 3. Approximate Man-Days Required
• 4. FortiGate Migration Plan
• 5. Proxy and SSL VPN Planning
• 6. Core FortiGate Addition
• 7. Risk Analysis
• 8. Recommendations for Success
• 9. Q&A
Project Overview
• • Existing Infrastructure:
• - Cisco ASA Perimeter Firewall
• - VPN Concentrator for SSL VPN
• - MPLS links for branch connectivity
• - Nexus Switches in VPC architecture

• • Final Objective:
• - Migrate Cisco Firewall to FortiGate 2600F
with UTM functionality.
Approximate Man-Days Required
• Preparation Phase:
- Network Assessment: 5 days
- Hardware Procurement & Setup: 3 days
• Implementation Phase:
- FortiGate 2600F Migration: 7 days
- FortiGate 3000F Core Addition: 5 days
- Proxy and SSL VPN Configuration: 4 days
• Testing and Validation:
- High-Level Functional Testing: 3 days
- User Acceptance Testing: 3 days

• Total Estimated Man-Days: 30–35 days


FortiGate Migration Plan
• • Assessment:
• - Identify critical services and dependencies
on Cisco ASA.
• - Backup current configurations.
• • Migration Approach:
• - Configure FortiGate in a parallel mode
initially.
• - Test network segments before full cutover.
• - Conduct phased migration by
Proxy and SSL VPN Planning
• • Proxy Planning:
• - Configure explicit proxy on FortiGate for
web filtering.
• - Ensure integration with existing
authentication systems.
• • SSL VPN Planning:
• - Set up a secure SSL VPN gateway on
FortiGate.
• - Configure user-based and device-based
access controls.
Core FortiGate Addition
• • Approach:
• - Deploy FortiGate 3000F in HA (High
Availability) mode.
• - Connect to Nexus switches for server farm
protection.
• • Recommendations:
• - Enable Advanced Threat Protection features
(sandboxing, IPS).
• - Ensure segmentation for critical
applications.
Risk Analysis
• • Potential Risks:
• - Network downtime during migration.
• - Compatibility issues with legacy systems.
• - Misconfigured security policies leading to
vulnerabilities.
• • Mitigation Strategies:
• - Conduct detailed pre-migration tests.
• - Plan rollback strategies in case of critical
failures.
Recommendations for Success
• 1. Engage stakeholders early to align project
goals.
• 2. Use FortiCare support for troubleshooting
during migration.
• 3. Provide training sessions for the client's IT
team.
• 4. Conduct regular post-implementation
audits to refine configurations.
Q&A
• Open floor for questions and discussions.

You might also like