Proxy (statistics)

About: Proxy (statistics) is a research topic. Over the lifetime, 5257 publications have been published within this topic receiving 94504 citations. The topic is also known as: proxy variable & proxy measurement.

Creating proxies from service description metadata at runtime

Abstract: The present invention extends to methods, systems, and computer program products for creating proxies from service description metadata at runtime. A proxy creation request is received from a requesting application while the requesting application is executing at runtime. The proxy creation request requests creation of a proxy instance to facilitate compatible communication between the requesting application and another application. A proxy instance is created in response to the proxy creation request. Service description metadata describing the other application is accessed (e.g., through a request to a metadata service or retrieval from cache). The proxy instance is configured in accordance with the service description metadata describing the other application. Accordingly, the proxy instance can facilitate compatible communication between the requesting application and the other application to implement operations that the requesting application requests to be performed at the other application.

Empirical study of tolerating denial-of-service attacks with a proxy network

Abstract: Proxy networks have been proposed to protect applications from Denial-of-Service (DoS) attacks However, since large-scale study in real networks is infeasible and most previous simulations have failed to capture detailed network behavior, the DoS resilience and performance implications of such use are not well understood in large networks While post-mortems of actual large-scale attacks are useful, only limited dynamic behavior can be understood from these single instances Our work provides the first detailed and broad study of this problem in large-scale realistic networks The key is that we use an online network simulator to simulate a realistic large-scale network (comparable to several large ISPs) We use a generic proxy network, and deploy it in a large simulated network using typical real applications and DoS tools directly We study detailed system dynamics under various attack scenarios and proxy network configurations Specific results are as follows First, rather than incurring a performance penalty, proxy networks can improve users' experienced performance Second, proxy networks can effectively mitigate the impact of both spread and concentrated large-scale DoS attacks in large networks Third, proxy networks provide scalable DoS-resilience - resilience can be scaled up to meet the size of the attack, enabling application performance to be protected Resilience increases almost linearly with the size of a proxy network; that is, the attack traffic that a given proxy network can resist, while preserving a particular level of application performance, grows almost linearly with proxy network size These results provide empirical evidence that proxy networks can be used to tolerate DoS attacks and quantitative guidelines for designing a proxy network to meet a resilience goal

Limitations and potential of country of birth as proxy for ethnic group.

Abstract: EDITOR—We agree with Jarman and Aylin that recording of ethnic group on death certificates needs to be improved in the United Kingdom.1 Currently, country of birth has been included in each UK census since 1841 and is a readily available and objective, although crude, method of ethnic group classification.2 Indeed it remains a good proxy for ethnic group for …

On the Reliability of Coverage-Based Fuzzer Benchmarking

Abstract: Given a program where none of our fuzzers finds any bugs, how do we know which fuzzer is better? In practice, we often look to code coverage as a proxy measure of fuzzer effectiveness and consider the fuzzer which achieves more coverage as the better one. Indeed, evaluating 10 fuzzers for 23 hours on 24 programs, we find that a fuzzer that covers more code also finds more bugs. There is a very strong correlation between the coverage achieved and the number of bugs found by a fuzzer. Hence, it might seem reasonable to compare fuzzers in terms of coverage achieved, and from that derive empirical claims about a fuzzer's superiority at finding bugs. Curiously enough, however, we find no strong agreement on which fuzzer is superior if we compared multiple fuzzers in terms of coverage achieved instead of the number of bugs found. The fuzzer best at achieving coverage, may not be best at finding bugs.

Method and system for analysing and filtering https traffic in corporate networks

Abstract: The proxy system according to the present invention, consists of forwarding the content of the HTTPS requests in an unusual way, by automatically generating a new certificate for the requested destination server. This new certificate is faked. It is signed by a corporate internal Certificate Authority (CA). The new certificate is included in the response sent by the proxy to the client during the SSL session establishment (according to the SSL protocol, the destination server, which in this case will be the proxy server, identifies itself using a certificate). The request is then transparently forwarded to the destination server as a normal or standard HTTP Proxy server does. To prevent clients from detecting this "man-in-the middle attack", the internal corporate Certificate Authority (CA) used to sign the "fake" certificates, must be included in the list of Certificates Authorities recognized by the clients in the corporate network.