ITU-T CYBEX standards for cybersecurity information dissemination and exchange Youki Kadobayashi, Ph.D. NICT Japan / Rapporteur, ITU-T SG17 Q.4 ITU-T SG17.

Slides:



Advertisements
Similar presentations
h Protection from cyber attacks is achieved by acting on several levels: first, at the physical and material, placing the server in a place as safe as.
Advertisements

Tony Rutkowski Yaana Technologies Georgia Tech Q.4/17 Rapporteur
Creating Stronger, Safer, Web Facing Code JPL IT Security Mary Rivera June 17, 2011.
Principles of Computer Security: CompTIA Security + ® and Beyond, Third Edition © 2012 Principles of Computer Security: CompTIA Security+ ® and Beyond,
CERN – European Organization for Nuclear Research GS Department – Administrative Information Services Secure software development for the World Wide Web.
4.1.5 System Management Background What is in System Management Resource control and scheduling Booting, reconfiguration, defining limits for resource.
Network Isolation Using Group Policy and IPSec Paula Kiernan Senior Consultant Ward Solutions.
Environmental Council of States Network Authentication and Authorization Services The Shared Security Component February 28, 2005.
DESIGNING A PUBLIC KEY INFRASTRUCTURE
It’s always better live. MSDN Events Security Best Practices Part 2 of 2 Reducing Vulnerabilities using Visual Studio 2008.
Advanced Security Center Overview Northern Illinois University.
Information Networking Security and Assurance Lab National Chung Cheng University 1 Top Vulnerabilities in Web Applications (I) Unvalidated Input:  Information.
Security+ Guide to Network Security Fundamentals, Third Edition Chapter 9 Performing Vulnerability Assessments.
CS 290C: Formal Models for Web Software Lecture 1: Introduction Instructor: Tevfik Bultan.
CERN – European Organization for Nuclear Research GS Department – Administrative Information Services Secure software development for the World Wide Web.
ASP.NET 2.0 Chapter 6 Securing the ASP.NET Application.
Geneva, Switzerland, September 2014 ITU-T CYBEX standards for cybersecurity and data protection Youki Kadobayashi, NICT Japan Rapporteur, ITU-T Q.4/17.
Vulnerability Assessments
Software Process and Product Metrics
Software Security Course Course Outline Course Overview Introduction to Software Security Common Attacks and Vulnerabilities Overview of Security.
OWASP Mobile Top 10 Why They Matter and What We Can Do
D ATABASE S ECURITY Proposed by Abdulrahman Aldekhelallah University of Scranton – CS521 Spring2015.
Auditing Logical Access in a Network Environment Presented By, Eric Booker and Mark Ren New York State Comptroller’s Office Network Security Unit.
Copyright 2013 FUJITSU LIMITED. AGENDA Mitigation Considerations 4. Data Security – Examples and Application 2. Data Security Life-Cycle 1 1. Data Management.
Secure Software Development Mini Zeng University of Alabama in Huntsville 1.
Software Assurance Automation throughout the Lifecycle OWASP AppSec USA 2011 September 23 rd 2011.
EOSC Generic Application Security Framework
Management Information Systems
Security Management prepared by Dean Hipwell, CISSP
A Framework for Automated Web Application Security Evaluation
A Security Review Process for Existing Software Applications
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ Identity and Privacy: the.
Integrating Security Design Into The Software Development Process For E-Commerce Systems By: M.T. Chan, L.F. Kwok (City University of Hong Kong)
Configuring Electronic Health Records Privacy and Security in the US Lecture f This material (Comp11_Unit7f) was developed by Oregon Health & Science University,
Service Transition & Planning Service Validation & Testing
1 Smart Grid Cyber Security Annabelle Lee Senior Cyber Security Strategist Computer Security Division National Institute of Standards and Technology June.
 Chapter 14 – Security Engineering 1 Chapter 12 Dependability and Security Specification 1.
