Abstract: In aspects of a multi-directional catheter guard, a first end is configured for fitment with an anatomically male patient, and a second end is configured for fitment with an anatomically female patient. The multi-directional catheter guard can include an expandable enclosure that expands and closes for fitment, encompassing a catheter tubing in a direction corresponding to patient anatomy. The multi-directional catheter guard may also include a friction material that resists lateral movement of the multi-directional catheter guard from an attached position on the catheter tubing.

Abstract: Provided herein are systems and methods for multi-event correlation. Receiving a stream of events, each leaf rule engine may detect a plurality of events from the stream that matches a characteristic for the leaf rule engine. Each leaf rule engine may identify, from the plurality of events and within a time window, a group of events that satisfies a condition for the respective leaf rule engine. A root conditions engine may receive a stream of leaf events corresponding to the group of events identified by each leaf rule engine. The root conditions engine may identify, from the received stream of leaf events and within a root time window, a collection of events that satisfies a condition for the root conditions engine. A trigger may execute an action according to the collection of events identified within the root time window.

Abstract: Provided herein are systems and methods for identifying personal identifiers in content. An entity engine may receive content to identify candidate personal identifiers. The entity engine may determine that a text string in the content matches to a data format specified in entity definitions corresponding to types of personal identifiers and a rule for finding a geographic or linguistic term in the content correlated to the specific type of personal identifier. Each entity definition may specify a data format for finding a specific type of personal identifier in content. The data format corresponds to a type of personal identifier. The entity engine may identify, according to a rule of the first entity definition, a geographic or linguistic term in the content correlated to the type of personal identifier. The entity engine may classify the text string as the type of personal identifier, for preventing data breach or exfiltration.

Abstract: Provided herein are systems and methods of investigating an entity or a potential incident. A tracker engine may receive an identification of a first entity in a networked environment. The tracker engine may display, in a user interface responsive to receiving the identification, a representation of the first entity, and representations of a plurality of entities associated with the first entity. The plurality of associated entities may include: a network connection, a file, a process, a user or a computing device. The tracker engine may receive, via the user interface, a selection of a second entity from the plurality of associated entities. The tracker engine may update, responsive to receiving the selection, the user interface to display a representation of the second entity graphically linked to the representation of the first entity, and representations of a plurality of entities associated with the second entity.

Abstract: Provided herein are systems and methods of tracing data. A tracing engine may receive, via the user interface, a selection of a target file or an event involving the target file. The tracing engine may generate, responsive to receiving the selection, a trace of first data in the target file to a plurality of file instances in a network each having at least one version of the first data. Each of the plurality of file instances may be related to at least the target file or another of the plurality of file instances via at least one file operation or data operation. The tracing engine may render, via a user interface, the generated trace.

Abstract: Provided herein are systems and methods for determining a likelihood that an executable comprises malware. A learning engine may determine a plurality of attributes of an executable identified in a computing environment, and a corresponding weight to assign to each of the plurality of attributes. Each of the plurality of attributes may be indicative of a level of risk for the computing environment. The learning engine may generate, according to the determined plurality of attributes and the corresponding weights, one or more scores indicative of a likelihood that the executable comprises malware. A rule engine may perform an action to manage operation of the executable, according to the generated one or more scores.

Abstract: Provided herein are systems and methods for classifying content to prevent data breach or exfiltration. An entity engine may receive content for classification into a content type for preventing data breach or exfiltration. The entity engine may determine that secondary data, defined by an operand of an entity definition, is present in the content. Each entity definition may correspond to one content type and may include a Boolean expression of operands. Each operand may include a matching element to be used for matching against content undergoing classification into one of the content types, upon secondary data defined by the operand being present in the content. The entity engine may classify the content into a content type of the content types, corresponding to the entity definition, based on matching the matching element of the operand to the content, and matching other operands of the entity definition to the content.

Abstract: Provided herein are systems and methods for identifying personal identifiers in content. An entity engine may receive content to identify candidate personal identifiers. The entity engine may determine that a text string in the content matches to a data format specified in entity definitions corresponding to types of personal identifiers and a rule for finding a geographic or linguistic term in the content correlated to the specific type of personal identifier. Each entity definition may specify a data format for finding a specific type of personal identifier in content. The data format corresponds to a type of personal identifier. The entity engine may identify, according to a rule of the first entity definition, a geographic or linguistic term in the content correlated to the type of personal identifier. The entity engine may classify the text string as the type of personal identifier, for preventing data breach or exfiltration.

Abstract: Provided herein are systems and methods for defining and securely sharing objects for use in preventing data breach or exfiltration. Memory may be configured to store a plurality of objects for use in preventing data breach or exfiltration. A validation engine can validate the objects, incorporate into each object an object identifier and a signature, and generate a subset of the objects for use by a first user. The validation engine can store, in the memory, the plurality of objects as a superset of objects corresponding to the generated subset. An evaluation engine may, responsive to identifying that one or more object identifiers and signatures in a received set of objects belong to the subset corresponding to the stored superset, verify whether any object in the received set has been tampered with.

Abstract: A firearm grip assembly includes a firearm adapter having functionality for engaging the receiver of a firearm. An elongated handgrip body having an opening along the top end slidingly receives the bottom end of the adapter. The latching mechanism is positioned within the adapter and includes a resilient member having a pair of buttons extending outward therefrom. The buttons are positioned through a first set of openings located on the adapter body and are selectively positioned within a second pair of openings on the handgrip body when the adapter is positioned within the handgrip body.

