Network Security / NGFW / FTD / Data Center & Branch

FTD 10.0: does the wizard move a Firepower 4100 or 9300 onto the new chassis?

Partner briefing summary of FTD 10.0 — new 220 and 6100 Series appliances, FMC x800, simplified upgrades, Encrypted Visibility Engine, SnortML, Dynamic Firewall identity, and SD-WAN / Zero Trust Access enhancements.

Quick Take

Quick Take: FTD 10.0 lands two new chassis families, a larger management appliance, and a migration wizard that moves Firepower 4100 and 9300 configurations onto current hardware. If a refresh sits in this budget year, the release changes both the shortlist and the upgrade window you can promise the business.

Hardware Innovations: 220 & 6100 Series

Quick Answer: Secure Firewall 220 fills the small-branch NGFW slot (~1.5 Gbps Firewalling+IPS). The 6100 Series targets data-center / high-throughput campus edges with up to ~400 Gbps NGFW, built-in multi-rate Ethernet, clustering up to 16 nodes, and dedicated crypto accelerators — both lines are marked PQC-ready and available with FTD 10.0.

This article distills the APJC Partner Information Webinar briefing on the Cisco Secure Firewall 10.0 release. It covers hardware, upgrade workflow, management UI, identity, threat detection, and SD-WAN / Zero Trust Access changes that matter for refresh, migration, and greenfield NGFW projects.

Use SKU Lookup (Cisco) or request a quote.

Cisco positions a continuous Secure Firewall portfolio from branch through hyperscale data center, with 20+ cloud variants for public/private cloud. Two new hardware families stand out in the 10.0 briefing:

Secure Firewall 220 (Available Now)

  • Single model designed for modern NGFW use cases at the branch edge
  • Network/Security SoC with 4 ARM cores and SoC-embedded encryption / traffic accelerators
  • Up to ~1.5 Gbps NGFW (1024B traffic profiles), ~1 Gbps IPsec VPN, ~0.7 Gbps TLS 1.2/1.3
  • Software: ASA 9.24 and FTD 10.0; PQC-ready silicon

Secure Firewall 6100 Series (Available Now)

  • Two CPUs with 192–256 physical cores (384–512 with hyperthreading)
  • Built-in 12× 1/10/25/50GE (SFP56) and 4× 40/100/200GE (QSFP56), plus two network-module bays
  • 1.5–2.3 TB RAM; two NVMe slots up to 7.2 TB RAID1-protected storage
  • HVAC / HVDC / DC redundant power; advanced FPGAs and one or two dedicated crypto accelerators
  • Clustering on all models, up to 16 nodes
  • Up to ~400 Gbps NGFW; up to ~140 Gbps with ~50% TLS 1.2/1.3 mix; up to ~350 Gbps IPsec
  • Software: ASA 9.24+ and FTD 10.0+; PQC-ready
Series Typical Role Firewalling + IPS IPsec VPN TLS Decryption
200 Series (220) Branch ~1.5 Gbps ~1.2 Gbps ~0.7 Gbps
1200 Series Branch / Campus 6–24 Gbps 5–22 Gbps 1–4.1 Gbps
3100 Series Campus / DC edge 10–45 Gbps 5.5–39.4 Gbps 3.2–11.5 Gbps
4200 Series Data center 71–149 Gbps 51–148 Gbps 20–45 Gbps
6100 Series Hyperscale DC 280–400 Gbps 280–350 Gbps 90–120 Gbps

Figures above are Cisco at-a-glance portfolio ranges from the briefing — validate against the specific PID datasheet and traffic mix for any RFQ.

New Firewall Management Center: FMC x800

Quick Answer: The x800 series succeeds the FMC 4700 as Cisco's flagship management appliance, built on the UCS M8 generation and expected to stay orderable through CY2030 and beyond. It roughly doubles both event retention and event ingest rate, and a single unit now oversees as many as 1,500 Threat Defense devices.

  • Based on UCS M8 server platform
  • Extended lifecycle: expected sellable life through CY2030+
  • ~2× event retention and event rate vs FMC 4700
  • Manage up to 1,500 FTDs (~50% boost over 4700)
  • Available now

Upgrade Hardening: Simple, Swift, Error-Free

