Abstract: An access revocation system for removing user data from a service provider device includes a processing device and a memory storing instructions for performing an access revocation method. The method includes receiving user data from a user device via a data channel, storing the user data in a data storage module, and receiving an access revocation message via a request channel separate from the data channel. The method also includes decrypting the access revocation message and performing at least one action defined by the access revocation message, the at least one action including scrubbing of user data from the data storage module.

Abstract: Embodiments are directed to a method of transferring data between a customer site and a benchmarking site, including: receiving, from the customer site, encrypted packet data, wherein the packet data is encrypted using a first key of a key pair; storing the encrypted packet data, by the processor, in a first cache at the benchmarking site; decrypting the encrypted packet data in the first cache, by the processor, using a second key of the key pair; storing decrypted packet data, by the processor, in a second cache at the benchmarking site; indexing the decrypted packet data in the second cache; storing indexed packet data as a dataset in a permanent storage device; and performing a benchmarking session on the indexed packet data.

Abstract: A method, apparatus and computer program product for managing security threats to a distributed network. A set of events are aggregated from a plurality of event sources in the network for each of a set of security threats to the network. A magnitude of a characteristic of each of the set of security threats is determined. Each of the set of security threats is represented as a three dimensional graphical object in a three dimensional (3D) representation of the network according to the respective magnitude of the characteristic. A security action is taken based on the determined magnitude of one of the set of security threats.

Abstract: Injection attack identification and mitigation includes tracking characteristics of user input by a user to a computer system via input device(s), building and maintaining a user profile based on the tracking and that provides a baseline of expected characteristics of user input, the baseline defined by the tracked characteristics, monitoring input to the computer system in real time as the input is provided to the computer system, identifying, based on the monitoring and on a comparison of characteristics of the monitored input to the baseline of expected characteristics, a potential malicious code injection as part of the monitored input to the computer system, and performing mitigation processing based on identifying the potential malicious code injection.

Abstract: A method, apparatus and computer program product for managing security threats to a distributed network. A set of events are aggregated from a plurality of event sources in the network for each of a set of security threats to the network. A magnitude of a characteristic of each of the set of security threats is determined. Each of the set of security threats is represented as a three dimensional graphical object in a three dimensional (3D) representation of the network according to the respective magnitude of the characteristic. A security action is taken based on the determined magnitude of one of the set of security threats.

Abstract: A technique for secure data storage and access during transition operations includes retrieving an encrypted instance of a data object from a data store. The retrieved encrypted instance of the data object is stored in a cryptcache. The encrypted instance in the cryptcache is decrypted to a cleartext instance of the data object and stored as the cleartext instance of the data object in a clearcache. The clearcache instance of the data object is secured by controlling an access window defining an amount of time the cleartext instance of the data object is accessible in the clearcache.

Abstract: An access revocation system for removing user data from a service provider device includes a processing device and a memory storing instructions for performing an access revocation method. The method includes receiving user data from a user device via a data channel, storing the user data in a data storage module, and receiving an access revocation message via a request channel separate from the data channel. The method also includes decrypting the access revocation message and performing at least one action defined by the access revocation message, the at least one action including scrubbing of user data from the data storage module.

Abstract: An access revocation system for removing customer data from a service provider device includes a processing device and a memory storing instructions for performing an access revocation method. The method includes receiving customer data from a customer device via a data channel, storing the customer data in a data storage module, and receiving an access revocation message via a request channel separate from the data channel. The method also includes decrypting the access revocation message and performing at least one action defined by the access revocation message, the at least one action including scrubbing of customer data from the data storage module.

Abstract: An access revocation system for removing customer data from a service provider device includes a processing device and a memory storing instructions for performing an access revocation method. The method includes receiving customer data from a customer device via a data channel, storing the customer data in a data storage module, and receiving an access revocation message via a request channel separate from the data channel. The method also includes decrypting the access revocation message and performing at least one action defined by the access revocation message, the at least one action including scrubbing of customer data from the data storage module.

Abstract: Embodiments are directed to a method of implementing a packet capture ring. The packet capture ring includes a plurality of appliances, and the plurality of appliances includes a first appliance and a second appliance. The first appliance and the second appliance are both attached to a network tap, and the first appliance works as a master appliance. The master appliance ingests packets from the network tap, encapsulates the packets and forwards encapsulated packets in the packet capture ring. The method includes: detecting, by the second appliance, a failure of the first appliance; working, by the second appliance, as the master appliance; and removing, by the second appliance, the first appliance from a forwarding designation list.

