Abstract: Apparatus and methods are provided for executing a rules-based authentication of an electronic transaction. The method may include receiving first and second payment authorization parameters and second payment authorization parameters. The method may also include receiving from a Point of Sale device a request for payment information and a purchase amount. The method may also include, determining if first or second parameters are satisfied. The first parameters may include a first time range, a pairing of the electronic device to a first apparatus, a first geolocation of the electronic device, and a first maximum transaction value. The second parameters may include a second time range, a pairing of the electronic device to a second apparatus, a second geolocation of the electronic device, and a second maximum transaction value, wherein the second time range does not include the first time range.

Abstract: Apparatus, systems, architectures and methods for communication over an enterprise internet-of-things (EIoT) network are disclosed. Network(s) may be micro- segmented. Network segment(s) may be associated with distinct function(s). EIoT device(s) may be identified by type(s), class(es), functionality(ies), function(s) and/or security level(s). EIoT device protocol(s) may be translated/emulated. EIoT device(s) may be temporarily/ permanently quarantined. Network gateway(s) may factor EIoT device/network data based on function(s) and/or specification(s). Data may be routed to network segment(s) based on associated function(s).

Abstract: Aspects of the disclosure relate to monitoring source code repository data in real-time to protect sensitive information and provide entity-specific alerts. A computing platform may receive configuration information defining one or more criteria for identifying sensitive data of an enterprise organization. The computing platform may monitor external code repository server infrastructure based on the configuration information. In response to detecting that first source code received by the external code repository server infrastructure contains first sensitive information associated with the enterprise organization, the computing platform may generate a notification comprising information indicating that the first sensitive information associated with the enterprise organization has been detected at the external code repository server infrastructure. Subsequently, the computing platform may send the notification to an enterprise administrator user computing device associated with the enterprise organization.

Abstract: Apparatus and methods are provided for executing a rules-based authentication of an electronic transaction. The method may include receiving first and second payment authorization parameters and second payment authorization parameters. The method may also include receiving from a Point of Sale device a request for payment information and a purchase amount. The method may also include, determining if first or second parameters are satisfied. The first parameters may include a first time range, a pairing of the electronic device to a first apparatus, a first geolocation of the electronic device, and a first maximum transaction value. The second parameters may include a second time range, a pairing of the electronic device to a second apparatus, a second geolocation of the electronic device, and a second maximum transaction value, wherein the second time range does not include the first time range.

Abstract: A system for exchanging authentication data between edge-nodes is provided. The system may include an edge-node network. The network may include a plurality of edge-nodes. Each edge-node may include a pairing module. Each pairing module may receive an instruction to pair with another edge-node. Each pairing module pair with another edge-node. The pairing module may continually transmit verification communications to other edge-nodes. The pairing module may continually discover responsive communications from other edge-nodes. The pairing module may continually receive responsive verification communications from other edge-nodes. Each edge-node may include an executable module. The executable module may determine occurrence of an event. Upon determination of the occurrence of an event, the executable module may analyze a stored event protocol. The protocol including an algorithm for implementing executables in response to an event.

Abstract: Apparatus and methods are provided for executing a rules-based authentication of an electronic transaction. The method may include receiving first and second payment authorization parameters and second payment authorization parameters. The method may also include receiving from a Point of Sale device a request for payment information and a purchase amount. The method may also include, determining if first or second parameters are satisfied. The first parameters may include a first time range, a pairing of the electronic device to a first apparatus, a first geolocation of the electronic device, and a first maximum transaction value. The second parameters may include a second time range, a pairing of the electronic device to a second apparatus, a second geolocation of the electronic device, and a second maximum transaction value, wherein the second time range does not include the first time range.

Abstract: Apparatus and methods are provided for executing a rules-based authentication of an electronic transaction. The method may include receiving first and second payment authorization parameters and second payment authorization parameters. The method may also include receiving from a Point of Sale device a request for payment information and a purchase amount. The method may also include, determining if first or second parameters are satisfied. The first parameters may include a first time range, a pairing of the electronic device to a first apparatus, a first geolocation of the electronic device, and a first maximum transaction value. The second parameters may include a second time range, a pairing of the electronic device to a second apparatus, a second geolocation of the electronic device, and a second maximum transaction value, wherein the second time range does not include the first time range.