Chapter 1 Overview The NIST Computer Security Handbook defines the term Computer Security as:
Week 10-11c Attacks and Malware III. Remote Control Facility distinguishes a bot from a worm distinguishes a bot from a worm worm propagates itself and.
Cloud Computing Security Keep Your Head and Other Data Secure in the Cloud Lynne Pizzini, CISSP, CISM, CIPP Information Systems Security Officer Information.
Security+ Guide to Network Security Fundamentals, Third Edition Chapter 9 Performing Vulnerability Assessments.
Security Automation May 26th, Security Automation: the challenge “Tower of Babel” – Too much proprietary, incompatible information – Costly – Error.
Building Secure Web Applications With ASP.Net MVC.
COMP1321 Digital Infrastructures Richard Henson University of Worcester April 2013.
Lecture slides prepared for “Computer Security: Principles and Practice”, 3/e, by William Stallings and Lawrie Brown, Chapter 1 “Overview”. © 2016 Pearson.
PwC New Technologies New Risks. PricewaterhouseCoopers Technology and Security Evolution Mainframe Technology –Single host –Limited Trusted users Security.
Lesson 19-E-Commerce Security Needs. Overview Understand e-commerce services. Understand the importance of availability. Implement client-side security.
CSCE 548 Secure Software Development Security Operations.
Principles of Computer Security: CompTIA Security + ® and Beyond, Third Edition © 2012 Principles of Computer Security: CompTIA Security+ ® and Beyond,
Securing Java Applications
Chapter 1 The Software Security Problem. Goals of this course Become aware of common pitfalls. Static Analysis and tools.
Security Environment Assessment. Outline  Overview  Key Sources and Participants  General Findings  Policy / Procedures  Host Systems  Network Components.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
MD5 & Hash Encryption By Alex Buzak. Overview Purpose of MD5 and Hash Encryptions Examples MD5 Algorithm Explanation of Possible Security Risks Practical.
SANS Top 25 Most Dangerous Programming Errors Catagory 1: Insecure Interaction Between Components These weaknesses are related to insecure ways.
COMP1321 Digital Infrastructure Richard Henson February 2016.
ASP.NET 2.0 Security Alex Mackman CM Group Ltd
COMP2322 Networks in Organisations Richard Henson University of Worcester April 2016.
1/27 ITU-T CYBEX standards for cybersecurity information dissemination and exchange Odessa, Ukraine, June 2016 Martin Euchner Adviser, ITU-T ITU.
Washington DC – Mar 16, 2017 DL Name(s)
Web Application Vulnerabilities, Detection Mechanisms, and Defenses
Theodore Lawson CSCE548 Student Presentation, Topic #2
A Security Review Process for Existing Software Applications
THE STEPS TO MANAGE THE GRID
Download Latest CompTIA CAS-002 Exam Dumps PDF Questions - CAS-002 Best Study Material - Realexamdumps.com
Risk Assessment = Risky Business
CS2S562 Secure Software Development
How to Mitigate the Consequences What are the Countermeasures?
CVE.
Presentation transcript:

ITU-T CYBEX standards for cybersecurity information dissemination and exchange Youki Kadobayashi, Ph.D. NICT Japan / Rapporteur, ITU-T SG17 Q.4 ITU-T SG17 meeting (Geneva, 16 March 2016)

Capacity building with ITU-T cybersecurity standards ITU-T SG17 tutorial, 16 March 2016 Existing process-oriented standards, as well as checklist standards, should be complemented with detailed knowledge-base of cybersecurity, because: Cyber-risks are highly volatile Chain reactions are typical – difficult to estimate the risk without considering technical detail You’ll need to communicate the detail ITU-T provides knowledge-base standards 2

Knowledge base of vulnerabilities ITU-T SG17 tutorial, 16 March 2016 CVE: Common Vulnerability Enumeration A structured means to exchange information on security vulnerabilities and exposures and provides a common identifier for publicly-known problems. Standardized as ITU-T Recommendation X.1520 National databases: U.S. NIST NVD Japan JVN R. Martin, “Managing Vulnerabilities in Networked Systems”, IEEE Computer, 34(11), Nov

Example: vulnerabilities of widely used software for data protection purposes ITU-T SG17 tutorial, 16 March 2016 CVE entries for MySQL CVE entries for OpenSSL 4

Ongoing Proliferation of CVE 149 CVE-compatible products and services ITU-T SG17 tutorial, 16 March 2016 U.S.: NIST NVD Japan: IPA JVN 5

Taxonomy of vulnerabilities ITU-T SG17 tutorial, 16 March 2016 CWE: Common Weakness Enumeration Group same kind of vulnerabilities into a weakness, and give it a distinct number Provides common names for publicly known problems in the commercial or open source software Intended for security tools and services that can find weaknesses in source code and operational systems Helps better understand and manage software weaknesses related to architecture and design Standardized as ITU-T Recommendation X

