FORTINET FC-10-0401E-175-02-DD Firewalls

FC-10-0401E-175-02-DD Subscription Identity

FC-10-0401E-175-02-DD identifies the legacy per-FortiGate FortiGuard Attack Surface Monitoring subscription for an existing FortiGate 401E. 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 401E Evidence

The platform token 0401E maps the entitlement to a storage-equipped mid-range edge. Keep the 401E serial, zone map, HA peer, SSD health, local-log purpose and export destination together. Storage responsibilities must not be copied from the diskless 400E.

Route new IoT discoveries to the operational owner of the affected zone and preserve the associated event trail locally and centrally. Record whether the response was patching, isolation, replacement or accepted risk.

Use the 401E asset register to connect each ASM observation with a concrete interface, VLAN and retained event set. The remediation owner should document why a vulnerable device cannot be updated, what compensating policy limits reachability and when the exception expires. Capture relevant local logs before policy changes, then verify central export and SSD health after the maintenance window. A completed ticket should show the original exposure, the approved response and an independent validation result, not merely a closed alert in the portal.

• Match token 0401E, the exact FortiGate 401E 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 supported-model documentation.