US 7,854,005 B2Grant
System and method for generating fictitious content for a computer
Issue Date:2010-12-14
•25 Claims
•16 Drawing Sheets
Abstract
A system and method are disclosed for generating fictitious computer file system content. A template is created. A collection of data items available to be inserted into the template is provided. The template is populated with at least one data item from the collection.
Metadata
Assignee
- Symantec Corporation
Inventors
- Michael P. Lyle
- Robert F. Ross
- James R. Maricondo
Application Information
Application Number:US 11/506,758
Filing Date:2006-08-18
Priority Date:1999-07-14
Art Unit:2431
Classifications
IPC:
G06F21/20G06F12/14G06F12/16
Patent Drawings (16 sheets)
Description
Cross Reference to Related Applications
[0001] This application is a divisional of U.S. patent application Ser. No. 09/616,805, entitled SYSTEM AND METHOD FOR GENERATING FICTITIOUS CONTENT FOR A COMPUTER filed Jul. 14, 2000 now U.S. Pat. No. 7,117,532, which claims priority to U.S. Provisional Patent Application No. 60/143,821 entitled “SYSTEM AND METHOD FOR COMPUTER SECURITY” filed Jul. 14, 1999, which is incorporated herein by reference for all purposes, and U.S. Provisional Patent Application No. 60/151,531 entitled “SYSTEM AND METHOD FOR PROVIDING COMPUTER SECURITY” filed Aug. 30, 1999, which is incorporated herein by reference for all purposes.
[0002] This application is related to U.S. patent application Ser. No. 09/615,967 entitled SYSTEM AND METHOD FOR COMPUTER SECURITY filed Jul. 14, 2000, now U.S. Pat. No. 6,981,155, and co-pending U.S. patent application Ser. No. 09/615,891 entitled SYSTEM AND METHOD FOR PREVENTING DETECTION OF A SELECTED PROCESS RUNNING ON A COMPUTER filed Jul. 14, 2000, and co-pending U.S. patent application Ser. No. 09/616,469 entitled SYSTEM AND METHOD FOR PREVENTING DETECTION OF A COMPUTER CONNECTION TO AN EXTERNAL DEVICE filed concurrently herewith, which is incorporated herein by reference for all purposes.
Field of the Invention
[0003] The present invention relates generally to computers. More specifically, a system and method for generating fictitious content for a computer is disclosed.
Background of the Invention
[0004] Computers and networks of computers, such as local area networks (LAN) and wide area networks (WAN), are used by many businesses and other organizations to enable employees and other authorized users to access information, create and edit files, and communicate with one another, such as by e-mail, among other uses. Often, such networks are connected or are capable of being connected to computers that are not part of the network, such as by modem or via the Internet. In such cases, the network becomes vulnerable to attacks by unauthorized users, such as so-called computer “hackers”, who may be able to gain unauthorized access to files store on network computers by using ports or connections provided to connect the network to computers outside of the network.
[0005] One known technique for foiling an attacker seeking to gain unauthorized access to a computer or computer network is a so-called “honey pot.” A honey pot, in computer security parlance, is a computer system containing a set of files that are designed to lure a computer hacker or other attacker to access the files, such as by making it seem like the files are particularly important or interesting. Since the honey pot files are typically not actually working files, any activity in the honey pot files is suspicious and an attempt is made to identify and locate any user who accesses or attempts to access the files.
[0006] The major shortcoming of the honey pot approach is that by the time the attacker has accessed the honey pot files, the attacker has already gained access to the computer containing the files. The attacker also has access to other files on the same computer, and may be able to access other computers in the same computer network. There is typically no mechanism for restricting the hacker to viewing only the honey pot files.
[0007] A second known approach is to provide a deception server. A deception server contains false data. A router or firewall is configured to route suspected attackers to the deception server instead of permitting the suspected attacker to access the real computer system or network.
[0008] The major shortcoming of prior art deception servers is that it is relatively easy for attackers to discover they are in a deception server. Among other things, prior art deception servers cannot make it appear to an attacker that the attacker has been allowed on the actual computer or computer network. In addition, deception servers have only a limited number of files, with the result that it is relatively easy to determine that a deception server does not contain the full array of files typically found in a true server, such as a typical business network computer server.
[0009] As a result, there is a need for a way to deceive attackers into believing they have gained access to a true computer system, without actually allowing them to gain access to true files. In addition, there is a need for a way to monitor such attackers, without their knowing, to facilitate efforts to improve security measures and identify attackers.
Summary of the Invention
[0010] Accordingly, a system and method for generating fictitious file system content for a computer is disclosed.
[0011] It should be appreciated that the present invention can be implemented in numerous ways, including as a process, an apparatus, a system, a device, a method, or a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or electronic communication links. Several inventive embodiments of the present invention are described below.
[0012] In one embodiment, a template is created. A collection of data items available to be inserted into the template is provided. The template is populated with at least one data item from the collection.
[0013] A system for generating fictitious file system content for a computer is disclosed. In one embodiment, the system comprises a computer configured to populate a template with at least one data item from a collection of data items available to be inserted into the template and a database configured to store the collection. The computer includes memory configured to store the populated template in a file system.
[0014] A computer program product for generating fictitious file system content for a computer is disclosed. In one embodiment, the computer program product is embodied in a computer readable medium and comprises computer instructions for retrieving a template; accessing a collection of data items available to be inserted into the template; and populating the template with at least one data item from the collection.
[0015] These and other features and advantages of the present invention will be presented in more detail in the following detailed description and the accompanying figures, which illustrate by way of example the principles of the invention.
Brief Description of the Drawings
[0016] The present invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
[0017] FIG. 1 is a block diagram of a general purpose computer system 100 suitable for carrying out the processing in accordance with one embodiment of the present invention.
[0018] FIG. 2 is a schematic diagram of a system used in one embodiment to provide computer security.
[0019] FIG. 3 is a flow chart illustrating a process used in one embodiment to provide computer security using a trap system such as trap system 210 of FIG. 2 .
[0020] FIG. 4 is a flowchart illustrating a process used in one embodiment to install a trap system, as in step 302 of FIG. 3 .
[0021] FIG. 5 is an exemplary administration console display 500 used in one embodiment to provide a graphical user interface on the administration console for configuration and control of the trap system.
[0022] FIG. 6 is a flowchart illustrating a process used in one embodiment to generate file content for the trap, as required, e.g., in step 304 of FIG. 3 .
[0023] FIG. 7 is a flowchart illustrating a process used in one embodiment to set the trap, as in step 306 of FIG. 3 .
[0024] FIG. 8 is an illustration of a deception login screen 800 used in one embodiment to prompt an intruder who has been routed into the cage directory of the trap system to enter a login name.
[0025] FIG. 9 is a flowchart illustrating a process used in one embodiment to keep an intruder in the trap, as in step 312 of FIG. 3 .
[0026] FIG. 10 is a flowchart illustrating a process used in one embodiment to determine whether access to a particular file requested by an intruder is permitted, as in step 906 of FIG. 9 .
[0027] FIG. 11A is a flowchart illustrating a process used in one embodiment to monitor the activity of an intruder, as in step 314 of FIG. 3 .
[0028] FIG. 11B is a flow chart illustrating a process used in one embodiment to regenerate a virtual cage environment by using a product serial number as the seed for a pseudo random number generator.
[0029] FIG. 11C is a flow chart illustrating a process used in one embodiment to hide the connection between the administrative console and the trap host system by using a “connectionless” port, as discussed above in connection with step 1104 of FIG. 11A .
[0030] FIG. 12 is a schematic diagram of a system used in one embodiment to provide such a test environment.
[0031] FIG. 13 is a flowchart illustrating a process used in one embodiment to provide a virtual test environment to test the effect of a configuration change prior to implementing the configuration change on the actual computer system.
Detailed Description
[0032] A detailed description of a preferred embodiment of the invention is provided below. While the invention is described in conjunction with that preferred embodiment, it should be understood that the invention is not limited to any one embodiment. On the contrary, the scope of the invention is limited only by the appended claims and the invention encompasses numerous alternatives, modifications and equivalents. For the purpose of example, numerous specific details are set forth in the following description in order to provide a thorough understanding of the present invention. The present invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the present invention is not unnecessarily obscured.
[0033] FIG. 1 is a block diagram of a general purpose computer system 100 suitable for carrying out the processing in accordance with one embodiment of the present invention. FIG. 1 illustrates one embodiment of a general purpose computer system. Other computer system architectures and configurations can be used for carrying out the processing of the present invention. Computer system 100, made up of various subsystems described below, includes at least one microprocessor subsystem (also referred to as a central processing unit, or CPU) 102. That is, CPU 102 can be implemented by a single-chip processor or by multiple processors. CPU 102 is a general purpose digital processor which controls the operation of the computer system 100. Using instructions retrieved from memory 110, the CPU 102 controls the reception and manipulation of input data, and the output and display of data on output devices.
[0034] CPU 102 is coupled bi-directionally with memory 110 which can include a first primary storage, typically a random access memory (RAM), and a second primary storage area, typically a read-only memory (ROM). As is well known in the art, primary storage can be used as a general storage area and as scratch-pad memory, and can also be used to store input data and processed data. It can also store programming instructions and data, in the form of data objects and text objects, in addition to other data and instructions for processes operating on CPU 102. Also as well known in the art, primary storage typically includes basic operating instructions, program code, data and objects used by the CPU 102 to perform its functions. Primary storage devices 110 may include any suitable computer-readable storage media, described below, depending on whether, for example, data access needs to be bi-directional or uni-directional. CPU 102 can also directly and very rapidly retrieve and store frequently needed data in a cache memory (not shown).
[0035] A removable mass storage device 112 provides additional data storage capacity for the computer system 100, and is coupled either bi-directionally or uni-directionally to CPU 102. For example, a specific removable mass storage device commonly known as a CD-ROM typically passes data uni-directionally to the CPU 102, whereas a floppy disk can pass data bi-directionally to the CPU 102. Storage 112 may also include computer-readable media such as magnetic tape, flash memory, signals embodied on a carrier wave, PC-CARDS, portable mass storage devices, holographic storage devices, and other storage devices. A fixed mass storage 120 can also provide additional data storage capacity. The most common example of mass storage 120 is a hard disk drive. Mass storage 112, 120 generally store additional programming instructions, data, and the like that typically are not in active use by the CPU 102. It will be appreciated that the information retained within mass storage 112, 120 may be incorporated, if needed, in standard fashion as part of primary storage 110 (e.g. RAM) as virtual memory.
[0036] In addition to providing CPU 102 access to storage subsystems, bus 114 can be used to provide access other subsystems and devices as well. In the described embodiment, these can include a display monitor 118, a network interface 116, a keyboard 104, and a pointing device 106, as well as an auxiliary input/output device interface, a sound card, speakers, and other subsystems as needed. The pointing device 106 may be a mouse, stylus, track ball, or tablet, and is useful for interacting with a graphical user interface.
[0037] The network interface 116 allows CPU 102 to be coupled to another computer, computer network, or telecommunications network using a network connection as shown. Through the network interface 116, it is contemplated that the CPU 102 might receive information, e.g., data objects or program instructions, from another network, or might output information to another network in the course of performing the above-described method steps. Information, often represented as a sequence of instructions to be executed on a CPU, may be received from and outputted to another network, for example, in the form of a computer data signal embodied in a carrier wave. An interface card or similar device and appropriate software implemented by CPU 102 can be used to connect the computer system 100 to an external network and transfer data according to standard protocols. That is, method embodiments of the present invention may execute solely upon CPU 102, or may be performed across a network such as the Internet, intranet networks, or local area networks, in conjunction with a remote CPU that shares a portion of the processing. Additional mass storage devices (not shown) may also be connected to CPU 102 through network interface 116.
[0038] An auxiliary I/O device interface (not shown) can be used in conjunction with computer system 100. The auxiliary I/O device interface can include general and customized interfaces that allow the CPU 102 to send and, more typically, receive data from other devices such as microphones, touch-sensitive displays, transducer card readers, tape readers, voice or handwriting recognizers, biometrics readers, cameras, portable mass storage devices, and other computers.
[0039] In addition, embodiments of the present invention further relate to computer storage products with a computer readable medium that contain program code for performing various computer-implemented operations. The computer-readable medium is any data storage device that can store data which can thereafter be read by a computer system. The media and program code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known to those of ordinary skill in the computer software arts. Examples of computer-readable media include, but are not limited to, all the media mentioned above: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as floptical disks; and specially configured hardware devices such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs), and ROM and RAM devices. The computer-readable medium can also be distributed as a data signal embodied in a carrier wave over a network of coupled computer systems so that the computer-readable code is stored and executed in a distributed fashion. Examples of program code include both machine code, as produced, for example, by a compiler, or files containing higher level code that may be executed using an interpreter.
[0040] The computer system shown in FIG. 1 is but an example of a computer system suitable for use with the invention. Other computer systems suitable for use with the invention may include additional or fewer subsystems. In addition, bus 114 is illustrative of any interconnection scheme serving to link the subsystems. Other computer architectures having different configurations of subsystems may also be utilized.
[0041] FIG. 2 is a schematic diagram of a system used in one embodiment to provide computer security. The system includes a computer network 202 to which the operator of the computer network wishes to limit access to authorized users. Computer network 202 is comprised of a plurality of network devices 204. The plurality of network devices 204 may include, for example, individual computer work stations, network servers, printers, and any number of other devices such as may be found in a typical computer network, such as a local area network (LAN) or wide area network (WAN). Computer network 202 also includes a Internet access server 206 configured to enable users of host computer systems connected to the computer network 202 to access the Internet and in particular to access web pages via the World Wide Web by sending and receiving hypertext transfer protocol (HTTP) transmissions. Computer network 202 also includes a firewall 208 interposed between Internet access server 206 and the network connection to the Internet. Firewall 208 may be either a firewall, or a router with firewall functionality, configured to route authorized users to Internet access server 206 and to detect and route unauthorized users to the trap system described below.
[0042] The system shown in FIG. 2 also includes a trap system 210. Trap system 210 is comprised of a trap host system 212 in which a virtual cage 214 is established, as described below. Trap system 210 also includes an administration console 216 connected to trap host system 212 and configured to enable a system administrator (or other authorized user) to control the configuration of trap host system 212 and virtual cage 214. Trap system 210 also includes a database 218 used to store data relating to activities within trap host system 212 and virtual cage 214.
[0043] The system shown in FIG. 2 is designed to protect the computer network 202 from being accessed or otherwise compromised by an intruder who is attempting to gain access to computer network 202 via the Internet. FIG. 2 shows an exemplary intruder's system 220 such as might be used by a would-be intruder to attempt to gain access to the computer network 202 via the Internet.
[0044] FIG. 3 is a flow chart illustrating a process used in one embodiment to provide computer security using a trap system such as trap system 210 of FIG. 2 . The process begins with step 302 in which a trap system such as trap system 210 of FIG. 2 is installed. In step 304, the file content for a deception environment to be presented to would-be intruders is created. Examples of the content of the deception environment include fictitious content generated automatically as described below; non-confidential (i.e., public) files drawn from the computer network being protected, such as computer network 202 of FIG. 2 ; or a combination of fictitious and non-confidential file content.
[0045] In step 306, a trap is established within the trap system. For example, a virtual cage such as virtual cage 214, shown in FIG. 2 may be established within a trap host system, such as trap host system 212 of FIG. 2 , by establishing a file directory for the cage and copying the operating system of the trap host system—but not the modifications and additions to the operating system described below that function to monitor the intruder's actions, keep the intruder in the cage, and prevent the intruder from detecting that the intruder is in the cage—and the file system of the trap host system into the directory.
[0046] In step 308, a would-be intruder is detected, as described more fully below. In step 310, the would-be intruder is routed into the trap system, such as trap system 210 of FIG. 2 , as described more fully below. Once the intruder has been routed into the trap, in step 312 affirmative efforts can be made to ensure that the intruder does not break out of the trap system and gain access to the portions of computer network 202 that are being protected from unauthorized access. In step 314, the activity of the intruder within the trap system is monitored, as described more fully below.
[0047] Once the activity of the intruder has ceased, either because the intruder has discontinued the attempt to access computer network 202 or because the system administrator has terminated the intruder's connection with the system, it is determined in step 316 whether the changes to the configuration to the trap system that were made by the intruder during the attack will be kept in place. For example, a system administrator might wish to leave changes made by an intruder in place if the system administrator believes the same intruder may attempt a future attack and might realize that he or she has been routed into a deception environment, as opposed to gaining access to the true computer network, if the changes made by the intruder in the prior attack were not still present. If it is determined in step 316 that the changes will be kept, the process shown in FIG. 3 ends and the trap remains in place, as modified by the intruder, unless or until a future intruder is routed into the trap or the trap is reset. If it is determined in step 316 that the changes made by a particular intruder will not be kept, the process proceeds to step 318 in which the trap is reset to eliminate the changes made by the intruder. In one embodiment, the trap is reset by regenerating the trap to restore the trap environment to the condition it was in at the time the intruder was first routed into the trap. In one embodiment, additional content is added when the trap is regenerated to make it appear that additional content was created by users of the computer network during the time period from the last update of the trap to the time the trap was reset.
[0048] FIG. 4 is a flowchart illustrating a process used in one embodiment to install a trap system, as in step 302 of FIG. 3 . The process begins with step 402 in which a trap host system is installed. In one embodiment, the trap host system is a computer, such as an Intel or SPARC computer, running the Solaris 7 operating system. In one embodiment, application programs that the user of the trap system wishes to have appear in the deception environment may be installed in the trap host system prior to the installation of the trap system software and the establishment of the virtual cage environment into which the operating system and file system of the trap host system will be copied. In one embodiment, probabilistic data combined with random number data from a pseudo random number generator are used to determine which application programs will appear in the deception environment. In one embodiment, the nature of the business or other organization that uses the computer network influences which application programs are selected. For example, a financial institution may have different application programs, and different types of files, than a law firm.
[0049] In step 404, an administration console, such as administration console 216 of FIG. 2 , is installed. The administration console is a second computer system connected to the trap host system. The administration console is used to configure and control the operation of the trap host system. In addition, the administration console receives logging information from the trap host system concerning the activities of the intruder within the trap host system. In one embodiment, administration console 216 is a computer system running either a UNIX or a Windows operating system. The administration console uses its connection to the trap host system to retrieve log and configuration information for the purpose of displaying the information to the system administrator.
[0050] In step 406, the trap host system is configured. As noted above, the administration console 216 is used to select configuration options for the trap software, once the trap software has been installed in the trap host system. In one embodiment, upon installation, the trap software automatically configures the trap host system in accordance with the preferences selected by the system administrator or other authorized user of the system by means of the administration console and randomly generated variations in certain system settings, as described more fully below.
[0051] The process shown in FIG. 4 continues with step 408 in which a network connection is made between the trap system and the router or firewall used in the computer network being protected to detect and route would-be intruders into the trap system. In one embodiment, network connections are made between the trap host system and the router or firewall for all or selected ones of the remote access services that an intruder might use to attempt to gain unauthorized access to, or control over, a target computer or computer network. In one embodiment, the trap host system operating system is the Solaris 7 operating system and the remote access services for which a network connection is established include FTP (file transfer protocol), telnet, and/or other services considered to be in the so-called “demilitarized zone”, or “DMZ”, of the network being protected.
[0052] In step 410, the policy editor of the router or firewall, which is typically provided as part of the software associated with a router or firewall, is used to establish policies which will route likely intruders to the trap host system. Such policies may include, where supported by the particular router or firewall being used, a policy that attempts to gain access to the computer network via a port or service not normally used by the computer network, but known to be exploited by hackers and other intruders to gain access to computer networks, such as the FTP and telnet ports, for example, can be routed to the corresponding port of the trap host system. In one embodiment, a would-be intruder is permitted to see the devices behind the router or firewall. If the would-be intruder seeks to gain access to the virtual cage environment, which can be configured to appear to be an interesting and easy target for intrusion (e.g. because services that are known to be exploitable to gain unauthorized access or control, such as FTP and telnet, will be available), the router or firewall can be configured in step 410 to route the intruder to the appropriate port of the trap host system using well known network address translation (NAT) techniques. In one embodiment, a would-be intruder cannot see the devices behind the router or firewall and any attempt to access a prohibited service on any network system is routed instead to the trap host system using NAT.
[0053] FIG. 5 is an exemplary administration console display 500 used in one embodiment to provide a graphical user interface on the administration console for configuration and control of the trap system. The administration console display 500 includes a menu display area 502 in which menu choices are displayed. As shown in FIG. 5 , in one embodiment, the major headings “General”, “Decoy User Names”, “Logging”, “Alerting”, and “Advanced” are displayed in menu display area 502. In one embodiment, selection of a major menu listing results in the subheadings under that menu listing being displayed. Display 500 also includes an instruction display area 504 in which instructions relating to the current menu selection are displayed. Display 500 also includes an input area 506 in which the system administrator or other user either enters data or selects an option from a pick list to provide input with respect to the current menu selection.
[0054] In one embodiment, the “General” menu provides options for entering the name of the company using the trap system; entering a license key or serial number for the system; entering a host name to be used in the contents created for the deception environment to identify the host associated with certain content; and to designate a domain name to be used for similar purposes, such as to be included as the domain name for Internet e-mail addresses for the fictitious and other user names used in the e-mail messages generated to be included in the deception environment. In one embodiment, the menu selection “Decoy User Name” enables the system administrator to provide the full name and a login or user name for from one to five individuals. Such an option may be used to provide the name of from one to five prominent and publicly-known individuals associated with the computer system being protected, such as the chief executive officer and/or president of the company that uses the system.
[0055] In one embodiment, the menu option labeled “Logging” includes options that enable the system administrator to route logging information from the trap system to a remote logging device, such as by providing the DNS name or IP address of the remote logging server. In addition, the “Logging” menu in one embodiment includes an option to either enable remote logging, as described above, or to disable remote logging and to have the log information spooled only to the trap host system. Finally, the “Logging” menu option in one embodiment includes an option that permits the system administrator to designate the name of the network interface used to gather information on an intruder's network activity, for example for use in later tracing the source of an intruder's attack.
[0056] In one embodiment the menu heading “Alerting” provides options for controlling the manner in which alerts regarding intruder activity is provided and the criteria used to determine when such an alert should be sent. The purpose of such an alert is to advise the system administrator that an intruder has gained a certain level of access to or control over the trap system. Providing such an alert enables the system administrator to more closely monitor the intruder and, if necessary, to cut off the intruder's connection to the system. The degree to which an intruder has gained unauthorized access or control is sometimes referred to as the extent to which the security of the system or network has been compromised by the intruder. In one embodiment, the options under the menu heading “Alerting” include the options to designate an e-mail address to be used to provide alerts, a fictitious subject line to be used in such e-mail messages, and an option for selecting an alert threshold.
[0057] For example, in one embodiment, one of five alert thresholds may be selected. The lowest threshold provides that no e-mail alert messages will be sent regardless of the type or severity of the compromise achieved by the intruder. A somewhat higher threshold provides for an e-mail alert message to be sent if the trap host computer system experiences a fatal error, for example if the host runs out of disk space. The next higher level provides for an e-mail alert message to be sent in a clear case of compromise such as if a new process has started within the virtual cage environment in the trap host system. The next somewhat higher level of alert provides for an e-mail alert message to be sent in situations that indicate a possible security compromise, such as if multiple port connections are opened by an intruder in an attempt to determine which processes are currently running on the host system. The most sensitive and final level of alert provides for an e-mail alert message to be sent whenever the virtual cage environment experiences any traffic, regardless of type. At this heightened level, alert messages may be generated based on intruder activity within the cage environment even in cases where there is no information indicating that the cage has been compromised or is in risk of being compromised.
[0058] Finally, the menu heading “Advanced” in one embodiment provides options for customizing the file content for the virtual cage environment and for making more complex configuration changes, to accomplish such goals as optimizing system performance or to otherwise tailor the trap system to the specific needs of a particular user.
[0059] Referring further to FIG. 5 , the administration console display 500 also includes a back button 508 and a next button 510 used to navigate back to the previous menu option or forward to the next menu option, respectively. The display 500 also includes a revert button 512 used to cancel a configuration change entered at the administration console and revert to the configuration settings that were in place prior to any changes being made. Display 500 also includes an update button 514 used to update a file maintained locally at the administration console to store configuration changes entered at the administration console but not yet applied to the trap host system. Display 500 also includes an apply button 516 used to apply configuration changes entered at the administration console to the trap host system. Finally, display 500 includes a reboot button 518, which causes the trap host system to reboot. In one embodiment, it is necessary to reboot the trap host system in order for configuration changes to be implemented in the trap host system.
[0060] FIG. 6 is a flowchart illustrating a process used in one embodiment to generate file content for the trap, as required, e.g., in step 304 of FIG. 3 . The process begins with step 602 in which operating system settings are generated automatically for the operating system installed in the trap host system. Operating system settings are generated automatically, with random variations included, to avoid having the same operating system configuration for each trap system. If such variations were not introduced, would-be intruders might be able to recognize that a system is a trap system provided by a particular manufacturer based on the presence of a standard operating system configuration used by the manufacturer.
[0061] Next, in step 604, information is generated automatically concerning the hardware installed on the trap host system, the configuration of such hardware, and other information concerning the configuration of the trap host system.
[0062] The process continues with step 606 in which selected real data and files are received and loaded. Any selected real files to be made available in the trap system, such as publicly-available documents or information, are stored in the file system or the trap host system. Real data to be used to fill in document templates, such as the names of key employees or other publicly-known individuals, are stored in the applicable database.
[0063] Then, in step 608, a database of fictitious names to be used in automatically generated e-mail and other documents is generated. A unique key or serial number provided with each copy of the software for the trap system serves in one embodiment as the seed for a pseudo random number generator. Numbers from the pseudo random number generator are used in conjunction with probabilistic data concerning the occurrence of first and last names from a database of names to generate a list of fictitious user names to be used to generate file content for a particular trap system.
[0064] The process continues with step 610 in which fictitious file content, such as fictitious e-mail, word processing document, spreadsheet, and other file content, is generated. In one embodiment, e-mail and other document templates are provided which require data values such as dates, names, product names, and other types of information to be inserted. Random numbers from a pseudo random number generator and probabilistic data are used to select a set of file templates to be used for the file content of a particular trap system. The set of templates to be used for any given system will be unique because the pseudo random number generator uses the unique product serial number or key for each particular system as the seed for the pseudo random number generator. Once the set of templates has been selected, the data values for each of the inputs required by each template are provided by using the pseudo random number generator and probabilistic data to select values from various databases of possible values provided for each type of input required by the templates.
[0065] An exemplary e-mail template used in one embodiment for generating an e-mail message announcing a meeting for a project identified by a code name follows:
-
- [0066] &MEETING: 10
- [0067] To: @EMPLOYEE
- [0068] Subject: Meeting re @PROJECT
- [0069] The meeting re @PROJECT will take place on @DAY, @MONTH @1TO28, at @TIME. The meeting will be held in @NAME=1's office. Coffee and rolls will be served. Please RSVP to @NAME=2 NLT (@DAY-1).
[0070] In the above exemplary template, the entry “&MEETING: 10” indicates that the template is a meeting announcement template with a relative probability of occurrence of 10. The relative probability of occurrence is a weight value for the template, which is based on studies of actual file systems found in a typical network server. The sum of all of the relative probability values for all templates appears at the top of the template file, and the relative likelihood that the above particular template will be selected at random from among the entire body of templates is determined by dividing the weight for the template, 10, by the sum of all of the weights. For example, if the sum of all of the weights were 1,000, the probability of the above template being selected would be 10/1,000. By comparison, a product launch announcement template might have a weight of only 1. The probability of such a template being selected would be 1/1,000, or about one tenth that of the above template. This would indicate that a product launch announcement e-mail would be one tenth as likely as a meeting announcement e-mail to be found in a typical network server. As described above, in one embodiment the selection of a set of templates for the initial file content for the trap file system would be based on the probability weight values and numbers generated by a pseudo random number generator.
[0071] The values of the variables @EMPLOYEE, @PROJECT, @DAY, @MONTH, @1TO28, @TIME, @NAME=1, and @NAME=2 in the above exemplary template are selected in one embodiment from corresponding files comprising possible values and a corresponding probability weight for each possible value. A number generated by a pseudo random number generator is used, in combination with the probability weights, to select the specific value for a particular instance. For example, the value of the variable @EMPLOYEE is selected at random from a file comprising names of fictitious employees and associated data, such as network usernames, e-mail addresses, and host system identification information. In one embodiment, the variable @EMPLOYEE is replaced with the e-mail address of from one to ten fictitious employees (and other information required for a file comprising an e-mail to the employee(s)), with the precise number of recipients being determined at random. In a similar manner, a day of the week would be selected as the value of the variable @DAY, a month for the variable @MONTH, a number from 1 to 28 for the variable @1TO28, and a time (e.g., at half hour increments during business hours) for the variable @TIME, would be chosen at random from corresponding files of possible values.
[0072] A similar technique may be used to select values for the variables @NAME=1 and @NAME=2 from a file containing the fictitious user names, created as described above. The annotations “=1” and “=2” indicate that a different name should be selected for each variable.
[0073] For certain types of variables, probabilities of occurrence would be considered in one embodiment in selecting the value. For example, the value for the variable @PROJECT is selected in one embodiment from a file such as the following:
-
- [0074] @PROJECT: 90
- [0075] 10: SPEAR
- [0076] 20: WIN
- [0077] 20: SPEED
- [0078] 10: NORMANDY
- [0079] 10: STORM
- [0080] 20: VICTORY
[0081] In the above file, the entry “@PROJECT: 90” identifies the files as containing possible values for the variable @PROJECT and indicates the sum of the probability weights for the possible values is 90. (In one embodiment, if the relative probability of occurrence of each value were the same, the number after the colon would be the total number of possible values in the file and the relative weight of each value would be assumed to be 1.) Each of the remaining entries in the file comprises a probability weight followed by a possible value. For example, the entry “10: SPEAR” has a probability weight of 10 and a value of “SPEAR”. The weight indicates the value SPEAR has a 10 in 90 (i.e., one in nine) probability of occurrence. The value chosen for a particular instance of a template is selected using a number generated by a pseudo random number generator and the probabilistic data.
[0082] In one embodiment, spelling, grammatical, and typographical errors are introduced into at least certain portions of the generated file content. Probabilistic data concerning the occurrence of such errors and a pseudo random number generator are used to determine the nature and location of the errors that are introduced.
[0083] In one embodiment, additional file content is generated, in the manner described above, at random intervals after the initial set of file content has been generated. In one embodiment, a pseudo random number generator is used to determine the intervals at which additional file content is generated. In one embodiment, file content is generated at more frequent intervals during certain times of the day, such as business hours, than during other times of the day. Additional file content is generated over time in order to provide a more realistic deception environment. For example, if an intruder accesses the trap system on one occasion and later returns to access the trap system in the future, the intruder may become suspicious if no additional file content has been generated in the file system since the initial attack. In addition, even if an intruder only accesses the file system on one occasion, the intruder may become suspicious if the system has been installed for a considerable period of time and no additional file content has been generated since the time of installation.
[0084] FIG. 7 is a flowchart illustrating a process used in one embodiment to set the trap, as in step 306 of FIG. 3 . The process begins with step 702 in which a cage is established within the trap host system. In one embodiment, this is accomplished by creating within the file system of the trap host system a new directory to contain the file structure for the cage.
[0085] In step 704, the operating system of the trap host system is copied into the cage directory. As described more fully below, the interface to the operating system kernel is modified to monitor the intruder's actions (e.g., by generating log data regarding an intruders activities), keep the intruder in the cage, and prevent the intruder from detecting that the intruder is in the cage. The files and programs that perform these latter functions are not copied into the cage. In step 706, the file system of the trap host system is copied into the cage directory.
[0086] By copying the operating system of the trap host system and the file system of the trap host system into the cage directory, it becomes easier to route an intruder into the cage directory and present to the intruder a deception environment that leads the intruder to believe that the intruder has successfully gained access to the operating system and file system of the computer the intruder is targeting. From time to time, additional file content is generated and added to the copy of the file system in the cage directory, as described above, to provide a more realistic deception environment.
[0087] Once an intruder has been detected and routed into the cage directory of the trap host system, a deception environment is presented to the intruder. The intruder interacts with the instance of the operating system running in the virtual cage environment. FIG. 8 is an illustration of a deception login screen 800 used in one embodiment to prompt an intruder who has been routed into the cage directory of the trap system to enter a login name. In one embodiment, the trap host system is configured to make it relatively easy for an intruder to obtain a login or user name and the corresponding password that will enable the intruder to gain access to the trap system using well-known hacking techniques.
[0088] FIG. 9 is a flowchart illustrating a process used in one embodiment to keep an intruder in the trap, as in step 312 of FIG. 3 . The process begins with step 902 in which a request to access a file within the cage directory is received from the intruder. In one embodiment, a software module is provided to serve as a filter between requests made by an intruder to access a file, on the one hand, and the copy of the file system contained in the cage directory of the trap system, on the other hand. Such filtering software is used to prevent the intruder from accessing files that might enable the intruder to discovery that the intruder is in a trap system, and not an actual system, as described more fully below.
[0089] In step 904, the filtering software sends log information to the user-specified destination for logging data concerning activities of intruders.
[0090] The process continues with step 906 in which it is determined whether the intruder is permitted to access the particular file the intruder has requested. In one embodiment, the filtering software referred to above, and described more fully below, makes this determination. If it is determined in step 906 that the intruder is not permitted to access the requested file, the process proceeds to step 908 in which an indication is provided to the intruder that the requested file does not exist. If it is determined in step 906 that the intruder is authorized to access the requested file, the process proceeds to step 910 in which the intruder is provided access to the copy of the requested file contained within the cage directory in the trap system.
[0091] FIG. 10 is a flowchart illustrating a process used in one embodiment to determine whether access to a particular file requested by an intruder is permitted, as in step 906 of FIG. 9 . The process begins at step 1002 in which it is determined whether the intruder is attempting to request a file that is at a level within the trap host system file structure that is above the highest level of the cage file structure, i.e., above the directory created to hold the file structure and operating system for the cage. For example, in one embodiment, the trap host system operating system is Solaris 7™. In the Solaris 7 operating system, the command “/../proc”, for example may be used to gain access to the directory level above the file “proc”, which would normally be in the highest level of the file structure for a system such as the trap host system. If an intruder were able to use this command to move above the “proc” file in the cage directory (which is a copy of the proc file of the trap host system copied into the cage directory), the intruder likely would realize that the intruder has been contained within the cage directory and, once the intruder has broken out of the cage directory, the intruder is much more likely to be able to compromise the trap host system. In one embodiment, the “/../proc” command or similar commands that might be used to access a level of the trap host system file structure that is above the highest level of the cage file structure are filtered by a software module which recognizes such commands, prevents them from being executed, and provides an indication (as in step 1002) that an attempt is being made to move above the highest level of the cage file structure.
[0092] If it is determined in step 1002 that an attempt is being made to move above the highest level of the cage file structure, the process proceeds to step 1004 in which access to the requested file structure level is denied and an indication is provided to the intruder that the requested file does not exist, in accordance with step 908 of FIG. 9 . If it is determined in step 1002 that an attempt is not being made to move above the highest level of the cage file structure, the process proceeds to step 1006 in which it is determined whether the intruder is making an attempt to access a blocked network data file. For example, in the Solaris 7 operating system, all network devices have a major and minor number associated with them. It is known in the art of computer security and the art of computer hacking that files associated with certain device numbers are susceptible to being used to gain unauthorized access to or control over a target computer system. For example, in one embodiment the trap host system uses the Solaris 7 operating system for which the device files for devices that have a major number 7 and a minor number in the range of 0-7, or devices that have a major number 11 and a minor number 7, may be exploited by an intruder to gain an unauthorized level of access to or control over a target computer system. As a result, in one embodiment, it is determined in step 1006 whether the intruder is attempting to access the device files associated with a device having a major and minor number in one of the ranges listed above.
[0093] If it is determined in step 1006 that an attempt is being made to access a blocked network data file, the process proceeds to step 1008 in which access to the requested file is denied, and an indication is provided that the file does not exist in accordance with step 908 of FIG. 9 . If it is determined in step 1006 that an attempt to access a blocked network data file is not being made, the process proceeds to step 1010 in which it is determined whether an attempt is being made to access a process file for a process running outside of the virtual cage environment. Each computer operating system provides a way to monitor the processes or tasks currently being performed by the host system. In the Solaris 7 operating system, for example, a process table is provided in a file contained within the operating system's virtual file system. The process table is accessed by entering a file name in the directory “/proc”. In one embodiment, a software module is used to filter access to the “proc” file to limit an intruder's access to files associated with processes running within the cage environment and to prevent access to processes running on the trap host system outside of the virtual cage.
[0094] If it is determined in step 1010 that an attempt is being made to access a process file for a process running outside of the cage environment, the process of FIG. 10 proceeds to step 1012 in which access to the requested file is denied, and an indication is provided that the file does not exist in accordance with step 908 of FIG. 9 . If it is determined in step 1010 that an attempt is not being made to access a process file for a process running outside of the cage environment, the process proceeds to step 1014 in which access to the requested file is permitted in accordance with step 910 of FIG. 9 .
[0095] In one embodiment, at least one of the steps of the process illustrated in FIG. 10 is implemented by replacing one or more operating system functions in the system entry (or “sysent”) table with a new program designed to perform the above-described filtering function. In one embodiment, the new program returns the output of the original operating system function if access to a requested file (or process) is permitted (i.e., the file or process is within the virtual cage) and returns an indication that the file (or process) does not exist, if the file (or process) is not inside the cage. In one embodiment, a similar approach is used to modify the function that responds to system calls such as “kill”, in order to permit intruders to terminate only processes running inside the cage.
[0096] FIG. 11A is a flowchart illustrating a process used in one embodiment to monitor the activity of an intruder, as in step 314 of FIG. 3 . The process begins at step 1102 in which a log of the intruder's actions is maintained. In one embodiment, the software modules used to filter requests to access various types of files send information concerning each request by the intruder to access a file to a log file used to store information concerning the files requested by an intruder. In one embodiment, the trap system can be configured to log either each command entered by an intruder or to log each keystroke entered by the intruder. In addition to information concerning the intruder's actions sent by the filtering software modules described above, information concerning the processes running within the virtual cage environment and what specific tasks each process is performing is available from the existing process file system (/proc) and is logged along with the log information derived from the filtering software modules.
[0097] As noted above, the intruder is prevented from becoming aware of the monitoring and logging processes by operation of the software module that filters the intruder's requests to access files within the process file system to prevent access to files relating to the monitoring and logging processes.
[0098] The process shown in FIG. 11A also includes a step 1104 in which log information is made available to the system administrator or other user of the trap system at a graphical user interface (GUI) presented at a control station such as administration console 216 of FIG. 2 . This enables a system administrator or other user of the trap system either to perform an analysis of an intruder's actions subsequent to an attack or to monitor the actions of an intruder in real time, so as to be in a position, for example, to terminate the connection of the intruder to the trap host system if there is a risk the intruder may gain access to files outside of the virtual cage environment. In one embodiment, the connection of the administration console or other control system providing a graphical user interface for the trap system is hidden from detection by an intruder by use of a so-called “connectionless” port to provide for the exchange of information between the administration console and the trap host system, as described more fully below in connection with FIG. 11C .
[0099] The process illustrated in FIG. 11A also includes step 1106 in which it is determined whether the alert conditions established at the time the trap system was configured have been met. For example, in one embodiment, as described above, the “normal” level of alert conditions provides for the trap system to send an alert e-mail in a situation that indicates a possible security compromise, for example if multiple port connections are open, which may indicate that an intruder is attempting to determine which processes are currently running on the host system. As described above, a more sensitive level of alert may be established in which an alert e-mail message would be sent whenever the virtual cage environment experiences any activity, regardless of the type.
[0100] If it is determined in step 1106 that the alert conditions have not been met, the process proceeds to step 1108 in which the monitoring and logging of the intruder's activities continues until the intruder leaves the system. If it is determined in step 1106 that the alert conditions have been met, the process proceeds to step 1110 in which an alert is sent to the system administrator (or other designated user). In one embodiment, the alert is an e-mail message sent to the system administrator. In one embodiment, a subject line provided as part of the system configuration process is used to identify the nature of the message to an authorized individual who sees the subject line. If an alert has been sent in step 1110, the process continues with step 1112 in which the monitoring and logging of the intruder's activities continues either until the intruder voluntarily leaves the system or until the intruder's connection to the system is terminated by the system administrator, for example by regenerating the virtual cage environment, rebooting the trap host system, or changing the firewall rule set to no longer permit the intruder to access the trap host system.
[0101] The automatically logged information can be used to analyze the strategies and techniques used by the intruder to gain access to and attempt to gain control of the system. In one embodiment, another approach used to evaluate the activities of an intruder once an intruder has exited the system is to make a copy of the file system of the virtual cage environment and then to regenerate the virtual cage environment, as described above, and compare the regenerated virtual cage environment, which will not have any of the changes made by the intruder, with the copy of the virtual cage environment as modified by the activities of the intruder.
[0102] In one embodiment, a unique key is used to seed the pseudo random number generator used to generate content for the file system, as described above. In one embodiment, the key is the serial number of the copy of the trap software provided for a particular installation. Using a unique key to seed the pseudo random number generator ensures that the content of each trap system installed will be unique. The use of the same key to seed the pseudo random number generator each time the virtual cage environment for a particular installation is regenerated results in the same content being created each time the cage is regenerated. As a result, a returning intruder will see all of the same file content that was in the cage during the intruder's previous attack, even if the cage has been regenerated. If the changes made by the intruder during a prior attack were kept (i.e., the cage was not regenerated), the intruder will see the effects of the intruder's previous attack in the virtual cage environment. If the cage has been regenerated since a prior attack, the file system will contain the same file content the intruder saw during the previous attack, but will not contain changes made or caused by the intruder's activities. This is the same environment an intruder would expect to see if the system had been reconstructed, such as from back-up tapes. In either event, the intruder sees a sufficiently familiar environment that the intruder likely will continue to be deceived.
[0103] FIG. 11B is a flow chart illustrating a process used in one embodiment to regenerate a virtual cage environment by using a product serial number as the seed for a pseudo random number generator. The process begins with step 1120 in which a product serial number is received. In step 1122, the product serial number is used as the seed for a pseudo random number generator used to generate file content for the virtual cage environment, as described above. In step 1124, it is determined whether a command to regenerate the trap has been received. If a request to regenerate the trap has not been received, the process ends. If a request to regenerate the trap has been received, the process returns to step 1122 in which the product serial number is used once again as the seed for the pseudo random number generator used to generate file content for the virtual cage environment.
[0104] FIG. 11C is a flow chart illustrating a process used in one embodiment to hide the connection between the administrative console and the trap host system by using a “connectionless” port, as discussed above in connection with step 1104 of FIG. 11A .
[0105] A typical way to connect such an administration console to a system such as the trap host system would be to use a connection that employs transmission control protocol (TCP), in which many packets of information are assembled together to appear as a uniform stream of information exchanged between the administration console and the trap host system. The shortcoming of this approach in the context of a system such as the trap system described herein is that an intruder would be able to see a connection that uses TCP as a continuously live connection to the trap host system. An intruder may become suspicious if the intruder can see that such a live connection exists.
[0106] In one embodiment, this shortcoming is avoided by employing a user datagram protocol (UDP) connection to connect the administration console to the trap host system. Unlike a TCP connection, a UDP connection does not result in many packets of data being assembled and transmitted as a uniform stream of information. Instead, each packet of information is sent with a hashed message authentication code (HMAC) used to identify the packet as having originated from an authorized source. Each packet is accepted at the receiving end if the required HMAC is present in the packet. In one embodiment, if the required HMAC is not present in a packet, the administration console replies with the Internet Control Message Protocol (ICMP) packet that would be sent if the port were not in use.
[0107] Unlike TCP, UDP does not require a communication channel to be established and maintained between the administration console and the trap host system in order for data to be exchanged between the two systems. When an authorized user logs into the administration console to view logging information, the user enters a password and the administration console generates a key that will be used to determine the HMAC that is required to be included in a valid transmission to the trap host system. Data packets sent by the trap host system to the administration console that contain the required HMAC will be accepted and acted on by the administration console system. If an intruder, on the other hand, sends a packet to the administration console via the UDP port in an attempt to determine if the trap host system is communicating with a device connected to the port (i.e., software is bound to the port), the administration console will see that the required HMAC is not present and will reply with the packet that would be sent if the port were not in use, as described above. As a result, the intruder will be led to believe that the port is not in use.
[0108] The process shown in FIG. 11C begins with step 1140, in which a user name and password are received at the administration console. In step 1142, a key for the session is provided. In one embodiment, the key is randomly generated. In one embodiment, the key is derived from the password. In step 1144, a message is received at the administration console via the connection to the trap host system. In step 1146, it is determined whether the incoming message contains the required HMAC.
[0109] If it is determined in step 1146 that the incoming message does not contain the required HMAC, the process proceeds to step 1148 in which the ICMP packet that would be provided if the port of the trap host system to which the administration console is connected were not in use is sent in response to the incoming message. If it is determined in step 1146 that the incoming message does contain the required HMAC, the process continues with step 1150, in which the incoming message is accepted by the administration console and the administration console takes appropriate responsive action, for example by responding to a command or query from the trap host system.
[0110] In step 1152, it is determined whether the session has ended, for example by determining whether the user has logged out of the administration console. If it is determined in step 1152 that the session has ended, the process ends. If it is determined in step 1152 that the session has not ended, the process returns to step 1144 in which the next incoming message, if any, is received.
[0111] In addition to providing computer security, the system and methods described herein may also be used for other purposes. For example, in one embodiment the techniques described above are used to provide a test environment to test the impact of a configuration change on a computer system without placing the actual files and data stored on the computer system at risk. FIG. 12 is a schematic diagram of a system used in one embodiment to provide such a test environment. The system 1200 includes a network server 1202 in which a virtual test environment 1204 is established in the same manner as the virtual cage environment described above. One or more network devices 1206 are connected to the network server 1202 by means of a network bus 1208. A remote system 1210 is configured to connect to network server 1202 by means of the Internet. An administration console 1212 is connected to the network server 1202 to be used to configure the network server and test environment, and to monitor activities in the test environment, similar to the administration console in the above-described security embodiment.
[0112] FIG. 13 is a flowchart illustrating a process used in one embodiment to provide a virtual test environment to test the effect of a configuration change prior to implementing the configuration change on the actual computer system. The process begins with step 1302 in which the software for providing the virtual environment is installed in the server or other computer system in which the configuration change is to be made. Next, in step 1304, a virtual test environment is established in the same manner as described above for establishing a cage environment in the trap host system in a security embodiment. Specifically, a test environment directory is established and the network server operating system and file system are copied into the virtual test environment.
[0113] Then, in step 1306, the contemplated change in configuration of the network server is implemented only in the test environment. For example, the configuration change may be the installation of a new software application. Alternatively, the configuration change may be the installation of a new network device on the network bus, or the connection of a new remote system via the Internet or some other means of remote access to the network server.
[0114] Next, in step 1308, the server is operated with the configuration change having been implemented in the test environment.
[0115] In step 1310, data concerning the operations of the server within the test environment is logged. In one embodiment, data concerning the processes running on the server, and in particular processes running within the virtual test environment, is provided by the operating system kernel and sent to the administration console for storage in the database.
[0116] In step 1312, logged data is analyzed to determine the effect of the configuration change on the virtual test environment. In one embodiment, a copy of the virtual test environment is made and then the virtual test environment is regenerated to restore the virtual test environment to the condition it was in before the configuration change was made. Then, the copy of the virtual test environment as modified by the configuration change is compared to the regenerated virtual test environment to analyze all of the effects of the configuration change.
[0117] The process continues with step 1314 in which it is determined whether the configuration change created any problems in the configuration or operation of the server within the virtual test environment. If the configuration change did create a problem, the process proceeds to step 1316 in which the configuration change is reversed and the server is restored to the condition it was in prior to the configuration change. If it is determined in step 1314 that the configuration change did not result in any problem in the virtual test environment, the process proceeds to step 1318, in which the configuration change is implemented in the server outside of the virtual test environment and the server is operated normally with the configuration change implemented.
[0118] Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. It should be noted that there are many alternative ways of implementing both the process and apparatus of the present invention. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
What is claimed is:
1. A method for generating fictitious computer file system content for a computer system configured to provide a deception environment in which an intruder is allowed to access at least part of the generated fictitious computer file system content, comprising:
creating a plurality of templates;
providing a collection of data items available to be inserted into the templates, the data items including one or more fictitious user names;
selecting one or more of the templates; and
for each template selected:
automatically, using a computer processor, selecting at least one data item from the collection; and
populating the template with the at least one data item from the collection so as to generate fictitious computer file system content.
2. The method of claim 1 wherein the collection of data items comprises one or more dates.
3. The method of claim 1 wherein at least one template is an e-mail message requiring at least one item of data to be complete.
4. The method of claim 1 wherein at least one template is a word processing document requiring at least one item of data to be complete.
5. The method of claim 1 wherein at least one template is a spreadsheet requiring at least one item of data to be complete.
6. The method of claim 1 wherein for at least one selected template the step of populating comprises receiving a number from a random number generator.
7. The method of claim 6 wherein the random number generator is a pseudo random number generator.
8. The method of claim 7 wherein the pseudo random number generator employs a unique key to generate numbers.
9. The method of claim 1 wherein for at least one selected template the step of populating comprises correlating a random number to an item of data in the collection.
10. The method of claim 1 wherein for at least one selected template the step of populating comprises inserting an item of data into the template.
11. The method of claim 1 further comprising intentionally including at least one spelling error in at least one template.
12. The method of claim 11 wherein a random number is used to determine what the at least spelling error will be.
13. The method of claim 1 further comprising intentionally introducing at least one grammatical error into at least one populated template.
14. The method of claim 1 wherein for at least one selected template, selecting the at least one data item is based at least in part on the relative probability of occurrence of the at least one data item.
15. The method of claim 1 wherein for at least one selected template, selecting the at least one data item is a function of (1) a random number and (2) the relative probability of occurrence of the at least one data item.
16. The method of claim 15 wherein a pseudo random number generator provides the random number.
17. The method of claim 1, further comprising associating a probability of occurrence with each template and wherein selecting one or more of the templates is based at least in part on the associated probability of occurrence.
18. The method of claim 1 wherein at least one template requires that at least two items of data be compatible with one another.
19. The method of claim 1, wherein the collection includes at least one data item that is not fictitious.
20. The method of claim 1, wherein the fictitious computer file system content comprises fictitious computer file system content of a deception environment on a server.
21. The method of claim 1, wherein the fictitious computer file system content comprises fictitious computer file system content of a deception environment on a PC.
22. The method of claim 1, wherein the fictitious computer file system content comprises fictitious computer file system content of a deception environment as part of a trap system.
23. A system for generating fictitious computer file system content for a computer system configured to provide a deception environment in which an intruder is allowed to access at least part of the generated fictitious computer file system content, comprising:
a processor configured to:
create a plurality of templates;
provide a collection of data items available to be inserted into the templates, the data items including one or more fictitious user names;
select one or more of the templates; and
for each template selected:
automatically select at least one data item from the collection; and
populate the template with the at least one data item from the collection so as to generate fictitious computer file system content; and
a memory coupled with the processor, wherein the memory provides the processor with instructions.
24. A computer program product for generating fictitious file system content for a computer configured to provide a deception environment in which an intruder is allowed to access at least part of the generated fictitious computer file system content, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
creating a plurality of templates;
providing a collection of data items available to be inserted into the templates, the data items including one or more fictitious user names;
selecting one or more of the templates; and
for each template selected:
automatically selecting at least one data item from the collection; and
populating the template with the at least one data item from the collection so as to generate fictitious computer file system content.
25. The method of claim 1, wherein the fictitious computer file system content is generated periodically over time in order to provide a more realistic deception environment.
Patent Citations (167)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4719566(A) | 1988-01-01 | Kelley | Applicant |
| US4825406(A) | 1989-04-01 | Bean | Applicant |
| US4922408(A) | 1990-05-01 | Davis et al. | Applicant |
| US5020052(A) | 1991-05-01 | DePrycker et al. | Applicant |
| US5032979(A) | 1991-07-01 | Hecht et al. | Applicant |
| US5107489(A) | 1992-04-01 | Brown et al. | Applicant |
| US5278901(A) | 1994-01-01 | Shieh et al. | Applicant |
| US5301333(A) | 1994-04-01 | Lee | Applicant |
| US5345590(A) | 1994-09-01 | Ault et al. | Applicant |
| US5349655(A) | 1994-09-01 | Mann | Applicant |
| US5361359(A) | 1994-11-01 | Tajalli et al. | Applicant |
| US5390173(A) | 1995-02-01 | Spinney et al. | Applicant |
| US5440723(A) | 1995-08-01 | Arnold et al. | Examiner |
| US5471631(A) | 1995-11-01 | Beardsley et al. | Applicant |
| US5483649(A) | 1996-01-01 | Kuznetsov et al. | Applicant |
| US5485409(A) | 1996-01-01 | Gupta et al. | Applicant |
| US5511188(A) | 1996-04-01 | Pascucci et al. | Applicant |
| US5530757(A) | 1996-06-01 | Krawczyz | Applicant |
| US5533123(A) | 1996-07-01 | Force et al. | Applicant |
| US5535375(A) | 1996-07-01 | Eshel et al. | Applicant |
| US5555543(A) | 1996-09-01 | Grohoski et al. | Applicant |
| US5557742(A) | 1996-09-01 | Smaha et al. | Applicant |
| US5566339(A) | 1996-10-01 | Perholtz et al. | Applicant |
| US5572590(A) | 1996-11-01 | Chess | Applicant |
| US5574898(A) | 1996-11-01 | Leblang et al. | Applicant |
| US5574912(A) | 1996-11-01 | Hu et al. | Applicant |
| US5581541(A) | 1996-12-01 | Whetsel | Applicant |
| US5606669(A) | 1997-02-01 | Bertin et al. | Applicant |
| US5613113(A) | 1997-03-01 | Goldring | Applicant |
| US5619645(A) | 1997-04-01 | Montenegro et al. | Applicant |
| US5621889(A) | 1997-04-01 | Lermuzeaux et al. | Applicant |
| US5623601(A) | 1997-04-01 | Vu | Applicant |
| US5633933(A) | 1997-05-01 | Aziz | Applicant |
| US5638509(A) | 1997-06-01 | Dunphy et al. | Applicant |
| US5642083(A) | 1997-06-01 | Kato et al. | Applicant |
| US5649185(A) | 1997-07-01 | Antognini et al. | Applicant |
| US5649194(A) | 1997-07-01 | Miller et al. | Applicant |
| US5655081(A) | 1997-08-01 | Bonnell et al. | Applicant |
| US5680585(A) | 1997-10-01 | Bruell | Applicant |
| US5694590(A) | 1997-12-01 | Thuraisingham et al. | Applicant |
| US5724569(A) | 1998-03-01 | Andres | Applicant |
| US5757913(A) | 1998-05-01 | Bellare et al. | Applicant |
| US5771291(A) | 1998-06-01 | Newton et al. | Applicant |
| US5778070(A) | 1998-07-01 | Mattison | Applicant |
| US5790808(A) | 1998-08-01 | Seaman | Applicant |
| US5796942(A) | 1998-08-01 | Esbensen | Applicant |
| US5809230(A) | 1998-09-01 | Pereira | Applicant |
| US5822434(A) | 1998-10-01 | Caronni et al. | Applicant |
| US5825750(A) | 1998-10-01 | Thompson | Applicant |
| US5826013(A) | 1998-10-01 | Nachenberg | Applicant |
| US5842002(A) | 1998-11-01 | Schnurer et al. | Applicant |
| US5844986(A) | 1998-12-01 | Davis | Applicant |
| US5850515(A) | 1998-12-01 | Lo et al. | Applicant |
| US5862477(A) | 1999-01-01 | Wellard et al. | Applicant |
| US5870550(A) | 1999-02-01 | Wesinger et al. | Applicant |
| US5892903(A) | 1999-04-01 | Klaus | Applicant |
| US5892924(A) | 1999-04-01 | Lyon et al. | Applicant |
| US5903830(A) | 1999-05-01 | Joao et al. | Applicant |
| US5910987(A) | 1999-06-01 | Ginter et al. | Applicant |
| US5913024(A) | 1999-06-01 | Green et al. | Applicant |
| US5919258(A) | 1999-07-01 | Kayashima et al. | Applicant |
| US5920705(A) | 1999-07-01 | Lyon et al. | Applicant |
| US5925126(A) | 1999-07-01 | Hsieh | Applicant |
| US5928363(A) | 1999-07-01 | Ruvolo | Applicant |
| US5937413(A) | 1999-08-01 | Hyun et al. | Applicant |
| US5958050(A) | 1999-09-01 | Griffin et al. | Applicant |
| US5960170(A) | 1999-09-01 | Chen et al. | Applicant |
| US5961644(A) | 1999-10-01 | Kurtzberg et al. | Applicant |
| US5974549(A) | 1999-10-01 | Golan | Applicant |
| US5978791(A) | 1999-11-01 | Farber et al. | Applicant |
| US5991881(A) | 1999-11-01 | Conklin et al. | Applicant |
| US6009474(A) | 1999-12-01 | Lu et al. | Applicant |
| US6009524(A) | 1999-12-01 | Olarig et al. | Applicant |
| US6014645(A) | 2000-01-01 | Cunningham | Applicant |
| US6021491(A) | 2000-02-01 | Renaud | Applicant |
| US6038667(A) | 2000-03-01 | Helbig | Applicant |
| US6041123(A) | 2000-03-01 | Colvin | Applicant |
| US6049546(A) | 2000-04-01 | Ramakrishnan | Applicant |
| US6055236(A) | 2000-04-01 | Nessett et al. | Applicant |
| US6058431(A) | 2000-05-01 | Srisuresh et al. | Applicant |
| US6067620(A) | 2000-05-01 | Holden et al. | Applicant |
| US6070246(A) | 2000-05-01 | Beser | Applicant |
| US6079020(A) | 2000-06-01 | Liu | Applicant |
| US6097817(A) | 2000-08-01 | Bilgic et al. | Applicant |
| US6122256(A) | 2000-09-01 | Berglund | Applicant |
| US6134664(A) | 2000-10-01 | Walker | Applicant |
| US6141686(A) | 2000-10-01 | Jackowski et al. | Applicant |
| US6151495(A) | 2000-11-01 | Rune | Applicant |
| US6170063(B1) | 2001-01-01 | Golding | Applicant |
| USH1944(H) | 2001-02-01 | Cheswick et al. | Applicant |
| US6226745(B1) | 2001-05-01 | Wiederhold | Applicant |
| US6233686(B1) | 2001-05-01 | Zenchelsky et al. | Applicant |
| US6247032(B1) | 2001-06-01 | Bernardo et al. | Applicant |
| US6247055(B1) | 2001-06-01 | Cotner et al. | Applicant |
| US6253323(B1) | 2001-06-01 | Cox et al. | Applicant |
| US6256393(B1) | 2001-07-01 | Safadi et al. | Applicant |
| US6256664(B1) | 2001-07-01 | Donoho et al. | Applicant |
| US6260016(B1) | 2001-07-01 | Holm et al. | Applicant |
| US6269447(B1) | 2001-07-01 | Maloney et al. | Applicant |
| US6278966(B1) | 2001-08-01 | Howard et al. | Applicant |
| US6289462(B1) | 2001-09-01 | McNabb et al. | Applicant |
| US6311274(B1) | 2001-10-01 | Day | Applicant |
| US6321338(B1) | 2001-11-01 | Porras et al. | Applicant |
| US6347374(B1) | 2002-02-01 | Drake et al. | Applicant |
| US6351752(B1) | 2002-02-01 | Cousins et al. | Applicant |
| US6351811(B1) | 2002-02-01 | Groshon et al. | Applicant |
| US6367029(B1) | 2002-04-01 | Mayhead et al. | Applicant |
| US6381632(B1) | 2002-04-01 | Lowell | Applicant |
| US6389458(B2) | 2002-05-01 | Shuster | Applicant |
| US6405318(B1) | 2002-06-01 | Rowland | Applicant |
| US6408391(B1) | 2002-06-01 | Huff et al. | Applicant |
| US6442694(B1) | 2002-08-01 | Bergman et al. | Applicant |
| US6453345(B2) | 2002-09-01 | Trcka et al. | Applicant |
| US6453419(B1) | 2002-09-01 | Flint et al. | Applicant |
| US6470027(B1) | 2002-10-01 | Birrell, Jr. | Applicant |
| US6470384(B1) | 2002-10-01 | O'Brien et al. | Applicant |
| US6484203(B1) | 2002-11-01 | Porras et al. | Applicant |
| US6499107(B1) | 2002-12-01 | Gleichauf et al. | Applicant |
| US6505311(B1) | 2003-01-01 | Ichinohe et al. | Applicant |
| US6519703(B1) | 2003-02-01 | Joyce | Applicant |
| US6560611(B1) | 2003-05-01 | Nine et al. | Applicant |
| US6567808(B1) | 2003-05-01 | Eschelbeck et al. | Applicant |
| US6574194(B1) | 2003-06-01 | Sun et al. | Applicant |
| US6577920(B1) | 2003-06-01 | Hypponen et al. | Applicant |
| US6628653(B1) | 2003-09-01 | Salim | Applicant |
| US6647400(B1) | 2003-11-01 | Moran | Applicant |
| US6665733(B1) | 2003-12-01 | Witkowski et al. | Applicant |
| US6681331(B1) | 2004-01-01 | Munson et al. | Applicant |
| US6687833(B1) | 2004-02-01 | Osborne et al. | Applicant |
| US6694045(B2) | 2004-02-01 | Chung et al. | Applicant |
| US6704874(B1) | 2004-03-01 | Porras et al. | Applicant |
| US6708212(B2) | 2004-03-01 | Porras et al. | Applicant |
| US6711615(B2) | 2004-03-01 | Porras et al. | Applicant |
| US6742121(B1) | 2004-05-01 | Safadi | Applicant |
| US6757717(B1) | 2004-06-01 | Goldstein | Applicant |
| US6804778(B1) | 2004-10-01 | Levi et al. | Applicant |
| US6826697(B1) | 2004-11-01 | Moran | Applicant |
| US6839850(B1) | 2005-01-01 | Campbell et al. | Applicant |
| US6886102(B1) | 2005-04-01 | Lyle | Applicant |
| US6907533(B2) | 2005-06-01 | Sorkin et al. | Applicant |
| US6921336(B1) | 2005-07-01 | Best | Applicant |
| US6971028(B1) | 2005-11-01 | Lyle et al. | Applicant |
| US6981155(B1) | 2005-12-01 | Lyle et al. | Applicant |
| US6996843(B1) | 2006-02-01 | Moran | Applicant |
| US7032114(B1) | 2006-04-01 | Moran | Applicant |
| US7065657(B1) | 2006-06-01 | Moran | Applicant |
| US7085936(B1) | 2006-08-01 | Moran | Applicant |
| US7117532(B1) | 2006-10-01 | Lyle et al. | Applicant |
| US7152239(B1) | 2006-12-01 | Lyle et al. | Applicant |
| US7203962(B1) | 2007-04-01 | Moran | Applicant |
| US7356844(B2) | 2008-04-01 | Lyle et al. | Applicant |
| US7409376(B2) | 2008-08-01 | Jameson | Examiner |
| US7424735(B2) | 2008-09-01 | Sorkin et al. | Applicant |
| US7461402(B1) | 2008-12-01 | Lyle et al. | Examiner |
| US2002/0002621(A1) | 2002-01-01 | Zhang et al. | Applicant |
| US2002/0066034(A1) | 2002-05-01 | Schlossberg | Applicant |
| US2002/0083343(A1) | 2002-06-01 | Crosbie et al. | Applicant |
| US2002/0087883(A1) | 2002-07-01 | Wohlgemuth et al. | Applicant |
| US2002/0144156(A1) | 2002-10-01 | Copeland | Applicant |
| US2002/0157021(A1) | 2002-10-01 | Sorkin et al. | Applicant |
| US2003/0204632(A1) | 2003-10-01 | Willebeek-LeMair et al. | Applicant |
| JP8032611 | 1996-02-01 | Applicant | |
| JP2000174794 | 2000-06-01 | Applicant | |
| WO1/04757 | 2001-01-01 | Applicant | |
| WO1/04759 | 2001-01-01 | Applicant | |
| WO1/05168 | 2001-01-01 | Applicant | |
| WO1/06373 | 2001-01-01 | Applicant |
Non-Patent Literature (70)
- Neumann, “The Risks Digest”, Forum on Risks to the Public in Computers and Related Systems, ACM, vol. 15, Issue 45, Feb. 8, 1994, 11 pages.Applicant
- Adam, J., Data Security-Threats and Countermeasures, IEEE Spectrum, vol. 29, Issue 8, pp. 21-28, Aug. 1992.Applicant
- Al-Shar, E., et al., Hi-Fi+: A Monitoring Virtual Machine for Autonomic Distributed Management', School of CS, DePaul University, Retrieved from the Internet at: http://www.mnlab.cs.depaul.edu/˜ehab/papers/dsom04.pdf, (2004).Applicant
- Atkinson, R., “IP Authentication Header” Request for Comment: 1826, Naval Research Laboratory, Aug. 1995.Applicant
- Bace, R., Introduction to Intrusion Detection Assessment, no date, for System and Network Security Management.Applicant
- Baldwin, Rule-Based Analysis of Computer Security, Massachusetts Institute of Technology, Jun. 1987.Applicant
- Cheswick, An Evening with Berferd in Which a Cracker is Lured, Endured, and Studied, AT&T Bell Labs (1990).Applicant
- Cheswick, An Evening with Berferd (1995).Applicant
- Cheswick, W, et al., Firewalls and Internet Security-Repelling the Wily Hacker, Addison-Wesley Publishing Co., Chapter 10, pp. 167-179, 1994.Applicant
- Cohen, A Note on the Role of Deception in Information Protection, Management Analytics; Fred Cohen and Associates; pp. 1-22, Retrieved from the Internet at: http://all.net/journal/deception/deception.html, (1998).Applicant
- Cohen, Deception Toolkit, Retrieved from the Internet at: http://www.all.net/dtk/dtk.html, 1999.Applicant
- Cohen, “A Mathematical Structure of Defensive Network Deceptions”, http://www.all.net/journal/deception/mathdeception.html, (1999).Applicant
- Cohen, Fred, “Internet Holes-Internet Lightning Rods”, Management Analytics 1996.Applicant
- Cohen, Operating System Protection Through Program Evolution (1998).Applicant
- Durst and Champion, Brian Witten, Eric Miller, and Luigi Spagnuolo, Testing and Evaluating Computer Intrusion Detect/on Systems. Jul. 1999 Communications of the ACM, at http:I/www.acm.orglpubs/contents/journals/cacmJ1999-42-7/p53-durstjps3durst.pdf.Applicant
- Even, What is a Honeypot Honey Pot Systems Explained, http://sans.orglnewloolc/resources/IDFAQ/honeypOt3.htm, (2000).Applicant
- Farmer and Spafford; The COPS Security Checker System, Proceedings of the Summer 1990 USENIX Conference, Anaheim, CA: pp. 165-170. Jun. 1990; Coast TR 94-01; Jun. 1990 http://www.cerias.purdue.eduJhomes/spaftech-reps993.ps.Applicant
- Frisch, “Essential System Administration”, pp. 250 and 262-265, 1995.Applicant
- Georgeff and Ingrand, “Decision-Making in an Embedded Reasoning System”, in Proceedings of IJCAI89, Detroit, MI, 1989.Applicant
- Georgeff and Ingrand, “Real-Time Reasoning: The Monitoring and Control of Spacecraft Systems”, in Proceedings of the Sixth IEEE Conference on Artificial Intelligence Applications, 1990.Applicant
- Georgeff and Lansky, “A Procedural Logic”, in Proceedings of IICAI85, Los Angeles, CA, 1985.Applicant
- Georgeff and Lansky, “Procedural Knowledge”, in Proceedings of the IEEE Special Issue on Knowledge Representation, vol. 74, pp. 1383-1398, 1986.Applicant
- Georgeff and Lansky, “Reactive Reasoning and Planning” An Experiment with a Mobile Robot, in Proceedings of AAAI87, 1987.Applicant
- Gross, “Analyzing Computer Intrusions”, Ph.D. thesis, Electrical and Computer Engineering (Communication Theory and Systems), San Diego Supercomputer Center, University of California, San Diego, 1997.Applicant
- Halme and Lunt et al., “Automated Analysis of Computer System Audit Trials for Security Purposes”, Proceedings of the National Computer Security Conference, Washington, D.C., 1986.Applicant
- Kim and Spafford, “Writing, Supporting and Evaluating Tripware: A Publically Available Security Tool”, Mar. 12, 1994, Purdue Technical Report; Purdue University.Applicant
- Knuth, The Art of Computer Programming, vol. 1, 2nd Edition, pp. 234-238, 1973.Applicant
- Latham, Department of Defense Trusted Computer System Evaluation Criteria, Dec. 1985, Department of Defense Standard.Applicant
- Lee, et al. “Mining in a Data-Flow Environment: Experience in Network Intrusion Detection”, Aug. 18,1997.Applicant
- Leffler, and McKusick, et al., The Design and Implementation of the 4.3 BSD UNIX Operating System, Addison-Wesley, 1989 Chapter 7 “The Filesystem”.Applicant
- Lippmann, et al., Evaluating Intrusion Detection Systems: The 1998 DARPA Off-Line Intrusion Detection Evaluation, Lincoln Laboratory MIT.Applicant
- Lunt et al., A Real-Time Intrusion-Detection Expert System (IDES), Feb. 28, 1992, SRI International Project 6784.Applicant
- Lunt and Tamaru, et al., “IDES: A Progress Report” Proceedings of the Sixth Annual Computer Security Applications Conference, Tucson, AZ, Dec. 1990.Applicant
- Lunt, “Automated Audit Trail Analysis and Intrusion Detection: A Survey”, Proceedings of the Eleventh National Computer Security Conference, Washington, D.C., Oct. 1988.Applicant
- Mattsson, U, “A Real Time Intrusion Prevention System for Enterprise Databases”, Protegrity, Retrieved on from the Internet at: http://www.quest-pipelines.com/newsletter-v5/1104—B.htm, Nov. 2004.Applicant
- Menezes, et al., Handbook Applied Cryprography, CRC Press LLC, pp. 397-405, 1997.Applicant
- Messmer, Ellen Decoy Server Helps Track Down Hackers, NW Fusion Focus, Newsgroups:a1t2600, news:3Th88c t2.94791 12Q)netnews.worldnet.att.net, Aug. 1999.Applicant
- Moran et al. DERBI: Diagnosis, Explanation and Recovery From Break-Ins, no date, Artificial Intelligence Center SRI International, (2000).Applicant
- Mukherjee, et al., Network Intrusion Detection, IEEE Network, pp. 26-41, May 1994.Applicant
- Myers, “A Procedural Knowledge Approach to Task-level Control”, Proceedings of the Third International Conference on AI Planning Systems, AAAI Press, 1996.Applicant
- Neville, Alan, “IDS Logs in Forensics Investigations: An Analysis of a Compromised Honeypot”. SecurityFocus, 2004. http://www.securityfocus.com/printable'infocus/1676.Applicant
- Norvill, T., “Auditing and Event Correction”, Department of IT & EE, University of Queensland, 2001.Applicant
- Pennington, A.G., et al., “Storage-based Intrusion Detection: Watching Storage Activity for Suspicious Behavior”, Carnegie Mellon University, USENIX Security Symposium, Aug. 2003.Applicant
- Porras and Neumann, et al., Emerald: Event Monitoring Enabling Responses to Anomalous Live Disturbances, 1997 National Information Systems Security Conference.Applicant
- Roebuck, T., Time Stamps and Timing in Audit-Based Digital Forensic Systems Examination, Retrieved on the Internet at: http://admin.usask.ca/roebuck/time.HTML, (1999).Applicant
- Safford and Schales, et al., “The TAMU Security Package: An ongoing Response to Internet Intruders in an Academic Environment”, Proceedings of the Fourth USENIX Security Symposium, Oct. 1993, Santa Clara, CA.Applicant
- Spitnzer, To Build a Honeypot, Whitepapers/Publications; pp. 1-5, Retrieved from the Internet at: http://www.spitzner.net/honeypot.html Aug. 4, 1999.Applicant
- Spitzner, Lance, “To Build a Honeypot”, http://web.archive.otB/web/19991013141306/http://enteract.com/˜1spitzhoneypot.btml, Jun. 28, 2002.Applicant
- Staggs, IDS: RE: CyberCop Sting, University of Wollongong, Australia, Oct. 1999.Applicant
- Tanenbaum, “Operating Systems Design and Implementation”, pp. 58-59, 1987.Applicant
- Tyson, Ph.D., Explaining and Recovering From Computer Break-Ins, Jan. 12, 2001, SRI International.Applicant
- Undercoffer, J., et al., “Modeling Computer Attacks: A Target-Centric Otology for Intrusion Detection”, Department of CS & EE, University of Maryland Baltimore County, 2002, Retrieved from the Internet at: http://www.csee.umbc.edu/cadip/2002Symposium/Ontfor-IDS.pdf.Applicant
- Unknown, “Decoy Nets Gain Backers in Battle Against Hackers”, Network World, Mar. 6, 2001.Applicant
- Unknown, “Network Associates Ships Cybercop Sting-.—Industiy's First ‘Decoy’ Server Silently Traces and Tracks Hacker Activity”, http://www.inforwar.com/Pands/99/pns071699di.shtml, Jun. 28, 2002.Applicant
- Unknown, Aleph One, Smashing the Stack for Fun and Profit, no date, vol. 7, Issue 49; File 14 of 16 of BugTraq, r00t, and Underground. Org, Nov. 8, 1996.Applicant
- Unknown, Cyber Cop Sting-Industry's First ‘Decoy’ Server Silently Traces and Tracks Hacker Activity, via Google, 1999.Applicant
- Unknown, Honeynet.Org Know Your Enemy: Honeynets, Honeynet Project web site, Apr. 21, 2001, http://web.archive.org/web/20010428053525/ http://project.honeynet.org.Applicant
- Unknown, Honeynet.org, “Know Your Enemy: Defining Virtual Honeynets”, Honeynet.org, Honeynet project, Jan. 27, 2003. http://www.honeynet.org/papers/virtual/index.html.Applicant
- Unknown, Honeynet.org, “Know Your Enemy: GenII Honeynets”, Honeynet. org, Honeynet project, Nov. 3, 2003, http://www.honeynet.org/papers/gen2/index.html.Applicant
- Unknown, IBM Technical Disclosure Bulletin Address Assignment for Nodes, vol. 36, No. 7, pp. 301-302, Jul. 1993.Applicant
- Unknown, IBM Technical Disclosure Bulletin Dynamic Control of Static Connections Through a Serial Switch vol. 34, No. 9, pp. 484-486, Feb. 1992.Applicant
- Unknown, IBM Technical Disclosure Bulletin Technique for Computer Network Security without Encryption, vol. 30, No. 4, pp. 1587-1589, Sep. 1987.Applicant
- Unknown, IDS: RE: Cyber Cop Sting, Michael Staggs, University of Wollongong, Australia, Oct. 8, 1999.Applicant
- Unknown, Internet Security Systems; Comparison between Internet Security Scanner (ISS) J.x and Internet Scanner 3.2, 1996. http://www.iss.net, (1996).Applicant
- Unknown, Internet Security Systems; Technical Specifications for Internet Scanner Version 3.0. [This document is undated—it is believed to be 1996 or earlier based on Item F which is version 3.2 of this document].Applicant
- Unknown, James P. Anderson Co., Computer Security Threat Monitoring and Surveillance, Feb. 26, 1980, Contract 79F296400.Applicant
- Unknown, Network Associates, “Network Associates Ships Cybercop Sting” Network Associates Inc., (“NAI”) http://www.serverwatch.com/news/print.php/1399041, (1999).Applicant
- Unknown, Pages regarding DERBI Project from SRI International Website at http://www.ai.sri.com/˜derbi/ (2000).Applicant
- Zerkle and Levitt, A Multi-Host Configuration Vulnerability Checker, Proceedings of the Sixth USENIX Security Symposium, San Jose, CA, Jul. 1996.Applicant
- Supplementary European Search Report in European Application No. 02 72 1805 dated Mar. 25, 2009.Applicant