DOCSLIB.ORG

Webproxy, DNS Hijacking, Layer Seven Level Security Approach: to Protect SAAS from Web Based DDOS and Web Service Based DDOS Attacks in Cloud

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Webproxy, DNS Hijacking, Layer Seven Level Security Approach: to Protect SAAS from Web Based DDOS and Web Service Based DDOS Attacks in Cloud International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 2, February- 2013 Webproxy, DNS Hijacking, Layer Seven Level Security Approach: To Protect SAAS From Web based DDOS and Web Service Based DDOS Attacks In Cloud S.Tamilselvi1, Dr.S.Tamilarasi2,S.Loganathan3 1. M. tech , ISCF, Dr.mgr educational and research institute, chennai 2. Associate Professor, CSE, Dr.mgr educational and research institute, chennai 3.Assistant Professor, ECE, Paavai Engineering College , Namakkal, Tamil Nadu ABSTRACT Cloud services offers platform services, software services, infrastructure services via web services. Cloud computing is an emerging trend in business these type of services increases vulnerability which world. Provide services to its customers on demand, invite attackers. common vulnerabilities are services like Infrastructure services , Platform services , Software services , Network services so Security level attacks: on. Resources are maintained in the virtualIJERT IJERT datacenters for both private and public clouds. Saas 1. Dictionary attacks contains web application services, windows 2. Brute force attacks application services, tools services, console 3. Spoofing application services, third party software services so 4. Credential theft on. In web application services web based distributed 5. Password cracking denial and web services based distributed denial of attack is easily implemented hacker because web Management level attacks: application transmitted through hypertext transfer protocol and web services through XML, WSDL .In 1. Credential theft 2. Elevation of privileges this paper we introduce DNS hijacking security, Web 3. luring proxy implementation, application level security to resolve web based and web services based distributed Infrastructure layer security attacks: denial of service attacks. 1. Side channel attacks KEYWORDS: web application security, web service 2. Tampering security, ddos attacks, DNS hijaking security, web 3. Eves dropping proxy implementation, cgi security. 4. Privilege elevation 5. Physical access 1.INTRODUCTION Platform layer attacks: www.ijert.org 1 International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 2, February- 2013 1. Buffer overflow attacks 1.2 cloud service 2. canonicalization 3. Encryption 4. Tampering 5. Confidential data disclosure 6. SQL injection SERVICE DELIEVERY(SOFTWARE SERVICES,PLATFORM Application layer attacks: SERVICES,INFRASTRUTURE SERVICES) 1. Connection pooling 2. Privilege elevation 3. Open redirect 4. CSRF 5. SQL Injection 6. Buffer over flow attacks STORAGE VIRTUALIZATION 7. Encryption HARDWARE SOFTWARE Client Level attacks: 1. Session modification 2. Cookie manipulation Fig 1.Cloud service 3. Privilege elevation 4. Buffer overflow attacks 1.3 cloud service providers 5. Key loggers 6. Device theft Software services includes web application,SCMsoftware,CRM.software.serviceprov Service delivery level attacks: iders Google apps, Microsoft dynamics, sales force soon. Plat form services includes Application Dev, 1. Cookie replay Middleware, Enterprise portals. Plat form service 2. Ip spoofing IJERTIJERT 3. Dos attacks providers are windows azure, Google App engine, 4. Encryption Force.com. infra structure service includes networking, servers, storage. Infra structure service web based and web service based ddos attack is very includes Amazon web service, Verizon, backspace so dangerous when compare to other attacks. on. 1.1 Software services in cloud 2. RELATED WORK Delivers application to its clients. all the Day to day cloud faces new attacks. This paper back office details of application provided as service. is mainly focusing on web based and web service based DDOS attacks. websites accessed in the internet considered as software services. for example gmail or yahoo mail commonly cloud security focuses on API ,service provides email services. Share point as software hacking, attack on firewall, attack on browser, service online via web browser. confidentiality sign on, authentication problems and integrity, risk profile, data leakage, shared technology vulnerabilities so on. We analyze DDOS attacks and mitigation techniques through online, international journals, corporate solution white papers, international conference papers. According to the literature survey web application crashes under DDOS attacks in few minutes. Private and public www.ijert.org 2 International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 2, February- 2013 clouds are affected by Denial attacks in few minutes. Double signature by again attach some SOAP 3.SYSTEM ARCHITECTURE parameter sign Cloud CGI DNS Attach SOAP header with client IP address clients security Hijack Xml ing Attach encryption key in SOAP message header security analy zer Attach decryption key in SOAP message header IP PROXY AND CLOU CAPCHA PROXY D Fig 3.Attaching double signature and security PROVI keys in soap and wsdl WEBSERV ICES DER C)security key attachments Encryption and decryption key attached in WSDL and SOAP request message Fig 2.System Architecture <wsp:Policy Xmlns: wsp=policy link 4.XML VALIDATORS AND EMBEDDING Xmlns: wsu=”” SOAP MESSAGE WITH DOUBLESIGNATURE Fig4.Encrption key attached in WSDL a) Now a days web services via XML and WSDL IJERTIJERT .REST web services uses HTTP and representational <wssp: decryption <wssp : message> state transfer protocol principles. To avoid XML INJECTION and XML DDOS we using Wsp: Body/wssp: msg> XMLVALIDATORS. Fig 5.Decrption key attached in SOAP <!DOCTYPE transaction 5.CLOUD SPACE CREATION <!DOCTYPE Transaction system “file”> b)parameter double signature protection against XML rewriting by making some SOAP parameters signed again and kept with SOAP header. Fig 6.cloud space creation www.ijert.org 3 International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 2, February- 2013 5)CGI security Fig 7.workflow of system a)In private and public clouds we 8)PROXY IMPLEMENTATION introduce cgi security byMD5 hash authentication ,Locking normal hypertext transfer and secure It works as middleware between cloud server and hypertext transfer. This is a infrastructure browser. It detects system name, IP address, request security. URL, time which is invoked by client. b)CGI security on IIS by 9)PROXY WEBSERVICE IMPLEMENTATION . Web service extension for To scan the request. IIS6.0 CGI SECURITY authenticates transport and socket . role service for IIS7.0 level transactions. If any unauthorized action takes place means lock the http and https. Dns hijacking 6)DNS hijacking analyzer analyzer detect the ip spoofing. If any suspected ip Analyze and scan the tcp dump of the victim. means deny the request. Commonly used hijacking tools are Hjsuite. Ip capcha responsible for monitoring suspected ip by 7)IP CAPCHA help of MAC address verification, unique frequency of IP soon. Capture the suspected IP by means of proxy web service responsible for detect the IP, time Increase no of Ip, same domain name request,. ip request, system name so on. spoofing verified with hardware address, unique frequency. 10)OTHER SECURITY ACTS yes Increased no of IP 10.1) Audit log The audit log file must be Suspected ip IJERT Deny the IJERTencrypted and stored in network segments. request Same domain name 10.2) Attach providers information yes request 10.3) Reduce of risk patches Wrong Suspected ip Use isv to reduce risk. yes decryption yes key Verify MAC address 10.4) Several factor authentication yes More than password to prove Web identity . must for admin who are unable to onsite Suspected ip baseddd but access the production. os attack 11)CONCLUSION no yes yes Signature mismatch Now a days cloud DDOS attacks are challenge for no medical and banking domain. Enterprises also attacked by web based and web service based ddos yes yes attacks. W ebservice ddos attack provide cloud service www.ijert.org 4 International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 2, February- 2013 To avoid this we introduce CGI authentication, DNS 9.Cloud -DoS and XML-DoS attacks by Ashley hijacking analyzer, IP CAPCHA , proxy web services Chonka, YangXiangn, WanleiZhou, AlessioBonti. for web based DDOS attacks. Contents lists available at Science Direct journal homepage.. security key and double signature to avoid web service DDOS attacks. IPCACHA uses MAC address 10.Guidelines on Security and Privacy in Public verification , frequency verification, same domain Cloud Computing by Wayne Jansen, Timothy name request. Grance.NSI U.S department of commerce. These techniques will helpful to avoid the web based 11. HTTP DDoS Attack Mitigation Using and web service based DDOS attacks. Tarpitting by Joe Stewart available on web. 12)REFERENCES 12.Tracing Sources of DDoS Attacks in IP Networks Using Machine Learning Automatic Defence System, 1.Security Manager's Journal: First task is to tighten k. subhashini , g.subbalakshmi, International Journal up SaaS security By Mathias Thurman of Electronics Communication and Computer Engineering Volume 3, Issue (1) NCRTCST, ISSN 2.Security Manager's Journal: Plugging a SaaS access 2249 –071X. hole By Mathias Thurman 13.Fog Computing: Mitigating Insider Data Theft 3.On deterministic packet marking Attacks in the Cloud by Salvatore J. Stolfo. byAndreyBelenky, NirwanAnsari available online at 15.An Efficient Way Of IP Trace back Of DDOS science direct website Attacks Based On Entropy International Journal of Communications
Load more