Abstract: Provided herein are systems and methods for risk tracking. A tracker engine executable on servers may provide, in a user interface, a plurality of categories of locations for files in a networked environment. The tracker engine may identify in the user interface risk categories of the files in each of the categories of the locations. The tracker engine may provide, in the user interface, types of egress points for the files. The tracker engine may generate links between the categories of the locations of the files, the risk categories of the files and the types of egress points for the files. Details about each of the files may be navigable from the user interface via a corresponding category of a location of the file, a corresponding risk category of the file or a corresponding type of egress point for the file.

Abstract: Provided herein are systems and methods for protecting data from injected malware. In some embodiments, a virtual memory validator may execute in user mode memory space on a computing device. The virtual memory validator may monitor an execution stack of an executing thread of a process. The virtual memory validator may identify a memory address referenced in the execution stack, responsive to the process attempting to access a protected resource. The virtual memory validator may determine that the memory address refers to a memory region that is designated as executable. The virtual memory validator may determine that the memory address is outside memory regions identified in a memory range map. The virtual memory validator may, responsive to the determination, identify the process as a potential malware process.

Abstract: Provided herein are systems and methods for multi-event correlation. Receiving a stream of events, each leaf rule engine may detect a plurality of events from the stream that matches a characteristic for the leaf rule engine. Each leaf rule engine may identify, from the plurality of events and within a time window, a group of events that satisfies a condition for the respective leaf rule engine. A root conditions engine may receive a stream of leaf events corresponding to the group of events identified by each leaf rule engine. The root conditions engine may identify, from the received stream of leaf events and within a root time window, a collection of events that satisfies a condition for the root conditions engine. A trigger may execute an action according to the collection of events identified within the root time window.

Abstract: Provided herein are systems and methods of investigating an entity or a potential incident. A tracker engine may receive an identification of a first entity in a networked environment. The tracker engine may display, in a user interface responsive to receiving the identification, a representation of the first entity, and representations of a plurality of entities associated with the first entity. The plurality of associated entities may include: a network connection, a file, a process, a user or a computing device. The tracker engine may receive, via the user interface, a selection of a second entity from the plurality of associated entities. The tracker engine may update, responsive to receiving the selection, the user interface to display a representation of the second entity graphically linked to the representation of the first entity, and representations of a plurality of entities associated with the second entity.

Abstract: Provided herein are systems and methods for multi-event correlation. Receiving a stream of events, each leaf rule engine may detect a plurality of events from the stream that matches a characteristic for the leaf rule engine. Each leaf rule engine may identify, from the plurality of events and within a time window, a group of events that satisfies a condition for the respective leaf rule engine. A root conditions engine may receive a stream of leaf events corresponding to the group of events identified by each leaf rule engine. The root conditions engine may identify, from the received stream of leaf events and within a root time window, a collection of events that satisfies a condition for the root conditions engine. A trigger may execute an action according to the collection of events identified within the root time window.

Abstract: A firearm grip with locking mechanism includes an elongated handgrip body having an elongated opening on the front side and a generally hollow interior space. A pair of doors are pivotally secured to the handgrip body to move between a closed position, and an open position. A firearm engagement body is pivotally secured along the top end of the handgrip body for attachment to a firearm receiver at a location adjacent to the trigger assembly. The handgrip body moves between a FIRE position where the handgrip body is positioned perpendicular to the engagement body, and a SAFE position where the handgrip body is positioned parallel to the engagement body and the firearm trigger assembly is located within the interior space of the handgrip body.

Abstract: A firearm grip with selector switch lock includes a handgrip for engaging a firearm receiver having a selector switch. A switch engagement unit is positioned within the handgrip. The switch engagement unit including a motor, piston, spring and detent for selectively engaging the selector switch of the receiver to which the handgrip is located. An RFID interrogator is positioned within the handgrip and communicates with a portable RFID chip. Upon detecting the presence of the RFID chip, the switch engagement unit moves the piston to the retracted position for manual free operation of the selector switch. Upon detecting the RFID chip is not within the proximity of the handgrip, the switch engagement unit moves the piston to the extended/SAFE position. A replacement selector switch having a torque limiter is provided.

Abstract: Provided herein are systems and methods for defining and securely sharing objects for use in preventing data breach or exfiltration. Memory may be configured to store a plurality of objects for use in preventing data breach or exfiltration. A validation engine can validate the objects, incorporate into each object an object identifier and a signature, and generate a subset of the objects for use by a first user. The validation engine can store, in the memory, the plurality of objects as a superset of objects corresponding to the generated subset. An evaluation engine may, responsive to identifying that one or more object identifiers and signatures in a received set of objects belong to the subset corresponding to the stored superset, verify whether any object in the received set has been tampered with.

Abstract: Systems and methods for enhanced DOM and event mirroring and security in web applications provides an intermediate Master Browser between web content and client devices to improve security and other enhancements.

Abstract: A biometric electro-mechanical locking system for a firearm includes a generally hollow main body having a pivot plate that is secured along the first end. A hand grip is positioned along the main body and configured to slide between a FIRE position where the trigger assembly of the firearm is accessible, and a SAFE position where the trigger assembly of the firearm is not accessible. A release button is positioned along the main body and is mechanically coupled to a dual locking assembly that is positioned within the main body. The dual locking assembly including an electromechanical locking unit having a processor, memory, fingerprint sensor and electric servo, and a mechanical locking unit having a mechanical combination lock.