A network prevents unauthorized users from gaining access to confidential information. The network has various workstations and servers connected by a common medium and through a router to the Internet. The network has two major components, a network security Center (NSC) and security network interface cards or devices. The NSC is an administrative workstation through which the network security officer manages the network as a whole as well as the individual security devices. The security devices are interposed, between each of workstation, including the NSC, and the common medium and operate at a network layer (layer 3) of the protocol hierarchy. The network allows trusted users to access outside information, including the Internet, while stopping outside attackers at their point of entry. At the same time, the network limits an unauthorized insider to information defined in their particular security profile. The user may select which virtual network to access at any given time. The result is trusted access to multiple secure Virtual Private networks (VPN), all from a single desktop machine.
|
17. A security device for a multi-level secure network implementing security at a network layer (layer 3) of protocol hierarchy having a plurality of host computers accessible to users and connected to a computer network medium, said security device connectable between at least one host computer bus and the network medium, wherein said security device comprises a local bus, a network interface for connecting said local bus to the computer network medium, and a communication separation means for connection between said local bus and said host bus and for preventing direct pass-through of signals between said host bus and said local bus, said communication separation means including a memory device for storing information provided over said host bus in a memory space, and means for switching said information from said memory space to said local bus while making said switched information inaccessible to said host bus.
1. A security device for connecting a host computer from a host bus to a network accessible to other host computers, the security device comprising a local bus, a network interface connecting said local bus to the network, and a two-port memory device connecting said local bus to the host bus including a first port coupled to said host bus, a second port coupled to said local bus, and a ram connected between said first and second ports, said ram storing information provided over said host bus in a host bus memory space and storing information provided over said local bus in a local bus memory space wherein information to be transferred from the host bus to the local bus is written to said host bus memory space and then transferred out of host bus memory space into local bus memory space in advance of security processing, said transferred information being invisible to said host bus, said security device further comprising a central processing unit connected with said local bus, said central processing unit having associated firmware, and a security device local ram, said central processing unit transferring information out of said local bus memory space of said two-port memory device into said security device local ram in accordance with a predetermined security policy.
7. A security device for connecting a host computer from a host bus to a computer-accessible network, the security device comprising a local bus, a network interface for connecting said local bus to the computer network, and a communication separation unit for connection between said local bus and said host bus, said communication separation unit including a first port coupled to said host bus, a second port coupled to said local bus, and a signal storage device interconnecting said first and second ports, said signal storage device storing signals provided over said host bus in a host bus memory space and over said local bus in a local bus memory space, wherein said signals are switchable between said host bus memory space and said local bus memory space with said switched signals from said host bus memory space being invisible to said host bus after being switched to said local bus memory space, said communication separation unit preventing pass-through of signals between said host bus and said computer-accessible network without transitory storage in said signal storage device, said security device further comprising security device processing means and a local ram, said security device processing means for transferring signals between said local bus memory space of said signal storage device and said local ram.
19. A security device for a multi-level secure network implementing security at a network layer (layer 3) of protocol hierarchy having a plurality of host computers accessible to users and connected to a computer network medium, said security device connectable between at least one host computer bus and the network medium, said security device comprising
a local bus, a local ram, and a local processor; a network interface for connecting said local bus to the computer network medium and including a network processing means for transferring information between said local ram and said network medium; a communication separation means for connection between said local bus and said host bus and for preventing direct pass-through of information between said host bus and said local bus and for preventing direct access between said host bus and components within said security device, said communication separation means including a memory device for storing information provided over said host bus in a memory space, a first port interconnecting said host bus and said memory device, and a second port interconnecting said local bus and said memory device, said information transferrable from said memory space to said local bus while making the transferred information inaccessible to said host bus; wherein said local processor processes information to be transferred between said host bus and said network medium in accordance with a predetermined security policy to determine whether communication between a host computer and the network medium is authorized, said local processor including means for accessing host bus information from said memory space of said communication separation means, processing said host bus information in accordance with said security policy, transferring the processed host bus information to said local ram for access by said network processing means, accessing network medium information placed in said local ram by said network processing means, processing said network medium information in accordance with said security policy, and transferring the processed network medium information to said communication separation means for access by said host bus.
3. The security device of
5. The security device of
6. The security device of
10. The security device of
12. The security device of
14. The security device of
16. The security device of
18. The security device of
20. The security device of
21. The security device of
22. The security device of
|
|||||||||||||||||||||||||||||||||||
The present invention relates to a multi-level security network system. More particularly, the present invention relates to a secure communication between hosts using a network that implements a security policy, and especially a network allowing multiple levels of information to coexist on a network system.
The National Security Agency (NSA) has set forth specific definitions and requirements that establish various levels of security in computer and network systems. These basic definitions are set forth in "Trusted Computer System Evaluation Criteria," Department of Defense, 1985 (TCSEC) and "Trusted Network Interpretation of the Trusted computer System Evaluation Criteria," National Computer Security Center, 1987 (TNI). These documents define the requirements for systems to be evaluated in one of six hierarchical ratings: C1, C2, B1, B2, B3, and A1, with C1 being the least secure and A1 the most secure.
Division B, that is, ratings B1, B2, and B3, introduces the requirements for multi-level secure (MLS) systems. The term "multi-level security" refers to a system in which two or more classification levels of information are processed simultaneously, and not all users are cleared for all levels of information present. This same concept was applied during the 1980's to networked systems, at which time the phrase MLS network was generally used to refer to a network that was capable of simultaneously transmitting data at multiple security levels when some hosts or users were not cleared for all levels of data.
In order for an MLS network to qualify as a B-level secure network, it must provide at least the following five security functions: (1) access control, (2) object reuse, (3) labeling, (4) identification and authentication (I&A), and (5) auditing. Open Systems Interconnection (OSI) sets forth industry standard definition of seven layers of network connection: (1) physical, (2) data link, (3) network, (4) transport, (5) session, (6) presentation, and (7) application.
The first criteria, "access control," is concerned with the enforcement of rules (security policy) by which active subjects (e.g., processes, hosts) access passive objects (for example, files, memory, and devices). In a network system, operating at the OSI network layer of the protocol hierarchy, access control is concerned with the access of hosts to network packets. Rule-based Mandatory Access Control (MAC) is concerned with preventing each host from transmitting or receiving data at the wrong level. Discretionary Access Control (DAC), on the other hand, is concerned with ensuring that a host computer can only establish authorized connections to other hosts.
The second criteria, "object reuse" is concerned with preventing inadvertent release of residual data, typically in unused fields or at the end of a packet buffer. "Labeling" of each packet is necessary in a distributed system to convey the sensitivity of data to the various elements of the network. "Identification and Authentication" (I&A) is concerned with establishing individual accountability for authorized users. "Audit" is concerned with recording information about the use of the network's security mechanisms, to further support the requirement of user accountability.
In addition to these five basic requirements, a secure network should also provide two other capabilities, communications secrecy and communications integrity. These additional requirements support the secure transfer of MLS labeling and control information in an open environment, such as the Internet. Communications secrecy is provided by appropriate use of encryption to transform user data and control information so that it is unintelligible to wiretappers. Encryption is a process that scrambles or transforms sensitive data within messages (either an entire message, or part of a message) to make them unreadable to any recipient who does not know a secret string of characters, called a key.
Communications integrity, on the other hand, is concerned with detecting modification of data, such as security labels, and user data, as it traverses the network. Packet integrity has also been accomplished by calculating cryptographic checksums of packet headers and packet data. The receiving node can straightforwardly detect message modification to a high degree of probability by recalculating the cryptographic checksum on the received data, and comparing it to the received checksum.
The current approaches to MLS networking include Verdix VSLAN (which has subsequently changed to GKI, then to Cryptek Secure Communications VSLAN), Boeing MLS LAN and ITT networks.
The Verdix Secure Local Area Network (VSLAN) product was developed by Verdix Corporation in the 1980s. VSLAN was the first network product evaluated by the TNI criteria and the first commercial network product to provide MLS security. VSLAN is the only commercial network product available with a B2 rating. However, VSLAN operates at the link layer (layer 2) of the protocol stack and, thus, its security mechanisms are limited to the scope of a local area network. While VSLAN uses Data Encryption Standard (DES) for communications integrity, it cannot be used on an open network because DES is not sufficiently strong to protect classified data.
The Boeing MLS LAN has received an A1 security rating with respect to the TNI. It does not provide any encryption, but relies on physical protection of the medium to protect data in transit.
The ITT network security is described in U.S. Pat. No. 5,577,209 to Boyle et al. ("Boyle"). Boyle uses cryptographic sealing techniques to support MLS labeling and mediation. The approach operates at the session layer (layer 5) of the OSI protocol reference model. Boyle, however, does not provide encryption of data for purposes of secrecy. Consequently, classified data could be accessed by passive wiretapping or by use of readily available tools, such as tcpdump running on any host in any of the intermediate networks.
Most protocol architectures do not have a protocol implementation that uses a distinct session-layer protocol. Rather, for protocols commonly used on the Internet, application programs (layer 7) interface directly to the transport layer (layer 4) of the protocol hierarchy. For these two reasons, Boyle is not very useful with real classified data on real networks, such as the Internet.
Over the past 15 years, computer security and network security have progressed on separate tracks. Computer security has generally been concerned with the evaluation of standalone computer systems, without networking, at a time when the Internet was exploding. With the exception of a few TNI-evaluated products, network security has concentrated on the use of cryptography (particularly public key cryptography) and firewalls. Cryptography has been used to provide secrecy and integrity, largely without regard for the security of the communicating systems.
Various methods and devices have been used to enhance network security, including firewalls, identification and authentication (I&A), intrusion detectors, and virtual private networks (VPN).
Firewalls have been used to protect an organization's internal resources from the external Internet by passing certain protocols (e.g., email, name services) into the protection perimeter, but filtering out all protocols not explicitly listed. The firewalls attempt to isolate a company's intranetwork from the remainder of the Internet. Firewalls provide proxy servers that stand between the external network and internal resources and that pre-validate external requests.
However, firewalls are only intended to protect internal resources from outsiders. As a result, firewalls offer no protection against an internal attack upon those same resources. Firewalls are generally subject to impersonation, in which an intruder's host is programmed to use an IP address of one of the network computers, or an attacker may know the password of one of the trusted users. Firewalls are also subject to session stealing, in which the intruder takes over an authorized session, together with all access modes established for the authorized user.
Firewalls may provide an IP tunneling capability to provide encrypted channel across the Internet to another part of the company's intranetwork. However, a major problem with firewalls is that once an unauthorized user is "in" to a host of the internal network, it is possible to use that host as a point for attacking other hosts within that network.
I&A devices generally involve the use of passwords for a user on one host to gain access across a network to another host. I&A may also be implemented by the use of a Personal Identification Number (PIN) and device to authenticate the user. The I&A device may be hardware using smart card technology that either takes a challenge and calculates a response or uses some clock-based synchronization to ensure that the I&A data passed across the network is unique from one access attempt to another. I&A may also be implemented in software.
However, the use of I&A mechanisms does not address mediation (MAC, DAC) in any way, nor does it address the use of encryption or packet integrity on a stream of packets from one host to another. Furthermore, the risks of reusing a password across a network are obvious, given the availability of public domain software to grab packets as they traverse internal networks. Once an attacker (whether inside or outside the network) is able to send packets to your host, there are other attacks, such as routing via your host to another host, or sending packets to unprotected TCP/UDP ports, that could jeopardize the operation of any host on the network.
An intrusion detector generally involves the use of a "sniffer," such as tcpdump or hardware that snoops packets on the internal network, that attempts to detect and react to malicious behavior. However, intrusion detectors only provide detection, and not prevention. That is, the detectors cannot prevent an intrusion, but only detect that an intrusion has occurred. Intrusion detectors also do not provide a way for mediating the flow of packets, protecting packet secrecy, or protecting packet integrity.
Virtual private networks (VPNs) are implemented by firewalls with encryption between different sites of a network or local area network (LAN). Some VPNs provide software-based encryption that runs on the individual host computers of the network. Generally, a VPN may be defined as a private network that exists within a larger, open network and uses methods (such as encryption) to make the network private.
Site-Level VPNs have the classic problems of firewalls. That is, they do not protect internal communications, and are susceptible to session stealing and sniffing on local and remote networks. An encrypted path between two sites may shut out an external attacker, but an internal attacker on the LAN has free rein to attack any host in that network, as well as any host in any of the other related LAN sites.
Software-based host level VPNs provide a driver that sits between the ethernet driver and the TCP/IP protocol stack. These VPNs offer some of the distributed advantages of having a firewall-at-each-host architecture, but do not have an architectural basis for protecting the hosts. The software VPN can be bypassed, for instance, if an application process on the host can communicate directly with the NIC driver via the OS on that host, instead of using the software VPN interface. Software VPNs may also be disabled or modified by processes running with privilege (e.g., the UNIX root user or its equivalent on NT boxes). It relies on the host OS for protection, and not all hosts provide equivalent protections, so a node with a weak OS could be used as a location to launch attacks against other hosts.
Therefore, it is a primary object of the present invention to overcome the limitations of the conventional security mechanisms. It is a further object of the invention to provide a secure network in which the security mechanisms are at layer 3 of protocol hierarchy. It is another object of the invention to provide a centralized administration of a layer 3 secure network that may be distributed over the Internet. It is another object of the invention to provide a security device that prevents unauthorized third parties from gaining access to a host. It is another object of the invention to provide a multi-level secure network having a security device coupled between each host and the network medium.
In accordance with these and other objectives, the secure network of the present invention, having a commercial name DiamondTEK Ultra, provides a unique implementation of cryptographic technology with high-assurance policy-based enforcement of packet flow. The network prevents unauthorized users from gaining access to sensitive information. Although the network of the present invention has not yet completed evaluation by the NSA, it is designed to satisfy all of the B2 criteria.
The network generally comprises various host computers (such as PCs, workstations, or servers) connected by a common medium. Routers may be used to connect Local Area Networks to public networks, such as the Internet. The network has two major components, a Network Security Center (NSC) and security network interface cards or "security devices."
The NSC is an administrative workstation through which a network security officer manages the security aspects of the system and implemented by the individual security devices. The NSC is responsible for setting up authentication materials and for authorizing individual peer-to-peer and client server associations. In addition, since this is a Multi-Level Secure network, the NSC is responsible for defining the security levels and categories of information permitted on the network and the labeling used by each host.
The security devices are interposed between each host, including the NSC, and the common medium. The security devices enable a host to communicate across the network. Unlike other network security solutions, the security device is designed as a self-contained circuit board that is directly integrated into the hardware of the host system. The architecture of the security device is readily integrated into a variety of hardware environments.
The security devices authenticate principals responsible for host computers that connect to the network. Through use of the security devices and the NSC, the network allows trusted users to access outside information, including the Internet, while stopping outside attackers at their point of entry. At the same time, the network limits an insider to information defined in their particular security profile. The user may select which logical network to access at any given time. The result is trusted access to multiple secure Virtual Private Networks (VPN), all from a, single desktop machine.
The present network simultaneously enforces two independent and complementary types of access control rules: discretionary access control (DAC) and mandatory access control (MAC).
The network further ensures confidentiality and integrity of host-to-host communications by the use of encryption mechanisms. Cryptography provides the underlying secrecy and integrity of communications required for the network to be able to enforce a unique policy when operating over an open backbone network. Various types of cryptography are available, including DES, and Triple-DES for commercial and financial applications, and high-grade Type 1 encryption for classified applications. The network ensures that messages cannot be modified by an unauthorized user, or attacker, through the use of message digests.
The features of the network overcome the problems associated with traditional I&A devices, intrusion detectors, firewalls and VPNs, as well as with previous MLS networks (such as VSLAN, Boeing MLS LAN and the ITT network). The security device is a separate hardware board having a separate CPU, memory, network interface and bus architecture from the application processes on the host. A dual-ported RAM architecture guarantees that no malicious host process can tamper with the internal configuration of the security device. All network accesses must go through a security device, which implement security mechanisms for each and every access attempt. The security devices cannot be bypassed since there is no other path to or from the network.
The network extends the mediation and cyptographic protection offered by a firewall (with its mediation and its cryptographic protection) to the network interface of each individual host computer. This may still permit a malicious user on a particular Bethesda machine to use a permitted association to a host in Tampa to attack that machine, but the network architecture significantly restricts the ability of the attacker to access other hosts. Further, the auditing by the network involved, transparently forwarded to a central collection site at the NSC, can be used to provide accountability, which makes discovery for such attacks more certain.
The network provides hardware based mediation (MAC and DAC) at each host, and provides cryptographic protection (secrecy, integrity) on all host-to-host associations.
As used herein, the term "policy" refers to the control of sensitive and potentially classified data according to the rules of the system as set by the system controller. For example, a host operating at a security level of Secret may transfer data to another Secret host, but is prohibited from sending data to a host operating at a lower classification. Similarly, hosts operating at higher classifications or with additional non-hierarchical categories are prohibited from sending messages to the Secret host.
FIGS. 1-3 show various instances of the secure network having a security device in accordance with the present invention.
FIG. 4 is a diagram of the conceptual network architecture.
FIG. 5 is a diagram of the packet format, including packet labeling, used on the network.
FIG. 6 depicts representative labeling for the hierarchical levels and non-hierarchical categories used by the network.
FIG. 7 is a representation of the transmit and receive windows for communication of information between hosts of the network.
FIG. 8 is a block diagram of the security device.
FIG. 9 is a flow diagram showing the IP packet transmission for the security device.
FIG. 10 is a flow diagram showing the IP packet reception for the security device.
FIG. 11 is a schematic showing conventional network adapter architecture.
FIG. 12 is a schematic showing the host bust interface using a two-port RAM.
FIG. 13 is a block diagram showing the overall structure of the network.
FIG. 14 is an example of how the security device can be used to partition a network (including the Internet) into multiple trusted Virtual Private Networks (VPNs), with the ability to switch a host between VPNs.
In describing a preferred embodiment of the invention illustrated in the drawings, specific terminology will be resorted to for the sake of clarity. However, the invention is not intended to be limited to the specific terms so selected, and it is to be understood that each specific term includes all technical equivalents which operate in a similar manner to accomplish a similar purpose.
Turning to the drawings, FIGS. 1-3 show various embodiments of a security network 10 having a dedicated Network Security Controller (NSC) 12, workstations 14 and servers 16. The NSC 12 permits a Security Officer to configure and audit the operation of the secure network 10. The network 10 also has security devices 18, having the commercial name DiamondNIC, installed between each host (workstation 14 or server 16) and the local area network medium 20 to form a Local Area Network (LAN) 5. The various LANs 5 are connected to an untrusted backbone net 30 by a router 22.
The security device 18 is preferably a Network Interface Card (NIC) that easily replaces a standard NIC card for nodes that contain or need access to sensitive information. The security device is a self-contained circuit board that is directly integrated into the hardware of the host system.
Thus, the security cards 18 operate at the network layer (layer 3) of the protocol stack and provide encrypted, controlled communications from one host (IP address, TCP/UDP port) to another. Because the security mechanisms operate at layer 3, the security mechanisms pertain to the entire Internet address space. Further, the choice of LAN or WAN medium is not relevant to the security provided by the system.
Each security device 18 enforces a mandatory access control (MAC) policy, as well as discretionary access control (DAC) policy, on the flow of packets to and from that host 14, 16. It ensures labeling of all data packets with a hierarchical security level and a set of non-hierarchical security categories appropriate for the local hosts
The DiamondNIC security device 18 provides user identification and authentication (I&A) via a card reader and, keypad (not shown) attached to the device 18. Auditing is provided by the use of embedded firmware within the security device, with audit data directed to the NSC 12 for archival. Finally, the security device 18 uses encryption to provide secrecy and communications integrity on all selected connections.
Hosts that are installed with the DiamondNIC security devices 18 may communicate with like hosts on the internetwork, as permitted by profiles, operating at security levels loaded from the NSC 12. Host software, even malicious host software, cannot bypass the security mechanisms (mediation, auditing, encryption) provided by the security device 18 because the security mechanisms are embedded within the device 18 itself and all network communications must pass through the security device 18 in order to access the network.
The network 10 provides the same capabilities as firewalls, with several additional advantages. The network 10 extends the firewall concept to each individual host in the intranet. Thus, the policy enforced for each host is the policy required for that host, not a one-size-fits-all policy imposed by a single firewall. The network 10 also provides centralized network control, which permits hosts to be switched from one security profile to another, without risk that information may leak across security levels. This network security architecture makes an NSA B2 security rating possible.
To be effective, security mechanisms should be derived from the security threats that affect an organization. All security threats generally are concerned with the unauthorized disclosure of sensitive information or the modification of data. The primary threats for an organization processing sensitive data within a networked system, and particularly a networked system interconnected with the Internet, are disclosure, downgrading, passive wiretapping, active wiretapping, downloaded software, and covert channels.
In a classified environment, the threat of disclosure includes the ability to read data that is classified above the user's current level. In a classified environment, the threat of downgrading includes writing data to a lower classification than the user's current level. These threats are addressed by appropriate use of multi-level security (MLS) technology.
Passive wiretapping includes monitoring at intermediate sites, using tools such as tcpdump, as well as attaching devices to monitor the communications medium. The network counters the threat of passive wiretapping by appropriate use of encryption.
Active wiretapping, also known as message stream modification, includes the modification of selected data (e.g., monetary amounts) within a packet, insertion of new packets into the data stream, playback of packets, and deletion of selected packets. Network control, as well as user data connections, can be attacked. This is countered by appropriate use of cryptographic checksums.
Cryptographic checksums are used to calculate an error detection code on a block of data, using encryption and a secret key. If two communicating hosts each calculate the same code, then there is a very high probability that the data was not modified in transit.
The threat of downloaded software includes viruses, malicious programs, Java code, and other software that can be downloaded by a trusted host from potentially malicious hosts. This is addressed in the present network by ensuring that hosts interact only with other trusted hosts operating at the same classification.
A covert channel exists when a high-level process manipulates a shared resource or modulates the rate at which data is sent, to signal data to a lower-level process. There are two types of covert channels, timing and storage. Covert channels, however, are much less a problem in a network environment than on a standalone computer, but still must be addressed in MLS systems. Secure networks cannot entirely stop covert channels between communicating hosts.
The network 10 architecture essentially comprises a specialized NSC 12 host dedicated to configuring and auditing the secure network and a DiamondNIC network security device 18 installed between each host computer and the network medium 20.
Hosts, Users, and Principal
The network over which the security device 18 communicates actually enforces security with respect to network hosts. A principal is an individual that authorizes one or more users to access the network from a given host system, subject to a certain security profile (mandatory and discretionary access control rules). The network can be configured by the network security officer such that a single host may have more than one principal. Hence, each principal must complete an identification and authentication (I&A) procedure before the host is permitted to communicate over the network.
When the I&A procedure has been completed, the security device 18 communicates with the NSC and downloads the principal's operational profile--the combination of association lists (for discretionary access control) and security windows (for mandatory access control)--from the NSC. From that point onward, the security device securely transmits and receives data over the network independently and transparently, relying upon its own CPU to avoid depriving the host of processing bandwidth. The bandwidth may be needed to offload processing, such as encryption. More importantly, however, independent transmission by the security device also prevents the host software from being able to bypass the security mechanisms.
The security device will only send and receive messages if the communication has been specifically authorized in the operational profile assigned by the network security officer. Encryption keys are generated and exchanged as necessary. The VPN is a collection of potentially communicating hosts, such as A, B, C, D and E. Each individual pair has an association, and the virtual private network (VPN) is the collection of all possible associations (e.g., A-B, A-C, A-D, A-E, B-A, B-C, etc.). Each pair of communicating security devices may be said to establish a transparent VPN, whereby every message is automatically encrypted before transmission and decrypted after arrival at its intended destination.
The network security officer may empower each user to access a variety of hosts with different degrees of privilege. For instance, suppose that a certain user is authorized to access the network not only from his desktop PC, but also from a workstation housed within a physically secure laboratory protected by a cipher lock. The NSO can define two operational profiles for the user, thought of as different roles, to give that user more privileges when accessing the network from the physically secure workstation than when connected from the unprotected desktop PC.
In addition, a person may be a principal at different devices with different profiles (that is, security levels and associations) defined for each device. A principal can also be enabled to operate the security device in a bypass or non-secured mode and thereby network non-sensitive data with other hosts that are not individually equipped with a security device.
Conceptual Network Architecture
FIG. 4 depicts the architecture of the system with respect to the trust required in its constituent parts and the OSI layers in the protocol hierarchy where these functions reside. Region A includes the physical layer communications links, link layer protocols, repeaters, bridges, and intermediate routing hosts. The hardware and software in this region need not be trusted or physically protected, because of end-to-end mechanisms implemented in Region B.
Region B consists of the trusted devices, where each security device 18 is represented by a diamond-shaped object. The dashed lines indicate that control and auditing of the security devices 18 is implemented wholly within Region B, by the NSC 12. The devices 18 operate within layer 3 of the protocol hierarchy and provide a cryptographic foundation that assures communications secrecy and communications integrity. Any suited cryptographic method may be used, including the Data Encryption Standard (DES) and Triple-DES for commercial and financial applications and ranging to high-grade Type 1 algorithms for government and military applications.
Because the security devices 18 provide communications secrecy appropriate for the information being carried on the network, there is no need to physically or procedurally protect the communications medium in Region A. Any information intercepted by a wiretapper or intermediate host will be unintelligible. In addition, the security devices 18 provide communications integrity mechanisms appropriate for the information being carried on the network. Communications integrity mechanisms include, but are not limited to, keyed message digests (MDS), secure host algorithm (SHA) and message authentication code. Thus, any attempts to modify the host data (IP data field or header) will be detected by the recipient security device 18.
Regions C and D include host computers 14 (either workstations 14 or servers 16), the TCP/IP protocol stack, application programs, and users. The Internet Protocol (IP) runs at layer 3, the Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) run at the transport layer (layer 4) and application protocol (e.g., Telnet, File Transfer Protocol) clients and servers run at layer 7 of the protocol hierarchy.
The distinction between Region C and Region D is that hosts in Region C are trusted MLS computers that are capable of simultaneously processing data at multiple security levels, while hosts in Region D are not capable of simultaneously processing data at multiple security levels. Hosts in Region D may be evaluated according to the U.S. Government Trusted Product Evaluation Program (TPEP) or Trusted Technology Assessment Program (TTAP) programs, the upcoming Common Criteria, or less rigorous programs such as Security Proof of Concept Keystone (SPOCK) or the International computer Security Association (ICSA). These hosts may be multi-user or single-user at a time computers, but are capable of operating only at one security level at a time.
Installation and Profiles
The network 10 is typically installed by first installing the NSC 12 in a secure location, readily available to the security officers. The security device 18 adapters are typically installed in the backplanes of the various host computers, and software drivers, associated with the operating system, are installed on the host computers.
After the network 10 is installed and configured, the Security Administrator defines information about the security devices, their principals, and attached hosts. The administrator adds the information for each of the security devices 18 to a database located at the NSC 12. In addition, the administrator programs an authentication card for the principal with the security device information, including the principal's one-time password. The administrator travels to each of the nodes, and reads in the card to install node-specific information onto the board of the security device.
A principal initializes and uses a node by first going to the node and, using the appropriate I&A means, selects a profile and identifies and authenticates himself/herself to the network. For example, this may include inserting the principal's authentication card in the card reader attached to the security device 18.
The principal also selects a usage profile using the pushbuttons on the front of the card reader. The principal is able to select only among those profiles entered by the security administrator. There can be up to 100 profiles defined for each principal although, in practical use, most principals will have only a few profiles. The selected profile has associated with it a security window and permitted host-to-host associations.
The NSC 12 sends the appropriate security window and associations for the profile to the security device 18. Once the host initializes the device driver, the host transmits packets to the network. The security device 18 mediates each packet according to the security window and authorized associations, then encrypts the packet using the appropriate traffic key.
When the security device 18 detects an attempted security violation, it sends an audit event to the NSC. If authorized, the principal may switch to a different profile, with a different security window and different associations. This permits a principal to easily change from one usage profile to another, as required, among the set of such profiles authorized for the principal.
However, only one profile (that is, security windows and associations) can be in effect at a given security device at any time. Thus, if a principal change profiles by selecting a different profile, the security device is flushed and all data is reloaded. The principal may or may not have to remove the authentication card. The clearing out of the security device is not known by the principal.
The principal shuts down the security device 18 by removing the card (or logging out) and perhaps powering down the system. Throughout this operation, the security device 18 will only transmit or receive packets in accordance with the established current profile. Hence, the principal's profile is preferably configured to prevent access to both classified and public outside information at the same time.
Accordingly, the network allows trusted users to access outside information, including the Internet, while stopping outside attackers at their point of entry. At the same time, the network limits an insider to information defined in their particular security profile. The network preserves the security effects compartmentalization, while making it easy for authorized users to access the information they need. Unlike static VPN solutions, the network lets the user decide which network to access at any given time.
Integrity and Assurance
The network system ensures both confidentiality and integrity of host-to-host communications by the use of encryption and integrity techniques. Encryption is a process that scrambles sensitive messages to make them unreadable to any recipient who does not know a secret string of characters, called a key.
If the network security officer has authorized two hosts to communicate at a given security level, via the use of principal profiles, the security devices 18 perform a key exchange protocol and generate unique keys known only to that pair of security devices 18. These keys are henceforth used to encrypt all communication between the attached hosts at the chosen security level until one of the hosts either shuts down or disconnects from the network or a defined limit of use has been exceeded.
By having the security device automatically encrypt all messages, security of communication across the network is ensured. The user need not remember complex pass phrases and complete an authentication protocol that could be spoofed by Trojan horse software. In addition, by applying encryption at the network layer, rather than at the application layer, the network accomplishes all authentication, key generation, and key distribution functions transparently and effortlessly. An application programming interface may also be provided by the security device 18 to allow the user to encrypt individual files and directories, as well as messages.
The assignment of unique keys to each pair of hosts at each security level offers two advantages. First, the network preferably incorporates various LANs, such as Ethernet and Token Ring, as well as transmitting packets through the Internet, which potentially allows messages to be intercepted by hosts other than the intended recipient. Encryption guarantees that only authorized target hosts can retrieve the information.
Second, if a key should somehow be stolen unbeknownst to the principals that share the key, only a small subset of the total network traffic is compromised. It is noted, however, that the traffic keys are not known even to the principals. The keys are established by the two communicating security devices, and kept in memory inside the two security devices. So, there's no practical way for someone to steal a key. Yet, if someone is snooping packets on the network, and manages to guess the key, the key would only be valid for traffic from one host, to another host, at a particular level.
Additional security may be provided by intermediate hosts on the Internet, such as Internet Service Providers, that run readily available sniffing tools, such as the UNIX tcpdump program to view all packets matching certain filters defined by the wiretapper.
The network 10 further ensures that messages have not been modified by an attacker through the use of message digests, such as cryptographic checksums. As noted above, a message digest is a number that is calculated from the text of the message and is then transmitted along with the message. When the encrypted information is received, the digest calculation is performed anew (for the encrypted data) at the receiving host and compared to the received value of the digest. If the transmitted value and newly calculated value match, the receiving host can be confident that the message was delivered intact.
Cryptographic Protocol Overview
FIG. 5 shows the preferred protocol headers for host-to-host messages and for control messages. All packets have an Ethernet or Token Ring header, as appropriate, with the standard IPv4 (Internet Protocol version 4) header and an IP Security (IPSec) header extension with an Common IP Security Option (CIPSO) label, as specified by RFCs 1825-1829. Different packet formats, as yet unspecified, will be used for the Type 1 model of the security device 18.
The headers (IP, IPSec, CIPSO label, and cryptographic headers) are in clear text while IP data (i.e., TCP or UDP headers and data) are encrypted. RFC 1851 describes the formatting of encrypted packets. Label integrity uses, but is not limited to, DSS, SHA or MD5. This provides protection of both data and control communications. If tunneling is configured for the association, the host's IP header is encapsulated in the encrypted payload. At the receive end, before the packet is decrypted, MAC processing is based on the CIPSO label and DAC processing is based on the sending host's IP address.
Traffic keys are determined by each pair of communicating security device 18 using Internet Engineering Task Force (IETF) key determination based on shared secret information (IKE) or some other recognized process. The NSC 12 can be used as a Certificate Authority. Traffic keys are derived separately for each security level and host.
Key life is determined centrally, based on elapsed time or number of bytes. The NSC 12 defines the key life when the security device 18 is initialized and the security device 18 initiates its own key change when the key life expires. The security devices 18 transfer traffic keys to the NSC (via key generation audit) for short-term archival and potential key recovery.
Individual host-to-host associations may be protected by an appropriate encryption algorithm, as determined by the administrator. All network control communications are protected by the highest level of encryption available to the system. The network 10 also permits a network administrator to designate certain associations as clear-text (unencrypted). This mode of operation permits a host to communicate with other cleartext hosts.
This section describes the Mandatory Access Control (MAC) and Discretionary Access Control (DAC) policies enforced by the security devices 18. It also describes Labeling, Identification and Authentication (I&A), Audit, Object Reuse, and System Architecture as they relate to the policy of the network.
Mandatory Access Control (MAC) Policy
Mandatory access control is implemented through a security window calculation (FIG. 7) at both the sending and receiving hosts. Each message is assigned a level that reflects both its sensitivity (e.g., secret, proprietary) and its handling restrictions (e.g., not releasable to foreign nationals, not releasable to the engineering department). Sensitivity is the combination of a hierarchical level (TopSecret>Secret>Proprietary>SBU>Unclassified) and a non-hierarchical category. Categories may be of the form "X," where X is the name of some project "Corporate Merger" or operation "Desert Storm."
Similarly, for at least single level workstations, each network principal, or authorized user, is assigned a level that reflects the host's trustworthiness to read and properly handle sensitive messages.
Two rules govern the reception and transmission of messages by the host. First, only an authorized host may receive sensitive data over the network. Thus, for instance, a standard PC operating as a host without any added security mechanisms of its own may have a security device configured to operate at Level-Top Secret and Categories=(USNukes, SpySatellites). This configuration would be okay provided that the host is not permitted to transmit any of that onto the network or to receive anything different. Thus, the security window for that host, but not that principal, is closed down so that the host can only SEND TS (USNukes, SpySatellites) and RECEIVE TS (USNukes, SpySatellites).
Second, data that is transmitted is properly labeled so that it will be properly handled by the transmitting host as well as the remote receiving host. If the remote host is also a PC, then its security windows must be closed down to a single point as in the preceding example. The security device ensures that its transmissions are securely labeled. The network security officer is able to determine the specific range of levels, or security window, at which each host is permitted to communicate.
If the remote host is a Mulit-Level Secure computer that is capable of simultaneously processing a range of Secret to Top Secret, then the securtity window can be opened up accordingly. In this sense, the host is then trusted not to mix up the Secret with the Top Secret.
This flexible design permits unsecured hosts to be quickly and easily added to the network 10. These unsecured hosts can freely inter-operate with other unsecured hosts without any restriction. However, secured network hosts will not inter-operate with these unsecured hosts unless the secured hosts are specifically authorized to network non-sensitive data, that is, via a defined security window.
MAC is concerned with preventing each host from receiving data classified above the host's current level ("read up") and transmitting data classified below the hosts's current level ("write down"). The level of a host computer is expressed as a range of hierarchical clearance levels (e.g., Secret, Top Secret) and sets of non-hierarchical categories (e.g., Project1, Operation2000), as determined by the profiles of individuals that: use the computer. Individual host computers may or may not be trusted to handle MLS data.
As shown in FIG. 6, the network 10 is capable of supporting up to 256 hierarchical security levels and at least 65,535 non-hierarchical categories. The security administrator assigns names (e.g., "Unclassified", "Secret") and a hierarchical relationship to the security levels that will be used in the system. Typically, only a few security levels are defined and the rest are unused.
The administrator also assigns names to the non-hierarchical categories, but as the name implies, these can be placed anywhere in the category space. All hosts must use the same labeling conventions on the network, but individual MLS hosts may have different values for a level or category as represented within the operating system.
Referring back to FIG. 4, the network 10 architecture provides an innovative and flexible "security window" mechanism that is capable of supporting both trusted MLS hosts (Region C) and single-level hosts (Region D). For hosts in Region C, the security device 18 can be configured to permit packets labeled at multiple levels, with multiple different sets of categories. There are separate windows for a host's transmissions to the network and the host's receptions from the network. The security window can be closed down to a single authorized level and set of categories, or can be opened up to accommodate multi-level hosts.
As shown in FIG. 7, packets {a, b, c} pass through the origin security device 18 transmit window, while packets {d, e} are labeled below allowable limits (attempts to "write down") and are rejected and audited. For the packets that pass through the sending host's transmit window, the packets are labeled by the sending host and mediated by the sending security device 18. At the destination, only packets {b, c} pass through the receive window while packet {a} is labeled above allowable limits.
As further shown in FIG. 7, in order for data to flow from one host to another, it must satisfy the MAC restrictions enforced by both the sending and receiving security device 18. The diamond shapes in the figure are intended to reflect the lattice organization of a range of security levels and non-hierarchical categories.
More formally, the requirements to transmit data are stated in terms of the dominance relationships. The hierarchical classification in the packet's security label must be greater than or equal to the minimum allowable classification in the host's transmit window. In addition, the packet's security label must be less than or equal to the maximum allowable classification in the host's transmit window.
The non-hierarchical categories in the object's security label include all the categories defined for the lower bound of the host's transmit window and are included in the categories defined for the upper bound of the host's transmit window.
A similar dominance relationship is defined for the receive side of the association. The important point, though, is that the purpose of this is to prevent the sending host from sending data below its actual classification ("write down") and prevent the receiving host from reading data above its authorizations ("read up").
As an example, suppose the labeling space defined for the network includes four hierarchical levels: Unclassified, Confidential, Secret, Top_Secret and Ultra_Secret; and 26 non-hierarchical categories {A, B, C, D, . . . X, Y, Z}. In addition, suppose a B2-evaluated host is operating at a range of levels Secret to Top Secret, with category A required, and categories {D, Z) optional depending on the data processed by the operating system. The security device 18 might be configured to permit any of the labels of Table 1 to be transmitted and received.
| TABLE 1 |
| Level Categories |
| Secret A |
| Secret A, D |
| Secret A, Z |
| Secret A, D, Z |
| Top_Secret A |
| Top_Secret A, D |
| Top_Secret A, Z |
| Top_Secret A, D, Z |
Continuing with our example, the security device 18 may also be configured by the system administrator to reject and audit any of the representative labels shown in Table 2.
| TABLE 2 |
| Level Categories Reason |
| Secret A, B Category B is not |
| permitted |
| Top_Secret A, D, M, Z Category M is not |
| permitted |
| Secret none Must have Category A |
| Top_Secret D, Z Must have Category A |
| Unclassified A Security Level too low |
| Ultra_Secret A, D Security Level too high |
For hosts in Region D, policy dictates that each host must operate at a single level at a time (otherwise it would be a non-MLS host processing more than one level of information). For these single-level hosts, the security window can be collapsed to a single labeling and all packets sent by the host must match that labeling exactly. For simplicity, however, a different option is permitted below.
Labeling--Single Level Hosts
The MAC implementation described above calls for each host to create a label in each packet, then to pass the packet to the security device 18 where the label is mediated with respect to the security window for that node. For single-level hosts, either the security device 18 can simply stamp the administratively-defined label into the packet header or a simplified driver can read the appropriate information from the security device and label the packets before giving them to the security device.
For single-level hosts, stamping the label into the header is equivalent to mediating the host-defined label against a security window that contains a single acceptable labeling. No mediation is required for these single level hosts because the security device 18 stamps the only label that is acceptable for that node. The two approaches (security window, labeling) are compatible because, in both cases, (1) only packets consistent with the security policy are transferred onto the network, and (2) each packet on the network is labeled at the correct level.
The label can be at any hierarchical level and non-hierarchical category set defined for the network. The labeling information is transferred to/from the NSC 12 to the security device 18 in CIPSO format using the same means used to transfer the security window for multi-level hosts.
This method for stamping a label into the packet header works only for single-level hosts, or for MLS hosts that are administratively constrained to a single level on the network. Hosts that operate in MLS mode on the network must provide a trusted labeling process with the label mediated by the security device 18.
Discretionary Access Control (DAC) Policy
Discretionary access control at layer 3 of the protocol stack is concerned with ensuring that a host computer can only have associations with authorized host computers. DAC is implemented through a pair of association lists, a "receive" association list and a "transmit" association list. Both the receive and transmit association lists are assigned by the network security officer.
Each network host, or authorized user permitted to access an authorized workstation, can only send messages to hosts that appear in its transmit association list. Likewise, a host is only permitted to receive messages from hosts that are named in its receive association list.
The network 10 enforces a centralized discretionary access control (DAC) policy based on hardware addresses, Internet Protocol (IP) addresses and Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) ports. This policy is specified by a network security administrator at the NSC 12 and downloaded to each security device 18 as part of the principal's security profile. The DAC policy is not settable by the individual hosts involved.
The IP portion of the DAC policy addresses the ability of any host in the 32-bit IP address space to send and receive from any other host. This policy is enforced at the transmit side of the network (based on the sending host's authorization to send to the destination address) and at the receive side of the network (based on the receiving host's authorization to receive from the destination address). The DAC policy is independent of the classification level and categories, but cannot override a MAC decision.
In actual use, this may be set up, for instance, as associations between pairs of hosts. For example, a first set of hosts {A, B} may communicate with each other, and a second set of hosts {C, D, E} may also be permitted to communicate with each other. However, communication is not permitted between any of the hosts of the first set with any of the hosts from the second set. These sets of hosts are essential VPNs.
The network 10 also provides rudimentary port filtering based on TCP and UDP ports, with the default being no port-based filtering. TCP and UDP each provide 16-bits of port space, with the ports used to identify specific endpoints (client or server process) on the sending and receiving hosts. Each TCP/UDP header has a source port address and a destination port address, where the source port address is associated with the sending process on the source host, and the destination port address is associated with the intended recipient process on the destination host.
The port filtering rules are also part of the DAC policy, specified by a network security administrator at the NSC 12, downloaded to security devices 18 as they come online, and enforced by the security device 18 for every packet. The port filtering aspect of the policy serves to further restrict communications between pairs of hosts that are authorized to communicate. For example, workstation A may be permitted to access server B, but the security device 18 for server B might block packets to port 23 (to block use of Telnet) or port 514 (to block access to the UNIX syslog facility).
The port filter is preferably per association, so effectively Telnet from a specific host may be permitted, and denied for all other hosts. For instance, if the protocol type does not specify either TCP or UDP, then the packet is passed to IP address filtering. Packets that are rejected because of a host-to-host association or a blocked port may be audited by the NSC.
The network 10 preferably combines the features of both mandatory and discretionary access control. Accordingly, for instance, in order for host A to transmit a message to host B, three conditions must be met: (1) the network requires that principal A's transmit association list must include host B; (2) host B's receive association list must include host A; and, (3) the security level of the message must be included within both host A's
and host B's security windows. Requirements (1) and (2) are based upon DAC, and requirement (3) is based upon MAC.
Identification and Authentication (I&A)
I&A is performed at the NSC 12 for operators and administrators and is performed at the security device 18 for the principals that are authorized to operate a node of the secure network. Identification of security officers at the NSC is a conventional login with user ID and password.
The security device 18 boards support various types of I&A for principals, including but not limited to authentication cards (what the user has) and ID/password (what the user knows). The mechanism used by a particular security device 18 board is determined from configuration data read from the administrator's card. The mechanisms include: an authentication card, ID/Password, Fortezza and Authentication card and PIN.
An authentication card is the standard means for I&A, and requires each principal to insert an authentication card in the security device 18 card reader to use the network. Each principal's card is programmed at the NSC and preferably transferred to the principal in person. The card contains one-time password information that prevents spoofing by anyone other than an administrator. This information includes the principal ID and a random value that is updated once per login.
The security device 18 performs I&A via an ID and password entered by the principal at the attached host. The password is compared with the value stored at the NSC. This method requires the local host to provide a trusted path mechanism by which the principal can reliably place the user ID and password in the security device 18. For single-user workstations, this may mean, for instance, that the user of the workstation enter the principal ID and password.
Fortezza involves the use of a Fortezza card in the host system to sign a defined value with the identity of the principal. It also requires a trusted path between the host's Fortezza software and the network driver.
The authentication card and PIN mechanism requires the principal to enter a PIN at the host in addition to inserting the authentication card.
Regardless of the means used for authentication, a principal's ability to use the network depends upon the Security Officer defining the principal in a database at the NSC, and providing the means of authentication (programmed card, password, etc.) to the principal.
Audit
Audit is the second key part of an accountability policy. MLS systems must record information about security-relevant events such as use of I&A mechanisms and attempts to send data outside of the host's security range or on unauthorized connections.
The network 10 provides selectable auditing of the following types of events: login and logout of security officers at the NSC; change of security databases at the NSC; I&A of principals; statistical events, providing detailed information about the individual packets transmitted and received; exception events, including attempts to violate the security window, send to or receive from an unauthorized association, etc.; TCP/UDP port filtering rejections; and, TCP opens and closes.
The NSC provides real-time alarms of attempted security violations. These are typically directed to a printer, and include the date and time, principal identifier, IP addresses, and protocol type and port number. The network immediately notifies the network security officer of any attempted violations. The network optionally disconnects the offending host from the network to avoid additional audit data from being generated.
Object Reuse
Object reuse (OR) is concerned with preventing inadvertent release of residual data, typically, in unused fields or at the end of a packet buffer. The TNI has two requirements for object reuse: preventing access to the residual data itself, and preventing use of residual authorizations. Both object reuse requirements are addressed by the innovative use of specialized hardware on the security device 18 board hardware that sanitizes buffers before they are reused again by the system. This hardware may be thought of as a macro extension of the processor.
System Architecture Requirement
A secure network must have a system architecture that ensures the network functions as a reference monitor. In accordance with the TNI, which defines the Network Reference Monitor (NRM) concept, an NRM must be tamperproof, must always be invoked, and must be small enough to be subject to complete analysis and testing. This relates to the ability of a MLS network to accurately and completely perform the functions that it is supposed to provide.
This requirement is inherently addressed by placing the security enforcement mechanisms in their own dedicated domain on the security device 18 board, where they cannot be interfered with by the host's software. It is supported by the effective use of cryptography to provide communications secrecy and communications integrity for all host-to-host transfers and all control communications.
The secure network described above consists of a specialized NSC 12 host dedicated to configuring and auditing the secure network and a network security device 18 installed between each host computer and the network medium. The design of the NSC 12 and the security device 18 mediation will now be discussed.
Network Security Center or Controller (NSC)
The NSC 12 is a dedicated machine used by the security officer to configure, operate, and audit the operation of the secure network. The NSC is necessary for the network to run, although the security devices 18 may also be configured to continue operating without the NSC.
The NSC is responsible for both authenticating principals when they connect to the network and for authorizing connections. When a principal initially signs onto the network over an authorized security device, the NSC is contacted to verify the authentication data and to initialize security-relevant parameters, including the security profile, the association profiles, and the seed, or keying material, from which the security device generates individual encryption keys.
Once the initialization is complete, the security device possesses sufficient intelligence and autonomy to manage all subsequent communication with other security devices across the network by itself. However, the security device continues to automatically report security-relevant occurrences to the NSC where they are displayed as real-time alarms and added to the audit log where they can later be examined for evidence of potential security violations.
The network architecture preferably provides for up to two separate NSCs, a primary NSC and a hot backup NSC. In normal operation, the primary NSC manages all aspects of the network, and provides automatic updates of network databases to the backup. The address of the backup NSC is known to the various security device adapters (from information read from an installation card), but the backup NSC does not participate in network policy management.
If the primary NSC fails, each security device independently switches over to the hot backup and periodically checks the availability of the primary. The backup preferably allows network principals to authenticate themselves, download configuration data, and begin operating on the network. The backup also logs audit data and provides the ability to configure individual boards to operate in "emergency mode" and generate their own keying material.
The NSC is preferably implemented on a commercial off-the-shelf Pentium-class machine, using Windows NT for screen management, printer management, keyboard/mouse input, threads dispatching, and object reuse. The NSC software is organized as a main application with multiple worker threads for network control, network I/O, audit, print management, and system monitoring.
The NSC does not use any NT networking code. Instead, the NSC uses a security device 18 board with special firmware (known as the security device 18-Prime) that manages the encryption/transmission of control messages to the various security device boards, and the reception/decryption of responses and audit data. The security device 18-Prime manages control keys based on the security device 18 addresses.
The NSC 12 provides at least two levels of Security Officers in accordance with the concept of least privilege: an administrator has access to all NSC commands (configuration, operation, and auditing), while an operator can only perform restricted control and monitoring functions. A security administrator can define additional site-specific roles that permit operators at a particular facility to have additional privileges beyond the pre-defined operator role.
The NSC command set includes security officer, network control, network management, principal, and security device 18 functions. The Security officer commands provide the ability for a security officer to login, logout, acknowledge alarms, and modify the security officer database. Network control functions include starting, stopping, suspending, resuming, and auditing the network.
Network management functions include defining user profiles, including security windows and host-to-host associations. It also includes loading key files, setting date and time, and database functions such as archiving the audit file and backing up and restoring databases.
Principals are the individuals that are directly responsible for the operation of nodes of the secure network. They may be users of single-user workstations, or may be administrators of multi-user systems. The functions related to management of principals include defining, editing, listing, and removing the principal data records, and programming access cards for the principals to bring up a network node.
Security device 18 functions include editing security device 18 data records, shutting down, suspending, and resuming security device 18 operation, and refreshing encryption keys used by the security device 18. Creating an installation card used to installation of the security device boards with their IP address and control keys.
Security Device 18 Architecture
In the preferred embodiment, the security device 18 is at self-contained circuit board that is directly attached into the hardware of the host system. The architecture is straightforward, enabling the device to be readily integrated into a variety of hardware environments. The device operates using its own independent processor 48, bus 46, program and data memory 54. These independent elements isolate the security device, including its algorithms, and insure that it operates within its own protected domain. Providing an independent processor also avoids stealing any memory cycles or processing bandwidth from the host in which it is installed. Since the device operates at a low OSI level, enforcing all security mechanisms within the hardware circuit board, it is tamperproof and cannot be compromised by software-based attacks.
As shown in FIG. 8, the security device 40 consists of a single-board adaptor installed on a Host Backplane Bus 42. Different implementations exist for various host bus architectures (for instance, PCI, Sbus, and ISA) and various network interfaces (such as Ethernet and Token Ring). Yet, each security device 40 includes a host interface, attached card reader 62, processor block, local RAM 54, cipher block and network block.
The host interface includes the host adapter's bus interface logic (not shown) and a block of two-port RAM 44. Portions of the memory 44 can be mapped into either the host. adapter memory space or the security device's 40 own internal memory, but not both at the same time. The host copies a packet into the two-port RAM 44 buffer and writes a memory location to cause the buffer to be mapped into the security device memory. After the buffer is transferred to the security device, it is invisible to the host processor until it is processed.
The processor block consists of a dedicated processor 48, non-volatile memory 52 (EPROM/flash) for program storage, and support logic. The processor block includes dedicated hardware logic burned into a ROM on the security device board, to move buffers, scrub buffers in support of object reuse requirements, and move data to and from the encryption chip.
The security device has its own internal system RAM 54, which is used for transitory storage of data packets, security windows, association lists, and the like. A portion of the internal RAM 54, identified as network coprocessor RAM 64, is used by the network block to send and receive packet buffering.
The cipher block 58, which consists of encryption device (s), support circuitry, and dedicated memory two-port RAM 56 available only to the processor and encryption hardware. The network block is the network coprocessor 66, which includes logic to send and receive packets on the network 68. The network 68 is preferably a LAN.
A key architectural feature of this hardware design is that the network medium 68 is separated from the host bus 42. This separation of the two interfaces dictates that packets will move from one interface to the other only if moved by security device's 40 software 52. The only way a packet may move from host bus 42 to local bus 46, is for the CPU 48, running the firmware 52, to grab the packet from the two-port RAM 44.
In addition, the hardware design provides a separation of the security device's own processing environment from both the host and the network. The security device's program and internal buffers are invisible to the host because of the dual-ported RAM design. Further, except for control requests from the NSC 12, which are accepted only from the NSC and must be cryptographically verified, there is no interface by which another host on the network can retrieve data from the security device's internal buffers.
Because all communications from one host to another must use the services provided by the security device in order to access the network, it is not possible for a host to inadvertently or maliciously bypass the security device security features. In a properly configured network, where there are no other electrical connections to the network, it is possible to make absolute statements that the host software (whether trusted to operate in MLS mode, or not) must operate in accordance with the centralized network security policy set up by the security policy defined by the security officer at the NSC. Further, any packets that are transmitted are cryptographically protected before being placed on the network.
The security device functions are implemented in firmware 52 installed on the security device board. During installation, the security device firmware reads an administrator installation card at the authentication interface unit 62 to get the board IP addresses (Node, NSC, default router) and cipher key. Subsequently, the security device downloads principal-specific and node-specific data, via the network interface 66, from the NSC and sends audit events to the network for archival. However, the security device operates independently of the attached host.
The security device has four general phases of operation: configuration, initialization, key exchange, and secure communication. Configuration is performed by the network security officer at the NSC workstation. The NSO configures each security device to support one or more principals, where each principal may have up to about 100 profiles. Each profile has associated mandatory access controls (security windows) and discretionary access controls (association lists).
Initialization of the security device occurs when a principal authenticates, via the security device, to the NSC. The security device reads security profile selected by the principal and cryptographic seed keying material from the database resident on the NSC. Whenever the security device establishes initial contact with another host that is also equipped with a security device, key exchange is conducted to prepare for secure communications between the hosts.
After a user is authenticated and selects a valid profile, the security device firmware downloads the security window and association list for the principal from the NSC. The window (that is, the hierarchical security levels and non-hierarchical categories, are represented in CIPSO format.
After configuration, initialization, and key exchange have taken place, secure communication between pairs of hosts is automatically and transparently managed by the respective security devices. User programs executing atop a security device equipped host only require access to a standard built-in networking application program interface (API) such as WinSock or TLI. This interface to the security device disguises the fact that an intricate sequence of operations is being performed by the security device each time a packet is transmitted or received across the network.
The network security claims for the security device 18 depend upon the proper sequence as well as execution of the following tasks. This can be viewed as multiple layers of processing in which the transmit flow of packets involves processing the individual layers from the highest layer (host) to lowest layer (network).
Packets are transmitted from the left to the right, that is, from the host bus 42 to the network 68, and received right to left, from the network 68 to the host 42. Packet flow is controlled by the CPU 48 and its firmware programs 52. Transmission and reception of packets will be discussed in further detail below with reference to FIGS. 9, 10 and 12.
The security device 40 is configured so that malicious programs on the host computer can not directly access any of the devices on the security device local bus 46. Thus, direct access cannot be established to the local RAM 54, network coprocessor 66, encryption hardware 58, or authentication interface 60. This is accomplished by only permitting communications between the host bus 42 and the internal bus 46 via the two-port RAM 44. Thus, the host bus 42 address signals, data signals, read/write signals, and so forth, do not extend to the local bus 46. Instead, each bus 42, 46 essentially terminates at the two-port RAM interface 44. (FIG. 12).
The two-port RAM 44 is connected to the host bus 42 and provides complete separation of the host and internal busses. The two-port RAM 44 is implemented as standard RAM storage devices with, two separate bus interfaces. This design provides for no pass-through or leakage from one bus to the other, except by a write on one bus to a memory cell followed by a read on the other bus.
In operation, a principal inserts a card in the authentication interface unit 62 and selects a profile using the keypad and display on that unit. The unit 62 is typically connected to the interface logic 60 by a ribbon cabling. The logic 60 enables information to be read/write to/from the card, as well as to read the keypad and write to a display.
Once a principal is authenticated, the host may transmit packets to the network. With cross reference to FIG. 9, a host asserts a signal on the bus 42 to put a packet into the two-port RAM 44, step 100. The CPU 48, operating under control of firmware 52, reads the packet from the shared memory 44 by asserting signals on the local bus 46.
The CPU 48, using a transmit association list in the internal memory 54, performs DAC by determining if the destination IP address is in the transmit list, step 102. The transmit list was previously downloaded from the NSC via the network 68, based upon the principal authentication and profile selected. The CPU 48, using a transmit security window in the internal memory 54, performs MAC by determining if the security label is consistent with the transmit security window, step 104. As with the transmit list, the security window was also downloaded from the NSC as a result of the principal authentication and the profile selected.
The CPU 48 then puts the packet in the cipher two-port RAM 56, which is used for communications with the cipher unit 58. The cipher unit 58 uses pre-loaded keying material to perform the cryptographic transformation and place the result back into the two-port RAM 56. Unlike the host two-port RAM, the cipher two-port RAM 56 preferably does not have protection responsibility. Rather, the cipher two-port RAM 56 is used to facilitate communications between the CPU 48 and cipher unit 58, step 106.
Next, the CPU 48 collects information from the packet that is to be protected by a message digest (cryptographic checksum), and places it in the cipher two-port RAM 56. The cipher unit 58 makes the cryptographic transformation and puts it back into the cipher two-port RAM, where the CPU takes it and puts it in the IP header, step 107.
The CPU 48 then puts the packet into a reserved area in the network coprocessor RAM 64. The network coprocessor 66 takes the packet from this RAM 64 and transmits it onto the network 68, steps 108, 110. RAM 64 is a portion of the internal RAM 54 that is dedicated by the firmware 52 for use by the network coprocessor.
Packet reception operates in the reverse manner, as discussed with relation to FIG. 10. After the packet is received from the network 68 by the network coprocessor 66 and placed in the network coprocessor RAM 64, the CPU 48 takes over and does reception DAC, step 152 and MAC, step 154 using data structures in internal RAM 54 that were downloaded from the NSC after principal authentication and profile selection.
The CPU 48 verifies the integrity of the packet, step 156, by performing the same message digest calculation done by the sending host in step 107. If the results match, then the packet was not modified en route. This involves putting data in cipher two-port RAM 56 and the cipher unit 58 performing a transformation using keys loaded in the hardware. The CPU 48 decrypts the packet, step 158, using the same general approach flow of processing as for encryption, step 106, but with the cipher unit operating in decryption mode.
FIG. 9 shows the process for transmitting information. At step 100, the host requests and the security device 18 maps the packet to be transmitted. At this step, the host places a packet in the Interface Control Block (ICB) and notifies the security device. This maps the packet out of host memory and into board memory.
At the security device, the packet then undergoes DAC, step 102. Here, the security device verifies that the host has an authorized transmit association to the destination address in the host's IP header. If not, an audit is generated, step 112, and the processing flow is terminated, step 114.
If the destination address is in the transmit list, Mandatory Access Control is performed. At step 104, the security device verifies that the host-specified packet label (CIPSO) is consistent with the transmit security window, or (for single-level hosts) labels the packet with the host label. If not, an audit is generated, step 112, and the processing flow is terminated, step 114.
At step 106, for packets satisfying both discretionary and mandatory access control, the packet is encrypted, using the encryption key for the destination IP address. At step 107, the cryptographic checksum B is computed and placed in to the packet. Proceeding to step 108, the link layer header is generated, and at step 110, the packet is transmitted.
Similarly, packet reception occurs in an order of processing, from the lowest layer to the highest. Turning to step 150 of FIG. 10, the security device receives the packet from the network. Discretionary Access Control is then performed by security device by verifying that the host has a receive association for the source IP address in the incoming packet's IP header, step 152. If not, an audit is generated, step 162, and the processing flow is terminated, step 164.
Mandatory Access Control is performed at step 154 by verifying that the packet label (CIPSO) is consistent with the receive security window. At step 154, the security device verifies the integrity of the received packet by calculating a message digest (cryptographic checksum) of the received data. If the computed value matches the value sent by the originating security device, then the packet was not modified. If not, an audit is generated, step 162, and the processing flow is terminated, step 164.
For packets satisfying both discretionary and mandatory access control, the packet is decrypted, step 156, using traffic key for source IP address. The security device then maps the packet out of the board memory and into the host memory.
When configured at installation (by data on the administrator's card), the security device 18 provides the ability for the attached host computer to initiate switching from one authorized profile to another. Each profile has associated with it separate transmit and receive security windows for MAC, as well as separate transmit and receive association association lists for DAC.
The host enters the profile by using its trusted path to write the new profile identifier into the security device ICB. The security device validates that the host actually has the requested profile and, if so, then resets the security window and associations and sends a profile change notification to the NSC. If the security device is not configured to allow the host to initiate profile switching, then principal must select another profile via the card reader in order to switch profiles.
The security device also provides a way for the local host to place cleartext data in the ICB and receive the encrypted results. This uses the standard packet transmission code with a specified key.
Host Bus Interface Using Two-Port RAM
In order to better understand the operation of the host bus interface, which uses two-port RAM 44, reference will first be made to the conventional network adapter architecture. A standard network adapter 310 is shown in FIG. 11. The same general architecture is used for other types of adapters, e.g., SCSI controllers, video controllers, etc.
Typically the adapter is plugged into the host bus 302, which typically consists of address lines 304, data lines 306, and control lines 308. For example, on a 32-bit computer, there might be 32 address lines, 32 data lines, and several control lines (interrupt, I/O, etc.). In a standard network adapter, some portion of these lines extend directly into the adapter card 310. For example, the local bus 311 might consist of 8 address lines, 8 data lines, and a few control lines. These are wired directly or with minimal interface logic to the host bus 302.
If the adapter has local RAM 312 or local adapter firmware 314, these are directly accessible to software (typically a device driver) on the host computer. This means is commonly used for personal computers to execute extensions to the device driver that are resident in firmware on the adapter board. In the case of a network adapter, a network coprocessor sits on the bus and sends receives packets from adapter RAM 312 or from host memory (not shown).
The problem with this architecture for a security device, however, is that the contents of memory on the adapter board depend on the trustworthiness of the host operating system. Any user process on the host 300 that can bypass these host controls can modify memory locations on the adapter board and cause the network adapter to send or receive anything.
Turning to FIG. 12, the host bus interface having a two-port RAM is shown in further detail. The security device 310 runs in its own protected domain, completely isolated from potentially malicious host software running on the host CPU 300. This is done via a two-port RAM interface 312 implemented on the security device 310, and providing only a limited means for the host software to interact with the security device.
In particular, it is not possible for host software to observe or modify data in the local RAM 334, firmware 336, or network coprocessor 338. This is because the only signal lines that extend from the host bus onto the security device are those address and data lines used to read and write data into the host port 314 of the two port RAM 312. There is no path onto the local bus 320.
The operation of the two-port RAM interface for packet transmission will now be discussed. The host 300 device driver builds a packet for transmission and writes the packet into a portion of the two port RAM. However, the exact memory layout of the two-port RAM is irrelevant to the security provided by the system, and other suitable configurations may be used.
The host 300 device driver writes to a memory location in the two-port RAM that causes an interrupt 326 to be signaled to the CPU 332 of the security device.
The firmware 336 of the security device contains code to map the portion of two port RAM 312 out of host memory and into the security device's memory. When this occurs, the memory is no longer visible to the host (typically, a bus error occurs if it is accessed) and is visible to the security devices firmware. Thus, when the transmit buffer is mapped out of host memory, a new buffer is mapped into host memory. Therefore the host always has a buffer to which he has access. The device will not map the buffer out of host space until it can process the buffer.
Next, the firmware 336 accesses the data by memory reads using the local address 322 and data 324 lines to the two port RAM. The packet is moved from the two port RAM area into local RAM space via a hardware assisted block move mechanism. The firmware 336 running on the local CPU 332 then performs MAC, DAC, encryption and integrity functions, and may hand the packet to the network coprocessor 338 for transmission. All of this is invisible to software running on the host CPU 300.
The operation for packet reception is similar. The network coprocessor 338 receives a packet, places it in local RAM, and the firmware 336 on the local CPU performs MAC, DAC, decryption, and packet integrity functions. If the packet is valid for the host, the firmware 336 places the packet in the two port RAM via memory writes using the address 322 and data 324 lines. Again, this goes into an available portion of the two port RAM using conventions established by the security device and the host device driver.
When the packet is fully placed into this memory, the firmware maps the memory buffer into host memory (thus making it visible to the host device driver) and writes a memory location that causes the two port RAM interface circuitry to assert an interrupt signal 308 to the host CPU.
The key points of this interface are: (1) host signal lines do not extend into the security device board, and so the only means for the host to interact with the security device is via this two port RAM interface. (2) A particular buffer in the two port RAM is invisible to the host while the security device is processing its contents.
The CPU of the security device has access to all memory on the NIC board at all times, even when a particular buffer in the two port RAM is mapped into host memory. However, when the buffer is mapped into the security device's address space, the host computer has no access to the buffer.
General Operation
The overall operation of the system will now be discussed with reference to FIG. 13. The first step is to configure the network. A security officer 502 at the network security center 500 interacts via menus at the security center console 504 to define security devices (510, 520), principals (512, 522), classification levels, etc. This includes profiles for principals, which includes associations such as the ability of host 514 to transmit to host 524.
The security officer 502 also specifies the authentication method (card, password, etc.) to be used by the principal. If the principals are to use an authentication card, the security officer creates individual authentication cards at the card reader 506 and gives these cards to principals (512, 522). During this process, the security officer 502 creates an initialization card for security devices (510, 520) and physically goes to that site to read in the card via card readers (516, 526) in order to complete installation of the devices.
Each principal goes to the location of the security device (510, 520) and initiates the authentication method specified for the principal. Different principals may be configured to use different means, for example, principal 512 may be configured to use an authentication card and principal 522 may be configured to use a password.
When an authentication card is required, the principal 512 inserts the authentication card into the card reader 516, which is connected to the security device 510. The card is read by the security device 510. Principal 522, which has a password instead of a card, types the password at the console of host 528. The host transfers the password to the security device 524 via a trusted path.
The device will be defined to support a specified authentication type. The principal who is attempting to use the device must have the appropriate authentication data. The security devices independently transfer the authentication data to the security center 500 via an encrypted (nominally Triple DES, although other methods are conceivable) connection. The security center replies to the security device, listing the profiles that may be selected by the principal. This may be anywhere from a single profile up to a hundred profiles.
Each principal (independently) selects the desired profile at the keypad of the local card reader (516, 526). Each security device (510, 520) sends this information to the security center 500 via an encryption connection.
There is not an initial communication without the selected profile between the device and the controller. The device gathers the required data and then sends all of the information via the encrypted channel to the controller. The security center responds to the security device with the security windows to be used for MAC and the security associations to be used for DAC. Assuming that security devices (510, 520) permit associations between hosts (518, 528), the security devices negotiate traffic keys between the two devices (based on a shared secret value downloaded from the security center). The shared secret is only one of the possible mechanisms. The approved mechanisms are defined in the IPSec standards.
At this point the two hosts (518, 528) may communicate via their respective security devices, provided that communications are consistent with the predefined security windows (MAC).
Example Embodiment
Turning to FIG. 14, an example of a local area network 10 is shown connected to a network 30. The LAN 10 comprises a first VPN 80, and a second VPN 82. The VPNs 80, 82, are established by a security officer that sets up permitted associations between hosts based on IP addresses. The VPNs are collections of host IP addresses that are permitted to communicate. Hosts on the second VPN 82 are invisible to hosts which are not directly addressable. This centralized configuration of secure VPNs is enforced by the respective security devices 18 of each host.
In the example set forth in FIG. 14, working from the left of the page, a first host 86 is configured to operate on both the first and second VPNs 80, 82. The third and fourth hosts, 90, 92, only have the ability to operate on either the first VPN 80 or the second VPN 82, respectively, but cannot access both VPNs. This is merely a matter of defining the IP associations permitted for this host.
The second host 88 has a security device 18 that permits the host 88 to operate either on the second VPN 82 or on an untrusted line 84. This ability to switch between a trusted network 82 and an untrusted network 84 is defined by the security officer at the NSC by defining multiple permitted profiles for a principal. When the principal authenticates at the security device 18 associated with this host 88, the principal determines which of the permitted profiles is to be used.
According to our example, the profile for the principal operating at the second host 88 is twofold. First, for the second, VPN 82, the host 88 is permitted to transmit and receive associations with the first host 86 and with the fourth host 92. A security window for MAC is also defined. A security window is always used, except when the security device is operating in a bypass mode to unprotected hosts, such as hosts without a security device. Secondly, when operating on network 84, the second host 88 is permitted to communicate with any unprotected host (not shown) anywhere on the Internet.
Although the principal at host 88 may switch between the second trusted VPN 82, and an untrusted path 84, the principal may only use one profile at a time. Thus, the host 88 may connect to either the untrusted network 84 or the trusted network 82 to communicate only with hosts 86, 92. Thus, it is impossible for a host on the Internet to route packets through hosts 88 and back out on the trusted network 82, perhaps to attack the fourth host 92.
If the principal has a profile that permits communication with unprotected hosts (such as hosts that do not have a security device 18), the security device operates in a "bypass" mode. In the "bypass" mode, the security device does not provide encryption but does implement MAC and DAC. Thus, MAC and DAC are always performed, though encryption may not be performed depending on the destination node.
Further to this example, if the second host 88 is an untrusted host and it is operating at a secret level, then the memory of the second host 88 before permitting connections to or from any other untrusted host. This is possible, for instance, by switching disk drives, such as a slide-in drive, and power-cycling the host to clear memory.
Unlike the second host 88, the third host 90 is configured (by the user's profile) to be able to connect over the Internet 30 to a remote host 94, as well as to the first host 86 via line 80. Simultaneously, the first host 86 may be connected to the fourth host 92 via line 82.
Alternative Embodiments
The preferred embodiment is for networks including multi-user servers, where the principal is not necessarily a user of the attached host. However, the invention may be used in any suitable network environment, such as one having single-user workstations where the principal is the current user of the workstation. The security devices in the single-user workstation network may be configured so that the classification of the host is related to the administrative clearance of the user/principal operating at the host. The network would support multi-level security for communications between individual users.
Although the preferred embodiment is also for a network having classified information, the invention has uses for unclassified environments as well. As implemented in an unclassified network, for instance, instead of establishing different hierarchical security levels, various non-hierarchical descriptors may be defined by the network security officer. Also, a combination of levels and descriptors may be defined.
In the present embodiment, for example, the security device may be used to monitor and distribute incoming and outgoing information in accordance with the various descriptors. Principals are assigned profiles that define permitted associations and the like. Each principal may be assigned one or more profiles. The principal may log in at any host and select from the one or more profiles. The selected user profile is then used to define the permitted communications for that host. Accordingly, a principal may use any host to connect to the network, and select a user profile to establish the parameters for that connection.
In yet another alternative embodiment, the security device 18 may be eliminated altogether and the security mechanisms implemented by software located at the computer (or as otherwise suitable). Thus, for instance, the software is configured to is implement encryption, DAC and MAC for all incoming and outgoing communications. In addition, the software establishes and implements user profiles, association lists, and audit events, as defined by the network security officer.
The foregoing descriptions and drawings should be considered as illustrative only of the principles of the invention. The invention may be configured in a variety of manners and is not limited by the design of the preferred embodiment. Numerous applications of the present invention will readily occur to those skilled in the art. Therefore, it is not desired to limit the invention to the specific examples disclosed or the exact construction and operation shown and described. Rather, all suitable modifications and equivalents may be resorted to, falling within the scope of the invention.
| Patent | Priority | Assignee | Title |
| 10009320, | Mar 15 2006 | Fortinet, Inc. | Computerized system and method for deployment of management tunnels |
| 10013580, | Mar 29 2013 | SECTURION SYSTEMS, INC. | Security device with programmable systolic-matrix cryptographic module and programmable input/output interface |
| 10050917, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Multi-dimensional reputation scoring |
| 10110667, | Apr 08 2008 | RPS CANADA INC | System and method for providing data and application continuity in a computer system |
| 10114766, | Apr 01 2013 | SECTURION SYSTEMS, INC. | Multi-level independent security architecture |
| 10165051, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | High performance IP processor using RDMA |
| 10193861, | Nov 16 2004 | Cisco Technology, Inc. | Method and apparatus for best effort propagation of security group information |
| 10250778, | Jul 18 2017 | Xerox Corporation | Distributed smart card reader for multifunction printer |
| 10326734, | Jul 15 2013 | University of Florida Research Foundation, Incorporated | Adaptive identity rights management system for regulatory compliance and privacy protection |
| 10560339, | Dec 30 2011 | VeriSign, Inc. | DNS package in a partitioned network |
| 10680816, | Mar 26 2014 | CONTINENTAL TEVES AG & CO OHG | Method and system for improving the data security during a communication process |
| 10708236, | Oct 26 2015 | SECTURION SYSTEMS, INC | Multi-independent level secure (MILS) storage encryption |
| 10902155, | Mar 29 2013 | SECTURION SYSTEMS, INC. | Multi-tenancy architecture |
| 11063914, | Mar 29 2013 | SECTURION SYSTEMS, INC. | Secure end-to-end communication system |
| 11070612, | Apr 08 2008 | RPS CANADA INC | System and method for providing data and application continuity in a computer system |
| 11122054, | Aug 27 2019 | Bank of America Corporation | Security tool |
| 11283774, | Sep 17 2015 | SECTURION SYSTEMS, INC | Cloud storage using encryption gateway with certificate authority identification |
| 11288402, | Mar 29 2013 | SECTURION SYSTEMS, INC. | Security device with programmable systolic-matrix cryptographic module and programmable input/output interface |
| 11429540, | Apr 01 2013 | SECTURION SYSTEMS, INC. | Multi-level independent security architecture |
| 11575736, | Apr 08 2008 | RPS CANADA INC | System and method for providing data and application continuity in a computer system |
| 11750571, | Oct 26 2015 | SECTURION SYSTEMS, INC. | Multi-independent level secure (MILS) storage encryption |
| 11783089, | Mar 29 2013 | SECTURION SYSTEMS, INC. | Multi-tenancy architecture |
| 11792079, | Dec 30 2011 | VeriSign, Inc. | DNS package in a network |
| 11792169, | Sep 17 2015 | SECTURION SYSTEMS, INC. | Cloud storage using encryption gateway with certificate authority identification |
| 6438612, | Sep 11 1998 | Inside Secure | Method and arrangement for secure tunneling of data between virtual routers |
| 6519171, | Nov 17 2000 | SOCIONEXT INC | Semiconductor device and multichip module |
| 6549972, | Nov 22 1999 | International Business Machines Corporation | Method and system for providing control accesses between a device on a non-proprietary bus and a device on a proprietary bus |
| 6711681, | May 05 1999 | Sun Microsystems, Inc. | Cryptographic authorization with prioritized authentication |
| 6763469, | Mar 03 1999 | Telecom Italia | Systems for local network security |
| 6775657, | Dec 22 1999 | Cisco Technology, Inc.; Cisco Technology, Inc | Multilayered intrusion detection system and method |
| 6845452, | Mar 12 2002 | Cisco Technology, Inc | Providing security for external access to a protected computer network |
| 6850943, | Oct 18 2002 | CHECK POINT SOFTWARE TECHNOLOGIES, INC | Security system and methodology for providing indirect access control |
| 6865674, | Jun 02 1999 | Entrust Technologies Limited | Dynamic trust anchor system and method |
| 6871277, | Oct 20 1998 | Canon Kabushiki Kaisha | Apparatus and method for preventing disclosure of protected information |
| 6922785, | May 11 2000 | Lenovo PC International | Apparatus and a method for secure communications for network computers |
| 6931529, | Jan 05 2001 | International Business Machines Corporation | Establishing consistent, end-to-end protection for a user datagram |
| 6931530, | Jul 22 2002 | THALES DIS CPL USA, INC | Secure network file access controller implementing access control and auditing |
| 6938169, | Dec 10 1999 | Oracle America, Inc | Channel-specific file system views in a private network using a public-network infrastructure |
| 6941350, | Oct 19 2000 | STRIPE, INC | Method and apparatus for reliably choosing a master network manager during initialization of a network computing system |
| 6941467, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for adaptive message interrogation through multiple queues |
| 6970941, | Dec 10 1999 | Oracle America, Inc | System and method for separating addresses from the delivery scheme in a virtual private network |
| 6975996, | Oct 09 2001 | GOLDMAN, SACHS & CO | Electronic subpoena service |
| 6977929, | Dec 10 1999 | Oracle America, Inc | Method and system for facilitating relocation of devices on a network |
| 6978300, | Oct 19 2000 | International Business Machines Corporation | Method and apparatus to perform fabric management |
| 6981025, | Oct 19 2000 | International Business Machines Corporation | Method and apparatus for ensuring scalable mastership during initialization of a system area network |
| 6986061, | Nov 20 2000 | TREND MICRO INCORPORATED | Integrated system for network layer security and fine-grained identity-based access control |
| 6988208, | Jan 25 2001 | NTT SECURITY US INC | Method and apparatus for verifying the integrity and security of computer networks and implementing counter measures |
| 6990528, | Oct 19 2000 | International Business Machines Corporation | System area network of end-to-end context via reliable datagram domains |
| 7007301, | Jun 12 2000 | Hewlett Packard Enterprise Development LP | Computer architecture for an intrusion detection system |
| 7020718, | May 15 2000 | HEWLETT-PACKARD DEVELOPMENT COMPANY L P | System and method of aggregating discontiguous address ranges into addresses and masks using a plurality of repeating address blocks |
| 7024686, | May 15 2000 | HEWLETT-PACKARD DEVELOPMENT COMPANY L P | Secure network and method of establishing communication amongst network devices that have restricted network connectivity |
| 7042852, | May 20 2002 | Extreme Networks, Inc | System and method for wireless LAN dynamic channel change with honeypot trap |
| 7043753, | Mar 12 2002 | Cisco Technology, Inc | Providing security for external access to a protected computer network |
| 7051365, | Jun 30 1999 | RPX Corporation | Method and apparatus for a distributed firewall |
| 7058796, | May 20 2002 | Extreme Networks, Inc | Method and system for actively defending a wireless LAN against attacks |
| 7062570, | Aug 04 2000 | Citrix Systems, Inc | High performance server farm with tagging and pipelining |
| 7069437, | Aug 06 1998 | API CRYPTEK INC | Multi-level security network system |
| 7072657, | Apr 11 2002 | NTT DOCOMO INC | Method and associated apparatus for pre-authentication, preestablished virtual private network in heterogeneous access networks |
| 7073173, | Dec 04 2000 | Microsoft Technology Licensing, LLC | Code and thread differential addressing via multiplex page maps |
| 7080094, | Oct 29 2002 | Lockheed Martin Corporation | Hardware accelerated validating parser |
| 7086089, | May 20 2002 | Extreme Networks, Inc | Systems and methods for network security |
| 7089590, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for adaptive message interrogation through multiple queues |
| 7096498, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for message threat management |
| 7099955, | Oct 19 2000 | LENOVO INTERNATIONAL LIMITED | End node partitioning using LMC for a system area network |
| 7113995, | Oct 19 2000 | LinkedIn Corporation | Method and apparatus for reporting unauthorized attempts to access nodes in a network computing system |
| 7124438, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for anomaly detection in patterns of monitored communications |
| 7131140, | Dec 29 2000 | Cisco Technology, Inc. | Method for protecting a firewall load balancer from a denial of service attack |
| 7134141, | Jun 12 2000 | HEWLETT-PACKARD DEVELOPMENT COMPANY L P | System and method for host and network based intrusion detection and response |
| 7143288, | Oct 16 2002 | THALES DIS CPL USA, INC | Secure file system server architecture and methods |
| 7146643, | Oct 29 2002 | Lockheed Martin Corporation | Intrusion detection accelerator |
| 7162737, | Feb 13 2001 | FORCEPOINT FEDERAL HOLDINGS LLC; Forcepoint LLC | Synchronization of security gateway state information |
| 7168093, | Jan 25 2001 | NTT SECURITY US INC | Method and apparatus for verifying the integrity and security of computer networks and implementation of counter measures |
| 7177945, | Aug 04 2000 | Citrix Systems, Inc | Non-intrusive multiplexed transaction persistency in secure commerce environments |
| 7185365, | Mar 27 2002 | Intel Corporation | Security enabled network access control |
| 7188365, | Apr 04 2002 | Intellectual Ventures II LLC | Method and system for securely scanning network traffic |
| 7192093, | Apr 23 2004 | MINISTER OF NATURAL RESOURCES CANADA | Excavation apparatus and method |
| 7203957, | Apr 04 2002 | RAKUTEN GROUP, INC | Multipoint server for providing secure, scaleable connections between a plurality of network devices |
| 7213260, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for upstream threat pushback |
| 7213265, | Nov 15 2000 | Lockheed Martin Corporation | Real time active network compartmentalization |
| 7225466, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for message threat management |
| 7225467, | Nov 15 2000 | Lockheed Martin Corporation | Active intrusion resistant environment of layered object and compartment keys (airelock) |
| 7228350, | Aug 04 2000 | Citrix Systems, Inc | Intelligent demand driven recognition of URL objects in connection oriented transactions |
| 7243235, | Jun 08 2004 | Sovereign Peak Ventures, LLC | Mandatory access control (MAC) method |
| 7260668, | Feb 14 2001 | Micronas GmbH | Network co-processor for vehicles |
| 7263719, | May 15 2000 | VALTRUS INNOVATIONS LIMITED | System and method for implementing network security policies on a common network infrastructure |
| 7277404, | May 20 2002 | Extreme Networks, Inc | System and method for sensing wireless LAN activity |
| 7281265, | Jun 02 2003 | Cisco Technology, Inc. | System and method for communicating packets in a network environment |
| 7284268, | May 16 2002 | ARRIS ENTERPRISES LLC | System and method for a routing device to securely share network data with a host utilizing a hardware firewall |
| 7287280, | Feb 12 2002 | GOLDMAN SACHS & CO LLC | Automated security management |
| 7290278, | Oct 02 2003 | GOOGLE LLC | Identity based service system |
| 7293175, | Jun 29 2000 | Lockheed Martin Corporation | Automatic information sanitizer |
| 7302569, | Aug 19 2003 | SAILPOINT TECHNOLOGIES HOLDINGS, INC | Implementation and use of a PII data access control facility employing personally identifying information labels and purpose serving functions sets |
| 7302700, | Sep 28 2001 | Juniper Networks, Inc | Method and apparatus for implementing a layer 3/layer 7 firewall in an L2 device |
| 7320069, | Feb 14 2003 | Apple Inc | Selective encryption of media data |
| 7322044, | Jun 03 2002 | Extreme Networks, Inc | Systems and methods for automated network policy exception detection and correction |
| 7324804, | Apr 21 2003 | Extreme Networks, Inc | Systems and methods for dynamic sensor discovery and selection |
| 7334124, | Jul 22 2002 | THALES ESECURITY, INC | Logical access block processing protocol for transparent secure file storage |
| 7336790, | Dec 10 1999 | Oracle America, Inc | Decoupling access control from key management in a network |
| 7343497, | Oct 17 2001 | Telefonaktiebolaget LM Ericsson (publ) | Security in communication networks |
| 7353532, | Aug 30 2002 | GOOGLE LLC | Secure system and method for enforcement of privacy policy and protection of confidentiality |
| 7355996, | Feb 06 2004 | Extreme Networks, Inc | Systems and methods for adaptive monitoring with bandwidth constraints |
| 7356695, | Aug 01 2002 | International Business Machines Corporation | Multi-level security systems |
| 7359676, | Apr 21 2003 | Extreme Networks, Inc | Systems and methods for adaptively scanning for wireless communications |
| 7366148, | Apr 11 2002 | Johns Hopkins University, The | Intrusion detection system for wireless networks |
| 7370348, | Jul 30 1999 | Intel Corporation | Technique and apparatus for processing cryptographic services of data in a network system |
| 7376755, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | TCP/IP processor and engine using RDMA |
| 7383577, | May 20 2002 | Extreme Networks, Inc | Method and system for encrypted network management and intrusion detection |
| 7400591, | May 15 2000 | VALTRUS INNOVATIONS LIMITED | Method of creating an address and a discontiguous mask for a network security policy area |
| 7401352, | Aug 30 2002 | Slingshot IOT LLC | Secure system and method for enforcement of privacy policy and protection of confidentiality |
| 7415723, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | Distributed network security system and a hardware processor therefor |
| 7424743, | Jan 25 2001 | NTT SECURITY US INC | Apparatus for verifying the integrity of computer networks and implementation of countermeasures |
| 7444679, | Oct 31 2001 | HTC Corporation | Network, method and computer readable medium for distributing security updates to select nodes on a network |
| 7448081, | Apr 04 2002 | Intellectual Ventures II LLC | Method and system for securely scanning network traffic |
| 7457244, | Jun 24 2004 | Cisco Technology, Inc | System and method for generating a traffic matrix in a network environment |
| 7458098, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for enhancing electronic communication security |
| 7487264, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | High performance IP processor |
| 7490348, | Mar 17 2003 | LONE STAR WIFI | Wireless network having multiple communication allowances |
| 7496950, | Jun 13 2002 | Intellectual Ventures II LLC | Secure remote management appliance |
| 7516408, | Sep 28 2001 | MAPLEBEAR INC | Method, system and program for switching between various computer-based communication techniques |
| 7519826, | Oct 01 2003 | Gula Consulting Limited Liability Company | Near real-time multi-party task authorization access control |
| 7519994, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for adaptive message interrogation through multiple queues |
| 7522908, | Apr 21 2003 | Extreme Networks, Inc | Systems and methods for wireless network site survey |
| 7523484, | Sep 24 2003 | INFOEXPRESS, INC | Systems and methods of controlling network access |
| 7526808, | May 20 2002 | Extreme Networks, Inc | Method and system for actively defending a wireless LAN against attacks |
| 7529927, | Mar 27 1999 | Microsoft Technology Licensing, LLC | Specifying security for an element by assigning a scaled value representative of the relative security thereof |
| 7530112, | Sep 10 2003 | Cisco Technology, Inc.; Cisco Technology, Inc | Method and apparatus for providing network security using role-based access control |
| 7532895, | May 20 2002 | Extreme Networks, Inc | Systems and methods for adaptive location tracking |
| 7536462, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | Memory system for a high performance IP processor |
| 7543293, | Dec 27 2005 | Microsoft Technology Licensing, LLC | Privelege level changing for virtual memory mapping |
| 7543332, | Apr 04 2002 | Intellectual Ventures II LLC | Method and system for securely scanning network traffic |
| 7546458, | May 04 2002 | Qualcomm Incorporated | Method for organizing virtual networks while optimizing security |
| 7548883, | Mar 20 2001 | REGULATORY DATACORP, INC | Construction industry risk management clearinghouse |
| 7549162, | Dec 06 2004 | AT&T Intellectual Property I, L P | Methods of providing security for data distributions in a data network and related devices, networks, and computer program products |
| 7562386, | Apr 04 2002 | RAKUTEN GROUP, INC | Multipoint server for providing secure, scaleable connections between a plurality of network devices |
| 7565351, | Mar 14 2005 | Rockwell Automation Technologies, Inc.; ROCKWELL AUTOMATION TECHNOLOGIES, INC | Automation device data interface |
| 7565532, | Oct 16 2002 | THALES ESECURITY, INC | Secure file system server architecture and methods |
| 7574738, | Nov 06 2002 | AT&T Corp | Virtual private network crossovers based on certificates |
| 7577424, | Dec 19 2005 | Extreme Networks, Inc | Systems and methods for wireless vulnerability analysis |
| 7590684, | Jul 06 2001 | CHECK POINT SOFTWARE TECHNOLOGIES, INC | System providing methodology for access control with cooperative enforcement |
| 7590733, | Sep 14 2005 | InfoExpress, Inc.; INFOEXPRESS, INC | Dynamic address assignment for access control on DHCP networks |
| 7596806, | Sep 06 2002 | INTELLECTUAL VENTURES ASSETS 3 LLC | VPN and firewall integrated system |
| 7600117, | Sep 29 2004 | Panasonic Corporation | Mandatory access control scheme with active objects |
| 7607011, | Jul 16 2004 | Rockwell Collins, Inc.; Rockwell Collins, Inc | System and method for multi-level security on a network |
| 7610332, | Jan 15 2002 | RPX CLEARINGHOUSE LLC | Overlay networks |
| 7617393, | Aug 19 2003 | SAILPOINT TECHNOLOGIES HOLDINGS, INC | Implementation and use of PII data access control facility employing personally identifying information labels and purpose serving function sets |
| 7627693, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | IP storage processor and engine therefor using RDMA |
| 7627896, | Dec 24 2004 | Check Point Software Technologies, Inc.; CHECK POINT SOFTWARE TECHNOLOGIES, INC | Security system providing methodology for cooperative enforcement of security policies during SSL sessions |
| 7631107, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | Runtime adaptable protocol processor |
| 7636772, | Oct 19 2000 | International Business Machines Corporation | Method and apparatus for dynamic retention of system area network management information in non-volatile store |
| 7669052, | Jan 21 2000 | SONY NETWORK ENTERTAINMENT PLATFORM INC ; Sony Computer Entertainment Inc | Authentication and encryption utilizing command identifiers |
| 7669244, | Oct 21 2004 | Cisco Technology, Inc. | Method and system for generating user group permission lists |
| 7685254, | Dec 30 2005 | MEMORY ACCESS TECHNOLOGIES LLC | Runtime adaptable search processor |
| 7685309, | Dec 10 1999 | Sun Microsystems, Inc. | System and method for separating addresses from the delivery scheme in a virtual private network |
| 7693581, | May 31 2005 | Rockwell Automation Technologies, Inc. | Application and service management for industrial control devices |
| 7693947, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for graphically displaying messaging traffic |
| 7694128, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for secure communication delivery |
| 7695071, | Oct 15 2002 | MINISTER OF NATURAL RESOURCES CANADA | Automated excavation machine |
| 7702574, | Nov 14 2002 | GOLDMAN SACHS & CO LLC | Independent research consensus earnings estimates and methods of determining such |
| 7706895, | Feb 25 2005 | Rockwell Automation Technologies, Inc.; ROCKWELL AUTOMATION TECHNOLOGIES, INC | Reliable messaging instruction |
| 7715800, | Jan 13 2006 | Extreme Networks, Inc | Systems and methods for wireless intrusion detection using spectral analysis |
| 7721323, | Nov 23 2004 | Cisco Technology, Inc. | Method and system for including network security information in a frame |
| 7734844, | Aug 19 2003 | GENERAL DYNAMICS MISSION SYSTEMS, INC | Trusted interface unit (TIU) and method of making and using the same |
| 7734916, | Aug 01 2002 | International Business Machines Corporation | Multi-level security systems |
| 7757077, | Jan 14 2000 | Microsoft Technology Licensing, LLC | Specifying security for an element by assigning a scaled value representative of the relative security thereof |
| 7765581, | Dec 10 1999 | Oracle America, Inc | System and method for enabling scalable security in a virtual private network |
| 7770215, | Dec 29 2000 | Cisco Technology, Inc. | Method for protecting a firewall load balancer from a denial of service attack |
| 7779126, | Oct 26 2000 | Cisco Technology, Inc. | System and method for propagating filters |
| 7779156, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Reputation based load balancing |
| 7779255, | Aug 01 2002 | International Business Machines Corporation | Multi-level security systems |
| 7779459, | Sep 28 2001 | Juniper Networks, Inc. | Method and apparatus for implementing a layer 3/layer 7 firewall in an L2 device |
| 7779466, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for anomaly detection in patterns of monitored communications |
| 7779476, | May 20 2002 | Extreme Networks, Inc | Active defense against wireless intruders |
| 7788726, | Jul 02 2003 | CHECK POINT SOFTWARE TECHNOLOGIES, INC | System and methodology providing information lockbox |
| 7797752, | Dec 17 2003 | RPX Corporation | Method and apparatus to secure a computing environment |
| 7805415, | Jun 10 2003 | ABACUS INNOVATIONS TECHNOLOGY, INC ; LEIDOS INNOVATIONS TECHNOLOGY, INC | Systems and methods for sharing data between entities |
| 7822980, | Mar 15 2002 | International Business Machines Corporation | Authenticated identity propagation and translation within a multiple computing unit environment |
| 7827402, | Dec 01 2004 | Cisco Technology, Inc. | Method and apparatus for ingress filtering using security group information |
| 7836490, | Oct 29 2003 | Cisco Technology, Inc. | Method and apparatus for providing network security using security labeling |
| 7836494, | Dec 29 1999 | Intel Corporation | System and method for regulating the flow of information to or from an application |
| 7840708, | Aug 13 2007 | Cisco Technology, Inc | Method and system for the assignment of security group information using a proxy |
| 7870203, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Methods and systems for exposing messaging reputation to an end user |
| 7870217, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | IP storage processor and engine therefor using RDMA |
| 7877601, | Nov 23 2004 | Cisco Technology, Inc. | Method and system for including security information with a packet |
| 7877796, | Nov 16 2004 | Cisco Technology, Inc. | Method and apparatus for best effort propagation of security group information |
| 7886145, | Nov 23 2004 | Cisco Technology, Inc. | Method and system for including security information with a packet |
| 7886340, | Jun 13 2003 | Intellectual Ventures II LLC | Secure remote management appliance |
| 7890658, | Sep 14 2005 | InfoExpress, Inc. | Dynamic address assignment for access control on DHCP networks |
| 7899722, | Mar 20 2001 | REGULATORY DATACORP, INC | Correspondent bank registry |
| 7900038, | Apr 29 2003 | WELLS FARGO BANK, N A | Method and apparatus for a broker entity |
| 7903549, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Content-based policy compliance systems and methods |
| 7904361, | Mar 20 2001 | REGULATORY DATACORP, INC | Risk management customer registry |
| 7917627, | Jul 12 2004 | Cisco Technology, Inc. | System and method for providing security in a network environment |
| 7937480, | Jun 02 2005 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Aggregation of reputation data |
| 7941829, | Oct 01 2003 | Gula Consulting Limited Liability Company | Near real-time multi-party task authorization access control |
| 7941837, | Apr 18 2007 | Juniper Networks, Inc. | Layer two firewall with active-active high availability support |
| 7944355, | Sep 01 2004 | Microsoft Technology Licensing, LLC | Security techniques in the RFID framework |
| 7949716, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Correlation and analysis of entity attributes |
| 7954145, | Sep 27 2007 | Oracle International Corporation | Dynamically configuring a client for virtual private network (VPN) access |
| 7954163, | Sep 10 2003 | Cisco Technology, Inc. | Method and apparatus for providing network security using role-based access control |
| 7958027, | Mar 20 2001 | REGULATORY DATACORP, INC | Systems and methods for managing risk associated with a geo-political area |
| 7958351, | Aug 29 2002 | CALLAHAN CELLULAR L L C | Method and apparatus for multi-level security implementation |
| 7969966, | Sep 29 2005 | WSOU Investments, LLC | System and method for port mapping in a communications network switch |
| 7970013, | Jun 16 2006 | Extreme Networks, Inc | Systems and methods for wireless network content filtering |
| 7971251, | Mar 17 2006 | Extreme Networks, Inc | Systems and methods for wireless security using distributed collaboration of wireless clients |
| 7996543, | Aug 16 2007 | RESTOREN PARTNERS | Client-to-client direct RTP exchange in a managed client-server network |
| 8000698, | Jun 26 2006 | Microsoft Technology Licensing, LLC | Detection and management of rogue wireless network connections |
| 8010789, | Nov 13 2003 | Lantronix, Inc. | Secure data transfer using an embedded system |
| 8016363, | Oct 15 2002 | HER MAJESTY THE QUEEN IN RIGHT OF CANADA, REPRESENTED BY THE MINISTER OF NATURAL RESOURCES, CANADA | Automated excavation machine |
| 8037530, | Aug 28 2000 | Verizon Patent and Licensing Inc | Method and apparatus for providing adaptive self-synchronized dynamic address translation as an intrusion detection sensor |
| 8042149, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for message threat management |
| 8042181, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for message threat management |
| 8045458, | Nov 08 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Prioritizing network traffic |
| 8051460, | Sep 24 2003 | InfoExpress, Inc. | Systems and methods of controlling network access |
| 8060939, | May 20 2002 | Extreme Networks, Inc | Method and system for securing wireless local area networks |
| 8065393, | Feb 24 2006 | Cisco Technology, Inc. | Method and system for obviating redundant actions in a network |
| 8069105, | Mar 20 2001 | REGULATORY DATACORP, INC | Hedge fund risk management |
| 8069481, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for message threat management |
| 8098158, | Sep 01 2004 | Microsoft Technology Licensing, LLC | RFID server internals design |
| 8108909, | Sep 24 2003 | InfoExpress, Inc. | Systems and methods of controlling network access |
| 8112788, | Sep 24 2003 | InfoExpress, Inc. | Systems and methods of controlling network access |
| 8117645, | Sep 24 2003 | InfoExpress, Inc. | Systems and methods of controlling network access |
| 8121937, | Mar 20 2001 | REGULATORY DATACORP, INC | Gaming industry risk management clearinghouse |
| 8132004, | Jun 12 2008 | The Boeing Company | Multiple independent levels of security containing multi-level security interface |
| 8132250, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Message profiling systems and methods |
| 8136149, | Jun 07 2004 | Check Point Software Technologies, Inc. | Security system with methodology providing verified secured individual end points |
| 8136152, | Feb 06 2007 | Intellectual Ventures II LLC | Method and system for securely scanning network traffic |
| 8136155, | Apr 01 2003 | CHECK POINT SOFTWARE TECHNOLOGIES, INC | Security system with methodology for interprocess communication control |
| 8140415, | Mar 20 2001 | REGULATORY DATACORP, INC | Automated global risk management |
| 8160975, | Jan 25 2008 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Granular support vector machine with random granularity |
| 8161281, | Apr 13 2006 | Rockwell Collins, Inc. | High assurance data tagger for I/O feeds |
| 8166549, | Jun 14 2001 | Stragent, LLC | Hash-based systems and methods for detecting and preventing transmission of polymorphic network worms and viruses |
| 8179798, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Reputation based connection throttling |
| 8181239, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | Distributed network security system and a hardware processor therefor |
| 8185930, | Nov 06 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Adjusting filter or classification control settings |
| 8196199, | Oct 19 2004 | AIRDEFENSE, LLC | Personal wireless monitoring agent |
| 8200818, | Jul 06 2001 | CHECK POINT SOFTWARE TECHNOLOGIES, INC | System providing internet access management with router-based policy enforcement |
| 8204945, | Jun 19 2000 | Stragent, LLC | Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail |
| 8209246, | Mar 20 2001 | REGULATORY DATACORP, INC | Proprietary risk management clearinghouse |
| 8214497, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Multi-dimensional reputation scoring |
| 8217756, | Sep 01 2004 | Microsoft Technology Licensing, LLC | Rule-based filtering and alerting |
| 8233626, | Oct 12 2007 | Hitachi, Ltd. | Storage system and storage system management method |
| 8261347, | Jan 25 2001 | NTT SECURITY US INC | Security system for a computer network having a security subsystem and a master system which monitors the integrity of a security subsystem |
| 8272060, | Jun 14 2001 | Stragent, LLC | Hash-based systems and methods for detecting and preventing transmission of polymorphic network worms and viruses |
| 8281392, | Aug 11 2006 | Extreme Networks, Inc | Methods and systems for wired equivalent privacy and Wi-Fi protected access protection |
| 8285615, | Mar 20 2001 | REGULATORY DATACORP, INC | Construction industry risk management clearinghouse |
| 8291114, | Sep 28 2001 | Juniper Networks, Inc. | Routing a packet by a device |
| 8301882, | Dec 01 2004 | Cisco Technology, Inc. | Method and apparatus for ingress filtering using security group information |
| 8302157, | Oct 21 2004 | Cisco Technology, Inc. | Method and system for generating user group identifiers |
| 8307419, | Dec 29 1999 | Intel Corporation | System and method for regulating communications to or from an application |
| 8312530, | Jul 12 2004 | Cisco Technology, Inc | System and method for providing security in a network environment using accounting information |
| 8316051, | Nov 30 2001 | Oracle International Corporation | Techniques for adding multiple security policies to a database system |
| 8327436, | Oct 25 2002 | Infrastructure architecture for secure network management with peer to peer functionality | |
| 8327451, | Aug 30 2002 | Slingshot IOT LLC | Secure system and method for enforcement of privacy policy and protection of confidentiality |
| 8341707, | Oct 02 2003 | Gula Consulting Limited Liability Company | Near real-time multi-party task authorization access control |
| 8347350, | Sep 24 2003 | InfoExpress, Inc. | Systems and methods of controlling network access |
| 8347351, | Sep 24 2003 | InfoExpress, Inc. | Systems and methods of controlling network access |
| 8352729, | Jul 29 2008 | International Business Machines Corporation | Secure application routing |
| 8353025, | Sep 27 2007 | Oracle International Corporation | Method and system for dynamically establishing a virtual private network (VPN) session |
| 8364580, | Nov 14 2002 | GOLDMAN SACHS & CO LLC | Independent research consensus earnings estimates and methods of determining such |
| 8375199, | Feb 12 2002 | Goldman, Sachs & Co. | Automated security management |
| 8375206, | Jan 21 2000 | SONY NETWORK ENTERTAINMENT PLATFORM INC ; Sony Computer Entertainment Inc | Authentication and encryption utilizing command identifiers |
| 8402101, | Feb 25 2005 | Rockwell Automation Technologies, Inc. | Reliable messaging instruction |
| 8458718, | Aug 27 2009 | The Boeing Company | Statically partitioning into fixed and independent systems with fixed processing core |
| 8468256, | Mar 08 2001 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Automatically configuring a computer firewall based on network connection |
| 8474016, | Jun 13 2002 | Intellectual Ventures II LLC | Secure management access control for computers, embedded and card embodiment |
| 8499330, | Nov 15 2005 | AT&T Properties, LLC; AT&T INTELLECTUAL PROPERTY II, L P | Enterprise desktop security management and compliance verification system and method |
| 8510334, | Nov 05 2009 | Oracle International Corporation | Lock manager on disk |
| 8539571, | Oct 29 2003 | Cisco Technology, Inc. | Method and apparatus for providing network security using security labeling |
| 8549611, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for classification of messaging entities |
| 8555056, | Nov 23 2004 | Cisco Technology, Inc. | Method and system for including security information with a packet |
| 8561140, | Nov 23 2004 | Cisco Technology, Inc. | Method and system for including network security information in a frame |
| 8561167, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Web reputation scoring |
| 8576854, | Jan 16 2004 | TRIOSYN HOLDING INC | System for communication between private and public IP networks |
| 8578051, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Reputation based load balancing |
| 8578444, | Sep 24 2003 | Info Express, Inc. | Systems and methods of controlling network access |
| 8578480, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for identifying potentially malicious messages |
| 8583935, | Mar 17 2003 | LONE STAR WIFI | Wireless network having multiple communication allowances |
| 8589503, | Apr 04 2008 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Prioritizing network traffic |
| 8595820, | Dec 17 2003 | RPX Corporation | Surround security system |
| 8606910, | Apr 04 2008 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Prioritizing network traffic |
| 8621559, | Nov 06 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Adjusting filter or classification control settings |
| 8621596, | Nov 16 2004 | Cisco Technology, Inc. | Method and apparatus for best effort propagation of security group information |
| 8621638, | May 14 2010 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for classification of messaging entities |
| 8631495, | Mar 08 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Systems and methods for message threat management |
| 8635690, | Nov 05 2004 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Reputation based message processing |
| 8650610, | Sep 24 2003 | InfoExpress, Inc. | Systems and methods of controlling network access |
| 8650643, | Aug 28 2000 | Verizon Patent and Licensing Inc | Method and apparatus for providing adaptive self-synchronized dynamic address translation as an intrusion detection sensor |
| 8660886, | May 17 2000 | Chartered Professional Accountants of Canada | Continuously updated data processing system and method for measuring and reporting on value creation performance that supports real-time benchmarking |
| 8661556, | Sep 10 2003 | Cisco Technology, Inc. | Method and apparatus for providing network security using role-based access control |
| 8666919, | Jul 29 2011 | Accenture Global Services Limited | Data quality management for profiling, linking, cleansing and migrating data |
| 8677450, | Sep 24 2003 | InfoExpress, Inc. | Systems and methods of controlling network access |
| 8689316, | Sep 28 2001 | Juniper Networks, Inc. | Routing a packet by a device |
| 8700535, | Feb 25 2003 | Microsoft Technology Licensing, LLC | Issuing a publisher use license off-line in a digital rights management (DRM) system |
| 8713201, | Aug 13 2007 | Cisco Technology, Inc. | Method and system for the assignment of security group information using a proxy |
| 8719171, | Feb 25 2003 | Microsoft Technology Licensing, LLC | Issuing a publisher use license off-line in a digital rights management (DRM) system |
| 8725646, | Apr 15 2005 | Microsoft Technology Licensing, LLC | Output protection levels |
| 8745219, | Jun 13 2002 | Intellectual Ventures II LLC | Out-of-band remote management station |
| 8752131, | Apr 30 2008 | Fujitsu Limited | Facilitating protection of a maintenance entity group |
| 8762191, | Jul 02 2004 | REGULATORY DATACORP, INC | Systems, methods, apparatus, and schema for storing, managing and retrieving information |
| 8762537, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Multi-dimensional reputation scoring |
| 8763114, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Detecting image spam |
| 8781969, | May 20 2005 | Microsoft Technology Licensing, LLC | Extensible media rights |
| 8782260, | Oct 09 1998 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Network access control system and method using adaptive proxies |
| 8788814, | Nov 13 2003 | LANTRONIX, INC | Secure data transfer using an embedded system |
| 8843411, | Mar 20 2001 | REGULATORY DATACORP, INC | Gaming industry risk management clearinghouse |
| 8849736, | Jul 29 2011 | Accenture Global Services Limited | Data quality management for profiling, linking, cleansing, and migrating data |
| 8874790, | Dec 30 2011 | Verisign, Inc | DNS package in a partitioned network |
| 8931075, | Sep 14 2009 | International Business Machines Corporation | Secure route discovery node and policing mechanism |
| 8931076, | Sep 14 2009 | International Business Machines Corporation | Secure route discovery node and policing mechanism |
| 8931077, | Jan 25 2001 | Solutionary, Inc. | Security system for a computer network having a security subsystem and a master system which monitors the integrity of a security subsystem |
| 8996481, | Jul 02 2004 | REGULATORY DATACORP, INC | Method, system, apparatus, program code and means for identifying and extracting information |
| 9009321, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Multi-dimensional reputation scoring |
| 9058581, | Jul 02 2004 | REGULATORY DATACORP, INC | Systems and methods for managing information associated with legal, compliance and regulatory risk |
| 9063985, | Jul 02 2004 | REGULATORY DATACORP, INC | Method, system, apparatus, program code and means for determining a redundancy of information |
| 9064210, | Mar 31 2012 | EMC IP HOLDING COMPANY LLC | Semantically-aware behavioral security analysis system for security information and event management |
| 9082076, | Jul 29 2011 | Accenture Global Services Limited | Data quality management for profiling, linking, cleansing, and migrating data |
| 9129043, | Dec 08 2006 | INFOSIL INC | 100GBPS security and search architecture using programmable intelligent search memory |
| 9141557, | Dec 08 2006 | INFOSIL INC | Dynamic random access memory (DRAM) that comprises a programmable intelligent search memory (PRISM) and a cryptography processing engine |
| 9237158, | Sep 10 2003 | Cisco Technology, Inc. | Method and apparatus for providing network security using role-based access control |
| 9240890, | Mar 15 2006 | Fortinet, Inc. | Computerized system and method for deployment of management tunnels |
| 9246586, | May 15 2001 | SRI International | Method and system for enabling and controlling communication topology, access to resources, and document flow in a distributed networking environment |
| 9294286, | Mar 15 2006 | Fortinet, Inc. | Computerized system and method for deployment of management tunnels |
| 9300638, | Aug 28 2000 | Verizon Patent and Licensing Inc | Method and apparatus for providing adaptive self-synchronized dynamic address translation as an intrusion detection sensor |
| 9317718, | Mar 29 2013 | SECTURION SYSTEMS, INC | Security device with programmable systolic-matrix cryptographic module and programmable input/output interface |
| 9355279, | Mar 29 2013 | SECTURION SYSTEMS, INC | Multi-tenancy architecture |
| 9397978, | Dec 21 2012 | Western Digital Technologies, Inc.; Western Digital Technologies, INC | Cloud to local router security |
| 9407509, | Nov 09 1998 | SRI International | Network surveillance |
| 9407604, | Nov 16 2004 | Cisco Technology Inc. | Method and apparatus for best effort propagation of security group information |
| 9407605, | Sep 28 2001 | Juniper Networks, Inc. | Routing a packet by a device |
| 9461979, | Oct 11 2013 | Cisco Technology, Inc. | Method and system for including network security information in a frame |
| 9485218, | Mar 23 2010 | Adventium Enterprises, LLC; Adventium Enterprises | Device for preventing, detecting and responding to security threats |
| 9524399, | Apr 01 2013 | SECTURION SYSTEMS, INC | Multi-level independent security architecture |
| 9544272, | Jan 24 2007 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Detecting image spam |
| 9589158, | Dec 08 2006 | INFOSIL INC | Programmable intelligent search memory (PRISM) and cryptography engine enabled secure DRAM |
| 9667723, | Jun 11 2002 | MEMORY ACCESS TECHNOLOGIES LLC | High performance IP processor using RDMA |
| 9673987, | Mar 15 2006 | Fortinet, Inc. | Computerized system and method for deployment of management tunnels |
| 9674268, | Apr 08 2008 | RPS CANADA INC | System and method for providing data and application continuity in a computer system |
| 9794064, | Sep 17 2015 | SECTURION SYSTEMS, INC | Client(s) to cloud or remote server secure data or file object encryption gateway |
| 9798899, | Mar 29 2013 | SECTURION SYSTEMS, INC | Replaceable or removable physical interface input/output module |
| 9825915, | Mar 15 2006 | Fortinet, Inc. | Computerized system and method for deployment of management tunnels |
| 9858442, | Mar 29 2013 | SECTURION SYSTEMS, INC. | Multi-tenancy architecture |
| 9860254, | Sep 10 2003 | Cisco Technology, Inc. | Method and apparatus for providing network security using role-based access control |
| 9860310, | Apr 08 2008 | RPS CANADA INC | System and method for providing data and application continuity in a computer system |
| 9912543, | Dec 30 2011 | Verisign, Inc | DNS package in a partitioned network |
| 9952983, | Dec 08 2006 | Programmable intelligent search memory enabled secure flash memory |
| Patent | Priority | Assignee | Title |
| 4797928, | Jan 07 1987 | MIU INDUSTRIES LTD 1600-609 GRANVILLE STREET | Encryption printed circuit board |
| 4845717, | Nov 14 1986 | Kabushiki Kaisha Toshiba | IC card having two output buffers |
| 4987595, | Sep 11 1989 | GENERAL DYNAMICS C4 SYSTEMS, INC | Secure cryptographic processor arrangement |
| 5075884, | Dec 23 1987 | Lockheed Martin Corporation | Multilevel secure workstation |
| 5155829, | Jan 21 1986 | Sheyu Group, LLC | Memory system and method for protecting the contents of a ROM type memory |
| 5263147, | Mar 01 1991 | Hughes Training, Inc. | System for providing high security for personal computers and workstations |
| 5297255, | Jan 19 1988 | Hitachi, Ltd. | Parallel computer comprised of processor elements having a local memory and an enhanced data transfer mechanism |
| 5459851, | Feb 12 1991 | Mitsubishi Denki Kabushiki Kaisha | Dual-port memory with selective read data output prohibition |
| 5548721, | Apr 28 1994 | W D BURGEON, LIMITED LIABILITY COMPANY | Method of conducting secure operations on an uncontrolled network |
| 5577209, | Jul 11 1991 | Round Rock Research, LLC | Apparatus and method for providing multi-level security for communication among computers and terminals on a network |
| 5602918, | Dec 22 1995 | SSL SERVICES LLC | Application level security system and method |
| 5603031, | Jul 08 1993 | Intellectual Ventures I LLC | System and method for distributed computation based upon the movement, execution, and interaction of processes in a network |
| 5623601, | Nov 21 1994 | RPX Corporation | Apparatus and method for providing a secure gateway for communication and data exchanges between networks |
| 5638448, | Oct 24 1995 | Network with secure communications sessions | |
| 5680452, | Sep 13 1994 | TECSEC Inc.; TecSec Incorporated | Distributed cryptographic object method |
| 5689566, | Oct 24 1995 | Network with secure communications sessions | |
| 5692124, | Aug 30 1996 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Support of limited write downs through trustworthy predictions in multilevel security of computer network communications |
| 5699513, | Mar 31 1995 | GENERAL DYNAMICS C4 SYSTEMS, INC | Method for secure network access via message intercept |
| 5701343, | Dec 01 1994 | Nippon Telegraph & Telephone Corporation | Method and system for digital information protection |
| 5724027, | Sep 28 1995 | Intel Corporation | Method and apparatus for providing system security to personal computer systems using transparent system interrupt |
| 5765036, | Oct 06 1994 | VIRTUAL RESOURCE COMMUNICATIONS, INC | Shared memory device with arbitration to allow uninterrupted access to memory |
| 5787310, | Jan 31 1995 | Mitsubishi Denki Kabushiki Kaisha | Microcomputer |
| 5802178, | Jul 30 1996 | Round Rock Research, LLC | Stand alone device for providing security within computer networks |
| 5818939, | Dec 18 1996 | Intel Corporation | Optimized security functionality in an electronic system |
| 5822435, | Jul 10 1992 | McAfee, Inc | Trusted path subsystem for workstations |
| 5822784, | Mar 19 1993 | Intel Corporation | Mechanism supporting execute in place read only memory applications located on removable computer cards |
| 5860021, | Apr 24 1997 | INTELLECTUAL VENTURES ASSETS 12 LLC; SK HYNIX INC | Single chip microcontroller having down-loadable memory organization supporting "shadow" personality, optimized for bi-directional data transfers over a communication channel |
| 6081848, | Aug 14 1998 | Intel Corporation | Striping packets of data across multiple virtual channels |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Aug 06 1998 | Cryptek Secure Communications, LLC | (assignment on the face of the patent) | / | |||
| Aug 25 1998 | WILLIAMS, TIMOTHY C | Cryptek Secure Communications, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 009408 | /0010 | |
| Jan 02 2002 | Cryptek Secure Communications, LLC | CRYPTEK, INC | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 013203 | /0751 | |
| Jan 14 2005 | CRYPTEK, INC | COMERICA BANK | SECURITY AGREEMENT | 015703 | /0527 | |
| Feb 26 2007 | COMERICA BANK | CRYPTEK, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 018961 | /0385 | |
| Aug 17 2007 | API CRYPTEK INC | API CRYPTEK INC | FORECLOSURE BILL OF SALE | 024794 | /0142 | |
| Aug 17 2007 | CRYPTEK, INC | Wachovia Bank, National Association | SECURITY AGREEMENT | 024927 | /0349 | |
| Aug 17 2007 | CRYPTEK, INC | WACHOVIA CAPITAL FINANCE CORPORATION | SECURITY AGREEMENT | 024927 | /0349 | |
| Jun 23 2009 | Wachovia Bank, National Association | API CRYPTEK INC | LOAN PURCHASE AGREEMENT | 024927 | /0475 | |
| Jun 23 2009 | WACHOVIA CAPITAL FINANCE CORPORATION | API CRYPTEK INC | LOAN PURCHASE AGREEMENT | 024927 | /0475 | |
| Jul 07 2009 | API CRYPTEK INC | API CRYPTEK INC | CORRECTIVE ASSIGNMENT TO CORRECT THE RE-RECORDING THE EXECUTION DATE PREVIOUSLY RECORDED ON REEL 024794 FRAME 0142 ASSIGNOR S HEREBY CONFIRMS THE FORECLOSURE-BILL OF SALE | 025422 | /0620 | |
| Apr 20 2011 | API CRYPTEK INC | RBC BANK USA | SECURITY AGREEMENT | 026305 | /0163 | |
| Jun 01 2011 | API CRYPTEK, INC | MORGAN STANLEY SENIOR FUNDING, INC , AS COLLATERAL AGENT | SECURITY INTEREST | 026417 | /0670 | |
| Jun 01 2011 | RBC BANK USA | API CRYPTEK INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 026373 | /0573 | |
| Feb 06 2013 | API DEFENSE, INC | GUGGENHEIM CORPORATE FUNDING, LLC | PATENT SECURITY AGREEMENT | 029777 | /0130 | |
| Feb 06 2013 | API NANOFABRICATLON AND RESEARCH CORPORATION | WELLS FARGO BANK, NATIONAL ASSOCIATION AS AGENT | SECURITY AGREEMENT | 029800 | /0494 | |
| Feb 06 2013 | SPECTRUM MICROWAVE, INC | WELLS FARGO BANK, NATIONAL ASSOCIATION AS AGENT | SECURITY AGREEMENT | 029800 | /0494 | |
| Feb 06 2013 | SPECTRUM CONTROL, INC | WELLS FARGO BANK, NATIONAL ASSOCIATION AS AGENT | SECURITY AGREEMENT | 029800 | /0494 | |
| Feb 06 2013 | API CRYPTEK INC | WELLS FARGO BANK, NATIONAL ASSOCIATION AS AGENT | SECURITY AGREEMENT | 029800 | /0494 | |
| Feb 06 2013 | MORGAN STANLEY SENIOR FUNDING, INC , AS COLLATERAL AGENT | API CRYPTEK, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 029767 | /0651 | |
| Feb 06 2013 | SPECTRUM MICROWAVE, INC | GUGGENHEIM CORPORATE FUNDING, LLC | PATENT SECURITY AGREEMENT | 029777 | /0130 | |
| Feb 06 2013 | API CRYPTEK INC | GUGGENHEIM CORPORATE FUNDING, LLC | PATENT SECURITY AGREEMENT | 029777 | /0130 | |
| Feb 06 2013 | SPECTRUM CONTROL, INC | GUGGENHEIM CORPORATE FUNDING, LLC | PATENT SECURITY AGREEMENT | 029777 | /0130 | |
| Feb 06 2013 | National Hybrid, Inc | GUGGENHEIM CORPORATE FUNDING, LLC | PATENT SECURITY AGREEMENT | 029777 | /0130 | |
| Feb 06 2013 | API DEFENSE INC | WELLS FARGO BANK, NATIONAL ASSOCIATION AS AGENT | SECURITY AGREEMENT | 029800 | /0494 | |
| Feb 06 2013 | API Nanofabrication and Research Corporation | GUGGENHEIM CORPORATE FUNDING, LLC | PATENT SECURITY AGREEMENT | 029777 | /0130 | |
| Feb 06 2013 | NATIONAL HYBRID INC , | WELLS FARGO BANK, NATIONAL ASSOCIATION AS AGENT | SECURITY AGREEMENT | 029800 | /0494 | |
| Mar 21 2014 | Wells Fargo Bank, National Association, As Agent | API CRYPTEK INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 032501 | /0458 | |
| Mar 21 2014 | Wells Fargo Bank, National Association, As Agent | National Hybrid, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 032501 | /0458 | |
| Mar 21 2014 | Wells Fargo Bank, National Association, As Agent | API Nanofabrication and Research Corporation | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 032501 | /0458 | |
| Mar 21 2014 | Wells Fargo Bank, National Association, As Agent | API DEFENSE, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 032501 | /0458 | |
| Mar 21 2014 | Wells Fargo Bank, National Association, As Agent | SPECTRUM MICROWAVE, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 032501 | /0458 | |
| Mar 21 2014 | Wells Fargo Bank, National Association, As Agent | SPECTRUM CONTROL, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 032501 | /0458 | |
| Apr 22 2016 | GUGGENHEIM CORPORATE FUNDING, LLC, AS AGENT | National Hybrid, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 038502 | /0459 | |
| Apr 22 2016 | GUGGENHEIM CORPORATE FUNDING, LLC, AS AGENT | SPECTRUM CONTROL, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 038502 | /0459 | |
| Apr 22 2016 | GUGGENHEIM CORPORATE FUNDING, LLC, AS AGENT | API DEFENSE, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 038502 | /0459 | |
| Apr 22 2016 | GUGGENHEIM CORPORATE FUNDING, LLC, AS AGENT | API CRYPTEK INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 038502 | /0459 | |
| Apr 22 2016 | GUGGENHEIM CORPORATE FUNDING, LLC, AS AGENT | SPECTRUM MICROWAVE, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 038502 | /0459 | |
| Apr 22 2016 | GUGGENHEIM CORPORATE FUNDING, LLC, AS AGENT | API Nanofabrication and Research Corporation | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 038502 | /0459 | |
| Apr 20 2018 | SPECTRUM MICROWAVE, INC | ANTARES CAPITAL LP, AS AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045595 | /0601 | |
| Apr 20 2018 | SPECTRUM CONTROL, INC | ANTARES CAPITAL LP, AS AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045595 | /0601 | |
| Apr 20 2018 | API TECHNOLOGIES CORP | ANTARES CAPITAL LP, AS AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045595 | /0601 | |
| May 09 2019 | Antares Capital LP | API TECHNOLOGIES, CORP | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 049132 | /0139 | |
| May 09 2019 | Antares Capital LP | SPECTRUM CONTROL, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 049132 | /0139 | |
| May 09 2019 | Antares Capital LP | SPECTRUM MICROWAVE, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 049132 | /0139 |
| Date | Maintenance Fee Events |
| Jan 28 2005 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
| Apr 27 2009 | REM: Maintenance Fee Reminder Mailed. |
| Oct 16 2009 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Oct 16 2009 | M1555: 7.5 yr surcharge - late pmt w/in 6 mo, Large Entity. |
| Oct 19 2009 | STOL: Pat Hldr no Longer Claims Small Ent Stat |
| Feb 16 2011 | ASPN: Payor Number Assigned. |
| May 24 2013 | REM: Maintenance Fee Reminder Mailed. |
| Sep 12 2013 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
| Sep 12 2013 | M1556: 11.5 yr surcharge- late pmt w/in 6 mo, Large Entity. |
| Date | Maintenance Schedule |
| Oct 16 2004 | 4 years fee payment window open |
| Apr 16 2005 | 6 months grace period start (w surcharge) |
| Oct 16 2005 | patent expiry (for year 4) |
| Oct 16 2007 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Oct 16 2008 | 8 years fee payment window open |
| Apr 16 2009 | 6 months grace period start (w surcharge) |
| Oct 16 2009 | patent expiry (for year 8) |
| Oct 16 2011 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Oct 16 2012 | 12 years fee payment window open |
| Apr 16 2013 | 6 months grace period start (w surcharge) |
| Oct 16 2013 | patent expiry (for year 12) |
| Oct 16 2015 | 2 years to revive unintentionally abandoned end. (for year 12) |