Abstract: Injection attack identification and mitigation includes tracking characteristics of user input by a user to a computer system via input device(s), building and maintaining a user profile based on the tracking and that provides a baseline of expected characteristics of user input, the baseline defined by the tracked characteristics, monitoring input to the computer system in real time as the input is provided to the computer system, identifying, based on the monitoring and on a comparison of characteristics of the monitored input to the baseline of expected characteristics, a potential malicious code injection as part of the monitored input to the computer system, and performing mitigation processing based on identifying the potential malicious code injection.

Abstract: Embodiments are directed to a method of transferring data between a customer site and a benchmarking site, including: receiving, from the customer site, encrypted packet data, wherein the packet data is encrypted using a first key of a key pair; storing the encrypted packet data, by the processor, in a first cache at the benchmarking site; decrypting the encrypted packet data in the first cache, by the processor, using a second key of the key pair; storing decrypted packet data, by the processor, in a second cache at the benchmarking site; indexing the decrypted packet data in the second cache; storing indexed packet data as a dataset in a permanent storage device; and performing a benchmarking session on the indexed packet data.

Abstract: Embodiments are directed to a method of implementing a packet capture ring. The packet capture ring includes a plurality of appliances, and the plurality of appliances includes a first appliance and a second appliance. The first appliance and the second appliance are both attached to a network tap, and the first appliance works as a master appliance. The master appliance ingests packets from the network tap, encapsulates the packets and forwards encapsulated packets in the packet capture ring. The method includes: detecting, by the second appliance, a failure of the first appliance; working, by the second appliance, as the master appliance; and removing, by the second appliance, the first appliance from a forwarding designation list.

Abstract: A technique for secure data storage and access during transition operations includes retrieving an encrypted instance of a data object from a data store. The retrieved encrypted instance of the data object is stored in a cryptcache. The encrypted instance in the cryptcache is decrypted to a cleartext instance of the data object and stored as the cleartext instance of the data object in a clearcache. The clearcache instance of the data object is secured by controlling an access window defining an amount of time the cleartext instance of the data object is accessible in the clearcache.

Abstract: A policy engine generates configlets that are vendor-neutral, vendor-specific or both, based on a selected target level and a selected device/device group. A translator translates and combines the configlets to form vendor-dependent configuration files. The policy engine generates the configlets using policies associated with the selected target level and its sub-target levels, as defined by a target level hierarchy. A policy includes at least a condition, and an action which the policy engine performs if the condition is true. In performing the action, the policy engine typically writes to at least a partial configlet. A policy may further include a verification clause, which is used to verify a running configuration. Policy dependencies may also be defined such that where a second policy is dependent on a first policy, the second policy must be evaluated after the first policy. This is necessary, where, for example, the first policy generates and stores a value to be used by the second policy.

Abstract: A policy engine generates configlets that are vendor-neutral, vendor-specific or both, based on a selected target level and a selected device/device group. A translator translates and combines the configlets to form vendor-dependent configuration files. The policy engine generates the configlets using policies associated with the selected target level and its sub-target levels, as defined by a target level hierarchy. A policy includes at least a condition, and an action which the policy engine performs if the condition is true. In performing the action, the policy engine typically writes to at least a partial configlet. A policy may further include a verification clause, which is used to verify a running configuration. Policy dependencies may also be defined such that where a second policy is dependent on a first policy, the second policy must be evaluated after the first policy. This is necessary, where, for example, the first policy generates and stores a value to be used by the second policy.

Abstract: A policy engine generates configlets that are vendor-neutral, vendor-specific or both, based on a selected target level and a selected device/device group. A translator translates and combines the configlets to form vendor-dependent configuration files. The policy engine generates the configlets using policies associated with the selected target level and its sub-target levels, as defined by a target level hierarchy. A policy includes at least a condition, and an action which the policy engine performs if the condition is true. In performing the action, the policy engine typically writes to at least a partial configlet. A policy may further include a verification clause, which is used to verify a running configuration. Policy dependencies may also be defined such that where a second policy is dependent on a first policy, the second policy must be evaluated after the first policy. This is necessary, where, for example, the first policy generates and stores a value to be used by the second policy.

Abstract: A computer-implemented method of designing a network includes the steps of populating a network design sheet on a computer display with an intelligent device object that represents a device object having physical attributes and logical attributes, selecting a communication protocol object representing a communication protocol having logical attributes, determining if the communication protocol object can be validly bound to the intelligent device object by comparing the logical attributes of each, and binding the communication protocol object to the intelligent device object on the network design sheet only if the binding is valid.