会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 14. 发明申请
    • Embedded Firewall at a Telecommunications Endpoint
    • 嵌入式防火墙在电信端点
    • US20080148384A1
    • 2008-06-19
    • US11610485
    • 2006-12-13
    • Akshay AdhikariSachin GargAnjur Sundaresan KrishnakumarNavjot Singh
    • Akshay AdhikariSachin GargAnjur Sundaresan KrishnakumarNavjot Singh
    • G06F17/00
    • H04L63/0209H04L63/0263
    • A method is disclosed that enables the implementation of an embedded firewall at a telecommunications endpoint. In particular, the illustrative embodiment of the present invention addresses the relationship between the application, firewall engine, and packet-classification rules database that are all resident at the endpoint. In the variations of the illustrative embodiment that are described herein, the application: (i) directly communicates with the co-resident firewall engine such as through local message passing, (ii) shares memory with the firewall engine, and (iii) makes socket calls to the operating system that are intercepted by a middleware layer that subsequently modifies the rules database, depending on the socket call. The common thread to these techniques is that the application, firewall engine, and rules database are co-resident at the endpoint, which is advantageous in the implementation of the embedded firewall.
    • 公开了一种能够在电信端点实现嵌入式防火墙的方法。 特别地,本发明的说明性实施例解决了所有驻留在端点的应用,防火墙引擎和分组分类规则数据库之间的关系。 在本文描述的说明性实施例的变型中,应用:(i)直接与共驻防火墙引擎通信,例如通过本地消息传递,(ii)与防火墙引擎共享存储器,以及(iii)使套接字 调用由中间件层拦截的操作系统,随后根据套接字调用修改规则数据库。 这些技术的共同点是应用程序,防火墙引擎和规则数据库共同驻留在端点,这在嵌入式防火墙的实现方面是有利的。
    • 16. 发明申请
    • Security vulnerability monitor
    • 安全漏洞监控
    • US20050005152A1
    • 2005-01-06
    • US10611264
    • 2003-07-01
    • Navjot SinghTimothy Tsai
    • Navjot SinghTimothy Tsai
    • G06F21/00H04L9/00
    • G06F21/577G06F21/554
    • A method and apparatus for automatically determining whether a security vulnerability alert is relevant to a device (e.g., personal computer, server, personal digital assistant [PDA], etc.), and automatically retrieving the associated software patches for relevant alerts, are disclosed. The illustrative embodiment intelligently determines whether the software application specified by a security vulnerability alert is resident on the device, whether the version of the software application on the device matches that of the security vulnerability alert, and whether the device's hardware platform and operating system match those of the security vulnerability alert.
    • 公开了一种用于自动确定安全漏洞警报是否与设备(例如,个人计算机,服务器,个人数字助理[PDA]等)相关的方法和装置,以及自动检索相关警报的相关软件补丁。 说明性实施例智能地确定由安全漏洞警报指定的软件应用程序是否驻留在设备上,设备上的软件应用程序的版本是否与安全漏洞警报的版本相匹配,以及设备的硬件平台和操作系统是否匹配 的安全漏洞警报。
    • 19. 发明授权
    • Method and apparatus for transparently directing requests for web objects to proxy caches
    • US06389462B1
    • 2002-05-14
    • US09212980
    • 1998-12-16
    • Ariel CohenSampath RangarajanNavjot Singh
    • Ariel CohenSampath RangarajanNavjot Singh
    • G06F1516
    • H04L67/2804H04L29/06H04L29/12009H04L61/00H04L67/1002H04L67/1017H04L67/1019H04L67/1027H04L67/2814H04L69/16H04L69/161H04L69/165H04L69/166
    • In order to transparently redirect an HTTP connection request that is directed to an origin server (107) to a proxy cache (110-1), a proxy redirector (104) translates the destination address of packets directed to the origin server to the address of the proxy. During a handshaking procedure, a TCP connection is transparently established between the client (110-1) and the proxy cache. When the client transmits a GET request to what it thinks is the origin server, which request specifies the complete address of an object at that origin server that it wants a copy of, the proxy redirector modifies the complete address specified in that GET request before it is sent to the proxy cache. Specifically, the IP address of the origin server found in the destination field in the IP header of the one or more packets from the client containing the GET request is added by the proxy redirector as a prefix to the complete URL in the GET request to form an absolute URL. The proxy cache determines from that absolute URL whether it has the requested object stored in its cache. If it does, it sends the object back to the proxy redirector, which masquerades those packets as coming from the origin server by translating their destination address to the address of the client and their source address to that of the origin server. If the proxy does not have the requested object, a separate TCP connection is established between the proxy and the origin server from where the object is retrieved and then forwarded over the TCP connection between the client and the proxy. In order to account for the additional number of bytes in the GET request, an acknowledgement sequence number in packets returned from the proxy that logically follow receipt of the GET request are decremented by that number by the proxy redirector before being forwarded to the client. Similarly, a sequence number in packets transmitted by the client subsequent to the GET request are incremented by that number before being forwarded by the proxy redirector to the proxy cache.