FIPS 140-2 Non-Proprietary
Security Policy
FortiAnalyzer™ 5.2
FortiAnalyzer™ 5.2 FIPS 140-2 Non-Proprietary Security Policy
Document Version: 0.9
Publication Date: December 23, 2015
Description: Documents FIPS 140-2 Level 1 Security Policy issues, compliancy and requirements for FIPS
compliant operation.
Firmware Version: v5.2.4-build0738 150923(GA)
FortiAnalyzer™ 5.2: FIPS 140-2 Non-Proprietary Security Policy
05-524-261848 -20151006
for FortiAnalyzer™ 5.2
Copyright© 2015 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.
This document may be freely reproduced and distributed whole and intact including this copyright notice.
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848 -20151006 1
http://docs.fortinet.com/ • Feedback
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Security Level Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Module Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Web-Based Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Roles, Services and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 6
Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
FIPS Approved Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Non-FIPS Approved Services . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Physical Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Operational Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Cryptographic Key Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Random Number Generation . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Entropy Token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Key Zeroization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Cryptographic Keys and Critical Security Parameters . . . . . . . . . . . . . 10
Key Archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Mitigation of Other Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
FIPS 140-2 Compliant Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Enabling FIPS mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Self-Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 2
http://docs.fortinet.com/ • Feedback
Overview
This document is a FIPS 140-2 Security Policy for Fortinet Incorporated’s FortiAnalyzer
5.2 firmware, which runs on the FortiAnalyzer family of security appliances. This policy
describes how the FortiAnalyzer 5.2 firmware (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 FIPS 140-2 Level 1 validation of the
Module.
This document contains the following sections:
• Introduction
• Security Level Summary
• Module Description
• Mitigation of Other Attacks
• FIPS 140-2 Compliant Operation
• Self-Tests
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 Module 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:
• Find general product information in the product section of the Fortinet corporate
website at http://www.fortinet.com/products.
• Find on-line product support for registered products in the technical support section of
the Fortinet corporate website at http://www.fortinet.com/support
• Find contact information for technical or sales related questions in the contacts section
of the Fortinet corporate website at http://www.fortinet.com/contact.
• Find security information and bulletins in the FortiGuard Center of the Fortinet
corporate website at http://www.fortinet.com/FortiGuardCenter.
Introduction
The FortiAnalyzer family of logging, analyzing, and reporting appliances securely
aggregate log data from Fortinet devices and other syslog-compatible devices. Using a
comprehensive suite of customizable reports, users can filter and review records,
including traffic, event, virus, attack, Web content, and email data.
A typical deployment architecture for a FortiAnalyzer appliance is shown in Figure 1.
Security Level Summary
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 3
http://docs.fortinet.com/ • Feedback
Figure 1: A typical FortiAnalyzer deployment architecture
Security Level Summary
The Module meets the overall requirements for a FIPS 140-2 Level 1 validation.
Internet
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
Module Description
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 4
http://docs.fortinet.com/ • Feedback
Module Description
The Module is a firmware operating system that runs exclusively on Fortinet’s
FortiAnalyzer product family. FortiAnalyzer units are PC-based, purpose built appliances.
The FortiAnalyzer appliances are multiple chip, standalone cryptographic modules
consisting of production grade components contained in a physically protected enclosure.
Figure 2: FortiAnalyzer Physical Cryptographic Boundary
Figure 3: FortiAnalyer Logical Cryptographic Boundary
For the purposes of FIPS 140-2 conformance testing, the Module was tested on a
FortiAnalyzer-200D unit and used a Fortinet entropy token (part number FTR-ENT-1) as
the entropy source.
The validated firmware version is FortiAnalyzer v5.2.4-build0738 150923(GA).
The Module can also be executed on any of the following FortiAnalyzer appliances and
remain vendor affirmed FIPS-compliant:
• FortiAnalyzer-100C
• FortiAnalyzer-1000C
• FortiAnalyzer-1000D
• FortiAnalyzer-2000B
• FortiAnalyzer-3000D
Firmware
Control
Input
Status
Output
Data
I/O
Module Description
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 5
http://docs.fortinet.com/ • Feedback
• FortiAnalyzer-3000E
• FortiAnalyzer-3500E
• FortiAnalyzer-3900E
• FortiAnalyzer-4000B
The CMVP makes no statement as to the correct operation of the Module or the security
strength of the generated keys when so ported if the specific operational environment is
not listed on the validation certificate.
Module Interfaces
The Module’s logical interfaces and physical ports are described in Table 2.
Web-Based Manager
The FortiAnalyzer web-based manager provides GUI based access to the Module and is
the primary tool for configuring the Module. The manager requires a web browser on the
management computer and an Ethernet connection between the FortiAnalyzer unit and
the management computer.
A web-browser that supports Transport Layer Security (TLS) 1.0 is required for remote
access to the web-based manager when the Module is operating in FIPS mode. HTTP
access to the web-based manager is not allowed in FIPS mode and is disabled.
Table 2: FortiAnalyzer logical interfaces 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
Module Description
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 6
http://docs.fortinet.com/ • Feedback
Figure 4: The FortiAnalyzer web-based manager
Command Line Interface
The FortiAnalyzer 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 FortiAnalyzer 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
mode). Telnet access to the CLI is not allowed in FIPS mode and is disabled.
Roles, Services and Authentication
Roles
When configured in FIPS mode, the Module provides the following roles:
• Crypto Officer
• 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 Crypto Officer operator accounts by giving
the account super user access permissions.
The Module provides a Network User role. Network users have read/write access to a
restricted set of the Module’s administrative services. Network User accounts are created
by Crypto Officers and do not have super user access permissions.
The Module does not provide a Maintenance role.
Module Description
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 7
http://docs.fortinet.com/ • Feedback
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 3: 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 Session
Authentication Keys, and HTTPS/TLS
Session Encryption Keys, DRBG Output,
DRBG Seed, DRBG Input String
show system status WE N/A
show FIPS mode enabled/disabled
(console/CLI only)
WE N/A
enable FIPS mode of operation
(console only)
WE Configuration Integrity Key
key zeroization (console/CLI only) WE All keys. (See “Key Zeroization” on
page 9)
execute factory reset (disable FIPS
mode, console/CLI only)
WE All keys except firmware update key,
configuration integrity key, configuration
backup key
execute FIPS on-demand self-tests
(console only)
E Configuration Integrity Key, Firmware
Integrity Key
add/delete operators and network
users
WE Crypto Officer Password,
Network User Password
set/reset operator and network user
passwords
WE Crypto Officer Password,
Network User Password
backup/restore configuration file WE Configuration Encryption Key,
Configuration Backup Key
read/set/delete/modify Module
configuration
WE N/A
execute firmware update E Firmware Update Key
read log data WE N/A
delete log data (console/CLI only) WE N/A
execute system diagnostics
(console/CLI only)
WE N/A
Module Description
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 8
http://docs.fortinet.com/ • Feedback
Table 4: Services available to Network Users
Non-FIPS Approved Services
The Module also provides the following non-FIPS approved services:
• Configuration backups using password protection
• LLTP and PPTP VPN
• All services in Table 3 & Table 4 are considered non-approved when using the
following algorithms:
• Non-compliant-strength Diffie-Hellman
• Non-compliant-strength RSA key wrapping
• DES
• HMAC-MD5
The above services shall not be used in the FIPS approved mode of operation.
Authentication
The Module implements identity based authentication. Operators must authenticate with a
user-id and password combination to access the Module remotely or locally via the
console. Remote operator authentication is done over HTTPS (TLS) or SSH. The
password entry feedback mechanism does not provide information that could be used to
guess or determine the authentication data.
The minimum password length is 8 characters when in FIPS mode (maximum password
length is 32 characters). The password may contain any combination of upper- and
lowercase letters, numbers, and printable symbols; allowing for 94 possible characters.
The odds of correctly guessing a password are 1/948
which is significantly lower than one
in a million. Recommended procedures to increase the password strength are explained in
“FIPS 140-2 Compliant Operation” on page 12.
Note that operator authentication over HTTPS/SSH and using the console is subject to a
limit of 3 failed authentication attempts in 1 minute; thus, the maximum number of
attempts in one minute is 3. Therefore, the probability of a success with multiple
consecutive attempts in a one-minute period is 3/948
which is less than 1/100,000.
Physical Security
The physical security for the Module is provided by the FortiAnalyzer hardware which uses
production grade components and an opaque enclosure.
Service/CSP Access Key/CSP
authenticate to Module WE Crypto Officer Password, Diffie-Hellman
Key, HTTP/TLS and SSH Server/Host
Keys, HTTPS/TLS and SSH Session
Authentication Keys, and HTTPS/TLS
Session Encryption Keys, DRBG
Output, DRBG Seed, DRBG Input String
show system status (console only) WE N/A
execute FIPS on-demand self-tests
(console only)
E Configuration Integrity Key, Firmware
Integrity Key
show FIPS mode enabled/disabled
(console/CLI only)
WE N/A
Module Description
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 9
http://docs.fortinet.com/ • Feedback
Operational Environment
The Module constitutes the entire firmware operating system for a FortiAnalyzer unit and
can only be installed and run on a FortiAnalyzer appliance. The Module provides a
proprietary and non-modifiable operating system and does not provide a programming
environment.
For the purposes of FIPS 140-2 conformance testing, the Module was tested on the
FortiAnalyzer-200D appliance.
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. There is no assurance of the minimum
strength of generated keys.
Entropy Token
The Module uses an entropy token (part number FTR-ENT-1 or part number FTR-ENT-2)
to seed the DRBG during the Module’s 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.
The default reseed period is once every 24 hours (1440 minutes). The token must be
installed to complete the boot process and to reseed of the DRBG. The entropy token is
responsible for loading a minimum of 256 bits of entropy.
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 flash memory and then power
cycling the FortiAnalyzer unit. To erase the flash memory, execute the following command
from the CLI:
execute erase-disk flash <erase-times>
Module Description
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 10
http://docs.fortinet.com/ • Feedback
Algorithms
Note that the SSH and TLS protocols have not been tested by the CMVP or CAVP.
Cryptographic Keys and Critical Security Parameters
The following table lists all of the cryptographic keys and critical security parameters used
by the Module. The following definitions apply to the table:
Table 5: FIPS Approved Algorithms
Algorithm NIST Certificate Number
CTR DRBG (NIST SP 800-90A) with 256-bits 930
Triple-DES in CBC mode with 192-bits 2002
AES in CBC mode (128-, 192-, 256-bits) 3595
SHA-1 2957
SHA-256 2957
HMAC SHA-1 2292
HMAC SHA-256 2292
RSA PKCS1
-Signature Generation: 2048 and 3072-bit
-Signature Verification: 1024, 2048 and 3072-bit
-For legacy use, the module supports 1024-bit RSA
keys and SHA-1 for signature verification
1849
CVL (SSH) - with TDES-192 bit-CBC, AES 128 bit-,
AES 256 bit -CBC (using SHA1, SHA256 and SHA512)
617
CVL (TLS) - TLS1.0/1.1 617
Table 6: FIPS Allowed Algorithms
Algorithm
RSA (key wrapping; key establishment methodology provides 112 or 128 bits of
encryption strength)
Diffie-Hellman (key agreement; key establishment methodology provides between 112
and 201 bits of encryption strength)
NDRNG (Entropy Token) - please refer to the “Entropy Token” on page 9 for additional
information.
Table 7: Non-FIPS Approved Algorithms
Algorithm
DES (disabled in FIPS mode)
MD5 (disabled in FIPS mode)
HMAC MD5 (disabled in FIPS mode)
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.
Key or CSP The key or CSP description.
Storage Where and how the keys are stored
Module Description
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 11
http://docs.fortinet.com/ • Feedback
Usage How the keys are used
Zeroization The key zeroization method
Table 8: Cryptographic Keys and Critical Security Parameters used in FIPS Mode
Key or CSP Generation Storage Usage Zeroization
Diffie-Hellman
Keys
Automatic SDRAM
Plaintext
Key agreement and key
establishment
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
NDRNG output
string
Automatic Flash RAM
Plain-text
Input string for the
entropy pool
By erasing the flash
memory and power
cycling the FortiManager
unit
DRBG seed Automatic Flash RAM
Plain-text
Seed used by the
DRBG (output from
NDRNG)
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
DRBG output Automatic Flash RAM
Plain-text
Random numbers used
in cryptographic
algorithms
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
DRBG v and key
values
Automatic Flash Ram
Plain-text
Internal state values for
the DRBG
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
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)
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
Firmware
Integrity Key
Preconfigured Flash RAM
Plain-text
Verification of firmware
integrity in the firmware
integrity test using RSA
public key (firmware
integrity test)
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
HTTPS/TLS
Server/Host Key
Preconfigured Flash RAM
Plain-text
RSA private key used in
the HTTPS/TLS
protocols (key
establishment)
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
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 FortiAnalyzer
unit
HTTPS/TLS
Session
Encryption Key
Automatic SDRAM
Plain-text
AES or Triple-DES key
used for HTTPS/TLS
session encryption
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
SSH
Server/Host Key
Preconfigured Flash RAM
Plain-text
RSA private key used in
the SSH protocol (key
establishment)
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
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 FortiAnalyzer
unit
SSH Session
Encryption Key
Automatic SDRAM
Plain-text
AES or Triple-DES key
used for SSH session
encryption
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
Mitigation of Other Attacks
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 12
http://docs.fortinet.com/ • Feedback
Note: 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.
Key Archiving
The Module supports key archiving to a 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 Configuration Encryption Key or stored as a keyed
hash using HMAC SHA-1 using the Configuration Backup Key.
Mitigation of Other Attacks
The Module does not mitigate against any other attacks.
FIPS 140-2 Compliant Operation
FIPS 140-2 compliant operation requires both that you use the Module in its FIPS mode of
operation and that you follow secure procedures for installation and operation of the
FortiAnalyzer unit. You must ensure that:
• The FortiAnalyzer unit is configured in the FIPS mode of operation.
• The FortiAnalyzer unit is installed in a secure physical location.
• Physical access to the FortiAnalyzer unit is restricted to authorized operators.
• A USB entropy token is used to seed the DRBG.
• The token remains in the USB port during operation
Crypto Officer
Password
Manual Flash RAM
SHA-1
hash
Used to authenticate
operator access to the
Module
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
Configuration
Integrity Key
Preconfigured Flash RAM
Plain-text
HMAC SHA-256 hash
used for configuration
integrity test
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
Configuration
Encryption Key
Automatic Flash RAM
Plain-text
AES key used to
encrypt CSPs on the
flash RAM 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 FortiAnalyzer
unit
Configuration
Backup Key
Automatic 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 FortiAnalyzer
unit
Network User
Password
Manual Flash RAM
SHA-1
hash
Used to authenticate
network access to the
Module
By erasing the flash
memory and power
cycling the FortiAnalyzer
unit
Table 8: Cryptographic Keys and Critical Security Parameters used in FIPS Mode
Key or CSP Generation Storage Usage Zeroization
Self-Tests
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 13
http://docs.fortinet.com/ • Feedback
• Administrative passwords are at least 8 characters long.
• Administrative passwords are changed regularly.
• Administrator account passwords must have the following characteristics:
• One (or more) of the characters must be capitalized
• One (or more) of the characters must be numeric
• One (or more) of the characters must be non-alphanumeric (e.g. punctuation mark)
• Administration of the Module is permitted using only validated administrative methods.
These are:
• Console connection
• Web-based manager via HTTPS
• Command line interface (CLI) access via SSH
• Diffie-Hellman groups of less than 2048 bits are not used.
• Client side RSA certificates must use 2048 bit or greater key sizes.
• Only approved and allowed algorithms are used (see “Algorithms” on page 10).
The Module can be used in either of its two operation modes: NAT/Route or Transparent.
NAT/Route mode applies security features between two or more different networks (for
example, between a private network and the Internet). Transparent mode applies security
features at any point in a network. The current operation mode is displayed on the web-
based manager Status page and in the output of the get system status CLI
command.
Enabling FIPS 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
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 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 mode by
executing the following command from the CLI:
get system status
If the Module is running in FIPS mode, the system status output will display the line:
FIPS mode: enable
Note: Enabling/disabling the FIPS mode of operation will automatically invoke the key zeroization
service. The key zeroization is performed immediately after FIPS mode is enabled/disabled.
Additionally, certain non-FIPS approved services may still be available, but they shall not be used in
the FIPS approved mode of operation.
Self-Tests
The Module executes the following self-tests during startup and initialization:
Self-Tests
FortiAnalyzer 5.2 FIPS 140-2 Security Policy
05-524-261848-20151006 14
http://docs.fortinet.com/ • Feedback
• Firmware integrity test using RSA signatures
• Configuration integrity test using HMAC SHA-1
• Triple-DES, CBC mode, encrypt known answer test
• Triple-DES, CBC mode, decrypt known answer test
• AES, CBC mode, encrypt known answer test
• AES, CBC mode, decrypt known answer test
• HMAC SHA-1 known answer test
• SHA-1 known answer test (test as part of HMAC SHA-1 known answer test)
• HMAC SHA-256 known answer test
• SHA-256 known answer test (test as part of HMAC SHA-256 known answer test)
• RSA signature generation known answer test
• RSA signature verification known answer test
• DRBG known answer 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 Module executes the following conditional tests when the related service is invoked:
• Continuous TRNG test
• Continuous NDRNG test
• Continuous DRBG test
• RSA pairwise consistency test
• Configuration integrity test using HMAC SHA-256
• Firmware load test using RSA signatures
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.