The following materials are incorporated by reference as if fully set forth herein:
The technology disclosed relates to securing network traffic to and from hosted services and, in particular, relates to using metadata to detect and prevent phishing attacks that attempt to exfiltrate data from the hosted services.
The subject matter discussed in this section should not be assumed to be prior art merely as a result of its mention in this section. Similarly, a problem mentioned in this section or associated with the subject matter provided as background should not be assumed to have been previously recognized in the prior art. The subject matter in this section merely represents different approaches, which in and of themselves can also correspond to implementations of the claimed technology.
Phishing is an attempt from phishers to elicit confidential information of users by using fake websites. Phishers want to get access to private account information and passwords. A successful phishing attack can have disastrous consequences for the victims leading to financial losses and data theft. Usually, phishers send fraudulent emails or chat messages with a link and the lure to click on it. There is a multitude of different phishing attacks like spear phishing, where phishers want to increase their success rate by sending e-mails to specific companies with individual matched content. Another type of phishing is called clone phishing, where phishers clone a previously sent message and replace the legitimate content with malicious information like links or formulas.
The ability to access cloud services from anywhere makes the potential for a successful phishing-based compromise easier. 25% of phishing attacks bypass default security measures built into Office 365, a prominent cloud service which is the most-impersonated brand in phishing attacks.
Cloud-based email has rung in a new era of phishing. The connected nature of cloud-based email allows phishers to get access to a bigger bounty from a single successful phishing attack since the credentials give them access to other connected accounts.
Impersonation phishing attacks involve placing a link to a phishing web page that prompts employees to log in; however, the users are actually sacrificing their credentials to phishers instead of logging in. From there, when the unsuspecting victims click on the link and are directed to a false sign-in page, they provide phishers with their usernames and password without knowing they had done anything out of the ordinary.
After stealing the credentials, the phishers typically use them to remotely log into the user's Office 365 account or other email accounts and use this as a launching point for other spear phishing attacks. At this point, it becomes even more difficult to detect phishers at work because they send additional phishing emails to other employees or external partners, trying to entice those recipients to click on a phishing link.
Impersonation phishing attacks are challenging to detect for several reasons. Phishing links are typically zero-day where a unique link is sent to each recipient, and therefore they never appear on any security blacklists. In many cases, the phishing links lead to a legitimate website, where the attacker has maliciously inserted a sign-in page, and the domain and IP reputation are legitimate. Link protection technologies such as safe links do not protect against these phishing links. Since the phishing link just contains a sign-in page and does not download any malicious viruses, the user follows the safe link and still enters the username and password.
Therefore, effective protection against phishing is needed.
In the drawings, like reference characters generally refer to like parts throughout the different views. Also, the drawings are not necessarily to scale, with an emphasis instead generally being placed upon illustrating the principles of the technology disclosed. In the following description, various implementations of the technology disclosed are described with reference to the following drawings.
The following discussion is presented to enable any person skilled in the art to make and use the technology disclosed, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed implementations will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations and applications without departing from the spirit and scope of the technology disclosed. Thus, the technology disclosed is not intended to be limited to the implementations shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
We describe a system and various implementations for detecting and preventing phishing attacks. The system and processes are described with reference to
The network security system 125 includes an image classifier 135 (e.g., convolutional neural network), a webpage analyzer 145, a traffic data analyzer 155, a security action executer 165, and a metadata store 175.
The modules of the endpoints 102 and the network security system 125 can be implemented in hardware or software, and need not be divided up in precisely the same blocks as shown in
The interconnections of the elements of environment 100 are now described. The public network(s) 115 couples the endpoints 102, the network security system 125, and the hosted services 108, all in communication with each other (indicated by solid double-arrowed lines). The actual communication path can be point-to-point over public and/or private networks. Some items, such as the endpoint routing client 112, might be delivered indirectly, e.g., via an application store (not shown). The communications can occur over a variety of networks, e.g., private networks, VPN (Virtual Private Network), MPLS circuit, or Internet, and can use appropriate application programming interfaces (APIs) and data interchange formats, e.g., Representational State Transfer (REST), JavaScript Object Notation (JSON), Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Java Message Service (JMS), and/or Java Platform Module System. All of the communications can be encrypted. The communication is generally over a network such as the LAN (local area network), WAN (wide area network), telephone network (Public Switched Telephone Network (PSTN), Session Initiation Protocol (SIP), wireless network, point-to-point network, star network, token ring network, hub network, Internet, inclusive of the mobile Internet, via protocols such as EDGE, 3G, 4G LTE, Wi-Fi, and WiMAX. Additionally, a variety of authorization and authentication techniques, such as username/password, Open Authorization (OAuth), Kerberos, SecureID, digital certificates and more, can be used to secure the communications.
Endpoints 102 can be desktop computers, laptops, tablet computers, mobile phones, or any other type of computing devices. The engines or system components of environment 100 such as the network security system 125 are implemented by software running on varying types of computing devices. Example devices are a workstation, a server, a computing cluster, a blade server, and a server farm.
Having introduced the elements of
In
Hosted services 108 provide functionality to users that can be implemented in the cloud and that can be the target of data loss prevention (DLP) policies, e.g., logging in, editing documents, downloading bulk data, reading customer contact information, entering payables, and deleting documents. Hosted services 108 can be a network service or application, or can be web-based (e.g., accessed via a URL) or native, such as sync clients. Examples include software-as-a-service (SaaS) offerings, platform-as-a-service (PaaS) offerings, and infrastructure-as-a-service (IaaS) offerings, as well as internal enterprise applications that are exposed via URLs. Examples of common hosted services today include BOX™, GOOGLE DRIVE™, SALESFORCE.COM™, DROPBOX™, MICROSOFT ONEDRIVE 365™, APPLE ICLOUD DRIVE™, ORACLE ON DEMAND™, SUGARSYNC™, IDRIVE™, and SPIDEROAK ONE™.
Sanctioned hosted services are those hosted services that the company provides for employee use and of which IT is aware. IT usually has full administrative control over these hosted services and maintains them on behalf of the business. Even though IT may manage sanctioned hosted services, the department still may lack specific knowledge about how users are accessing these hosted services and what activities they are performing, including uploading, downloading, sharing, or editing corporate data.
Unsanctioned hosted services are those hosted services that the company does not know about. Very often, if IT does not provide the necessary tools to accomplish a needed business function, employees go outside of IT and procure their own hosted services. Employees can easily find, pay for, download, and administer these hosted services without IT's knowledge or assistance. On the one hand, this is a good thing because it gives employees a way to work efficiently. On the other hand, these unsanctioned hosted services create risk for IT. Keeping hosted services and the data within them secure is challenging when IT does not know about them. IT cannot properly enforce security or compliance in unsanctioned hosted services. Without important security features, such as strong user authentication and audit logging, these hosted services and the data within them are vulnerable to inadvertent or intentional data exposure. Finally, IT has no idea how users are using unsanctioned hosted services.
Hosted services 108 can also be determined/identified/graded based on NETSKOPE CLOUD CONFIDENCE INDEX™ that assesses a hosted service's enterprise-readiness based on objective criteria and assigns an overall score. In particular, NETSKOPE CLOUD CONFIDENCE INDEX™ measures the enterprise readiness of hosted services by taking into various attributes of the hosted services. The following list of hosted service attribute is exemplary rather than exhaustive and includes: encryption policies, auditability and business continuity, disaster management policies, number of data centers, compliance certifications (e.g. SOC2) of the data centers, identity and access control, file sharing, data classification, audit and alert, data access logs preservation, password policy, forfeiture policies, published data recovery plan, and ability to proxy traffic for inspection and security controls.
In some implementations, NETSKOPE CLOUD CONFIDENCE INDEX™ assigns a score between 0 and 100 to each hosted service that interfaces with an organization's network. Further, based on the assigned score, the hosted services can be categorized into different cloud confidence levels such as excellent, high, medium, low, or poor.
In other implementations, NETSKOPE CLOUD CONFIDENCE INDEX™ groups the hosted services into a plurality of categories, including cloud storage, collaboration, finance and accounting, customer relationship management (CRM), human resources, and software development.
Hosted services 108 publish their application programming interfaces (APIs) to allow a third party to communicate with them and utilize their underlying data. An API refers to a packaged collection of code libraries, routines, protocols methods, and fields that belong to a set of classes, including its interface types. The API defines the way that developers and programmers can use the classes for their own software development, just by importing the relevant classes and writing statements that instantiate the classes and call their methods and fields. An API is a source code-based application intended to be used as an interface by software components to communicate with each other. An API can include applications for routines, data structures, object classes, and variables. Basically, an API provides an interface for developers and programmers to access the underlying data, platform capabilities, and features of hosted services. Implementations of the technology disclosed use different types of APIs, including web service APIs such as HTTP or HTTPs based APIs like SOAP, WSDL, Bulk, XML-RPC and JSON-RPC and REST APIs (e.g., FLICKR™, GOOGLE STATIC MAPS™, GOOGLE GEOLOCATION™), web socket APIs, library-based APIs like JavaScript and TWAIN (e.g., GOOGLE MAPS™ Javascript API, DROPBOX™ JavaScript Data store API, TWILIO™ APIs, Oracle Call Interface (OCI)), class-based APIs like Java API and Android API (e.g., GOOGLE MAPS™ Android API, MSDN Class Library for .NET Framework, TWILIO™ APIs for Java and C #), OS functions and routines like access to file system and access to user interface, object remoting APIs like CORBA and .NET Remoting, and hardware APIs like video acceleration, hard disk drives, and PCI buses. Other examples of APIs used by the technology disclosed include AMAZON EC2 API™, BOX CONTENT API™, BOX EVENTS API™, MICROSOFT GRAPH™, DROPBOX API™, DROPBOX API v2™, DROPBOX CORE API™, DROPBOX CORE API v2™, FACEBOOK GRAPH API™, FOURSQUARE API™, GEONAMES API™ FORCE.COM API™, FORCE.COM METADATA API™, APEX API™, VISUALFORCE API™, FORCE.COM ENTERPRISE WSDL™, SALESFORCE.COM STREAMING API™ SALESFORCE.COM TOOLING API™, GOOGLE DRIVE API™, DRIVE REST API™ ACCUWEATHER API™, and aggregated-single API like CLOUDRAIL™ API.
Having described the hosted services 108 and their APIs, the discussion now turns to the network security system 125.
The network security system 125 provides a variety of functionalities, including using the image classifier 135 to analyze one or more images of a webpage and determine that a particular hosted service is represented by the images, using the webpage analyzer 145 to analyze one or more fields of the webpage and determine that the fields elicit confidential information, using the traffic data analyzer 155 to analyze a request (e.g., HTTP request) and determine that the confidential information is being exfiltrated to an unsanctioned resource by comparing a resource address in the request with one or more sanctioned resource addresses used by the particular hosted service, using the metadata store 175 to store/list/identify the sanctioned resource addresses, and using the security action executer 165 to block transmission of the confidential information to the unsanctioned resource. These functionalities collectively prevent phishers from maliciously accessing the hosted services 108 via the endpoints 102. More generally, the network security system 125 provides application visibility and control functions as well as security.
The image classifier 135 can implement any image classification algorithm such as convolutional neural networks, state vector machines, random forests, and gradient boosted decision trees. The image classifier 135 can be trained to map webpage images to hosted services 108 using backpropagation-based stochastic gradient update training techniques (e.g., by using the ADAM training algorithm).
The webpage analyzer 145 parses and analyzes an HTML document, a PDF, an image, a JavaScript code, a data storage layer (e.g., local Storage, IndexedDB, WebSQL, FileSystem), or some other type of content (e.g., cascading style sheets (CSS)). In one implementation, the webpage analyzer 145 parses the HTML document and converts elements to DOM nodes in a content tree. In another implementation, it parses and analyzes the already generated content tree. In one implementation, it parses and analyzes style data, both in external CSS files and in style elements. In another implementation, it parses and analyzes a render tree that contains styling information together with visual instructions in the HTML document. In some implementations, the parsing also includes lexical analysis and syntax analysis of the text and fields (key-value pairs) of the HTML document.
The traffic data analyzer 155 parses and analyzes Hypertext Transfer Protocol (HTTP) requests such as GET requests, POST requests, and HEAD requests. The HTTP requests include general headers (connection, date), request/response headers, and entity headers (content-length, content-type, last-modified). In one implementation, the traffic data analyzer 155 parses and analyzes the HTTP headers in the POST requests. In one implementation, the traffic data analyzer 155 uses connectors or standardized integrations to interpret the HTTP transactions using deep API inspection (DAPII).
The security action executer 165 executes security actions, including block, alert, bypass, quarantine, coach, initiate a workflow to remediate, record, seek justification, report on the out-of-compliance event or activity, or content encryption. The type of the security action can be based on at least one of the type of the content policies, the content-level activity being performed, and the content-type. In other implementations, certain off-line inspections can be triggered as security actions, such as changing the ownership of sensitive data.
For further information regarding the functionalities of the network security system 125, reference can be made to, for example, commonly owned U.S. patent application Ser. Nos. 14/198,499; 14/198,508; 14/835,640; 14/835,632; and 62/307,305; Cheng, Ithal, Narayanaswamy, and Malmskog. Cloud Security For Dummies, Netskope Special Edition. John Wiley & Sons, Inc. 2015; “Netskope Introspection” by Netskope, Inc.; “Data Loss Prevention and Monitoring in the Cloud” by Netskope, Inc.; “Cloud Data Loss Prevention Reference Architecture” by Netskope, Inc.; “The 5 Steps to Cloud Confidence” by Netskope, Inc.; “The Netskope Reactive Platform” by Netskope, Inc.; “The Netskope Advantage: Three “Must-Have” Requirements for Cloud Access Security Brokers” by Netskope, Inc.; “The 15 Critical NSS Use Cases” by Netskope, Inc.; “Netskope Reactive Cloud DLP” by Netskope, Inc.; “Repave the Cloud-Data Breach Collision Course” by Netskope, Inc.; and “Netskope Cloud Confidence Index™” by Netskope, Inc., which are incorporated by reference for all purposes as if fully set forth herein.
Regarding the endpoint routing client 112, it routes network traffic emanating from the endpoints 102 to the network security system 125. Depending on the type of device, it can be a virtual private network (VPN) such as VPN on demand or per-app-VPN that use certificate-based authentication. For example, for iOS™ devices, it can be a per-app-VPN or can be a set of domain-based VPN profiles. For Android™ devices, it can be a cloud director mobile app. For Windows™ devices, it can be a per-app-VPN or can be a set of domain-based VPN profiles. Endpoint routing client 112 can also be an agent that is downloaded using e-mail or silently installed using mass deployment tools like ConfigMgr™, Altris™, and Jamf™.
The endpoint security system 202 provides a variety of functionalities, including using the image classifier 135 to analyze one or more images of a webpage and determine that a particular hosted service is represented by the images, using the webpage analyzer 145 to analyze one or more fields of the webpage and determine that the fields elicit confidential information, using the traffic data analyzer 155 to analyze a request (e.g., HTTP request) and determine that the confidential information is being exfiltrated to an unsanctioned resource by comparing a resource address in the request with one or more sanctioned resource addresses used by the particular hosted service, using the metadata store 175 to store/list/identify the sanctioned resource addresses, and using the security action executer 165 to block transmission of the confidential information to the unsanctioned resource. These functionalities collectively prevent phishers from maliciously accessing the hosted services 108 via the endpoints 102. More generally, the endpoint security system 202 provides application visibility and control functions as well as security.
The phishing decoy 402 traditionally arrives as an email attachment to phishing victims. It is crafted to contain legitimate content and comes from legitimate sources. Often, attachments are saved to cloud storage services like GOOGLE DRIVE™. Sharing these documents with other users can cause secondary propagation vector like the cloud fishing fan-out effect described in U.S. Nonprovisional patent application Ser. No. 15/911,034, which is incorporated herein.
The phishing decoy 402 contains a hyperlink to download the actual PDF, as shown in
The phishing webpage 602 is hosted in Azure blob storage. As a result, it has a valid Microsoft-issued SSL certificate 702 and is hosted on a Microsoft-owned domain, as shown in
First, the image classifier 135 accesses the images of the phishing webpage 602 and, based on processing the image features 604 and 606, determines that the images are used by the MICROSOFT EXCEL™ application of the hosted service MICROSOFT OFFICE 365™. Therefore, the image classifier 135 predicts that the images of the phishing webpage 602 represent the hosted service MICROSOFT OFFICE 365™.
Then, the webpage analyzer 145 parses the phishing webpage 602 and analyzes the fields 614 and 624. Based on the analysis of the fields 614 and 624, the webpage analyzer 145 infers that the fields 614 and 624 are eliciting confidential information, i.e., email addresses and email password. In other implementations, different type of confidential information may be elicited and thereby detected. Some examples include controlled unclassified information (CUI), personally identifiable information (PII), protected health information (PHI), payment card industry (PCI) information, social security numbers, driver's license information, and biometric records.
The traffic data analyzer 155 then parses the HTTP header 844 and determines that the confidential information 832 and 834 is being uploaded to the URL 824 in the POST field. Then, the traffic data analyzer 155 accesses the metadata store 175 to determine which sanctioned resource addresses 804 (URLs, domain names, subdomain names, URIs, IP addresses, SNIs, SANs) are associated with the hosted service MICROSOFT OFFICE 365™. The traffic data analyzer 155 then compares 802 substrings of the URL 824 with substrings of the sanctioned resource addresses 804. If, based on the comparison 802, the traffic data analyzer 155 determines that the URL 824 is not a sanctioned resource address of the hosted service MICROSOFT OFFICE 365™. Therefore, the traffic data analyzer 155 determines that the confidential information 832 and 834 is being exfiltrated 806 to an unsanctioned resource or location.
The security action executer 165 stops the exfiltration 806 by blocking 818 the posting of the confidential information 832 and 834 to the unsanctioned URL 824.
In other implementations of the technology disclosed, in addition to or instead of the machine learning-based classification approaches, the technology disclosed can use image fingerprinting algorithms like perceptual hashing for image disambiguation and classification. Additional details about perceptual hashing can be found here Perceptual hashing, https://en.wikipedia.org/w/index.php?title=Perceptual_hashing&oldid=999157579 (last visited Jan. 25, 2021), which is incorporated by reference as if fully set forth herein.
Communications between the endpoints 102 and the server 1008 are monitored and mediated by the network security system 125 that is interposed in between them.
First, a user issues user action 1014 via a client 1012 (e.g., browser) running on the endpoints 102. In one implementation, the user action 1014 is selection of a hyperlink that serves as a phishing bait.
In response to the user action 1014, the server 1008 sends toward the client 1012 a phishing webpage 1026.
Then, the image classifier 135 of the network security system 125 performs image analysis 1032 of images of the phishing webpage 1026 and identifies a particular hosted service represented by the images.
Then, the webpage analyzer 145 of the network security system 125 performs field analysis 1042 of the fields of the phishing webpage 1026 and determines that the fields are eliciting confidential information.
Then, a user action 1054 attempts to submit the confidential information via the request 1052. The request 1052 is intercepted by the network security system 125 and not completed.
Then, the traffic data analyzer 155 of the network security system 125 performs request analysis 1062 of the request 1052 and determines that the confidential information is being exfiltrated to an unsanctioned resource or location. This determination is made by comparing 1076 a resource address in the request 1052 (e.g., POST URL) with one or more sanctioned resource addresses used by the particular hosted service, which are identified/listed in the metadata store 175 of the network security system 125.
Then, the network security system 125 determines that the phishing webpage is effectuating a phishing attack and blocks 1086 transmission of the confidential information to the unsanctioned resource.
In other implementations, if the comparison 1076 yields that the confidential information is being sent to a sanctioned resource or location, then the request is not blocked and instead fulfilled.
First, a user issues user action 1114 via a client 1112 (e.g., browser) running on the endpoints 102. In one implementation, the user action 1114 is selection of a hyperlink that serves as a phishing bait.
In response to the user action 1114, the server 1108 sends toward the client 1112 a phishing webpage 1126.
Then, the image classifier 135 of the endpoint security system 202 performs image analysis 1132 of images of the phishing webpage 1126 and identifies a particular hosted service represented by the images.
Then, the webpage analyzer 145 of the endpoint security system 202 performs field analysis 1142 of the fields of the phishing webpage 1126 and determines that the fields are eliciting confidential information.
Then, a user action 1154 attempts to submit the confidential information via the request 1152. The request 1152 is intercepted by the endpoint security system 202 and not completed.
Then, the traffic data analyzer 155 of the endpoint security system 202 performs request analysis 1162 of the request 1152 and determines that the confidential information is being exfiltrated to an unsanctioned resource or location. This determination is made by comparing 1176 a resource address in the request 1152 (e.g., POST URL) with one or more sanctioned resource addresses used by the particular hosted service, which are identified/listed in the metadata store 175 of the endpoint security system 202.
Then, the endpoint security system 202 determines that the phishing webpage is effectuating a phishing attack and blocks 1186 transmission of the confidential information to the unsanctioned resource.
In other implementations, if the comparison 1176 yields that the confidential information is being sent to a sanctioned resource or location, then the request is not blocked and instead fulfilled.
In one implementation, the network security system 125 and/or the endpoint security system 202 are communicably linked to the storage subsystem 1210 and the user interface input devices 1238.
User interface input devices 1238 can include a keyboard; pointing devices such as a mouse, trackball, touchpad, or graphics tablet; a scanner; a touch screen incorporated into the display; audio input devices such as voice recognition systems and microphones; and other types of input devices. In general, use of the term “input device” is intended to include all possible types of devices and ways to input information into the computer system 1200.
User interface output devices 1276 can include a display subsystem, a printer, a fax machine, or non-visual displays such as audio output devices. The display subsystem can include an LED display, a cathode ray tube (CRT), a flat-panel device such as a liquid crystal display (LCD), a projection device, or some other mechanism for creating a visible image. The display subsystem can also provide a non-visual display such as audio output devices. In general, use of the term “output device” is intended to include all possible types of devices and ways to output information from computer system 1200 to the user or to another machine or computer system.
Storage subsystem 1210 stores programming and data constructs that provide the functionality of some or all of the modules and methods described herein. Subsystem 1278 can be graphics processing units (GPUs), field-programmable gate arrays (FPGAs), or coarse-grained reconfigurable architectures.
Memory subsystem 1222 used in the storage subsystem 1210 can include a number of memories including a main random access memory (RAM) 1232 for storage of instructions and data during program execution and a read only memory (ROM) 1234 in which fixed instructions are stored. A file storage subsystem 1236 can provide persistent storage for program and data files, and can include a hard disk drive, a floppy disk drive along with associated removable media, a CD-ROM drive, an optical drive, or removable media cartridges. The modules implementing the functionality of certain implementations can be stored by file storage subsystem 1236 in the storage subsystem 1210, or in other machines accessible by the processor.
Bus subsystem 1255 provides a mechanism for letting the various components and subsystems of computer system 1200 communicate with each other as intended. Although bus subsystem 1255 is shown schematically as a single bus, alternative implementations of the bus subsystem can use multiple busses.
Computer system 1200 itself can be of varying types including a personal computer, a portable computer, a workstation, a computer terminal, a network computer, a television, a mainframe, a server farm, a widely-distributed set of loosely networked computers, or any other data processing system or user device. Due to the ever-changing nature of computers and networks, the description of computer system 1200 depicted in
Particular Implementations
In one implementation, we disclose a computer-implemented method of detecting and preventing phishing attacks.
A network security system intercepts a webpage rendered by a server in response to a user action executed on a client. The network security system analyzes one or more images of the webpage and determines that a particular hosted service is represented by the images. The webpage is accompanied with a valid domain and certificate issued by the particular hosted service and impersonates one or more official webpages of the particular hosted service.
The network security system analyzes one or more fields of the webpage and determines that the fields elicit confidential information. The network security system intercepts a request generated by the client in response to another user action providing the confidential information via the fields.
The network security system analyses the request and determines that the confidential information is being exfiltrated to an unsanctioned resource. This determination is made by comparing a resource address in the request with one or more sanctioned resource addresses used by the particular hosted service.
The network security system determines that the webpage is effectuating a phishing attack and blocks transmission of the confidential information to the unsanctioned resource.
The method described in this section and other sections of the technology disclosed can include one or more of the following features and/or features described in connection with additional methods disclosed. In the interest of conciseness, the combinations of features disclosed in this application are not individually enumerated and are not repeated with each base set of features. The reader will understand how features identified in these implementations can readily be combined with sets of base features identified in other implementations.
The particular hosted service can be a cloud computing and storage service and the webpage can be hosted on the cloud computing and storage service. The webpage can have a uniform resource locator (URL) of the cloud computing and storage service that is different from one or more official URLs of the particular hosted service.
The particular hosted service can be a website. The network security system can be configured with an image classifier that is trained to map webpage images to hosted services. In one implementation, the image classifier is a convolutional neural network (CNN).
The sanctioned resource addresses used by the particular hosted service can be identified in a metadata store maintained at the network security system. The sanctioned resource addresses can be identified by at least one of domain names, subdomain names, uniform resource identifiers (URIs), and URLs. The sanctioned resource addresses can be identified by at least one of Internet Protocol (IP) addresses, server name indications (SNIs), and subject alternative names (SANs).
The request can include a Hypertext Transfer Protocol (HTTP) header and the resource address can be identified in a POST field of the HTTP header. The request can include a HTTP header and the resource address can be identified in a referer field of the HTTP header.
The fields that elicit confidential information can be username and password authentication fields, PHI fields, and/or PCI fields.
Other implementations of the method described in this section can include a non-transitory computer readable storage medium storing instructions executable by a processor to perform any of the methods described above. Yet another implementation of the method described in this section can include a system including memory and one or more processors operable to execute instructions, stored in the memory, to perform any of the methods described above.
In another implementation, we disclose a computer-implemented method of detecting and preventing phishing attacks.
An endpoint security system intercepts a webpage rendered by a server in response to a user action executed on a client. The endpoint security system analyzes one or more images of the webpage and determines that a particular hosted service is represented by the images. The webpage is accompanied with a valid domain and certificate issued by the particular hosted service and impersonates one or more official webpages of the particular hosted service.
The endpoint security system analyzes one or more fields of the webpage and determines that the fields elicit confidential information. The endpoint security system intercepts a request generated by the client in response to another user action providing the confidential information via the fields.
The endpoint security system analyses the request and determines that the confidential information is being exfiltrated to an unsanctioned resource. This determination is made by comparing a resource address in the request with one or more sanctioned resource addresses used by the particular hosted service.
The endpoint security system determines that the webpage is effectuating a phishing attack and blocks transmission of the confidential information to the unsanctioned resource.
The method described in this section and other sections of the technology disclosed can include one or more of the following features and/or features described in connection with additional methods disclosed. In the interest of conciseness, the combinations of features disclosed in this application are not individually enumerated and are not repeated with each base set of features. The reader will understand how features identified in these implementations can readily be combined with sets of base features identified in other implementations.
The particular hosted service can be a cloud computing and storage service and the webpage can be hosted on the cloud computing and storage service. The webpage can have a uniform resource locator (URL) of the cloud computing and storage service that is different from one or more official URLs of the particular hosted service.
The particular hosted service can be a website. The endpoint security system can be configured with an image classifier that is trained to map webpage images to hosted services. In one implementation, the image classifier is a convolutional neural network (CNN).
The sanctioned resource addresses used by the particular hosted service can be identified in a metadata store maintained at the endpoint security system. The sanctioned resource addresses can be identified by at least one of domain names, subdomain names, uniform resource identifiers (URIs), and URLs. The sanctioned resource addresses can be identified by at least one of Internet Protocol (IP) addresses, server name indications (SNIs), and subject alternative names (SANs).
The request can include a Hypertext Transfer Protocol (HTTP) header and the resource address can be identified in a POST field of the HTTP header. The request can include a HTTP header and the resource address can be identified in a referer field of the HTTP header.
The fields that elicit confidential information can be username and password authentication fields, PHI fields, and/or PCI fields.
Other implementations of the method described in this section can include a non-transitory computer readable storage medium storing instructions executable by a processor to perform any of the methods described above. Yet another implementation of the method described in this section can include a system including memory and one or more processors operable to execute instructions, stored in the memory, to perform any of the methods described above.
Clauses
We disclose the following clauses:
The method described in this section and other sections of the technology disclosed can include one or more of the following features and/or features described in connection with additional methods disclosed. In the interest of conciseness, the combinations of features disclosed in this application are not individually enumerated and are not repeated with each base set of features. The reader will understand how features identified in these implementations can readily be combined with sets of base features identified in other implementations.
Other implementations of the method described in this section can include a non-transitory computer readable storage medium storing instructions executable by a processor to perform any of the methods described above. Yet another implementation of the method described in this section can include a system including memory and one or more processors operable to execute instructions, stored in the memory, to perform any of the methods described above.
While the technology disclosed is disclosed by reference to the preferred embodiments and examples detailed above, it is to be understood that these examples are intended in an illustrative rather than in a limiting sense. It is contemplated that modifications and combinations will readily occur to those skilled in the art, which modifications and combinations will be within the spirit of the innovation and the scope of the following claims.
This application claims the benefit of and priority to Provisional Patent Application No. 62/966,412, titled “METADATA-BASED DETECTION AND PREVENTION OF PHISHING ATTACKS,” filed on Jan. 27, 2020. The provisional application is incorporated by reference as if fully set forth herein.
Number | Name | Date | Kind |
---|---|---|---|
4574346 | Hartung | Mar 1986 | A |
5452460 | Distelberg et al. | Sep 1995 | A |
6502192 | Nguyen | Dec 2002 | B1 |
6574655 | Libert et al. | Jun 2003 | B1 |
6687732 | Bector et al. | Feb 2004 | B1 |
6829654 | Jungck | Dec 2004 | B1 |
6898636 | Adams et al. | May 2005 | B1 |
6981155 | Lyle et al. | Dec 2005 | B1 |
7231426 | Hall et al. | Jun 2007 | B1 |
7234168 | Gupta et al. | Jun 2007 | B2 |
7296058 | Throop | Nov 2007 | B2 |
7475146 | Bazot et al. | Jan 2009 | B2 |
7536439 | Jaladanki et al. | May 2009 | B1 |
7587499 | Haghpassand | Sep 2009 | B1 |
7769994 | Peles | Aug 2010 | B2 |
7908472 | Freed et al. | Mar 2011 | B2 |
7996373 | Zoppas et al. | Aug 2011 | B1 |
8280986 | Deprun | Oct 2012 | B2 |
8281372 | Vidal | Oct 2012 | B1 |
8346580 | Nakfoor | Jan 2013 | B2 |
8363650 | Rao et al. | Jan 2013 | B2 |
8365243 | Lu et al. | Jan 2013 | B1 |
8544060 | Khetawat | Sep 2013 | B1 |
8549300 | Kumar et al. | Oct 2013 | B1 |
8566932 | Hotta et al. | Oct 2013 | B1 |
8572758 | Clifford | Oct 2013 | B1 |
8613040 | Barile | Dec 2013 | B2 |
8640216 | Anderson et al. | Jan 2014 | B2 |
8677448 | Kauffman et al. | Mar 2014 | B1 |
8763072 | Agrawal | Jun 2014 | B2 |
8856869 | Brinskelle | Oct 2014 | B1 |
8892665 | Rostami-Hesarsorkh et al. | Nov 2014 | B1 |
8914461 | Murai | Dec 2014 | B2 |
8914892 | Karande et al. | Dec 2014 | B2 |
8925069 | Louboutin et al. | Dec 2014 | B2 |
8959329 | Altman | Feb 2015 | B2 |
9069436 | Fieweger et al. | Jun 2015 | B1 |
9069955 | Dolph et al. | Jun 2015 | B2 |
9069992 | Vaikar et al. | Jun 2015 | B1 |
9122869 | Sobel et al. | Sep 2015 | B1 |
9137131 | Sarukkai et al. | Sep 2015 | B1 |
9185088 | Bowen | Nov 2015 | B1 |
9197628 | Hastings | Nov 2015 | B1 |
9230096 | Sarin et al. | Jan 2016 | B2 |
9246944 | Chen | Jan 2016 | B1 |
9246948 | Jaiswal et al. | Jan 2016 | B2 |
9256727 | Manmohan | Feb 2016 | B1 |
9270765 | Narayanaswamy et al. | Feb 2016 | B2 |
9398102 | Narayanaswamy et al. | Jul 2016 | B2 |
9405904 | Fang et al. | Aug 2016 | B1 |
9418232 | Khetawat et al. | Aug 2016 | B1 |
9438506 | Ryland | Sep 2016 | B2 |
9460179 | Gunaratne et al. | Oct 2016 | B1 |
9537884 | Raugas et al. | Jan 2017 | B1 |
9553860 | Meyer | Jan 2017 | B2 |
9626528 | Butler | Apr 2017 | B2 |
9692759 | Chandrasekhar | Jun 2017 | B1 |
9917817 | Lad et al. | Mar 2018 | B1 |
9928377 | Narayanaswamy et al. | Mar 2018 | B2 |
9998496 | Narayanaswamy et al. | Jun 2018 | B2 |
10142362 | Weith et al. | Nov 2018 | B2 |
10162767 | Spurlock et al. | Dec 2018 | B2 |
10178120 | Keegan et al. | Jan 2019 | B1 |
10248797 | Shinde et al. | Apr 2019 | B1 |
10277625 | Efstathopoulos et al. | Apr 2019 | B1 |
10291651 | Chaubey | May 2019 | B1 |
10291657 | Narayanaswamy et al. | May 2019 | B2 |
10404755 | Narayanaswamy et al. | Sep 2019 | B2 |
10404756 | Narayanaswamy et al. | Sep 2019 | B2 |
10440036 | Pal et al. | Oct 2019 | B2 |
10454933 | Chenard et al. | Oct 2019 | B2 |
10491638 | Narayanaswamy et al. | Nov 2019 | B2 |
10757090 | Kahol et al. | Aug 2020 | B2 |
10764313 | Mushtaq | Sep 2020 | B1 |
10812531 | Narayanaswamy et al. | Oct 2020 | B2 |
10826940 | Narayanaswamy et al. | Nov 2020 | B2 |
10855671 | Kahol et al. | Dec 2020 | B2 |
10860730 | Weaver et al. | Dec 2020 | B1 |
10862916 | Hittel et al. | Dec 2020 | B2 |
10979458 | Narayanaswamy et al. | Apr 2021 | B2 |
11019101 | Narayanaswamy et al. | May 2021 | B2 |
11064013 | Cheng et al. | Jul 2021 | B2 |
11089064 | Sarukkai et al. | Aug 2021 | B1 |
20010011238 | Eberhard et al. | Aug 2001 | A1 |
20010054157 | Fukumoto | Dec 2001 | A1 |
20020016773 | Ohkuma et al. | Feb 2002 | A1 |
20020091532 | Viets et al. | Jul 2002 | A1 |
20020138593 | Novak et al. | Sep 2002 | A1 |
20030191989 | OSullivan | Oct 2003 | A1 |
20040001443 | Soon et al. | Jan 2004 | A1 |
20040088423 | Miller et al. | May 2004 | A1 |
20040122977 | Moran et al. | Jun 2004 | A1 |
20040128538 | Gmuender et al. | Jul 2004 | A1 |
20040268451 | Robbin et al. | Dec 2004 | A1 |
20050086197 | Boubez et al. | Apr 2005 | A1 |
20050251856 | Araujo et al. | Nov 2005 | A1 |
20060248045 | Toledano et al. | Nov 2006 | A1 |
20070006293 | Balakrishnan et al. | Jan 2007 | A1 |
20070011319 | McClure et al. | Jan 2007 | A1 |
20070220251 | Rosenberg et al. | Sep 2007 | A1 |
20070289006 | Ramachandran et al. | Dec 2007 | A1 |
20080034418 | Venkatraman et al. | Feb 2008 | A1 |
20080127303 | Wrighton et al. | May 2008 | A1 |
20080189778 | Rowley | Aug 2008 | A1 |
20080229428 | Camiel | Sep 2008 | A1 |
20080250390 | Feblowitz et al. | Oct 2008 | A1 |
20080263215 | Schnellbaecher | Oct 2008 | A1 |
20080301231 | Mehta et al. | Dec 2008 | A1 |
20090100077 | Jung et al. | Apr 2009 | A1 |
20090225762 | Davidson et al. | Sep 2009 | A1 |
20090328188 | Raymer et al. | Dec 2009 | A1 |
20100024008 | Hopen et al. | Jan 2010 | A1 |
20100146260 | Levow et al. | Jun 2010 | A1 |
20100146269 | Baskaran | Jun 2010 | A1 |
20100169472 | Okamoto et al. | Jul 2010 | A1 |
20100188975 | Raleigh | Jul 2010 | A1 |
20100251369 | Grant | Sep 2010 | A1 |
20100287613 | Singh et al. | Nov 2010 | A1 |
20100325287 | Jagadeeswaran et al. | Dec 2010 | A1 |
20110016197 | Shiimori et al. | Jan 2011 | A1 |
20110154506 | Osullivan et al. | Jun 2011 | A1 |
20110196914 | Tribbett | Aug 2011 | A1 |
20110247045 | Rajagopal et al. | Oct 2011 | A1 |
20110321170 | Onodera et al. | Dec 2011 | A1 |
20120008786 | Cronk et al. | Jan 2012 | A1 |
20120020307 | Henderson et al. | Jan 2012 | A1 |
20120042361 | Wong et al. | Feb 2012 | A1 |
20120237908 | Fitzgerald et al. | Sep 2012 | A1 |
20120278872 | Woelfel et al. | Nov 2012 | A1 |
20130145483 | Dimuro et al. | Jun 2013 | A1 |
20130191627 | Ylonen et al. | Jul 2013 | A1 |
20130268677 | Marshall et al. | Oct 2013 | A1 |
20130298192 | Kumar et al. | Nov 2013 | A1 |
20130347085 | Hawthorn et al. | Dec 2013 | A1 |
20140007182 | Qureshi et al. | Jan 2014 | A1 |
20140007222 | Qureshi et al. | Jan 2014 | A1 |
20140026182 | Pearl et al. | Jan 2014 | A1 |
20140032691 | Barton et al. | Jan 2014 | A1 |
20140053280 | Durazzo et al. | Feb 2014 | A1 |
20140082204 | Shankar et al. | Mar 2014 | A1 |
20140115702 | Li et al. | Apr 2014 | A1 |
20140165148 | Dabbiere et al. | Jun 2014 | A1 |
20140165213 | Stuntebeck | Jun 2014 | A1 |
20140181971 | Tatarinov et al. | Jun 2014 | A1 |
20140245381 | Stuntebeck et al. | Aug 2014 | A1 |
20140259190 | Kiang et al. | Sep 2014 | A1 |
20140269279 | Ismail et al. | Sep 2014 | A1 |
20140310392 | Ho | Oct 2014 | A1 |
20140317681 | Shende | Oct 2014 | A1 |
20140337862 | Valencia et al. | Nov 2014 | A1 |
20140344573 | Tsai et al. | Nov 2014 | A1 |
20140380491 | Abuelsaad et al. | Dec 2014 | A1 |
20150074744 | McLean et al. | Mar 2015 | A1 |
20150088791 | Lin et al. | Mar 2015 | A1 |
20150113264 | Wang et al. | Apr 2015 | A1 |
20150135302 | Cohen et al. | May 2015 | A1 |
20150200924 | Parla et al. | Jul 2015 | A1 |
20150205973 | Huh et al. | Jul 2015 | A1 |
20150254469 | Butler | Sep 2015 | A1 |
20150271207 | Jaiswal et al. | Sep 2015 | A1 |
20150319156 | Guccione et al. | Nov 2015 | A1 |
20150347447 | Ho et al. | Dec 2015 | A1 |
20160087970 | Kahol et al. | Mar 2016 | A1 |
20160134653 | Vallone et al. | May 2016 | A1 |
20160188880 | Smith et al. | Jun 2016 | A1 |
20160241528 | Kulkarni et al. | Aug 2016 | A1 |
20160253352 | Kluck et al. | Sep 2016 | A1 |
20160269467 | Lee et al. | Sep 2016 | A1 |
20160275577 | Kolluri Venkata Sesha et al. | Sep 2016 | A1 |
20160277374 | Reid et al. | Sep 2016 | A1 |
20160292445 | Lindemann | Oct 2016 | A1 |
20160306980 | Kotler et al. | Oct 2016 | A1 |
20160330219 | Hasan | Nov 2016 | A1 |
20160350539 | Oberheide et al. | Dec 2016 | A1 |
20170063720 | Foskett et al. | Mar 2017 | A1 |
20170063886 | Muddu et al. | Mar 2017 | A1 |
20170078323 | Ross | Mar 2017 | A1 |
20170091482 | Sarin et al. | Mar 2017 | A1 |
20170195427 | Choquette et al. | Jul 2017 | A1 |
20170201537 | Caldwell et al. | Jul 2017 | A1 |
20170206353 | Jai et al. | Jul 2017 | A1 |
20170213037 | Toledano et al. | Jul 2017 | A1 |
20170223054 | Wing et al. | Aug 2017 | A1 |
20170251013 | Kirti et al. | Aug 2017 | A1 |
20170251370 | Liljenstam et al. | Aug 2017 | A1 |
20170286229 | Cheung | Oct 2017 | A1 |
20170286690 | Chari et al. | Oct 2017 | A1 |
20170302685 | Ladnai et al. | Oct 2017 | A1 |
20170353496 | Pai et al. | Dec 2017 | A1 |
20180020018 | Walheim et al. | Jan 2018 | A1 |
20180048668 | Gupta et al. | Feb 2018 | A1 |
20180048669 | Lokamathe et al. | Feb 2018 | A1 |
20180146004 | Belfiore et al. | May 2018 | A1 |
20180181761 | Sinha et al. | Jun 2018 | A1 |
20180190146 | Bodnarium | Jul 2018 | A1 |
20180191727 | Baldwin et al. | Jul 2018 | A1 |
20180239902 | Godard et al. | Aug 2018 | A1 |
20180248896 | Challita et al. | Aug 2018 | A1 |
20180262348 | Golshan et al. | Sep 2018 | A1 |
20180324204 | McClory et al. | Nov 2018 | A1 |
20190200282 | Sahin et al. | Jun 2019 | A1 |
20190327268 | Goutal | Oct 2019 | A1 |
20200128022 | Bleikertz et al. | Apr 2020 | A1 |
20200311265 | Jones | Oct 2020 | A1 |
20200372040 | Boehmann et al. | Nov 2020 | A1 |
20210099485 | Lancioni | Apr 2021 | A1 |
20210144174 | N | May 2021 | A1 |
20210367976 | Khurshid et al. | Nov 2021 | A1 |
Number | Date | Country |
---|---|---|
111147490 | May 2020 | CN |
2011234178 | Nov 2011 | JP |
201284141 | Apr 2012 | JP |
101622874 | May 2016 | KR |
2005069823 | Aug 2005 | WO |
WO-2009111224 | Sep 2009 | WO |
2014093613 | Jun 2014 | WO |
Entry |
---|
Cheng et al., “Cloud Security for Dummies, Netskope Special Edition” John Wiley & Sons, Inc. 2015, 53 pages. |
“Data Loss Prevention and Monitoring in the Cloud” by netSkope, Inc., Nov. 2014, 18 pgs. |
“Repave the Cloud-Data Breach Collision Course,” netSkope, Inc., 2014, 6 pgs. |
“Netskope Cloud Confidence Index™”, netSkope, Inc., 2015, 4 pages. |
“The 5 Steps to Cloud Confidence”, netSkope, Inc., 2014, 11 pages. |
“Netskope Active Cloud DLP,” netSkope, Inc., 2015, 4 pgs. |
Screen capture of https://www.bitglass.com/blog/how-topatent-a-phishing-attack, dated Oct. 1, 2015. |
PTAB Case No. PGR2021-00091, Petition for Post-Grant Review of U.S. Pat. No. 10,855,671, Netskope, Inc., Petitioner, v. Bitglass, Inc., Patent Owner. |
PTAB Case No. PGR2021-00092, Petition for Post-Grant Review of U.S. Pat. No. 10,855,671, Netskope, Inc., Petitioner, v. Bitglass, Inc., Patent Owner. |
Jill Gemmill et al., Cross-domain authorization for feder-ated virtual organizations using the myVocs collaboration environment, 21 Concurrency & Computation: Prac-Tice and Experience 509 (2008). |
PTAB Case No. IPR2021-01045, Petition for Inter Partes Review of U.S. Pat. No. 10,757,090, Netskope, Inc., Petitioner, v. Bitglass, Inc., Patent Owner. |
PTAB Case No. IPR2021-01046, Petition for Inter Partes Review of U.S. Pat. No. 10,757,090, Netskope, Inc., Petitioner, v. Bitglass, Inc., Patent Owner. |
“Cloud Data Loss Prevention Reference Architecture”, Netskope, Sep. 2015, WP-88-1, 2 pages. |
“Data Breach: The Cloud Multiplier Effect”, Ponemon Institute, Jun. 4, 2014, 27 pages. |
“Netskope Introspection,” netSkope, Inc., 2015, 3 pgs. |
“Netskope The 15 Critical CASB Use Cases”, Netskope Inc., EB-141-1, dated 2015, 19 pages. |
“The Netskope Active Platform Enabling Safe Migration to the Cloud”, Apr. 2015, DS-1-8, Netskope, Inc., 6 pages. |
“The Netskope Advantage: Three “Must-Have” Requirements for Cloud Access Security Brokers”, Jul. 2015, WP-12-2 1 pages. |
Anonymous, Installing Box Sync, Box, retrieved on Feb. 6, 2019, 13 pages. Retrieved from the internet [URL: hllps://community.box.com/t5/Using-Box-Sync/Installing-Box-Sync/ta-p/85]. |
Daigneau, Service Design Patterns—Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services, Derason Education, dated 2012, 60 pages. |
EP 14761047.1—Extended Search Report dated Aug. 4, 2016, 7 pages {NSKO 1000-5 EP). |
EP 14761047.1—Notice of Allowance dated Jun. 1, 2018, 45 pages (NSKO 1000-5 EP). |
EP 14761047.1—Response to Extended Search Report dated Aug. 4, 2016 filed Feb. 28, 2017, 10 pages NSKO 1000-5 EP). |
EP 18199916.0—Extended European Search Report dated Feb. 14, 2019, 8 pages {NSKO-1000-10). |
EP 18199916.0—Response to Extended European Search Report dated Feb. 14, 2019, as filed Sep. 20, 2019, 12 pages {NSKO-1000-10). |
Kark et al., “Trends: Calculating the Cost of a Security Breach”, Forrester Research, Inc. Apr. 10, 2007, 7 pgs. |
Liu et al., Data Loss Prevention, IT Professional, vol. 12, Issue 2, IEEE, Mar. 29, 2010, pp. 10-13. |
Masse, Rest API—Design Rulebook, O'Reilly publication, dated 2012, 114 pages. |
Netskope, “Data Loss Prevention and Monitoring in the Cloud”, Nov. 2014, 18 pages, {NSKO 1006 2). |
Netskope, “The 5 Steps to Cloud Confidence”, Version 2, Jan. 29, 2014, 10 pages. |
Netskope, “The 5 Steps to Cloud Confidence,” netSkope Inc., 2014, 11 pgs. |
Nllamaraju, RESTful Web Services Cookbook, O'Reilly Publication, dated Mar. 2010, 314 pages. |
Oasis, Key Management Interoperability Protocols Use Cases Version 1.2, dated Mar. 18, 2013, 132 pages. |
Pandire et al., Attack Detection in Cloud Virtual Environment and Prevention using Honeypot, International Conference in Inventive Research in Computing Applications {ICIRCA), IEEE, Jul. 11-12, 2018, pp. 515-520. |
Park et al., Derwent translation of KR 101622874 B1; May 19, 2016, 35 pages. (Year: 2016). |
PCT/US2014/21174—International Preliminary Report on Patentabilily, dated Sep. 8, 2015, 10 pages {NSKO 1000-4). |
PCT/US2014/21174—International Search Report and Written Opinion, dated Aug. 29, 2014, 13 pages {NSKO 1000-4). |
Richardson et al., RESTful Web APIs, O'Reilly Publication, dated Sep. 2013, 404 pages. |
Richardson et al., RESTful Web Services, O'Reilly Publication, dated May 2007, 448 pages. |
Zhu, Xiaojin Jerry. “Semi-supervised learning literature survey.” (2005). (Year: 2005), 39 pages. |
EP 19727564.7 Rules 161(1) and 162 Communication, dated Jan. 15, 2021, 3 pages. (NSKO 1019-6), Jan. 15, 2021. |
Eastlake, D., “RFC-6066-Standard”, Internet Engineering Task Force (IETF), Jan. 2011, 25 pages. (NSKO I007-1), Jan. 2011. |
Khanuja Harmeet et al: “Role of metadata in forensic analysis of database attack”, 2014 IEEE International Advance Computing Conference (IACC), IEEE, Feb. 21, 2014 (Feb. 21, 2014), pp. 457-462., Feb. 21, 2014. |
U.S. Appl. No. 15/958,672—Notice of Allowance dated Feb. 24, 2020, 26 pages {NSKO 1007-2)., dated Feb. 24, 2020. |
U.S. Appl. No. 15/958,637—Preinterview First Office Action dated Mar. 2, 2020, (NSKO I 008-1). 7 pages, dated Mar. 2, 2020. |
U.S. Appl. No. 15/958,637—Response to Preinterview First Office Action dated Mar. 2, 2020, filed Apr. 2, 2020, (NSKO 1008-1). 19 pages, dated Apr. 10, 2020. |
Wikipedia, “Traffic Server”, [retrieved on Apr. 13, 2018]. Retrieved from the Internet <URL: https://en.wikipedia.org/wiki/Traffic_Server> (NSKO 1008-1), 1 page, Apr. 13, 2018. |
Wikipedia, “HTTPS”, [retrieved on Apr. 17, 2018]. Retrpieved from the Internet <URL: <https://en.wikipedia.org/w/index.php?title=HTTP S&oldid=836835625>. (NSKO 1007-2) 8 pages, Apr. 17, 2018. |
Wikipedia, “List of HTTP header fields”, [retrieved on Apr. 17, 2018]. Retrieved from the Internet <URL: <“https://en.wikipedia.org/w/index.php?title=List_of HTTP header fields&oldid=83686420”2>. 7 pages—(NSKO 1007-2), Apr. 17, 2018. |
JP 2019-081108 Response to First Office Action dated May 18, 2021, filed Sep. 21, 2021, 13 pages (NSKO 1003-9)., May 18, 2021. |
Symantec, Symantec Data Loss Prevention for Endpoint, dated May 2011, 3 pages, May 2011. |
McAfee, McAfee Data Loss Prevention Endpoint, dated May 2017, 3 pages, May 2017. |
U.S. Appl. No. 15/958,672—Notice of Allowance dated Jun. 9, 2020, 25 pages (NSKO 1007-2)., Jun. 9, 2020. |
U.S. Appl. No. 15/958,637—Notice of Allowance dated Jun. 17, 2020, 10 pages (NSKO 1008-1)., Jun. 17, 2020. |
Blake-Wilson, S., et al., “RFC-3546-Standard”, Network Working Group, The Internet Society, Jun. 2003, 29pgs. (NSKO 1007-2), Jun. 2003. |
Fielding, R, “Hypertext Transfer Protocol (HTTP/I.1): Message Syntax and Routing”, Internet Engineering Task Force, Jun. 2014, 89 pages. (NSKO 1007-2), Jun. 2014. |
Fielding, R., “Hypertext Transfer Protocol (HTTP/I.I): Semantics and Content”, Internet Engineering Task Force, Jun. 2014, 101 pages. (NSKO 1007-2), Jun. 2014. |
U.S. Appl. No. 16/411,039—Response to Office Action dated Feb. 10, 2021, filed Jul. 9, 2021, 18 pages {NSKO 1029-1)., Jul. 9, 2021. |
European Search Report issued in EP Application No. 21191734.9, dated Jul. 12, 2022, 7 pages, Jul. 12, 2022. |
EP 19727564.7 Response to Rules 161(1) and 162 Communication dated Jan. 15, 2021, filed Jul. 26, 2021, 12 pages. (NSKO 1019-6), dated Jul. 26, 2021. |
EP 17713822.9 Decision to Grant, dated Aug. 1, 2019, 2 pages (NSKO 1003-7)., dated Aug. 1, 2019. |
Heckel, “Use SSLsplit to transparently sniff TLS/SSL connections—including non-HTTP(S) protocols”, Blog post Aug. 4, 2013, 28 pages (NSKO 1008-1)., Aug. 4, 2013. |
EP 19189235.5 Certificate of Grant, dated Aug. 31, 2021, 1 pages. (NSKO 1003-10). |
U.S. Appl. No. 16/408,215 Preinterview First Office Action dated Sep. 23, 2021, 21 pgs. (NSKO 1019-2), dated Sep. 23, 2021. |
U.S. Appl. No. 16/411,039—Office Action dated Oct. 21, 2021, 37 pages (NSKO 1029-1)., dated Oct. 21, 2021. |
U.S. Appl. No. 16/738,964—Notice of Allowance dated Oct. 23, 2020, 38 pages (NSKO 1007-3)., dated Oct. 23, 2020. |
JP 2019-081108 Notice of Allowance, dated Oct. 26, 2021, 5 pages. (NSKO 1003-9), dated Oct. 26, 2021. |
Bremler-Barr, Anat Et Al:“Deep Packet Inspection as a Service”, Proceedings of The 10th ACM International on Conference on Emerging Networking Experiments and Technologies, CONEXT '14, ACM Press, New York, NY, USA, Dec. 2, 2014 (Dec. 2, 2014), pp. 271-282., Dec. 2, 2014. |
Li el. al., Security Intelligence—A Practitioner's Guide to Solving Enterprise Security Challenges, Wiley, dated 2015, 363 pages, 2015. |
Number | Date | Country | |
---|---|---|---|
20210234892 A1 | Jul 2021 | US |
Number | Date | Country | |
---|---|---|---|
62966412 | Jan 2020 | US |