Abstract: A system for exchanging authentication data between edge-nodes is provided. The system may include an edge-node network. The network may include a plurality of edge-nodes. Each edge-node may include a pairing module. Each pairing module may receive an instruction to pair with another edge-node. Each pairing module pair with another edge-node. The pairing module may continually transmit verification communications to other edge-nodes. The pairing module may continually discover responsive communications from other edge-nodes. The pairing module may continually receive responsive verification communications from other edge-nodes. Each edge-node may include an executable module. The executable module may determine occurrence of an event. Upon determination of the occurrence of an event, the executable module may analyze a stored event protocol. The protocol including an algorithm for implementing executables in response to an event.

Abstract: Apparatus and methods for a federated edge-node computing system are provided. The federated system may allow customers to work in offline mode (e.g., during a disaster). Local data stored on edge-nodes may be used to process offline transactions. Offline transactions may include money transfers and merchant payments using mobile wallets. A plurality of nodes may form a consortium. The consortium may be formed based on geographic proximity of nodes. Member of the consortium may locally store geographically relevant data for authorizing offline transactions.

Abstract: Aspects of the disclosure relate to monitoring source code repository data in real-time to protect sensitive information and provide entity-specific alerts. A computing platform may receive configuration information defining one or more criteria for identifying sensitive data of an enterprise organization. The computing platform may monitor external code repository server infrastructure based on the configuration information. In response to detecting that first source code received by the external code repository server infrastructure contains first sensitive information associated with the enterprise organization, the computing platform may generate a notification comprising information indicating that the first sensitive information associated with the enterprise organization has been detected at the external code repository server infrastructure. Subsequently, the computing platform may send the notification to an enterprise administrator user computing device associated with the enterprise organization.

Abstract: Apparatus and methods for a reverse proxy server are provided. The reverse proxy server may provide compatibility and security for nodes on an IoT network. A reverse proxy server may normalize inter-node communications. A reverse proxy server may identify an IoT node and upon identification of the node, determine native communication protocol(s) specific to the node. The reverse proxy server may encapsulate data transmitted via the native communication protocol. The reverse proxy server may impose a principal-agent relationship. For example, the reverse proxy server may be a principal of one or more nodes (agents) on the IoT. The reverse proxy server may enforce security protocols on all agents. An agent (e.g., node) may be required to route all communications to other IoT devices through the principal (e.g., reverse proxy server). An IoT network may include more than one reverse proxy server. Each agent may have one or more principals.

Abstract: Apparatus, systems, architectures and methods for communication over an enterprise internet-of-things (EIoT) network are disclosed. Network(s) may be micro-segmented. Network segment(s) may be associated with distinct function(s). EIoT device(s) may be identified by type(s), class(es), functionality(ies), function(s) and/or security level(s). EIoT device protocol(s) may be translated/emulated. EIoT device(s) may be temporarily/permanently quarantined. Network gateway(s) may factor EIoT device/network data based on function(s) and/or specification(s). Data may be routed to network segment(s) based on associated function(s).

Abstract: Apparatus, systems, architectures and methods for communication over an enterprise internet-of-things (EIoT) network are disclosed. Network(s) may be micro-segmented. Network segment(s) may be associated with distinct function(s). EIoT device(s) may be identified by type(s), class(es), functionality(ies), function(s) and/or security level(s). EIoT device protocol(s) may be translated/emulated. EIoT device(s) may be temporarily/permanently quarantined. Network gateway(s) may factor EIoT device/network data based on function(s) and/or specification(s). Data may be routed to network segment(s) based on associated function(s).

Abstract: Apparatus, systems, architectures and methods for communication over an enterprise internet-of-things (EIoT) network are disclosed. Network(s) may be micro-segmented. Network segment(s) may be associated with distinct function(s). EIoT device(s) may be identified by type(s), class(es), functionality(ies), function(s) and/or security level(s). EIoT device protocol(s) may be translated/emulated. EIoT device(s) may be temporarily/permanently quarantined. Network gateway(s) may factor EIoT device/network data based on function(s) and/or specification(s). Data may be routed to network segment(s) based on associated function(s).

Abstract: Apparatus and methods for a reverse proxy server are provided. The reverse proxy server may provide compatibility and security for nodes on an IoT network. A reverse proxy server may normalize inter-node communications. A reverse proxy server may identify an IoT node and upon identification of the node, determine native communication protocol(s) specific to the node. The reverse proxy server may encapsulate data transmitted via the native communication protocol. The reverse proxy server may impose a master-slave relationship. For example, the reverse proxy server may be a master of one or more nodes (slaves) on the IoT. The reverse proxy server may enforce security protocols on all slaves. A slave (e.g., node) may be required to route all communications to other IoT devices through the master (e.g., reverse proxy server). An IoT network may include more than one reverse proxy server. Each slave may have one or more masters.