Introduction of CCDS- Toward Trustful IoT Life -Connected Consumer Device Security Council(CCDS）
Tsukasa Ogino, Representative Director

Copyright 2016 Connected Consumer Device Security Council Proprietary1

Contents••••••

Recognition of Current issues
CCDS Overview
CCDS R&D
CCDS Security Guideline Development
CCDS IoT Vulnerability Testing PF Development
CCDS other activities

Copyright 2016 Connected Consumer Device Security Council Proprietary2

ISSUE: Threats from Cooperated Devices
If even Single App is safe, but may be vulnerable in cooperated situation
Difference of security levels
between each apps domains

A consumer device infected malware
spread to other device and apps

ITS, Vehicle
AppsMalware

AV, HomeAppliance Apps

Apps
Cooperation

Medical,Healthcare
Apps
Intrusion

OtherConsumer
Devices

Energy, HEMS
Apps
3

Intrusion via vulnerable app,
Crack to cooperative app

Server Cooperation
Copyright 2016 Connected Consumer Device Security Council Proprietary3

Trust(safety and security)Level Difference①Different Level of Requirement
For Safety and Security Levelby product domains

Required or Demanding Level

Actual Product Level

安心・安全安心・
安全安心・安
全②Total Security Level
will be leveledat the lowest product
When connectedDomain Ａ 連携 Domain Ｂ 連携 Domain ＣProductProductProductCopyright 2016 Connected Consumer Device Security Council Proprietary

4Value and Cost Balance

IoT service
value
Function andArchitecture
Cost Up by complex architecture

Comply Important
Requirement
such as Safety＞

Security
Protection
CostSafety

ISO/IEC 61508 SIL 1～4
ISO 26262 ASIL QM, A～D, etc

Security

ISO/IEC 15408/CC EAL 1～7
FIPS 140-2 Level 1～4
ETIS ITS/C2C-CC TAL 1～4, etc

Countermeasure
Also countermeasureby architecture and Usability

Quality
Keep Higher Quality

Different Priority and Judgement level
Product domain by domain
Copyright 2016 Connected Consumer Device Security Council Proprietary5

CCDS Overview•

Name: General Incorporated Association: Connected Consumer Device Security Council••

Establishment: October 6, 2014
Chairman: Hideyuki Tokuda (Professor of Keio University, Cabinet Security Advisor)•

Representative Director: Tsukasa Ogino (Specially Appointed Professor, Kyoto University)••

Managing Director: Kosuke Ito (Zero-one Laboratory)
Directors: Atsuhiro Goto (Professor, Institute of Information Security, SIP: PD)
Katsutoshi Hasegawa (President, eSOL Co., Ltd.)
Hiroyuki Hattori (President, Witz Co., Ltd.)•

Number of members: 129(Official members or higher: 43, General members: 62, Academic members: 14, Liaison members: 10)•

Main businesses:
1.

2.
3.
4.

Internal/external trend investigation on security in various field of life devices, andinterchange/cooperation with internal/external organizations
Development of security technology which satisfies safety and security of life devices
Development of security design process, development/preparation of verification method
guidelines and promotion of international standardization
Preparation/control of life device verification environment, verification business and humanresource development on security, public relations/dissemination activity, etc.
Copyright 2016 Connected Consumer Device Security Council Proprietary

6SCOPE:
Embedded/IoT/M2M in general, Connected Consumer Devices
which are not operated (monitored and controlled) by professionals
HEMS Network
Power, Utility

SmartMeter

AV Network

PVHomeAppliance

Battery

4K・8K
Contents

Wearable
Devices
Medical, Healthcare
Devices

HomeServer

HEMS
ConsoleMFP

Healthcare
serverHEMS
company

Home Gateway
Automated Driving

Road SideUNIT

CloudContents
ProviderAfterDevices

ECU

Medical,Healthcare

Telematics, Eco,
Drive Recorder, etc.

Vehicle andTraffic Control

Convenience

V2X Communication
PotableDevices

ITS＆Vechile Safety

Office Area
NetworkCare Robots

NetworkAppliance
EV/HV

Medical/Healthcare
Network

New Services

お弁
当セール

ATM

Public Area
Devices

Remote Monitor/ Maintenance

Copyright 2016 Connected Consumer Device Security Council Proprietary

7

CCDS Organization
CCDS
Secretariat Office

ReviewCommittee

Administration

Vulnerability
Testing Center

R&D Center

IoT Security
Guideline WG

IoT Vuln. R&D Unit
No1, No2Car
Sub WG

Home NW
Sub WGATM
Sub WGPOS
Sub WGUsability WG

Car-A: Vuln. Testing Tool for
Com Unit (Navigation)
Car-B: Vuln. Testing Tool for
Body control ECUs

Security
Tech. WGDeviceSecurity
Technology
WG

Home GW: Vuln. Testing
Tool for Home NW Devices
ATM: ①Tool for ATM,
②Tool for USB Test PF
POS: Vuln. Testing tool forOpen POS (Tablet type)
Platform for Vuln. Testing
operation for IoT system

Copyright 2016 Connected Consumer Device Security Council Proprietary8

R&D Units activities• Unit 1 (stationed in Okinawa):– Unit Leader: Dr. Inoue, Assoc. Prof. of Hiroshima City Univ.

– R&D in Car Hacking (CAN) hacking, USB Hacking, Feedback fuzz
data processing function on fuzzing tool, etc.

• Unit 2:– Unit Leader: Dr. Ogino, Kyoto Univ.
– R&D in Home GW vulnerability research, Auto Vulnerability
checker for Android apps, etc.

Copyright 2016 Connected Consumer Device Security Council Proprietary9Cyber Security Policy for Vitalizing Society andits sustainable development by NISC
Security By Design (SBD)
System Design with Security Considerationfrom planning and design stage

Preparation of the general guidelines
to affect security on IoT system
Enforcement of the technology development and proof trial
in consideration of the characteristic (long life cycle,limit of the processing capacity) of the IoT system,
importance of the hardware genuine nature

出典：NISC:サイバーセキュリティ戦略（案）より
Copyright 2016 Connected Consumer Device Security Council Proprietary

10

CCDS External Cooperation

IoT Security Guideline Dev.

WG on theDevelopment Guideline
for the Smart-society

・Design Process Guide = Security by Design
・Security Testing Guide ->International Std.
toward the safe and secure IoT service/product development!

IoT Vuln. Evaluation PF Dev.
・Vulnerability Testing Tool Development
・Testing Scenario Development
Developing the Security Testing Platform
Copyright 2016 Connected Consumer Device Security Council Proprietary

11PLAN: Security Development Guideline Definition
Security Development Guideline
Per Domains

CommonV2X, Probe
Remote Access,Control

Arrange basic
items forembed devices

Vehiclecommon part

Discuss Integrated
situation includes
cyber spacefor Automated Drv.
Health Data
Embedded
DomainWearable Comm.
Remote Access,Control
HEMS Cooperation

Healthcare
Devicescommon part

Embedded
Systems
common part(Base)

HomeAppliancecommon part

Cooperated
Services
common part

Office Devices (MFP, etc.)
Public Space Devices(ATM, etc.)
CyberSystem
DomainAs a beginning,
Discuss for each Apps

Arrange eachcommon part

Copyright 2016 Connected Consumer Device Security Council Proprietary

12

CCDS life device security guideline for each field v1.0
PurposeSince threats for each product field vary,
security actions are summarized in viewof each field based on IPA "Development
guideline of connecting world" to easily
disseminate the security-by-designconcept in the industry.

Target field
Onboard unit
IoT gateway

Financial terminal(ATM)
Accounting terminal(POS)

Onboard system configuration

IoT-GW: Home GW case

Major contents of guideline
・ Target system configuration
・ Anticipated security threat・ Security action in each phase of productlife cycle(Relationship with IPA "Development
guideline of connecting world")

・Threat analysis/risk evaluation method
・ 3rd party security evaluation for entire
product and security measure function
English Version are coming soon!

ATM system configuration

POS system configuration

Copyright 2016 Connected Consumer Device Security Council Proprietary13

Position of guideline for each CCDS field (private opinion)
IoT security
generalframework
NISC

Cyber securitystrategy
NISC
Proposal of IoT systemdevelopment by Security-bydesign concept

Proposal

Clarification of general basic requirements related todesign, building and operation of the IoT system

IoT service
providerReference

IoT security
guideline
IoT Promotion
Consortium
MIC and METI
Refer to review forcooperation.

Development
guideline ofconnecting
world

Cooperationforindustry
deployment

International deploymentof Japanese idea

CCDS
Onboardunit

CCDS
IoT-GW

Security guideline for all layers of IoT service
relevant persons

IoT platform/network
providerSafe and secure IoT system development guideline
which can be used across product fields(checklist)

CCDSATM

Specific threat or risk point in viewof each product field
Summary of security review points
from design stage

IoT systemvendor

CCDS
OpenPOS

Copyright 2016 Connected Consumer Device Security Council Proprietary14

Founding the 3rd Party Security V&V Evaluation Center
Okinawa Pref.

ＩＰＡ

Participants from Major Brands

FY2015～FY2017

ＣＣＤＳ
重要生活機器連携セキュリティ協議会

Automotives
On-Board Head Units,
Body Control ECUs

IoT Vuln. Testing Ctr.

R&D Center

Working Group onDevelopment Guideline
for Smart-Society

Home
IoT Security Guideline
Development WG

Home GW, IoT GW
for sensor network

Financial Terminals
ATM/POS

Testing
Tool Dev.

ATM/POS

Evaluation Testing
Platform System
IoT Evaluation Test Scenario
And Test result Integration

Testing
Process Dev.

Testing DB
Dev. & Ope

Trial Testing（Training)

Certification
Authority(Future)Vuln.
Evaluation
Platform

3rd Party
TestingService

3rd Party Security
V&V Evaluation Ctr(Future)Venders in Okinawa

V&V: Verification and Validation
Vuln: Vulnerability
Copyright 2016 Connected Consumer Device Security Council Proprietary
15CCDS IoT Vulnerability Testing Units
Review Committee

JVC Kenwood

Test Tool Development Team
Product Testing TeamWitz

Test Tool Development Team
Product Testing Team

HomeHITACHI

Test Tool Development Team
Product Testing TeamATMHitachi Omron

Test Tool Development Team
Product Testing Team

POS(Point of Sales)

Omron SW

Test Tool Development Team
Product Testing TeamIoT Vuln. Testing
Platform System

BBTower

Test Tool Development Team
Product Testing Team

Automotives

Copyright 2016 Connected Consumer Device Security Council Proprietary16

Other CCDS activities• Usability WG– Objective: Discussing UI design as a part of security
countermeasures to keep the IoT devices in secured• Collaboration with HCD-net（人間中心設計推進機構）– Leader: Ueyes’ Design– Kicked off in Aug., 2016., participating about 20 members• Device Security Technology SWG– Objective:• Building comprehensive security countermeasure technologies MAP(categorizing) for IoT devices• Envisioning to develop the Implementation Guideline for IoTsecurity countermeasures in future– Leader: SELTECH, Deputy Leader: DNP (Dai-Nippon-Printing)– Kicked off in Jun., 2016., participating about 35 members

Copyright 2016 Connected Consumer Device Security Council Proprietary17