FORTINET FC-10-F6H0E-175-02-DD FortiGate 600E Attack Surface Monitoring Subscription

FC-10-F6H0E-175-02-DD Subscription Identity

FC-10-F6H0E-175-02-DD identifies the legacy per-FortiGate FortiGuard Attack Surface Monitoring subscription for an existing FortiGate 600E. It is an electronic security service; no firewall appliance, support contract or replacement hardware is included.

Service Capabilities

Fortinet describes service code 175 as providing IoT detection, IoT vulnerability correlation and Security Rating updates. Those results support inventory and exposure governance; they do not patch a discovered device, guarantee complete asset discovery or replace the team responsible for remediation.

Current Procurement Status

Fortinet's current Secure SD-WAN Ordering Guide states that the older individual Attack Surface SKU is no longer available a la carte as of January 2026 and is now delivered through the applicable SD-WAN Service Bundle. Treat this page as an exact legacy-entitlement and renewal-reference record. Confirm current eligibility and replacement path in an authorized quote before ordering.

The suffix DD does not establish a duration on this page. Preserve the authorized start and end dates, co-termination terms, registration region and current entitlement status from the quote.

FortiGate 600E Evidence

The platform token F6H0E maps the entitlement to a diskless high-capacity edge. Capture the 600E HA topology, monitored segments, management route, external evidence repository and serial. The official series table distinguishes this diskless model from 601E.

Use the external monitoring timeline to validate when an IoT device appeared and which high-capacity path observed it. Remediation closure should prove owner assignment, segmentation or patch action and resumed off-box visibility.

The 600E review depends on surrounding telemetry. Start by verifying central log continuity, flow visibility and management access for every monitored high-capacity handoff. Rank unknown devices by reachable services and business path, then have the network owner approve isolation rules and rollback criteria. After a change, prove that HA stayed stable, expected traffic recovered and the off-box collector received fresh evidence. Do not add storage-health or failed-media steps copied from 601E; the diskless model needs a complete external evidence chain instead.

• Match token F6H0E, the exact FortiGate 600E serial and the FortiCare account.
• Confirm monitored networks, IoT inventory ownership and alert recipients.
• Record vulnerability disposition, due date and validation evidence for each actionable finding.
• Use an authorized quote to confirm the current SD-WAN bundle or legacy-renewal path.

Official sources: Fortinet Secure SD-WAN Ordering Guide; Fortinet 600E Series Data Sheet.