Non-Proprietary Security Policy, Version 2.0
June 20, 2007
iDirect Secure Satellite Broadband Solutions
Page 16 of 19
© 2007 iDirect Technologies This document may be freely reproduced and distributed whole and intact including this Copyright Notice.
3 Secure Operation
The Secure Satellite Broadband Solutions meet Level 1 requirements for FIPS 140-2. The sections below describe
how to place and keep the module in a FIPS-approved mode of operation.
3.1 Crypto-Officer Guidance
The Crypto-Officer is responsible for installing, configuring, and monitoring the module.
The Crypto-Officer
accesses the module locally over the console port or remotely over a secured session. Remote secured sessions are
provided via TLS, SSH, or the satellite channel.
3.1.1
Initialization
While the modules are shipped with the Linux OS configured for single user mode, they must be configured for use
in a TRANSEC-enabled network using a TRANSEC enabled Protocol Processor and the iBuilder application. All
network elements that are subsequently created under a TRANSEC-enabled protocol processor will become part of
the TRANSEC-compliant network.
This process involves configuring each respective module in iBuilder (entering the device type, serial number,
Satellite and LAN IP addresses, db threshold, etc.), uploading the resulting `options file', issuing the Certificate
Authority via the CA Foundry utility in the Network Management Server (NMS), un-checking the `Disable
Authentication' option in iBuilder and finally re-uploading the new options file and resetting each module.
The resulting TRANSEC-enabled network operates in the FIPS-approved mode.
In-depth and detailed guidance for configuring, operating, and maintaining an iDirect satellite network is detailed in
the iDirect Network Management System iBuilder's User Guide.
The Crypto-Officer should monitor the module's status by regularly checking the Statistics log information. If any
irregular activity is noticed or the module is consistently having errors, then iDirect Technologies customer support
should be contacted.
3.1.2
Management
According to FIPS 140-2 requirements, the operating system of the module must be configured in the single user
mode. For a Linux operating system to be in the single user mode, it must meet the following requirements
·
All login accounts except "root" should be removed.
·
Network Information Service (NIS) and other named services for users and groups need to be disabled.
·
All remote login, remote command execution, and file transfer daemons should be turned off.
iDirect follows the following procedures to configure Linux operating system in single user mode.
1.
Log in as the "root" user.
2.
Edit the system files /etc/passwd and /etc/shadow and remove all the users except "root" and the pseudo-
users. Make sure the password fields in /etc/shadow for the pseudo-users are either a star (*) or double
exclamation mark (!!). This prevents login as the pseudo-users.
3.
Edit the system file /etc/nsswitch.conf and make "files" the only option for "passwd", "group", and
"shadow". This disables NIS and other name services for users and groups.
4.
Reboot the system for the changes to take effect.
When the module is received by the Crypto-Officer, the Linux operating system has already been configured in the
single user mode. It is suggested that the Crypto-Officer confirm that the above steps have been taken in order to
ensure that the operating system is in fact running in single user mode.