Welcome to our user's guide for the family of Raptor products. Raptor designed its products as a response to customers' need for far greater network security. Since security was not an issue when TCP/IP was designed, there are many security holes in the TCP/IP suite of communication protocols. There are also many ways that a user can achieve privileged status and bypass system-mandated security policies.
Since the Eagle (and its associated product, the Eaglet) limit the allowed network services to our modified versions of ftp (file transfer) and telnet (remote login) daemons, and since all network packet headers are rewritten to enforce security for the local network, expectation theory can demonstrate mathematically provable levels of security. The Eagle family greatly simplifies the number of system dependent procedures and checklists that your administrator must follow, in essence providing maximum security with minimum inconvenience.
An Eagle consists of two discrete processors - the gateway (or G) box and the authorization (or A) box. The two systems are connected by a private, non-network link. The link is not network accessible, even to privileged users on the gateway box. The A box can thus be physically secured. All connections must be approved by the G box per rules of access contained in an authorization rule database that resides on the A box. There is no way the A box's rules can be accessed from the network. The G box has read-only access, but only via the private link between the two.
Normal users never log onto either system; it is used only as a transit relay. As such, there is no opportunity for them to break the system. Should someone ever determine a way around this, a second level of security is incorporated in the Eagle which constantly examines the integrity of the A and the G box. If it finds active user logins or other processes it does not recognize as legitimate, it will kill them to assure security. If the Eagle detects that it has been tampered with, it shuts itself down, preventing all remote network access until a verifiably correct version has been reloaded.
The operational phases of the Eagle are illustrated in figure
.