Teradata Tape Encryption

Total Page:16

File Type:pdf, Size:1020Kb

Teradata Tape Encryption A Seat Belt for Data Practical Use of Encryption in Teradata Systems Jim Browning Enterprise Security Architect Teradata Labs #TDPARTNERS16 Sept 11,2016 GEORGIA WORLD CONGRESS CENTER “Encryption is the equivalent of a seat belt for data.” -- Andy Cordial, Managing Director, Origin Storage 2 Agenda • Key Encryption Drivers • Cryptographic Technology Primer • Important Considerations • Use of Encryption in Teradata Systems 3 Drivers for the Use of Encryption Types of Data Requiring Protection Credit Card Information Protected Health Information > Credit Card Numbers (PAN) > Identifiable Patient Data > Service Codes > Medical Record Numbers > Expiration Dates Corporate Financial Data Personal Identifying Information > Non-public Information > Social Security Numbers > Tax Identifiers Human Resources Data > Driver’s License Numbers > Payroll Information > Date of Birth > Performance Ratings Consumer Financial Data Customer and Prospect Data > Account Numbers Trade Secrets and Intellectual > PINs Property 4 Drivers for the Use of Encryption Standards and Regulations • Payment Card Industry (PCI) Data Security Standard • HIPAA Privacy Rule • U.S. State Security Breach Notification Laws • EU General Data Protection Regulation (GDPR) 5 Agenda • Key Encryption Drivers • Cryptographic Technology Primer • Important Considerations • Use of Encryption in Teradata Systems 6 “Any sufficiently advanced technology is indistinguishable from magic.” -- Sir Arthur C. Clarke 7 Symmetric Key Cryptography • Symmetric Key Cryptography – Cryptography in which the same key is used for encryption and decryption • Single Key Cryptography • Secret Key Cryptography • Shared Key Cryptography Hello World! B$s70x2G0&vC1lZA Hello World! 8 Symmetric Key Cryptography • Symmetric Key Algorithms – Data Encryption Standard (DES) – Triple DES (3DES) – Blowfish – Advanced Encryption Standard (AES) – Twofish – International Data Encryption Standard (IDEA) – RC5 9 Symmetric Key Cryptography • Advanced Encryption Standard (AES) – Standardized by FIPS in 2001 (FIPS Pub 197) – Uses 128-bit, 196-bit, or 256-bit keys – Operates on 16-byte data blocks – De facto standard for commercial and government applications Hello World! Js7%qaQ1b8$@nPl0 Hello World! 10 Asymmetric Key Cryptography • Asymmetric Key Cryptography – Cryptography in which a pair of mathematically related keys are used for encryption and decryption • Public Key Cryptography • Data encrypted using one key (e.g., public key) can only be decrypted using the other key (e.g., private key) in the pair - and vice versa Hello World! 9vDf4$1j&Fqo*cR1 Hello World! 11 Asymmetric Key Cryptography • Asymmetric Key Algorithms – RSA (Rivest Shamir Adleman) – Digital Signature Algorithm (DSA) – Elliptic Curve Cryptography (ECC) – RSA and DSA are used to provide confidentiality for secure communications protocols such as Transport Layer Security (TLS) and Secure Shell (SSH) 12 Hash Cryptography • Hash Cryptography – Cryptography in which a mathematical algorithm is applied to produce a condensed representation of data • No key is used • Hash output is a fixed length - regardless of the size of input data • It is computationally infeasible to find the data which corresponds to a given hash, or to find different data that produces the same hash • Hash is one-way; plain text cannot be recreated from the hash Js7%qaQ1b8$@nPl0 Hello World! 9vDf4$1j&Fqo*cR1 B$s70x2G0&vC1lZA 13 Hash Cryptography • Hash Cryptographic Algorithms – Message Digest Algorithm 5 (MD5) • Produces 128-bit hash – Secure Hash Algorithm (SHA) • SHA-1: Produces 160-bit hash • SHA-256: Produces 256-bit hash • SHA-512: Produces 512-bit hash – Applications for hashing • Password storage • Message integrity • Digital signatures 14 Secret Key Negotiation • Diffie-Hellman Key Negotiation Protocol – Allows client and server to agree on a secret key over an insecure communication channel – Protocol uses two public values • p is a prime number • g is an integer less than p with the property that for every number n between 1 and p-1 inclusive, there is a power k of g such that n = gk mod p – Security is provided by the discrete logarithm problem • It is computationally infeasible to calculate the shared secret key when the prime p is sufficiently large 15 Secure Communications Protocols • Transport Layer Security (TLS) – An industry standard protocol for transmitting data in a secure manner over a network • Supersedes older Secure Sockets Layer (SSL) protocol – Defines methods for authentication, data encryption, and message integrity – Underlies protocols such as https, ldaps, ftps, pop3s, etc. • Secure Shell (SSH) – Establishes a cryptographic tunnel between two network hosts – Secures remote logons, file transfers and remote command executions SSH Client SSH Server 16 Agenda • Key Encryption Drivers • Cryptographic Technology Primer • Important Considerations • Use of Encryption in Teradata Systems 17 “The only truly secure system is one that is powered off, cast in a block of concrete and sealed in a lead-lined room with armed guards.” -- Dr. Eugene Spafford, Professor of Computer Science, Purdue University 18 Important Considerations • Performance • Table Size Expansion • Encryption Key Security • User/Application Transparency 19 Performance • Cryptographic operations add performance overhead – Function of hardware generation and speed of processors • Cryptographic operations are CPU-intensive – Function of cryptographic algorithm and key strength – Function of size of data and/or number of columns encrypted – Function of the characteristics of queries • Encrypted indexes, range searches, joins on encrypted columns – Function of the frequency of access – Function of table skew (affects parallel execution of cryptographic functions) 20 Performance Millions Crypto Operations per Second AES-128 AES-192 AES-256 Hundreds 3DES Size of Data 21 Table Size Expansion • Encrypted data (ciphertext) requires more storage space than plain text data – Function of the size of original columns • Padding required for the selected cryptographic algorithm (e.g., 8-byte block, 16- byte block) Original Data Padding (2 bytes) (14 bytes) Original Data Padding (12 bytes) (4 bytes) Ciphertext (16 bytes) – Function of the number of columns encrypted 22 – Loss of multi-value compression (MVC) benefits Encryption Key Security • Encryption keys must be securely managed – Strong keys should be securely and randomly generated – Keys must be protected wherever stored (disk or memory) – Keys should be distributed in a secure manner – Access to keys should be restricted – Keys should be periodically rotated – Keys should be archived with encrypted data “Random numbers should not be generated with a method chosen at random.” -- Donald E. Knuth, The Art of Computer Programming, Volume 2: Seminumerical Algorithms 23 User/Application Transparency • Use of encryption should be largely transparent to users and applications – No transparency issues with encryption of network traffic – Cryptographic operations on table data can be largely transparent through the use of views and triggers • Flexibility needed to directly invoke functions as required to optimize queries – Use of encrypted data types further improves transparency • Limits on type functionality often restrict use – e.g., no statistics collection, cannot be part of an index 24 Agenda • Key Encryption Drivers • Cryptographic Technology Primer • Important Considerations • Use of Encryption in Teradata Systems 25 “Security doesn't matter until all of a sudden it does - and then it *really* matters.” -- Ben Adida, Mozilla Architect 26 Use of Encryption within Teradata Systems • Securing Remote Support Connectivity • Securing Network Connections • Securing Stored Passwords • Securing Stored Data • Securing Backups and Archives 27 Secure Remote Support Connectivity Teradata ServiceConnectTM • No Virtual Private Network (VPN) or public IP address required • Firewall-friendly – all connections initiated from Service Workstation (SWS) on customer side • Connections secured using HTTPS and 128-bit TLS encryption Customer Teradata ServiceConnect™ ServiceConnect Enhanced Internet Policy Server Enterprise Optional 28 Secure Remote Support Connectivity Teradata ServiceConnectTM • Outbound Connections – TLS port 443 • Remote connectivity • Teradata Vital Infrastructure (TVI) alerts, events, and reports • Crashdump uploads • ServiceConnectTM Enhanced – Axeda Policy Server • Enforce restrictions on remote support activities performed by Teradata – Logon access – File upload/download – Command execution • Audit remote support activities performed by Teradata 29 Network Traffic Encryption • Network Traffic Encryption – Provides confidentiality for sensitive data when transmitted over untrusted networks – Protects against compromise by network sniffers – Examples • HTTP over TLS to secure communications to web services • LDAP over TLS to secure communications to authentication services • Teradata Generic Security Services (TDGSS) to secure communications between Teradata Clients and Database 30 Network Traffic Encryption HTTP over TLS (https) • Secures browser-based connections to web-based services – TDput – port 8443 • Use TDput AllowedCiphers file to manage encryption algorithms allowed for connections – Viewpoint – port 443 or 9443 • Use Certificates portlet to create and install TLS certificate – Create and install self-signed certificate – Create certificate signing request and install CA-signed certificate • Use General portlet to enable Require Access
Recommended publications
  • Cryptography
    56 Protecting Information With Cryptography Chapter by Peter Reiher (UCLA) 56.1 Introduction In previous chapters, we’ve discussed clarifying your security goals, determining your security policies, using authentication mechanisms to identify principals, and using access control mechanisms to enforce poli- cies concerning which principals can access which computer resources in which ways. While we identified a number of shortcomings and prob- lems inherent in all of these elements of securing your system, if we re- gard those topics as covered, what’s left for the operating system to worry about, from a security perspective? Why isn’t that everything? There are a number of reasons why we need more. Of particular im- portance: not everything is controlled by the operating system. But per- haps you respond, you told me the operating system is all-powerful! Not really. It has substantial control over a limited domain – the hardware on which it runs, using the interfaces of which it is given control. It has no real control over what happens on other machines, nor what happens if one of its pieces of hardware is accessed via some mechanism outside the operating system’s control. But how can we expect the operating system to protect something when the system does not itself control access to that resource? The an- swer is to prepare the resource for trouble in advance. In essence, we assume that we are going to lose the data, or that an opponent will try to alter it improperly. And we take steps to ensure that such actions don’t cause us problems.
    [Show full text]
  • PCI Assessment Evidence of PCI Policy Compliance
    PCI Assessment Evidence of PCI Policy Compliance CONFIDENTIALITY NOTE: The information contained in this report document is for the Prepared for: exclusive use of the client specified above and may contain confidential, privileged and non-disclosable information. If the recipient of this report is not the client or Prospect or Customer addressee, such recipient is strictly prohibited from reading, photocopying, distributing or otherwise using this report or its contents in any way. Prepared by: Your Company Name Evidence of PCI Policy Compliance PCI ASSESSMENT Table of Contents 1 - Overview 1.1 - Security Officer 1.2 - Overall Risk 2 - PCI DSS Evidence of Compliance 2.1 - Install and maintain firewall to protect cardholder data 2.1.1.1 - Requirements for firewall at each Internet connections and between DMZ and internal network zone 2.1.1.2 - Business justification for use of all services, protocols and ports allowed 2.1.2 - Build firewall and router configurations that restrict connections between untrusted networks and the cardholder data environment 2.1.2.1 - Restrict inbound and outbound to that which is necessary for the cardholder data environment 2.1.2.3 - Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet 2.1.2.4 - Implement stateful inspection (also known as dynamic packet filtering) 2.1.2.5 - Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet 2.2 - Prohibition of vendor-supplied default password for systems and security parameters 2.2.1
    [Show full text]
  • Self-Encrypting Deception: Weaknesses in the Encryption of Solid State Drives
    Self-encrypting deception: weaknesses in the encryption of solid state drives Carlo Meijer Bernard van Gastel Institute for Computing and Information Sciences School of Computer Science Radboud University Nijmegen Open University of the Netherlands [email protected] and Institute for Computing and Information Sciences Radboud University Nijmegen Bernard.vanGastel@{ou.nl,ru.nl} Abstract—We have analyzed the hardware full-disk encryption full-disk encryption. Full-disk encryption software, especially of several solid state drives (SSDs) by reverse engineering their those integrated in modern operating systems, may decide to firmware. These drives were produced by three manufacturers rely solely on hardware encryption in case it detects support between 2014 and 2018, and are both internal models using the SATA and NVMe interfaces (in a M.2 or 2.5" traditional form by the storage device. In case the decision is made to rely on factor) and external models using the USB interface. hardware encryption, typically software encryption is disabled. In theory, the security guarantees offered by hardware encryp- As a primary example, BitLocker, the full-disk encryption tion are similar to or better than software implementations. In software built into Microsoft Windows, switches off software reality, we found that many models using hardware encryption encryption and completely relies on hardware encryption by have critical security weaknesses due to specification, design, and implementation issues. For many models, these security default if the drive advertises support. weaknesses allow for complete recovery of the data without Contribution. This paper evaluates both internal and external knowledge of any secret (such as the password).
    [Show full text]
  • Cryptographic Control Standard, Version
    Nuclear Regulatory Commission Office of the Chief Information Officer Computer Security Standard Office Instruction: OCIO-CS-STD-2009 Office Instruction Title: Cryptographic Control Standard Revision Number: 2.0 Issuance: Date of last signature below Effective Date: October 1, 2017 Primary Contacts: Kathy Lyons-Burke, Senior Level Advisor for Information Security Responsible Organization: OCIO Summary of Changes: OCIO-CS-STD-2009, “Cryptographic Control Standard,” provides the minimum security requirements that must be applied to the Nuclear Regulatory Commission (NRC) systems which utilize cryptographic algorithms, protocols, and cryptographic modules to provide secure communication services. This update is based on the latest versions of the National Institute of Standards and Technology (NIST) Guidance and Federal Information Processing Standards (FIPS) publications, Committee on National Security System (CNSS) issuances, and National Security Agency (NSA) requirements. Training: Upon request ADAMS Accession No.: ML17024A095 Approvals Primary Office Owner Office of the Chief Information Officer Signature Date Enterprise Security Kathy Lyons-Burke 09/26/17 Architecture Working Group Chair CIO David Nelson /RA/ 09/26/17 CISO Jonathan Feibus 09/26/17 OCIO-CS-STD-2009 Page i TABLE OF CONTENTS 1 PURPOSE ............................................................................................................................. 1 2 INTRODUCTION ..................................................................................................................
    [Show full text]
  • Unlocking the Fifth Amendment: Passwords and Encrypted Devices
    Fordham Law Review Volume 87 Issue 1 Article 9 2018 Unlocking the Fifth Amendment: Passwords and Encrypted Devices Laurent Sacharoff University of Arkansas School of Law, Fayetteville Follow this and additional works at: https://ir.lawnet.fordham.edu/flr Part of the Constitutional Law Commons, and the Criminal Procedure Commons Recommended Citation Laurent Sacharoff, Unlocking the Fifth Amendment: Passwords and Encrypted Devices, 87 Fordham L. Rev. 203 (2018). Available at: https://ir.lawnet.fordham.edu/flr/vol87/iss1/9 This Article is brought to you for free and open access by FLASH: The Fordham Law Archive of Scholarship and History. It has been accepted for inclusion in Fordham Law Review by an authorized editor of FLASH: The Fordham Law Archive of Scholarship and History. For more information, please contact [email protected]. UNLOCKING THE FIFTH AMENDMENT: PASSWORDS AND ENCRYPTED DEVICES Laurent Sacharoff* Each year, law enforcement seizes thousands of electronic devices— smartphones, laptops, and notebooks—that it cannot open without the suspect’s password. Without this password, the information on the device sits completely scrambled behind a wall of encryption. Sometimes agents will be able to obtain the information by hacking, discovering copies of data on the cloud, or obtaining the password voluntarily from the suspects themselves. But when they cannot, may the government compel suspects to disclose or enter their password? This Article considers the Fifth Amendment protection against compelled disclosures of passwords—a question that has split and confused courts. It measures this right against the legal right of law enforcement, armed with a warrant, to search the device that it has validly seized.
    [Show full text]
  • Pgpfone Pretty Good Privacy Phone Owner’S Manual Version 1.0 Beta 7 -- 8 July 1996
    Phil’s Pretty Good Software Presents... PGPfone Pretty Good Privacy Phone Owner’s Manual Version 1.0 beta 7 -- 8 July 1996 Philip R. Zimmermann PGPfone Owner’s Manual PGPfone Owner’s Manual is written by Philip R. Zimmermann, and is (c) Copyright 1995-1996 Pretty Good Privacy Inc. All rights reserved. Pretty Good Privacy™, PGP®, Pretty Good Privacy Phone™, and PGPfone™ are all trademarks of Pretty Good Privacy Inc. Export of this software may be restricted by the U.S. government. PGPfone software is (c) Copyright 1995-1996 Pretty Good Privacy Inc. All rights reserved. Phil’s Pretty Good engineering team: PGPfone for the Apple Macintosh and Windows written mainly by Will Price. Phil Zimmermann: Overall application design, cryptographic and key management protocols, call setup negotiation, and, of course, the manual. Will Price: Overall application design. He persuaded the rest of the team to abandon the original DOS command-line approach and designed a multithreaded event-driven GUI architecture. Also greatly improved call setup protocols. Chris Hall: Did early work on call setup protocols and cryptographic and key management protocols, and did the first port to Windows. Colin Plumb: Cryptographic and key management protocols, call setup negotiation, and the fast multiprecision integer math package. Jeff Sorensen: Speech compression. Will Kinney: Optimization of GSM speech compression code. Kelly MacInnis: Early debugging of the Win95 version. Patrick Juola: Computational linguistic research for biometric word list. -2- PGPfone Owner’s
    [Show full text]
  • Case Study on the Official Scripts Electronic Applications in Bantul)
    I.J. Information Engineering and Electronic Business, 2017, 4, 1-6 Published Online July 2017 in MECS (http://www.mecs-press.org/) DOI: 10.5815/ijieeb.2017.04.01 The Implementation of Pretty Good Privacy in eGovernment Applications (Case Study on the Official Scripts Electronic Applications in Bantul) Didit Suprihanto Department of Electrical Engineering Universitas Mulawarman, Kalimantan Timur, Indonesia, 75123 Email: [email protected] Tri Kuntoro Priyambodo Department of Computer Sciences & Electronics, Universitas Gadjah Mada, Yogyakarta, Indonesia, 55281 Corresponding Author Email: [email protected] Abstract—eGovernment application has evolved from the world [1]. The United Nations‘ global survey reports simply appearing as a website providing news and some ICT indicators that point to the measure of how far information, to the application that provides various a nation has gone in the implementation of e-governance services through online transactions. Provision of online such as: 1.E-readiness, 2.Web measure index, 3. transactions require the effectively and safely service, so Telecommunications infrastructure index, 4. Human the users can make sure that the entry data is secure and capital index, 5. E-participation index[2] will not be used by other parties which are not authorized. Information security is a major factor in the service of Security is also necessary for the service provider side of eGovernment. The using of the host to host in previous online transactions, it is necessary to keep the system, and services of eGovernment is considered as lacking in the data transactions sent through the communications security. Therefore, it needs more security to serve clients media and the data stored in the database are secured.
    [Show full text]
  • I2P, the Invisible Internet Projekt
    I2P, The Invisible Internet Projekt jem September 20, 2016 at Chaostreff Bern Content 1 Introduction About Me About I2P Technical Overview I2P Terminology Tunnels NetDB Addressbook Encryption Garlic Routing Network Stack Using I2P Services Using I2P with any Application Tips and Tricks (and Links) Conclusion jem | I2P, The Invisible Internet Projekt | September 20, 2016 at Chaostreff Bern Introduction About Me 2 I Just finished BSc Informatik at BFH I Bachelor Thesis: "Analysis of the I2P Network" I Focused on information gathering inside and evaluation of possible attacks against I2P I Presumes basic knowledge about I2P I Contact: [email protected] (XMPP) or [email protected] (GPG 0x28562678) jem | I2P, The Invisible Internet Projekt | September 20, 2016 at Chaostreff Bern Introduction About I2P: I2P = TOR? 3 Similar to TOR... I Goal: provide anonymous communication over the Internet I Traffic routed across multiple peers I Layered Encryption I Provides Proxies and APIs ...but also different I Designed as overlay network (strictly separated network on top of the Internet) I No central authority I Every peer participates in routing traffic I Provides integrated services: Webserver, E-Mail, IRC, BitTorrent I Much smaller and less researched jem | I2P, The Invisible Internet Projekt | September 20, 2016 at Chaostreff Bern Introduction About I2P: Basic Facts 4 I I2P build in Java (C++ implementation I2Pd available) I Available for all major OS (Linux, Windows, MacOS, Android) I Small project –> slow progress, chaotic documentation,
    [Show full text]
  • Conditional Pseudonymity in Vehicular Ad Hoc Networks
    Diplom Thesis Faculty of Engineering and Computer Science Ulm University Conditional Pseudonymity in Vehicular Ad Hoc Networks Florian Marcus Schaub presented on November 13, 2008 Supervisors Prof. Dr.-Ing. Michael Weber Dr. Frank Kargl Advisor Zhendong Ma Faculty of Engineering and Computer Science, Ulm University James-Franck-Ring, 89081 Ulm, Germany This thesis has been prepared in the summer semester 2008 as a requirement for the completion of the Diplom course Medieninformatik at Ulm University. Cover photo: Night blur by Mando Gomez http://www.mandolux.com Printed on November 9, 2008. Some rights reserved. This work is licensed under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Germany License. To view a copy of this license, visit http://creativecommons.org/ licenses/by-nc-nd/3.0/de/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. Computer Science is no more about computers than astronomy is about telescopes. Edsger W. Dijkstra Contents 1 Introduction 1 2 Problem Analysis 5 2.1 Characteristics of Vehicular Ad Hoc Networks . 5 2.2 Security and Privacy in Vehicular Ad Hoc Networks . 9 2.3 Conditional Pseudonymity . 14 2.4 Summary . 18 3 Requirements for Privacy in VANETs 19 3.1 Assumptions . 20 3.2 General VANET Requirements . 21 3.3 Pseudonym Requirements . 23 3.4 Authentication Requirements . 28 3.5 Summary . 30 4 Privacy in other Domains 33 4.1 Health Care . 34 4.2 E-Government . 39 4.3 E-Commerce . 43 4.4 Internet . 51 4.5 Ad Hoc Networks . 59 4.6 Summary .
    [Show full text]
  • Modern End-To-End Encrypted Messaging for the Desktop
    Die approbierte Originalversion dieser Diplom-/ Masterarbeit ist in der Hauptbibliothek der Tech- nischen Universität Wien aufgestellt und zugänglich. http://www.ub.tuwien.ac.at The approved original version of this diploma or master thesis is available at the main library of the Vienna University of Technology. http://www.ub.tuwien.ac.at/eng Modern End-to-End Encrypted Messaging for the Desktop DIPLOMARBEIT zur Erlangung des akademischen Grades Diplom-Ingenieur im Rahmen des Studiums Software Engineering and Internet Computing eingereicht von Richard Bayerle Matrikelnummer 1025259 an der Fakultät für Informatik der Technischen Universität Wien Betreuung: Privatdozent Dipl.Ing. Mag. Dr. Edgar Weippl Mitwirkung: Dr. Martin Schmiedecker Wien, 2. Oktober 2017 Richard Bayerle Edgar Weippl Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel. +43-1-58801-0 www.tuwien.ac.at Modern End-to-End Encrypted Messaging for the Desktop DIPLOMA THESIS submitted in partial fulfillment of the requirements for the degree of Diplom-Ingenieur in Software Engineering and Internet Computing by Richard Bayerle Registration Number 1025259 to the Faculty of Informatics at the TU Wien Advisor: Privatdozent Dipl.Ing. Mag. Dr. Edgar Weippl Assistance: Dr. Martin Schmiedecker Vienna, 2nd October, 2017 Richard Bayerle Edgar Weippl Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel. +43-1-58801-0 www.tuwien.ac.at Erklärung zur Verfassung der Arbeit Richard Bayerle Seestraße 67 78315 Radolfzell am Bodensee Deutschland Hiermit erkläre ich, dass ich diese Arbeit selbständig verfasst habe, dass ich die verwen- deten Quellen und Hilfsmittel vollständig angegeben habe und dass ich die Stellen der Arbeit – einschließlich Tabellen, Karten und Abbildungen –, die anderen Werken oder dem Internet im Wortlaut oder dem Sinn nach entnommen sind, auf jeden Fall unter Angabe der Quelle als Entlehnung kenntlich gemacht habe.
    [Show full text]
  • Analysis of the I2P Network
    Analysis of the I2P Network Degree programme: BSc in Computer Science | Specialisation: IT-Security Thesis advisor: Prof. Dr. Emmanuel Benoist Expert: Daniel Voisard (BAKOM) Providing anonymous online communication is challenging and an 1 important task. Similar to the well-known and -researched TOR project, I2P (Invisible Internet Project) aims to provide this inside its own network. But how secure and protected can a user feel when using I2P? The main objectives of this thesis were to create I2P Observer, a Java program which gathers and publishes information about the I2P network, and to evaluate possible attacks on the software. The I2P Network view pages with accurate data and monthly ones I2P aims to provide anonymous communication bet- where the average for each day is computed. I2P ween participating systems inside an overlay network, Observer is also easily configurable to collect more separated from other Internet traffic. It is written in and more accurate data. Java with versions for Windows, Linux and Mac, pro- viding HTTP- and HTTPS-Proxies for browsing and Theoretical Attacks on I2P APIs to adapt applications to communicate over I2P. The main motivation for this thesis was an evaluation Multiple layers of strong cryptography are used to pro- of I2P’s security, which was researched with 4 dif- tect the content of packets and a mechanism called ferent approaches: Garlic Routing, where multiple messages for the same − Impersonation of a service: Can a user be redirec- destination can be encapsulated, to hide meta data. ted to a malicious server without noticing it? Jens Henning Müller Its NetDB, a database distributed across participating A Clickjacking attack which allows this under cer- [email protected] peers – so called floodfil routers – contains all infor- tain circumstances was found.
    [Show full text]
  • Prying Open Pandora's Box: KCI Attacks Against
    Prying open Pandora’s box: KCI attacks against TLS Clemens Hlauschek, Markus Gruber, Florian Fankhauser, Christian Schanes RISE – Research Industrial Systems Engineering GmbH {clemens.hlauschek, markus.gruber, florian.fankhauser, christian.schanes}@rise-world.com Abstract and implementations of the protocol: their utility is ex- tremely limited, their raison d’ˆetre is practically nil, and Protection of Internet communication is becoming more the existence of these insecure key agreement options common in many products, as the demand for privacy only adds to the arsenal of attack vectors against cryp- in an age of state-level adversaries and crime syndi- tographically secured communication on the Internet. cates is steadily increasing. The industry standard for doing this is TLS. The TLS protocol supports a multi- 1 Introduction tude of key agreement and authentication options which provide various different security guarantees. Recent at- The TLS protocol [1, 2, 3] is probably the most tacks showed that this plethora of cryptographic options widely used cryptographic protocol on the Internet. in TLS (including long forgotten government backdoors, It is designed to secure the communication between which have been cunningly inserted via export restric- client/server applications against eavesdropping, tamper- tion laws) is a Pandora’s box, waiting to be pried open by ing, and message forgery, and it also provides additional, heinous computer whizzes. Novel attacks lay hidden in optional security properties such as client authentica- plainsight. Parts of TLS areso oldthat theirfoul smell of tion. TLS is an historically grown giant: its predecessor, rot cannot be easily distinguished from the flowery smell SSL [4,5], was developed more than 20 years ago.
    [Show full text]