FIPS 140-2 Security Policy FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 blades CONSOLE USB 1 2 3 4 5 6 7 8 5 PWR ACC STA IPM CONSOLE USB 1 2 3 4 5 6 7 8 4 PWR ACC STA IPM CONSOLE USB 1 2 3 4 5 6 7 8 3 PWR ACC STA IPM USB 1 2 3 4 5 6 7 8 2 CONSOLE PWR ACC STA IPM POWER USB 1 2 3 4 5 6 7 8 1 PWR ACC CONSOLE STA IPM ShMC Critical ShMC Major Hot Swap 1 Status 2 Minor Alarm Alarm Reset Console Ethernet FIPS 140-2 Security Policy - FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 blades Document Version: 1.8 Publication Date: June 7, 2007 Description: Documents FIPS 140-2 Security Policy issues, compliancy and requirements for FIPS compliant operation. Hardware Models: FortiGate-5001SX (P4CF76) FortiGate-5001FA2 (C5FA26) FortiGate-5050 (C4QP38) Firmware Version: FortiOS 3.0, build8317, 061121 www.fortinet.com FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 blades FIPS 140-2 Security Policy v1.8 June 7, 2007 01-00000-0386-20061206 This document may be copied without Fortinet Incorporated's explicit permission provided that it is copied in it's entirety without any modification. Trademarks Dynamic Threat Prevention System (DTPS), APSecure, FortiASIC, FortiBIOS, FortiBridge, FortiClient, FortiGate, FortiGate Unified Threat Management System, FortiGuard, FortiGuard-Antispam, FortiGuard- Antivirus, FortiGuard-Intrusion, FortiGuard-Web, FortiLog, FortiAnalyzer, FortiManager, Fortinet, FortiOS, FortiPartner, FortiProtect, FortiReporter, FortiResponse, FortiShield, FortiVoIP, and FortiWiFi are trademarks of Fortinet, Inc. in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Regulatory compliance FCC Class A Part 15 CSA/CUS Caution: If you install a battery that is not the correct type, it could ! explode. Dispose of used batteries according to local regulations. Contents Contents References .................................................................................................... 5 Security Level Summary ................................................................................... 5 FIPS-CC Mode of Operation.............................................................................. 6 FortiGate Module Description .......................................................................... 6 Cryptographic Module Description ................................................................ 7 Cryptographic Module Ports and Interfaces .................................................. 8 Roles, Services and Authentication ............................................................ 14 Physical Security......................................................................................... 17 Operational Environment ............................................................................ 18 Cryptographic Key Management................................................................. 18 Alternating Bypass Feature ......................................................................... 21 Key Archiving .............................................................................................. 21 Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC) ... 21 Mitigation of Other Attacks............................................................................. 22 NIPS Signature Protection .......................................................................... 22 NIPS Attack Protection................................................................................ 23 Antivirus Protection ..................................................................................... 23 Antispam Protection .................................................................................... 23 Web Filtering ............................................................................................... 24 FortiGuard Services .................................................................................... 24 FIPS 140-2 Compliant Operation .................................................................... 24 Overview of FIPS 140-2 compliant operation.............................................. 25 Initial configuration of the FortiGate unit ..................................................... 25 Enabling FIPS-CC mode ............................................................................. 27 Self-Tests .................................................................................................... 29 Effects of FIPS-CC compliant mode ........................................................... 30 Remote access requirements ..................................................................... 31 Disabling FIPS-CC mode ............................................................................ 32 Administration ................................................................................................. 32 Administrator roles ...................................................................................... 33 Administrator accounts and profiles ............................................................ 33 Enabling multiple virtual domain configuration ............................................ 33 Disclaimer access banner ........................................................................... 34 Using custom administrator access keys (certificates) ............................... 34 Configuration backup .................................................................................. 35 FortiGate-5050 Chassis with FortiGate-5001SX, 5001FA2 and 5005FA2 Blades - FIPS 140-2 Security Policy 01-00000-0382-20061201 3 Contents Logging ............................................................................................................ 35 Default log settings ..................................................................................... 36 Excluding specific logs................................................................................ 37 Viewing log messages from the web-based manager ................................ 38 Viewing log messages from the CLI ........................................................... 38 Backing up log messages ........................................................................... 40 Viewing log file information ......................................................................... 41 Deleting filtered log messages .................................................................... 41 Deleting rolled log files................................................................................ 41 Alarms .............................................................................................................. 42 Configuring alarms...................................................................................... 42 Alarm notifications....................................................................................... 44 Acknowledging alarms ................................................................................ 44 Clearing Error mode........................................................................................ 44 Non-FIPS Approved Services......................................................................... 45 FortiGate-5050 Chassis with FortiGate-5001SX, 5001FA2 and 5005FA2 Blades - FIPS 140-2 Security Policy 4 01-00000-0382-20061201 References This document is a FIPS 140-2 Security Policy for Fortinet Incorporated's FortiGate-5050 with the FortiGate-5001SX and 5001FA2 blade based Multi- Threat Security Systems. This policy describes how the FortiGate-5001SX and 5001FA2 blades, when installed in the FortiGate-5050 chassis (hereafter referred to in combination as the `module' or `modules'), meet the FIPS 140-2 security requirements and how to operate the modules in a FIPS compliant manner. This policy was created as part of the Level 2 FIPS 140-2 validation of the modules. This document contains the following sections: · Security Level Summary · FIPS-CC Mode of Operation · FortiGate Module Description · Mitigation of Other Attacks · FIPS 140-2 Compliant Operation · Administration · Logging · Alarms · Clearing Error mode · Non-FIPS Approved Services 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/cryptval/. References This policy deals specifically with operation and implementation of the FortiGate modules in the technical terms of the FIPS 140-2 standard and the associated validation program. Additional information on the FortiGate modules and the entire FortiGate 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. Security Level Summary The modules, consisting of the Fortinet FortiGate-5050 chassis with the FortiGate-5001SX and 5001FA2 blade based Multi-Threat Security Systems, meet the overall requirements for a Level 2 FIPS 140-2 validation. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 5 References . Table 1: Summary of FIPS Security Requirements and Compliance Levels Security Requirement Compliance Level Cryptographic Module Specification 2 Cryptographic Module Ports and Interfaces 3 Roles, Services and Authentication 3 Finite State Model 2 Physical Security 2 Operational Environment N/A Cryptographic Key Management 3 EMI/EMC 2 Self-Tests 2 Design Assurance 3 Mitigation of Other Attacks 2 FIPS-CC Mode of Operation To operate the FortiGate modules in a FIPS compliant manner, the modules must be configured to run in the FIPS-CC mode of operation. Enabling the FIPS-CC mode of operation sets default values, disables some features and performs additional configuration procedures to meet the following requirements: · FIPS 140-2 Level 2 as specified in Table 1. · US Government Firewall Protection Profile for Medium Robustness Environments, Version 1.0, October 28, 2003 See "FIPS 140-2 Compliant Operation" on page 23 for complete details on configuring the modules in the FIPS-CC mode of operation. FortiGate Module Description The FortiGate family spans the full range of network environments, from SOHO to service provider, offering cost effective systems for any size of application. They detect and eliminate the most damaging, content-based threats from email and Web traffic such as viruses, worms, intrusions, inappropriate Web content and more in real time -- without degrading network performance. In addition to providing application level firewall protection, the FortiGate modules deliver a full range of network-level services -- VPN, intrusion prevention, web filtering, antivirus, antispam and traffic shaping -- in dedicated, easily managed platforms. All FortiGate Multi-Layered Security Systems employ Fortinet's unique FortiASICTM content processing chip and the powerful, secure, FortiOSTM operating system to achieve breakthrough price/performance. The unique, ASIC- based architecture analyzes content and behavior in real time, enabling key applications to be deployed right at the network edge, where they are most effective at protecting enterprise networks. As the only systems in the world that are certified by ICSA for firewall, IPSec VPN, SSL VPN, antivirus, and intrusion FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 6 01-00000-0382-20061201 Cryptographic Module Description prevention functionality, the FortiGate modules deliver the highest level of security available. They provide a critical layer of real-time, network-based antivirus protection that complements host-based antivirus software and supports "defense-in-depth" strategies without compromising performance or cost. They can be easily configured to provide antivirus protection, antispam protection and content filtering in conjunction with existing firewall, VPN, and related devices, or as complete network protection systems. FortiGate modules support the IPSec industry standard for VPN, allowing VPNs to be configured between a FortiGate module and any client or gateway/firewall that supports IPSec VPN. FortiGate modules also provide SSL VPN services. This section contains the following information: · Cryptographic Module Description · Cryptographic Module Ports and Interfaces · Roles, Services and Authentication · Physical Security · Operational Environment · Cryptographic Key Management · Alternating Bypass Feature · Key Archiving · Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC) Cryptographic Module Description The FortiGate modules (the blades and chassis in combination) are multiple chip, standalone cryptographic devices consisting of production grade components contained in a physically protected enclosure in accordance with FIPS 140-2 Level 2 requirements. The blades run the FortiOS firmware, perform all of the cryptographic functions and provide the input/output interfaces. The chassis provide power, cooling and physical protection for the modules as a whole. The chassis do not run FortiOS firmware. The modules are Internet devices that provide integrated firewall, VPN, antivirus, antispam, intrusion prevention, content filtering and traffic shaping capabilities. This FIPS 140-2 Security Policy specifically covers the firewall, IPSec and SSL- VPN capabilities of the modules. The antivirus, antispam, intrusion prevention, content filtering and traffic shaping capabilities of the modules can be used without compromising the FIPS approved mode of operation. The blades have a similar appearance and perform the same functions, but have different numbers and types of network interfaces in order to support different network configurations: · The FortiGate-5001SX has 8 Gigabit network interfaces with a status LED for each interface (4 Gigabit SFP, 4 10/100/1000 BaseT) · The FortiGate-5001FA2 has 8 Gigabit network interfaces with a status LED for each interface (2 Accelerated Gigabit SFP, 2 Gigabit SFP, 4 10/100/1000 BaseT) The blades each have two x86 compatible CPUs. The blades are ATCA compliant. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 7 Cryptographic Module Ports and Interfaces The blades and chassis do not have hard drives. The FortiGate-5050 has a hot Swapable fan unit that contains 2 ventilation fans on the right side of the chassis The FortiGate-5050 includes two DC power connectors. The FortiGate-5050 chassis uses an external DC power sources. The FortiGate-5050 chassis include removable Shelf Manager panels. The Shelf Manager provides management functions for the chassis only. The FortiGate-5050 chassis includes slots for rear-panel blades. The rear-panel slots are not used in the validated configuration. Cryptographic Module Ports and Interfaces FortiGate-5001SX Blade Figure 1: FortiGate-5001SX Front Panel l Flash Disk Module Access Link/Traffic Position Power USB Status CONSOLE USB 1 2 3 4 5 6 7 8 PWR ACC STA IPM Mounting Extraction Extraction Mounting Knot Lever Lever Knot Locking Console 1234 5678 Screw Port SFP Gigabit fiber Gigabit Copper or copper Table 2: FortiGate-5001SX Status LEDs LED State Description PWR Green The Fortinet module is powered on. ACC Off or The ACC LED flashes red when the Fortinet module Flashing accesses the FortiOS flash disk. The FortiOS flash disk red stores the current FortiOS firmware build and configuration files. The system accesses the flash disk when starting up, during a firmware upgrade, or when an administrator is using the CLI or GUI to change the FortiOS configuration. Under normal operating conditions this LED flashes occasionally, but is mostly off. STA Green Normal operation. Red The Fortinet is starting or a fault condition exists. IPM Blue The Fortinet is ready to be hot-swapped (removed from the chassis). If the IPM light is blue and no other LEDs are lit the Fortinet module has lost power, possibly because of a loose or incorrectly aligned left extraction lever. Flashing The Fortinet is changing from hot swap to running mode Blue or from running mode to hot swap. Off Normal operation. The Fortinet module is in contact with the chassis backplane. 1, 2, 3, 4 Green The correct cable is connected to the gigabit SFP interface. Flashing Network activity at the gigabit SFP interface. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 8 01-00000-0382-20061201 Cryptographic Module Ports and Interfaces Table 2: FortiGate-5001SX Status LEDs LED State Description 5, 6, Link Green The correct cable is inserted into this interface and the 7, 8 LED connected equipment has power. Flashing Network activity at this interface. Speed Green The interface is connected at 1000 Mbps. LED Amber The interface is connected at 100 Mbps. Unlit The interface is connected at 10 Mbps. Table 3: FortiGate-5001SX Front Panel Connectors and Ports Connector Type Speed Supported Logical Description Interfaces 1, 2, 3, 4 LC-SFP 1000BaseSX Data input, data Gigabit SFP interfaces output, control input that can accept fiber or and status output copper gigabit transceivers. These interfaces only operate at 1000Mbps. 5, 6, 7, 8 RJ-45 10/100/1000 Data input, data Copper gigabit BaseT output, control input connection to and status output 10/100/1000Base-T copper networks. CONSOLE DB-9 9600 bps Control input, status Optional connection to output the management computer. Provides access to the command line interface (CLI). USB USB N/A Key loading and Optional connection archiving for FortiUSB token. FortiGate-5001FA2 Blade Figure 2: FortiGate-5001FA2 Front Panel Flash Disk Link/Traffic Module Access Position Power USB Status USB 1 2 3 4 5 6 7 8 CONSOLE PWR ACC STA IPM Mounting Extraction 3 4 SPF Gigabit Extraction Mounting Knot Lever Fiber or Copper Lever Knot Console 1 2 SPF Gigabit 5678 Port Fiber or Copper Gigabit Copper Accelerated Table 4: FortiGate-5001SX Status LEDs LED State Description PWR Green The FortiGate-50012FA2 module is powered on. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 9 Cryptographic Module Ports and Interfaces Table 4: FortiGate-5001SX Status LEDs LED State Description ACC Off or The ACC LED flashes red when the Fortinet module accesses Flashing the FortiOS flash disk. The FortiOS flash disk stores the red current FortiOS firmware build and configuration files. The system accesses the flash disk when starting up, during a firmware upgrade, or when an administrator is using the CLI or GUI to change the FortiOS configuration. Under normal operating conditions this LED flashes occasionally, but is mostly off. STA Green Normal operation. Red The Fortinet is booting or a fault condition exists. IPM Blue The Fortinet is ready to be hot-swapped (removed from the chassis). If the IPM light is blue and no other LEDs are lit the Fortinet module has lost power, possibly because of a loose or incorrectly aligned left extraction lever. Flashing The Fortinet is changing from hot swap to running mode or Blue from running mode to hot swap. Off Normal operation. The Fortinet module is in contact with the chassis backplane. 1, 2, 3, 4 Green The correct cable is connected to the gigabit SFP interface. Flashing Network activity at the gigabit SFP interface. 5, 6, Link Green The correct cable is inserted into this interface and the 7, 8 LED connected equipment has power. Flashing Network activity at this interface. Speed Green The interface is connected at 1000 Mbps. LED Amber The interface is connected at 100 Mbps. Unlit The interface is connected at 10 Mbps. Table 5: FortiGate-5001FA2 Front Panel Connectors and Ports Connector Type Speed Supported Logical Description Interfaces 1, 2 LC-SFP 1000BaseSX Data input, data Accelerated gigabit SFP output, control input interfaces that can and status output accept fiber or copper gigabit transceivers. These interfaces only operate at 1000Mbps. 3, 4 LC-SFP 1000BaseSX Data input, data Gigabit SFP interfaces output, control input that can accept fiber or and status output copper gigabit transceivers. These interfaces only operate at 1000Mbps. 5, 6, 7, 8 RJ-45 10/100/1000 Data input, data Copper gigabit BaseT output, control input connection to and status output 10/100/1000Base-T copper networks. CONSOLE RJ-45 9600 bps Control input, status Optional connection to output the management computer. Provides access to the command line interface (CLI). USB USB N/A Key loading and Optional connection for archiving FortiUSB token. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 10 01-00000-0382-20061201 Cryptographic Module Ports and Interfaces FortiGate-5050 Chassis Figure 3: FortiGate-5050 Front Panel CONSOLE USB 1 2 3 4 5 6 7 8 5 PWR ACC STA IPM CONSOLE USB 1 2 3 4 5 6 7 8 4 PWR ACC STA IPM CONSOLE USB 1 2 3 4 5 6 7 8 3 PWR ACC STA IPM Hot-swap 2 PWR ACC CONSOLE USB 1 2 3 4 5 6 7 8 STA IPM POWER cooling fa USB Power LE 1 2 3 4 5 6 7 8 1 PWR ACC CONSOLE STA IPM ShMC Critical ShMC Major Hot Swap 1 Status 2 Minor Alarm Alarm Reset Console Ethernet FortiGate-5050 ESD socket Shelf Manager Figure 4: FortiGate-5050 Rear Panel 5 4 3 2 RTN RTN 1 INPUT A INPUT B Ground -48V DC VOLTAGE RANGE -48V TO -58V RTN (-DC IN) -48V DC VOLTAGE RANGE -48V TO -58V RTN (-DC IN) Connector GND 25 25 AMP AMP (green) -48V to -58V -48V to -58V Positive (-DC in) Positive (-DC in) (RTN) (black) (RTN) (black) Power (red) (red) wire fixture ESD socket DC Power DC Power Input A Input B Web-Based Manager The FortiGate web-based manager provides GUI based access to the modules 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 FortiGate module and the management computer. The web-based manager uses Transport Layer Security (TLS) for connection security in FIPS-CC mode. HTTP access to the web-based manager is not allowed in FIPS-CC mode and is disabled. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 11 Cryptographic Module Ports and Interfaces The web browser is not part of the validated module boundaries. Figure 5: The FortiGate web-based manager Command Line Interface The FortiGate Command Line Interface (CLI) is a full-featured, text based management tool for the FortiGate modules. The CLI provides access to all of the possible services and configuration options in the modules. The CLI uses a console connection or a network (Ethernet) connection between the FortiGate module 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 is required. A FIPS 140-2 validated SSH client is recommended for SSH access to the CLI when the modules are operating in FIPS-CC mode. Telnet access to the CLI is not allowed in FIPS-CC mode and is disabled. The Telnet or SSH client is not part of the validated module boundaries. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 12 01-00000-0382-20061201 Roles, Services and Authentication Control Panel and LCD The front panel of the modules provides a control panel and an LCD. The control panel has 4 buttons. The buttons and LCD can be used to configure basic parameters such as the network interface addresses, and the default gateway address. To access advanced services and configurations the operator must use the web-based manager or the CLI. Use of the control panel is disabled in the FIPS-CC mode of operation. Roles, Services and Authentication Roles When configured in FIPS-CC mode, the modules provide three roles for Crypto Officers (hereafter referred to as operators): Security Administrator, Crypto Administrator and Audit Administrator. These roles, or combinations of these roles, are assumed by an operator after authenticating to the module remotely or through the console connection using a username/password combination. An operator assuming the Security Administrator role has read/write access to all of the administrative functions and services of the module, including resetting or shutting down the module. An operator with the Security Administrator role can also create accounts for additional operators and assign roles to those operators. However, the Security Administrator role has read only access to crypto and audit related functions and services. An operator assuming the Crypto Administrator role has read/write access to crypto related functions and services and read only access to all other functions and services. An operator assuming the Audit Administrator role has read/write access to audit related functions and services and read only access to all other functions and services. Operators can be assigned more than one role. An operator that assumes all three administrative roles has complete administrative access to the module. Multiple operator accounts can be created. Operator accounts are differentiated by the username during authentication. More than one operator can be connected to the modules at any given time, however each operator session is authenticated separately. The modules 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. Refer to the next section on Services for detailed information on what functions and services each role has access to. 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, the types of access for each role and the CSPs they affect. The role names are abbreviated as follows: FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 13 Roles, Services and Authentication Security Administrator SA Crypto Administrator CA Audit Administrator AA Network User NU Table 6: FIPS approved services available by role via the CLI Service/CSP SA CA AA authenticate to module E E E show system status R R R show FIPS mode enabled/disabled R R R enable/disable FIPS mode of WE N/A N/A operation set/reset operator passwords WE N/A N/A zeroize keys (execute factory reset) E N/A N/A execute FIPS-CC on-demand self- E N/A N/A tests add/delete operators RWE N/A N/A set/reset own password WE N/A N/A execute firmware download E N/A N/A execute system reboot E N/A N/A execute system shutdown E N/A N/A execute system diagnostics E N/A N/A change system time WE N/A N/A read/set/delete/modify RWE N/A N/A system/network configuration read/set/delete/modify firewall RWE N/A N/A policies. enable/disable alternating bypass mode read/set/delete/modify AV RWE N/A N/A configuration read/set/delete/modify AS RWE N/A N/A configuration read/set/delete/modify Web Filter RWE N/A N/A configuration read/set/delete/modify IM/P2P RWE N/A N/A configuration read/set/delete/modify VPN R RWE N/A configuration read/set/delete/modify IPS RWE N/A N/A configuration read/set/delete/modify R N/A RWE logging/reporting configuration manual AV/IPS signature E N/A N/A download/update FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 14 01-00000-0382-20061201 Roles, Services and Authentication Table 7: FIPS approved services available by role via the web-manager Service/CSP SA CA AA authenticate to module E E E show system status R R R zeroize keys (execute factory reset) E N/A N/A add/delete operators RWE N/A N/A set/reset operator passwords WE N/A N/A execute firmware download E N/A N/A execute system reboot E N/A N/A execute system shutdown E N/A N/A create and download backup WE N/A N/A configuration file restore system configuration from RWE N/A N/A backup change system time WE N/A N/A set/reset own password WE N/A N/A read/set/delete/modify RWE R R system/network configuration read/set/delete/modify firewall RWE R R policies. enable/disable alternating bypass mode read/set/delete/modify AV RWE R R configuration read/set/delete/modify AS RWE R R configuration read/set/delete/modify Web Filter RWE R R configuration read/set/delete/modify IM/P2P RWE R R configuration read/set/delete/modify VPN R RWE R configuration read/set/delete/modify NIPS RWE R R configuration read/set/delete/modify R R RWE logging/reporting configuration manual AV/IPS signature E N/A N/A download/update Table 8: VPN Cryptographic Services available to Network Users Service/CSP NU authenticate to module RWE encrypt/decrypt controlled by firewall E policies Authentication Operators must authenticate with a user-id and password combination to access the module remotely or via the console. Remote operator authentication is done over HTTPS or SSH. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 15 Physical Security By default, Network User access to the modules is based on authentication by IP address for FQDN. Network Users can optionally be forced to authenticate to the module using a username/password combination to enable use of the encrypt/decrypt or bypass services. Network User authentication is done over HTTPS and does not allow access to the modules for administrative purposes. For Network Users invoking the SSL-VPN encrypt/decrypt services, the module supports authentication with a user-id/password combination or an RSA certificate. The minimum password length is 8 characters when in FIPS-CC mode. Using a strong password policy, where operator or network user passwords are at least 8 characters in length and use a mix of alphanumeric (printable) characters from the ASCII character set, the odds of guessing a password are 1 in 968. For Network Users invoking the IPSec encrypt/decrypt services, the module acts on behalf of the Network User and negotiates a VPN connection with a remote module. The strength of authentication for IPSec services is based on the authentication method defined in the specific firewall policy: either manual key (manually entered electronic key), pre-shared key or RSA certificate. The minimum permitted IPSec manual key size in FIPS-CC mode is 128 bits, pre- shared key authentication uses Diffie-Hellman with a minimum modulus of 768 bits and certificate based authentication uses 1024 bit keys. Therefore the odds of guessing an IPSec authentication key are at least 1 in 2128. Note that a minimum modulus of 1024 bits must be used in order to operate the modules in a FIPS compliant manner. Physical Security The modules meet FIPS 140-2 Security Level 2 requirements by using production grade components with passivation coating (where applicable) and an opaque, sealed enclosure. Access to the enclosure is restricted through the use of tamper- evident seals to secure the overall enclosure. The modules, consisting of the FortiGate-5050 chassis with the FortiGate-5001SX and 5001FA2 blades, use multiple seals to secure the external enclosure. Each blade or blank faceplate must be sealed. The seals are blue wax/plastic with white lettering that reads "Fortinet Inc. Security Seal". The tamper seals are not applied at the factory prior to shipping. The required number of seals to secure each unit are included in the product packaging. It is the responsibility of the customer to apply the seals before use to ensure full FIPS compliance. Once the seals have been applied, the customer must develop an inspection schedule to verify that the external enclosure of the modules and the tamper seals have not been damaged or tampered with in any way. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 16 01-00000-0382-20061201 Operational Environment Figure 6: FortiGate-5050 front panel tamper seal placement CONSOLE USB 1 2 3 4 5 6 7 8 5 Security Seal Fortinet Inc. PWR ACC STA IPM CONSOLE USB 1 2 3 4 5 6 7 8 4 PWR ACC STA IPM CONSOLE USB 1 2 3 4 5 6 7 8 Security Seal 3 Fortinet Inc. PWR ACC STA IPM USB 1 2 3 4 5 6 7 8 CONSOLE 2 PWR ACC STA IPM POWER USB 1 2 3 4 5 6 7 8 1 Security Seal CONSOLE Fortinet Inc. PWR ACC STA IPM Fortinet Inc. Fortinet Inc. Security Seal Security Seal ShMC ShMC Critical Major Hot Swap 2 1 Status Minor Alarm Alarm Reset Console Ethernet Figure 7: FortiGate-5050 rear panel tamper seal placement Fortinet Inc. Security Seal 5 4 3 2 1 Fortinet Inc. INPUT A Security Seal INPUT B DC VOLTAGE RANGE DC VOLTAGE RANGE -48V TO -58V -48V TO -58V RTN (-DC IN) RTN (-DC IN) 25 25 AMP AMP Operational Environment This section is not applicable to the modules. The modules utilize a firmware based, proprietary and non-modifiable operating system that does not provide a programming environment. Cryptographic Key Management Random Number Generation The modules use a firmware based, deterministic random number generator that conforms to ANSI X9.31 Appendix A.2.4. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 17 Cryptographic Key Management Key Zeroization Key zeroization occurs when the operator executes a factory reset via the web- manager, CLI or console and when enabling or disabling the FIPS-CC mode of operation via the console. All keys and critical security parameters are zeroized. See Table 11 on page 18 for details. Algorithms Table 9: FIPS Approved or Allowed Algorithms Algorithm NIST Certificate Number RNG (ANSI X9.31 Appendix A) 251 Triple-DES 486, 487, 490 AES 471, 472, 476 SHA-1 539, 540, 544 HMAC SHA-1 229, 228, 233 Diffie-Hellman (key agreement; key establishment methodology provides between 80 and 201 bits of encryption strength; non- compliant less than 80-bits of encryption strength) RSA ANSI X9.31 (key generation, signature 193 generation/verification) RSA PKCS1 (digital signature creation and 193 verification, key wrapping; key establishment method provides 110 bits of encryption strength - only 2048 bit certificates are supported) Table 10: Non-FIPS Approved Algorithms Algorithm DES (disabled in FIPS mode) MD5 (disabled in FIPS mode) HMAC MD5 (disabled in FIPS mode) 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 table: Key or CSP The key or CSP description. Storage Where and how the keys are stored Usage How the keys are used Table 11: FIPS Approved Cryptographic Keys and Critical Security Parameters Key or CSP Storage Usage Diffie-Hellman Keys SDRAM Key agreement and key establishment Plaintext IPSEC Encryption Key Flash RAM VPN traffic encryption/decryption using AES encrypted Triple-DES or AES FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 18 01-00000-0382-20061201 Cryptographic Key Management Table 11: FIPS Approved Cryptographic Keys and Critical Security Parameters Key or CSP Storage Usage IPSEC Authentication Key Flash RAM Peer-to-Peer authentication using AES encrypted manually entered electronic keys IPSEC Session Encryption SDRAM VPN traffic encryption/decryption using Key Plain-text Triple-DES or AES IKE Pre-Shared Key Flash RAM Used to generate IKE session AES encrypted encryption key and authentication key IKE Authentication Key SDRAM IKE peer-to-peer authentication using Plain-text HMAC SHA-1 (SKEYID_A) IKE Key Generation Key SDRAM IPSEC SA keying material (SKEYID_D) Plain-text IKE Session Encryption Key SDRAM Encryption of IKE peer-to-peer key Plain-text negotiation using Triple-DES or AES (SKEYID_E) IKE RSA Key Flash Ram IKE peer-to-peer authentication using Plain text X.509 certificates HA Password Flash RAM Used to authenticate FortiGate units in SHA-1 hash an HA cluster HA Encryption Key Flash RAM Encryption of traffic between modules in AES encrypted an HA cluster using AES Firmware Integrity Key Flash RAM Verify integrity of firmware during self- Plain-text test using HMAC SHA-1 VPN Bypass Key Flash RAM Verify integrity of VPN table during self- Plain-text tests (bypass test) using HMAC SHA-1 ANSI X9.31 RNG AES Key Flash RAM Static AES key used with ANSI X9.31 Plain-text RNG Firmware Download Public Flash RAM Verification of firmware integrity for Key Plain-text download of new firmware versions using RSA public key TLS/SSH/SSL-VPN Flash RAM Remote Web manager and CLI Server/Host Key Plain-text authentication using HMAC SHA-1. Also used for encrypting TLS session key using RSA method. TLS Session Key SDRAM Remote Web manager session Plain-text encryption and authentication using AES or Triple-DES SSH Session Key SDRAM Remote CLI session encryption and Plain-text authentication using AES or Triple-DES SSL-VPN Session Key SDRAM SSL-VPN session encryption and Plain-text authentication using AES or Triple-DES Operator Username Flash RAM Used during operator authentication to Plain-text identify and assign roles to operators Operator Password Flash RAM Used to authenticate operator access to SHA-1 hash the module FIPS-CC Mode Key Flash RAM AES key used to encrypt key CSPs AES encrypted stored on flash card Backup Configuration Flash RAM Used as seed to generate configuration Password AES encrypted file encryption key Configuration File Encryption Flash RAM AES key used to encrypt backup key AES encrypted configuration file FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 19 Alternating Bypass Feature Alternating Bypass Feature The primary cryptographic function of the FortiGate modules is as a firewall and VPN device. Encrypt/decrypt operations are performed on outgoing/incoming traffic based on firewall policies. Firewall policies with an action of IPSec or SSL- VPN mean that the firewall is functioning as a VPN start/end point for the specified source/destination addresses and will encrypt/decrypt traffic accordingly. Firewall policies with an action of allow mean that the firewall is accepting/sending plaintext data for the specified source/destination addresses. The FortiGate implements an alternating bypass feature that is based on the firewall policies. A firewall policy with an action of accept is means that the module operating in a bypass state for that policy. A firewall policy with an action of IPSec or SSL-VPN means that the module is operating in a non-bypass state for that policy. Two independent actions must be taken by an operator to create bypass firewall policies: the operator must create the bypass policy and then specifically enable that policy. Key Archiving The module supports key archiving to a management computer or USB token as part of a module configuration file backup. Operator entered keys are archived as part of the module configuration file. By default, the configuration file is stored in plain text, but any keys in the configuration file keys are AES encrypted. The modules also support encrypting the entire configuration file using AES. Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC) The modules comply with EMI/EMC requirements as specified by Part 15, Subpart B, of the FCC rules. The following table lists the specific lab and FCC report information for the modules. Table 12: FCC Report Information Module Lab Information FCC Report Number FG-5050 Compliance Certification Services 05U3590-1 Inc. 561F Monterey Road. Morgan Hill, CA, 95037, USA (408) 463-0885 Mitigation of Other Attacks The FortiGate modules include a real-time Network Intrusion Prevention System (NIPS) as well as antivirus protection, antispam and content filtering. Use of these capabilities is optional. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 20 01-00000-0382-20061201 NIPS Signature Protection The FortiGate NIPS has two components: a signature based component for detecting attacks passing through the FortiGate module and a local attack detection component that protects the firewall from direct attacks. Functionally, signatures are similar to virus definitions, with each signature designed to detect a particular type of attack. The IPS signatures are updated through the FortiGuard IPS service. The IPS engine can also be updated through the FortiGuard IPS service. FortiGate antivirus protection removes and optionally quarantines files infected by viruses from web (HTTP), file transfer (FTP), and email (POP3, IMAP, and SMTP) content as it passes through the FortiGate module. FortiGate antivirus protection also controls the blocking of oversized files and supports blocking by file extension. Virus signatures are updated through the FortiGuard antivirus service. The antivirus engine can also be updated through the FortiGuard antivirus service. FortiGate antispam protection tags (SMTP, IMAP, POP3) or discards (SMTP only) email messages determined to be spam. Multiple spam detection methods are supported including the FortiGuard managed antispam service. FortiGate web filtering can be configured to provide web (HTTP) content filtering. FortiGate web filtering uses methods such as banned words, address block/exempt lists, and the FortiGuard managed content service. Whenever a NIPS, antivirus, antispam or filtering event occurs, the module can record the event in the log and/or send an alert email to an operator. The rest of this section provides additional information on the NIPS, antivirus, antispam and web and email filtering capabilities of the FortiGate modules and the FortiGuard Service. For complete information refer to the FortiGate Installation Guide for the specific module in question, the FortiGate Administration Guide, and the FortiGate IPS Guide. This section contains the following information: · NIPS Signature Protection · NIPS Attack Protection · Antivirus Protection · Antispam Protection · Web Filtering · FortiGuard Services NIPS Signature Protection The FortiGate NIPS can detect a wide variety of suspicious network traffic and network-based attacks aimed at systems behind the FortiGate module. Attack signatures are the core of the FortiGate NIPS signature protection component. Signatures are transmission patterns and other codes that indicate that a system might be under attack. Functionally, signatures are similar to virus definitions, with each signature designed to detect a particular type of attack. The FortiGate modules can be configured to automatically check for and download updated attack definitions from the FortiGuard server, or they can be downloaded manually by the operator. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 21 NIPS Attack Protection Downloading updated IPS signatures or an updated IPS engine makes no changes to the configuration or basic operation of the modules. Verification of the IPS download package is done using RSA. The IPS package is signed with the FortiGuard server's private key and verified by the FortiGuard module using the FortiGuard server's private key. User defined attack signatures are also supported. NIPS Attack Protection The FortiGate NIPS can also protect the module itself from direct attacks, such as TCP, ICMP, UDP, and IP attacks. Access is denied or packets are dropped when an attack is detected. Attack parameters can be modified by the operator to ensure that normal network traffic is not considered an attack. Antivirus Protection FortiGate antivirus protection scans for infected files in the protocols for which antivirus protection as been enabled. Supported protocols include HTTP, FTP, SMTP, POP3, IMAP, and IM. Each file is tested to determine the file type and to determine the most effective method of scanning the file for viruses. For example, binary files are scanned using binary virus scanning and Microsoft Office files containing macros are scanned for macro viruses. If a file is found to contain a virus it is removed from the content stream and replaced with a replacement message. FortiGate antivirus protection can also be configured to quarantine blocked or infected files. The quarantined files are stored on the module's hard disk. An operator can delete quarantined files from the hard disk or download them. Downloaded quarantine files can be submitted to the FortiGuard Center as a virus sample. FortiGate antivirus protection is transparent to the end user. Downloading updated AV signatures or an updated AV engine makes no changes to the configuration or basic operation of the modules. Verification of the AV download package is done using RSA. The AV package is signed with the FortiGuard server's private key and verified by the FortiGuard module using the FortiGuard server's private key. FortiGate antivirus protection also detects and removes grayware such as adware, spyware, etc. Antispam Protection FortiGuard antispam protection can detect spam in SMTP, POP3 or IMAP traffic. Spam email is tagged or discarded. Spam detection methods include banned words, black/white lists, return email DNS check and the FortiGuard antispam service. The FortiGuard Antispam Service provides IP checking, URI address checking and email checksum analysis. To prevent unintentional tagging of email from legitimate senders, an operator can add sender address patterns to an exempt list that overrides the email block and banned word lists. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 22 01-00000-0382-20061201 Web Filtering Web Filtering FortiGate web filtering can be configured to scan HTTP protocol streams for banned URLs or web page content. Web filtering methods include banned words, URLs and the FortiGuard web filtering service. The FortiGuard web filtering service is a managed service that uses a database of URLs to block access to banned web sites and URLs based on content categories. If a match is found between a URL in the URL block list, the FortiGuard web filtering service, or if a web page is found to contain a word or phrase in the content block list, the FortiGate module blocks the web page. The blocked web page is replaced with a message that an operator can edit using the web-based manager. An operator can configure URL blocking to block all or just some of the pages on a web site. This feature can be used to deny access to parts of a web site without denying access to it completely. To prevent unintentional blocking of legitimate web pages, an operator can add URLs to an Exempt List that overrides the URL blocking and content blocking. Web content filtering also includes a script filter feature that can be configured to block insecure web content such as Java Applets, Cookies, and ActiveX. FortiGuard Services The FortiGuard services are a family of managed services available to Fortinet customers. The FortiGuard services include: · IPS signature and engine updates · AV signature and engine updates · A managed antispam service · A managed web filtering service · Firmware updates Customers can purchase FortiGuard services for their FortiGate units on a yearly basis. Use of the FortiGuard services is optional, but recommended. FIPS 140-2 Compliant Operation To operate a FortiGate module in a FIPs compliant manner, organizations must follow the procedures explained in this section of the Security Policy. This section contains the following information: · Overview of FIPS 140-2 compliant operation · Initial configuration of the FortiGate unit · Enabling FIPS-CC mode · Self-Tests · Effects of FIPS-CC compliant mode · Remote access requirements · Disabling FIPS-CC mode FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 23 Overview of FIPS 140-2 compliant operation Overview of FIPS 140-2 compliant operation FIPS 140-2 compliant operation requires both that you use the FortiGate Multi- Threat Security System in its FIPS-CC mode and that you follow secure procedures for installation and operation of the FortiGate unit. You must ensure that: · The FortiGate unit is installed in a secure physical location. · Physical access to the FortiGate unit is restricted to authorized operators. · 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 should be capitalized. · One (or more) of the characters should be numeric. · One (or more) of the characters should be non alpha-numeric (e.g. punctuation mark). · Administration of the FortiGate unit is permitted using only certified administrative methods. These are: · console connection · web-based manager via HTTPS · command line interface (CLI) access via SSH · The FortiGate unit 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. Also, on LCD-equipped units, Transparent mode is indicated by "FIPS-CC-TP" and NAT/Route by "FIPS-CC-NAT" on the LCD display. Initial Inspection of the Modules The SO must inspect a module before installation to verify that it has not been tampered with during shipment. The packaging and external enclosure must be inspected for visible signs of damage or tampering. If a module displays signs of damage or tampering, the SO must contact Fortinet to obtain a replacement unit. Applying the Security Seals After completing the initial inspection of the modules the SO must apply the security seals as explained in the section "Physical Security" on page 16 to ensure full compliance with the FIPS 140-2 standard. Initial configuration of the FortiGate unit This section describes how to configure your FortiGate unit in the FIPS-CC mode of operation. Proceed as follows: · Install the unit following the procedures in the documentation. · Register your FortiGate unit with Fortinet. · If you are upgrading an existing FortiGate unit to FIPS-CC firmware, download the appropriate firmware from Fortinet and install it on your unit. · Verify the firmware version of your FortiGate unit. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 24 01-00000-0382-20061201 Initial configuration of the FortiGate unit · Enable FIPS-CC mode. Verifying the hardware version of the unit Check the label on the blade or chassis of the unit to determine the hardware version. Match the first 6 characters of the hardware version to the FIPS validated hardware versions listed in Table 13. Table 13: FIPS 140-2 validated hardware versions FortiGate Model Hardware Version FG-5001SX P4CF76 FG-5001FA2 C5FA26 FG-5050 C4QP38 Installing the unit Both the Quick Start Guide and the Getting Started section of the Installation Guide for your FortiGate unit provide instructions on the physical installation and initial configuration of your unit. When you have completed these procedures you will be able to access both the web-based manager and Command Line Interface (CLI). Registering the unit For information about registering your FortiGate unit, see "Registering a FortiGate unit" in the System Maintenance chapter of the Administration Guide for your unit. You need the user name and password Fortinet provides to you to download the FIPS-CC compliant firmware. Downloading and installing FIPS-CC compliant firmware Unless you received a FortiGate unit with FIPS-CC firmware pre-installed, you need to download and install the appropriate firmware for your FortiGate unit. The firmware files can be obtained from the Fortinet support site after registering your unit. The firmware build information and firmware files for each model are listed in Table 14 and Table 15. Note that the chassis component of the modules do not require firmware. Table 14: Firmware builds for validated FortiGate models FortiGate Model Firmware Build FG-5001SX FortiOS 3.0, build8317, 061121 FG-5001FA2 FortiOS 3.0, build8317, 061121 Table 15: Firmware files for validated FortiGate models FortiGate Model Firmware File FG-5001SX FGT_5001-v300-build8317-fips_cc_lr.out FG-5001FA2 FGT_5001FA2-v300-build8317-fips_cc_lr.out FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 25 Enabling FIPS-CC mode To download the firmware 1 Determine the appropriate firmware version from Table 14. 2 Determine the appropriate firmware file from Table 15. 3 With your web browser, go to https://support.fortinet.com and log in using the name and password you received when you registered with Fortinet Support. 4 Navigate to the v3.00 FIPS-CC certified firmware page for the FortiGate product. Select the firmware build(s) you need and save the file on the management computer or on your network where it is accessible from the FortiGate unit. Installing the FIPS-CC firmware You install the FIPS-CC compliant firmware as an upgrade from the standard firmware. To install the FIPS-CC firmware 1 Using the management computer, connect to the unit's web-based manager. See the Quick Start Guide or the Installation Guide for information. 2 Type admin in the name field. If you have assigned a password, type it in the Password field. Select Login. 3 Go to System > Status. 4 Under System Information > Firmware version, select Update. 5 Type the path and filename of the firmware image file, or select Browse and locate the file. 6 Select OK. The unit uploads the firmware image file, upgrades to the new firmware version, restarts, and displays the Login page. This process takes a few minutes. Verifying the firmware version of the unit Execute the following command from the command line: get system status The version line of the status display shows the FortiGate model number, firmware version, build number and date: Version:Fortigate-5001 3.00,build8317,061121 Verify that your firmware version, build number and date match those shown above for your specific model. Enabling FIPS-CC mode If you have verified the firmware version, you are ready to enable FIPS-CC mode. As part of enabling FIPS-CC mode, you must define administrator account names and passwords. The default admin account is not available in FIPS-CC mode. You must use a console connection to enable FIPS-CC mode. If you try to use another type of connection, a "check permission failed" error occurs. Note: When you enable FIPS-CC mode, all of the existing configuration is lost. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 26 01-00000-0382-20061201 Enabling FIPS-CC mode To enable FIPS-CC mode 1 Log in to the CLI and enter the following commands: config system fips-cc set status enable end 2 In response to the following prompt, enter the account name for the Security Administrator: Please enter SECURITY administrator name: 3 In response to the following prompt, enter the password for the Security Administrator: Please enter SECURITY administrator password: 4 When prompted, re-enter the Security Administrator password. 5 In response to the following prompt, enter the account name for the Audit Administrator: Please enter AUDIT administrator name: If you want the Security Administrator to also act as the Audit Administrator, enter the Security Administrator account name you defined in step 2. There will be no prompt for a password. (Skip step 6.) 6 In response to the following prompt, enter the password for the Audit Administrator: Please enter AUDIT administrator password: 7 When prompted, re-enter the Audit Administrator password. 8 In response to the following prompt, enter the account name for the Crypto Administrator: Please enter CRYPTO administrator name:CryptoAdmin If you want the Security Administrator to also act as the Crypto Administrator, enter the Security Administrator account name you defined in step 2. There will be no prompt for a password. (Skip step 9.) 9 In response to the following prompt, enter the password for the Cryptographic Administrator: Please enter CRYPTO administrator password: 10 When prompted, re-enter the Crypto Administrator password. The CLI displays the following message: Warning: most configuration will be lost, do you want to continue? (y/n) 11 Enter y. The FortiGate unit restarts and runs in FIPS-CC compliant mode. FIPS-CC mode status indicators There are two status indicators that show whether the FortiGate unit is running in the FIPS 140-2 and Common Criteria compliant mode of operation: FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 27 Self-Tests Table 16: FIPS-CC mode status indicators Location Indication Front panel LCD FIPS-CC-NAT or FIPS-CC-TP Output of get system status command FIPS-CC mode: enable Self-Tests The modules execute the following self-tests during startup and initialization: · Firmware integrity test using HMAC SHA-1 · VPN bypass test using HMAC SHA-1 (VPN table integrity test) · Triple-DES, CBC mode, encrypt/decrypt known answer test · AES, CBC mode, encrypt/decrypt known answer test · HMAC SHA-1 known answer test · RSA signature generation/verification known answer test · RNG 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 (to initiate a specific self-test). The modules execute the following conditional tests when the related service is invoked: · Continuous RNG test · RSA pairwise consistency test · Firmware download integrity test using RSA public/private keys Self-Test Status Indicators There are two types of self-test status indicators: the startup indicators and the on- demand indicators. The startup self-test status indicators are output through the console connection during the startup process. The on-demand self-test status indicators are output as a the result of a execute fips CLI command. The following output shows the successful completion of the startup self-tests: Initializing firewall... System is started. FIPS-CC mode: Starting self-tests. Running AES test... passed Running 3DES test... passed Running SHA1 HMAC test... passed Running RSA test... passed Running Firmware/VPN config integrity test... passed Running RNG test... passed Self-tests passed FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 28 01-00000-0382-20061201 Effects of FIPS-CC compliant mode The following output shows the successful completion of the on-demand self-tests for all of the algorithm known answer tests: Fortigate-5001 # execute fips kat all Starting self-tests Running AEStest... passed Running 3DES test... passed Running SHA1 HMAC test... passed Running RSA test... passed Running RNG test... passed Self-tests passed Effects of FIPS-CC compliant mode The following list describes, not necessarily in order, the effects of enabling FIPS- CC mode with respect to the normal mode of operation. · All previous configuration settings except the network interface settings are lost. If HTTP or Telnet administrative access was enabled on any interfaces, it is disabled. · The FortiGate unit front panel LCD displays "FIPS-CC-" followed by the operation mode, "NAT" or "TP". You might have to press an LCD panel key to see this display. · The get system status CLI command display includes "FIPS-CC mode: enable". · Logging is enabled by default for: · new firewall policies · interfaces where administrative access is enabled · failed connection attempts to the FortiGate unit using TCP/IP ports other than 22 (ssh), 23 (telnet), 80 (HTTP), and 443 (HTTPS). · all configuration changes · configuration failures · remote IP lockout due to reaching maximum number of failed login attempts · log viewing · interface going up or down · Disk logging is enabled. · Reaching 95% of the log disk storage capacity results in the FortiGate unit entering an error mode that shuts down all of the interfaces until the administrator intervenes. · Anomaly detection and protection is applied to traffic addressed to the FortiGate unit. · TFTP communication is not permitted. It is not secure. In non-FIPS-CC operation this can be used for remote configuration backup. · SNMP services are disabled. · Remote access clients must meet security requirements. See "Remote access requirements" on page 30. · All firewall policies are removed. · All administrators must accept a disclaimer statement at logon. This disclaimer is configured in the Post Login replacement message. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 29 Remote access requirements · The FortiGate unit performs self-tests at startup. Also, the administrator can run some self-tests at any time. If any of these tests fail, the unit goes into error mode and shuts down. · There is an alarm capability. See "Alarms" on page 40. · The DES and MD5 algorithms are not available for VPN configurations. · Diffie-Hellman groups 14 through 18 are available to VPN configurations and group 15 is the default. DH groups 15 through 18 use 3072 to 8192-bit keys. You should use these groups for FIPS-CC complaint VPNs between FortiGate units. Current versions of the FortiClient Host Security application support only DH groups 1, 2 and 5. · ANSI X9.31 RSA signature is an optional authentication method for IPSec VPNs. This method is supported only on FortiGate units in FIPS-CC mode. · When configuring passwords, the FortiGate unit requires you to enter the password a second time as confirmation. · Configuration backups use Triple-DES encryption with a HMAC-SHA1 checksum and a user-defined password. It is not possible to use a FIPS-CC backup file if you take the FortiGate unit out of FIPS-CC mode. If you re-enable FIPS-CC mode, the seed key used in the encryption changes. · In High Availability mode, the High Availability heartbeat data is encrypted. · Blocking of spoofed TCP RST packets is enabled by default. · On a CLI session, when an administrator logs out or the session times out, the FortiGate unit sends 100 carriage return characters to clear the screen. Remote access requirements In FIPS-CC mode, remote administration using HTTP or Telnet is disabled. SSH and HTTPS access are supported, but clients must meet certain security requirements. Diffie-Hellman prime sizes By default, in FIPS-CC mode the FortiGate unit requires values at least 3072 bits long to be used in the Diffie-Hellman key exchange when an HTTPS session begins. Using the CLI, you can set this minimum to any of the safe standard values specified in RFC 3526: 1024, 1536, 2048, 3072, 4096, 6144 or 8192 bits. For example, to use many commercially available browsers, you might need to set the key size to 1024, as follows: config system global set dh-params 1024 end SSH client requirements To access the CLI through network interfaces in FIPS-CC mode, your SSH client must support the following: Authentication: · HMAC SHA-1 Encryption: · AES256 FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 30 01-00000-0382-20061201 Disabling FIPS-CC mode Web browser requirements To use the web-based manager in FIPS-CC mode, your web browser application must meet the following requirements: · Authentication algorithm: · PKCS1 RSA · Connection security: · TLS 1.0 Enabling administrative access In FIPS-CC mode, the network interfaces by default do not allow administrative access, preventing you from using the web-based manager. You can re-enable use of the web-based manager using CLI commands on the console. This example enables HTTPS administrative access on the Internal interface to allow use of the web-based manager: config system interface edit internal set allowaccess https end For detailed information about accessing the web-based manager, see "Connecting to the web-based manager" in the Installation Guide for your unit. Disabling FIPS-CC mode The only way that you can return the FortiGate unit to the normal mode of operation is to restore the factory default configuration. Enter the following CLI command: execute factoryreset Disabling FIPS-CC mode erases the current configuration. Administration FIPS-CC mode enforces predefined administrator roles instead of the more granular selection access permissions allowed in the non-FIPS-CC mode of operation. Also, by default, administrator logon requires acceptance of a disclaimer statement. This section contains the following information: · Administrator roles · Administrator accounts and profiles · Enabling multiple virtual domain configuration · Disclaimer access banner · Using custom administrator access keys (certificates) · Configuration backup FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 31 Administrator roles Administrator roles In FIPS-CC mode, access profiles for administrators are configured only in terms of administrator roles. There are three administrator roles. All have read access to the entire configuration. They can modify the configuration as follows: Administrator role can modify Security administrator all except VPN settings and log data (cannot delete logs) Audit administrator log data (can delete logs) but cannot change log settings Crypto administrator VPN settings Administrator accounts and profiles When you invoke FIPS-CC mode for the first time, the FortiGate unit prompts you for a name and password to create an administrator account for each role. You can, as an alternative, assign the Security administrator account all three roles. After the initial configuration of administrators when you enable FIPS-CC mode, you can modify administrators and administrator profiles through the web-based manager or the CLI. In FIPS-CC mode, the FortiGate unit has three preconfigured access profiles, that you can edit, but not delete: Table 17: Default administrator access profiles Access profile Default administrator role def_prof_SA Security Administrator Role def_prof_AA Audit Administrator Role def_prof_CA Crypto Administrator Role def_prof_SA_AA Security/Audit Administrator Role def_prof_SA_CA Security/Crypto Administrator Role def_prof_AA_CA Audit/Crypto Administrator Role def_prof_SA_AA_CA Security/Audit/Crypto Administrator Role You can create additional access profiles and enable one or more administrator roles for them. You can create additional administrators and assign them to any of the access profiles. If, when enabling FIPS-CC mode, you chose to use the SA account name for the AA and/or CA account names, only the applicable default profiles will be created. For example, if you used the SA account name for both the AA and CA account names, only the def_prof_SA_AA_CA access profile will be created. Enabling multiple virtual domain configuration The FortiGate unit can operate multiple virtual domains (VDOMs). VDOMs enable a FortiGate unit to function as multiple independent units. For more information, see the "Using virtual domains" chapter of the FortiGate Administration Guide. Before you can enable virtual domain operation, you must make at least one of your administrators a VDOM administrator using the CLI. For example, to make the "SecAdmin" administrator a VDOM admin, enter the following command: config sys admin FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 32 01-00000-0382-20061201 Disclaimer access banner edit cc_admin set is-admin 1 end To enable multiple VDOM operation in the web-based manager, go to System > Admin > Settings, select Virtual Domain Configuration, and then select Apply. To enable multiple VDOM operation using the CLI, enter the following command: config system global set vdom-admin enable end Disclaimer access banner By default, in FIPS-CC mode, each time you log on as an administrator, you see a warning statement that usage is monitored and that unauthorized usage can result in disciplinary or legal action. You must accept the statement to continue. If you decline the statement, you are immediately logged out. Logs record response to the disclaimer at each logon. You can disable the disclaimer in the CLI as follows: config system global set access-banner disable end Similarly, you can enable the disclaimer, like this: config system global set access-banner enable end You can modify the disclaimer to meet the requirements of your organization. The disclaimer is an editable replacement message called "Post login". See "Replacement messages" in the System Config chapter of the FortiGate Administration Guide. Using custom administrator access keys (certificates) You can upload VPN certificates to use as custom RSA keys to authenticate administrators. To do this, you must upload the signed public certificate to the FortiGate unit. If the private key was not generated on the FortiGate unit, it also must be uploaded. Certificates must have a modulus of at least 2048 bits. Importing the custom RSA key In FIPS-CC mode, you cannot import certificates using TFTP. You must use a USB storage device instead. Put the files you want to upload on the device and connect the device to the FortiGate unit. Use one of the following commands to import the files: If you have a PKCS12 format key-certificate file, execute vpn certificate local import pkcs12 If you have separate certificate and key files, execute vpn certificate local import cert Each command is a single line. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 33 Configuration backup Enabling the custom RSA key To enable the custom RSA key you imported, use the following CLI command: config system global set admin-server-cert admin-cert end This applies to both HTTPS and SSH connections. Configuration backup Configuration backup files created in FIPS-CC mode are not compatible with backup files created in non-FIPS-CC mode. Also, a FIPS-CC backup file is not usable after you exit and then re-enter FIPS-CC mode because its checksum is based on a seed value calculated when you start FIPS-CC mode. Logging The FIPS-CC mode of operation enforces logging of all traffic and system events. The severity threshold for logging is set to the lowest level: debug. This ensures that the maximum amount of information is logged. This section contains the following information: · Default log settings · Excluding specific logs · Viewing log messages from the web-based manager · Viewing log messages from the CLI · Backing up log messages · Viewing log file information · Deleting filtered log messages · Deleting rolled log files Default log settings Logs are written to the FortiGate unit hard disk. The FortiGate unit generates warning log entries when the disk space allocated for logging is filled to 75%, then 90% and finally 95% of capacity. When logs exceed 95% of capacity, the default action is to block further traffic and switch to Error mode. See "Clearing Error mode" on page 42 for more information. Logging to external devices is disabled due to the security requirements of FIPS- CC operation, except for downloading of logs to the management computer. See "Backing up log messages" on page 38. Table 19 lists the disk logging settings required for FIPS-CC mode. If you change these options from the default, the operation of your FortiGate unit is no longer FIPS-CC compliant. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 34 01-00000-0382-20061201 Excluding specific logs Table 18: config log disk filter command keywords and variables Keywords and variables Description Default admin Enable or disable logging all administrative enable {disable | enable} events, such as user logins, resets, and configuration updates in the event log. This is available only if event is set to enable. allowed Enable or disable logging all traffic that is enable {disable | enable} allowed according to the firewall policy settings in the traffic log. This is available only if traffic is set to enable. auth Enable or disable logging all firewall-related enable {disable | enable} events, such as user authentication in the event log. This is available only if event is set to enable. event Enable or disable the event log. enable {disable | enable} severity Select the logging severity level. The debug {alert | critical | FortiGate unit logs all messages at and debug | emergency | above the logging severity level you select. For example, if you select error, the unit error | information logs error, critical, alert and | notification | emergency level messages. warning} emergency - The system is unusable. alert - Immediate action is required. critical - Functionality is affected. error - An erroneous condition exists and functionality is probably affected. warning - Functionality might be affected. notification - Information about normal events. information - General information about system operations. debug - Information used for diagnosing or debugging the FotiGate unit. system Enable or disable logging of all system- enable {disable | enable} related events, such as ping server failure and gateway status, in the event log. This is available only if event is set to enable. traffic Enable or disable the traffic log. enable {disable | enable} violation Enable or disable logging of all traffic that enable {disable | enable} violates the firewall policy settings in the traffic log. This is available only if traffic is set to enable. Table 19: config log disk setting command keywords and variables Keywords and variables Description Default diskfull Enter the action to take when the log disk is blocktraffic {blocktraffic | full. nolog | overwrite} Excluding specific logs Use the exclude-list option of the log filtering command to define log entries that will not be recorded: FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 35 Viewing log messages from the web-based manager config log disk filter config exclude-list edit set category config fields edit set args set negate {enable | disable} end end end end end Table 20: log filter exclude-list command keywords and variables Keywords and variables Description Default category category is one of: No default. attack, content, event, im, spam, traffic, virus, webfilter edit Enter the name of the field on which to No default. base exclusion. Available field_name values depend on the category setting. If you enter an invalid field name, valid field names are listed. args Enter the field value to match. No default. negate Enable to exclude logs where the value disable {enable | disable} of the field does not match . Disable to exclude logs where the value of the field matches . Viewing log messages from the web-based manager To view log messages from the web-based manager, go to Log & Report > Log Access. For detailed instructions about viewing the logs, consult the online Help system or see the Log & Report chapter of the FortiGate Administration Guide. Viewing log messages from the CLI You can view and clear log messages from the CLI. Before viewing logs, you must set filter options to select the logs that you want to view. You can view one log category on one device at a time. Optionally, you can filter the listing to show only specified date ranges or severities of log messages. For traffic logs, you can filter log messages by source or destination IP address. Setting filtering for log messages Use execute log filter commands to select which logs to display with the execute log display command. Commands are cumulative. Enter execute log filter list to see the current settings. For more information about log filtering, see the FortiGate CLI Reference. The command syntax is: FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 36 01-00000-0382-20061201 Viewing log messages from the CLI execute log filter Table 21: execute log filter command keywords and variables Keywords and variables Description Default category Type of log, except list, which displays event {event | ids | spam | the current setting. traffic | virus | webfilter | list } device Device where the logs are stored, except disk {disk | memory | list} list, which displays the current setting. field Filter on log field. Use ? as No default. field_name to see a list of valid fields. lines-per-view Set lines per view. Range: 5 to 1000 10 list Display current filter settings. No default. reset Reset filter settings. No default. rolled-number Select logs from rolled log files. 0 selects 0 current log file. sortby Set display order. See "Sorting log No default. messages" on page 37. start_line Select first line of logs to display. 1 Use as many execute log filter commands as you need to define the log messages that you want to view. For example, to select the memory event logs from 10-14 July 2006, you use the following commands: execute log filter category event execute log filter device memory execute log filter field date 2006-07-10 2006-07-14 Sorting log messages In addition to selecting logs to display, the execute log filter command can sort logs by field. execute log filter sortby Enter the command without a field name to see a list of valid field names. Viewing log messages After you have selected the log messages that you want to view using the execute log filter command, you can display them with the following command: execute log display The console displays the first 10 log messages. To view more messages, run the command again. You can do this until you have seen all of the selected log messages. To restart viewing the list from the beginning, use the commands execute log filter start_line 1 execute log display FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 37 Backing up log messages Resetting log filters You can restore the log filters to their default values using the command execute log reset Backing up log messages You can back up log messages to your Administrative computer or other computer on the network. Backing up log messages using the web-based manager The FortiGate unit downloads log files to the Administrative computer using HTTPS. 1 Go to Log & Report > Log Access. 2 Select either the Disk or Memory tab as appropriate. 3 From the Log Type list, select the type of log you want to back up. 4 Select the download icon for the log file you want to back up. 5 Select either Download file in the normal format or Download file in CSV format, as appropriate. 6 Follow your browser's procedure for saving the downloaded file. Backing up log messages using the CLI You can back up logs from the CLI only if you re-enable TFTP communication which is disabled by default in FIPS-CC mode. Enter the following command: config system global set tftp enable end Using the CLI, you can back up selected log types or perform an all-logs backup that includes logs that have rolled over. To back up log messages using the CLI 1 Install a TFTP server on the computer in the directory where you want to receive the log files. 2 Use a crossover cable to connect the computer to the appropriate network interface. On models 800 and below, connect to the Internal interface; on other models, connect to port 1. 3 Start the TFTP server. 4 Connect to the CLI interface. 5 To back up all log messages, execute the following command: execute backup alllogs To back up only a specific log type, execute the following command: execute backup log can be one of: traffic, event, ids, virus, webfilter or spam. The FortiGate unit reports each transferred file as follows: FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 38 01-00000-0382-20061201 Viewing log file information Connect to tftp server 192.168.1.1 ... Please wait... ##Sent log file /var/log/tlog to tftp server as tlog_20041014_080007 OK. Viewing log file information You can view the list of current and rolled log files on the console. The list shows the file name, size and timestamp. The CLI command is as follows: execute log list must be one of: event, ids, spam, traffic, virus or webfilter. The output looks like this: elog 8704 Fri Jan 28 14:24:35 2005 elog.1 1536 Thu Jan 27 18:02:51 2005 elog.2 35840 Wed Jan 26 22:22:47 2005 At the end of the list the total number of files in the category is displayed. For example: 501 event log file(s) found. Deleting filtered log messages You can select log messages with the execute log filter command and then delete them with the command: execute log delete-filtered For example, to delete all the traffic logs, enter the following commands: execute log filter category traffic execute log delete-filtered For information about the execute log filter command, see "Setting filtering for log messages" on page 36. Deleting rolled log files You can delete rolled log files using the execute log delete-rolled command: execute log delete-rolled [] must be one of: event, ids, spam, traffic, virus or webfilter. The and values represent the range of log files to delete. If is not specified, only the log number specified by is deleted. For example, to delete all of the rolled traffic log files, enter the following command: execute log delete-rolled traffic 1 9999 FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 39 Configuring alarms Alarms In FIPS-CC mode, the FortiGate unit can raise alarms for the following types of events: · failed administrator authentication · packet replay attempts (IPS?) · bootup self-test failure · cryptographic failure · firewall policy violation (blocked sessions) Alarms for all of these events are based on logs that report these events. For firewall events, traffic violation logs are used.This section contains the following information: · Configuring alarms · Alarm notifications · Acknowledging alarms Configuring alarms An alarm consists of one or more trigger events that occur a specified number of times in a particular time period. For example, you could configure the FortiGate unit to raise an alarm if there are three unsuccessful administrative login attempts in the same minute. You can configure alarms only in the CLI. Each alarm is defined as an "alarm group". There are separate alarm groups for each virtual domain (VDOM). You can select whether the alarms in each VDOM are audible. Within each alarm group, you specify: · the threshold for each triggering event, 0 for events that will not trigger the alarm · the period over which the number of triggering events is counted, 0 to count from startup If you include more than one trigger event, the threshold for all the trigger events must be met to trigger the alarm. Firewall policy violations are configured together. Alarm notification messages appear on the web-based manager, in SSH administrator sessions and on the console. The messages repeat until the administrator acknowledges the alarm. Alarm CLI configuration The system alarm command syntax is as follows: config system alarm set status {enable | disable} set audible {enable | disable} config groups edit set admin-auth-failure-threshold set crypto-failure-threshold set period set replay-attempt-threshold set self-test-failure-threshold FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 40 01-00000-0382-20061201 Configuring alarms config fw-policy-violations edit dst-port dst-ip src-port src-ip threshold end end end The keywords and variables are: Table 22: system alarm keywords and variables Keywords and variables Description Default audible If enabled, the console beeps when the disable {enable | disable} alarm notification appears. status Enable or disable all alarms. disable {enable | disable} Alarm group keywords and variables edit is the group identifier. Use No default. 0 to automatically assign the next available number. admin-auth-failure- Enter threshold for administrator 0 threshold authentication failures. Use 0 to disregard in this alarm group. crypto-failure-threshold Enter threshold for cryptographic failure. 0 Use 0 to disregard in this alarm group. period Enter the period over which triggering 0 events are counted. Use 0 for no limit (events are counted from start-up). replay-attempt-threshold Enter threshold for packet replay 0 attempts. Use 0 to disregard in this alarm group. self-test-failure- Enter threshold for failure of startup 0 threshold integrity tests. Use 0 to disregard in this alarm group. A self-test failure alarm is visible only after you recover from Error mode. fw-policy-violations keywords and variables edit is the identifier for No default. this trigger. Use 0 to automatically assign the next available number. dst-port Enter the destination port number to 0 match in the traffic violation log. dst-ip Enter the destination IP or subnet address 0 to match in the traffic violation log. src-port Enter the source port number to match in 0 the traffic violation log. src-ip Enter the source IP or subnet address to 0 match in the traffic violation log. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 41 Alarm notifications Alarm notifications Alarm notifications appear on both the CLI console and the web-based manager. On the CLI console alarm notifications look like this: ******************* !!! A L A R M !!! ******************* * ID: 1 Time: Tue Sep 5 09:39:55 2006 * Group ID: 1 VD: root * Type: Authentication failures * Message: Alarm is triggered ********************************************************* On the web-based manager, alarm notifications appear in a separate browser window and look like this: Figure 8: Alarm notification - web-based manager The notification clearly shows the time, virtual domain, alarm group and type. Alarm notifications repeat until you acknowledge them. On the CLI console, the notification repeats every time you use the Enter key. In the web-based manager, you can close the alarm notification window, but the alarm will reappear in a few seconds. Acknowledging alarms To acknowledge an alarm in the web-based manager, you simply select OK in the alarm notification window. On the CLI console, you acknowledge alarms using one of the following commands: To acknowledge a single alarm execute ack-alarm To acknowledge all alarms execute ack-alarm all Clearing Error mode The FortiGate unit switches to Error mode, shuts down network interfaces and blocks traffic when current and rolled log files consume more than 95% of disk capacity. The FortiGate unit indicates Error mode as follows: · The console displays "FIPS-CC-ERR". You might have to press an LCD panel key to see this display. FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 42 01-00000-0382-20061201 Acknowledging alarms · "FIPS-CC-ERR" is prepended to the CLI prompt, FIPS-CC-ERR FortiGate-5001$, for example. To resume normal FIPS-CC mode operation, you first must reduce the logs to below 95% of device capacity. Only an administrator with the Audit Administrator role can do this. From the console, do any of the following: · Delete rolled log files using the command execute log delete-rolled. · Delete all current log entries using the command execute log delete-all. Ideally you should reduce logs to 50% or less of device capacity. For information on how to delete logs, see "Deleting filtered log messages" on page 39. To disable error mode, enter the following CLI command: execute error-mode exit The FortiGate unit resumes normal FIPS-CC compliant operation unless there is still too little free space on the log device. Non-FIPS Approved Services The modules also provide the following non-FIPS approved services: · NTP synchronization · DHCP server · Configuration backup and recovery FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 01-00000-0382-20061201 43 Acknowledging alarms FortiGate-5050 Chassis with FortiGate-5001SX and 5001FA2 Blades FIPS 140-2 Security Policy 44 01-00000-0382-20061201