Recommended publications
  • Infoblox White Paper
    Enterprise Strategy Group | Getting to the bigger truth.™ White Paper Enterprise DNS Security By Jon Oltsik, Senior Principal Analyst March 2018 This ESG White Paper was commissioned by Infoblox and is distributed under license from ESG. © 2018 by The Enterprise Strategy Group, Inc. All Rights Reserved. White Paper: Enterprise DNS Security 2 Contents Executive Summary ................................................................................................................................................................. 3 The State of Cybersecurity in 2018 ......................................................................................................................................... 3 DNS and Cybersecurity ............................................................................................................................................................ 5 DNS for Cybersecurity Advantage ....................................................................................................................................... 5 Enterprise-Class Secure DNS ................................................................................................................................................... 6 Enter Infoblox ActiveTrust Suite (Cloud and On-premises) ................................................................................................ 7 The Bigger Truth .....................................................................................................................................................................
    [Show full text]
  • Godaddy – Domain Hijacking
    Domain Hijacking Matthew C. Stith, Spamhaus Eddy Winstead, ISC April 29th, 2020 https://www.isc.org What we’re going to covering • What why and how of domain hijacking • Examples of various hijacking methods • High profile stories about hijacked domains • What can be done to protect domains and networks • Q&A 2 What is Domain Hijacking? • Malicious actors gaining access to the DNS records of a legitimate domains (which they do not own): • In some cases only the root domain’s DNS is changed. This is reflected in the WHOIS. • In other cases a new host (subdomain) is created with new DNS settings. This practice is called domain shadowing. This is not visible at the WHOIS level. 3 Why is it exploited? These following two factors lead to a positive reputation: • The age of the domain • The legitimacy of the domain Meaning many of these domains could be able to send email or serve content without much scrutiny from content or reputation filters. 4 How is it happening? Phishing Social Compromised Exploiting Malware engineering DNS weaknesses in applications 5 Investigating domain hijacking • Passive DNS data is collected with special Client queries local DNS resolver Passive DNS Data probes activated on a DNS Resolver. Domain not included in cache • The probes record anonymized cache Data from Query external root server recursive miss. segment is recorded • Data is collected through DNS recursive Domain not found servers. Query top level domain server • Simple and extensive search functionalities make this data easy to Domain not found Client
    [Show full text]
  • Ethical Hacking
    Ethical Hacking Alana Maurushat University of Ottawa Press ETHICAL HACKING ETHICAL HACKING Alana Maurushat University of Ottawa Press 2019 The University of Ottawa Press (UOP) is proud to be the oldest of the francophone university presses in Canada and the only bilingual university publisher in North America. Since 1936, UOP has been “enriching intellectual and cultural discourse” by producing peer-reviewed and award-winning books in the humanities and social sciences, in French or in English. Library and Archives Canada Cataloguing in Publication Title: Ethical hacking / Alana Maurushat. Names: Maurushat, Alana, author. Description: Includes bibliographical references. Identifiers: Canadiana (print) 20190087447 | Canadiana (ebook) 2019008748X | ISBN 9780776627915 (softcover) | ISBN 9780776627922 (PDF) | ISBN 9780776627939 (EPUB) | ISBN 9780776627946 (Kindle) Subjects: LCSH: Hacking—Moral and ethical aspects—Case studies. | LCGFT: Case studies. Classification: LCC HV6773 .M38 2019 | DDC 364.16/8—dc23 Legal Deposit: First Quarter 2019 Library and Archives Canada © Alana Maurushat, 2019, under Creative Commons License Attribution— NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) https://creativecommons.org/licenses/by-nc-sa/4.0/ Printed and bound in Canada by Gauvin Press Copy editing Robbie McCaw Proofreading Robert Ferguson Typesetting CS Cover design Édiscript enr. and Elizabeth Schwaiger Cover image Fragmented Memory by Phillip David Stearns, n.d., Personal Data, Software, Jacquard Woven Cotton. Image © Phillip David Stearns, reproduced with kind permission from the artist. The University of Ottawa Press gratefully acknowledges the support extended to its publishing list by Canadian Heritage through the Canada Book Fund, by the Canada Council for the Arts, by the Ontario Arts Council, by the Federation for the Humanities and Social Sciences through the Awards to Scholarly Publications Program, and by the University of Ottawa.
    [Show full text]
  • DNS and the DNS Cache Poisoning Attack
    Lecture 17: DNS and the DNS Cache Poisoning Attack Lecture Notes on “Computer and Network Security” by Avi Kak ([email protected]) June 25, 2021 3:21pm ©2021 Avinash Kak, Purdue University Goals: The Domain Name System BIND Configuring BIND Running BIND on your Ubuntu laptop Light-Weight Nameservers (and how to install them) DNS Cache Poisoning Attack Writing Perl and Python code for cache poisoning attacks Dan Kaminsky’s More Virulent DNS Cache Poisoning Attack CONTENTS Section Title Page 17.1 Internet, Harry Potter, and the Magic of DNS 3 17.2 DNS 5 17.3 An Example That Illustrates Extensive DNS 13 Lookups in Even the Simplest Client-Server Interactions 17.4 The Domain Name System and The dig Utility 28 17.5 host, nslookup, and whois Utilities for Name 42 Lookup 17.6 Creating a New Zone and Zone Transfers 45 17.7 DNS Cache 48 17.7.1 The TTL Time Interval 51 17.8 BIND 56 17.8.1 Configuring BIND 58 17.8.2 An Example of the named.conf Configuration File 64 17.8.3 Running BIND on Your Ubuntu Laptop 68 17.9 What Does it Mean to Run a Process in a 70 chroot Jail? 17.10 Phishing versus Pharming 73 17.11 DNS Cache Poisoning 74 17.12 Writing Perl and Python Code for Mounting a 81 DNS Cache Poisoning Attack 17.13 Dan Kaminsky’s More Virulent Exploit for 92 DNS Cache Poisoning 17.14 Homework Problems 99 Computer and Network Security by Avi Kak Lecture 17 Back to TOC 17.1 INTERNET, HARRY POTTER, AND THE MAGIC OF DNS If you have read Harry Potter, you are certainly familiar with the use of owl mail by the wizards and the witches.
    [Show full text]
  • (Synced) Cookie Monster Breached My Encrypted VPN Session
    Exclusive: How the (synced) Cookie Monster breached my encrypted VPN session Panagiotis Papadopoulos Nicolas Kourtellis Evangelos P. Markatos FORTH-ICS, Greece Telefonica Research, Spain FORTH-ICS, Greece [email protected] [email protected] [email protected] ABSTRACT worse, last year, the USA House of Representatives voted to reverse In recent years, and after the Snowden revelations, there has been a FCC’s regulations that prevented Internet Service Providers (ISPs) significant movement in the web from organizations, policymakers from selling users web-browsing data without their explicit con- and individuals to enhance the privacy awareness among users. sent [14]. Apart from the profit-oriented data collection, ad-related As a consequence, more and more publishers support TLS in their tracking techniques have been also exploited by agencies (as proven websites, and vendors provide privacy and anonymity tools, such after the Snowden revelations [36]) to increase the effectiveness of as secure VPNs or Tor onions, to cover the need of users for privacy- their mass surveillance mechanisms. preserving web browsing. But is the sporadic appliance of such tools This intensive data collection and use beyond the control of the enough to provide privacy? end-users, in some cases has been characterized as pervasive or even In this paper, we describe two privacy-breaching threats against intruding, thus, raising significant privacy concerns [22, 36]. These users accessing the Internet over a secure VPN. The breaches are privacy concerns have made Internet users more privacy-aware [4], made possible through Cookie Synchronization, nowadays widely leading browser vendors to adopt more privacy preserving features used by third parties for advertisement and tracking purposes.
    [Show full text]
  • Are Dns Requests Encrypted
    Are Dns Requests Encrypted Iago still caparisons teasingly while movable Ford interposing that scars. Neall stand-up hoarsely. How yon is Pierson when fluviatile and unappealing Nevins approve some bilker? A beard to DNS-over-HTTPS how to new web protocol aims. The handwriting of these DNS services bypasses controls that expertise IT. Blocking domains serving clients about dns timings to both are reported for multiple providers to prevent employees from those requests encrypted with the. If possible and are requested service is optional, i look back to. Dns queries and a keen marathon runner whenever it! Fi networks where another in physical proximity can cry and decrypt wireless network traffic. How do telecom companies survive when everyone suddenly knows telepathy? Tls and forwards it could be a household name resolution of efficiency and not too large websites, unencrypted dhs examine raw packets in on. Mozilla has adopted a fine approach. How does DNS-over-HTTPS work The basic idea behind DoH is to add a growing of encryption to your DNS request to graze its contents invisible. Properties and are requested site reliability requires a request first step is incredibly reliable and redirect to digital world. Which had again encapsulated by another ip header destined to my vpn provider. Rsa key infrastructure and dns are requests encrypted anywhere your dns resolution. Dns privacy breach by encrypting dns server it can encrypt dns servers after criticism, who can act as a public key of just over http. DNS over TLS DoT when a security protocol for encrypting and wrapping Domain the System DNS queries and answers via the Transport Layer Security TLS protocol The goal knowing the method is small increase user privacy and security by preventing eavesdropping and manipulation of DNS data quality man-in-the-middle attacks.
    [Show full text]
  • Are You Fully Prepared to Withstand DNS Attacks? Fortifying Mission-Critical DNS Infrastructure Are You Fully Prepared to Withstand DNS Attacks?
    WHITE PAPER Are You Fully Prepared to Withstand DNS Attacks? Fortifying Mission-Critical DNS Infrastructure Are You Fully Prepared to Withstand DNS Attacks? Fortifying Mission-Critical DNS Infrastructure The most common service targeted by application layer attacks is now1, for the first time, Domain Name System (DNS). Why? Because by its very nature, DNS is easy to exploit. • Most enterprise firewalls are configured to allow port 53 traffic to service DNS, giving attackers an easy way to evade your existing defense systems. • Because DNS queries are asymmetrical, they can result in a response many times larger than the query, which means that your DNS system itself can be made to amplify an attack. Hackers can send one packet of data and cause a flurry that is amplified several times—effectively stopping your business in its tracks. • Attackers can easily conceal their identities, because the DNS protocol is stateless. DNS attacks do more than target external authoritative servers. More recently, NXDOMAIN attacks and other low-volume DDoS attacks that affect recursive or caching servers have been on the rise. These are stealth attacks that cause as much damage as the popular volumetric attacks but are less understood and remain under the radar. Attackers are using more advanced techniques than ever before, ranging from simple NXDOMAIN attacks to highly sophisticated DDoS attacks involving botnets, chain reactions, and misbehaving domains. The impact on the recursive server includes resource exhaustion, cache saturation, and outbound bandwidth congestion, while the target domain experiences DDoS. DNS-based attacks are also used as diversions in broader plans to breach company defenses and steal data, a practice called “smoke screening.” DNS hijacking compromises the integrity of DNS and redirects users who are trying to access a website to a bogus site controlled by the hackers, which may look like the real thing.
    [Show full text]
  • DNS Over HTTPS—What Is It and Why Do People Care?
    INSIGHTi DNS over HTTPS—What Is It and Why Do People Care? October 16, 2019 Internet pioneer David Clark said: “It’s not that we didn’t think about security. We knew that there were untrustworthy people out there, and we thought we could exclude them.” Those who created the internet were focused on enabling the utility of the network, and a repercussion of their design decisions is that internet security is not inherent but must be retrofitted. Efforts to change one of the internet’s hardwired insecurities—the Domain Name System (DNS)—are ongoing but will be disruptive. How We Get to Websites Today When someone wants to visit a website, they type the web address into their browser, and the website loads. DNS is one of the many protocols needed to make that work. Many call DNS the “phonebook of the internet”: it takes the user-readable web address and sends that information to a DNS resolver. The resolver retrieves the internet protocol (IP) address of the website (i.e., the network address of the server that hosts the website) and returns that information to users’ computers. Knowing where to go, the browser then retrieves the website. Most users receive DNS resolver services from their internet service provider (ISP), but some choose to use another service. For instance, some businesses choose to use a resolver that provides additional security or filtering services. Today, DNS queries are generally sent unencrypted. This allows any party between the browser and the resolver to discover which website users want to visit. Such parties can already monitor the IP address with which the browser is communicating, but monitoring DNS queries can identify which specific website users seek.
    [Show full text]
  • Alert: DNS Hijacking Activity Targeting Government and Commercial Organisations Worldwide
    Alert: DNS hijacking activity targeting government and commercial organisations worldwide Version 2.0 Reference: NCSC-Ops/03-19 5 February 2019 © Crown Copyright 2019 About this document This NCSC alert highlights recent DNS hijacking activity that has affected a number of domains globally. It provides a summary of available information and tailored mitigation advice. Handling of the Report Information in this report has been given a Traffic Light Protocol (TLP) of WHITE, which means it can be shared within and beyond the CiSP community with no handling restrictions. Disclaimer This report draws on information derived from NCSC and industry sources. Any NCSC findings and recommendations made have not been provided with the intention of avoiding all risks and following the recommendations will not remove all such risk. Ownership of information risks remain with the relevant system owner at all times. Introduction The NCSC is investigating a large-scale Domain Name System (DNS) hijacking campaign that has reportedly affected government and commercial organisations worldwide.1 The majority of the entities targeted are in the Middle East, but some impact has also been reported in Europe and the United States. While the NCSC is not currently aware of any compromised entities in the UK, the techniques exhibited could feasibly be deployed against UK targets. In the campaign, attackers are believed to have compromised credentials that have given them the ability to manipulate DNS records, giving them the ability to redirect traffic to attacker-owned infrastructure. Techniques Industry reporting has identified two principal techniques being deployed: • DNS A (Address) record hijacking A DNS A record maps a domain name to the IP address of the computer hosting that domain.
    [Show full text]
  • Senate Committee on the Judiciary Subcommittee on Human Rights and the Law
    Senate Committee on the Judiciary Subcommittee on Human Rights and the Law Hearing on Global Internet Freedom: Corporate Responsibility and the Rule of Law May 20, 2008 Testimony by Shiyu Zhou, Ph.D. Deputy Director, Global Internet Freedom Consortium Mr. Chairman, members of the Committee, Ladies and Gentlemen. I would like to thank you for this opportunity to testify before you today on the topic of global Internet freedom and the Corporate Responsibility and the Rule of Law. The lack of information freedom in closed societies is usually coupled with severe violations of human rights and it also puts the United States at risk. In Iran, Cuba and certain other totalitarian countries, information control is often used for manipulation and indoctrination and whipping up anti-US sentiment, as illustrated by the xenophobia fostered online in the People’s Republic of China (PRC) following the Tibet crackdown and the Olympics Torch Relay. Violence begins with hate, and hate begins with distorted information. Information control can also cost lives. When the PRC leadership chose to suppress news of the SARS outbreak in 2002, the virus spread far beyond China’s borders to places like San Francisco, causing the death of at least several hundred victims and almost a global pandemic. The Internet has become the greatest hope for global information freedom. It is a vast, fast, and inexpensive way to access information and to communicate and the number of Internet users worldwide has soared. By January of this year, the PRC had 210 million users and has since surpassed the US, and both Iran and Vietnam were at 18 million users and growing.
    [Show full text]
  • A Taxonomy of Internet Censorship and Anti- Censorship
    A Taxonomy of Internet Censorship and Anti- Censorship Draft Version December 31, 2010 Christopher S. Leberknight Mung Chiang Princeton University Princeton University Department of Electrical Engineering Department of Electrical Engineering [email protected] [email protected] Harold Vincent Poor Felix Wong Princeton University Princeton University Department of Electrical Engineering Department of Electrical Engineering [email protected] [email protected] ABSTRACT – Internet is supposed to be born free, yet it is censored almost everywhere, and severely censored in a few countries. The tug-of-war on the Internet between censors and anti-censors is intensifying. This survey presents a taxonomy on the principles, techniques, and technologies of Internet censorship and anti-censorship. It highlights the challenges and opportunities in anti-censorship research, and outlines a historical account via the lenses of news coverage in the past decade. I. INTRODUCTION Internet is supposed to be born free, yet it is censored almost everywhere, and severely censored in a few countries. Censorship is defined as the institution, system or practice of reading communication and deleting material considered sensitive or harmful [1]. Throughout history, various methods of censorship have been used to reinforce specific religious and political agendas. Technology has often served as a major obstacle and catalyst for mandating censorship. Even though technological advancement often ameliorates the inefficiencies and limitations of the past, it also can precipitate unforeseen consequences. The invention of the printing press in Europe in the 15th century is a prime example. The printing press not only increased the spread of information and knowledge but it also increased the practice and frequency of censorship.
    [Show full text]
  • The Cracked Cookie Jar: HTTP Cookie Hijacking and the Exposure of Private Information
    The Cracked Cookie Jar: HTTP Cookie Hijacking and the Exposure of Private Information Suphannee Sivakorn∗, Iasonas Polakis∗ and Angelos D. Keromytis Department of Computer Science Columbia University, New York, USA fsuphannee, polakis, [email protected] ∗Joint primary authors Abstract—The widespread demand for online privacy, also the necessity of securing web connections from prying eyes. fueled by widely-publicized demonstrations of session hijacking The publicity garnered by the Firesheep extension [1], which attacks against popular websites, has spearheaded the increasing demonstrated how easily attackers can hijack a user’s session, deployment of HTTPS. However, many websites still avoid ubiq- uitous encryption due to performance or compatibility issues. The was a catalyst in expediting migration of critical user activity prevailing approach in these cases is to force critical functionality to mandatory HTTPS connections in major services (e.g., and sensitive data access over encrypted connections, while transmitting user credentials during the log-in process). allowing more innocuous functionality to be accessed over HTTP. Nonetheless, many major websites continue to serve content In practice, this approach is prone to flaws that can expose over unencrypted connections, which exposes the users’ HTTP sensitive information or functionality to third parties. In this paper, we conduct an in-depth assessment of a diverse cookies to attackers monitoring their traffic. Not enforcing set of major websites and explore what functionality and infor- ubiquitous encrypted connections may be attributed to various mation is exposed to attackers that have hijacked a user’s HTTP reasons, ranging from potential increases to infrastructure costs cookies. We identify a recurring pattern across websites with and the loss of in-network functionality [2] to maintaining partially deployed HTTPS; service personalization inadvertently support for legacy clients.
    [Show full text]