12
HoliSec Holistic Approach to Improve Data Security Topic: WP2: Cryptographic support and key management Presenter: Christian Sandberg, Volvo GTT September 7, 2017. Time 13:00 – 13:20

13.00 HoliSec WP2 2017-09-07 Final - Autosec

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandberg,VolvoGTTSeptember7,2017.Time13:00 – 13:20

Page 2: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Presentation outline

2Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

• Purpose• Timeline• Tasks:

• SecOCFreshnesshandling• SecOCKeyderivation• Keymanagementlifecycle

Page 3: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Purpose

3Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

Hostandsupportotherworkpackageswithactivitiesrelatedtocryptography

Input:DerivecryptographicneedsfromWP1

Page 4: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Timeline

4Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

Deliverables

Q1/22017: ExtractingrequirementsfromD1.1CollectingOEMrequirementsonSecOCfreshnesshandling

Q3/42017: DocumentrequirementsAnalyzefreshnessalgorithmsAnalyzekeyderivationalgorithms

Page 5: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Tasks: SecOC freshness handling

5Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

• OEMtospecifyfreshnesshandlingalgorithm,notcoveredbytheAUTOSARstandard

• Freshnessascounter• IndividualcountersforeachPDU• Riskofgettingoutofsynchbetweensenderandreceiver

• Freshnessastime• Needtoensuresecureglobaltimebroadcastinthevehicle

Page 6: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Tasks: SecOC freshness handling

6Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

• Transparentgateways(repackagingmightputincreasedcertificationrequirementsongateways,e.g.ISO26262ASIL)

• J1939compliant(e.g.ForCAN8byteframes,29bitid...)• Samealgorithmformulti-protocol,e.g.CAN,Ethernet(aidgateway

transparency)• Avoidsinglepointoffailuredesigns• Considerresynchspeedtoquicklygetcommunicationrunninge.g.

followingstartup,sleep,orerroneousrestartbyacommunicatingparty.Exampleusecase:safetyapplications

• Vehiclemodeaware(e.g.keepbussilence,sleep)• Potentiallyeasiertograduallyintroducecounterbasedsolutioninlegacy

platformthanintroducesecureglobaltime

Page 7: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Tasks: Key derivation algorithms

7Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

EachPDUmayhaveauniquekey(e.g.AES128).WithmanyPDUsbeingcommunicatedtomanypeers,itwouldrequiresecurestorageofmanykeys.AwaytoaddressthisistoderivekeysfromasmallersetofmasterkeysusingKeyderivationalgorithms.

Masterkey

=f(PDUID, MasterKey)PDU1key

PDU2key

Page 8: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Tasks: Key derivation algorithms

8Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

Activities:

• Identifysuitablekeyderivationalgorithms

• Keyderivationalgorithmswillbeanalyzedforrelevantusecases

involving,amongothers,AUTOSARSecureOnboardCommunication

• Implementation

• Usage

• Evaluationofe.g.resourceneeds

Page 9: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Tasks: Key lifecycle management

9Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

Activities:

• ExtractkeylifecycleusecasesandrequirementsfromD1.1

• AnalyzehowNIST.SP.800-130/57(Part1-3)maybeusedforautomotive

keymanagementusecases

• DescribekeylifecycleprocessforselctedusecasesidentifiedfromD1.1

Page 10: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Tasks: Key lifecycle management

10Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

Example:D1.1RT-TN-10”Howtoprotectinformationheldinthevehiclefromunauthorizedmodificationanddeletion(dataatrest)”

Derivedusecases:• Securesoftwaredownload• Securestorageofdata

Exampleofhighlevelderivedsecurityrequirements:• ECU/Sensorshallusecryptographicmechanismtoensureintegrityofdata

atrest• ECU/Sensorshallusecryptographicmechanismtoensureauthenticityand

integrityofdatapackagesbeingdownloaded

Page 11: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Tasks: Key lifecycle management

11Topic:WP2:Cryptographicsupportandkeymanagement

Presenter:ChristianSandbergSeptember7,2017.Time13:00– 13:20

NIST.SP.800 Specifies,keyphases,activitiesandstates.Dependingonkeyusecases,akeymayenterthesephases/statesatdifferenttimesduringtheproductlifecycle,puttingrequirementsonhowtheyarehandledduringdevelopment,manufacturing,useinthefield,serviceworkshopsetc.

Page 12: 13.00 HoliSec WP2 2017-09-07 Final - Autosec

HoliSecHolisticApproachtoImproveDataSecurity

Thankyouforyourattention!