Quick Answer: Cisco’s adoption data shows 57% of Threat Defense deployments still run code older than three years — missing features and carrying quality/security risk. FTD 10.0 hardens the upgrade path: fewer than 10 UI clicks from backup through upgrade and deploy, target under one hour for a full environment, with fewer mid-upgrade failures.

Adoption context: About 43% of environments run Threat Defense code 0–2 years old; 22% older than 3 years; 35% older than 4 years. Staying on stale trains blocks new capabilities and increases operational risk.

Upgrade workflow improvements called out in the briefing:

  • Step navigation with filter tabs, selected devices, device details, and explicit upgrade steps
  • Advanced Settings drawer (immediate apply) including Snort upgrade checkbox for 7.3.x–7.6.x upgrades of older Snort 2 devices
  • Single-pane monitoring of device upgrades across the estate

New Firewall Release Numbering

Quick Answer: Read a string like 10.5.5.2 right to left: the trailing digits mark a vulnerability release cut from a maintenance build, the third position marks that maintenance train, and the leading pair identifies the feature minor. Cisco opens each series at x.0, closes it at x.5, and routes the x.5 line into government-certification submission.

Component Example Meaning
Major 10 Release series
Initial minor 10.0 First feature train in the series
Final minor 10.5 Final feature train; submitted for government certification
Maintenance 10.0.2 / 10.5.2 Bug fixes and vulnerability protection on that minor
Vulnerability release 10.5.5.2 VR based on a maintenance release (sustaining path for 10.x customers)

Additional Device Model Migration Support

Quick Answer: FMC 10.0.0’s built-in FTD Model Migration Wizard can move device-specific config from Firepower 1010 / 1100 / 2100 / 4100 / 9300 Series onto Secure Firewall 1200, 3100, or 4200 Series — covering interfaces, inline sets, routing, DHCP, VRFs, and objects.

  • Firepower 4100 source models: 4112, 4115, 4125, 4145
  • Firepower 9300 SM source modules: SM40, SM48, SM56
  • Typical path: any 1100 / 2100 / 4100 / 9300 FTD on 7.3+ → 3100 or 4200 FTD on 7.4.1+
  • Earlier note: Device Model Migration for 4110, 4120, 4140, 4150, SM24, SM36, and SM44 on 7.2.x remains supported with FMC 7.6.1

Platform Additions & Updates

Quick Answer: Beyond the new chassis, release 10.0 widens the 4200 Series order book: a dedicated DC power-supply PID, the FPR4K-XNM-6X1SXF hardware-bypass network module, and multi-instance capacity on the 4225 rising from fifteen to twenty-one instances. Clustering matures too — multiple nodes join in parallel and health checks pick up CCL MTU-related hardening.

  • Secure Firewall 4200: additional PID for DC power supply
  • New hardware-bypass network module: FPR4K-XNM-6X1SXF
  • Multi-instance scale on 4225 increased from 15 → 21
  • Secure Gateway on FTD
  • Parallel joining of multiple cluster nodes
  • Cluster health-check improvements (CCL MTU and related)

FMC UI Simplification & Splunk Syslog

Quick Answer: FMC navigation is reorganized to align with Security Cloud Control — customizable single-column menus, Find-in-Menu, and new top-level areas for Secure Connection and Troubleshooting. A wizard now ships FMC and FTD syslog to Splunk over TCP, UDP, or TLS; profiles bundle destination, event, and certificate settings, stack additively, and apply only to leaf domains.

Navigation renames (high level):

  • Overview → Insights & Reports
  • Analysis → Events & Logs
  • New Secure Connection menu
  • New Troubleshooting menu
  • System moved into left-nav Administration
  • On-Screen Assistance → page-level Help

Splunk integration is configured under Integration → Splunk. Each profile covers Destination, Event, Source, Client certificates, and Summary. Profiles targeting the same devices are additive and limited to leaf domains.

Identity: Dynamic Firewall

Quick Answer: Dynamic Firewall binds an identity source (ISE or pxGrid Cloud) to Cisco Identity Intelligence (CII) trust scores so FMC can act on Questionable and Untrusted users at login time. CII aggregates identity signals (for example Duo or Entra ID) into five trust levels: Trusted, Favorable, Neutral, Questionable, Untrusted.

