Product Overview

Identity is now one of the most important control points in a business network. Employees, contractors, administrators, branch users, remote workers, guests and service accounts all need access to different systems, yet their access should not be treated equally. FortiAuthenticator FAC-VM provides a central virtual platform that helps organisations verify users, apply stronger authentication and share reliable identity information with security infrastructure. Instead of managing authentication separately on every firewall, VPN gateway, wireless platform, switch or application, the business can establish a more consistent identity layer.

The software is delivered as a virtual appliance, making it suitable for organisations that already operate a virtualisation platform and prefer to use existing compute, memory and storage resources. This approach can simplify data-centre planning, remote deployment and disaster-recovery design because the identity service is not tied to a single hardware chassis. It also allows technical teams to increase virtual resources as usage grows, subject to platform support, licensing and sizing guidance.

FAC-VM can act as a RADIUS, TACACS+ and LDAP service, support multi-factor authentication, provide single sign-on capabilities, integrate with Active Directory and other directories, issue and manage certificates, support identity-provider functions and share user identity with FortiGate security policies. These capabilities are useful where a business wants to protect VPN access, administrator logins, wireless authentication, switch access, web applications, cloud services or sensitive internal resources with stronger verification.

The platform can fit into both Fortinet-focused and mixed-vendor environments. A company may use it alongside FortiGate, FortiToken, FortiManager, FortiClient and other Security Fabric components, or connect it to third-party systems that support established authentication standards. This flexibility is important for organisations that have grown over time and cannot replace every existing system at once.

For Africa buyers, the main purchasing challenge is usually not identifying the product name. The real work is choosing the correct license quantity, support term, authentication method, high-availability design, virtual infrastructure and integration plan. FourTeck helps procurement and technical teams review these questions so that the requested quotation reflects the actual user environment rather than a generic software line item.

Key Business Benefits

The value of an identity platform is measured by how well it improves security, administration and user access. The following benefits explain why organisations consider FortiAuthenticator FAC-VM for modern business environments.

Product Highlights

These highlights should be reviewed as part of a full identity design. Token quantities, SMS services, public cloud charges, high-availability nodes, support contracts and user upgrades may be separate items. The correct quotation therefore depends on how many people will authenticate, which services they will access, what authentication methods are required and whether the organisation needs a primary and secondary node.

Technical Specifications

The minimum virtual-machine values are platform requirements, not a complete sizing recommendation for every deployment. A small user count may still need more storage when long-term logs are retained, while a large user population may require additional CPU and memory because of authentication volume, certificate activity, portal use, reporting or redundancy. Buyers should also allow resources for the underlying hypervisor, backups and monitoring. For high availability, the secondary appliance should be licensed and sized according to Fortinet guidance rather than treated as a free standby instance.

Configuration and Buyer Guidance

A successful identity project starts with a clear count of users and systems. The licensed user quantity should include the people who will authenticate through the platform, not only the employees who use VPN. Organisations should consider administrators, contractors, branch users, wireless users, application users and any remote identities that will depend on the service. Growth should also be estimated so that the initial design does not immediately require a licensing change.

Virtual infrastructure also matters. The hypervisor version must be supported by the selected FortiAuthenticator release. CPU reservation, memory, storage performance, virtual interfaces, time synchronisation, DNS and network routing should be prepared before installation. The security team should define who can administer the appliance, how administrator access will be protected and how configuration backups will be stored.

Support should be included in the purchasing discussion rather than added after deployment. The correct FortiCare contract depends on the licensed user tier and chosen term. Buyers should also decide who will perform directory integration, token enrolment, RADIUS client configuration, SAML setup, certificate services, testing and user communication. FourTeck can help turn these questions into a structured bill of materials and deployment scope.

Ideal Business Use Cases

The platform is relevant to financial services, education, healthcare, government, hospitality, retail, logistics, professional services, technology providers and other sectors where user access must be controlled. The exact configuration will differ. A school may prioritise wireless authentication and guest access, while a bank may focus on privileged administration, strong MFA and high availability. A managed service provider may need broad client support and careful separation, while a multi-site business may prioritise central policy and branch resilience. The product should therefore be selected around the organisation’s access model rather than purchased only because it belongs to an existing Fortinet environment.

FortiAuthenticator FAC-VM Centralised Authentication

Centralised authentication reduces the number of places where user verification must be configured and maintained. In a typical business, remote-access gateways, wireless networks, switches, firewalls and applications may each have separate user databases or directory connections. Over time, this creates inconsistent password rules, duplicate accounts and weak visibility. FAC-VM can provide shared authentication services so that approved systems use a common identity source and policy framework.

