FIPS 140-2 Non-Proprietary Security Policy
FortiWeb 5.6
FortiWeb 5.6 FIPS 140-2 Security Policy
Document Version: 2.5
Publication Date: Thursday, January 04, 2018
Description: Documents FIPS 140-2 Non-Proprietary Level 1 Security Policy issues, compliancy and requirements
for FIPS compliant operation.
Firmware Version: v5.6.0, build 6180,170928
FORTINET DOCUMENT LIBRARY
http://docs.fortinet.com
FORTINET VIDEO GUIDE
http://video.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
CUSTOMER SERVICE & SUPPORT
https://support.fortinet.com
http://cookbook.fortinet.com/how-to-work-with-fortinet-support/
FORTIGATE COOKBOOK
http://cookbook.fortinet.com
FORTINET TRAINING SERVICES
http://www.fortinet.com/training
FORTIGUARD CENTER
http://www.fortiguard.com
FORTICAST
http://forticast.fortinet.com
END USER LICENSE AGREEMENT
http://www.fortinet.com/doc/legal/EULA.pdf
FORTINET PRIVACY POLICY
https://www.fortinet.com/corporate/about-us/privacy.html
FEEDBACK
Email: techdocs@fortinet.com
Thursday, January 04, 2018
FortiWeb 5.6 FIPS 140-2 Non-Proprietary Level 1 Security Policy
01-560-0418200-20170410
This document may be freely reproduced and distributed whole and intact when including the copyright notice found on the
last page of this document.
TABLE OF CONTENTS
FortiWeb 5.6 1
Overview 4
References 4
Introduction 5
Security Level Summary 6
Module Descriptions 7
Module Interfaces 9
Web-Based Manager 9
Command Line Interface 10
Roles, Services and Authentication 10
Roles 10
FIPS Approved Services 11
Non-FIPS Approved Services 12
Authentication 13
Operational Environment 13
Cryptographic Key Management 13
Random Number Generation 13
Entropy 13
Key Zeroization 14
Algorithms 14
Cryptographic Keys and Critical Security Parameters 15
Alternating Bypass Feature 18
Key Archiving 18
Mitigation of Other Attacks 19
FIPS 140-2 Compliant Operation 20
Enabling FIPS-CC mode 21
Self-Tests 22
Startup and Initialization Self-tests 22
Conditional Self-tests 23
Critical Function Self-tests 23
Error State 23
Overview
This document is a FIPS 140-2 Security Policy for Fortinet Incorporated’s FortiWeb 5.6 Web Application Firewall
appliances. This policy describes how the FortiWeb 5.6 (hereafter referred to as the ‘module’) meets the FIPS
140-2 security requirements and how to operate the module in a FIPS compliant manner. This policy was created
as part of the Level 2 FIPS 140-2 validation of the module.
The Federal Information Processing Standards Publication 140-2 - Security Requirements for Cryptographic
Modules (FIPS 140-2) details the United States Federal Government requirements for cryptographic modules.
Detailed information about the FIPS 140-2 standard and validation program is available on the NIST (National
Institute of Standards and Technology) website at http://csrc.nist.gov/groups/STM/cmvp/index.html.
References
This policy deals specifically with operation and implementation of the modules in the technical terms of the FIPS
140-2 standard and the associated validation program. Other Fortinet product manuals, guides and technical
notes can be found at the Fortinet technical documentation website at http://docs.fortinet.com.
Additional information on the entire Fortinet product line can be obtained from the following sources:
l Find general product information in the product section of the Fortinet corporate website at
http://www.fortinet.com/products.
l Find on-line product support for registered products in the technical support section of the Fortinet corporate
website at http://www.fortinet.com/support.
l Find contact information for technical or sales related questions in the contacts section of the Fortinet corporate
website at http://www.fortinet.com/contact.
l Find security information and bulletins in the FortiGuard Center of the Fortinet corporate website at
http://fortiguard.com.
4 FIPS 140-2 Security Policy
Fortinet, Inc.
Introduction
The FortiWeb Web Application Firewall provides specialized, layered application threat protection for medium
and large enterprises, application service providers, and SaaS providers. FortiWeb Web Application Firewall
protects your web-based applications and internet-facing data from attack and data loss. Using advanced
techniques to provide bidirectional protection against malicious sources, application layer DoS Attacks and
Sophisticated Threats like SQL injection and Cross-site scripting.
FortiWeb platforms help you prevent identity theft, financial fraud and denial of service. It delivers the technology
you need to monitor and enforce government regulations, industry best practices, and internal policies.
FIPS 140-2 Security Policy
Fortinet, Inc.
5
Security Level Summary
The modules meets the overall requirements for a FIPS 140-2 Level 1 validation.
Table 1: Summary of FIPS security requirements and compliance levels
Security Requirement Compliance Level
Cryptographic Module Specification 1
Cryptographic Module Ports and Interfaces 3
Roles, Services and Authentication 3
Finite State Model 1
Physical Security 1
Operational Environment N/A
Cryptographic Key Management 1
EMI/EMC 1
Self-Tests 1
Design Assurance 3
Mitigation of Other Attacks N/A
6 FIPS 140-2 Security Policy
Fortinet, Inc.
Module Descriptions
The module is a firmware operating system that runs exclusively on the FortiWeb line of appliances. The
firmware consists of multiple object files.
The FortiWeb appliances are purpose built, PC based, multiple chip, standalone cryptographic modules
consisting of production grade components contained in a physically protected enclosure.
Figure 1 - FortiWeb Physical Cryptographic Boundary
The Boot Device in the diagram above can refer to a separate, internal component or a partition on the Mass
Storage device. All references herein of ‘boot device’ shall refer to the configuration specific to the FortiWeb
appliance.
FIPS 140-2 Security Policy
Fortinet, Inc.
7
Module Descriptions
Figure 2 - FortiWeb Logical Cryptographic Boundary
For the purposes of FIPS 140-2 conformance testing, the module was tested on the FortiWeb-4000E appliance
and used a Fortinet entropy token (part number FTR-ENT-1) as the entropy source.
The validated firmware version is FortiWeb v5.6.0, build 6180,170928.
The module can also be executed on any of the following FortiWeb appliances and remain vendor affirmed FIPS-
compliant.
Table 2: Vendor affirmed FIPS-compliant appliances
FortiWeb 100D FortiWeb 400C
FortiWeb 400D FortiWeb 600D
FortiWeb 1000C FortiWeb 1000D
FortiWeb 3000C FortiWeb 3000CFSX
FortiWeb 3000D FortiWeb 3000DFSX
FortiWeb 3000E FortiWeb 3010E
FortiWeb 4000C FortiWeb 4000D
Note that no claim can be made as to the correct operation of the module or the security strengths of the
generated keys when ported to an operational environment which is not listed on the validation certificate.
8 FIPS 140-2 Security Policy
Fortinet, Inc.
Module Descriptions Module Interfaces
Module Interfaces
The Module’s logical interfaces and physical ports are described in Table 2.
Table 3: FortiWeb logical and physical ports
FIPS 140 Interface Logical Interface Physical Port
Data Input API input parameters Network interface, USB interface
(Entropy Token)
Data Output API output parameters Network interface
Control Input API function calls Network interface, serial interface,
USB interface (Entropy Token)
Status Output API return values Network interface, serial interface
Power Input N/A The power supply is the power
interface
Web-Based Manager
The FortiWeb web-based manager provides GUI based access to the module and is the primary tool for
configuring the modules. The manager requires a web browser on the management computer and an Ethernet
connection between the FortiWeb unit and the management computer.
A web-browser that supports Transport Layer Security (TLS) 1.2 is required for remote access to the web-based
manager when the module is operating in FIPS-CC mode. HTTP access to the web-based manager is not
allowed in FIPS mode and is disabled.
FIPS 140-2 Security Policy
Fortinet, Inc.
9
Command Line Interface Module Descriptions
Figure 3 - The FortiWeb web-based manager
Command Line Interface
The FortiWeb Command Line Interface (CLI) is a full-featured, text based management tool for the module. The
CLI provides access to all of the possible services and configuration options in the module. The CLI uses a
console connection or a network (Ethernet) connection between the FortiWeb unit and the management
computer. The console connection is a direct serial connection. Terminal emulation software is required on the
management computer using either method. For network access, a Telnet or SSH client that supports the SSH
v2.0 protocol is required (SSH v1.0 is not supported in FIPS-CC mode). Telnet access to the CLI is not allowed in
FIPS-CC mode and is disabled.
Roles, Services and Authentication
Roles
When configured in FIPS mode, the module provides the following roles:
l Crypto Officer
l Network User
The Crypto Officer role is initially assigned to the default ‘admin’ operator account. The Crypto Officer role has
read-write access to all of the module’s administrative services. The initial Crypto Officer can create additional
operator accounts. These additional accounts are assigned the Crypto Officer role and can be assigned a range
of read/write or read only access permissions including the ability to create operator accounts.
10 FIPS 140-2 Security Policy
Fortinet, Inc.
Module Descriptions Roles, Services and Authentication
The modules also provide a Network User role for end-users (Users). Network Users can make use of the
encrypt/decrypt services, but cannot access the modules for administrative purposes.
The module does not provide a Maintenance role.
FIPS Approved Services
The following tables detail the types of FIPS approved services available to each role in each mode of
operation, the types of access for each role and the Keys or CSPs they affect.
The access types are abbreviated as follows:
Read Access R
Write Access W
Execute Access E
Table 4: Services available to Crypto Officers
Service Access Key/CSP
authenticate to module* WE Crypto Officer Password, Diffie-Hellman
Key, HTTP/TLS and SSH Server/Host
Keys, HTTPS/TLS and SSH Authentication
Keys, and HTTPS/TLS and SSH Session
Encryption Keys, DRBG Output, DRBG
Seed, NDRNG Output String, DRBG v and
key values
show system status N/A N/A
show FIPS-CC mode enabled/disabled
(console/CLI only)
N/A N/A
enable FIPS-CC mode of operation
(console only)
WE Configuration Integrity Key
key zeroization W All Keys
execute factory reset (disable FIPS-CC
mode, console/CLI only)
W All keys stored in Flash RAM
execute FIPS-CC on-demand self-tests
(console only)
E Configuration Integrity Key, Firmware
Integrity Key
add/delete Crypto Officer and network
users
WE
Crypto Officer Password, Network User
Password
FIPS 140-2 Security Policy
Fortinet, Inc.
11
Roles, Services and Authentication Module Descriptions
Service Access Key/CSP
set/reset Crypto Officer and network
user passwords
WE Crypto Officer Password, Network User
Password
backup/restore configuration file RWE
Configuration Encryption Key,
Configuration Backup Key
read/set/delete/modify module
configuration
N/A N/A
modify user preferences N/A N/A
execute firmware update WE Firmware Update Key
read log data (GUI only) N/A N/A
delete log data (GUI only) N/A N/A
execute system diagnostics
(console/CLI only)
N/A N/A
format log disk (CLI only) WE N/A
enable/disable alternating bypass mode WE N/A
Table 5: Services available to Network Users in FIPS-CC mode
Service/CSP Access Key/CSP
authenticate to module* E Network User Password, Diffie-Hellman
Key, HTTPS/TLS Server/Host Key,
HTTPS/TLS Session Authentication Key,
HTTPS/TLS Session Encryption Key,
DRBG Output, DRBG Seed, NDRNG
Output String, DRBG v and key values,
Non-FIPS Approved Services
The module also provides the following non-FIPS approved services:
l Configuration backups using password protection
l Services marked with an asterisk (*) Table 4 and Table 5 are considered non-approved when using the following
algorithms:
l Non-compliant-strength Diffie-Hellman
l Non-compliant-strength RSA key wrapping
The above services shall not be used in the FIPS approved mode of operation.
12 FIPS 140-2 Security Policy
Fortinet, Inc.
Module Descriptions Operational Environment
Authentication
The module uses identity based authentication. By default, operators and users authenticate with a username
and password combination to access the module. Remote operator authentication is done over HTTPS (TLS) or
SSH. Local operator authentication is done over the console connection. Remote user authentication is done over
HTTPS (TLS). Password entry is obfuscated using asterisks.
Operator authentication over HTTPS/SSH and user authentication over HTTPS are subject to a limit of 3 failed
authentication attempts in 1 minute. Operator authentication using the console is not subject to a failed
authentication limit, but the number of authentication attempts per minute is limited by the bandwidth available
over the serial connection.
The minimum password length is 8 characters when in FIPS-CC mode (maximum password length is 32
characters). The password may contain any combination of upper- and lower-case letters, numbers, and printable
symbols; allowing for 94 possible characters. The odds of guessing a password are 1 in 94^8 which is significantly
lower than one in a million. Recommended procedures to increase the password strength are explained in FIPS
140-2 Compliant Operation .
Operational Environment
The module constitutes the entire firmware operating system for a FortiWeb unit and can only be installed and
run on a FortiWeb appliance. The module provides a proprietary and non-modifiable operating system and does
not provide a programming environment.
Cryptographic Key Management
Random Number Generation
The module uses a firmware based, deterministic random bit generator (DRBG) that conforms to NIST Special
Publication 800-90A. The Module generates cryptographic keys whose strengths are modified by available
entropy.
Entropy
The module uses a Fortinet entropy token (part number FTR-ENT-1 or part number FTR-ENT-2) to seed the
DRBG during the modules’ boot process and to periodically reseed the DRBG. The entropy token is not included
in the boundary of the module and therefore no assurance can be made for the correct operation of the entropy
token nor is there a guarantee of stated entropy.
Entropy Strength
The entropy loaded into the approved AES-256 bit DRBG is 256 bits. The entropy source is over-seeded and then
an HMAC-SHA-256 post-conditioning component (as per section 6.4.2 of SP 800-90B) is applied.
FIPS 140-2 Security Policy
Fortinet, Inc.
13
Cryptographic Key Management Module Descriptions
Reseed Period
The RBG is seeded from the entropy token during the boot process and then reseeded periodically. The default
reseed period is once every 24 hours (1440 minutes) and is configurable (1 to 1440 minutes). The entropy token
must be installed to complete the boot process and to reseed the DRBG.
Key Zeroization
The zeroization process must be performed under the direct control of the operator. The operator must be
present to observe that the zeroization method has completed successfully.
All keys and CSPs are zeroized by erasing the module’s boot device and then power cycling the FortiGate unit. To
erase the boot device, execute the following command from the CLI:
execute erase-disk <boot device>
The boot device ID may vary depending on the FortiGate module. Executing the following command will output a
list of the available internal disks:
execute erase-disk ?
Algorithms
Table 6: FIPS Approved Algorithms
Algorithm NIST Certificate Number
CTR DRBG (NIST SP 800-90A) with AES 256-bits 1434
AES in CBC mode (128-, 256-bits) 4461
SHA-1 3673
SHA-256 3673
HMAC SHA-1 2960
HMAC SHA-256 2960
RSA PKCS1
l Key Pair Generation: 2048 and 3072 bit
l Signature Generation: 2048 and 3072-bit
l Signature Verification: 1024, 2048 and 3072-bit
l For legacy use, the module supports 1024-bit RSA
keys and SHA-1 for signature verification
2437
CVL (SSH) AES 128-bit, AES 256-bit CBC (using
SHA1)
1169
CVL (TLS 1.0 and 1.1) 1169
CKG (NIST SP 800-133) Vendor Affirmed
14 FIPS 140-2 Security Policy
Fortinet, Inc.
Module Descriptions Cryptographic Key Management
KTS (AES Cert. #4461 and HMAC Cert. #2960; key establishment methodology provides between 128 and 256
bits of encryption strength).
In accordance with FIPS 140-2 IG D.12, the cryptographic module performs Cryptographic Key Generation
(CKG)as per SP800-133 (vendor affirmed). The resulting generated symmetric key and the seed used in the
asymmetric key generation are the unmodified output from SP800-90A DRBG.
There are algorithms, modes, and keys that have been CAVs tested but are not available when the module is
configured for FIPS compliant operation. Only the algorithms, modes/methods, and key lengths/curves/moduli
shown in this table are supported by the module in the FIPS validated configuration.
Table 7: FIPS Allowed Algorithms
Algorithm
RSA (CVL Cert. #1169, key wrapping; key establishment methodology provides 112 or 128 bits of encryption
strength)
Diffie-Hellman (CVL Cert. #1169, key agreement; key establishment methodology provides 112 bits of
encryption strength)
NDRNG (Entropy Token)
MD5 (only used as part of the TLS protocol)
Table 8: Non-FIPS Approved Algorithms
Algorithm
RSA is non-compliant when keys less than 2048 bits are used, since such keys do not provide the minimum
required 112 bits of encryption strength.
Diffie-Hellman is non-compliant when keys less than 2048 bits are used, since such keys do not provide the
minimum required 112 bits of encryption strength.
Note that the SSH and TLS protocols, other than the KDF, have not been tested by the CMVP or CAVP as per
FIPS 140-2 Implementation Guidance D.11.
Cryptographic Keys and Critical Security Parameters
The following table lists all of the cryptographic keys and critical security parameters used by the modules. The
following definitions apply to the tables below.
Table 9: Cryptographic Keys and Critical Security Parameters Descriptions
Key or CSP The key or CSP description.
Storage Where and how the keys are stored
FIPS 140-2 Security Policy
Fortinet, Inc.
15
Cryptographic Key Management Module Descriptions
Key or CSP The key or CSP description.
Usage How the keys are used
Zeroization The key zeroization method
Table 10: Cryptographic Keys and Critical Security Parameters used in FIPS-CC mode
Key or CSP Generation Storage Usage Zeroization
NDRNG output
string
Automatic Flash RAM
Plain-text
Input string for the
entropy pool (5120
bits)
By erasing the flash
memory and power
cycling the module
DRBG seed Automatic Flash RAM
Plain-text
256-bit seed used by
the DRBG (output
from NDRNG)
By erasing the flash
memory and power
cycling the module
DRBG output Automatic Flash RAM
Plain-text
Random numbers
used in cryptographic
algorithms (256-bits)
By erasing the flash
memory and power
cycling the module
DRBG v and key
values
Automatic Flash RAM
Plain-text
Internal state values
for the DRBG 128 and
256
By erasing the flash
memory and power
cycling the module
Diffie-Hellman
Keys
Automatic SDRAM
Plain-text
Key agreement and
key establishment
By erasing the flash
memory and power
cycling the module
Firmware Update
Key
Preconfigured Flash RAM
Plain-text
Verification of
firmware integrity
when updating to new
firmware versions
using RSA public key
(firmware load test,
2048-bit signature)
By erasing the flash
memory and power
cycling the module
Firmware Integrity
Key
Preconfigured Flash RAM
Plain-text
Verification of
firmware integrity in
the firmware integrity
test using RSA public
key (firmware integrity
test, 2048-bit
signature)
By erasing the flash
memory and power
cycling the module
16 FIPS 140-2 Security Policy
Fortinet, Inc.
Module Descriptions Cryptographic Key Management
Key or CSP Generation Storage Usage Zeroization
HTTPS/TLS
Server/Host Key
Preconfigured Flash RAM
Plain-text
RSA private key used
in the HTTPS/TLS
protocols (key
establishment, 2048-
bit signature)
By erasing the flash
memory and power
cycling the module
HTTPS/TLS
Session
Authentication Key
Automatic SDRAM
Plain-text
HMAC SHA-1 or
HMAC SHA-256 key
used for HTTPS/TLS
session
authentication
By erasing the flash
memory and power
cycling the module
HTTPS/TLS
Session Encryption
Key
Automatic SDRAM
Plain-text
AES (128-, 256- bit)
key used for
HTTPS/TLS session
encryption
By erasing the flash
memory and power
cycling the module
SSH Server/Host
Key
Preconfigured Boot device
Plain-text
RSA private key used
in the SSH protocol
(key establishment,
2048-bit signature)
By erasing the flash
memory and power
cycling the module
SSH Session
Authentication Key
Automatic SDRAM
Plain-text
HMAC SHA-1 or
HMAC SHA-256 key
used for SSH session
authentication
By erasing the flash
memory and power
cycling the module
SSH Session
Encryption Key
Automatic SDRAM
Plain-text
AES (128-, 256- bit)
key used for SSH
session encryption
By erasing the flash
memory and power
cycling the module
Crypto Officer
Password
Manual Flash RAM
SHA-256 hash
Used to authenticate
operator access to the
module
By erasing the flash
memory and power
cycling the module
Configuration
Integrity Key
Preconfigured Flash RAM
Plain-text
HMAC SHA-256 hash
used for configuration
and firmware integrity
(bypass) tests
By erasing the flash
memory and power
cycling the module
Configuration
Encryption Key
Preconfigured Flash RAM
Plain-text
AES 256-bit key used
to encrypt CSPs on
the Boot device and in
the backup
configuration file
(except for crypto
officer passwords in
the backup
configuration file)
By erasing the flash
memory and power
cycling the module
FIPS 140-2 Security Policy
Fortinet, Inc.
17
Alternating Bypass Feature Module Descriptions
Key or CSP Generation Storage Usage Zeroization
Configuration
Backup Key
Preconfigured Flash RAM
Plain-text
HMAC SHA-256 key
used to encrypt crypto
officer passwords in
the backup
configuration file
By erasing the flash
memory and power
cycling the module
Network User
Password
Manual Flash RAM
SHA-256 hash
Used during user
authentication
By erasing the flash
memory and power
cycling the module
The Generation column lists all of the keys/CSPs and their entry/generation methods.
Manual entered keys are entered by the operator electronically (as defined by FIPS)
using the console or a management computer. Pre-configured keys are set as part of
the firmware (hardcoded) and are not operator modifiable. Automatic keys are
generated as part of the associated protocol.
Alternating Bypass Feature
The primary cryptographic function of the module is encrypting/decrypting web application traffic sent using
HTTPS. The module can also send/receive plain-text web traffic using HTTP. The module implements an
alternating bypass feature based on the module's configuration. If the traffic from the client is sent/received using
HTTPS , the module is operating in a non-bypass state. If traffic from the client is passed directly to the backend
webserver using HTTP, the module is operating in bypass state.
Two independent actions must be taken by a CO to create the bypass HTTPs policy: the CO must select HTTPS
and then specifically save that policy.
Incoming traffic is processed according to the module configuration. If HTTPS option is selected, the module
handles SSL negotiations and encryption/decryption, instead of the web servers. Connections between the client
and the module are encrypted using TLS (non-bypass state). If HTTP option is selected the module accepts
connections to the web servers in plain-text (bypass state).
Outgoing traffic is processed according to the HTTP service configured on the module. If HTTPS is selected, web
traffic will be encrypted using TLS (non-bypass state). If HTTP is configured, web traffic is sent in plain-text
(bypass state).
Use of HTTPS for incoming/outgoing traffic is enabled by selecting " HTTPS" as the HTTPS Service via Server
Policy configuration.
Key Archiving
The module supports key archiving to a directly attached management computer as part of the module
configuration file backup. Operator entered keys are archived as part of the module configuration file. The
configuration file is stored in plain text, but keys in the configuration file are either AES encrypted using the
18 FIPS 140-2 Security Policy
Fortinet, Inc.
Module Descriptions Mitigation of Other Attacks
Configuration Encryption Key or stored as a keyed hash using HMAC SHA-256 using the Configuration Backup
Key.
Mitigation of Other Attacks
The module does not mitigate against any other attacks.
FIPS 140-2 Security Policy
Fortinet, Inc.
19
FIPS 140-2 Compliant Operation
The Fortinet hardware is shipped in a non-FIPS 140-2 compliant configuration. The following steps must be
performed to put the module into a FIPS compliant configuration:
1. Download the model specific FIPS validated firmware image from the Fortinet Support site
athttps://support.fortinet.com/
2. Verify the integrity of the firmware image
3. Install the FIPS validated firmware image
4. Install the entropy token
5. Enable the FIPS-CC mode of operation
These steps are described in detail in the "FIPS 140-2 and Common Criteria Compliant Operation for FortiWeb
5.6" document that can be found on the Fortinet Technical Documentation website.
In addition, FIPS 140-2 compliant operation requires that you follow secure procedures for installation and
operation of the FortiWeb unit. You must ensure that:
l The FortiWeb unit is configured in the FIPS-CC mode of operation.
l The FortiWeb unit is installed in a secure physical location.
l The Fortinet entropy token is enabled.
l The Fortinet entropy token remains in the USB port during opration.
l Physical access to the FortiWeb unit is restricted to authorized operators.
l Administrative passwords are at least 8 characters long.
l Administrative passwords are changed regularly.
l Administrator account passwords must have the following characteristics:
l One (or more) of the characters must be capitalized
l One (or more) of the characters must be numeric
l One (or more) of the characters must be non alpha-numeric (e.g. punctuation mark)
l Administration of the module is permitted using only validated administrative methods. These are:
l Console connection
l Web-based manager via HTTPS
l Command line interface (CLI) access via SSH
l Diffie-Hellman groups of less than less than 2048 bits are not used.
l Client side RSA certificates must use 2048 bit or greater key sizes.
l Only approved and allowed algorithms are used (see “Algorithms” on page 12).
l The module is configured in reverse proxy mode.
Once the FIPS validated firmware has been installed and the module properly configured in the FIPS-CC mode of
operation, the module is running in a FIPS compliant configuration. It is the responsibility of the CO to ensure the
module only uses approved algorithms and services to maintain the module in a FIPS-CC Approved mode of
operation. Using any of the non-approved algorithms and services switches the module to a non-FIPS mode of
operation. Prior to switching between modes the CO should ensure all keys and CSPs are zeroized to prevent
sharing of keys and CSPs between the FIPS Approved and non-FIPS mode of operation.
20 FIPS 140-2 Security Policy
Fortinet, Inc.
FIPS 140-2 Compliant Operation Enabling FIPS-CC mode
Enabling FIPS-CC mode
To enable the FIPS 140-2 compliant mode of operation, the operator must execute the following command from
the Local Console:
config system fips-cc
set entropy-token enable
set status enable
end
The Operator is required to supply a password for the admin account which will be assigned to the Crypto Officer
role.
The supplied password must be at least 8 characters long and correctly verified before the system will restart in
FIPS-CC mode.
Upon restart, the module will execute self-tests to ensure the correct initialization of the module’s cryptographic
functions.
After restarting, the Crypto Officer can confirm that the module is running in FIPS-CC mode by executing the
following command from the CLI:
get system status
If the module is running in FIPS-CC mode, the system status output will display the line:
FIPS-CC mode: enabled
Note that enabling/disabling the FIPS-CC mode of operation will automatically invoke the key zeroization service.
The key zeroization is performed immediately after FIPS-CC mode is enabled/disabled.
FIPS 140-2 Security Policy
Fortinet, Inc.
21
Self-Tests
Startup and Initialization Self-tests
The module executes the following self-tests during startup and initialization:
l Firmware integrity test using RSA 2048-bit signatures
l Configuration integrity test using HMAC SHA-256
l Triple-DES, CBC mode, encrypt known answer test
l Triple-DES, CBC mode, decrypt known answer test
l AES, CBC mode, encrypt known answer test
l AES, CBC mode, decrypt known answer test
l HMAC SHA-1 known answer test
l SHA-1 known answer test (tested as part of HMAC SHA-1 known answer test)
l HMAC SHA-256 known answer test
l SHA-256 known answer test (tested as part of HMAC SHA-256 known answer test)
l RSA signature generation known answer test
l RSA signature verification known answer test
l DRBG known answer test
l RBG Instantiate test
l RBG Generate test
l RBG Reseed test
The results of the startup self-tests are displayed on the console during the startup process. The startup self-tests
can also be initiated on demand using the CLI command execute fips kat all(to initiate all self-tests) or
execute fips kat <test> (to initiate a specific self-test).
When the self-tests are run, each implementation of an algorithm is tested - e.g. when the AES self-test is run, all
AES implementations are tested.
The output for successful self-tests is shown below:
FIPS-CC mode: Starting self-tests.
Running Configuration Integrity test... passed
Running AES test... passed
Running SHA1 HMAC test... passed
Running SHA256 HMAC test... passed
Running 3DES test... passed
Running RSA test... passed
Running Firmware integrity test... passed
Running RBG instantiate test... passed
Running RBG reseed test... passed
Running RBG generate test... passed
Self-tests passed
22 FIPS 140-2 Security Policy
Fortinet, Inc.
Self-Tests Conditional Self-tests
Conditional Self-tests
The module executes the following conditional tests when the related service is invoked:
l Continuous NDRNG test
l Continuous DRBG test
l RSA pairwise consistency test
l Configuration integrity test using HMAC SHA-256
l Firmware load test using RSA signatures
Critical Function Self-tests
The module also performs the following critical function self-tests appicable to the DRBG, as per NIST SP 800-
90A Section 11:
l Instantiate test
l Generate test
l Reseed test
l Uninstantiate test
Error State
If any of the self-tests or conditional tests fail, the module enters an error state as shown by the console output
below:
Self-tests failed
Entering error mode...
The system is going down NOW !!
The system is halted.
All data output and cryptographic services are inhibited in the error state.
FIPS 140-2 Security Policy
Fortinet, Inc.
23
Copyright© 2018 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet,
Inc., in the U.S. and other jurisdictions, and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company
names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and
actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein
represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written
contract, signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified
performance metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For
absolute clarity, any such warranty will be limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. In no event does Fortinet make any
commitment related to future deliverables, features, or development, and circumstances may change such that any forward-looking statements herein are not accurate.
Fortinet disclaims in full any covenants, representations,and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify,
transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.