Fortinet FortiAnalyzer Cloud in Dubai, UAE
FortiAnalyzer Cloud gives organisations a hosted way to centralise Fortinet security logs, analyse events, build reports and support security-operations workflows without having to size and maintain a conventional FortiAnalyzer appliance for standard cloud logging use cases. The right subscription depends on the devices sending logs, daily ingestion volume, required retention and any additional services.
Share the firewall models. FortiGate and FortiWeb subscriptions are model-linked.
Estimate daily log volume. Default device entitlements may be sufficient, or a shared GB/day subscription may be required.
List other log sources. FortiClient, FortiMail and third-party sources follow different ingestion and connector requirements.
Direct answer for buyers
Fortinet FortiAnalyzer Cloud is a cloud-based logging and analytics platform built on FortiAnalyzer. It is mainly used to receive security and event logs, centralise reporting, support investigation workflows and provide security-operations visibility for Fortinet environments. It is worth considering when an organisation wants FortiAnalyzer capabilities with a hosted service rather than a locally managed analyzer platform. Before proceeding, confirm every FortiGate or FortiWeb model, expected daily log volume, retention requirements, other Fortinet log sources, third-party integrations, subscription term and whether services such as SOCaaS, FortiAI or additional ingestion capacity are required.
What FortiAnalyzer Cloud does
FortiAnalyzer Cloud receives supported log data into a hosted Fortinet environment so security and network teams can work with centralised logging, analytics, reports, dashboards and security-operations functions. For FortiGate and FortiWeb, the commercial model is commonly tied to a per-device subscription. Current Fortinet ordering guidance also provides pooled GB/day subscriptions for extra ingestion capacity and for supported sources that do not use the same device-based entitlement.
The practical value is operational consolidation. Instead of treating each firewall or security product as an isolated source of events, teams can review data in a common analysis platform. This is useful for incident review, operational troubleshooting, reporting, threat hunting and maintaining a consistent view across distributed sites.
Who should consider it
The service may fit organisations running FortiGate or FortiWeb devices across a headquarters, branch network, data centre, cloud edge or managed security environment. It is especially relevant when the buyer wants hosted log analytics and does not want the operational responsibility of deploying storage, compute resources and a conventional FortiAnalyzer instance for the same central logging objective.
It is not automatically the right choice for every environment. Businesses with strict data-location policies, unusual third-party log sources, high ingestion volumes, established on-premises SOC tooling or a requirement for tightly controlled local infrastructure should compare deployment alternatives carefully before licensing FortiAnalyzer Cloud.
Business problems the service can help address
Scattered firewall logs
When branch and perimeter devices are reviewed separately, investigations can take longer and reporting becomes inconsistent. Centralised log collection can give operations teams one place to search and analyse relevant events.
Limited local infrastructure
A hosted service can reduce the need to procure and maintain dedicated analyzer hardware or self-managed virtual infrastructure for standard cloud logging requirements, although licensing and network connectivity still need to be planned.
Growing operational workload
Dashboards, reporting, event analysis and automation features can help security teams organise recurring review tasks. The value depends on correct configuration, sensible alerting and enough log capacity for the environment.
Unclear retention planning
Log retention is a procurement decision as well as a technical setting. Fortinet’s current device-license guidance includes default analytics and archive retention, while higher ingestion requirements can change the required subscription structure.
Capability band: what buyers are actually selecting
Bring supported security logs into one analysis environment rather than reviewing each source independently.
Use dashboards, searchable event data and reports to support operations, troubleshooting and security review.
Build repeatable response and analysis workflows where the licensed service and configuration support them.
Use IOC and outbreak-related services included in current FortiAnalyzer Cloud licensing guidance to add useful context to security events.
Product-fit matrix
| Requirement | Suitable when | Confirm before ordering |
|---|---|---|
| Hosted Fortinet log analytics | You prefer a Fortinet-hosted service instead of operating dedicated analyzer infrastructure. | Data-location policy, internet connectivity and subscription term. |
| Multiple FortiGate devices | You need central visibility across several firewalls or sites. | Exact model code and one applicable device subscription per firewall. |
| Higher log volume | Default per-device ingestion entitlement will not cover the expected data volume. | Measured GB/day, peak behaviour and required pooled capacity. |
| FortiClient or FortiMail logging | You want supported non-firewall Fortinet logs in FortiAnalyzer Cloud. | GB/day subscription requirement and supported product versions. |
| Third-party logging | You need to bring supported third-party data into the service through the current connector architecture. | Collector requirements, supported parser/source, FortiAnalyzer version and GB/day capacity. |
Verified service and licensing information
FortiAnalyzer Cloud is a service rather than one fixed hardware model, so buyers should read the table as procurement guidance rather than as a single appliance specification. Current Fortinet ordering material distinguishes device-linked subscriptions from shared GB/day ingestion options.
| Brand | Fortinet |
|---|---|
| Product name | FortiAnalyzer Cloud |
| Product type | Cloud-based central logging, analytics and security-operations platform |
| Primary device subscription pattern | FortiGate: FC-10-[FORTIGATE MODEL CODE]-585-02-DD; FortiWeb follows the corresponding model-code pattern. |
| GB/day subscription tiers | Current ordering guidance lists 5 GB/day, 50 GB/day and 500 GB/day tiers, with multiple subscriptions used where needed. |
| Included capabilities in device-based guidance | Central logging, analytics, reports, dashboards, IOC-related service, FortiGuard Outbreak Detection and Security Automation. Exact current entitlement should be confirmed for the purchased SKU. |
| Default cloud log retention | Current Fortinet ordering guidance states 3 months for analytics and 12 months for archive on device-based licensing. Confirm current terms for your SKU and service release. |
| Additional Fortinet sources | Supported products such as FortiClient and FortiMail may use shared GB/day licensing. |
| Third-party sources | Configuration dependent. Current guidance uses an on-premises FortiAnalyzer collector/connector workflow for supported third-party logs. |
| SOCaaS option | Subscription dependent. A FortiAnalyzer Cloud with SOCaaS licensing path is available; scope should be confirmed separately. |
| FortiAI service | Add-on and tier dependent. Current ordering guidance lists matching ingestion-tier subscriptions and token top-up options. |
| Availability | Contact FourTeck for current UAE license availability, term options and quotation guidance. |
Licensing, capacity and compatibility dependencies
The most common purchasing error with FortiAnalyzer Cloud is treating it as a single universal license. For FortiGate and FortiWeb environments, the device-based subscription is tied to the device model. Each applicable device requires the correct subscription, and the default log-ingestion entitlement varies with platform size. If the environment generates more data than that entitlement, a shared GB/day subscription can supplement the device licenses.
Supported sources that do not use per-device licensing can consume shared GB/day capacity. Third-party logging has additional architecture requirements, and the current Fortinet order guidance uses an on-premises FortiAnalyzer as a collector for that use case. Add-on services also have tier dependencies. For example, a FortiAI service tier should correspond to the relevant GB/day ingestion tier. These relationships make a bill-of-material review important before a quote is finalised.
Compatibility must also be checked against device firmware, FortiAnalyzer Cloud service release, FortiCloud account structure and the specific products sending logs. FourTeck can help map the environment before ordering, but final supportability depends on Fortinet’s current licensing and compatibility guidance.
A practical purchase and deployment journey
Inventory log sources
List every FortiGate, FortiWeb, FortiClient, FortiMail and third-party source that should send logs. Record model numbers and software versions where possible.
Measure or estimate volume
Use observed log generation when available. New projects should estimate daily ingestion conservatively and revisit the figure after production data is available.
Build the license structure
Map device subscriptions, pooled GB/day capacity, add-on services and subscription term. Do not assume a storage add-on replaces required per-device subscriptions.
Plan onboarding and validation
Confirm FortiCloud account access, device registration, log forwarding, retention expectations, reports, alerts and operational ownership before moving the environment into normal use.
Centralised visibility without managing a dedicated analyzer appliance
For many IT teams, the attraction of FortiAnalyzer Cloud is not simply that it is “in the cloud.” The more important point is that the hosted service changes the infrastructure responsibility. A traditional FortiAnalyzer appliance or self-managed virtual machine requires resource planning, storage design, maintenance and lifecycle work. The cloud service lets the buyer focus more directly on log sources, license entitlement, retention and operational use.
That does not remove every design decision. Reliable log forwarding still depends on network connectivity, source configuration and correct FortiCloud account relationships. Administrators also need to decide what data is useful, how dashboards and reports will be used, who will investigate alerts and what retention is necessary for operational or policy reasons.
For distributed UAE businesses, the hosted approach can be attractive when branch appliances need to feed a central security view but the organisation does not want to deploy an analyzer at every site. Centralisation can also make it easier for a shared IT or SOC team to support several offices from one operational process.
Ask whether your main constraint is infrastructure ownership, log volume, retention, regulatory control or operational staffing. The answer influences whether FortiAnalyzer Cloud, FortiAnalyzer VM or a hardware appliance is the better fit.
Analytics, reporting and security-operations workflows
Centralised logging becomes useful when teams can turn raw events into an operational view. FortiAnalyzer provides dashboards, reports, event analysis and security-operation capabilities that help analysts move from “what happened on one firewall?” to broader questions such as which devices saw the same indicator, whether a change created unusual traffic, or whether an incident pattern spans several sites.
Fortinet’s current FortiAnalyzer positioning combines a unified data approach with threat intelligence, automation and integrated security-operations functions. FortiAnalyzer Cloud device licensing guidance also lists IOC-related services, FortiGuard Outbreak Detection and Security Automation. These functions are most useful when the organisation has defined review processes. A dashboard that nobody owns, a report that nobody reads, or an alert policy tuned too broadly can still create operational noise.
When evaluating the service, identify the reports and investigations your team performs repeatedly. Determine which logs support those tasks and whether they will be retained for long enough. Then decide which automation or add-on services are needed. This approach produces a more useful license and configuration plan than selecting a subscription based only on device count.
FourTeck can discuss the intended operational workflow during the quotation stage so that the subscription choice, configuration scope and handover expectations are aligned with what administrators and analysts will actually do after deployment.
Scalable ingestion through device entitlements and pooled GB/day capacity
FortiAnalyzer Cloud uses more than one licensing mechanism because different log sources and traffic volumes create different requirements. In a FortiGate or FortiWeb deployment, the per-device subscription provides a model-linked starting point. Fortinet’s current order guide states that each device license includes a default log-ingestion volume that varies by device size. A separate GB/day subscription is used when the environment needs additional capacity beyond those device entitlements or when supported sources use the shared ingestion model.
The pooled design matters for organisations with many devices. Additional GB/day capacity can be shared across supported sources in the same FortiCloud account rather than being permanently attached to one firewall. This can be useful when branches produce uneven amounts of data. However, pooling does not eliminate the need to license applicable FortiGate or FortiWeb devices individually.
Capacity planning should consider average volume and peaks. Security events can rise during attacks, outages, policy changes, troubleshooting activity or major application shifts. If the licensed ingestion level is exceeded, current Fortinet guidance warns that logs may be throttled or dropped. A buyer therefore needs headroom and an operational process for monitoring consumption.
For a new deployment, FourTeck can help estimate the initial requirement from device models and expected usage, but measured production data remains the best basis for long-term tuning. Renewal time is also a useful point to review whether capacity and add-ons still match the environment.
Where FortiAnalyzer Cloud can fit well
Distributed branches
A retail, services or professional organisation with multiple FortiGate-protected branches may want one log-analysis platform instead of maintaining separate review processes at each location.
Lean security teams
A small SOC or shared IT team may prefer a hosted service that reduces infrastructure administration while still providing centralised analytics and security-operation functions.
Managed environments
Service providers and multi-account structures may use FortiCloud organisation capabilities and central reporting, subject to the current multitenancy model, licensing and administrative design.
Security review and troubleshooting
Teams that regularly investigate firewall events, VPN issues, traffic anomalies or policy effects can benefit from searchable historical logs and a central place to compare activity.
Integration and operational considerations
FortiAnalyzer Cloud should be planned as part of a wider security operations process. Confirm how each source will authenticate and forward logs, which administrative accounts will access the service, how roles will be separated and how the FortiCloud account is structured. For larger organisations, account ownership is a governance issue: the team responsible for procurement, security operations and cloud administration should agree who controls subscriptions, renewals and administrative access.
FortiGate and FortiWeb follow a direct device-oriented cloud logging path under current guidance. FortiClient, FortiMail and certain other supported Fortinet sources may use the shared GB/day subscription model. Third-party logs require a different design, and buyers should confirm the supported parser or connector before promising that a non-Fortinet system will be visible in the platform.
Operationally, define retention, reporting schedules, alert ownership, incident escalation and capacity review. Also decide whether FortiAnalyzer Cloud is being used only for logging and investigation or as part of a broader security-operations workflow that includes automation, FortiAI or SOCaaS. Each choice can affect licensing, configuration and support requirements.
If the environment already uses another SIEM, log platform or data lake, identify whether FortiAnalyzer Cloud will replace a function, complement it or serve as the Fortinet-focused analysis layer. Avoid purchasing overlapping services without a clear operating model.
Questions to resolve before ordering
The model code determines the corresponding device subscription SKU.
Use measured data where possible so pooled GB/day capacity is not undersized.
Separate operational analytics needs from archive requirements and any internal policy obligations.
FortiClient, FortiMail and third-party log sources can change licensing and architecture.
Treat these as separate scope and license decisions rather than assuming they are universally included.
Define admin ownership, reporting responsibilities, alert review and renewal management.
Procurement checklist
✓ Exact FortiGate and FortiWeb model codes
✓ Quantity of licensed devices
✓ Current firmware and planned upgrade state
✓ Average and peak daily log volume
✓ Required analytics and archive retention
✓ FortiClient, FortiMail or other Fortinet sources
✓ Third-party log-source requirements
✓ Subscription term and co-term preference
✓ Need for extra 5, 50 or 500 GB/day capacity
✓ FortiAI, SOCaaS or other service add-ons
✓ Configuration, migration or onboarding scope
✓ Support and operational handover expectations
How FourTeck can help with sizing and quotation preparation
A useful FortiAnalyzer Cloud quotation should be more specific than a request for “one cloud license.” FourTeck can help structure the requirement around the actual environment: device models, quantities, log sources, ingestion estimate, subscription period and optional services. This reduces the chance of choosing the wrong model-linked SKU or overlooking the GB/day capacity needed for additional sources.
For existing deployments, provide a current device inventory and any available FortiAnalyzer or FortiGate log-volume information. For new sites, share the expected firewall models, number of users, internet links, security services and whether logs from endpoints, email or third-party systems will also be included. FourTeck can then discuss a practical starting point and identify the items that still need vendor confirmation.
Where implementation support is required, include onboarding, log-forwarding configuration, report setup, migration from an existing analyzer and administrator handover in the requested scope. Visit FourTeck technology services or contact the Dubai team to discuss the requirement.
UAE availability and support guidance
FortiAnalyzer Cloud is subscription based, so availability depends on the required license SKU, firewall model, subscription term, quantity, account region and current vendor ordering policy rather than on physical warehouse stock alone. Contact FourTeck to confirm current UAE availability and the correct commercial structure for your environment. Where a project requires both Fortinet hardware and FortiAnalyzer Cloud subscriptions, it is useful to align the device bill of materials, support contracts and analytics subscriptions before placing the order.
Delivery and project coordination can be discussed after the exact requirement is confirmed. If installation or configuration assistance is needed, ask for that scope to be shown separately in the quotation so responsibilities are clear. You can also review related FourTeck security products and Fortinet firewall options in Dubai.
Dubai, Abu Dhabi, Sharjah and Ajman project coordination
Businesses in Dubai, Abu Dhabi, Sharjah and Ajman can contact FourTeck for requirement review, Fortinet model and license mapping, quotation preparation and project coordination. For FortiAnalyzer Cloud, the important regional question is usually not where a physical appliance will be installed but where the licensed devices are deployed, how they connect to the service, who owns the FortiCloud account and whether the organisation has policies governing log location or access. Share the site list, firewall models, required subscription term and any configuration or migration expectations so the solution can be reviewed as one complete requirement rather than as isolated license lines.
GCC Availability
FourTeck can assist organisations planning FortiAnalyzer Cloud requirements across GCC markets with device and license review, quotation coordination, ingestion-capacity planning, configuration scope and renewal guidance. A regional deployment may include the United Arab Emirates together with operations in Saudi Arabia, Kuwait, Qatar, Bahrain or Oman, but the commercial and technical details should be checked for each project. FortiCloud account region, subscription eligibility, service terms, device models and destination requirements can affect what should be ordered.
Product availability, licensing, delivery schedules for related hardware, service visits, project scope and vendor lead times can vary by country, model, quantity and requirement. Before requesting a GCC quotation, provide the destination country, FortiGate or FortiWeb models, number of devices, required subscription term, estimated GB/day, additional log sources and expected project timeline. For Kuwait-focused enquiries, FourTeck also provides regional contact options through FourTeck Kuwait. Confirm any installation, remote configuration or handover requirements as part of the same request.
Africa Availability
Organisations planning FortiAnalyzer Cloud for Africa can use FourTeck for requirement review, subscription selection, ingestion-capacity planning, accessories or related Fortinet hardware coordination, configuration scope and renewal preparation. Projects may cover East Africa, West Africa, Southern Africa or Central Africa, and the design should account for the destination, internet connectivity, FortiCloud account structure, device models, log volume and any local policy affecting how security logs are handled.
Availability and fulfilment can depend on the destination, exact firewall models, quantity, license region, subscription term, power or regulatory requirements for any associated hardware, shipping arrangements, vendor lead time and local project conditions. Buyers should provide the destination country, required product or service, quantity, deployment schedule and any installation or support expectations. FourTeck regional resources include FourTeck Africa, with additional information available for Kenya technology projects and Uganda technology projects. Confirm the exact commercial and technical scope before ordering.
Related FourTeck options to consider
FortiGate firewall sizing
If the firewall platform itself is still being selected, match FortiAnalyzer Cloud planning to the final FortiGate models rather than estimating licenses from a temporary shortlist.
Configuration and migration services
Plan log forwarding, account setup, report configuration and migration from an existing analyzer as a defined project scope when internal resources are limited.
On-premises FortiAnalyzer alternatives
Compare cloud service, virtual machine and hardware approaches when data control, very high log volume or local infrastructure requirements are important.
Security operations support
Where the objective includes ongoing monitoring rather than only logging, discuss SOCaaS, reporting responsibilities and support boundaries separately.
Why businesses contact FourTeck for FortiAnalyzer Cloud planning
The difficult part of a FortiAnalyzer Cloud purchase is usually not understanding that it stores and analyses logs. The difficult part is converting a real environment into the right collection of device subscriptions, pooled ingestion capacity, optional services and implementation tasks. FourTeck can help clarify those inputs before a quotation is prepared.
For a simple branch environment, this may mean confirming the correct FortiGate model codes and subscription terms. For a larger estate, it can involve multiple device types, a pooled GB/day requirement, retention planning, FortiCloud account design, third-party logging, FortiAI, SOCaaS and migration from an existing platform. A structured review helps separate what is required from what is optional.
FourTeck assistance can also cover bill-of-material guidance, compatibility review, quotation coordination, installation planning, configuration scope, migration planning and renewal discussion. The purpose is to give the buyer a clearer decision path without making unsupported promises about stock, delivery dates, compatibility or service outcomes.
How to plan FortiAnalyzer Cloud for a real business environment
Buyers researching FortiAnalyzer Cloud often arrive with several overlapping questions: whether it replaces FortiAnalyzer hardware, how its subscription is calculated, how much log storage is included, whether it is the same as FortiGate Cloud, and whether extra licenses are needed for non-FortiGate devices. The clearest way to answer those questions is to start with the architecture rather than the marketing label.
FortiAnalyzer Cloud is the hosted option in the wider FortiAnalyzer family. A hardware appliance or self-managed virtual machine gives the customer more direct responsibility for infrastructure, storage and lifecycle management. The cloud service shifts much of that platform operation to the hosted environment, but it still requires correct source configuration, suitable subscriptions and ongoing capacity review. The choice should reflect data-control needs, operational skills, expected ingestion and the organisation’s preference for hosted versus customer-managed infrastructure.
For FortiGate and FortiWeb, current Fortinet ordering guidance uses a per-device subscription. This means a ten-firewall estate should not be treated as one generic cloud license. Each applicable device needs the appropriate model-linked entitlement. The device license includes a default log-ingestion allowance that varies by platform. If the combined environment produces more data than those entitlements comfortably cover, additional GB/day capacity can be added and shared across supported sources in the same FortiCloud account.
Log volume, not just device count, drives capacity. A quiet branch firewall and a heavily used data-centre firewall may generate very different amounts of data. Buyers should use observed volume where possible and add headroom for events, troubleshooting and growth.
A service can collect the right logs yet still fail a business need if the required history is no longer available. Decide how long data is needed for investigations, operational reporting and internal policy before finalising capacity.
Another common research question is the difference between FortiAnalyzer Cloud and FortiGate Cloud. They are not simply two names for the same service. FortiGate Cloud is oriented toward FortiGate management and cloud-based operational functions, while FortiAnalyzer is the deeper logging, analytics and security-operations platform in Fortinet’s portfolio. Some organisations may use both because they solve different operational needs. The decision should be based on required management functions, depth of analytics, reporting, central log handling and the wider operating model.
Non-FortiGate sources need special attention. Supported Fortinet products such as FortiClient and FortiMail can use the shared GB/day licensing path under current ordering guidance. Third-party logs are more dependent on connector architecture and supported parsing. Fortinet’s current order material describes an on-premises FortiAnalyzer collector requirement for third-party sources. That means a buyer intending to send logs from switches, servers, applications or other vendors should verify support before assuming the cloud service will accept everything directly.
Buyers also ask whether they need the GB/day subscription immediately. Not always. A FortiGate or FortiWeb environment may be able to operate within the default device entitlements. The additional ingestion tier is used when more capacity is needed or when source types require it. This is why the quote should be based on the actual models and expected logs rather than an arbitrary package size.
Send the exact firewall models, quantities, subscription term, expected log volume, required retention, other Fortinet products, third-party sources, preferred FortiCloud account structure and any migration or configuration requirement. If you are comparing SOCaaS or FortiAI, state that separately because the service tier and operating scope can change the bill of materials.
For organisations in Dubai and the wider UAE, this approach also makes regional planning easier. A license can only be quoted accurately when the environment is defined well enough to map model codes and service terms. FourTeck can help assemble that requirement, compare the cloud approach with other FortiAnalyzer deployment options and identify the questions that should be confirmed before the order is placed.
Buyer questions that shape the final design
Do I size FortiAnalyzer Cloud by firewall count or by log volume?
Both matter, but in different ways. FortiGate and FortiWeb device subscriptions are tied to the individual model, while additional shared capacity is expressed in GB/day. Start with the number and exact model of applicable devices, then compare their included ingestion entitlements with the expected log volume. If the environment exceeds that baseline or includes sources that require shared capacity, add the appropriate GB/day subscription.
Can I use it if I already have an on-premises FortiAnalyzer?
Possibly, but the design depends on what the existing system is doing. A business may be migrating to the hosted service, keeping local analysis for selected data, or using an on-premises FortiAnalyzer as a connector for supported third-party logs. Define the target architecture before buying subscriptions so the old and new platforms do not create unnecessary duplication.
What happens if our log volume grows after deployment?
Review the service’s license-usage information and compare actual ingestion with the entitled capacity. Current Fortinet guidance provides additional 5, 50 and 500 GB/day subscription tiers that can be combined as the requirement changes. Capacity should be reviewed before sustained overage because exceeding entitlement can affect log continuity.
Is SOCaaS part of the standard FortiAnalyzer Cloud license?
Do not assume it is. Fortinet has a distinct FortiAnalyzer Cloud with SOCaaS licensing path. If managed security monitoring or analyst-led service is part of the requirement, request that scope specifically and confirm which devices and services are covered under the proposed subscription.
Should we buy extra capacity for future growth from day one?
A reasonable buffer is useful, but overbuying without evidence can increase cost unnecessarily. For an existing network, base the decision on observed logs and expected projects. For a new environment, estimate by model and use case, then schedule a capacity review after the system has run long enough to show real behaviour.
What information helps FourTeck prepare an accurate quote?
Provide model numbers, quantities, subscription duration, daily log estimate, required retention, extra Fortinet products, third-party data sources and any FortiAI, SOCaaS, configuration or migration requirements. For a multi-country project, also share the destination and account ownership structure. This lets the commercial discussion start from a defined bill of materials rather than a generic product name.
Frequently asked questions
What is Fortinet FortiAnalyzer Cloud?
It is a hosted FortiAnalyzer service for central logging, analytics, reporting and security-operations functions. It can receive supported Fortinet logs and, with the correct licensing and architecture, selected additional sources.
Does every FortiGate need a FortiAnalyzer Cloud subscription?
Under current device-based licensing guidance, each FortiGate sending logs through that model requires the applicable FortiAnalyzer Cloud device subscription for its model code.
Is additional GB/day capacity always required?
No. It is needed when the default device entitlement is insufficient or when supported log sources use the shared ingestion model. Actual need depends on log volume and source type.
How long are logs retained?
Fortinet’s current ordering guide states default device-based retention of three months for analytics and twelve months for archive. Confirm the current terms for the exact subscription being purchased.
Can FortiClient and FortiMail send logs to the service?
Supported FortiClient and FortiMail logging can use the GB/day subscription model. Confirm product version, logging support and required capacity before deployment.
Can third-party devices log directly to FortiAnalyzer Cloud?
Third-party logging is configuration dependent. Current Fortinet guidance uses an on-premises FortiAnalyzer collector/connector workflow for supported third-party logs, so source compatibility should be verified first.
Is FortiAI included?
FortiAI service licensing is an add-on consideration. Current ordering guidance provides ingestion-tier-based FortiAI subscriptions and token top-up options. Confirm the required tier and features for the deployment.
Can FourTeck help migrate from an existing FortiAnalyzer?
Migration assistance can be discussed as a project scope. The work depends on the current deployment, target cloud design, retained data, device configuration and desired reports or operational workflows.
How do I get a Dubai or UAE quotation?
Send FourTeck the firewall models, quantities, subscription term, log-volume estimate, additional log sources and required services. FourTeck can then confirm the appropriate license structure and current UAE commercial options.
Build the FortiAnalyzer Cloud requirement before you buy
Send the exact FortiGate or FortiWeb models, quantity, log-volume estimate, subscription term and any additional sources or services. FourTeck can help turn that information into a clearer licensing and deployment discussion for Dubai, the UAE and regional projects.
Product capabilities, supported integrations, licensing structures, service terms and retention behaviour can change by Fortinet release, device model, account region and subscription. Confirm the current bill of materials and supportability for your environment before ordering. Visible pricing is intentionally not stated because FortiAnalyzer Cloud pricing varies by model-linked subscription, term, ingestion capacity and optional services.
Reviews
There are no reviews yet.