RADIUS is widely used for network access, including VPN, Wi-Fi and 802.1X. TACACS+ is commonly used for administrator authentication and command control on network infrastructure. LDAP can provide directory services and integration. By supporting these methods on one platform, the organisation can avoid deploying unrelated tools for each access type. The technical team can also align user groups with policy, making it easier to distinguish finance staff, engineers, contractors, guests and administrators.

Centralisation does not remove the need for careful design. The appliance must be connected securely to directories, network clients and applications. Shared secrets, certificates, firewall rules and administrator permissions should be documented. The organisation should also define fallback behaviour if the identity service is unavailable. For critical environments, high availability and tested recovery procedures are essential because authentication can become a dependency for many services.

The business benefit is improved consistency. When access policies change, administrators can update a central service rather than manually changing every device. When a user leaves the organisation, directory integration can help remove access more predictably. When auditors ask how access is controlled, the security team has a clearer architecture to explain. FourTeck can help buyers identify which systems should authenticate through FAC-VM and which legacy services may need a phased integration plan.

FortiAuthenticator FAC-VM Multi-Factor and Passwordless Access

Passwords remain common, but they are vulnerable to phishing, reuse, sharing and credential theft. Multi-factor authentication adds another verification step so that possession of a password alone is not enough. FAC-VM can support FortiToken, email or SMS one-time passwords, FIDO-based passwordless methods and adaptive authentication, depending on the selected design and licenses.

The right method depends on users and risk. Mobile tokens are convenient for employees with smartphones, while hardware tokens may be preferred for controlled environments or users who cannot rely on personal mobile devices. Email OTP can be simple to introduce but depends on the security and availability of the user’s mailbox. SMS OTP may require a FortiGuard SMS entitlement or a third-party gateway and should be assessed for cost, coverage and security. FIDO methods can deliver stronger phishing resistance, but the organisation must plan device compatibility, enrolment and recovery.

Adaptive authentication can help the platform make decisions using login context. A normal login from a familiar environment may follow one path, while a login with higher risk can require an additional challenge or be denied. This can improve the balance between security and convenience, but policies should be tested carefully to avoid blocking legitimate users or allowing weak exceptions.

A successful rollout also requires user communication. Staff need clear enrolment instructions, recovery procedures and support contacts. Administrators should define what happens when a phone is lost, a token is replaced or a user changes roles. The purchasing list may include token licenses, physical tokens, SMS services, support and implementation assistance in addition to the FAC-VM base license. FourTeck can help buyers map the user population to a practical authentication method before the final order is prepared.

FortiAuthenticator FAC-VM Scalability and Resilience

The FAC-VM licensing model is designed to expand from a 100-user base through stackable upgrade licenses. This gives organisations a path to grow the identity service without migrating to a different product each time the user count increases. However, license expansion and infrastructure sizing must be planned together. Adding users without increasing virtual resources can create performance or storage pressure, especially where the appliance retains logs or provides multiple identity services.

Fortinet publishes virtual-machine guidance covering CPU, memory, storage and interfaces. The platform supports a minimum of eight virtual CPUs and sixteen gigabytes of memory, with much larger maximum values for high-capacity deployments. Storage can range from the minimum installation requirement to many terabytes. The correct amount depends on user population, authentication frequency, certificates, portals, reporting and how long logs remain on the appliance. A deployment that forwards logs to a central system may need less local retention than one that stores detailed history for an extended period.

Resilience is equally important. Active-passive high availability can reduce the risk of a single virtual appliance becoming a point of failure. Each node requires appropriate licensing, and the surrounding network must support reliable communication, synchronisation and failover. Organisations should test authentication during node maintenance and confirm that connected devices use both servers where supported.

Backup and recovery should cover configuration, certificates, token information, directory settings and operational procedures. The virtual-machine snapshot feature should not be treated as the only backup method without checking vendor guidance. Businesses should also monitor disk capacity, service health, time synchronisation and certificate expiry. FourTeck can help buyers review user growth, log-retention policy and availability requirements so that the initial configuration supports both current operations and a realistic expansion path.

What Buyers Should Check Before Purchase

Before requesting a quote, buyers should confirm the complete requirement rather than selecting FAC-VM only by model name. The base license, user upgrades, tokens, support contract, high-availability node and implementation services are separate planning items. A correct quotation begins with the number of users, the systems that will authenticate and the business impact if authentication is unavailable.

Infrastructure readiness is another common gap. The buyer should reserve suitable vCPU, memory and storage on a supported platform. Network connectivity, DNS, NTP, routing, firewall rules, backup storage and administrative access should be prepared. Where the service will support several branches, link quality and latency must be considered. Where long-term local logs are required, storage sizing should reflect the retention period rather than only the minimum installation value.

Accessories and add-ons can materially change the project cost. FortiToken licenses or devices, SMS credits, SSO mobility agent licenses, certificates, public cloud resources and professional services may all be relevant. High-availability deployments need a separately licensed secondary node. Existing support contracts may require co-term planning when the user count is upgraded.

