Limiting Vulnerability Exposure Through Effective Patch Management: Threat Mitigation Through Vulnerability Remediation

Total Page:16

File Type:pdf, Size:1020Kb

Limiting Vulnerability Exposure Through Effective Patch Management: Threat Mitigation Through Vulnerability Remediation Limiting Vulnerability Exposure through effective Patch Management: threat mitigation through vulnerability remediation Submitted in fulfilment of the requirements of the degree MASTER OF SCIENCE in the Department of Computer Science of Rhodes University Dominic Stjohn Dolin White <[email protected]> January 2006 Abstract This document aims to provide a complete discussion on vulnerability and patch management. The first chapters look at the trends relating to vulnerabilities, exploits, attacks and patches. These trends describe the drivers of patch and vulnerability management and situate the dis- cussion in the current security climate. The following chapters then aim to present both policy and technical solutions to the problem. The policies described lay out a comprehensive set of steps that can be followed by any organisation to implement their own patch management policy, including practical advice on integration with other policies, managing risk, identifying vulner- ability, strategies for reducing downtime and generating metrics to measure progress. Having covered the steps that can be taken by users, a strategy describing how best a vendor should implement a related patch release policy is provided. An argument is made that current monthly patch release schedules are inadequate to allow users to most effectively and timeously mitigate vulnerabilities. The final chapters discuss the technical aspect of automating parts of the policies described. In particular the concept of ’defense in depth’ is used to discuss additional strategies for ’buying time’ during the patch process. The document then goes on to conclude that in the face of increasing malicious activity and more complex patching, solid frameworks such as those provided in this document are required to ensure an organisation can fully manage the patching process. However, more research is required to fully understand vulnerabilities and exploits. In particular more attention must be paid to threats, as little work as been done to fully understand threat-agent capabilities and activities from a day to day basis. Contents 1 Introduction 1 1.1 Background . 1 1.2 Patch Management . 3 1.2.1 Definitions . 4 1.3 The Need for Patch Management . 6 1.4 Objectives . 7 1.5 Methodology . 8 1.6 Conclusion . 10 2 Vulnerability and Patch Management 11 2.1 Introduction . 11 2.2 The Vulnerability Life-Cycle . 12 2.3 Vulnerabilities, Malware and Exploitation Trends . 16 2.3.1 Increasing number of vulnerabilities . 17 2.3.2 Increasing number of attacks . 18 2.3.3 Exploit window shrinking . 21 2 CONTENTS 3 2.4 Problems with Patches . 23 2.4.1 Unpredictable Patches . 23 2.4.2 Too Many Patches . 24 2.4.3 Window to Patch is Shrinking . 25 2.4.4 Complex Patches . 26 2.4.5 Hard to obtain patches . 27 2.4.6 Problem Patch Examples . 28 2.4.6.1 SQL Slammer/Sapphire Worm . 28 2.4.6.2 GDI+ JPEG Vulnerability . 30 2.5 Conclusion . 31 3 Policy Solutions 33 3.1 Introduction . 33 3.2 Patch Management Policy Framework . 34 3.2.1 Patch and Vulnerability Group . 35 3.2.2 Security, Stability, Functionality Patches and Workarounds . 36 3.2.3 Policy . 38 3.2.3.1 Information Gathering . 40 3.2.3.2 Risk Assessment . 47 3.2.3.3 Scheduling and Patching Strategy . 53 3.2.3.4 Testing . 57 3.2.3.5 Planning & Change Management . 61 CONTENTS 4 3.2.3.6 Deployment, Installation and Remediation . 64 3.2.3.7 Verification & Reporting . 65 3.2.3.8 Maintenance . 71 3.2.3.9 Summary . 72 3.3 Conclusion . 73 4 Vendor Patch Release Policy 75 4.1 Introduction . 75 4.2 State of the Art . 76 4.3 An analysis of patch schedules . 78 4.3.1 The Disclosure Debate . 79 4.3.1.1 Delayed Disclosure . 80 4.3.1.2 Instantaneous Disclosure . 81 4.3.2 Patch Schedules and Delayed Disclosure . 82 4.3.3 Patch Schedules and Instantaneous Disclosure . 83 4.3.3.1 Quality . 84 4.3.3.2 Planned Deployment . 87 4.3.3.3 Examples . 88 4.3.4 Conclusion . 90 4.4 Advice for implementing a Patch Release Schedule . 90 4.4.1 Dual Schedules and Separation Criteria . 91 4.4.2 Predictable Patch Release Schedule . 92 CONTENTS 5 4.4.3 Critical Patch Release . 94 4.4.4 Encouraging Delayed Disclosure . 96 4.5 Conclusion . 97 5 Practical Solutions 98 5.1 Introduction . 98 5.2 Patch Management Software . 98 5.2.1 Functionality and Classification of Patching Tools . 99 5.2.1.1 Notification . 103 5.2.1.2 Inventory Management . 104 5.2.1.3 Vulnerability Scanner . 105 5.2.1.4 Patch Testing . 106 5.2.1.5 Patch Packaging . 107 5.2.1.6 Patch Distribution . 111 5.2.1.7 Reporting . 111 5.2.1.8 Summary . 112 5.2.2 Architecture . 112 5.2.2.1 Agentless . 112 5.2.2.2 Agent . 114 5.2.3 Available Tools . 115 5.2.3.1 Evolution . 115 5.2.3.2 Examples . 117 CONTENTS 6 5.3 Defence in-depth . 119 5.3.1 Firewalls and Anti-Virus . 119 5.3.2 Intrusion Detection/Prevention Systems . 120 5.3.2.1 Virtual Patching . 121 5.3.3 Other Hardening . 122 5.3.4 Software Selection . 122 5.4 Conclusion . 124 6 Conclusion 126 6.1 Introduction . 126 6.2 Objectives . 126 6.2.1 Summary . 128 6.3 Problems and Solutions . 129 6.4 Future Work . 129 6.4.1 Threat Management . 129 6.4.2 Vulnerability Detail and Trend Tracking . 130 6.4.3 Optimal Time to Patch for Large Vendors . 130 6.4.4 Patch Standards . 131 6.5 Final Word . 131 Bibliography 133 References 133 CONTENTS 7 A Time-line of Notable Worms and Viruses 157 A.1 Introduction . 157 A.2 Time-line . 157 A.2.1 2006 . 157 A.2.2 2005 . 157 A.2.3 2004 . 158 A.2.4 2003 . 158 A.2.5 2001 . 159 A.2.6 1999 . 159 A.2.7 1998 . 159 A.2.8 1995 . 160 A.2.9.
Recommended publications
  • Tangled Web : Tales of Digital Crime from the Shadows of Cyberspace
    TANGLED WEB Tales of Digital Crime from the Shadows of Cyberspace RICHARD POWER A Division of Macmillan USA 201 West 103rd Street, Indianapolis, Indiana 46290 Tangled Web: Tales of Digital Crime Associate Publisher from the Shadows of Cyberspace Tracy Dunkelberger Copyright 2000 by Que Corporation Acquisitions Editor All rights reserved. No part of this book shall be reproduced, stored in a Kathryn Purdum retrieval system, or transmitted by any means, electronic, mechanical, pho- Development Editor tocopying, recording, or otherwise, without written permission from the Hugh Vandivier publisher. No patent liability is assumed with respect to the use of the infor- mation contained herein. Although every precaution has been taken in the Managing Editor preparation of this book, the publisher and author assume no responsibility Thomas Hayes for errors or omissions. Nor is any liability assumed for damages resulting from the use of the information contained herein. Project Editor International Standard Book Number: 0-7897-2443-x Tonya Simpson Library of Congress Catalog Card Number: 00-106209 Copy Editor Printed in the United States of America Michael Dietsch First Printing: September 2000 Indexer 02 01 00 4 3 2 Erika Millen Trademarks Proofreader Benjamin Berg All terms mentioned in this book that are known to be trademarks or ser- vice marks have been appropriately capitalized. Que Corporation cannot Team Coordinator attest to the accuracy of this information. Use of a term in this book should Vicki Harding not be regarded as affecting the validity of any trademark or service mark. Design Manager Warning and Disclaimer Sandra Schroeder Every effort has been made to make this book as complete and as accurate Cover Designer as possible, but no warranty or fitness is implied.
    [Show full text]
  • The Norman Book on Computer Viruses Ii Z the Norman Book on Computer Viruses
    The Norman Book on Computer Viruses ii z The Norman Book on Computer Viruses Norman ASA is not liable for any other form of loss or damage arising from use of the documentation or from errors or deficiencies therein, including but not limited to loss of earnings. In particular, and without the limitations imposed by the licensing agreement with regard to any special use or purpose, Norman ASA will in no event be liable for loss of profits or other commercial damage including but not limited to incidental or consequential damages. The information in this document as well as the functionality of the software is subject to change without notice. No part of this documentation may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording or information storage and retrieval systems, for any purpose other than the purchaser's personal use, without the explicit written permission of Norman ASA. Contributors to The Norman Book on Viruses: Snorre Fagerland, Sylvia Moon, Kenneth Walls, Carl Bretteville Edited by Camilla Jaquet and Yngve Ness The Norman logo is a registered trademark of Norman ASA. Names of products mentioned in this documentation are either trademarks or registered trademarks of their respective owners. They are mentioned for identification purposes only. Norman documentation is Copyright © 1990-2002 Norman ASA. All rights reserved. October 2001 Copyright © 1990-2002 Norman z iii Norman Offices Norman Data Defense Systems Pty Ltd 6 Sarton Road, Clayton, Victoria, 3168 Australia. Tel: +61 3 9562 7655 Fax: +61 3 9562 9663 E-mail: [email protected] Web: http://www.norman.com.au Norman Data Defense Systems A/S Dronningensgade 23, DK-5000 Odense C, Denmark Tel.
    [Show full text]
  • UTTARAKHAND OPEN UNIVERSITY Teen Pani Bypass Road, Near Transport Nagar, Haldwani -263139 Phone No- 05946 - 261122, 261123 Toll Free No
    CYBER CRIMES AND CONSUMER PROTECTION IN CYBERSPACE CYL-104 [1] CYL- 104 Cyber Crimes And Consumer Protection in Cyber Space School of Law UTTARAKHAND OPEN UNIVERSITY Teen Pani Bypass Road, Near Transport Nagar, Haldwani -263139 Phone No- 05946 - 261122, 261123 Toll Free No. 18001804025 Fax No.- 05946-264232, Email- [email protected], http://uou.ac.in Uttarakhand Open University CYBER CRIMES AND CONSUMER PROTECTION IN CYBERSPACE CYL-104 [2] BOARD OF STUDIES Professor Girija Prasad Pande, Director, School of Law, Uttarakhand Open University, Haldwani, Nainital. Professor J.S.Bisht, Faculty of Law,S.S. Jeena Campus, Almora,Kumaun University, Nainital, Uttarakhand. Professor B.P. Maithani, Former RTI Advisor, Government of Uttarakhand Mr. Deepankur Joshi, Coordinator School of Law, Uttarakhand Open University, Haldwani, (Nainital). UNIT WRITING UNIT WRITERS UNIT [1] Dr. Razit Sharma, Assistant Professor, Unit- 1,2,3,4 Law College, Uttaranchal University, Dehradun Uttarakhand [2] Ms. Sapna Agarwal, Advocate High Court of Uttarakhand, Unit- 5,6,7 Nainital [3 Mr. Rajeev Bhatt, Advocate High Court of Uttarakhand, Ex. RTI Advisor Kumaun University Nainital, Ex. Assistant Professor Unity Unit- 8 ,9,10 Law College Rudrapur [4] Dr. Sushim Shukla, Assistant Professor, Unit- 11, 12, 13 Law College, Uttaranchal University, Dehradun Uttarakhand EDITOR Mr. Deepankur Joshi, Coordinator, School of Law, Uttarakhand Open University, Haldwani, (Nainital) Copyright © Uttarakhand Open University, Haldwani, Nainital Edition- 2018, Pre Publication copy for Limited Circulation ISBN- Publication- Directorate of Studies and Publication, Uttarakhand Open University, Haldwani, Nainital. E- Mail: [email protected] . Uttarakhand Open University CYBER CRIMES AND CONSUMER PROTECTION IN CYBERSPACE CYL-104 [3] POST GRADUATE DIPLOMA IN CYBER LAW CYL- 104 CYBERCRIMES AND CONSUMER PROTECTION IN CYBER SPACE INDEX S.
    [Show full text]
  • "Year 2000 Y2K" December 28, 1999
    NIPC ADVISORY 99-031 "Year 2000 Y2K" December 28, 1999 Introduction Large-scale U.S. infrastructure disruptions are not expected from "Y2K failures" during the Y2K transition period. However we are prepared for a possible increase in real or reported criminal cyber activity (such as hacking and spreading computer viruses), considering the heightened awareness of and media focus on malicious activity during the Y2K period. Any increased criminal activity during the Y2K period could raise the level of problems in infrastructure systems, adding to genuine Y2K-generated issues and the normal level of infrastructure concerns. We anticipate encountering both known and new viruses and hacking exploits. We could see the dissemination of several new and possibly destructive viruses, and the successful exploitation of both corporate and government information systems. But even these possibilities reflect only a larger assembly of the same kinds of malicious activity seen and addressed every day. Finally, known and possible extremist or apocalyptic terrorist activity in the United States by individuals or groups suggests the possibility of threats to domestic infrastructures. For example, the media have reported arrests of certain individuals allegedly planning violent actions against electric power and oil and gas facilities. These indications of possible threats to our infrastructures warrant an increased vigilance to protect against both cyber and physical threats to our nation's critical infrastructures. Summary The Y2K Transition might be seen by potential malefactors as an unprecedented opportunity for malicious code release and associated publicity, where a new and significant exploit can achieve a widespread notoriety in the information security and hacker world.
    [Show full text]
  • Chapter 3: Viruses, Worms, and Blended Threats
    Chapter 3 Chapter 3: Viruses, Worms, and Blended Threats.........................................................................46 Evolution of Viruses and Countermeasures...................................................................................46 The Early Days of Viruses.................................................................................................47 Beyond Annoyance: The Proliferation of Destructive Viruses .........................................48 Wiping Out Hard Drives—CIH Virus ...................................................................48 Virus Programming for the Masses 1: Macro Viruses...........................................48 Virus Programming for the Masses 2: Virus Generators.......................................50 Evolving Threats, Evolving Countermeasures ..................................................................51 Detecting Viruses...................................................................................................51 Radical Evolution—Polymorphic and Metamorphic Viruses ...............................53 Detecting Complex Viruses ...................................................................................55 State of Virus Detection.........................................................................................55 Trends in Virus Evolution..................................................................................................56 Worms and Vulnerabilities ............................................................................................................57
    [Show full text]
  • Virus Bulletin, June 1999
    ISSN 0956-9979 JUNE 1999 THE INTERNATIONAL PUBLICATION ON COMPUTER VIRUS PREVENTION, RECOGNITION AND REMOVAL Editor: Francesca Thorneloe CONTENTS Technical Consultant: Fraser Howard Technical Editor: Jakub Kaminski COMMENT Flashback – When the Chips were Down 2 Consulting Editors: VIRUS PREVALENCE TABLE 3 Nick FitzGerald, Independent Consultant, NZ Ian Whalley, Sophos Plc, UK NEWS Richard Ford, Independent Consultant, USA 1. Two Be or not Two Be 3 Edward Wilding, Maxima Group Plc, UK 2. ThanY2Ks for the Memory! 3 LETTERS 4 IN THIS ISSUE: VIRUS ANALYSES 1. Beast Regards 6 • Oh dear, oh dear, oh dear Virus Bulletin: At long last 2. Papa Don’t Preach 8 the Letters page makes a comeback in this issue. Love it or hate it, it’s your way to have your say, starting on p.4. A DAY IN THE LIFE • Define your terms: Find out all you need to know about Educating Who? 10 polymorphism. Two researchers from Kaspersky Lab set FEATURES the record straight on p.14. 1. Virus Writers – Part 2 12 • Don’t panic! Our tutorial this month paves the way for 2. pOLEmorphism 14 future corporate case studies. In clear and easy-to-follow steps, the actions to take in the event of a virus or malware TUTORIAL outbreak on your system are documented on p.16. When Barriers Break Down 16 PRODUCT REVIEWS 1. DialogueScience AntiVirus Kit v3.0 18 2. eSafe Protect Enterprise 21 END NOTES AND NEWS 24 VIRUS BULLETIN ©1999 Virus Bulletin Ltd, The Pentagon, Abingdon, Oxfordshire, OX14 3YP, England. Tel +44 1235 555139. /99/$0.00+2.50 No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form without the prior written permission of the publishers.
    [Show full text]
  • Basics of Ethical Hacking – Manthan M. Desai
    Hacking For Beginners – Manthan Desai 2010 Legal Disclaimer Any proceedings and or activities related to the material contained within this book are exclusively your liability. The misuse and mistreat of the information in this book can consequence in unlawful charges brought against the persons in question. The authors and review analyzers will not be held responsible in the event any unlawful charges brought against any individuals by misusing the information in this book to break the law. This book contains material and resources that can be potentially destructive or dangerous. If you do not fully comprehend something on this book, don‘t study this book. Please refer to the laws and acts of your state/region/ province/zone/territory or country before accessing, using, or in any other way utilizing these resources. These materials and resources are for educational and research purposes only. Do not attempt to violate the law with anything enclosed here within. If this is your intention, then leave now. While using this book and reading various hacking tutorials, you agree to follow the below mentioned terms and conditions: 1. All the information provided in this book is for educational purposes only. The book author is no way responsible for any misuse of the information. 2. "Hacking for Beginners” is just a term that represents the name of the book and is not a book that provides any illegal information. “Hacking for Beginners” is a book related to Computer Security and not a book that promotes hacking/cracking/software piracy. 3. This book is totally meant for providing information on "Computer Security”, "Computer Programming” and other related topics and is no way related towards the terms "CRACKING” or "HACKING” (Unethical).
    [Show full text]
  • What Are Kernel-Mode Rootkits?
    www.it-ebooks.info Hacking Exposed™ Malware & Rootkits Reviews “Accessible but not dumbed-down, this latest addition to the Hacking Exposed series is a stellar example of why this series remains one of the best-selling security franchises out there. System administrators and Average Joe computer users alike need to come to grips with the sophistication and stealth of modern malware, and this book calmly and clearly explains the threat.” —Brian Krebs, Reporter for The Washington Post and author of the Security Fix Blog “A harrowing guide to where the bad guys hide, and how you can find them.” —Dan Kaminsky, Director of Penetration Testing, IOActive, Inc. “The authors tackle malware, a deep and diverse issue in computer security, with common terms and relevant examples. Malware is a cold deadly tool in hacking; the authors address it openly, showing its capabilities with direct technical insight. The result is a good read that moves quickly, filling in the gaps even for the knowledgeable reader.” —Christopher Jordan, VP, Threat Intelligence, McAfee; Principal Investigator to DHS Botnet Research “Remember the end-of-semester review sessions where the instructor would go over everything from the whole term in just enough detail so you would understand all the key points, but also leave you with enough references to dig deeper where you wanted? Hacking Exposed Malware & Rootkits resembles this! A top-notch reference for novices and security professionals alike, this book provides just enough detail to explain the topics being presented, but not too much to dissuade those new to security.” —LTC Ron Dodge, U.S.
    [Show full text]
  • Reversing Malware [Based on Material from the Textbook]
    SoftWindows 11/23/05 Reversing Malware [based on material from the textbook] Reverse Engineering (Reversing Malware) © SERG What is Malware? • Malware (malicious software) is any program that works against the interest of the system’s user or owner. • Question: Is a program that spies on the web browsing habits of the employees of a company considered malware? • What if the CEO authorized the installation of the spying program? Reverse Engineering (Reversing Malware) © SERG Reversing Malware • Revering is the strongest weapon we have against the creators of malware. • Antivirus researchers engage in reversing in order to: – analyze the latest malware, – determine how dangerous the malware is, – learn the weaknesses of malware so that effective antivirus programs can be developed. Reverse Engineering (Reversing Malware) © SERG Distributed Objects 1 SoftWindows 11/23/05 Uses of Malware • Why do people develop and deploy malware? – Financial gain – Psychological urges and childish desires to “beat the system”. – Access private data – … Reverse Engineering (Reversing Malware) © SERG Typical Purposes of Malware • Backdoor access: – Attacker gains unlimited access to the machine. • Denial-of-service (DoS) attacks: – Infect a huge number of machines to try simultaneously to connect to a target server in hope of overwhelming it and making it crash. • Vandalism: – E.g., defacing a web site. • Resource Theft: – E.g., stealing other user’s computing and network resources, such as using your neighbors’ Wireless Network. • Information Theft: – E.g., stealing other user’s credit card numbers. Reverse Engineering (Reversing Malware) © SERG Types of Malware • Viruses • Worms • Trojan Horses • Backdoors • Mobile code • Adware • Sticky software Reverse Engineering (Reversing Malware) © SERG Distributed Objects 2 SoftWindows 11/23/05 Viruses • Viruses are self-replicating programs that usually have a malicious intent.
    [Show full text]
  • Infosec Year in Review -- 1999
    InfoSec Year In Review -- 1999 M. E. Kabay, PhD, CISSP. Security Leader, INFOSEC Group, AtomicTangerine Inc. Category 11 Breaches of confidentiality Date 1999-01-29 Keyword data leakage privacy confidentiality control Web Source, Vol, No. RISKS 20 18 The Canadian consumer-tracking service Air Miles inadvertently left 50,000 records of applicants for its loyalty program publicly accessible on their Web site for an undetermined length of time. The Web site was offline as of 21 January until the problem was fixed. Date 1999-02-03 Keyword data leakage Web script QA vulnerability confidentiality Source, Vol, No. WIRED via PointCast An error in the configuration or programming of the F. A. O. Schwarz Web site resulted paradoxically in weakening the security of transactions deliberately completed by FAX instead of through SSL. Customers who declined to send their credit-card numbers via SSL ended up having their personal details — address and so forth — stored in a Web page that could be accessed by anyone entering a URL with an appropriate (even if randomly chosen) numerical component. Date 1999-02-10 Keyword e-commerce credit card personal information password privacy Source, Vol, No. RISKS 20 20 Prof. Ross Anderson of Cambridge University analyzed requirements on the AMAZON.COM online bookstore for credit card number, password, and personal details such as phone number. He identified several risks: (1) merchant retention of credit card numbers poses a far higher risk of capture than of capture in transit; (2) adding a password increases the likelihood of compromise because so many naïve users choose bad passwords and then write them down; (3) even the British site for Amazon contravenes European rules on protecting consumer privacy; (3) such practices make it easier for banks to reject their clients' claims of fraudulent use of their credit-card numbers.
    [Show full text]
  • Topics in Malware What Is Malware?
    Topics in Malware What is Malware? • Malware (malicious software) is any program that works against the interest of the system’s user or owner. • Question: Is a program that spies on the web browsing habits of the employees of a company considered malware? • What if the CEO authorized the installation of the spying program? Uses of Malware • Why do people develop and deploy malware? – Financial gain – Psychological urges and childish desires to “beat the system”. – Access private data – … Typical purposes of Malware • Backdoor access: – Attacker gains unlimited access to the machine. • Denial-of-service (DoS) attacks: – Infect a huge number of machines to try simultaneously to connect to a target server in hope of overwhelming it and making it crash. • Vandalism: – E.g., defacing a web site. • Resource Theft: – E.g., stealing other user’s computing and network resources, such as using your neighbors’ Wireless Network. • Information Theft: – E.g., stealing other user’s credit card numbers. Types of Malware • Viruses • Worms • Trojan Horses • Backdoors • Mobile code • Adware • Sticky software Metamorphic viruses • Instead of encrypting the program’s body and making slight alterations in the decryption engine, alter the entire program each time it is replicated. • This makes it extremely difficult for antivirus writers to use signature-matching techniques to identify malware. • Metamorphism requires a powerful code analysis engine that needs to be embedded into the malware. Metamorphic viruses: Operation • Metamorphic engine scans the code and generates a different version of it every time the program is duplicated. • The metamorphic engine performs a wide variety of transformations on the malware and on the engine itself.
    [Show full text]
  • TCP SYN-ACK) to Spoofed IP Addresses
    Joint Japan-India Workshop on Cyber Security and Services/Applications for M2M and Fourteenth GISFI Standardization Series Meeting How to secure the network - Darknet based cyber-security technologies for global monitoring and analysis Koji NAKAO Research Executive Director, Distinguished Researcher, NICT Information Security Fellow, KDDI Outline of NICT Mission As the sole national research institute in the information and communications field, we as NICT will strive to advance national technologies and contribute to national policies in the field, by promoting our own research and development and by cooperating with and supporting outside parties. Collaboration between Industry, Academic Institutions and Government R&D carried out by NICT’s researchers Budget (FY 2012): approx. 31.45 Billion Yen (420 Million US$) Personnel: 849 Researchers: 517 PhDs: 410 R&D assistance (as of April 2012) to industry and life convenient Japan Standard Time and academia Space Weather Forecast services Forecast Weather Space of the global community community global the of Growth of Economy of Japanese Growth Promotion of ICT a more for Security and Safety businesses Interaction with National ICT Policy problems major solve to Contribution 2 Internet Security Days 2012 Network Security Research Institute Collabor • Cyber attack monitoring, tracking, • Dynamic and optimal deployment of ation security functions analysis, response and prevention New GenerationNetwork Security • Prompt promotion of outcomes • Secure new generation network design Security Cybersecurity Architecture Laboratory Security Organizations Laboratory Daisuke Inoue Shin’ichiro Matsuo Kazumasa Taira Koji Nakao (Director General) (Distinguished Researcher) Security • Security evaluation of cryptography Fundamentals • Practical security • Post quantum cryptography Laboratory • Quantum security Shiho Moriai Recommendations for Cryptographic Algorithms and Key Lengths to Japan e-Government and SDOs 3 Internet Security Days 2012 Content for Today • Current Security Threats (e.g.
    [Show full text]