DOCSLIB.ORG

The Need for Certainty

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Need for Certainty ® TRUSTLEAP The Need For Certainty Mathematically-Proven Unbreakable Security www.trustleap.com This document is aimed at helping people to understand the TrustLeap technology. A cryptographic oracle (where users chose and submit the plaintext: an ASCII classic English book and a sentence that they type, an encryption key, the standard encryption algorithm to secure like AES or RC4, and get the ciphertext, with the sentence injected at a random position that they must guess to demonstrate that teir plaintext attack is successful) as well as further information regarding the internals of TWD Industries AG's technology are available under a proper NDA, to selected partners. TrustLeap 2 | Copyright © 2013, TWD Industries AG. All rights reserved. I. Definition, Promotion, Reality TrustLeap 3 | Copyright © 2013, TWD Industries AG. All rights reserved. The Oxford Dictionary Encryption: to convert (information or data) into a code, especially to prevent unauthorized access. Origin: 1950s (in the US), from English 'in' and Greek kruptos 'hidden'. TrustLeap 4 | Copyright © 2013, TWD Industries AG. All rights reserved. Promotion “no one ever lost money to an attack on a properly designed [standard] cryptosystem” – Peter Gutmann TrustLeap 5 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2007 – RC4 / WEP 802.11 wireless standard Used to Steal 45 millions of Credit-Card Numbers Legal Costs: $40,900,000 TrustLeap 6 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2010 – A5-1 / GSM Phones wireless standard Spy, Trace and Impersonate Billion of Mobile Phone Users. – Karsten Nohl TrustLeap 7 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2011 – GPRS / Web - Mail wireless standard Spy, Trace and Impersonate Billion of Mobile Phone Users. – Karsten Nohl TrustLeap 8 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2013 – 3DES / SIM Card Javacard standard Steal data, Spy, Trace and Impersonate Billion of Mobile Phone Users. – Karsten Nohl TrustLeap 9 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2013 – Design of $1.5 trillion F-35 Stolen From ...Pentagon TrustLeap 10 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2013 – 96-bit secret key RFID car transponder Steal VW, Audi, Bentley, Lamborghini & Porsche cars as Megamos Crypto is broken. – Flavio Garcia TrustLeap 11 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2013 – Switzerland e-VOTE Forgery They know since 2002 what they do wrong... but 2012 audits still certify a flawed system. – advtools.com TrustLeap 12 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality Standard Encryption Is Broken, Routinely. But Experts Keep Saying: “It's Very Safe” TrustLeap 13 | Copyright © 2013, TWD Industries AG. All rights reserved. Promotion “Cryptosystem failure is orders of magnitude below any other risk.” – Peter Gutmann TrustLeap 14 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2012 – X.509 Certificates “the Flame malware has been signed by forged PKI certificates to appear as if it was produced by... Microsoft.” TrustLeap 15 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality The FLAME Malware Active Since Year 2000 (!) Exploiting Hashing Collisions Breaking “Trusted” PKI Standard TrustLeap 16 | Copyright © 2013, TWD Industries AG. All rights reserved. Promotion “SSL Authenticate-then-encrypt is Provably-Secure.” – Hugo Krawczyk TrustLeap 17 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality SSL & TLS standards 2011 “BEAST exploits CBC IVs” 2012 “CRIME exploits compression” 2013 “LUCKY13 exploits decryption” TrustLeap 18 | Copyright © 2013, TWD Industries AG. All rights reserved. Promotion “AES 256-bit Is Safe Even For TOP-SECRET Information.” – U.S. Government TrustLeap 19 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2011 - AES standard “AES Broken 5x Faster Than By Brute Force; Cause: Small Key Space.” – Andrey Bogdanov TrustLeap 20 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2012 - AES standard “OpenSSL Uses AES Tables For Speed, Leaking Many Key Bits” – Fraunhofer Research TrustLeap 21 | Copyright © 2013, TWD Industries AG. All rights reserved. Promotion “It Would Take Millions Of Years To Break Standard Encryption.” TrustLeap 22 | Copyright © 2013, TWD Industries AG. All rights reserved. Reality 2012 – RSA SecurID “It Takes 13 Minutes To Extract A Secret Key From AES-based RSA SecurID 800 Dongles” – INRIA TrustLeap 23 | Copyright © 2013, TWD Industries AG. All rights reserved. II. Discussion TrustLeap 24 | Copyright © 2013, TWD Industries AG. All rights reserved. The Myth of “Strong” Security There Is No Such A Thing Like: ● “Strong Authentication” ● “Strong Encryption” ● “Strong Security” > Crypto Is Either SAFE or UNSAFE. TrustLeap 25 | Copyright © 2013, TWD Industries AG. All rights reserved. Why Standards Fail? Encryption Keys Are Generated By: ● PSEUDO-RANDOM Number Generators ● OSes Do It Wrong (a recurring issue) ● Developers Told To Trust OSes or CPUs. > Crypto Keys Are Known In Advance. TrustLeap 26 | Copyright © 2013, TWD Industries AG. All rights reserved. Why Standards Fail? File Formats & Network Protocols Use: ● “Magic Words” In File Headers, Protocols (“PDF%”, “%PNG”, “HTTP/1.1”, etc.) ● Padding (often NULL bytes) > Leading To Known Plaintext Attacks. TrustLeap 27 | Copyright © 2013, TWD Industries AG. All rights reserved. Why Standards Fail? AES(input, key) < 2256 (AES < Key Space) AES(iv, key) = System of Equations AES(in, key) = AES(AES(i(n-1), key), key) 2 AES BLOCKS ENOUGH TO FIND KEY > ARITHMETIC, NOT “RANDOM” data. TrustLeap 28 | Copyright © 2013, TWD Industries AG. All rights reserved. Why Standards Fail? Design: Standards Are Trying To Hide The Wood With A Single Tree: YOUR DEAR “Safe” KEY DATA TrustLeap 29 | Copyright © 2013, TWD Industries AG. All rights reserved. Claude Shannon's “Information Theory” Defined The Rules In The 1940s: 1011011000010110111100101111 I CAN SEE 0110110111010110010001111101 S YOU! 1000100010100101001001010010 1010010010100000101001111011K A 0111101 1001111111010011111010101010E 0011001 1110101001011011111001101010L 0101001 E1011000010010100011111111111Y LE 010010 K 1010010100101001010010010101A 0101100101001001010010010010K YOUR 1 S DEAR “Safe” KEY 1001001010010110100010101001DATA 0100101001010010010101010100 TrustLeap 30 | Copyright © 2013, TWD Industries AG. All rights reserved. What's The Problem? The “Information Theory” Says “Either Perfect Secrecy OR Convenience”: True Random Encryption Keys Applied On Data Larger Than The Key Leaks Key Patterns That Can Be Spotted & Used To Recover The “Secret” Key. TrustLeap 31 | Copyright © 2013, TWD Industries AG. All rights reserved. Solutions? 1 Use The One-Time Pad; Keys Must Be: (a) Random & Unique, (b) As Long As Data, (c) Safely Exchanged Before Encryption. Provably Safe If Safe Random Source & Key Exchange & No Key Reuse: Not Convenient. TrustLeap 32 | Copyright © 2013, TWD Industries AG. All rights reserved. Solutions? 2 Use A Very Strictly Defined Grammar (a) Does Not Suit All Uses (b) Requires High Crypto Skills (c) Any Usage Error Implies Failure. Can Be Made Provably Safe If Properly Done & Used, But Not General-Purpose. TrustLeap 33 | Copyright © 2013, TWD Industries AG. All rights reserved. Solutions? 3 Use Provably-Safe Mathematical Rules To Remove All Exploitable Key Leaks From Encryption Standard ciphertexts (making AES and others provably-safe). Provably SAFE & CONVENIENT. Getting The Best Of Both World! TrustLeap 34 | Copyright © 2013, TWD Industries AG. All rights reserved. III. The Solution TrustLeap 35 | Copyright © 2013, TWD Industries AG. All rights reserved. TrustLeap Game-Changing: - Delivers Provably-Safe Certainty - Reduces Surface Of Vulnerability TrustLeap 36 | Copyright © 2013, TWD Industries AG. All rights reserved. Secure By-Design HOW: Mathematically-Proven: Its Design Does Not Expose Leaked Key Patterns In Encrypted Data. TrustLeap 37 | Copyright © 2013, TWD Industries AG. All rights reserved. Secure Forever WHY: Without Correlations To Spot In Encrypted Data There Is Nothing To Target & Break. TrustLeap 38 | Copyright © 2013, TWD Industries AG. All rights reserved. Ubiquity WHERE: A Low Overhead Makes It Suitable For All Uses (Servers, Phones, Embedded). TrustLeap 39 | Copyright © 2013, TWD Industries AG. All rights reserved. Convenient WHY: Security Becomes Independent From Chosen Key Length And Involved Encryption Algorithm. TrustLeap 40 | Copyright © 2013, TWD Industries AG. All rights reserved. Desirable Side Effects WHERE: By Restricting Access To Known Users It Excludes All External Threats, Reducing The Surface Of Vulnerability. TrustLeap 41 | Copyright © 2013, TWD Industries AG. All rights reserved. IV. Adoption TrustLeap 42 | Copyright © 2013, TWD Industries AG. All rights reserved. Political Obstacles? Consensus Easy To Obtain: ● Plug & Play, Securing AES, DES... ● Visible Undisputable Benefits ● 70-Year-Old Established Theory ● Affordable Licensing Terms TrustLeap 43 | Copyright © 2013, TWD Industries AG. All rights reserved. V. Frequently Asked Questions TrustLeap 44 | Copyright © 2013, TWD Industries AG. All rights reserved. Quantum Computers Quantum Computers (used by the NSA since 1990) find instantly results of algorithms without having to run them. This is the death of security based on computational hardness. Only Mathematically-Proven TrustLeap Encryption can resist to Quantum Computers (as
Load more

Recommended publications
  • IBM Multi-Factor Authentication for Z/OS
    Multi Factor Authentication for Linux on IBM Z using a centralized z/OS LDAP infrastructure Dr. Manfred Gnirss Thomas Wienert Z ATS IBM Systems IBM Germany R & D Boeblingen, 18.7.2018 © 2018 IBM Corporation 2 Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml: *BladeCenter®, DB2®, e business(logo)®, DataPower®, ESCON, eServer, FICON, IBM®, IBM (logo)®, MVS, OS/390®, POWER6®, POWER6+, POWER7®, Power Architecture®, PowerVM®, S/390®, System p®, System p5, System x®, System z®, System z9®, System z10®, WebSphere®, X-Architecture®, zEnterprise, z9®, z10, z/Architecture®, z/OS®, z/VM®, z/VSE®, zSeries® The following are trademearks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc.
    [Show full text]
  • SANS Spearphishing Survival Guide
    SANS Spearphishing Survival Guide A SANS Whitepaper Written by Jerry Shenk December 2015 Sponsored by Proofpoint ©2015 SANS™ Institute Executive Summary Organizations are constantly under attack. Nearly every week comes a news headline of another breach affecting millions of people. Organizations that experience “small” breaches spend hundreds of thousands of dollars on forensic examinations, infrastructure upgrades and identity monitoring. Those that get hit by a large breach spend millions. The majority of those threats still arrive by email in the form of weaponized file attachments, malicious links, wire-transfer fraud and credential phishing. In most cases, attackers deploy email-borne attacks that target specific individuals and fool them into believing they are from someone they do business with or someone in authority who knows them. Often, attackers gather the information they need to pull off these sorts of phishing attacks over social media, where employees share significant amounts of personal and contextual information. Just as often, employees leak information over mobile applications that make it easier for criminals to target their attacks. While most antivirus, anti-malware and email security systems are good at catching traditional mass email phishing attacks with known malicious attachments, links and content, they are not catching the most sophisticated targeted attacks on email recipients. These types of attacks, called spearphishing, gather information on high- value targets who have direct access to company financial or customer information.1 Using social media, mobile apps and other sources of information (such as a company website), criminals can make connections between business associates and third parties in order to craft emails that look like they come from someone the targets work with—and neither network-based nor email-based security tools are catching them consistently.
    [Show full text]
  • The Rise of Cyber-Espionage
    Case Study: THE RISE OF CYBER-ESPIONAGE 5HFUXLWPHQW3ODQ CounterTh e 20 7KH&RXQWHU7HUURULVW ~ June/July 2012 ©istockphoto/loops7 By Chris Mark At a Hopkinton, Massachusetts, offi ce, an executive received an email that appeared to be from a coworker on March 1, 2011. Attached to the email was an Excel spreadsheet titled “2011 Recruitment Plan.” The man opened the spreadsheet. The email was not from a coworker, it was a carefully crafted attack known as ”spearfi shing” in which a fraudulent email is sent to a specifi c person. he spearfi shing email contained an system, SecurID. SecurID is used by an Excel spreadsheet with a zero- estimated 250 million people worldwide. Tday exploit and a version of the Poison Th e attack was believed to have been ini- Ivy RAT (remote administration tool) tiated using a zero-day exploit created by payload embedded. Th e RAT enabled a Chinese hacker. Evidence suggests the a hacker to gain privileged access to the possibility of Chinese-sponsored cyber- network of RSA Security (an American espionage.1 RSA’s CEO, Art Coviello, computer and network security com- stated the stolen SecurID information pany). Th e company had been founded “could potentially be used to reduce by Ron Rivest, Adi Shamir, and Leonard the eff ectiveness of a current two-factor Adleman, the inventors of the RSA public authentication implementation as part key cryptographic algorithm. Th is single of a broader attack (italics added).”2 Th is The US government event initiated an attack that would result proved to be an ominous prediction.
    [Show full text]
  • Security Features
    Security Features SL1 version 10.1.0 Table of Contents Introduction 4 Who Should Read This Manual? 4 Built-In Security for Appliances and Data 5 Hardened Operating System 6 Limited Open Ports 6 Firewalls and White Lists 6 Hardened Configuration on Each Appliance 7 Root Access 7 API 7 All-In-One 7 Administration Portal 8 Database Server 8 Data Collectors and Message Collectors 8 Multiple Tenancy and Segregation of Duties 9 Account Types 9 Access Keys 9 Segregation by Organization 10 Credential Management 10 User Policies 11 Protection Against Injections and Cross-Site Scripting 12 Operating System Scan 12 Data Integrity 12 Backups 13 Disaster Recovery and High Availability 13 Audit Logs 13 Manage the Security of Your Network 15 Monitoring IDS, Firewalls, and Security Hardware 16 Security Events 16 Monitoring Changes to Device Configuration 16 Monitoring for Illicit Behavior 17 Blueprinting Windows Services 17 Blueprinting System Processes 17 Blueprinting DNS 18 Monitoring Open Ports 18 Monitoring Bandwidth Usage 18 Monitoring Hardware Performance 19 Managing Patches and Hot Fixes 21 Using Standard Deviation To Calculate "Normal" Conditions and Abnormal Conditions 21 Using Run Book Automation to Automate Responses to Security Events 21 Reports 22 Proxied Web Services 23 Security Settings 24 Access Control 25 Authentication 30 Multiple Tenancy and Segregation of Duties 31 Protection of Shared Content 33 Data Integrity 33 Security Events 34 Monitoring Changes to Device Configuration 35 Monitoring for Illicit Behavior 35 Blueprinting DNS, System Processes, and Windows Services 36 Monitoring Open Ports 37 Monitoring Bandwidth Usage 37 Monitoring Hardware Performance 39 Monitoring Patches and Hot Fixes 40 Using Run Book Automation to Automate Responses to Security Events 41 Reports 41 Proxied Web Services 41 Audit Logs 42 Chapter 1 Introduction Overview SL1 addresses two major aspects of system and network security: l SL1 appliances are lean, hardened, and configured for maximum security.
    [Show full text]
  • VULNERABLE by DESIGN: MITIGATING DESIGN FLAWS in HARDWARE and SOFTWARE Konoth, R.K
    VU Research Portal VULNERABLE BY DESIGN: MITIGATING DESIGN FLAWS IN HARDWARE AND SOFTWARE Konoth, R.K. 2020 document version Publisher's PDF, also known as Version of record Link to publication in VU Research Portal citation for published version (APA) Konoth, R. K. (2020). VULNERABLE BY DESIGN: MITIGATING DESIGN FLAWS IN HARDWARE AND SOFTWARE. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal ? Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. E-mail address: [email protected] Download date: 07. Oct. 2021 VULNERABLE BY DESIGN: MITIGATING DESIGN FLAWS IN HARDWARE AND SOFTWARE PH.D. THESIS RADHESH KRISHNAN KONOTH VRIJE UNIVERSITEIT AMSTERDAM, 2020 Faculty of Science The research reported in this dissertation was conducted at the Faculty of Science — at the Department of Computer Science — of the Vrije Universiteit Amsterdam This work was supported by the MALPAY consortium, consisting of the Dutch national police, ING, ABN AMRO, Rabobank, Fox-IT, and TNO.
    [Show full text]
  • EC-Council Certified Security Specialist Course Outline (Version 9)
    EC-Council Certified Security Specialist Exam ECSS Course Outline EC-Council Certified Security Specialist Course Outline (Version 9) Module 01: Information Security Fundamentals . Data Breach Statistics . Data Loss Statistics . The Global State of Information Security Survey 2016 . Information Security . Need for Security . Elements of Information Security . The Security, Functionality, and Usability Triangle . Security Challenges . Information Security Attack Vectors . Information Security Threat Categories . Types of Attacks on a System . Trends in Security . Information Security Laws and Regulations Module 02: Networking Fundamentals . Introduction . Types of Networks . OSI (Open Systems Interconnection) Reference Model o OSI Reference Model: Diagram Page | 1 EC-Council Certified Security Specialist Copyright © by EC-Council All Rights Reserved. Reproduction is Strictly Prohibited. EC-Council Certified Security Specialist Exam ECSS Course Outline o Application Layer o Presentation Layer o Session Layer o Transport Layer o Network Layer o Data Link Layer o Physical Layer . OSI Layers and Device Mapping . Protocols . TCP/IP Model . Comparing OSI and TCP/IP . Network Security . Essentials of Network Security . Data Security Threats over a Network . Basic Network Security Procedures . Network Security Policies . Types of Network Security Policies o Data Policy: Example o Computer Usage Policy: Example o E-mail Policy Module 03: Secure Network Protocols . Introduction . Terminology . Secure Network Protocols o E-mail Security Protocol – S/MIME o E-mail Security Protocol – PGP o Web Security Protocol – SSL Steps to Establish Connection Between Browser and Web server using SSL o Web Security Protocol – SSH (Secure Shell) o Web Security Protocol – HTTPS Page | 2 EC-Council Certified Security Specialist Copyright © by EC-Council All Rights Reserved.
    [Show full text]
  • Protecting Merchant Point of Sale Systems During the Holiday Season
    Protecting Merchant Point of Sale Systems during the Holiday Season November 7, 2014 Executive Summary This advisory was prepared in collaboration with the Financial Services Information Sharing and Analysis Center (FS-ISAC), the United States Secret Service (USSS), and the Retail Cyber Intelligence Sharing Center (R-CISC), and is directed towards retailers or companies which are processing financial transactions and managing customer personally identifiable information (PII) during the upcoming holiday season and beyond. This advisory serves to provide information on and recommends possible mitigations for common cyber exploitation tactics, techniques and procedures (TTPs) consistently and successfully leveraged by attackers in the past year. Many of these TTPs have been observed by the FS- ISAC, through its members, and identified in Secret Service investigations. The TTPs discussed in this report include: • Exploiting commercial application vulnerabilities • Unauthorized access via remote access • Email phishing • Unsafe web browsing from computer systems used to collect, process, store or transmit customer information This document provides recommended security controls in these four commonly observed areas to protect customer data and also provides recommendations to smaller merchants who should work with their vendors to implement these recommendations (see Appendix A). This advisory is not intended to be a robust, all-inclusive list of procedures as attackers will modify TTPs depending upon the target’s network and vulnerabilities. This report does not contain detailed information about memory scraping Point of Sale (PoS) malware that has been used in recent high- profile data breaches. Secret Service investigations of many of the recent PoS data breaches have identified customized malware only being used once per target.
    [Show full text]
  • Leadership and Responsibility for Cybersecurity
    Leadership and Responsibility for Cybersecurity Melissa E. Hathaway Melissa Hathaway According to Darwin, “it is not the most intellectual of the is President of Hatha- species that survives; it is not the strongest that survives; but way Global Strategies, LLC and former Act- the species that survives is the one that is able best to adapt ing Senior Direc- and adjust to the changing environment in which it finds tor for Cyberspace, 1 U.S. National Secu- itself.” We have certainly adapted to the Internet and the rity Council. Hathaway technology that underpins it. In fact, we have made it an served as Cyber Coor- dination Executive and integral part of just about everything in our life; and in many Director of the Joint ways we take it for granted that it will always work twenty-four Interagency Cyber Task Force in the Office hours a day, seven days a week. There are approximately 2.5 of the Director of billion Internet users around the world of which nearly half National Intelligence. 2 Previously, Hathaway are below the age of twenty-five. Yet, there is another set of was a Principal with actors that have adapted more successfully: criminals, spies, Booz Allen & Hamil- and some clever guys. Media headlines announce daily that ton, Inc. our bank accounts are being robbed, our intellectual prop- erty is being illegally copied, and our critical infrastructures are penetrated and could stop working at any moment. The very fabric that contributes to nearly 40 percent of the productivity growth of the global economy also facilitates an equally robust underground economy.3 These messages appear to fall on deaf ears as our corpo- rate and political leaders continue to talk about the troubled environment, yet too few are adapting to or assuming the [71] LEADERSHIP AND RESPONSIBILITY FOR CYBERSECURITY responsibility for resolving it.
    [Show full text]
  • Comptia® Security+® Review Guide: Exam SY0-601
    Telegram Channel @nettrain Telegram Channel @nettrain Telegram Channel @nettrain Telegram Channel @nettrain CompTIA® Security+® Review Guide Exam SY0-601 Fifth Edition Telegram Channel @nettrain Telegram Channel @nettrain CompTIA® Security+® Review Guide Exam SY0-601 Fifth Edition James Michael Stewart Telegram Channel @nettrain Copyright © 2021 by John Wiley & Sons, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-1-119-73538-0 ISBN: 978-1-119-73542-7 (ebk) ISBN: 978-1-119-73536-6 (ebk) No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at www.wiley.com/go/permissions. Limit of Liability/Disclaimer of Warranty: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. No warranty may be created or extended by sales or promotional materials. The advice and strategies contained herein may not be suitable for every situation.
    [Show full text]
  • USC Csci530 Computer Security Systems Lecture Notes Fall 2018 All
    USC CSci530 Computer Security Systems Lecture notes Fall 2018 Dr. Clifford Neuman University of Southern California Information Sciences Institute All lectures prior to mid-term exam Copyright © 1995-2018 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE CSci530: Security Systems Lecture 1 – August 24, 2018 – OHE122 The Security Problem Dr. Clifford Neuman University of Southern California Information Sciences Institute http://ccss.usc.edu/530 Copyright © 1995-2018 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Administration • Class home page http://ccss.usc.edu/530 – Preliminary Syllabus – Assigned Readings – Lecture notes – Assignments Copyright © 1995-2018 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Who gets in • If you wish to enroll and do not have D clearance yet, send an email to [email protected] with: – Your name – If you meet the prerequisites – A phone number – Request to received D clearance • I will assess and approve if appropriate. Copyright © 1995-2018 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Structure of lecture • Classes from 9:00 AM – 11:50 AM – 10 minute break halfway through – Before or after break, 10 minutes for discussion of two current events, to be led by students. ▪ Groups of 1 to 3. Send two sentences on topic by Wed, selected Thu AM then prepare slides. Copyright © 1995-2018 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Administration • Lab Component (see http://ccss.usc.edu/530L) – 1 of the 4 units – Instructor is David Morgan – Instruction 4:30-5:20 Fridays in OHE 122 ▪ WebCast via DEN ▪ Today’s Lab instruction is only a 30 minute introduction – Hands on sections, choose from several sessions ▪ Provides an opportunity to do hands on work in OHE 406 lab.
    [Show full text]
  • IBM Multi-Factor Authentication for Z/OS
    IBM Multi-Factor Authentication for z/OS Ross Cooper, *CISSP IBM z/OS Security Software Design and Development NewEra – The z Exchange 10/24/2017 Current Security Landscape 1,935 81% Number of security incidents Number of breaches in 2016 with confirmed data due to stolen and/or disclosure as a result of weak passwords.1 stolen credentials.1 (18% worse than prior year) (506 worse than prior year) 60% $4 million Number of security The average total cost incidents that are from 2 of a data breach. insider threats. 3 Criminals are identifying key employees at organizations and exploiting them with savvy phishing attacks to gain initial access to the employees’ system and steal their account credentials. This puts emphasis on the need for tighter restrictions on access privileges to key data repositories.1 1 2017 Verizon Data Breach Investigations Report 2 Ponemon: 2016 Cost of Data Breach Study: Global Analysis 2 3 IBM X-Force 2016 Cyber Security Intelligence Index User Authentication Today on z/OS • Users can authenticate with: ‒ Passwords ‒ Password phrases ‒ Digital Certificates ‒ via Kerberos • Problems with passwords: ‒ Common passwords ‒ Employees are selling their passwords ‒ Password reuse ‒ People write down passwords ‒ Malware ‒ Key log ‒ Password cracking 3 Compliance PCI DSS v3.2 8.3 Secure all individual non-console administrative access and all remote access to the CDE using multi-factor authentication. 8.3.1 Incorporate multi-factor authentication for all non-console access into the Cardholder Data Environment (CDE) for personnel with administrative access. Note: This requirement is a best practice until January 31, 2018, after which it becomes a requirement.
    [Show full text]
  • Guarding Beyond the Gateway: Challenges of Email Security
    Interested in learning more about security? SANS Institute InfoSec Reading Room This paper is from the SANS Institute Reading Room site. Reposting is not permitted without express written permission. Guarding Beyond the Gateway: Challenges of Email Security Learn how to maximize the trustworthiness of email services through changes to infrastructure and how to use your systems to improve the performance of the human firewall. Copyright SANS Institute Author Retains Full Rights Guarding Beyond the Gateway: Challenges of Email Security A SANS Whitepaper Written by Barbara Filkins January 2016 Sponsored by Mimecast ©2016 SANS™ Institute Introduction Email is often the first thing people check in the morning and the last thing they check in the evening. It is an essential communication channel in our business and personal lives, with more than 112 billion business emails being sent daily, according to a report by The Radicati Group.1 Almost half the time, employees (and more than half the time, executives) access their business email from mobile devices. A Business 2 Community article recently reported that 48 percent of all emails are now opened on mobile devices, and 64 percent of decision makers read their email via mobile devices.2 When accessing their email from all over the place (work, home or on the road), people Ubiquitous Email make mistakes and let in bad actors. Meanwhile bad actors, particularly phishers The average business user sends and that research their targets (known as spearphishers) are exploiting DNS weaknesses, receives
    [Show full text]