DOCSLIB.ORG

Eurosec2019-Paper21

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Eurosec2019-Paper21 This is an electronic reprint of the original article. This reprint may differ from the original in pagination and typographic detail. Bui, Thanh; Rao, Siddharth; Antikainen, Markku; Aura, Tuomas Pitfalls of open architecture Published in: Proceedings of the 12th European Workshop on Systems Security, EuroSec 2019 DOI: 10.1145/3301417.3312495 Published: 25/03/2019 Document Version Early version, also known as pre-print Please cite the original version: Bui, T., Rao, S., Antikainen, M., & Aura, T. (2019). Pitfalls of open architecture: How friends can exploit your cryptocurrency wallet. In Proceedings of the 12th European Workshop on Systems Security, EuroSec 2019 (pp. 6). [3] ACM. https://doi.org/10.1145/3301417.3312495 This material is protected by copyright and other intellectual property rights, and duplication or sale of all or part of any of the repository collections is not permitted, except that material may be duplicated by you for your research use or educational purposes in electronic or print form. You must obtain permission for any other use. Electronic or print copies may not be offered, whether for sale or otherwise to anyone who is not an authorised user. Powered by TCPDF (www.tcpdf.org) Pitfalls of open architecture: How friends can exploit your cryptocurrency wallet Submitted to EuroSec’19 ABSTRACT stolen from wallets by exploiting the remotely-accessible RPC in- Many cryptocurrency wallet applications on desktop provide an terface where authentication has not been properly configured [55]. open remote procedure call (RPC) interface that other blockchain- The primary solution for protecting the RPC interface against such based applications can use to access their functionality. This paper attacks has been to block remote access to the interface so that studies the security of the RPC interface in several cryptocurrency only local processes on the computer can access it. Furthermore, wallets. We find that, in many cases, a malicious process running the wallet applications usually require password authentication on the computer regardless of its privileges can impersonate the when accessing the RPC interface. However, while these security communication endpoints of the RPC channel and, effectively, steal mechanisms may help against remote attacks, their effectiveness the funds in the wallet. The attacks are closely related to server against local threats has not been considered. and client impersonation on computer networks but occur inside This paper studies the security of the RPC interface of the wallet the computer. The malicious process may be created by another applications in the presence of a local attacker. Our main contribu- authenticated but unprivileged user on the same computer or even tion is to show vulnerabilities in popular cryptocurrency wallets, by the guest user. The main contribution of this paper is to raise which allow nonprivileged processes that belong to other users on awareness among wallet developers about the need to protect local the same computer to exploit their RPC channel and steal the wal- RPC channels with the same prudence as network connections. We let content. We also show that the currently used authentication also hope that it will discourage users to run security-critical appli- mechanisms on the channel are not effective and discuss potential cations like cryptocurrency wallets on shared systems or computers mitigation techniques. with guest account enabled. The rest of the paper is organized as follows: Section 2 describes the background information on cryptocurrency wallet applications CCS CONCEPTS and our threat model. Section 3 shows our attacks to the RPC inter- face of various wallet applications, and Section 4 presents mitigation • Security and privacy → Authentication; Software security engi- solutions to the attacks. We have reported all the vulnerabilities neering. that we found to the corresponding vendors and received responses from Parity [21] and Bitcoin Core [5] teams. We include these re- KEYWORDS sponses in Section 5. Section 6 reviews the related prior research Cryptocurrencies, Remote Procedure Call (RPC), Impersonation and Section 7 concludes the paper. 1 INTRODUCTION 2 BACKGROUND This section describes how a typical cryptocurrency wallet applica- Bitcoin [45] and other cryptocurrencies have become remarkably tion works as well as explaining our threat model. popular in the last decade. In cryptocurrencies, transactions happen between public keys and are communicated as signed messages in an open peer-to-peer (P2P) network. The transactions are col- 2.1 Cryptocurrency wallets lected into blocks, which are appended into a structure, called the Most cryptocurrencies have one “official” wallet applications and blockchain. The global consistency of the blockchain is guaranteed several recommended third-party applications. A wallet application with a consensus mechanism, such as proof-of-work [45], proof-of- typically provides a command-line or graphical user interface for stake [35], or a Byzantine fault-tolerant (BFT) variant [52]. the users to manage their cryptocurrency accounts. Each account Users access a cryptocurrency with a wallet, which manages the is basically a private/public key-pair that is used for transactions private/public key-pairs that are used for transactions and allows and usually encrypted with a password. (Note that in some places the user to store, send and receive the cryptocurrency. There are “wallet” is used to refer to such key pair. We chose to use “account” various types of cryptocurrency wallets: online, mobile, desktop, instead to easy differentiation between key pairs and wallet appli- paper, and hardware wallets, each of which has its own pros and cations.) The user must enter the password to unlock the account cons [32]. This paper focuses solely on desktop wallet applications. before it can be used. For simplicity, in the rest of the paper, we will use wallet applications Most wallet applications provide a remote procedure call (RPC) to refer to desktop wallet applications. interface with a JSON-RPC over HTTP server [40] that runs on a Desktop wallet applications often provide a remote procedure call specific port number on the localhost. Other applications can con- (RPC) interface, through which other applications can access the nect to the RPC server as clients to access the wallet’s functionality, wallet’s functionality either locally or remotely. While this open such as querying account balance or making transactions. Examples interface enables easy development of other blockchain-based ap- of such RPC client applications include web-browser extensions plications, it increases the attack surface of the wallet. In fact, there [17], third-party wallet applications that do not want to implement have been reports on attacks where cryptocurrencies have been the cryptocurrency protocol by themselves [4], and cryptocurrency EuroSec’19, March 2019, Dresden, Germany Alice's login session Alice's login session Alice's login session RPC client Wallet app RPC client Wallet app RPC client Wallet app 8332 8332 8332 8332 Evil process Evil process Mallory's login session Mallory's login session (a) Normal operation (b) Server impersonation (c) Client impersonation Figure 1: Attacks on the RPC channel of a wallet application by a nonprivileged user exchange web platforms [3, 22]. While the number of RPC client 3.1 Case 1: Wallets with no authentication applications is still fairly low, the availability of open RPC interfaces Ethereum [56] has two official command-line wallets: Go-Ethereum and client libraries indicate that the wallet developers expect the (Geth) [14] and CPP [9], out of which only the former supports the ecosystem of such add-on software to grow in the future. RPC interface. If the user enables the RPC interface, Geth runs the RPC server on port 8545 of the localhost by default so that only 2.2 Threat model local clients can access it. Geth does not require any authentication In this paper, we consider threats on multi-user computers that have mechanism on its RPC interface, and it does not support TLS. If the processes belonging to two or more users running at the same time. user wants to access the interface over TLS, he/she must configure The attacker is a logged-in user who tries to steal cryptocurrency a TLS proxy on the same host, which relays requests to the RPC from the wallet of another logged-in user of the same computer. interface. The only security mechanism that Geth provides is allow- The attacker does this by impersonating the communication end- ing the user to configure cross-origin resource sharing (CORS) [41] points of the wallet’s RPC channel, as illustrated in Figure 1. Unlike to authorize specific web pages that are open in the user’s browser malware that runs with the victim’s privileges or as administrator, to access the wallet. the attacker here is nonprivileged, and we do not assume that he Attacks. Since there is no authentication between the RPC client can perform any kind of privilege escalation. and the RPC server, a malicious nonprivileged process can imper- To exploit the RPC channel, the attacker needs to run a process sonate the client by simply connecting to the server. CORS is clearly in the background when the victim is using the computer. On Linux not an effective mitigation solution here because the attacker can and macOS, the attacker only needs to log in, run the process, and set the Origin header of its HTTP requests to anything. While an leave it running when he logs out, e.g. with the nohup command. On account could be encrypted with a password, Geth allows the user Windows, user processes are killed at the end of the login session, to unlock the account when starting it. This allows the malicious and thus the attacker needs to do fast user switching [43] to leave client to access the account without knowing the password and, his session in the background. The attacker can also remotely run for example, sends the victim’s funds to the attacker’s account.
Load more

