IP Library › Granted Patent US 12,192,218
Granted Patent B2
US 12,192,218 · App. 18/360,713 · Granted Jan 7, 2025

Unwanted tunneling alert system

Inventors: Juan Ricafort (New York, NY); Harkirat Singh (New York, NY); Philip Martin (San Jose, CA)
Assignee: Palantir Technologies Inc.
H04L63/1416H04L61/5007H04L63/0272H04L63/029H04L63/1425H04L63/1441H04L63/145H04L63/20G06F21/556
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,192,218
App. No.
18/360,713
Granted
Jan 7, 2025
Kind
B2
Abstract

Various systems and methods are provided that detect malicious network tunneling. For example, VPN logs and data connection logs may be accessed. The VPN logs may list client IP addresses that have established a VPN connection with an enterprise network. The data connection logs may list client IP addresses that have requested connections external to the enterprise network and remote IP addresses to which connections are requested. The VPN logs and the data connection logs may be parsed to identify IP addresses that are present in the VPN logs as a client IP address and in the data connection logs as a remote IP address. If an IP address is so present, user data and traffic data associated with the IP address may be retrieved to generate a risk score. If the risk score exceeds a threshold, an alert to be displayed in a GUI is generated.

Claims (40)

1. A computing system comprising:

one or more computer processors; and

one or more non-transitory computer-readable storage mediums storing program instructions configured for execution by the one or more computer processors to cause the computing system to:

identify a first network address included in a first log and in a second log, wherein the first log identifies one or more second network addresses corresponding to one or more users granted access to a network, and wherein the second log identifies one or more third network addresses requested via the network;

determine based at least partly on the first network address, a score at least partly indicative of a likelihood that a malicious tunneling connection is present; and

initiate termination a first connection if the score satisfies a threshold value.

2. The computing system of claim 1 , wherein one or more non-transitory computer-readable storage medium further store program instructions that cause the computing system to:

generate user interface data that, when executed, causes a user device to display a user interface that depicts a notification derived from the score, wherein a user interface-based interaction with the notification causes the computing system to adjust determination of a future score.

3. The computing system of claim 2 , wherein the notification comprises at least one of a number of users that are connected to a known virtual private network (VPN) client during a time period associated with the notification, an indication of whether characteristics of traffic between the network and a second user device matches a tunneled connection profile, an indication of an amount of outbound data transmitted by the second user device to a remote user device, an indication of whether suspicious file transfer protocol (FTP) activity was detected, an indication of whether a country mismatch was detected, or an indication of whether a suspected case of a VPN compromise is present.

4. The computing system of claim 2 , wherein one or more non-transitory computer-readable storage medium further store program instructions that cause the computing system to, based on the user interface-based interaction with the notification, update the user interface data such that the user interface includes a window depicting at least one of information of a user associated with the first network address, an indication of whether the user is a person of interest, an indication of a geographic location of the user, or an indication of a geographic location to where the user tunneled.

5. The computing system of claim 2 , wherein the one or more non-transitory computer-readable storage mediums further store program instructions that cause the computing system to:

receive an indication that the notification is a false positive; and

adjust the determination of the future score based on the received indication that the notification is a false positive.

6. The computing system of claim 5 , wherein the one or more non-transitory computer-readable storage mediums further store program instructions that cause the computing system to adjust weights of one or more factors used to derive the future score based on the received indication that the notification is a false positive.

7. The computing system of claim 2 , wherein, in connection with a determination that the second log indicates that a tunneled connection is established over a first port, the determined future score is lower than if the tunneled connection is established over a second port.

8. A computer-implemented method comprising:

as implemented by one or more computer systems comprising computer hardware and memory, the one or more computer systems configured with specific executable instructions,

identifying a first address included in both a first log and in a second log, wherein the first log identifies one or more second addresses corresponding to one or more users granted access to a network, and wherein the second log identifies one or more third addresses requested via the network;

determining a score at least partly indicative of a likelihood that a malicious tunneling connection is present based at least partly on the first address; and

initiating termination a first connection if the score satisfies a threshold value.