CWE top 25 ‎ Prioritized list of dangerous software errors Intended to minimize software vulnerability and data breach Any software for data protection needs serious consideration of these failure modes, among others Useful for: Procurement Development, etc. RankScoreIDName [1]93.8CWE-89 Improper Neutralization of Special Elements used in an SQL Command [2]83.3CWE-78 Improper Neutralization of Special Elements used in an OS Command [3]79CWE-120Buffer Copy without Checking Size of Input [4]77.7CWE-79Improper Neutralization of Input During Web Page Generation [5]76.9CWE-306Missing Authentication for Critical Function [6]76.8CWE-862Missing Authorization [7]75CWE-798Use of Hard-coded Credentials [8]75CWE-311Missing Encryption of Sensitive Data [9]74CWE-434Unrestricted Upload of File with Dangerous Type [10]73.8CWE-807Reliance on Untrusted Inputs in a Security Decision [11]73.1CWE-250Execution with Unnecessary Privileges [12]70.1CWE-352Cross-Site Request Forgery (CSRF) [13]69.3CWE-22Improper Limitation of a Pathname to a Restricted Directory [14]68.5CWE-494Download of Code Without Integrity Check [15]67.8CWE-863Incorrect Authorization [16]66CWE-829Inclusion of Functionality from Untrusted Control Sphere [17]65.5CWE-732Incorrect Permission Assignment for Critical Resource [18]64.6CWE-676Use of Potentially Dangerous Function [19]64.1CWE-327Use of a Broken or Risky Cryptographic Algorithm [20]62.4CWE-131Incorrect Calculation of Buffer Size [21]61.5CWE-307Improper Restriction of Excessive Authentication Attempts [22]61.1CWE-601URL Redirection to Untrusted Site [23]61CWE-134Uncontrolled Format String [24]60.3CWE-190Integer Overflow or Wraparound [25]59.9CWE-759Use of a One-Way Hash without a Salt ITU-T SG17 tutorial, 16 March 20167

Quantification of vulnerabilities facilitates prioritization during vulnerability management ITU-T SG17 tutorial, 16 March 2016 CVSS: common vulnerability scoring system Base metrics: constant over time and across user environments Temporal metrics: reflects vulnerability landscape Environmental metrics: reflects user environments Standardized as ITU-T X

Knowledge base of attack patterns ITU-T SG17 tutorial, 16 March 2016 CAPEC: Common Attack Pattern Enumeration and Classification Dictionary of attack patterns, solutions & mitigations Facilitates communication of incidents, issues, as well as validation techniques and mitigation strategies Standardized as ITU-T Recommendation X

CAPEC example: SQL injection Summary, how it works, solutions and mitigations ITU-T SG17 tutorial, 16 March

Vulnerability assessment ITU-T SG17 tutorial, 16 March 2016 OVAL: Language for the open definition of vulnerabilities and for the assessment of a system state A standard for assessment and reporting of machine state of computer systems. OVAL includes a language to encode system details, and an assortment of content repositories held throughout the community. Standardized as ITU-T Recommendation X

Major ITU-T standards for cybersecurity Definitions, knowledge base standards ITU-T SG17 tutorial, 16 March 2016 X.1205, Overview of Cybersecurity X.1251, A framework for user control of digital identity X.1252, Baseline identity management terms and definitions X.1254, Entity authentication assurance framework X.1500, Overview of cybersecurity information exchange X.1520, Common vulnerabilities and exposures X.1521, Common vulnerability scoring system X.1524, Common weakness enumeration X.1525, Common weakness scoring system X.1526, Language for the open definition of vulnerabilities and for the assessment of a system state X.1528, Common platform enumeration X.1544, Common attack pattern enumeration and classification X.1546, Malware attribute enumeration and characterization 12

Improving cybersecurity throughout IT infrastructure lifecycle ITU-T SG17 tutorial, 16 March 2016 Development CWE X.1524 CAPEC X.1544 Deployment CVE X.1520 CVSS X.1521 Assessment OVAL X.1526 CPE X.1528 Knowledge bases, compatible products, informed communities and ITU-T Recommendations are already helping diverse organizations to protect their IT infrastructures and customers 13

Examples of CYBEX usage National coordination centers for cybersecurity make use of vulnerability information identifiers and scoring standards for public alerting purposes. Incident response teams efficiently keep track of vulnerabilities and attack patterns through a set of concise identifiers as predicated by CYBEX. System administrators assess presence of vulnerabilities using software tools that employ CYBEX. Cloud and network service providers keep track of vulnerabilities in their infrastructure, where they are prioritized according to impact, using the standardized scoring method. Embedded and IoT product developers learn typical patterns of software weaknesses through public knowledge base that is also part of CYBEX. Vulnerability researchers collectively maintain knowledge bases of vulnerabilities, each of which can be linked and integrated through common vulnerability identifiers. ITU-T SG17 tutorial, 16 March

Summary ITU-T SG17 tutorial, 16 March 2016 ITU-T cybersecurity standards provide critical instruments to deal with rapidly changing and diversifying cybersecurity phenomena, directly contributing to data protection Enumeration standards provides effective means of communication across businesses, government agencies as well as communities Cyber-risks are highly volatile and manifests through unexpected combination of components, that requires careful examination of technical risks through knowledge- base standards 15