CII aggregates identity signals (for example Duo or Entra ID) into five trust levels: Trusted, Favorable, Neutral, Questionable, Untrusted. FMC can consume the Untrusted and Questionable levels and apply them to logins received from ISE or pxGrid Cloud — enabling identity-aware enforcement without reinventing trust scoring on the firewall alone.

Threat Updates: EVE, Decryption Policy, SnortML

Quick Answer: Encrypted Visibility Engine moves onto the Access Control Policy page with Monitor vs Protect modes and a two-level High / Very High block threshold. Decryption policy creation focuses on intent (Standard vs Legacy modes; QUIC decryption no longer experimental). SnortML adds HTTP command-injection detection beyond SQL injection.

Encrypted Visibility Engine (EVE)

  • AI/ML detection of apps and malware in encrypted traffic without decrypting
  • New dashboard / widgets; configuration promoted from Advanced Settings to the main Access Control Policy page
  • Monitor vs Protect modes — Protect monitors and blocks based on Block Threshold Level
  • When EVE is enabled, it is used for client application detection (legacy “Use EVE for Application Detection” option removed)
  • Block threshold simplified from five threat-score levels to High and Very High

Simplified Decryption Policy

  • Intent-first policy creation with selective decryption options
  • Enhanced certificate management on the decryption policy page
  • Standard mode (default in 10.0) vs Legacy editor for policies from 7.7 or lower
  • QUIC decryption no longer experimental

SnortML

  • Neural-network exploit detector for Snort 3
  • Introduced in 7.6 for SQL Injection HTTP server attacks; 10.0 adds HTTP command injection, with more coverage planned
  • Under-the-hood performance and latency improvements

SD-WAN & Zero Trust Access Enhancements

Quick Answer: SGT can now ride encrypted across VTI-based site-to-site tunnels (DVTI/SVTI, ESP inline tagging, P2P and hub-and-spoke, ASA and FTD). SD-WAN gains ECMP for DVTI, BFD for VTI, and RFC 9242 / 9370 support; ZTNA gains ACME and IPv6 for clientless access.

Area Enhancement
Identity segmentation Carry SGT across VTI-based S2S tunnels for consistent micro-segmentation branch → DC → cloud
SD-WAN ECMP for DVTI; BFD for VTI; RFC 9242 & 9370 (FTD & ASA)
Remote Access FDM: RA-VPN with smartcard authentication; ACME support in FMC/FTD for RA-VPN
Zero Trust Access ACME for clientless ZTNA; IPv6 support for clientless ZTNA

Frequently Asked Questions

Quick Answer: Secure Firewall 220 and 6100 Series ship now alongside FMC x800, running FTD 10.0 with ASA 9.24 where applicable. Cisco markets the new silicon as post-quantum ready, so validate algorithm support on your target train. Listed 4100 and 9300 configurations migrate to 3100 and 4200 through the FMC wizard.

Yes. The briefing marks both series and the FMC x800 appliance as available now, with FTD 10.0 (and ASA 9.24 / 9.24+ where noted).

Cisco positions the new hardware as ready for post-quantum cryptography transitions — crypto accelerators and platform design intended to support PQC algorithms as standards and software trains mature. Confirm supported algorithms and licensing on the target software release for your RFQ.

Yes for listed models via the FMC 10.0.0 Model Migration Wizard (interfaces, inline sets, routing, DHCP, virtual routers, objects). Older 4110/4120/4140/4150 and selected SM modules on 7.2.x use the FMC 7.6.1 migration path.

Key Takeaway

Key Takeaway: Match the platform to throughput before anything else: Secure Firewall 220 at roughly 1.5 Gbps for branches, 6100 Series near 400 Gbps for the data center edge. Step up to FMC x800 only when the fleet outgrows FMC 4700, and put post-quantum algorithm support in writing on the order. BENQUAN supplies Secure Firewall hardware with competitive pricing.

Not sure your BOM is optimal?

If you are unsure whether your BOM is optimal, click below for a free compatibility and delivery risk assessment. Fast global BOM validation and risk assessment.

Free Compatibility & Delivery Risk Assessment

Or call +852-21349834 · info@benquan.hk

Contents