To prepare an accurate quote, provide FourTeck with the deployment country, user count, current directory, connected devices and applications, preferred authentication method, virtualisation platform, required support term, high-availability requirement and target project date. This information helps reduce incorrect licensing, missing add-ons and unexpected implementation work.

Africa Availability and Service Support

FourTeck supports FortiAuthenticator inquiries across Africa with help for product selection, license review, quotation, delivery coordination and deployment planning. Availability can vary according to the selected license model, user quantity, support term, supplier status and country. Because this is software rather than a standard boxed appliance, buyers should also confirm the delivery method for the registration code, the account details used for registration and the technical team responsible for downloading and activating the virtual appliance.

Configuration support begins with understanding the intended services. A simple 100-user VPN MFA deployment has different requirements from a multi-branch identity platform supporting RADIUS, TACACS+, SAML, certificates and high availability. FourTeck can help review the bill of materials so that token requirements, user upgrades, support contracts and implementation needs are not missed.

Warranty and support for software should be discussed in terms of the selected FortiCare entitlement, license term and deployment responsibility. Response coverage, access to updates and technical support depend on the contracted service. Buyers should request clarification on the exact support SKU and duration included in the quotation.

Contact FourTeck Sales

Africa Country and Regional Coverage

Businesses across Africa, including Kenya, Uganda, Nigeria, Ghana, Tanzania, Rwanda, Ethiopia, South Africa, Zambia, Botswana, Senegal and other regional markets can contact FourTeck for availability guidance, licensing review and quote assistance. Regional requirements differ, so the team considers the delivery country, customer type, user count, preferred currency, support term and project schedule before preparing the commercial response.

For multi-country organisations, a consistent identity architecture can simplify how employees and administrators access shared resources. However, each location may have different internet reliability, directory design, time zones, regulations and operational support. FourTeck can help the buyer prepare a standard product and license plan while identifying where local deployment details require adjustment. This approach is useful for branch networks, education groups, financial organisations, logistics companies, hospitality operators, public-sector projects and regional service providers.

The quotation process should clearly state whether the requirement is a new deployment, user expansion, support renewal, high-availability node or replacement for an existing platform. This helps distinguish the base license from upgrade and support SKUs and reduces delays during order processing.

GCC, Middle East and Africa Availability

FourTeck Africa can support identity-software inquiries for organisations in Africa while coordinating wider regional requirements through selected FourTeck platforms serving GCC and Middle East markets. Businesses with operations in the UAE, Saudi Arabia, Qatar, Oman, Bahrain and African countries may need a consistent license and deployment plan across several sites. The commercial and support approach can vary by country, order quantity, support entitlement and customer registration details.

Regional projects should define where the virtual appliance will be hosted, which directories and applications it will serve, how branches connect to it and who is responsible for administration. Some organisations prefer a central data-centre deployment, while others require local instances or a high-availability design. The decision should consider latency, business continuity, data-handling policy and available technical resources.

Buyers can review Africa services through FourTeck Africa, regional assistance through FourTeck Kenya and FourTeck Uganda, or wider Middle East project support through FourTeck UAE. Availability, delivery method, support handling and configuration assistance remain dependent on the selected country and project scope.

Other Options Buyers May Consider

The right identity solution depends on deployment size, hosting preference and security architecture. Buyers may consider related Fortinet products and services when building the complete access-control environment. The items below are not automatic substitutes; they address connected requirements that should be evaluated together.

Why Buyers Choose FourTeck

Identity software procurement involves more than ordering a license code. The buyer must connect licensing, virtual infrastructure, authentication methods, support and implementation into one workable plan. FourTeck helps customers translate technical requirements into a quotation that procurement teams can understand and technical teams can deploy.

The FourTeck process starts with requirement review. The team can help identify the user tier, base or upgrade license, support duration, high-availability requirement and token method. For customers with an existing Fortinet environment, the review can consider FortiGate, FortiToken, FortiClient, FortiManager and directory integration. For mixed environments, the discussion can focus on RADIUS, TACACS+, LDAP, SAML and other standards required by existing systems.

FourTeck also supports practical procurement concerns. Buyers may need a formal quotation, lead-time guidance, delivery coordination, invoice documentation, project supply planning and confirmation of what is included or excluded. These details are especially important for institutional, enterprise and multi-country orders where commercial approval may take several stages.

The goal is to reduce wrong selection, incomplete licensing and unclear deployment responsibility. FourTeck does not assume that every customer needs the largest package. The recommendation should match the real user count, risk level, hosting environment, growth plan and support expectation. This approach helps organisations control cost while preserving a clear path for future expansion.

Frequently Asked Questions