9. The computer-implemented method of claim 8 , further comprising, generating user interface data that, when executed, causes a user device to display a user interface that depicts a notification derived from the score, wherein a user interface-based interaction with the notification causes the computing system to adjust determination of a future score.

10. The computer-implemented method of claim 9 , wherein the notification comprises at least one of a number of users that are connected to a known virtual private network (VPN) client during a time period associated with the notification, an indication of whether characteristics of traffic between the network and a second user device matches a tunneled connection profile, an indication of an amount of outbound data transmitted by the second user device to a remote user device, an indication of whether suspicious file transfer protocol (FTP) activity was detected, an indication of whether a country mismatch was detected, or an indication of whether a suspected case of a VPN compromise is present.

11. The computer-implemented method of claim 9 , further comprising, based on the user interface-based interaction with the notification, updating the user interface data such that the user interface includes a window depicting at least one of information of a user associated with the first address, an indication of whether the user is a person of interest, an indication of a geographic location of the user, or an indication of a geographic location to where the user tunneled.

12. The computer-implemented method of claim 9 , further comprising:

receiving an indication that the notification is a false positive; and

adjusting the determination of the future score based on the received indication that the notification is a false positive.

13. The computer-implemented method of claim 12 , further comprising adjusting weights of one or more factors used to derive the future score based on the received indication that the notification is a false positive.

14. The computer-implemented method of claim 9 , wherein, in connection with a determination that the second log indicates that a tunneled connection is established over a first port, the determined future score is lower than if the tunneled connection is established over a second port.

15. One or more non-transitory computer-readable mediums comprising one or more program instructions recorded thereon, the instructions configured for execution by a computing system comprising one or more processors to cause the computing system to:

identify a first address included in both a first log and in a second log, wherein the first log identifies one or more second addresses corresponding to one or more users granted access to a network, and wherein the second log identifies one or more third addresses requested via the network;

determine a score at least partly indicative of a likelihood that a malicious tunneling connection is present based at least partly on the first address; and

initiate termination a first connection if the score satisfies a threshold value.

16. The medium of claim 15 , wherein the instructions are further configured to cause the computing system to:

generate user interface data that, when executed, causes a user device to display a user interface that depicts a notification derived from the score, wherein a user interface-based interaction with the notification causes the computing system to adjust a determination of a future score.

17. The medium of claim 16 , wherein the notification comprises at least one of a number of users that are connected to a known virtual private network (VPN) client during a time period associated with the notification, an indication of whether characteristics of traffic between the network and a second user device matches a tunneled connection profile, an indication of an amount of outbound data transmitted by the second user device to a remote user device, an indication of whether suspicious file transfer protocol (FTP) activity was detected, an indication of whether a country mismatch was detected, or an indication of whether a suspected case of a VPN compromise is present.

18. The medium of claim 16 , wherein the instructions are further configured to cause the computing system to, based on the user interface-based interaction with the notification, update the user interface data such that the user interface includes a window depicting at least one of information of a user associated with the first address, an indication of whether the user is a person of interest, an indication of a geographic location of the user, or an indication of a geographic location to where the user tunneled.

19. The medium of claim 16 , wherein the instructions are further configured to cause the computing system to:

receive an indication that the notification is a false positive; and

adjust the determination of the future score based on the received indication that the notification is a false positive.

