FORTINET FC-10-00307-188-02-DD FortiGate 301E FortiAnalyzer Cloud Base

FC-10-00307-188-02-DD Service Identity

FC-10-00307-188-02-DD is a historical FortiAnalyzer Cloud Base subscription for one existing FortiGate 301E. It provides cloud-based event and security-log management with IOC-oriented analysis; it does not include a FortiGate appliance, replacement hardware, a managed SOC or unrestricted log capacity.

Base Subscription Boundary

Fortinet documentation describes the base cloud service as a monitoring and alerting tier for event logs, security logs and IOC scans. Supported log classes and integrations vary by FortiAnalyzer Cloud and FortiOS release, so traffic-log ingestion, retention and reporting must be confirmed for the exact tenant before ordering or renewal.

Service code 188 belongs to a historical per-device ordering pattern. Confirm current orderability and the Fortinet-approved successor for the registered serial; do not treat a current FortiAnalyzer Cloud code as an automatic commercial replacement.

FortiGate 301E Acceptance

For the 301E, reconcile local logging and FortiAnalyzer Cloud instead of assuming that one automatically replaces the other. Generate a known security event, compare its local timestamp with cloud receipt, and retrieve it through the reporting workflow. Document which store is authoritative during a WAN outage and how gaps are reviewed after connectivity returns.

A 301E validation should start with an incident timeline that intentionally crosses both local and cloud records. Create an approved administrator login event, a policy change and a reversible test alert. Locate all three locally, locate them again in the cloud and note any differences in timestamp, field names or retention. Disconnect the upload path long enough to create a visible queue, then restore it and confirm whether events arrive in their original order. The purchasing record must say when investigators use local evidence, when they use cloud analytics and who resolves a mismatch. Test a report that covers the interruption and retain its query parameters. This prevents a buyer from assuming that local storage, cloud analysis and backup are interchangeable functions.

• Match the exact appliance serial, FortiCare account, tenant region and supported firmware.
• Define required event classes, daily volume, retention, reports, alerts, export and administrator roles.
• Run a controlled event, negative test, interrupted-upload recovery and evidence retrieval.
• Record current orderability, replacement SKU if required, owners, exceptions and renewal decision.

Official sources: FortiAnalyzer Ordering Guide; FortiAnalyzer Cloud Base limitations; FortiGate 301E data sheet.