Recommended publications
  • Malpedia: a Collaborative Effort to Inventorize the Malware Landscape
    Malpedia: A Collaborative Effort to Inventorize the Malware Landscape Daniel Plohmann @push_pnx [email protected] 2017-12-07 | Botconf, Montpellier Martin Clauß martin.clauß@fkie.fraunhofer.de Steffen Enders [email protected] Elmar Padilla [email protected] 1 © Cyber Analysis and Defense Department, Fraunhofer FKIE $whoami Daniel Plohmann Security Researcher @ Fraunhofer (Europe‘s largest organisation for applied research) Research Scope: Malware Analysis Reverse Engineering Automation 2 © Cyber Analysis and Defense Department, Fraunhofer FKIE Outline Summary Motivation (or: how it began) Approach The Malpedia Corpus & Platform A Comparative Structural Analysis of Windows Malware Future Plans / Conclusion 3 © Cyber Analysis and Defense Department, Fraunhofer FKIE Summary 4 © Cyber Analysis and Defense Department, Fraunhofer FKIE Summary TL;DR What is Malpedia? A free, independent, pooled resource for confidently labeled, unpacked reference samples for malware families and versions Meta data tracker for info such as references (analysis reports, blogs, …), YARA rules, actors, tied to these families Status (2017-12-01): 2491 samples for 669 families, multi-platform (WIN, ELF, APK, OSX, …) Our Contributions Definition of requirements for malware corpora and a reference corpus + platform implementing these A Comprehensive, quantitative static analysis of structural features for 446 Windows malware families 5 © Cyber Analysis and Defense Department, Fraunhofer FKIE Motivation … or
    [Show full text]
  • PETYA・JIGSAW・WANNACRY・ZEPTO・LOCKY Business Resilience = Data Resilience
    PETYA・JIGSAW・WANNACRY・ZEPTO・LOCKY Business Resilience = Data Resilience Speaker Introduction Brent Reichow From Minneapolis, Minnesota (USA) April 1992 Arrived in Chiba, Japan Work History LINC Computers (EDS), NTT-WT, PSINet (C&W) Stellent (Oracle), Internet Security Systems (ISS) July 2004 Co-founded Blueshift K.K. Blueshift Business Leading provider of data protection solutions delivering secure, off-site, disk based, data backup, and disaster recovery services to small, medium and large organizations Client Markets Automotive, education, financial services, healthcare, insurance, legal services, logistics, manufacturing, marketing, media, NPO, real estate, recruiting, retail and technology URL www.dataprotection.co.jp/www.dataprotection.jp Blueshift’s Cloud Backup Business A. Initial full backup is made, compressed and encrypted data is sent to public or private data center locations B. Additional schedule or manual backups, will transfer changed data (deltas) off-site (incremental forever Public or Private Client Site Data Centers • File Server • Mail Server C. Rapid restores (deltas /changed data) WAN / INTERNET • Database Server • Virtual Machine (VM) • Multiple restoration points in time • Cloud 2 Cloud • Restore in minutes not hours G. Retention Policy Administrator • 30 day, 1 year D. Security Location 2 • Longer options • All data is encrypted with 256 bit AES • Data remains encrypted in flight and at rest F. Remote Management E. Onsite Appliance (de-duplication, compression, encryption) • Email alerting functionality • LAN speed restores with local available storage • Manage multiple servers A Billion Dollar Industry So How Does Ransomware Work? Ransomware as a Service (RaaS) - Typically the Developer Receives 30% of Ransom Paid by Victims Zepto Ransomware Attack Internet Phishing Email Workstations USB File Database NAS Server Your computer files have been encrypted Your photos, videos, documents, etc… But, don’t worry! I have not deleted them, yet.
    [Show full text]
  • Essential Faqs to Combating Ransomware
    ESSENTIAL FAQS TO COMBATING RANSOMWARE S e p t e m b e r 2016 www.ensilo.com RESEARCH PAPER TABLE OF CONTENTS What is Ransomware? 3 Does Ransomware Only Encrypt Files? 4 What Are the Common Types of Ransomware In-the-Wild? 4 How are Victims Infected? 4 At What Stage Does the Ransomware Encrypt the Data? 5 How Long Does it Take for Ransomware to Encrypt Files? 5 How are the Threat Actors Paid? 6 What Platforms does Ransomware Target? 6 Don’t the Operating System Vendors, such as Microsoft, Place 7 Protections to Prevent Ransomware from Running? Have You Seen Any Ransomware Cases? 7 Is Ransomware a Periodic Fad or a Trending Issue? 8 What Strategy Should Businesses Adopt to Combat Ransomware? 9 Samples of ransomware notes 10 About enSilo 11 RESEARCH PAPER Ransomware isn’t new. But the tactics are. Ransomware has gone from a nickel & dime operation targeting individual computers to a multimillion dollar criminal operation targeting organizations that can afford to pay enterprise-level payments. Research1 showed that a single threat actor was “making more than $30M USD annually from ransomware infections alone”. Clearly, with such a strong financial motivation behind ransomware, the threat criminals behind these types of attacks are not going to stop anytime soon. To help combat against the threat of ransomware, we’ve put together this FAQ. If you see any question you’d like to add, or just want to be heard, feel free to email us: [email protected] WHAT IS RANSOMWARE? Ransomware is an increasingly popular tactic used to steal data and disrupt a system’s operations.
    [Show full text]
  • Analyzing Facebook, Twitter, and Google's Efforts to Combat Foreign
    PolicyBrief 2018 | No. 041 A Long Way To Go: Analyzing Facebook, Twitter, and Google’s Efforts to Combat Foreign Interference By Bradley Hanlon Executive Summary and improve verification standards for those hoping to publish political advertisements. Investments in Two years after the Russian government manipulated forward-looking measures have included internal social media to interfere in the 2016 U.S. presidential initiatives to critically assess vulnerabilities and external election, online information platforms continue to partnerships with civil society, academia, and fact- serve as mediums for such operations, including the checking organizations. They have also led to increased 2018 midterm elections. Under intense public criticism transparency about the behavior and content of accounts and congressional scrutiny, the three most prominent linked to the Russian operation against the 2016 and online information platforms – Facebook, Twitter, and 2018 elections, as well as other nation-state operations Google – have taken steps to address vulnerabilities and targeting Americans. to protect their users against information operations by actors linked to authoritarian regimes. However, given Though all of these steps are important, ongoing the ongoing nature of online authoritarian interference, vulnerabilities demand more urgent action by the the steps taken by these companies continue to fall platforms to secure the online information space against short. foreign manipulation, while ensuring American’s ability to engage freely in robust speech and debate. Six areas This report reviews and analyzes the steps taken by where Facebook, Twitter, and Google must take further online information platforms to better defend against steps include: foreign interference since 2016, adopting the framing of the Senate Intelligence Committee by focusing on • Focusing on behavior: Online information the largest and most influential online information platforms have unique insight into the platforms of Facebook, Twitter, and Google.
    [Show full text]
  • Male Homosocial Landscape
    MALE HOMOSOCIAL LANDSCAPE: FAULKNER,WRIGHT, HEMINGWAY, AND FITZGERALD A dissertation submitted To Kent State University in partial Fulfillment of the requirements for the Degree of Doctor of Philosophy by Masaya Takeuchi December, 2011 Dissertation written by Masaya Takeuchi B.A., Rikkyo University, 2001 M.A., Rikkyo University, 2004 Ph.D., Kent State University, 2011 Approved by Robert Trogdon , Chair, Doctoral Dissertation Committee Mark Bracher , Member, Doctoral Dissertation Committee Kevin Floyd , Member, Doctoral Dissertation Committee Elizabeth M. Smith-Pryor , Member, Doctoral Dissertation Committee Marilyn A. Norconk , Member, Doctoral Dissertation Committee Accepted by Donald M. Hassler , Interim Chair, English Department Timothy Moerland , Dean, College of Arts and Sciences ii TABLE OF CONTENTS Acknowledgments ……………………………………………………………………….iv Introduction …………………………………………………….………………………. 1 Part I: Chapter 1. ………………………………………………………………………………. 26 2. …………………..…………………………………………………………... 59 Part II: Chapter 3. ………………...……………………………………………………………... 93 Part III: Chapter 4. ……………...……………………………………………………………… 122 5. ………..……………………………………………………………………. 163 Part IV: Chapter 6. ……...……………………………………………………………………… 190 7. ……………………………………………………………………………... 225 Conclusion …………………………………………………………………………….. 254 Bibliography ….………………………………………..……………………………..... 261 iii Acknowledgements During the eight years I have studied in Ph.D. programs at Rikkyo University and Kent State University, I have received tremendous instruction and encouragement from many professors.
    [Show full text]
  • December 2004 Letters to the Editor 3
    DEAR EDITOR, Wireless Security: A Discussion Rik Farrow writes in the August ;login: that “the downside of Note from Rob Kolstad: This article [offshoring] is that real com- summarizes an email discussion munication between software between Marcus Ranum and Bill developers and program man- Cheswick after Marcus had an letters to agers will get even worse.” This “interesting experience” at the presumes a model where devel- USENIX Security Conference. the editor opers only communicate with Thanks to both of them for allow- managers, not directly with ing us to share it publicly in order users. My advice for how to be- to foster discussion. come offshoring-proof is to edu- cate yourself in contextual de- MARCUS RANUM: sign (or any of the other meth- odologies that likewise pre- I had an interesting experience at sumes extensive contact be- the USENIX Security Conference, tween developers and users), and I’d like to share it here for dis- and to complement your com- cussion. Like many conference puting skills with a liberal-arts attendees, I took advantage of the education, which will develop wireless network so I could check your communication skills and my email, update my Web site, etc. your ability to understand non- At virtually every USENIX confer- computing perspectives. ence, someone sets up dsniff and collects passwords as they cross the MAX HAILPERIN wireless, and this latest conference [email protected] was no exception. For the past few http://www.gustavus.edu/+max/ years I’ve basically chosen to ignore the snoopers because, frankly, I hoped they’d grow up and go away.
    [Show full text]
  • Ransomware 2017
    Internet Security Threat Report ISTR Ransomware 2017 An ISTR Special Report Analyst: Dick O’Brien July 2017 Contents Executive summary and Key findings Ransomware: An overview A new breed of threat: WannaCry and Petya Businesses in the crosshairs Affecting the bottom line: Impact of ransomware How ransomware is spread Major ransomware threats Protection and best practices Internet Security Threat Report Contents 3 Executive summary and key findings 28 02 Contain 29 Advanced antivirus engine 5 Ransomware: An overview 29 SONAR behavior engine 8 A new breed of threat: WannaCry 29 Sapient – machine learning and Petya 29 Best practice 9 How WannaCry spread and how it was stopped 29 Ongoing development 9 What is EternalBlue? 29 03 Respond 10 Poor implantation, poor returns 29 Incident Response 10 Petya: Different threat, similar tactics 29 Best practices 10 Who was behind the WannaCry attacks? 30 Appendix: Symantec detections for 11 How Petya was spread common ransomware families 11 Ransomware or wiper? 34 About Symantec 12 Ransomware as a political tool 34 More Information 13 Businesses in the crosshairs 14 Worms are not the only threat 14 Targeted ransomware attacks Figures and Tables 15 Prevention is possible, a cure may not be 6 Ransomware infections by year 6 Ransomware infections by month 16 Affecting the bottom line: Impact of ransomware 6 Impact of WannaCry and Petya outbreaks on monthly infection rate 17 Ransom demands stabilize 6 Monthly ransomware infection numbers 17 Financial and reputational damage without WannaCry and Petya 18
    [Show full text]
  • Ransomware Destructive Attack
    Ransomware Destructive Attack Jay Spreitzer, Vice President, Cyber Threat Management Wells Fargo Bank About - Jay Spreitzer Has over 18 years information security experience. Over the last 10 years as a senior member of a cyber intelligence team at Wells Fargo. Prior to joining Wells Fargo Jay retired from the US Army, after 23 years of service working in various technology and information security roles. He holds a Masters in Information Assurance and Security as well as multiple computer security certifications. 53 What is ransomware? Ransomware is a type of malware that can be covertly installed on a computer without knowledge or intention of the user that restricts access to the infected computer system in some way, and demands that the user pay a ransom to the malware operators to remove the restriction. Some forms of ransomware systematically encrypt files on the system's hard drive, which become difficult or impossible to decrypt without paying the ransom for the encryption key, while some may simply lock the system and display messages intended to coax the user into paying. 54 What is ransomware? Ransomware wreaking havoc in American and Canadian hospitals Tech & Science March 23, 2016 Spike in ransomware spam prompts warnings Technology, March 10, 2015 Ransomware alert issued by US and Canada following recent attacks April 4, 2016, Big paydays force hospitals to prepare for ransomware attacks Tech, April 23, 2016 55 The first known ransomwares and its evolution § AIDS Diskette ransomware discovered in 1989. § Contained a warning message in the letter regarding licensing fee and penalty. § Users were supposed to send a license fee to a PO box in Panama for "PC Cyborg Corporation.” 56 The first known ransomwares and its evolution Creates the file ATTENTION!!!.txt in every folder in which § Gpcoder was ransomware it encoded a file.
    [Show full text]
  • The Definitive Cybersecurity Guide for Directors and Officers
    NAVIGATING THE DIGITAL AGE THE DIGITAL NAVIGATING | BENELUX CONTRIBUTORS • Alan Jenkins, Associate Partner, IBM Security, UK • J.R. Santos, Executive Vice President Research, Cloud Security Alliance, USA • Attila Narin, CTO, EMEA, Palo Alto Networks, Luxembourg • Judith Vieberink, Lawyer, First Lawyers, the Netherlands • Avi Berliner, Manager, PwC, USA • Kelvin Rorive, Delivery Manager Security IT Threat Management, Rabobank, the Netherlands • Chris Bray, Partner, Heidrick & Struggles, UK • Marcel Van Eemeren, CEO, ON2IT, the Netherlands • Christophe Crous, Head of Security, Proximus, Belgium • Mark Hughes, President, BT Security, BT Global Services, UK • Elena Kvochko, CIO, Group Security Function, Barclays, USA • Mark McLaughlin, CEO, Palo Alto Networks, USA • Fred Streefland, Senior Product Marketing Manager, EMEA, Palo Alto Networks, the Netherlands; former • Neelie Kroes, former Vice President to the European CISO, LeaseWeb Commission, the Netherlands • Gavin Colman, Partner, Heidrick & Struggles, UK • Peter Mesker, CTO, SecureLink, the Netherlands • Gilles Orringe, Partner, Heidrick & Struggles, UK • Polo van der Putt, Lawyer, Vondst Advocaten, the Netherlands THE DEFINITIVE CYBERSECURITY GUIDE • Graham Bolton, Chairman, Institute for Software Quality (IfSQ), UK • Puck Polter, Lawyer, Vondst Advocaten, the Netherlands FOR DIRECTORS AND OFFICERS • Greg Day, Vice President and Regional Chief Security • Raoul Vernède, Information Security Officer, Wageningen Officer, EMEA, Palo Alto Networks, UK University and Research, the Netherlands
    [Show full text]
  • Jumanji: the Case for Dynamic NUCA in the Datacenter
    Jumanji: The Case for Dynamic NUCA in the Datacenter Brian C. Schwedock Nathan Beckmann Carnegie Mellon University Carnegie Mellon University [email protected] [email protected] Abstract—The datacenter introduces new challenges for com- Core LLC bank Thread Lat-crit Core LLC bank Thread Lat-crit puter systems around tail latency and security. This paper argues that dynamic NUCA techniques are a better solution to these challenges than prior cache designs. We show that dynamic NUCA designs can meet tail-latency deadlines with much less cache space than prior work, and that they also provide a natural defense against cache attacks. Unfortunately, prior dynamic NUCAs have missed these opportunities because they focus exclusively on reducing data movement. (a) Jigsaw [6,8]. (b) Jumanji. We present Jumanji, a dynamic NUCA technique designed Fig. 1: Dynamic NUCA has natural advantages in the datacenter for tail latency and security. We show that prior last-level because it meets performance targets with fewer resources and cache designs are vulnerable to new attacks and offer imperfect physically isolates data from attackers. (a) However, Jigsaw, a performance isolation. Jumanji solves these problems while signif- state-of-the-art D-NUCA, is oblivious to tail latency and security, icantly improving performance of co-running batch applications. leading to missed deadlines and potential cache side channels. Moreover, Jumanji only requires lightweight hardware and a few (b) With simple changes, Jumanji enforces tail-latency deadlines simple changes to system software, similar to prior D-NUCAs. At and defends side channels at similar performance to Jigsaw. 20 cores, Jumanji improves batch weighted speedup by 14% on average, vs.
    [Show full text]
  • Analysis of Ransomware on Windows Platform
    IJCSNS International Journal of Computer Science and Network Security, VOL.20 No.6, June 2020 21 Analysis of Ransomware on Windows platform Adel Hamdan Mohammad Computer Science Department The world Islamic Sciences and Education University Amman-Jordan Summary dataset used in this research. Section four talks about Ransomware is a very serious problem which all organization related studies to this research. In section five, the author and individual may face. No doubt that ransomware cost demonstrates his experiments and analysis. Finally, in individual an organization billions of dollars. A lot of researchers section six, the author talks about his conclusion and talk about ransomware and its effect. The number of researches future works. that talk about ransomware still needs more investigation. In this research, the author analyzes the impact of ransomware only on windows platforms. The author select windows platform since windows is widely spread and used. Analyzing of ransomware 2. Ransomware Analysis is done based on analyzing the behavior of selected ransomware families. The author monitors the behavior of ransomware and There are several types of ransomware. some researcher which files are created during the infection process. The author says that ransomware has more than 100 forms and also demonstrates the encryption techniques used by patterns. Other researcher says that ransomware has three ransomware families. Finally, the author notes that protecting types and according to other researcher ransomware has Windows operating system is highly possible by monitoring only two main forms [4,5]. Most security and anti-virus system files and registry entry. companies tend to divide ransomware into two types Key words: which are crypto ransomware and locker ransomware Ransomware, encryption, ransomware behavior.
    [Show full text]
  • White Paper Template 9-10-15
    Comparative Analysis of Surveillance Laws and Practices in Latin America Katitza Rodríguez Pereda October 2016 1 The lead author of the “Comparative Analysis of Surveillance Laws and Practices in Latin America” is Electronic Frontier Foundation's (EFF) International Rights Director, Katitza Rodríguez Pereda. The legal review was done by EFF's Civil Liberties Director, David Greene. The technical review was done by EFF's Senior Staff Technologist, Seth Schoen. EFF's International Project Manager, Kim Carlson edited and formatted this report. EFF would like to thank Juan Camilo Rivera who consulted for EFF on this project, and Ana María Acosta, EFF Google Policy Fellow (2016), for their contributions to this report. EFF would like to thank the following individuals for their valuable input, assistance, and feedback in the preparation of this paper: Agustina Del Campo, Centro de Estudios en Libertad de Expresión y Acceso a la Información (Argentina) Ana Tuduri (Uruguay) Carolina Botero, Fundación Karisma (Colombia) Daniela Schnidrig, Global Partners Digital (Argentina) Dennys Antonialli, InternetLab (Brazil) Fabrizio Scrollini (Uruguay) Jacqueline Abreu, Internet Lab (Brazil) Jorge Gabriel Jímenez (Guatemala) Juan Carlos Lara, Derechos Digitales (Chile, Latin America) Juan Diego Castañeda Gómez, Fundación Karisma (Colombia) Leandro Ucciferri, Asociación por los Derechos Civiles (Argentina) Luciana Peri, Fundación Acceso (Central America) Luis Fernando García, R3D (Mexico) Maricarmen Sequera, TEDIC (Paraguay) Marlon Hernández Anzora (El Salvador)
    [Show full text]