FORTINET FC-10-00306-175-02-DD Firewalls

FC-10-00306-175-02-DD Procurement Check

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

Authorized Term Evidence

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.

• Match token 00306, the exact FortiGate 300E 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.

Attack Surface Monitoring

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.

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.

Platform Operations

The platform token 00306 maps the entitlement to a diskless mid-range boundary. Map the 300E protected zones, sixteen copper and sixteen SFP positions, HA role, central log destination and serial. Keep its record separate from the storage-equipped 301E sibling.

Correlate IoT discoveries with the exact zone and switch path, then assign vulnerability findings to the owner who can isolate or patch the device. Preserve central evidence because this model does not provide the 301E storage workflow.

For the 300E, use zone ownership as the primary triage key. Reconcile each detected endpoint with DHCP, switch-port and asset-management records, then test whether the central collector retains the event before remediation begins. The closure package should include the affected zone, policy change, owner approval and evidence that the device stopped presenting the reported exposure. If no owner can be found, move the endpoint into a restricted segment under a documented change rather than suppressing the finding. This process fits a diskless boundary where external systems carry the audit trail.

Official sources: Fortinet Secure SD-WAN Ordering Guide; Fortinet 300E and 301E fast-path architecture.