20. The medium of claim 19 , wherein the instructions are further configured to cause the computing system to adjust weights of one or more factors used to derive the future score based on the received indication that the notification is a false positive.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 1, 2023
From: RICAFORT, JUAN; SINGH, HARKIRAT; MARTIN, PHILIP
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 064451/0697 →
Continuity (7)
Continuation 17526953 · Nov 15, 2021
Continuation 16822646 · Mar 18, 2020
Continuation 15891873 · Feb 8, 2018
Continuation 15228297 · Aug 4, 2016
Continuation 14823935 · Aug 11, 2015
Provisional Application 62036999 · Aug 13, 2014
Related Publication 20230370483A1 · Nov 16, 2023
References Cited (244)
US 5978475A · Schneier et al. · 1999 [cited by applicant]
US 6253203B1 · O'Flaherty et al. · 2001 [cited by applicant]
US 6725240B1 · Asad et al. · 2004 [cited by applicant]
US 6807569B1 · Bhimani et al. · 2004 [cited by applicant]
US 7013395B1 · Swiler et al. · 2006 [cited by applicant]
US 7017046B2 · Doyle et al. · 2006 [cited by applicant]
US 7069586B1 · Winneg et al. · 2006 [cited by applicant]
US 7225468B2 · Waisman et al. · 2007 [cited by applicant]
US 7287689B2 · Tidwell et al. · 2007 [cited by applicant]
US 7472421B2 · Cummins · 2008 [cited by applicant]
US 7596285B2 · Brown et al. · 2009 [cited by applicant]
US 7770032B2 · Nesta et al. · 2010 [cited by applicant]
US 7801871B2 · Gosnell · 2010 [cited by applicant]
US 7962495B2 · Jain et al. · 2011 [cited by applicant]
US 8181253B1 · Zaitsev et al. · 2012 [cited by applicant]
US 8190893B2 · Benson et al. · 2012 [cited by applicant]
US 8196184B2 · Amirov et al. · 2012 [cited by applicant]
US 8239668B1 · Chen et al. · 2012 [cited by applicant]
US 8295898B2 · Ashfield et al. · 2012 [cited by applicant]
US 8301904B1 · Gryaznov · 2012 [cited by applicant]
US 8312546B2 · Alme · 2012 [cited by applicant]
US 8321958B1 · Fleming et al. · 2012 [cited by applicant]
US 8434150B2 · Xie et al. · 2013 [cited by applicant]
US 8448247B2 · Stute · 2013 [cited by applicant]
US 8533319B2 · Draugelis · 2013 [cited by applicant]
US 8615605B2 · Yu et al. · 2013 [cited by applicant]
US 8646080B2 · Williamson et al. · 2014 [cited by applicant]
US 8683322B1 · Cooper · 2014 [cited by applicant]
US 8726379B1 · Stiansen et al. · 2014 [cited by applicant]
US 8769412B2 · Gill et al. · 2014 [cited by applicant]
US 8782794B2 · Ramcharran · 2014 [cited by applicant]
US 8789140B2 · Williams et al. · 2014 [cited by applicant]
US 8881288B1 · Levy et al. · 2014 [cited by applicant]
US 8904506B1 · Canavor et al. · 2014 [cited by applicant]
US 8931043B2 · Cooper et al. · 2015 [cited by applicant]
US 9009827B1 · Albertson et al. · 2015 [cited by applicant]
US 9021260B1 · Falk et al. · 2015 [cited by applicant]
US 9049117B1 · Nucci et al. · 2015 [cited by applicant]
US 9100428B1 · Visbal · 2015 [cited by applicant]
US 9319419B2 · Sprague et al. · 2016 [cited by applicant]
US 9335897B2 · Goldenberg · 2016 [cited by applicant]
US 9338013B2 · Castellucci et al. · 2016 [cited by applicant]
US 9401925B1 · Guo et al. · 2016 [cited by applicant]
US 9407652B1 · Kesin et al. · 2016 [cited by applicant]
US 9419992B2 · Ricafort et al. · 2016 [cited by applicant]
US 9537880B1 · Jones et al. · 2017 [cited by applicant]
US 9576119B2 · McGeehan et al. · 2017 [cited by applicant]
US 9628500B1 · Kesin et al. · 2017 [cited by applicant]
US 9930055B2 · Ricafort et al. · 2018 [cited by applicant]
US 10609046B2 · Ricafort et al. · 2020 [cited by applicant]
US 11201879B2 · Ricafort et al. · 2021 [cited by applicant]
US 11757905B2 · Ricafort et al. · 2023 [cited by applicant]
US 20020112157A1 · Doyle et al. · 2002 [cited by applicant]
US 20030055990A1 · Cheline et al. · 2003 [cited by applicant]
US 20040003285A1 · Whelan et al. · 2004 [cited by applicant]
US 20040123139A1 · Aiello et al. · 2004 [cited by applicant]
US 20040128508A1 · Wheeler et al. · 2004 [cited by applicant]
US 20040153418A1 · Hanweck · 2004 [cited by applicant]
US 20040250124A1 · Chesia et al. · 2004 [cited by applicant]
US 20050022012A1 · Bluestone et al. · 2005 [cited by applicant]
US 20050125295A1 · Tidwell et al. · 2005 [cited by applicant]
US 20050157662A1 · Bingham et al. · 2005 [cited by applicant]
US 20050229256A2 · Banzhof · 2005 [cited by applicant]
US 20050262556A1 · Waisman et al. · 2005 [cited by applicant]
US 20050275638A1 · Kolmykov-Zotov et al. · 2005 [cited by applicant]
US 20060021049A1 · Cook · 2006 [cited by applicant]
US 20060031928A1 · Conley et al. · 2006 [cited by applicant]
US 20060069912A1 · Zheng et al. · 2006 [cited by applicant]
US 20060156407A1 · Cummins · 2006 [cited by applicant]
US 20060179003A1 · Steele et al. · 2006 [cited by applicant]
US 20060212931A1 · Shull et al. · 2006 [cited by applicant]
US 20060218637A1 · Thomas et al. · 2006 [cited by applicant]
US 20060265324A1 · Leclerc et al. · 2006 [cited by applicant]
US 20060265747A1 · Judge · 2006 [cited by applicant]
US 20060265751A1 · Cosquer et al. · 2006 [cited by applicant]
US 20070067846A1 · McFarlane et al. · 2007 [cited by applicant]
US 20070143851A1 · Nicodemus · 2007 [cited by examiner]
US 20070214115A1 · Liu et al. · 2007 [cited by applicant]
US 20070294766A1 · Mir et al. · 2007 [cited by applicant]
US 20080005555A1 · Lotem et al. · 2008 [cited by applicant]
US 20080082380A1 · Stephenson · 2008 [cited by applicant]
US 20080104407A1 · Horne et al. · 2008 [cited by applicant]
US 20080201580A1 · Savitzky et al. · 2008 [cited by applicant]
US 20080222706A1 · Renaud et al. · 2008 [cited by applicant]
US 20080229422A1 · Hudis et al. · 2008 [cited by applicant]
US 20090103442A1 · Douville · 2009 [cited by applicant]
US 20090228701A1 · Lin · 2009 [cited by applicant]
US 20090292743A1 · Bigus et al. · 2009 [cited by applicant]
US 20090328222A1 · Helman et al. · 2009 [cited by applicant]
US 20100024017A1 · Ashfield et al. · 2010 [cited by applicant]
US 20100077481A1 · Polyakov et al. · 2010 [cited by applicant]
US 20100100963A1 · Mahaffey · 2010 [cited by applicant]
US 20100179831A1 · Brown et al. · 2010 [cited by applicant]
US 20100235915A1 · Memon et al. · 2010 [cited by applicant]
US 20100262688A1 · Hussain et al. · 2010 [cited by applicant]
US 20100330801A1 · Rouh · 2010 [cited by applicant]
US 20110060910A1 · Gormish et al. · 2011 [cited by applicant]
US 20110202555A1 · Cordover et al. · 2011 [cited by applicant]
US 20110219450A1 · McDougal et al. · 2011 [cited by applicant]
US 20110288660A1 · Wojsznis et al. · 2011 [cited by applicant]
US 20110295982A1 · Misra · 2011 [cited by applicant]
US 20110296003A1 · McCann et al. · 2011 [cited by applicant]
US 20120079592A1 · Pandrangi · 2012 [cited by applicant]
US 20120084866A1 · Stolfo · 2012 [cited by applicant]
US 20120110633A1 · An et al. · 2012 [cited by applicant]
US 20120110674A1 · Belani et al. · 2012 [cited by applicant]
US 20120124092A1 · Teranishi et al. · 2012 [cited by applicant]
US 20120169593A1 · Mak et al. · 2012 [cited by applicant]
US 20120185419A1 · Kuhn et al. · 2012 [cited by applicant]
US 20120198489A1 · O'Connell et al. · 2012 [cited by applicant]
US 20120218305A1 · Patterson et al. · 2012 [cited by applicant]
US 20120254129A1 · Wheeler et al. · 2012 [cited by applicant]
US 20120266245A1 · McDougal et al. · 2012 [cited by applicant]
US 20120284791A1 · Miller et al. · 2012 [cited by applicant]
US 20120304244A1 · Xie et al. · 2012 [cited by applicant]
US 20120323829A1 · Stokes et al. · 2012 [cited by applicant]
US 20120330801A1 · McDougal et al. · 2012 [cited by applicant]
US 20130019306A1 · Lagar-Cavilla et al. · 2013 [cited by applicant]
US 20130091052A1 · Kaperdal et al. · 2013 [cited by applicant]
US 20130097709A1 · Basavapatna et al. · 2013 [cited by applicant]
US 20130110876A1 · Meijer et al. · 2013 [cited by applicant]
US 20130139268A1 · An et al. · 2013 [cited by applicant]
US 20130239217A1 · Kindler et al. · 2013 [cited by applicant]
US 20130254833A1 · Nicodemus et al. · 2013 [cited by applicant]
US 20130254885A1 · Devost · 2013 [cited by applicant]
US 20130275416A1 · Thomson et al. · 2013 [cited by applicant]
US 20140013451A1 · Kulka et al. · 2014 [cited by applicant]
US 20140053265A1 · Crowley · 2014 [cited by applicant]
US 20140059683A1 · Ashley · 2014 [cited by applicant]
US 20140082691A1 · Warn et al. · 2014 [cited by applicant]
US 20140123279A1 · Bishop et al. · 2014 [cited by applicant]
US 20140143009A1 · Brice et al. · 2014 [cited by applicant]
US 20140173712A1 · Ferdinand · 2014 [cited by examiner]
US 20140173738A1 · Condry et al. · 2014 [cited by applicant]
US 20140181968A1 · Ge et al. · 2014 [cited by applicant]
US 20140188895A1 · Wang et al. · 2014 [cited by applicant]
US 20140201345A1 · Abuelsaad et al. · 2014 [cited by applicant]
US 20140229422A1 · Jain et al. · 2014 [cited by applicant]
US 20140279684A1 · Liao et al. · 2014 [cited by applicant]
US 20140283107A1 · Walton et al. · 2014 [cited by applicant]
US 20140366132A1 · Stiansen et al. · 2014 [cited by applicant]
US 20150026027A1 · Priess et al. · 2015 [cited by applicant]
US 20150039565A1 · Lucas · 2015 [cited by applicant]
US 20150089568A1 · Sprague et al. · 2015 [cited by applicant]
US 20150128274A1 · Giokas · 2015 [cited by applicant]
US 20150188715A1 · Castelluci et al. · 2015 [cited by applicant]
US 20150229664A1 · Hawthorn et al. · 2015 [cited by applicant]
US 20150235152A1 · Eldardiry et al. · 2015 [cited by applicant]
US 20150248563A1 · Alfarano et al. · 2015 [cited by applicant]
US 20150261847A1 · Ducott et al. · 2015 [cited by applicant]
US 20150326601A1 · Grondin et al. · 2015 [cited by applicant]
US 20160004864A1 · Falk et al. · 2016 [cited by applicant]
US 20160028759A1 · Visbal · 2016 [cited by applicant]
US 20160050224A1 · Ricafort et al. · 2016 [cited by applicant]
US 20160191532A1 · Seiver et al. · 2016 [cited by applicant]
US 20170003352A1 · Barre et al. · 2017 [cited by applicant]
US 20170099311A1 · Kesin et al. · 2017 [cited by applicant]
US 20170111381A1 · Jones et al. · 2017 [cited by applicant]
US 20170195354A1 · Kesin et al. · 2017 [cited by applicant]
US 20170302531A1 · Maes · 2017 [cited by applicant]
US 20190243819A1 · Miliauskas · 2019 [cited by applicant]
CN 101729531 · 2010 [cited by applicant]
CN 103281301 · 2013 [cited by applicant]
EP 1589716 · 2005 [cited by applicant]
EP 1962222 · 2008 [cited by applicant]
EP 2284769 · 2011 [cited by applicant]
EP 2892197 · 2015 [cited by applicant]
EP 2897051 · 2015 [cited by applicant]
EP 2963578 · 2016 [cited by applicant]
EP 2985974 · 2016 [cited by applicant]
EP 3110104 · 2016 [cited by applicant]
EP 3133522 · 2017 [cited by applicant]
NL 2011642 · 2015 [cited by applicant]
WO WO2005010685 · 2005 [cited by applicant]
Baker et al., “The Development of a Common Enumeration of Vulnerabilities and Exposures,” Presented at the Second International Workshop on Recent Advances in Intrusion Detection, Sep. 7-9, 1999, pp. 35. [cited by applicant]
Bhuyan et al., “Network Anomaly Detection: Methods, Systems and Tools,” First Quarter 2014, IEEE, 34 pages. [cited by applicant]
Crosby et al., “Efficient Data Structures for Tamper-Evident Logging,” Department of Computer Science, Rice University, 2009, pp. 17. [cited by applicant]
FireEye—Products and Solutions Overview, <http://www.fireeye.com/products-and-solutions> Printed Jun. 30, 2014 in 3 pages. [cited by applicant]
FireEye, <http://www.fireeye.com/> Printed Jun. 30, 2014 in 2 pages. [cited by applicant]
Glaab et al., “EnrichNet: Network-Based Gene Set Enrichment Analysis,” Bioinformatics 28.18 (2012): pp. i451-i457. [cited by applicant]
Huang et al., “Systematic and Integrative Analysis of Large Gene Lists Using David Bioinformatics Resources,” Nature Protocols, 4.1, 2008, 44-57. [cited by applicant]
Hur et al., “SciMiner: web-based literature mining tool for target identification and functional enrichment analysis,” Bioinformatics 25.6 (2009): pp. 838-840. [cited by applicant]
Lee et al., “A Data Mining and CIDF Based Approach for Detecting Novel and Distributed Intrusions,” Lecture Notes in Computer Science, vol. Nov. 11, 1907, 2000, pp. 49-65. [cited by applicant]
Ma et al., “A New Approach to Secure Logging,” ACM Transactions on Storage, vol. 5, No. 1, Article 2, Published Mar. 2009, 21 pages. [cited by applicant]
Schneier et al., “Automatic Event Stream Notarization Using Digital Signatures,” Security Protocols, International Workshop Apr. 1996 Proceedings, Springer-Verlag, 1997, pp. 155-169, https://schneier.com/paper-event-str… [cited by applicant]
Schneier et al., “Cryptographic Support for Secure Logs on Untrusted Machines,” The Seventh USENIX Security Symposium Proceedings, USENIX Press, Jan. 1998, pp. 53-62, https://www.schneier.com/paper-secure-logs.pdf. [cited by applicant]
VirusTotal—About, <http://www.virustotal.com/en/about/> Printed Jun. 30, 2014 in 8 pages. [cited by applicant]
Waters et al., “Building an Encrypted and Searchable Audit Log,” Published Jan. 9, 2004, 11 pages, http://www.parc.com/content/attachments/building_encrypted_searchable_5059_parc.pdf. [cited by applicant]
Zheng et al., “GOEAST: a web-based software toolkit for Gene Ontology enrichment analysis,” Nucleic acids research 36.suppl 2 (2008): pp W385-W363. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/982,699 dated Oct. 7, 2016. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/033,076 dated Mar. 11, 2016. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/223,918 dated Jan. 6, 2016. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/280,490 dated Nov. 26, 2014. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/473,860 dated Feb. 27, 2015. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/473,860 dated Jan. 5, 2015. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/479,863 dated Mar. 31, 2015. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/823,935 dated Apr. 25, 2016. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/970,317 dated May 26, 2016. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 15/224,443 dated Dec. 19, 2016. [cited by applicant]
Official Communication for European Patent Application No. 14199180.2 dated Jun. 22, 2015. [cited by applicant]
Official Communication for European Patent Application No. 14199180.2 dated Aug. 31, 2015. [cited by applicant]
Official Communication for European Patent Application No. 15175106.2 dated Nov. 5, 2015. [cited by applicant]
Official Communication for European Patent Application No. 15180985.2 dated Jan. 15, 2016. [cited by applicant]
Official Communication for European Patent Application No. 15180985.2 dated Mar. 30, 2017. [cited by applicant]
Official Communication for European Patent Application No. 16176273.7 dated Oct. 21, 2016. [cited by applicant]
Official Communication for European Patent Application No. 16184823.9 dated Nov. 24, 2016. [cited by applicant]
Official Communication for European Patent Application No. 17155145.0 dated Aug. 31, 2017. [cited by applicant]
Official Communication for U.S. Appl. No. 14/033,076 dated Aug. 13, 2015. [cited by applicant]
Official Communication for U.S. Appl. No. 14/033,076 dated Nov. 6, 2015. [cited by applicant]
Official Communication for U.S. Appl. No. 14/223,918 dated Jun. 8, 2015. [cited by applicant]
Official Communication for U.S. Appl. No. 14/280,490 dated Jul. 24, 2014. [cited by applicant]
Official Communication for U.S. Appl. No. 14/473,860 dated Nov. 4, 2014. [cited by applicant]
Official Communication for U.S. Appl. No. 14/479,863 dated Dec. 26, 2014. [cited by applicant]
Official Communication for U.S. Appl. No. 14/490,612 dated Aug. 18, 2015. [cited by applicant]
Official Communication for U.S. Appl. No. 14/490,612 dated Jan. 27, 2015. [cited by applicant]
Official Communication for U.S. Appl. No. 14/490,612 dated Mar. 31, 2015. [cited by applicant]
Official Communication for U.S. Appl. No. 14/731,312 dated Apr. 14, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 14/816,748 dated Apr. 1, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 14/816,748 dated May 24, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 14/823,935 dated Dec. 4, 2015. [cited by applicant]
Official Communication for U.S. Appl. No. 14/923,712 dated Feb. 12, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 14/923,712 dated Jun. 17, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 14/970,317 dated Mar. 21, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 14/982,699 dated Mar. 25, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 14/982,699 dated Aug. 26, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 15/071,064 dated Jun. 16, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 15/207,343 dated Nov. 23, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 15/207,343 dated Sep. 27, 2017. [cited by applicant]
Official Communication for U.S. Appl. No. 15/395,483 dated Jul. 6, 2017. [cited by applicant]
Official Communication for U.S. Appl. No. 15/462,540 dated Jul. 5, 2017. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 15/207,343 dated Apr. 3, 2018. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 15/228,297 dated Nov. 24, 2017. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 15/462,540 dated May 10, 2018. [cited by applicant]
Official Communication for European Patent Application No. 16184823.9 dated May 23, 2018. [cited by applicant]
Official Communication for European Patent Application No. 18161005.6 dated Apr. 11, 2018. [cited by applicant]
Official Communication for U.S. Appl. No. 15/207,343 dated May 17, 2017. [cited by applicant]
Official Communication for U.S. Appl. No. 15/224,443 dated Dec. 19, 2016. [cited by applicant]
Official Communication for U.S. Appl. No. 15/228,297 dated Jun. 30, 2017. [cited by applicant]
Official Communication for U.S. Appl. No. 15/395,483 dated Sep. 21, 2017. [cited by applicant]
Official Communication for U.S. Appl. No. 15/395,483 dated Mar. 28, 2018. [cited by applicant]
Official Communication for U.S. Appl. No. 15/462,540 dated Oct. 13, 2017. [cited by applicant]
Official Communication for U.S. Appl. No. 15/838,658 dated Mar. 8, 2018. [cited by applicant]
Official Communication for U.S. Appl. No. 16/035,956 dated Sep. 9, 2019. [cited by applicant]
Official Communication for U.S. Appl. No. 16/109,379 dated Jul. 17, 2019. [cited by applicant]