Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy September 7, 2007 Version: 1.3 Prepared by: Ingrian Networks 350 Convention Way Redwood City, CA 94063-1405 Copyright Ingrian Networks, Inc. 2007. May be reproduced only in its original entirety [without revision]. Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 TABLE OF CONTENTS 1. MODULE OVERVIEW .........................................................................................................................................3 2. SECURITY LEVEL................................................................................................................................................6 3. MODES OF OPERATION.....................................................................................................................................7 4. PORTS AND INTERFACES .................................................................................................................................8 5. IDENTIFICATION AND AUTHENTICATION POLICY................................................................................8 6. ACCESS CONTROL POLICY............................................................................................................................10 ROLES AND SERVICES ..............................................................................................................................................10 DEFINITION OF CRITICAL SECURITY PARAMETERS (CSPS)......................................................................................18 DEFINITION OF CSPS MODES OF ACCESS ................................................................................................................20 7. OPERATIONAL ENVIRONMENT....................................................................................................................22 8. SECURITY RULES .............................................................................................................................................22 9. PHYSICAL SECURITY POLICY ......................................................................................................................23 PHYSICAL SECURITY MECHANISMS .........................................................................................................................23 10. MITIGATION OF OTHER ATTACKS POLICY...........................................................................................24 11. REFERENCES ....................................................................................................................................................24 12. DEFINITIONS AND ACRONYMS...................................................................................................................24 Page 2 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 1. Module Overview The Ingrian DataSecure Appliance i416, i426, i116 is a multi-chip standalone cryptographic module that is encased in a hard, opaque, commercial grade metal case and is a hardware/software solution for providing security and cryptographic processing. The cryptographic module also utilizes an internal server called the Network-Attached Encryption Server, which executes a range of security-related tasks, including processing all cryptographic requests generated by NAE connectors residing on application servers and databases. The module configurations under validation are as follows: DataSecure Appliance i416: HW P/N DS-0416-0100-00; FW Version 4.6.2p01 DataSecure Appliance i426: HW P/N DS-0426-0100-00; FW Version 4.6.2p01 DataSecure Appliance i116: HW P/N DS-0116-0100-00; FW Version 4.6.2p01 The cryptographic module provides several interfaces for data input, data output, status output, and command input. The following images show the module's cryptographic boundary, which is the surrounding hard, opaque, commercial grade metal case, and the module's interfaces: Figure 1 ­ Image of the i416 Page 3 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Figure 2 ­ Image of the i426 Figure 3 ­ Image of the i116 Page 4 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 The following outlines the different hardware configurations of the Ingrian DataSecure Appliance: Ingrian DataSecure Appliance i116 Hardware VIA C3 800 MHz CPU, 1GB RAM, 80GB SATA drive This hardware platform is intended for smaller deployments. It features a single processor architecture and single hard drive resource and can process more than 11000 secure cryptographic operations per second. Ingrian DataSecure Appliance i416 Hardware Single Dual Core CPU, 1U Rack Mountable Chassis, 1GB RAM, 80 GB SATA drive This hardware platform is intended for medium sized deployments. It features a single processor architecture and single hard drive resource and can process more than 35000 secure cryptographic operations per second. The hard drive is hot swappable. Ingrian DataSecure Appliance i426 Hardware Two Dual Core CPUs, 2U Rack Mountable Chassis, 1GB RAM, 2 80GB SATA in RAID configuration. This hardware platform is intended for larger deployments. It features a dual processor architecture and dual hard drives in a RAID-1 mirroring configuration. These drives are hot swappable. This appliance can process more than 45000 secure cryptographic operations per second. Page 5 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 2. Security Level The cryptographic module meets the overall requirements applicable to Level 2 security of FIPS 140-2. Table 1 - Module Security Level Specification Security Requirements Section Level Cryptographic Module Specification 2 Module Ports and Interfaces 2 Roles, Services and Authentication 3 Finite State Model 2 Physical Security 2 Operational Environment N/A Cryptographic Key Management 2 EMI/EMC 2 Self-Tests 2 Design Assurance 2 Mitigation of Other Attacks N/A Page 6 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 3. Modes of Operation Approved mode of operation The cryptographic module supports the following FIPS Approved algorithms: · DSA with 1024-bit keys for digital signature generation and verification · RSA with 1024/2048-bit keys for digital signature generation and verification · Triple-DES (three key) for encryption and decryption · Triple-DES (two key) for encryption and decryption · AES for encryption and decryption · SHA-1 for hashing · HMAC-SHA-1 · ANSI X9.31 DRNG for key generation The cryptographic module supports the following commercially available protocols: · TLS/SSL V3.1 protocol for key establishment (RSA for key transport provides 80 or 112 bits of encryption strength) · SSH V2 protocol for key establishment (Diffie-Hellman for key agreement provides 80 bits of encryption strength) The cryptographic module relies on the implemented deterministic random number generator (DRNG) that is compliant with ANSI X9.31 for generation of all cryptographic keys. The module uses a NDRNG to generate the seed value and seed key for the ANSI X9.31 DRNG. The cryptographic module may be configured for FIPS mode via establishing the following configuration settings. Any deviation from the following configuration settings will put the module in non-FIPS mode. Authorized users can set the module in FIPS mode by setting the 'Set FIPS compliant' button under the high security configuration tab. The module is in FIPS mode when the `Set FIPS Mode' button is enabled and is not in FIPS Mode if otherwise. NOTE: The hot swappable hard drives in the i416 and i426 are not allowed to be removed while the module is in FIPS mode. Non-FIPS mode of operation In non-FIPS mode, the cryptographic module provides non-FIPS Approved algorithms as follows: · RSA 512, 768 · Single DES · SEED Page 7 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 · MD5 · RC4 4. Ports and Interfaces The cryptographic module provides the following physical ports and logical interfaces: 1) Serial Port (RS232 DB9): data input, data output, status output, command input 2) Ethernet 10/100/1000 (Qty. 1 or 2): data input, data output, status output, command input 3) PS2: control input (BIOS) (Qty. 2) 4) VGA: data output, status output (BIOS) 5) Power Interface: power 5. Identification and Authentication Policy Assumption of roles The cryptographic module shall support five distinct operator roles (User, Cryptographic Officer/Administrator, Ingrian User, Cluster Member and File Encryption User). The cryptographic module shall enforce the separation of roles using identity-based operator authentication. An operator must enter a username and its password and/or provide a certificate to log in. The username is an alphanumeric string of one or more characters. The password is a string of eight or more characters chosen by the operator from the 90 printable and human- readable characters. Upon correct authentication, the role is selected based on the username of the operator and the logical interface that the operator is connected to. At the end of a session, the operator must log-out. Table 2 - Roles and Required Identification and Authentication Role Type of Authentication Authentication Data User Identity-based operator Username/Password authentication and/or Public Certificate Cryptographic-Officer1 Identity-based operator Username/Password with authentication the option of Public Certificate Ingrian User Identity-based operator Public Certificate authentication 1 It should be noted that the terms `Administrators' and `Cryptographic Officer' are used interchangeably throughout this document. Page 8 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Role Type of Authentication Authentication Data Cluster Member Identity-based operator Public Certificate authentication File Encryption User Identity-based operator Public Certificate authentication Table 3 ­ Strengths of Authentication Mechanisms Authentication Mechanism Strength of Mechanism Username/Password The probability that a random attempt will succeed or a false acceptance will occur is 1/6,952,862,280 which is less than 1/1,000,000. The number of authentication attempts that can be made is 6 per minute (i.e. after 6 unsuccessful authentication attempts the account is locked for one minute). Therefore the probability of successfully authenticating to the module within one minute is 6/6,952,862,280 which is less than 1/100,000. Username/Password and Public Certificate The probability that a random attempt will succeed or a false acceptance will occur is less 1 than 80 which is less than 1/1,000,000. 2 The probability of successfully authenticating to the module within one minute is also less 1 than 80 which is less than 1/100,000. 2 Public Certificate The probability that a random attempt will succeed or a false acceptance will occur is less 1 than 80 which is less than 1/1,000,000. 2 The probability of successfully authenticating to the module within one minute is also less Page 9 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 1 than which is less than 1/100,000. 280 6. Access Control Policy Roles and Services Table 4 ­ Services Authorized for Roles Role Authorized Services User: · Encrypt Data: This service TDES or AES encrypts plaintext data passed into the cryptographic module. This role is associated with external applications that · Decrypt Data: This service TDES or AES decrypts connect via the module's ciphertext data passed into the cryptographic module. XML interface. · Sign Data: This service digitally signs data with RSA. This user is allocated all cryptographic services for · Verify Data: This service verifies the digital signature with keys that they have RSA. permission to access, such as encrypt data, decrypted · MAC Verify Data: The module enters this state when a user data, sign data, and verify wants to MAC verify a block of data. data. · MAC Data: The module will enter this state when a user wants to MAC a block of data. · Query Key Names: This service allows a User to output the list of key names and meta data that he/she is allowed to access. · Download Certificate: This service allows a User to download a certificate into the module. · Query Key Meta Data: This service allows a User to output the following key information that he/she is allowed to access: key length, whether a key is exportable, whether a key can be deleted by current user, key permissions, and supported algorithms and modes for a key. · Generate Random Bytes: This service allows a User to generate and return random data up to 217 bytes. · Authenticate User: This service allows an operator to authenticate into the User role with a username and password. Authentication into the User role may also Page 10 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 require an SSL tunnel to be created. None of the above services can be accessed until an operator successfully authenticates into a User role. · Export Key: This service allows a User to export encrypted cryptographic keys. Cryptographic-Officer: · Key Management: This service allows a CO to manage all cryptographic keys that are stored with in the module. This This role is associated with includes, the generation, storage, export (only public keys human administrators who can be export directly), import, and zeroization of keys. can access the module via the Web Management · Update Firmware: This service allows a CO to upgrade the Console and/or the CLI. module's firmware. This role provides all · Cluster Management: This service allows a CO to manage services that are necessary clusters. This includes the creation, joining, and removal of for the secure management a cluster from the module. of the module. · Service Management: This service allows a CO to manage all services that the module supports. This includes the starting and stopping of all services. · Enable/Disable FIPS Mode: This service allows the CO configure the module into its FIPS validated configuration. · Operator Management: This service allows a CO to create, modify, or delete module operators. The operators include Cryptographic Officers and Users. · Reset Factory Settings: This service allows a CO to rollback to the default image that was shipped with the module. · Restore Default Configuration: This service allows a CO to delete the current configuration file and restore the default configuration settings. · Restore Configuration File: This service allows a CO to restore a previously backed up configuration file. · Backup Configuration File: This service allows a CO to back up a configuration file · Migrate DB: This service allows a CO to encrypt and decrypt columns from a specific database. · Certificate Management: This service allows a CO to Page 11 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 create/import/revoke certificates within the module. · Authenticate Administrator: This service allows an operator to authenticate into the Administrator role with a username and password. · Zeroize Key(s): This service allows a CO to delete a specific key. Cluster Member: · Receive Configuration File: This service allows a Cluster Member to update the module's configuration settings. This role is associated to other DataSecure Servers · Zeroize Key(s): This service allows a Cluster Member to that can connect to this delete a specific key. module to create a cluster. · Backup Configuration File: This service allows a Cluster Member to back up a configuration file. · Authenticate Cluster Member: This service allows another module to authenticate into the module as a Cluster Member via an SSL tunnel. None of the above services can be accessed until another module is authenticated into the Cluster Member role. Ingrian User: · Authenticate Ingrian User: This service allows an operator to authenticate into the Ingrian User role with a signed This role is associated with token. None of the below services can be accessed until an an Ingrian employee who operator has successfully authenticated as an Ingrian User. can bring the module back into an "uninitialized state" · Restore Default Configuration: This service allows an in the event that the all CO Ingrian User to delete the current configuration file and passwords are lost. restore the default configuration settings. · Reset Factory Settings: This service allows an Ingrian User to rollback to the default image that was shipped with the module. · Zeroize Key(s): This service will automatically zeroize all keys when Restore Default Configuration and Reset Factory Settings are activated Page 12 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 File Encryption User: · Authenticate File Encryption User: This service allows the File Encryption Connector to authenticate into the module This role is associated with as a File Encryption User via a TLS tunnel. None of the the File Encryption below services can be accessed until the File Encryption Connector. Connector is authenticated into the File Encryption User role. · Request/Export Encrypted Key and Metadata: This Service allows a File Encryption User to request encrypted AES keys and metadata associated with the key. · Push Log Information: This service allows a File Encryption User to push log files to the module regarding key usage by the File Encryption Connector. Unauthenticated Services: The cryptographic module supports the following unauthenticated services: · Health Status: This service provides the current statistics of the cryptographic module; · Self-tests: This service executes the suite of self-tests required by FIPS 140-2. · SNMP statistics; · Initiation of authentication mechanisms (e.g. TLS, SSH); · Version negotiation of XML protocol. Page 13 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Table 5 - Specification of Service Inputs & Outputs Service Control Input Data Input Data Output Status Output Encrypt Data Encrypt Plaintext data Ciphertext data Success/fail Command Key name Algorithm Parameters Decrypt Data Decrypt Ciphertext data Plaintext data Success/fail Command Key name Algorithm Parameters Sign Data Sign Command Data to be signed Signed data Success/fail Key name Algorithm Parameters Verify Data Verify Data with signature None Success/fail Command Key name Algorithm Parameters MAC Verify MAC Verify Data to be verified None Success/fail Data Command with MAC Key name Algorithm Parameters MAC Data MAC Data Data to be MAC-ed MAC-ed data Success/fail Command Key name Algorithm Parameters Page 14 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Service Control Input Data Input Data Output Status Output Export Key Export Key Key name Exported key Success/fail Command Query Key Query Key None Key meta data Success/fail Names Names for all keys Command accessible by user Download Download Certificate name Certificate Success/fail Certificate Certificate Command Query Key Meta Query Key Meta Key name Key meta data if Success/fail Data Data Command accessible by user Generate Generate Number of random Random bytes Success/fail Random Bytes Random Bytes bytes Command Authenticate Authenticate Username/Password None Success/fail User User Command and/or Certificate Key Key Key name Key Permissions Success/fail Management Management Command Algorithm Public Key parameters Key permissions Key to be imported Update Update New image None Success/fail Firmware Firmware Command Cluster Cluster Cluster keys Cluster keys Success/fail Management Management Command Configuration file Configuration file Cluster commands Page 15 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Service Control Input Data Input Data Output Status Output Certificate Certificate Certificate Name Certificate Success/fail Management Management Command Common Name Key Size Certificate Duration Service Service Service name None Success/fail Management Management Command Enable/Disable Enable/Disable Configuration None Success/fail FIPS mode FIPS mode settings Command Operator Operator Operator password Operator Success/fail Management Management permissions Command Operator permissions Operator name Reset Factory Reset Factory None None Success/fail Settings Settings Command Restore Default Restore Default None None Success/fail Configuration Configuration Command Restore Restore Configuration file None Success/fail Configuration Configuration File File Command Backup Backup Configuration Configuration Success/fail Configuration Configuration settings file File File Command Page 16 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Service Control Input Data Input Data Output Status Output Migrate DB Migrate DB Database Encrypted Success/fail Command Column or Table Name Decrypted Column Column Name Encrypted Column or Plaintext Column Receive Receive New configuration None Success/fail Configuration Configuration file File File Command Zeroize Key(s) Zeroize Key Key name None Success/fail Command Authenticate Authenticate Cluster certificate None Success/fail Cluster Member Cluster Member Command Authenticate Authenticate Ingrian user None Success/fail Ingrian User Ingrian User certificate Command Authenticate Authenticate Username/password None Success/fail Administrator Administrator command Authenticate Authenticate File Encryption None Success/fail File Encryption File Encryption User certificate User User Command Request/Export Request/Export Configuration Encrypted Key Success/fail Encrypted Key Encrypted Key request2 and Metadata and Metadata and Metadata Command Push Log Push Log Log File None Success/fail Information Information command 2 Note that as the File Encryption User has already authenticated the only configuration that can be passed is the one associated with the authenticated user. Page 17 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Definition of Critical Security Parameters (CSPs) The following are CSPs contained in the module: Table 6 - Specification of Critical Security Parameters Key Description/Usage AES Key AES 128, 192, 256 key used to encrypt/decrypt input data. TDES-EDE Key TDES 168, 112 key used to encrypt/decrypt input data. HMACSHA1 Key HMAC key used to hash/verify input data. RSA 2048 Key Private part of a 2048 bit RSA key pair used for signing input data. RSA 1024 Key Private part of a 1024 bit RSA key pair used for signing input data. TLS RSA Key Private part of 1024/2048 bit RSA key pair used for TLS server 1024/2048 authentication and key transport. These certs are used for the Web Administration, User Cryptographic and Cluster services. TLS session keys 128 or 256 bit AES or 168 bit TDES keys; HMAC SHA-1 key CA RSA Key The private part of the RSA key pair used for signing X509 CSR and/or 1024/2048 CRL CO Password Used to authenticate COs. User Password Used to authenticate Users. DSA key 160-bit DSA private key SSHv2 Diffie- 1024-bit Diffie-Hellman private key Hellman key SSH session keys 168-bit TDES keys, 128-bit AES keys, 192-bit AES keys, or 256-bit AES keys ; HMAC SHA-1 keys SSH RSA key 1024-bit RSA private key Page 18 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Definition of Public Keys: The following are the public keys contained in the module: Table 7 - Specification of Public Keys Key Description/Usage RSA 1024 Public Public part used for verifying signatures. Key RSA 2048 Public Public part used for verifying signatures. Key TLS RSA Public Public part of 1024/2048 bit RSA key pair used for TLS server Key 1024/2048 authentication and key transport. These certs are used for the Web Administration, User Cryptographic and Cluster services. CA RSA Public Key The public part of the RSA key pair used for verifying signatures on 1024/2048 X509 certificates. Software Upgrade 1024 bit RSA public key used for verifying signatures on Software RSA Public key Upgrades. SSH Diffie-Hellman 1024-bit public key Public Key SSH DSA Public 1024-bit DSA public key Key SSH RSA Public 1024-bit RSA public key Key Ingrian User 1024-bit RSA public key Verification Public Key CO Verification Optional 1024-bit RSA public key Public Key User Verification Optional 1024-bit RSA public key Public Key Cluster Member 1024-bit RSA public key Public Key File Encryption User 1024-bit RSA public key Public Key Page 19 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Definition of CSPs Modes of Access Table 6 defines the relationship between access to CSPs and the different module services. The modes of access shown in the table are defined as follows: Table 8 ­ CSP Access Rights within Roles & Services Authorized Role(s) Service Cryptographic Keys and CSPs Access Operation User Encrypt Data Select AES or TDES-EDE Key User Decrypt Data Select AES or TDES-EDE Key User Sign Data Select RSA 1024 or 2048 User Verify Data Select RSA 1024 or 2048 User MAC Verify Data Select HMACSHA1 User MAC Data Select HMACSHA1 User Export Key Select any of the following keys: - AES or TDES-EDE - HMACSHA1 - RSA 2048 - RSA 1024 - DES-EDE3-CBC - CA RSA Key Pair 1024/2048 Wrap the above key with SSH session keys or TLS session keys. User Query Key Names Select any of the keys in Table 6. User Download Certificate Select any of the public keys in Table 7. Export public key. User Query Key Meta Data Select any of the keys in Table 6. User Generate Random Bytes None. User Authenticate User Select User Password Generate TLS or SSL session Page 20 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Authorized Role(s) Service Cryptographic Keys and CSPs Access Operation keys Cryptographic Officer Authenticate Administrator Generate TLS or SSL session keys Select CO Password Cryptographic Officer Key Management Select any of the keys in Table 6 an perform the following: - Generate selected key - Zeroize selected key Cryptographic Officer Update Firmware Select CA RSA Public Key 1024/2048 Cryptographic Officer Cluster Management Cryptographic Officer Service Management None. Cryptographic Officer Enable/Disable FIPS mode None Cryptographic Officer Operator Management None Cryptographic Officer, Reset Factory Settings Zeroizes all secret and private Ingrian User keys. Cryptographic Officer, Restore Default Configuration Zeroizes all secret and private Ingrian User keys. Cryptographic Officer Restore Configuration File None Cryptographic Officer, Backup Configuration File None Cluster Member Cryptographic Officer Migrate DB Select AES or TDES-EDE Key Encrypt with selected key Decrypt with selected key Cryptographic Officer Certificate Management Select RSA 1024 or 2048 Cluster Member Receive Configuration File Select AES or TDES-EDE Key Cryptographic Officer, Zeroize Key(s) Zeroizes selected key Cluster Member, Ingrian User Cluster Member Authenticate Cluster Member Select TLS RSA Public Key Page 21 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 Authorized Role(s) Service Cryptographic Keys and CSPs Access Operation 1024/2048 Ingrian User Authenticate Ingrian User Ingrian User Verification Public Key File Encryption User Authenticate File Encryption User File Encryption User Verification Public Key File Encryption User Request/Export Encrypted Key and AES key Metadata File Encryption User Push Log Information None 7. Operational Environment The FIPS 140-2 Area 6 Operational Environment requirements are not applicable because the device does not contain a modifiable operational environment. 8. Security Rules The example cryptographic module's design corresponds to the example cryptographic module's security rules. This section documents the security rules enforced by the cryptographic module to implement the security requirements of this FIPS 140-2 Level 2 module. 1. The cryptographic module shall provide five distinct operator roles. These are the User role, Ingrian role, Cluster User, Cryptographic-Officer, and the File Encryption User Role. 2. The cryptographic module shall provide identity-based authentication. 3. When the module has no valid roles logged in, the operator shall not have access to any cryptographic services. 4. The cryptographic module shall perform the following tests: A. Power up Self-Tests: 1. Cryptographic algorithm tests: a. TDES Known Answer Test b. AES Known Answer Test c. DRNG Known Answer Test d. SHA-1 Known Answer Test e. HMAC-SHA-1 Known Answer Test f. RSA Sign/Verify Known Answer Test Page 22 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 g. DSA Sign/Verify Known Answer Test 2. Software/Firmware Integrity Test (CRC-16 and RSA signature verification) B. Conditional Self-Tests: 1. Continuous Random Number Generator (RNG) test ­ performed on NDRNG and DRNG 2. DSA Pairwise Consistency Test 3. RSA Pairwise Consistency Test 4. Software/Firmware Load Test 5. At any time the cryptographic module is in an idle state, the operator shall be capable of commanding the module to perform the power-up self-test by power cycling the module. 6. Prior to each use, the internal RNG shall be tested using the conditional test specified in FIPS 140-2. 7. Data output shall be inhibited during key generation, self-tests, zeroization, and error states. 8. Status information shall not contain CSPs or sensitive data that if misused could lead to a compromise of the module. 9. The module shall support concurrent operators. 10. The hot swappable hard drives in the i416 and i426 shall not be removed or replaced. 9. Physical Security Policy Physical Security Mechanisms The multi-chip standalone cryptographic module includes the following physical security mechanisms: · Production-grade components and production-grade opaque enclosure with tamper evident seals (for all module configurations) and locks on the front bezel (for the i416 and i426 configurations). Table 9 ­ Inspection/Testing of Physical Security Mechanisms Physical Security Recommended Frequency of Inspection/Test Guidance Mechanisms Inspection/Test Details Tamper Evident Seals and 6 months Inspect the seals and or locks locks on the front bezel on the front bezel, and the seals on the removable doors Page 23 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 10. Mitigation of Other Attacks Policy The FIPS 140-2 Area 11 Mitigation of Other Attacks requirements are not applicable because the DataSecure Appliance is not designed to mitigate any specific attacks outside the scope of FIPS 140-2. 11. References National Institute of Standards and Technology (NIST), FIPS Pub 140-2, Security Requirements for Cryptographic Modules, May 25, 2001. 12. Definitions and Acronyms AES ­ Advanced Encryption Standard ANSI ­ American National Standards Institute BIOS ­ Basic Input/Output System CA ­ Certificate Authority CBC ­ Cipher-Block Chaining CLI ­ Command Line Interface CO ­ Cryptographic Officer CPU ­ Central Processing Unit CRC ­ Cyclic Redundancy Check CRL ­ Certificate Revocation List CSP ­ Critical Security Parameter CSR ­ Certificate Signing Request DB ­ Database DES ­ Data Encryption Standard DRNG ­ Deterministic Random Number Generator DSA ­ Digital Signature Algorithm EDE ­ Encrypt-Decrypt-Encrypt HMAC ­ Keyed-Hash Message Authentication Code MD5 ­ Message Digest Algorithm 5 NAE ­ Network Attached Encryption NDRNG ­ Non-Deterministic Random Number Generator RAID ­ Redundant Array of Independent Drives RAM ­ Random Access Memory Page 24 Ingrian Networks DataSecure Appliance i416, i426, and i116 Security Policy Version 1.3 September 7, 2007 RC4 ­ Rivest Cipher 4 RSA ­ Rivest, Shamir, Adelman SATA ­ Serial Advanced Technology Attachment SHA ­ Secure Hash Algorithm SNMP ­ Simple Network Management Protocol SSH ­ Secure Shell SSL ­ Secure Sockets Layer TDES ­ Triple-Data Encryption Standard TLS ­ Transport Layer Security VGA ­ Video Graphics Array XML ­ Extensible Markup Language Page 25