text: Security and Resilience of Smart Home Environments

text: Good Practices and Recommendations | December 2015

text: http://ec.europa.eu/priorities/digital-single-market/ http://ec.europa.eu/justice/data-protection/article-29/documentation/opinionrecommendation/files/2014/wp223_en.pdf http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31995L0046:en:HTML http://ec.europa.eu/justice/data-protection/article-29/documentation/opinionrecommendation/files/2014/wp213_en.pdf https://www.fiware.org http://www.aioti.eu http://ec.europa.eu/digital-agenda/en/news/conclusions-internet-things-public-consultation

text: Figure 1: Scope of the study

text: CONSTRAINEDbDEVICES HIGHbCAPACITYbDEVICES

text: Securityb alarms AudiobLbVisualbsystems Smartb -smartbTVBbTVbsetwtop lightbbulbs boxesMMMx Surveilance IPbcameras BroadbandbroutersbL Smartbsmoke homebgatewaysbL detectors smartbhubs Smart appliances Smartb Network thermostats AttachedbStorage

text: Smart locks

text: MOBILEb REMOTEbSERVICES APPLICATIONS

text: Processing Localbdevice Cloudbstorage management andbinteraction Device Userbaccount Management orbdatabmanagement

text: Remotebdevicebmanagement andbinteraction

text: RFC 7228, IETF https://tools.ietf.org/html/rfc7228

text: Figure 2: Example of several network types found in a Smart Home Environment

text: HO KS M OR E A W ET RE

text: SmartHH A N SecurityH locks N alarms

text: EA ET R W

text: A WAN PAN O E LP-

text: R ID K

text: S HIG S

text: W SetHH RK H NetworkH

text: O HHS

text: topHbox AttachedH W PE Storage

text: ET ED HNH H D HN EE ET P W HS H O

text: H SmartHHome R IG gateway H KS H Audio SmartHH orHhub phone visual systems

text: SmartHenergy Advanced management metering devices infrastructure

text: ADV UR ANCED UCT METERING INFRASTR

text: Table 1: Classes of IoT devices and the impact on their security capabilities.

text: EXAMPLE OF EXAMPLE OF MEMORY EXAMPLES OF TYPICAL IMPACT ON SECURITY DEVICE TYPE CLASS RAM STORAGE DEVICES CAPABILITIES CAPACITY CAPACITY

text: Class 0 devices may not be Constrained 0 << 10 KiB << 100 KiB Low-end sensors able to implement real security device measures

text: Class 0

text: EXAMPLE OF EXAMPLE OF MEMORY EXAMPLES OF TYPICAL IMPACT ON SECURITY CLASS RAM DEVICE TYPE STORAGE DEVICES CAPABILITIES CAPACITY CAPACITY

text: Class 1 devices may use dedicated protocols designed 10 for constrained nodes (such as Smart bulbs, 1 ~ 10 KiB ~ 100 KiB 11 CoAP) but they cannot use Smart locks Class 1 stronger standard security protocols

text: Class 2 devices have the Smart appliances, capacity to implement most high-end smart standard security protocols 2 ~ 50 KiB ~ 250 KiB sensors (such as (even if other limitations can Class 2 smart cause issues, such as thermostats) communication bandwidth)

text: High-capacity devices may include dedicated security hardware and/or are able to perform intensive Smart hubs or computation. They are able to >> 50 KiB >> 250 KiB gateways, Smart provide additional security TVs mechanisms to protect the

text: High-capacity device

text: other devices on the HAN (for example perform key generation or network scan)

text: For example http://www.anandtech.com/show/9372/lifx-white-800-smart-bulb-capsule-review. For example https://www.nordicsemi.com/eng/News/News-releases/Product-Related-News/Noke-Bluetooth- Smart-padlock-employs-Nordic-Semiconductor-technology-to-eliminate-keys-or-combinations-and-enable-operationfrom-smartphone

text: Capgemini - Securing the IoT Opportunity, https://www.capgemini.com/resource-file-access/resource/pdf/ securing_the_internet_of_things_opportunity_putting_cyber_security_at_the_heart_of_the_iot.pdf NCC Group - Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond McAfee Labs - Threats Report November 2014 https://www.mcafee.com/ca/resources/reports/rp-quarterly-threat-

text: FTC - Internet of Things - Privacy & Security in a Connected World https://www.ftc.gov/system/files/documents/reports/federal-trade-commission-staff-report-november-2013-

text: Kaspersky Lab – Surviving in an IoT-enabled world https://securelist.com/analysis/publications/72595/surviving-in-

text: See http://mozaiq-operations.com See http://www.theregister.co.uk/2015/10/19/bods_brew_ikettle_20_hack_plot_vulnerable_london_pots/

text: See The Internet of Fails Where IoT Has Gone Wrong and How We're Making It Right

text: See Structural Weaknesses in the Open Smart Grid Protocol and Dumb Crypto in Smart Grids: Practical Cryptanalysis of the Open Smart Grid Protocol See “Directive

text: ” and its amendment “

text: Regulation (EC) No 1882/2003

text: ”. http://eur-lex.europa.eu/legalcontent/EN/TXT/?uri=URISERV:l14012 See “COM/2012/011 final - 2012/0011 (COD) - Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on the protection of individuals with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation)”. http://eur-lex.europa.eu/legalcontent/en/TXT/?uri=CELEX:52012PC0011 Even smartphones, that raise many privacy issues, would not be able to constantly and stealthily record their user: a smartphone camera does not point directly, and constantly, at the user living room; additionally, the battery drain alone would be enough to warn users that something went wrong with their device. These limitations however do not apply to a Smart TV, which causes much more privacy issues with that regard, as explained in “The Outer Limits: Hacking the Samsung Smart TV” by Aaron Grattafiori and Josh Yavor, and “Hacking, surveilling, and deceiving victims on Smart TV” by Seung-Jin Lee and Seung-Joo Kim

text: See for example https://www.defcon.org/html/defcon-23/dc-23-speakers.html#Petro See The Internet of Fails Where IoT Has Gone Wrong and How We're Making It Right See e.g Executive summary of the Opinion of the European Data Protection Supervisor on the Commission's Communication on Unleashing the potential of cloud computing in Europe 2013/C 253/03, where the “key action 1” is “cutting through the jungle of standards” See The Internet of Fails Where IoT Has Gone Wrong and How We're Making It Right

text: See for example IoT-A - D4.2 - Concepts and Solutions for Privacy and Security in the Resolution Infrastructure

text: Figure 3: Good practices within the Smart Home lifecycle and their applicability to stakeholders

text: ENDgUSERS ELECTRONIClCOMMUNICATIONlPROVIDERS

text: DEVELOPMENTlOFlSMART INTEGRATIONlOFlDEVICES USAGElUNTILlENDgOFgLIFE HOMElDEVICESlANDlSERVICES INTOlTHElHOMElAREAlNETWORK

text: Securitylofltheldevelopment Minimumlreliability Protectionlofldatalexchanges

text: process GHardware GEnsureGaccessGrights GDesignGphase Software GGatewayGforGsecurity GDevelopmentGphase SegregationGwithGtheGAMI

text: TestingGphase Operationallsecurity GTrustGinfrastructure Securitylfunctionslforlhardware SecureGpairing andlmaintenance andlsoftware CheckGsecurityGassumptions VulnerabilityGsurvey SecurityGaudit Networklsecurity SecurityGupdates CommunicationGprotection RemoteGinterfacesGprotection GGatewayGforGsecurity Cryptography NetworkGsegregation GGSecurityGmanagementGsystem UserGdataGprotection forGsupportGinfrastructure GGIdentification,Gauthentication, Controllofluserldata authorisation GGSecureGbackupGand/orGdeletion Self-protection ofGdata

text: Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond, NCC group See for example https://www.nsa.gov/ia/_files/support/defenseindepth.pdf

text: See FTC Careful connections and FTC - Internet of Things - Privacy & Security in a Connected World for data collection

text: See Internet of things research study, HP 2014. Licensed tools exist for static analysis, but several free alternatives also provide valuable information, such as Clang or Findbugs Options vary depending on the language, compiler and target OS; to see what kind of protection they can provide, see for example https://wiki.debian.org/Hardening (gcc under Debian). See for example https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0313 ASLR or CFI are examples of such options (see http://pax.grsecurity.net/docs/aslr.txt and http://clang.llvm.org/docs/ControlFlowIntegrity.html). Other mechanisms exist, a recent albeit controversial example being RASP (runtime application self-protection)

text: See https://opencryptoaudit.org/ https://www.owasp.org ASLR or CFI are examples of such options (see http://pax.grsecurity.net/docs/aslr.txt and http://clang.llvm.org/docs/ControlFlowIntegrity.html). Other mechanisms exist, a recent albeit controversial example being RASP (runtime application self-protection)

text: See BSI - Privacy Impact Assessment Guideline (Kurzfassung), https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/ElekAusweise/PIA/ Privacy_Impact_Assessment_Guideline_Kurzfasssung.pdf?__blob=publicationFile See CNIL – Guides pratiques, http://www.cnil.fr/fileadmin/documents/Guides_pratiques/CNIL-PIA-1-Methode.pdf, http://www.cnil.fr/fileadmin/documents/Guides_pratiques/CNIL-PIA-2-Outillage.pdf and http://www.cnil.fr/fileadmin/documents/Guides_pratiques/CNIL-PIA-3-BonnesPratiques.pdf

text: http://www.commoncriteriaportal.org See Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond, NCC group and see OWASP I8 | Insufficient Security Configurability For example the stack trace in Java, or the memory current status

text: See The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right see OWASP I8 | Insufficient Security Configurability See OWASP I9 | Insecure Software/Firmware, or Symantec Insecurity in the Internet of things, March 12, 2015 See OWASP I4 | Lack of Transport Encryption Or DTLS for datagram communication such as UDP

text: See the example of Bluetooth, including Bluetooth 4.0, in Guide to Bluetooth Security - Recommendations of the National Institute of Standards and Technology - John Padgette, Karen Scarfone, Lily Chen See for examples replay attacks, or attacks on key provisioning in KillerBee: Practical ZigBee Exploitation Framework or “Wireless Hacking and the Kinetic World”, by Joshua Wright. 6LowPAN was also successfully attacked, see for example Hacking into Internet Connected Light Bulbs, Alex Chapman, 04 July 2014 See for instance attacks on WEP http://eprint.iacr.org/2007/120.pdf, WPS PIN vulnerability https://www.kb.cert.org/vuls/id/723755 or the Pixie Dust attack on WPS https://passwordscon.org/wpcontent/uploads/2014/08/Dominique_Bongard.pdf SSL and TLS have a long history of security vulnerabilities (see https://tools.ietf.org/html/rfc7457). TLS and DTLS share some vulnerabilities, for example CVE-2013-0169, also known as Lucky13 See for example CVE-2015-0204 at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0204 See “How can OpenSSL be fixed ?” at http://heartbleed.com/ See http://cognosec.com/zigbee_exploited_8F_Ca9.pdf

text: See OWASP I3 | Insecure Network Services See https://www.enisa.europa.eu/activities/risk-management/evolving-threat-environment/enisa-thematiclandscapes/threat-landscape-of-the-internet-infrastructure http://www.gsma.com/connectedliving/gsma-iot-device-connection-efficiency-guidelines/ See for example see Symantec Insecurity in the Internet of things, March 12, 2015 or Careful connections by FTC This study will not delve into the detailed requirements for cryptographic algorithms or acceptable keys sizes, since most of national cybersecurity agencies already provide consistent guidance on this topic

text: See https://www.enisa.europa.eu/activities/identity-and-trust/library/deliverables/algorithms-key-size-andparameters-report-2014 See examples in http://csrc.nist.gov/publications/nistpubs/800-90A/SP800-90A.pdf Symantec Insecurity in the Internet of things, March 12, 2015 It should be reminded that this study does not consider side-channel attacks, which would require further development on the topic of hardware cryptography.

text: See for example the Home Gateway Initiative: http://www.homegatewayinitiative.org/publis/RD039-Req-for- Wireless-home-area-networks.pdf See A proposal for: Functionality classes for random number generators, Version 2.0 , 18 September 2011 See for example See Making Smart Locks Smarter (aka. Hacking the August Smart Lock) or the Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right and LIFX vulnerability See for example GSMA remote provisioning architecture and Security of Things: An Implementers’ Guide to Cyber- Security for Internet of Things Devices and Beyond, NCC group

text: See SQRL Authentication. https://en.wikipedia.org/wiki/SQRL This study will not delve into the detailed requirements for cryptographic algorithms or acceptable keys sizes, since national cybersecurity agencies already provide consistent guidance on this topic http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31995L0046:en:HTML See http://www.lifehacker.com.au/2015/02/why-the-internet-of-things-is-a-problem-for-metadata-retention/ While the Terms and Conditions are a practical support for the vendors, many actors consider that this cannot be considered a good practice. In particular, the user may be lost in a barely-legible legalese instead of being able to make informed choices regarding their privacy. The US FTC gives recommendations on this topic, for example using other supports such as registration emails.

text: The European directive also includes cases where “processing is necessary in order to protect the vital interests of the data subject”, or “for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller or in a third party to whom the data are disclosed.” This topic could be typically related to the use cases of smoke or CO2 detectors. See for example OWASP I5 | Privacy Concerns

text: 77 o “one-way” or “non-reversible” measures such as truncation or a hash function. o reversible such as encryption (see good practices on Cryptography). Encrypted storage can also address authenticity or integrity of user data if combined with the right mechanisms (for example AES-GCM).  Pseudonymity and mainly unlinkability measures, such as ensuring that data is not correlated.

text: Truncation is often used in the payment industry to anonymize cardholder data (see https://www.pcisecuritystandards.org/documents/PCI%20SSC%20Quick%20Reference%20Guide.pdf) Hash functions also have vulnerabilities (see for example https://en.wikipedia.org/wiki/Cryptographic_hash_function). As for other cryptographic operations, robust standard mechanisms should be preferred – vendors are encouraged to contact their national cybersecurity agency if needed. See The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right, OWASP I5 | Privacy Concerns and OWASP I10 | Poor Physical Security See IoT-A - D4.2 - Concepts and Solutions for Privacy and Security in the Resolution Infrastructure See for example IoT-A - D1.5 - Final architectural reference model for the IoT v3.0 See Symantec Insecurity in the Internet of things, March 12, 2015

text: See See Home Automation Benchmarking by SYNACK, but also Making Smart Locks Smarter (aka. Hacking the August Smart Lock), The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right. See example of TRENDnet IP cameras vulnerability See Home Automation Benchmarking by SYNACK or Making Smart Locks Smarter (aka. Hacking the August Smart Lock). For details on Certificate pinning, see https://www.owasp.org/index.php/Certificate_and_Public_Key_Pinning#What_Is_Pinning.3F see OWASP I2 | Insufficient Authentication/Authorization, I6 | Insecure Cloud Interface, I7 | Insecure Mobile Interface See NIST Special Publication 800-63-2 – Electronic Authentication Guideline See “Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond, NCC group” See for example “Smart TV Security - #1984 in 21st century” I5 | Privacy Concerns See The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right

text: See OWASP I8 | Insufficient Security Configurability See I2 | Insufficient Authentication/Authorization and OWASP I1 | Insecure Web Interface. See also see Symantec Insecurity in the Internet of things, March 12, 2015 See OWASP I1 | Insecure Web Interface, OWASP I6 | Insecure Cloud Interface, OWASP I7 | Insecure Mobile Interface See Home Automation Benchmarking by SYNACK, and Careful Connections by FTC See Home Automation Benchmarking by SYNACK, also The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right. See OWASP I2 | Insufficient Authentication/Authorization See Careful Connections – FTC. See https://www.owasp.org/index.php/Password_Storage_Cheat_Sheet. Hash functions such as MD5, SHA should not be used for password protection, and even SHA256 or SHA3 would lack the additional work factor to be efficient in a password storage context see Symantec Insecurity in the Internet of things, March 12, 2015 and Home Automation Benchmarking by SYNACK see OWASP I2 | Insufficient Authentication/Authorization See OWASP I2 | Insufficient Authentication/Authorization and OWASP I8 | Insufficient Security Configurability An example of policy can be found at https://www.sans.org/security-resources/policies/general/pdf/passwordprotection-policy. Policies may vary depending on the threat analysis and dimensions (such as password length) also

text: depend on attacker’s capabilities, especially the computing power, which grows constantly over time. Vendors are invited to contact their national cybersecurity agency or CERT to stay informed of the state-of-the-art. See http://www.enisa.europa.eu/media/news-items/basic-security-practices-regarding-passwords-and-onlineidentities See OWASP I2 | Insufficient Authentication/Authorization See The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right See for example Veracode White Paper – The Internet of Things: Security Research Study, 2015, and also The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right See The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right Hardware protection measures are related to:  threats that are not related to privacy, and where the user itself is the attacker (for example fraud use cases);  threats to equipment that is not protected by physical measures (typically smart locks, cameras…). These are also related to attackers with very high skills and motivation profiles (which is for example the model used in smartcards). In the Smart Home context, this could typically apply to Advanced Persistent Threats (APT) or surveillance topics, where the physical tampering of Smart TVs could turn them into unwanted surveillance tools. This study aims at defining a minimum baseline of security, thus will not address these “high profile” attacks. For information, the security hardware that can be used in several Smart Home devices (smartcards, TPMs) typically include countermeasures against this type of attacks, for example:  Use of tamper-resistant hardware such as Active shields.  Protection against glitch.  Protection against fault injection.  Protection against side channels (for example electromagnetic or power analysis).

text: Examples can be found for example in Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond, NCC group. Even if this level of security cannot be required for all Smart Home devices, several physical protection measures can be recommended to ensure a better overall security on the device. Hacking IoT: A Case Study on Baby Monitor Exposures and Vulnerabilities, Rapid 7, September 2015 Introduction to Embedded Security, Joe Grand, Black Hat USA 2004 Physical protection: Anti-tamper mechanisms in Common Criteria security evaluations, Epoche & Espri, ICCC Norway 2010

text: “Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond, NCC group” states that “For chips with security features or functionality that may impact security it is important to understand where these are located on the chip’s pin out. It is generally advisable not to use chips where these features are on the outer two rows in high-security environments due to risk of fly wires being used.” Some labs consider today that for “grid array” chip carriers, the outer three or four rows might be relatively easy to access for an attacker. In any case, a consensus is needed amongst stakeholders and security labs on this topic, so cybersecurity agencies could provide vendors with clear recommendations. See for example IoT-A - D4.2 - Concepts and Solutions for Privacy and Security in the Resolution Infrastructure or https://www.blackhat.com/docs/us-14/materials/us-14-Jin-Smart-Nest-Thermostat-A-Smart-Spy-In-Your-Home- WP.pdf See Symantec Insecurity in the Internet of things, March 12, 2015 https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP I3 | Insecure Network Services

text: See for example Symantec Insecurity in the Internet of things, March 12, 2015, IoT-A - D4.2 - Concepts and Solutions for Privacy and Security in the Resolution Infrastructure or https://www.blackhat.com/docs/us- 14/materials/us-14-Jin-Smart-Nest-Thermostat-A-Smart-Spy-In-Your-Home-WP.pdf See The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right and OWASP I10 | Poor Physical Security See A Primer on IoT Security Research, March 30 2015, Stanislav See OWASP I8 | Insufficient Security Configurability and See Security of Things: An Implementers’ Guide to Cyber- Security for Internet of Things Devices and Beyond, NCC group

text: See Symantec Insecurity in the Internet of things, March 12, 2015 and The Internet of Fails Where IoT Has Gone Wrong and How We're Making It Right See Home Automation Benchmarking by SYNACK, or OWASP I3 | Insecure Network Services See Symantec Insecurity in the Internet of things, March 12, 2015 See for example Veracode White Paper – The Internet of Things: Security Research Study or Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond, NCC group see OWASP I10 | Poor Physical Security https://en.wikipedia.org/wiki/DMA_attack see e.g. OWASP I10 | Poor Physical Security

text: see Symantec Insecurity in the Internet of things, March 12, 2015 see Symantec Insecurity in the Internet of things, March 12, 2015 See Home Automation Benchmarking by SYNACK See for example http://knowledge.seagate.com/articles/en_US/FAQ/174791en?language=en_US

text: See for example See Home Automation Benchmarking by SYNACK See for example The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right, or

text: OWASP I8 | Insufficient Security Configurability

text: See for example Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond, NCC group, or OWASP I8 | Insufficient Security Configurability See for example IoT-A - D4.2 - Concepts and Solutions for Privacy and Security in the Resolution Infrastructure For example, the Thread group uses J-PAKE, see Thread commissioning, July 2015, http://threadgroup.org/Portals/0/documents/whitepapers/Thread%20Commissioning%20white%20paper_v2_public .pdf

text: See Fact sheet FS 2011-07 DigiNotar certificates and machine-to-machine (M2M) communication, GOVCERT.NL See http://crypto.stanford.edu/~dabo/pubs/abstracts/ssl-client-bugs.html See A comparison between traditional Public Key Infrastructures and Identity-Based Cryptography, Kenneth G. Paterson and Geraint Price and Identity-based cryptography: Panacea or Pandemonium? Kenny Paterson, ECC 2005 See http://scissor-project.com and related paper at http://www.wseas.us/elibrary/conferences/2015/Dubai/CEA/CEA-01.pdf See for example OneM2M TS-0003-V1.0.1, Security solutions, 30 January 2015 An overview of the different methods, albeit not focused on security, can be found in A comparative study of secure device pairing methods (ArunKumar, Nitesh Saxena, Gene Tsudik, Ersin Uzun) and Serial Hook-ups: A Comparative Usability Study of Secure Device Pairing Methods (Alfred Kobsa, Rahim Sonawalla, Gene Tsudik, Ersin

text: Uzun, Yang Wang)

text: See Stefan Viehböck - Brute forcing Wi-Fi Protected Setup - When poor design meets poor implementation An Experimental Study of Security and Privacy Risks with Emerging Household Appliances (Position Paper) See for example See The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right See Stefan Viehböck - Brute forcing Wi-Fi Protected Setup - When poor design meets poor implementation See for example IoT-A - D1.5 - Final architectural reference model for the IoT v3.0 See for example IoT-A - D4.2 - Concepts and Solutions for Privacy and Security in the Resolution Infrastructure

text: See for example in the BSI Smart Meter Gateway PP: “The Gateway connects a Wide Area Network (WAN) with a Network of Devices of one or more Smart Metering devices (Local Metrological Network, LMN) and the consumer Home Area Network (HAN), which hosts Controllable Local Systems (CLS)” (https://www.commoncriteriaportal.org/files/ppfiles/pp0073b_pdf.pdf) See The Current State Of Smart Locks See The Internet of Fails: Where IoT Has Gone Wrong and How We're Making It Right See FTC Careful Connections See also the global bounty aggregator https://firebounty.com

text: see Symantec Insecurity in the Internet of things, March 12, 2015 or FTC - Careful Connections See for example Nest product recall: http://www.cpsc.gov/en/Recalls/2014/Nest-Labs-Recalls-to-Repair-Nest- Protect-Smoke-CO-Alarms/ http://ec.europa.eu/justice/data-protection/article-29/documentation/opinionrecommendation/files/2014/wp213_en.pdf see Symantec Insecurity in the Internet of things, March 12, 2015 and Security of Things: An Implementers’ Guide to Cyber-Security for Internet of Things Devices and Beyond, NCC group see Symantec Insecurity in the Internet of things, March 12, 2015 and OWASP I9 | Insecure Software/Firmware See OWASP I9 | Insecure Software/Firmware

text: See What to Consider When Buying a Smart Device, TrendMicro See ENISA - Auditing Security Measures - An Overview of schemes for auditing security measures, September 2013

text: See https://resilience.enisa.europa.eu/cloud-computing-certification Description of typical measures and issues can be found in NIST Guidelines on Security and Privacy in Public Cloud

text: See for example http://www.homegatewayinitiative.org/ See for example OWASP testing guide (https://www.owasp.org/index.php/OWASP_Testing_Guide_v4_Table_of_Contents) See http://arstechnica.com/security/2015/08/uber-hires-researchers-who-hacked-chrysler-uconnect/

text: Code review typically in the case of mobile applications or embedded systems. In the case of more complex systems or even infrastructure, a configuration review would be more appropriate. White-box consists in testing a product with all the design and development knowledge, including source code. A grey-box approach would consist in not having the code but developer information such as credentials. Fuzzing is a black-box approach (no information is known on the product), where random data is given to the product to assess its robustness. The automation of the method is intended to compensate the lack of knowledge on the product. See for example Who Should be Responsible for Software Security? A Comparative Analysis of Liability Policies in Network Environments, Terrence August and Tunay I. Tuncay, March 2011

text: See https://abc4trust.eu See ISO/IEC 29191, ISO/IEC 20008 and ISO/IEC 20009. This “anonymous authentication” should not be mistaken for the “anonymous authentication” as defined in Microsoft IIS. See https://crypto.stanford.edu/craig/craig-thesis.pdf https://en.wikipedia.org/wiki/Secure_multi-party_computation

text: Figure 4: Communications in Smart Home Environments

text: Smart phone

text: Smartpsmoke detector

text: Processing Cloudpstorage Smartpappliances Smart home Device gateway management

text: Smart lightpbulbs

text: HAN:SSHORT-RANGESANDSDIRECTSCOMMUNICATION WAN:SLONG-RANGESCOMMUNICATION

text: PAN: HighSspeedSnetworks: LP-WAN: HighSspeedSnetworks:

text: 6LowPANZpBluetoothZ EthernetZpFiberpopticsZ NWaveZpLoRaWANZ 4GMLTEZpADSLZpFTTHWWW EnOceanZpNFCZpRFIDZ PowerlinepCommunicationZ LTE-MTCZpSigfoxZ ZigbeeZpZ-WaveWWW Wi-FiWWW UltrapNarrowpBandWWW

text: Table 2: Mapping threats with good practices

text: THREAT GOOD PRACTICES RATIONALE

text: Not addressed in this study except for select privacy issues.

text: See good practices for the Development phase on User data protection.

text: Identity fraud must be addressed not only  Identification, authentication, authorisation by credential protection, but also by the  User data protection protection of private data that might Identity fraud contribute to impersonation.

text: Usage until End-of-Life

text: Consequently this is also covered by  Operational security and maintenance privacy measures. (Section 7.2)

text: Unsolicited & infected e-  Self-protection This topic can typically be addressed by mail  Communication protection awareness campaigns from the vendors and service providers. Hoax

text: THREAT GOOD PRACTICES RATIONALE

text: Unsolicited & infected e-  Good practices for the integration of devices This topic can typically be addressed by mail in the Home Area Network (Section 6) awareness campaigns from the vendors and service providers. Hoax Usage until End-of-Life  Operational security and maintenance (Section 7.2)

text:  Communication protection Failsafe mechanisms, multiplicity of Integration interfaces and user notification should  Good practices for the integration of devices ensure a minimum level of robustness Denial of service in the Home Area Network (Section 6) against denial of service. The protection of communications also addresses these Usage until End-of-Life concerns.  Operational security and maintenance (Section 7.2)

text:  Self-protection Self-protection must cover the vulnerabilities related to malicious code.

text: Malicious code/software Another way to mitigate these threats  Good practices for the integration of devices activity consists in additional Home Area Network in the Home Area Network (Section 6) protection and management of trust Usage until End-of-Life relationships to isolate compromised devices.  Operational security and maintenance (Section 7.2)

text: Development Security administration functions must also be available (Security management).  Security of the development process (Section Eventually, the design should lead to 5.1) understandable and usable user  User data protection Abuse of information interfaces. leakage

text: Usage until End-of-Life

text: Privacy and confidentiality requirements  Good practices for the usage until end-of-life also require transparency, so that the user (Section 7) is aware of the type of data that are potentially at risk.

text: Generation and use of  Identification, authentication, authorisation The trust infrastructure must cover the rogue certificates risks of public key vulnerabilities.

text: THREAT GOOD PRACTICES RATIONALE

text: Generation and use of Integration The trust infrastructure must cover the

text: rogue certificates  Good practices for the integration of devices risks of public key vulnerabilities.

text: in the Home Area Network (Section 6)

text: Development Development security must ensure that unauthorized manipulations are not  Security of the development process Manipulation of hardware possible during production. (Section 5.1) & software  Self-protection After delivery to the end-user, the device

text: must be self-protected.

text:  Communication protection  Security audit Trust and reputation relationships,

text: associated to communication protection,

text: must cover the risks of external Manipulation of  Good practices for the integration of devices information manipulations information in the Home Area Network (Section 6) Manipulation of the audit trail must not Usage until End-of-Life be possible

text:  Operational security and maintenance

text: (Section 7.2)

text: Development Audit tools must be protected from unauthorized access. Furthermore, privacy  Security audit requirements contribute to reduce the Misuse of audit tools  User data protection amount of potentially exploitable data  Self-protection Falsification of records Self-protection contributes to mitigate the risks of manipulation by malicious code on the device.

text: Unauthorised access to Development information  Identification, authentication, authorisation Identification, authentication and system/network authorization are a general requirement Unauthorised use of Usage until End-of-Life for the access to sensitive functions. This administration of devices &  Operational security and maintenance is particularly the case for administrative systems (Section 7.2) capacities.

text: Abuse of authorizations

text: Development Self-protection contributes to mitigate the Unauthorised use of  Self-protection risks of manipulation by malicious code on software the device.

text: THREAT GOOD PRACTICES RATIONALE

text: Unauthorised installation of Usage until End-of-Life Security management also state that software firmware installation should be protected  Operational security and maintenance to ensure its authenticity and integrity Badware (Section 7.2)

text: Compromising confidential Development Private information must be protected information from unauthorized access. Furthermore,  User data protection privacy requirements contribute to reduce Abuse of personal data the amount of potentially exploitable data

text:  Communication protection  Identification, authentication, authorisation  Self-protection The remote capacities of a device must be Integration available only to authorized users – and Remote activity (execution)  they should be performed by secure Good practices for the integration of devices channels. in the Home Area Network (Section 6)

text: Usage until End-of-Life

text:  Operational security and maintenance (Section 7.2)

text: Targeted attacks (including These attacks are not considered here due to the very high potential of the attacker, with APT) regards to the assets. This topic should be addressed by national cybersecurity agencies.

text: Devices and services must implement  Communication protection secure communications.

text: Integration However there are some devices that lack capacities for this, and in the case of war  Good practices for the integration of devices War driving driving, the attacker aims at the Home in the Home Area Network (Section 6) Area Network. For this reason, the Usage until End-of-Life additional network protection on the HAN is particularly critical with regard to this  Operational security and maintenance threat. (Section 7.2)

text: Such side-channel attacks are not considered in this study, since they require a relatively high attack potential. Interception compromising emissions As far as Smart Home is concerned, the stocktaking and the interviews showed that communication protection is still more an exception than a rule, meaning that attackers are more likely to exploit non-protected communications than performing side channel attacks.

text: THREAT GOOD PRACTICES RATIONALE

text: Interception of information, Development Network reconnaissance  Communication protection and information gathering, - Replay of messages, Man in Usage until End-of-Life the middle/ session  Operational security and maintenance hijacking (Section 7.2)

text: Integration Failsafe mechanisms, multiplicity of interfaces and user notification should Interfering radiations  Good practices for the integration of devices ensure that interference or jamming do in the Home Area Network (Section 6) not hamper security

text: The notion of repudiation comes with the notion of legal or contractual binding. The main use cases foreseen are:  Billing (e.g. for protected content in Audio/Visual systems and devices) and  Insurance (e.g. using smart locks or surveillance data). Repudiation of actions The stocktaking did not show evidences of the latter, while the former belongs in a domain where vendors already have incentives to implement these kinds of security functions. In both cases, the threat would be addressed by digital signature functions in a secure element172, or by Trusted Platform Modules173. For these reasons, the study does not further address these threats.

text: Development Self-protection includes both physical and logical protections against physical  User data protection Simple physical attacks attacks. User data protection also  Self-protection mandates that user data is not easily accessible in cleartext on the device.

text: Advanced physical attacks These attacks are not considered here due to the very high potential of the attacker.

text: See for example the SSCD Protection Profiles recommended by SOG-IS (http://www.sogisportal.eu/uk/pp_en.html) See http://www.trustedcomputinggroup.org/developers/trusted_platform_module

text: THREAT GOOD PRACTICES RATIONALE

text: Lack of  Good practices for the integration of devices Failsafe mechanisms, multiplicity of resources/electricity, in the Home Area Network (Section 6) interfaces and user notification should Internet outage, Network ensure that power or network outage do outage, Strike, Loss of Usage until End-of-Life not hamper security support services  Operational security and maintenance (Section 7.2)

text: Absence of personnel Development The design should lead to understandable

text: and usable user interfaces – user guidance  Security of the development process also contributes to helping the user (Section 5.1) making sensible configuration choices

text: Development Security administration functions must also be available (Security management).  Security of the development process Information leakage or Eventually, the design should lead to (Section 5.1) sharing understandable and usable user  User data protection interfaces. Erroneous use or

text: Usage until End-of-Life

text: administration of devices Privacy and confidentiality requirements and systems  Operational security and maintenance also require transparency, so that the user

text: (Section 7.2) is aware of the type of data that are

text: potentially at risk.

text: Using information from an The devices and services must know the  Good practices for the integration of devices unreliable source level of trust of the information they use. in the Home Area Network (Section 6)

text: Unintentional change of Integration Components of the Smart Home must

text: data in an information  Good practices for the integration of devices handle data changes without failure, system in the Home Area Network (Section 6) errors and improper functioning

text: Inadequate design and  Security of the development process planning or lack of adaption (Section 5.1)

text: THREAT GOOD PRACTICES RATIONALE

text: Damage caused by a third See physical attacks party

text: Integration Components of the Smart Home must handle data changes without failure,  Good practices for the integration of devices errors and improper functioning. In Loss from DRM conflicts in the Home Area Network (Section 6) particular, they should not cause information loss outside of their own perimeter.

text: Loss of information in the cloud See “Information leakage” as well as “Eavesdropping / Interception / Hijacking” Loss of (integrity of) sensitive information

text: Loss or destruction of See “physical attacks”, as data leakage from a lost devices, storage media and or stolen device is a physical attack documents

text:  User data protection User data protection includes measures to ensure that these data is not accidentally Information leakage Usage until End-of-Life leaked. User guidance contributes to

text:  educate the end-user with that regard Operational security and maintenance (Section 7.2)

text: Failures / Malfunctions of Integration parts of devices, Failures / Reliability of devices and services is  Good practices for the integration of devices Malfunctions of devices or addressed as a basis requirement upon in the Home Area Network (Section 6) systems, Failures of which the security can be built hardware, Software bugs

text: Failures or disruptions of communication links  Good practices for the integration of devices Failsafe mechanisms, multiplicity of (communication networks), in the Home Area Network (Section 6) interfaces and user notification should Failures or disruptions of ensure that power or network outage main supply, Failures or Usage until End-of-Life does not hamper security disruptions of the power  Operational security and maintenance supply (Section 7.2)

text: THREAT GOOD PRACTICES RATIONALE

text: Failures of disruptions of This topic is not developed further in the study, service providers (supply since security organisational good practices chain) address only marginally these issues.

text:  Security of the development process The design should lead to understandable (Section 5.1) and usable user interfaces – user guidance Configuration errors also contributes to helping the user

text: Usage until End-of-Life

text: making sensible configuration choices  Operational security and maintenance (Section 7.2)

text: Class 0 devices and higher Class 1 devices and higher Class 2 devices and higher

text: High capacity devices Remote services

text: Table 3: Checklist of good practices

text: Security of the development process

text: Design phase

text: Use defence in depth

text: Separate security functions from other functions

text: Make assumptions for the security requirements explicit

text: Consider third-party review by security specialists for developers with limited security experience 1+

text: Prepare user interactions with the products or services

text: Development phase

text: Use configuration management tools, and leverage upon development environments such as compilers or static analysers 1+

text: Take security into account when choosing your programming language; when available, leverage upon the operating system security functions 1+

text: Use standard, secure frameworks or stacks whenever possible – do not redevelop security functions 1+

text: Ensure team training and awareness

text: Testing phase

text: Test the compliance of security functions

text: Perform additional security audits and penetration testing

text: Perform a privacy assessment

text: Security functions for hardware and software

text: Security audit

text: Log security events

text: Notifications should be easy to understand and help users find a remediation or workaround

text: Communication protection

text: Protect all communication against disclosure, modification and replay

text: Mitigate vulnerabilities or limitations of standard security library

text: Protect communications against denial of service

text: Do not create proprietary cryptographic schemes, but use state-of-the-art standards instead. Even a home-brewed implementation of a standard is not a good practice when standard

text: implementations are available.

text: Rely on an expert in cryptography for interfacing with HW accelerated cryptography or secure elements, or even using or configuring a standard implementation. 1+

text: When designing or procuring HW, pay attention to the requirements of cryptography in terms of CPU, memory and bandwidth and their impacts on battery. 1+

text: Be aware of limitations of HW-based cryptography solutions and choose wisely whether a SW or HW solution is needed for the given context. 1+

text: Manage keys securely

text: Use trust and reputation infrastructures

text: User data protection

text: Identify personal data

text: Implement transparency measures

text: Design the product/service with legitimate purpose and proportionality in mind

text: Identification, authentication, authorisation

text: Use mutual authentication for remote communication

text: Use multi-factor authentication for user authentication

text: Implement access control measures to separate the privileges of different users as well as the privileges of different applications 2+

text: Implement a strong password management policy

text: Enforce session management policies to avoid session hijacking

text: Implement tamper evidence / tamper resistance for hardware self-protection

text: Implement hardware self-protections at the design level

text: Protect the software security functions with self-protection measures by reinforcing interfaces and strengthening the application separation at runtime 1+

text: Provide a secure default configuration

text: Provide protection measures for security-enforcing data

text: Perform hardening on both HW and SW

text: Minimum reliability

text: Hardware must provide basic reliability measures to resist outages and jamming

text: Software components of the Smart Home must handle data changes without failure, errors and improper functioning 0+

text: Trust relationships

text: Use a trust infrastructure within and outside the HAN

text: Use secure pairing for devices

text: Check the security assumptions at installation time

text: Network security

text: Introduce a gateway to mitigate the propagation of attacks from or to the HAN

text: Network segregation as additional security measure

text: Protection of data exchanges

text: Ensure access rights

text: Leverage on gateways to reduce the network exposure of the weaker devices

text: Segregate the Smart Home Networks and the AMI

text: Operational security and maintenance

text: Vulnerability survey

text: Perform vulnerability survey

text: Check the security assumptions regularly during life-time

text: Security updates

text: Protect the software update mechanism

text: Remote interfaces protection

text: Provide user-friendly interfaces for device and services security management

text: Protect remote monitoring interfaces

text: Security management system for support infrastructures

text: Rely on existing sources for security good practices in order to secure infrastructures

text: Control of user data

text: Provide secure backup and/or deletion of the data stored/processed by the device (and by associated cloud services) during the operation and at end-of-life 1+

text: HOW TO CHOOSE A SMART HOME DEVICE SECURELY

text: Verify if the smart features are really required or if a normal device would be sufficient Be careful when buying used IoT devices, as they could have been tampered with Research the vendor’s device security measures If battery powered, favour devices providing alternate/emergency charging methods

text: HOW TO OPERATE A SMART HOME DEVICE SECURELY

text: Change default password of Wi-Fi networks and use robust encryption (e.g. WPA2) Change default password of device Disable or protect remote access to IoT devices when not needed Use wired connections instead of wireless where possible Modify the privacy and security settings of the device to your needs Disable features that are not being used Install updates when they become available Use devices on separate home network when possible Ensure that an outage (for example due to jamming or a network failure) does not result in a unsecure state of the installation

text: HOW TO USE ONLINE SERVICES FOR SMART HOME SECURELY

text: Use a password manager Use different passwords for different services Control data exchange requested by a service

text: ACRONYM DEFINITION

text: AFR Annual Failure Rate AMI Advanced Metering Infrastructure API Application Programming Interface APT Advanced Persistent Threat ASLR Address Space Layout Randomization BSI Bundesamt für Sicherheit in der Informationstechnik CC Common Criteria CERT Computer Emergency Response Team CPA Commercial Product Assurance CSPN Certification Sécuritaire de Premier Niveau CO2 Carbon dioxide CPU Central Processing Unit CSA Cloud Security Alliance CSRF Cross-Site Request Forgery DMA Direct Memory Access DTLS Datagram Transport Layer Security DoS Denial of Service EC European Commission EU European Union FTC Federal Trade Commission FTP File Transfer Protocol HAN Home Area Network HDL Hardware Description Language

text: HTTP HyperText Transfer Protocol HTTPS HyperText Transfer Protocol Secure HW Hardware I2C Inter-Integrated Circuit IBC Identity-Based Cryptography IBE Identity-Based Encryption IDS Intrusion Detection System IoT Internet of Thing IPC Inter-Process Communication IPS Intrusion Prevention System ISMS Information Security Management System ISP Internet Service Provider ISP In-System Programming JHAS JIL Hardware-related Attacks Subgroup JTAG Joint Test Action Group JTEMS JIL Terminal Evaluation Methodology Subgroup LED Light-Emitting Diode LPWAN Low-Power Wide-Area Network MNO Mobile Network Operator MS Member States MTBF Mean Time Between Failures MVNO Mobile Virtual Network Operator NAS Network Attached Storage OCSP Online Certificate Status Protocol OMA Open Mobile Alliance OS Operating System

text: OTA Over The Air PCB Printed Circuit Board PCI Payment Card Industry PKI Public Key Infrastructure PIN Personal Identification Number R&D Research and Development RFID Radio-Frequency IDentification SaaS Software as a Service SMS Short Message Service SoC System on Chip SPI Serial Peripheral Interface SSL Secure Sockets Layer SSH Secure SHell SW Software TCP Transmission Control Protocol TLS Transport Layer Security TPM Trusted Platform Module TV TeleVision UDP User Datagram Protocol UICC Universal Integrated Circuit Card URL Uniform Resource Locator VLAN Virtual Local Area Network WAN Wide Area Network WEP Wired Equivalent Privacy WPS Wi-Fi Protected Setup XSS Cross-Site Scripting

identifier: Security and Resilience of Smart Home Environments

nummer: security-resilience-good-practices

title: Security and Resilience of Smart Home Environments

text: Security and Resilience of Smart Home Environments Good practices and recommendations

text: DECEMBER 2015 www.enisa.europa.eu European Union Agency For Network And Information Security About ENISA

text: The European Union Agency for Network and Information Security (ENISA) is a centre of network and information security expertise for the EU, its member states, the private sector and Europe’s citizens. ENISA works with these groups to develop advice and recommendations on good practice in information security. It assists EU member states in implementing relevant EU legislation and works to improve the resilience of Europe’s critical information infrastructure and networks. ENISA seeks to enhance existing expertise in EU member states by supporting the development of cross-border communities committed to improving network and information security throughout the EU. More information about ENISA and its work can be found at www.enisa.europa.eu.

text: Authors

text: Dr. Cédric LÉVY-BENCHETON (ENISA), Ms. Eleni DARRA (ENISA), Mr. Guillaume TÉTU (Trusted labs), Dr. Guillaume DUFAY (Trusted Labs), Dr. Mouhannad ALATTAR (Trusted Labs)

text: Contact

text: For contacting the authors please use resilience@enisa.europa.eu For media enquires about this paper, please use press@enisa.europa.eu.

text: Acknowledgements

text: Dr. Serge AUTEXIER (German Research Centre for Artificial Intelligence – DFKI) Eng. Thierry BOUSQUET (ST MICROELECTRONICS) Dr. Andrei COSTIN (Firmware.RE) Mr. Thomas GAYET (CERT-UBIK) Mr. Filip GLUSZAK (GridPocket) Ms. Svetlana GRANT (GSM-A) Mr. Abraham JOSEPH (IOT Insights) Dr. Thibaut KLEINER (European Commission) Dr. Gert LÆSSØE MIKKELSEN (Alexandra Institute) Mr. Brian KNOPF (BRK Security / I am the Cavalry) Mr. Kai KREUZER (openHAB) Mr. Antoine LARPIN (Panasonic) Mr. Jan-Bernhard de MEER (smartspace laboratories GmbH) Mr. Cédric MESSEGUER (Digital Security) Mr. Chris de MOL (Fifthplay) Mr. Christian MÜLLER (University of Mannheim) Mr. Detlef OLSCHEWSKI (Cleopa GmbH) Ms. Barbara PAREGLIO (GSM-A) Mr. Antonio PELLICCIA (IBM) Mr. Gaus RAJNOVIC (Panasonic) Mr. Hartmut RICHTHAMMER (University of Regensburg) Mr. Mathieu SACRISPEYRE (INTESENS) Mr. Benjamin SCHWARZ (CTOi Consulting) Mr. Ian SMITH (GSM-A) Mr. Craig SPIEZLE (Online Trust Alliance) Dr. Pavel TUČEK (Cleopa GmbH)

text: Dr. Steffen WENDZEL (Fraunhofer FKIE) Mr. Peter WOOD (First Base Technologies) Mr. Andrej ZIEGER (DFN CERT Service GmbH)

text: Legal notice

text: Notice must be taken that this publication represents the views and interpretations of the authors and editors, unless stated otherwise. This publication should not be construed to be a legal action of ENISA or the ENISA bodies unless adopted pursuant to the

text: Regulation (EU) No 526/2013

text: . This publication does not necessarily represent state-of the-art and ENISA may update it from time to time.

text: Third-party sources are quoted as appropriate. ENISA is not responsible for the content of the external sources including external websites referenced in this publication.

text: This publication is intended for information purposes only. It must be accessible free of charge. Neither ENISA nor any person acting on its behalf is responsible for the use that might be made of the information contained in this publication.

text: Copyright Notice

text: © European Union Agency for Network and Information Security (ENISA), 2015 Reproduction is authorised provided the source is acknowledged.

text: ISBN: 978-92-9204-141-0 | doi:10.2824/360120

text: Table of Contents

text: Executive Summary 6

text: 1. Introduction 8

text: 1.1 EU Policy 8

text: 1.2 Scope of the study 9

text: 1.3 Target audience 10

text: 1.4 Methodology 10

text: 1.5 Outline 10

text: 2. The Smart Home Environments 12

text: 2.1 Overview 12

text: 2.1.1 Connectivity 12 2.1.2 Classes of IoT devices 13

text: 2.2 Threats to Smart Home Environments 15

text: 3. Key Findings 16

text: 3.1 The need for security in Smart Home Environments is still underestimated 16

text: 3.2 Vendors lack incentives to enhance security in Smart Home devices and services 17

text: 3.3 Smart Home devices and services implement few security measures 17

text: 3.4 Smart Home Environments result in new security challenges 18

text: 3.5 IoT vulnerable “building blocks” cause vulnerabilities to be shared at large scale 19

text: 3.6 IoT pervasiveness and dynamicity 19

text: 3.7 IoT brings new constraints on security 20

text: 4. Good practices for a Secure Smart Home Environment 21

text: 5. Good practices for the development of Smart Home devices and services 22

text: 5.1 Security of the development process 22

text: 5.1.1 Design phase 22 5.1.2 Development phase 23 5.1.3 Testing phase 25

text: 5.2 Security functions for hardware and software 27

text: 5.2.1 Security audit 27 5.2.2 Communication protection 28 5.2.3 Cryptography 30 5.2.4 User data protection 33 5.2.5 Identification, authentication, authorisation 35 5.2.6 Self-protection 38

text: 6. Good practices for the integration of devices in the Home Area Network 43

text: 6.1 Minimum reliability 43

text: 6.2 Trust relationships 44

text: 6.3 Network security 46

text: 7. Good practices for the usage until end-of-life 48

text: 7.1 Protection of data exchanges 48

text: 7.2 Operational security and maintenance 49

text: 7.2.1 Vulnerability survey 49 7.2.2 Security updates 50 7.2.3 Remote interfaces protection 51 7.2.4 Security management system for support infrastructures 51

text: 7.3 Control of user data 52

text: 8. Recommendations 53

text: 8.1 All stakeholders should reach a consensus on minimum security requirements 53

text: 8.2 Industry actors should support security-driven business models 53

text: 8.3 All actors should contribute to raise security awareness 54

text: 8.4 Industry actors should develop security assessment methods or frameworks 54

text: 8.5 Policy Makers should clarify the legal aspects of Smart Home Environments 55

text: 8.6 Industry research and publicly-funded initiatives should integrate cyber security in R&D projects related to Smart Home and IoT 56

text: Annexes Annex A: Additional details on Smart Home Environments 57 Annex B: Mapping threats with good practices 60 Annex C: Checklist of good practices 68 Annex D: Example of topics for user awareness 73 Annex E: List of Acronyms 74

text: Executive Summary

text: The Internet of Things (IoT) is an emerging concept where interconnected devices and services collect, exchange and process data in order to adapt dynamically to a context. In the context of “Smart Home Environments” both IoT and traditional devices and services integrate in a home to enhance the quality of life of citizens. This allows improvements in several domains such as energy efficiency, health monitoring…

text: New Smart Home devices and services appear at a fast pace, from various manufacturers which may have a limited experience of cyber security. Yet, it is often necessary to integrate these devices in the “Home Area Network” in order to provide connectivity for data exchange and to perform their operations.

text: Due to these interdependencies, numerous cyber threats appear with possible consequences on the life, health and safety of the inhabitants. Hence, it becomes important for manufacturers, solution vendors, developers, and end-users to understand how to secure devices and services.

text: In Smart Home environments, the security can be difficult to implement within a heterogeneous ecosystem which integrates several types of devices and services, which usually have limited security due to their weak capacities (CPU, battery…). Moreover the service they provide usually relies on remote infrastructures for cloud storage, analytics or even remote access to the devices.

text: It becomes necessary to follow a holistic approach of security as the multiple dependencies open new ways of remote attacks, as presented in presented in “ENISA Threat Landscape and Good Practice Guide

text: for Smart Home and Converged Media.”

text: The key findings of this study confirm the difficulty to ensure the security of Smart Home Environments:

text:  The need for security in Smart Home Environments is still underestimated and vendors lack incentives toward this goal.  It is difficult to understand which security measures can protect Smart Home devices and services, as they present new security challenges due to their interconnected and pervasive nature.  Many IoT applications, Smart Home devices and services rely on other “building blocks”, which may cause unknown vulnerabilities to appear.

text: This study aims at securing Smart Home Environments from cyber threats by highlighting good practices that apply to every step of a product lifecycle: its development, its integration in Smart Home Environments, and its usage and maintenance until end-of-life. The study also highlights the applicability of the security measures to different types of devices.

text: The good practices apply to manufacturers, vendors, solution providers for hardware and software, and developers. It can be used to assess their current security level, and evaluate the implementation of new security measures. European citizens, standardisation bodies, researchers and policy makers could also find an interest in this study.

text: The application of good practices aims at covering existing threats. However, Smart Home Environments remains only one specific application of the Internet of Things. Thus, it requires a continuous effort to ensure the security of new devices and services and the safety of its inhabitants.

text: ENISA proposes the following six recommendations with the objective of enhancing the current status of cyber security in Smart Home Environments and in a more general IoT context:

text: 1. All stakeholders should reach a consensus on minimum security requirements: the development of minimum security requirements should help non-experts in implementing specific security functions in their devices and services 2. Industry actors should support security-driven business models: as Smart Home manufacturers tend to focus on functionalities, security can become a differentiation factor and provide addedvalue to customers. 3. All actors should contribute to raise security awareness: to help manufacturers with less experience on security and customers, awareness is needed to understand which actions are needed to secure a Smart Home. 4. Industry actors should develop security assessment methods or frameworks: as IoT for Smart Home Environments brings a new paradigm. Specific methods or framework shall ease security assessment and accompany deployment of security measures. 5. Policy Makers should clarify the legal aspects of Smart Home Environments: since there is currently a limited scope in the liability when a device is compromised. With health and safety concerns, policy should help understand the responsibilities and have a preventive role.

text: 6. Industry actors and publicly-funded initiatives should integrate cyber security in R&D projects

text: related to Smart Home and IoT: there are numerous Research and Development projects in the domain of Smart Home Environments and IoT, which could gain impact by integrating specific security aspects.

text: Introduction

text: Smart Home Environments integrate multiple IoT devices and services that collect, process and exchange data. They provide users several possibilities to control and adapt the status of their home, either manually or automatically. For that purpose, Smart Home devices and services exchange data with internal and external actors. These interactions take place with mobile applications on an end-user’s equipment (smartphone, tablet…) and also with remote services in the Cloud.

text: Due to their interconnected nature, Smart Home devices are subject to a number of security threats either from remote attackers or from inside the Home Area Network (HAN). Moreover, these threat have an impact not only on a user’s data but also on his/her health and safety: this changes the accepted idea that the home is usually a safe place to live in.

text: Smart Home Environments being an emerging domain and because the liabilities are not well defined, it becomes important for all actors to develop adapted security measures to prevent cyber threats. For that purpose, there is a need to secure Smart Home Environments and effectively reduce the threats.

text: 1.1 EU Policy

text: At the time of this writing no dedicated EU Policy has been identified to target Smart Home Environments specifically.

text: However, the following general policies on IoT can be extended to this area:

text:  The Digital Single Market identifies internet and digital technologies as one of the 10 priorities of the European Commission to foster EU economy with IoT being a key enabler.  The Opinion 8/2014 on the Recent Developments on the Internet of Things identifies home automation as one of the three main IoT topics to be addressed in the coming years.  The EU Data Protection Directive

text: with the additional elements from Opinion 03/2014 on Personal Data Breach Notification covers security of personal data. 6 7  EU Research initiatives such as FIware and the AIOTI alliance bring building blocks toward an integrated IoT environment.

text: Note that no dedicated EU policy covers IoT security either. Indeed, for the European Commission “There is no consensus on the need for and the scope of public intervention in the field of IoT.” Should there be any future development on the EU regulation, it is important to consider the status of cyber security.

text: 1.2 Scope of the study

text: This study evaluates good practices to secure the lifecycle of Internet of Things (IoT) products and services in the context of Smart Home Environments.

text: As illustrated in Figure 1, this study focuses on:

text:  The two types of IoT Devices that can be found in a Smart Home Environment: o Constrained devices as defined by RFC 7228. The security in these devices may be limited due to their comparatively low capacities (CPU, memory, battery…). o High-capacity devices typically powered by the mains supply. These devices may be able to implement strong to very strong security features as they possess hardware configurations (CPU, memory) that grants them significant computing power.  The interactions and data exchange with remote services including remote activation, remote storage or content, device administration and analytics.  The interactions and data exchange with mobile applications for control/command purposes and data exchange among devices.

text: 1.3 Target audience

text: This study aims at providing simple and pragmatic guidance for securing Smart Home Environments. The main stakeholders that this study targets to include:  Smart Home manufacturers and third-party developers (including HW and SW components vendors, API developers…) as they are the main actors in IoT devices and services for Smart Home Environments.  Service and solution providers (Cloud service providers, Third-party services associated with Smart Home devices…) as they communicate and exchange data with Smart Home Environments.  Electronic communications providers (ISPs, MNOs, MVNOs) due to their implication in bringing connectivity to Smart Home devices and services. The findings could also potentially interest:  Cybersecurity agencies and/or Standardisation bodies for security awareness, device security certification and also security standardisation initiatives.  Consumer associations for end-users security awareness and benchmarking purposes.  Policy makers and academics to assess to which extent security can be integrated in their work (new policies, researches, funding…).  Hobbyists, enthusiasts and open source contributors that develop their own Smart Home by writing software or integrating open source software, and use frameworks such as Raspberry or Arduino platforms. These stakeholders can selectively apply good practices related to the development and usage of Smart Home devices and services, for example in association to a risk assessment. For example, electronic communication providers can implement good practices from the point of view of the local network protection offered by their set-top boxes.

text: 1.4 Methodology

text: This study is based on a collection of publically available information relevant to Smart Homes which were analysed and correlated to:  Update the threats applicable to Smart Home Environments.  Perform an inventory of the good practices identified by the security community in a Smart Home context, or in the IoT context when relevant. The results were then crosschecked with stakeholders through an online questionnaire and selected interviews with device manufacturers, security experts, standard groups and network operators. This step addressed open questions on emergent and unexpected topics. The results have been validated by experts in IoT and Smart Home Environments through document review and in a validation workshop.

text: 1.5 Outline

text: This study is organised as follows:  Section 2 “The Smart Home Environments” defines the type of devices, services and technologies encompassed in this study by the term “Smart Home” and also summarizes threats applicable to these environments.

text:  Section 3 “Key Findings” presents the outcome of stocktaking and interviews with stakeholders from the Smart Home ecosystem with regards to current implementation of security in Smart Home products and Smart Home particularities.  Section 4 “Good practices for a Secure Smart Home Environment” introduces the core of this study. It defines the comprehensive set of security “good practices” applicable to the Smart Home context for mitigating existing threats. These good practices are organized according to the lifecycle of Smart Home devices and services in the following sections.  Section 5 “Good practices for the development of Smart Home devices and services” highlights the good practices to secure the development of Smart Home devices and services.  Section 6 “Good practices for the integration of devices in the Home Area Network” presents the good practices to integrate devices securely in a Smart Home Environments  Section 7 “Good practices for the usage until end-of-life” focuses on the good practices to ensure security for the operation and maintenance of products deployed in Smart Home Environments.  Section 8 “Recommendations” builds upon the gap analysis in order to propose recommendations aimed at improving the level of security in future Smart Home Environments. These recommendations are intended for vendors and service providers, national cybersecurity agencies, consumer groups, standard groups and/or industry associations.

text: The Smart Home Environments

text: 2.1 Overview

text: The definition of Smart Home Environments is taken from the one found in “ENISA Smart Home threat

text: landscape.” This definition refers to devices and systems present in the Smart Home, the associated services and the networks used to interconnect these devices and services, located inside or outside the home.

text: This study is a follow-up of the ENISA Smart Home threat landscape, which presented the various threats applicable to Smart Home. Findings showed that threats target a wide range of applications in the Smart Home and can have consequences on the end-user. For that purpose, it is important to define appropriate security measures that rely on the specificities of the Smart Home.

text: 2.1.1 Connectivity

text: The common point between Smart Home devices resides in the combination of “smartness” (data processing and connectivity) and the “local” nature of the use case (devices are in the user home). This means in practice that connectivity:

text:  is always present in the devices, either limited to the Home Area Network or with access to the Internet;  may be related to several kinds of communication protocols (direct, short-range or long-range, wired or wireless); and  may lead to several interconnected networks in the home and outside the home.

text: Such networks are described further in Figure 2. They typically include:

text:  One or several Home Area Networks (HAN), which are dedicated to local networks or subnetworks for Smart Home devices and sensors: o One or several High Speed Networks, usually Wi-Fi networks, that may be provided by a set-top-box, mobile devices… o Personal Area Networks or ad-hoc networks created between several devices, for instance using low-speed connections (e.g. Bluetooth, Zigbee…).  Connections to Wide Area Networks (WAN): o High Speed Networks, typically providing access to the Internet, for instance through the Internet Service Provider (ISP) network or the Mobile Network Operator (MNO) network. o One or several Low Power Wide Area Networks (LPWAN), which provide WAN connectivity while requiring low power from the device (e.g. LoRaWAN, Sigfox…).  If the home uses a smart meter, this meter connects the home to the associated Advanced Metering Infrastructure (AMI) used to communicate with smart energy management devices.

text: It should be noted that real-life deployments of Smart Home might include only some of these networks, or might use them differently: for example, home automation devices may directly use the home Wi-Fi to access remote services, without using a dedicated gateway.

text: Note that many elements of the Smart Home have connections to other domains: energy might have connections to the smart metering domain, devices related to assisted-living might have connections to the eHealth domain, many other devices in the Smart Home might have connections to the connected mobility or wearables domain.

text: These connections might bring additional security constraints to these devices, notably in terms of compliance to national health or energy (critical infrastructure) requirements. This is out of the scope of this study.

text: 2.1.2 Classes of IoT devices

text: The types of devices taken into account for this study are constrained (defined as per RFC 7228) and highcapacity ones. Constrained devices are divided into three classes depending on their RAM capacity, memory storage capacity and CPU power. Indeed, the class of a constrained device has an impact on its security capabilities, and thus it introduces limits to the application of some good practices.

text: Table 1 summarizes the classes of IoT devices based on their hardware properties. It describes the impacts on their security capabilities.

text: More details on technologies used in Smart Home can be found in Annex A: “Additional details on Smart Home Environments.”

text: 2.2 Threats to Smart Home Environments

text: The threats to Smart Home Environments are real and apply to all devices and services as confirmed during 12 13 14 15 16 the stocktaking phase of this study. While the presentation and categories of threats differ from analysis to analysis, outcome of this comparison showed that the content remains the same, that nearly all threats found in these sources are retained. Thus, the following threats groups are still relevant:

text:  Physical attacks arise from a well-identified attack vector (physical manipulation of devices). They might lead to various types of risks, including the categories described hereafter as Nefarious Activity/Abuse or Eavesdropping/Interception/Hijacking. A physical attack typically threatens all assets.  Unintentional damage (accidental) may result from incorrect trust relationships or they may occur to insufficiently trained personnel (for administration, design, operation…). As it may impact administration capacities, the potential consequences also cover the whole spectrum of data leak, unauthorized modification or loss.  Disasters and Outages were considered only as far as they result in a preventable denial of service for the user.  Damage/ Loss (IT Assets) leads not only to disruption of service, but also possible leaks, as shown by ENISA’s threat analysis. This study only addresses this from the point of view of the secure deletion of sensitive information at the end-of-life of a product, since all other aspects of this topic are not directly related to IT security.  Failures/ Malfunctions are by definition one of the best entry points for an attacker and constitutes a first step of many scenarios of Nefarious Activity/Abuse or Eavesdropping/Interception/Hijacking.  Eavesdropping/Interception/Hijacking as well as Nefarious Activity/Abuse are related to both privacy and cybersecurity threats. These two categories are what is generally regarded as a security threat. By leveraging design or implementation flaws, an attacker will compromise one or several assets, whether it means a loss of confidentiality on private data or a loss of control over a device. Most security good practices aim at mitigating these cases.  Legal, as described in the ENISA documentation, this is another possible consequence of the same attacks. While a threat analysis is likely to contribute to distinguishing this case from the others, the attack vectors remain unchanged and they will not be distinguished from the point of view of good practices. While this study does not challenge these threats, there are however a few findings regarding the attack model and the risks associated with these threats. For more details, see Section 3.

text: Key Findings

text: In this section we present the key findings discovered during the stocktaking and the analysis of the results of the on-line survey and interviews. These key findings also provide information on the challenges related to the current level of security of Smart Home products in relation with the good practices described above.

text: 3.1 The need for security in Smart Home Environments is still underestimated

text: Smart Home raises new security concerns that are not easily shown in a traditional threat assessment.

text: Current privacy regulations ensure that service providers will not intentionally collect private data. Smart Home actors comply with this regulation by privacy measures on the server-side of their services, which would arguably be enough in a world where no malicious actors were present. However, the absence of protection on the device-side means that private data collection might be relatively easy to perform on targeted individuals, even by attackers with low skills.

text: Industry players usually give two reasons not to implement more security measures:

text:  Few attackers have an incentive to perform such attacks on an individual.  This hypothetical targeted individual will, anyway, not chose a secure device over a lower-cost insecure device.

text: The first argument cannot be retained due to the lack of security in the context of today’s Smart Home: when attacks are almost trivial to perform, attackers do not need many incentives.

text: The second argument assumes that an individual is able to give a financial cost to his private data. This line of thought is consistent with most risk assessment methods, which assess the relative importance of the threatened assets as a first step. When an asset is described as having a low value, it is expected that an attacker is less likely to compromise it, and that the asset owner is less likely to spend efforts on protecting it. The problem of this assumption is that in this case, the asset owner is not able to measure this value, since:

text:  they are not necessarily aware of which private data could be leaked; and  they are not necessarily aware of how easy it is to obtain these data.

text: As an additional issue in the Smart Home context, trying to assess the value of private data is very difficult, since this value might vary widely depending on the local culture, amongst many other factors. This is apparent for example in the Mozaiq initiative which aims at ensuring that Smart Home data is stored and processed within Germany borders.

text: Moreover, attacks on Smart Home can target the weakest element to capture credentials of the HAN and elaborate more powerful attacks. For example, researchers have recovered the Wi-Fi private key from an unsecured device and could connect to the network to take control of the Smart Home.

text: In any case, it is a common sense to say that home is the definition of a private space. If someone has a need for privacy, he will probably try to find it at home. This implies that the value of private data stored in Smart Home devices should only be defined by the users themselves. Since the users cannot define it today, this value is however set by industry players instead.

text: 3.2 Vendors lack incentives to enhance security in Smart Home devices and services

text: Most security researchers in IoT describe the current state of the industry as not security minded. In particular, many actors are hobbyists or come from the startup domain. It is easy to estimate that it might cause issues on simple topics such as security updates, since these kind of actors:  Might not have the culture of long-term support.  Might not want to provide updates as long as their products live.  Might not be aware of the importance of security update.  Might even be hostile to third party researchers disclosing vulnerabilities…

text: More generally, the issue of the community culture is seen as a major obstacle to security. Our stocktaking and interviews shows however a slightly different picture: our overall analysis of weak security was confirmed by the actors themselves and generally resulted from an intentional market positioning.

text: Many interviewees were quite aware of security good practices, but were lacking incentives to implement them in their products. Few incentives exist to implement security, especially for low-cost devices. During the interview phase, all industry actors described the consumer market as cost-driven, functionality driven, with short time-to-market requirements, while security is a criterion only in business-to-business contexts.

text: Interviews and stocktaking have shown that many vendors are still waiting for end-users to ask for more security. The consumer market is seen as being mainly cost-driven, with:

text:  An increasing awareness of privacy issues.  A very limited awareness of cybersecurity issues.

text: Some vendors are voluntarily implementing security, so as to protect the company image in case of an attack. Cost and innovation are however competing with security: except for Cloud services or smartcard providers, many actors see certification as an expensive marketing tool. However, security-aware actors share the idea that legislation, and a mandatory certification scheme, could be the only incentive able to counterbalance the time-to-market pressure, while maintaining equality amongst actors on European markets.

text: Effective implementation of security measures is usually found in actors who target both business-tobusiness and consumer markets, as the need is generally expressed by business customers.

text: 3.3 Smart Home devices and services implement few security measures

text: As a consequence of the previous finding, it appears that many devices or services implement few security measures.

text: When following the list of good practices of Sections 4 to 7, it appears that the only features implemented today are:

text:  Development security measures (often limited to quality control measures; in some cases, dedicated security testing is performed in a very short timeframe, such as 3-4 days campaigns)  In terms of security functions: o Security audit trails (generally not protected and more used as “log files” than audit trails). o Secure communications (but usual good practices such as certificate pinning are ignored when using standards such as TLS). o Cryptographic support (generally only found in high-capacity devices such as gateways; in some cases, vulnerable cryptography is used, as shown in the OMA vulnerability cases). o privacy protection (mainly addressed on the remote service side, while user data are generally not protected on devices). o authentication (often not implemented for local network communications, and strong password policies are not always available). o very limited self-protection and hardening measures.  In terms of integration in the HAN: o Trust relationships (albeit often weak ones, such as vulnerable pairing, or usage of trust elements without a capacity to revocation or renewal).  In terms of usage until the end-of-life: o Limited operational security and maintenance.

text: 3.4 Smart Home Environments result in new security challenges

text: Actors coming from the world of IoT might face new security challenges in Smart Home Environments:

text:  Devices will have to meet higher privacy expectations than in usual IoT devices. These specifics lead to increased privacy risks for users, while the cost of keeping data safe might be too high for industry players. The Data Protection Directive (which may soon be superseded by the General Data Protection Regulation) addresses general privacy protection, but might not be suitable to prevent such privacy violations. For example, a Smart TV may cause several privacy issues with that regard. Home is by definition the place where privacy is expected to be enforced.  Devices may integrate safety concerns that are specific to home. For example the loss of control of a thermostat, a smoke detector or a CO2 detector might have consequences on the user safety. The CE marking implies liability for damages or injuries due to defects, but not due to security negligence.  Vendors may integrate the fact that, when home is concerned, security attacks are not only a hypothesis but a fact to be dealt with. For example, a smart lock or safe is a security product and

text: must be designed to sustain a cybersecurity attack. Companies selling security devices are often unaware that the “smart” part of the device can be easily compromised and rely too much on the physical part of the device.

text: 3.5 IoT vulnerable “building blocks” cause vulnerabilities to be shared at large scale

text: IoT in general provides a very large ecosystem of hardware, operating systems, software and services upon which vendors can build solutions.

text: Many vendors are now able to integrate solutions easily, by using existing “building blocks.” But if these blocks have security flaws, these flaws will be present on all the solutions that use them.

text: The situation is summed up by researchers in a few sentences: Your vendor may be leveraging six other vendors. Where’s your data going once it enters that IoT device? Who has access to your network via proxy

text: connections?

text: Several issues directly come from this situation:

text:  Developers do not necessarily know which frameworks and APIs are useful or vulnerable. While this is sometimes described as a lack of expertise from the developers, this is actually more probably related to the sheer number of third-party and open-source components available. This is already an issue in many domains. A whitelisting approach might help vendors in the process of selecting secure third-party or open-source APIs.  Vendors may be locked in third-party operating systems and applications, and not be able to patch or migrate to other solutions in cases of vulnerabilities.  Many devices share the same third-party services or components, thus sharing their potential vulnerabilities. There is at that time no easy means: o To detect who are the providers of all the components and services that are integrated in a given product, and o To select suppliers based on security requirements.

text: 3.6 IoT pervasiveness and dynamicity

text: IoT devices in general are pervasive and dynamically interconnected. This has several consequences:

text:  It increases the attack surface on a given device (which may be attacked from several sources: devices, social networks, other online services…)  It increases the nuisance potential of a device after it has been compromised (which may be connected to many other devices).  It increases the combinations between devices and services, leading to interoperability issues (for example unintentional denial of services due to badly implemented bandwidth usage). Such issues are not security issues but may be used to investigate vulnerabilities or leverage attacks.

text: Smart Home adds a level of dynamicity, since nodes can enter or exit several kinds of networks dynamically:

text:  Mobile networks and internet (WAN, LPWAN).  Virtual networks of a service provider (different identical devices and the corresponding cloud services or device management services).  Home area network (several different devices in a single user network).

text: The integration of all the devices grows more and more complex due to the number of devices and their capacities to dynamically interact (researchers use the example of the If-This-Then-That mobile application, which triggers Smart Home devices behaviour on events coming from other devices, social networks, and so on).

text: 3.7 IoT brings new constraints on security

text: The configurations of some devices (typically home automation sensors) are too weak to implement strong protections. This is due to not only the hardware or the device connectivity, but also the lack of identified security standards dedicated for these use cases (weak CPUs, limited memory, low bandwidth, battery usage, etc.)

text: Interaction with vendors show that many of them are confident in the technology to solve these issues. Hardware gets more powerful year after year. It should solve the present limitations in terms of security, even in small devices such as sensors. The main perceived barrier is the bandwidth, when using low-power networks.

text: Good practices for a Secure Smart Home Environment

text: This study provides a detailed list of security “good practices” to mitigate the threats identified in Smart Home Environment. We identify different types of good practices that range from basic security hygiene to dedicated countermeasures against given threats, for different types and classes of devices as well as for associated remote services.

text: The list can be utilised by stakeholders as a companion to their risk assessment, either to evaluate the current level of security or to enhance it with new security measures. For that purpose, this study highlights the application of good practices to the different classes of devices and services. This list should be interpreted as an informative statement.

text: The good practices are presented according to the devices and services lifecycle, as well as to the stakeholder to which they apply as presented in Figure 3. These good practices are separated into the three phases of the lifecycle of devices and services:

text: 1. Development of Smart Home devices and services by device vendors and service providers. During this phase, the vendors and service providers define the requirements of the product, design, develop and test the product. The associated good practices are presented in Section 5. 2. Integration of devices by the end-user into his Home Area Network. During this phase, the enduser configures and connects its Smart Home device to its HAN, potentially with support of the device vendor, the service provider, or the electronic communication provider. The associated good practices are presented in Section 6. 3. Usage of the devices and services until their end-of-life. Apart from direct and local interactions with his device, the end-user may also request support from the vendor and use on-line services related to the device through various communication channels. Thus this phase may imply interactions with the device vendor, the service provider, or the electronic communication provider for usage and decommission. The associated good practices are presented in Section 7.

text: Good practices for the development of Smart Home devices and services

text: This section describes the good practices related to the development of Smart Home devices and services. These good practices consist of two different sets:

text:  Security “good practices” for the development process of Smart Home devices and services.  Security functions that are considered good practices. These security functions address the devices themselves and theirs interfaces with web services and mobile applications.

text: 5.1 Security of the development process

text: The development process comprises the design phase, the development phase and the testing phase. For each phase, several good practices are highlighted.

text: 5.1.1 Design phase

text: Security concerns must be taken into account in the early phases of the product or service lifecycle. As a general rule, the security architecture of a solution must be defined and documented early. This is the practical implementation of the often-used security by design requirement.

text: At the design level, several aspects can be recommended to vendors as well as service providers, as described in existing guidance.

text: Use defence in depth

text: Applies to remote services, class 1 devices and higher

text: Designers should assume that their security measures will be compromised at some point – and they should therefore provide redundancy by the means of layered security measures. It also means that error and attack scenarios should be taken into account during the design (not limiting the design to nominal cases).

text: Consequently security functions should have clear and limited interfaces to the “non-secure” functionality. It enables to clarify interfaces between the “secure” and “non-secure” functions, thus limiting the design errors that might arise. It enables to separate development teams and focus the task of security experts only on secure parts.

text: When “secure” and “non-secure” parts are not necessarily easy to distinguish, using a modular design gives an assurance to separate functions and clarify interfaces.

text: All “secure” and “non-secure” parts should be reviewed from a security point of view, since many vulnerabilities can originate from “non-secure” parts such as memory management or string formatting.

text: The design stage should clearly explain the assumptions for the security requirements. Such assumptions include:

text:  Limitations in the usage of the device (for example, a given device might need ZigBee connectivity to transmit security alarms, implying that it will not be able to send alarms when deployed behind a very thick wall)  Assumed properties of the environment (for example, assuming that the certification authorities in the certificate store are all trusted and not compromised)

text: Assumed properties of cryptographic properties (for example, assuming that a given algorithm and key size are sufficient for a given task).

text: Consider third-party review by security specialists for developers with limited security experience

text: An independent third-party review is recommended for the whole design; it is deemed to be crucial especially for cryptography, in order to select the appropriate algorithms and associated functions, and know-how to implement or configure them correctly. This review should be a mandatory step during the design stage, since cryptographic operations might put resource conditions that have a significant impact on components procurement. Such a review is also absolutely crucial for system security, i.e. considering the security elements in the whole usage context, in order to avoid inconsistencies and design flaws (for example sensitive elements could be safely stored but allowed to leak by other channels such as error messages)

text: Applies to remote services, class 0 devices and higher

text: Developers must prototype the user interface as soon as possible in order to identify ways to help users on security issues.

text: Interactions with the user can happen in many forms and the security impact of these interactions have to be carefully planned. The US Federal Trade Commission (FTC) reminds that it does not only concern setup wizards, admin dashboards or external signals (LEDs/alarms/icons...), but also sign-up procedures and information emails/or SMS.

text: 5.1.2 Development phase

text: The importance of development of the product for security is two-fold. It is during this step that security functions are used or implemented to satisfy the security requirements from the design phase and also that programming errors may introduce security vulnerabilities.

text: For that purpose, actors involved in product and service development use security-enhancing tools, and ensure training and awareness of their developers.

text: Use configuration management tools, and leverage upon development environments such as compilers or static analysers

text: The source code (for hardware developers, this may include HDL files) should be managed according to a sound configuration management process, in order to be able to identify versions, responsibilities of changes, and so on.

text: Static code analysis should be used to gain security assurance on the code (by identifying potential vulnerabilities), as well as quality assurance. Static code analysis is usually based on automatic tools.

text: Compiler security options must be used when native code is used.

text: Take security into account when choosing your programming language; when available, leverage upon the operating system security functions

text: Some programming languages offer memory management capacities. The use of such “managed code” instead of native code should be considered from a security point of view, but it must be considered carefully. The usage of “Managed code” in place of native code has both benefit and costs:

text:  Benefit: Managed code can reduce the risk of vulnerabilities due to memory allocation, and the need for memory management guidelines.  Cost: Managed code can make it harder to really control the erasure of elements in memory, so native code might be more appropriate when processing key material, for example. When used for security functions, managed code is also easier for an attacker to decompile and understand.  Cost: any vulnerability in the shared memory management capacities lead to a single point of failure so the runtime associated with the managed code must be kept up-to-date.

text: The good practice generally consists of using both “managed code” and native code for different purposes, and limit native code to parts where a low level of control over security elements is needed.

text: Operating system security options must be used with the associated compiler options.

text: Use standard, secure frameworks or stacks whenever possible – do not redevelop security functions

text: For example in cryptography, existing libraries must be used: redevelopment is widely considered as a bad practice.

text: Of course, existing libraries might also have flaws, and there is no simple criterion to assess whether a given library should be trusted or not. Several information should be used for this purpose:

text:  Does it implement standard mechanisms? (e.g., “standard” mechanisms may refer to mechanisms approved by the ISO ISO/IEC JTC 1/SC 27 subcommittee, including its workgroup 2 for cryptography. It may also refer to mechanisms approved by national cybersecurity agencies).  Is it widely used? (even if this is no definitive guarantee of security, a widely used library such as OpenSSL should probably be preferred to a brand new library that has been developed a few weeks ago).  Has it been audited? (for example an independent audit was performed on TrueCrypt to assess its resistance to cryptanalysis).  Has it been verified? (for example some libraries underwent government or proprietary certification programs such as FIPS 140-2, which give an additional assurance).

text: Ensure team training and awareness

text: It is necessary to make sure that the teams in charge of security are skilled enough:

text:  Secure programming guidelines should be used and regularly updated whenever flaws are found in the product. An example of such guideline can be found at OWASP.  Security training must be in place for the developers contributing to critical parts.  Security training should also be in place for all the other developers/testers, as many security flaws can occur in “non-secure” parts (for example the lack of input validation in user interfaces).

text: 5.1.3 Testing phase

text: Testing the compliance of a product, or service, against its specifications, is required to give assurance of its correct behaviour. Such tests should not only focus on the “nominal” behaviour, but also cover a robust error handling and fault tolerance. This will reduce the opportunity for an attacker to exploit vulnerabilities, for example improper input validation.

text: However, even to claim a basic level of robustness against attacks, compliance testing is not enough. For example, a simple error case test of a web service input fields will not be able to detect a potential vulnerability to a script injection. Vulnerability assessment and testing provide the appropriate assurance against an attack, because they actually consist in simulating or even performing such attacks.

text: Tests must demonstrate that the security behaviour of the product or service is effectively implemented.

text: Patches must be validated (for example if patches are applied to usual open source libraries, Linux kernel, OpenSSL…).

text: Automated unit tests and continuous integration should be considered.

text: Automated and manual test plans must be updated according to the findings of the security audits.

text: Compliance testing should be completed by dedicated security audits or penetration testing.

text: Skilled experts should simulate attacks and try to circumvent or weaken the product or service security functions. The scope may vary depending on the target product but should at least include:  A design and code review for critical parts (notably cryptography) and for the system as a whole.  A configuration review of the product or infrastructure.  A network scan (for infrastructures).  A radio frequency audit (if applicable).  An assessment of the public vulnerabilities that might impact the product.  Penetration testing.

text: Perform a privacy assessment

text: Conduct an analysis of the design and implementation of the product or service, to ensure that private data is correctly processed with regard to European regulations.

text: The approach consisting in implementing privacy protections from the design phase has led to the often used notion of “privacy by design”, which may appear confusing to several vendors, since it might lead to think that privacy can be obtained by the application of simple design patterns or rules. Quite the contrary, this approach is more easily implemented by performing an independent assessment of the design.

text: Such assessment can take multiple forms but is often called a Privacy Impact Assessment. This activity can typically be performed by the developer itself or by a third-party, which guarantees both skills and independence for the assessment.

text: As a good example of such approach, the BSI issued in 2011 a guidance in English:  A Privacy Impact Assessment Guideline.  A Privacy Impact Assessment Guideline for RFID applications.

text: Vendors should also be aware that their national privacy agencies, such as the French CNIL, might have published guidance for privacy assessment in their own language.

text: 5.2 Security functions for hardware and software

text: This section describes security functions, or requirements, which are considered good practices for devices as well as mobile applications or services.

text: These requirements use categories loosely adapted from the Common Criteria security certification standard. These categories are:

text:  Security audit: security events must be logged, and users should be notified whenever needed.  Communication protection: communication should be protected against disclosure, modification, replay and denial of service.  Cryptography: Confidentiality, integrity and authenticity must be protected by using strong and standard cryptography. Keys must be managed securely, and the use of a trust infrastructure (such as PKI) is encouraged.  User data protection: the integrity, confidentiality and authenticity of user data must be protected. Confidentiality protection must be defined with regards to privacy issues.  Identification, authentication, authorization: strong authentication methods must be used, as well as access control mechanisms. Passwords and sessions should be managed accordingly.  Self-protection: HW and SW self-protection measures should be in place to protect previous security functions. Data used to enforce these security functions should be protected, and hardening should be used to reduce the attack surface.

text: 5.2.1 Security audit

text: Security audit aims at enabling logging, audit and forensic and at providing user notification.

text: Log security events

text: Security events must be logged and access to the logs must be documented and protected from disclosure to unauthorized users.

text: Logs are also needed for device integration. Typically, HW suppliers must give possibility for their customers to understand security events happening at the HW level.

text: However logs may also give information to an attacker, which is a serious security drawback. For this reason, the audit trail must be protected:  Logs should be anonymous (see good practices on User data protection for anonymity measures).  Avoid logging information that would give useful information to an attacker.  Access control mechanisms should limit the access to the logs (see good practices on Identification, authentication, authorisation).  When sent to a remote system, logs should be protected by cryptographic mechanisms (see good practices on Cryptography).

text: HW and embedded systems should provide clear error data that can be leveraged upon by the SW vendors. The user must be notified in case of security errors, updates or compromised data in a device or service they use.

text: In particular, users must be notified in the case of security events . Notification might vary greatly depending on the type of software considered. Mobile applications notification, messaging such as SMS or e-mail, hardware interfaces such as LEDs, dedicated error messages to a gateway…

text: However developers should be aware that for some functions, an excess of clarity is a valuable information for an attacker. As a common example, when a login fails, the product should not communicate to the user whether the error is due to a non-existent login or a bad login/password combination.

text: The optimal balance between not enough or too much clarity is to be assessed during dedicated security testing (see good practices for the Testing phase).

text: 5.2.2 Communication protection

text: The protection of communications aims at protecting against disclosure, modification, replay and Denial of Service. Moreover, the protection of communications shall also protect authentication and associated mechanisms.

text: Provide end-to-end protection in confidentiality and integrity. Use protocols that resist replay attacks. Favour methods providing forward secrecy whenever possible. This should be true even for the communication of already encrypted data.

text: Encryption must cover not only WAN traffic (Internet and LPWAN traffic), but also local networks.

text: Many protocols use both transport layer and applicative layer protection. The need for applicative layer protection comes from end-to-end protection needs: the transport layer could be exposed if different transport technologies are used during the transmission, therefore needing a dedicated protection:

text:  In TCP communications, the latest version of TLS is the default choice for securing the transport layer; DTLS is an equivalent of TLS for UDP communications.  Applicative layer can be protected by recognized cryptographic means, so as to protect confidentiality and integrity of the payload.

text: Note that manufacturers and service providers are expected to manage the security of their cryptographic keys and certificates used by their devices and services (see good practices on Cryptography).

text: Using a standard security library does not mean that the product will automatically be secure. Developers must be aware of the vulnerabilities (due to a flawed implementation) and limitations (vulnerability of the protocol itself) of the third-party components they use. They should mitigate them whenever possible by performing patching and by securing the configuration of the communication stacks, which might typically include:

text:  Bluetooth.  6LowPAN/ZigBee/802.15.4.  Wi-Fi.  TLS or DTLS.

text: Regarding Patching: Communication protection protocols are often implemented by using third-party or open-source libraries. They all need frequent patching: vulnerabilities are regularly found in all these implementations, even those considered as “industry standard.” Communications protection work only as long as firmware updates are available and applied to fix vulnerabilities. See good practices on Operational security and maintenance for more details on security updates.

text: Regarding Configuration: Due to the existence of vulnerabilities in frequently used protocol implementations, configuration of the library is a significant part of the security functionality. Developers should in particular be vigilant to the configuration of cipher suite negotiation and key sizes: allowing weak cipher suites provides an entry point for attacks aiming at downgrading the level of security of the exchanges . See good practices on Self-protection for more details on hardening. Amongst many examples, here are two recent vulnerabilities:

text:  OpenSSL libraries that were compiled to work with heartbeats were vulnerable to the Heartbleed bug.  ZigBee allows some flexibility, thus potential implementation or configuration flaws.

text: Consider denial of service as a usual threat to communication infrastructures.

text: This threat should be addressed from the design phase of the infrastructures.

text: On this topic, this study encourages the vendors and service providers to read the ENISA Internet Infrastructure Threat Landscape (for network components) or the GSMA IoT Device Connection Efficiency Guidelines.

text: 5.2.3 Cryptography

text: Cryptography aims at many protection measures to protect data confidentiality and integrity rely on cryptographic functions. In a broad definition, cryptography support for security must include user’s protection and authentication, data protection and the cryptographic infrastructure. For example, such a support may implement:

text:  For authentication primitives: o user/entity authentication; o message authentication and integrity.  For data protection: o symmetric or asymmetric encryption; o hash functions; o digital signature.  For cryptographic infrastructure: o random number generation; o key management.

text: We identify hereafter four main considerations for cryptography:

text:  Use strong and standard cryptography, including random number generation.  Use hardware-accelerated cryptography with care.  Manage and provision keys securely.  Use of trust and reputation infrastructures.

text: Do not create proprietary cryptographic schemes, but use state-of-the-art standards instead. Even a home-brewed implementation of a standard is not a good practice when standard implementations are available.

text: If needed, consider getting advice from security experts or your national cybersecurity agency. If no recommendations exist for vendors at a national level, ENISA recommendations should be considered as a

text: reference. This applies also to random number generation, which is a critical part of the cryptographic support. A possible recommendation would be the use of cryptographically secure pseudorandom number generators.

text: Rely on an expert in cryptography for interfacing with HW accelerated cryptography or secure elements, or even using or configuring a standard implementation.

text: These tasks are difficult for most of developers. If not properly done, the security might be heavily reduced or even completely suppressed. This part should be performed by an expert in cryptography or at least a third-party code review should be performed to ensure that HW or a standard implementation of cryptography is properly used.

text: When designing or procuring HW, pay attention to the requirements of cryptography in terms of CPU, memory and bandwidth and their impacts on battery.

text: Applies to class 1 devices and higher

text: On high-capacity devices, consider using dedicated hardware security modules.

text: Be aware of limitations of HW-based cryptography solutions and choose wisely whether a SW or HW solution is needed for the given context.

text: Applies to class 1 devices and higher

text: HW-based cryptography solutions may help avoiding the incorrect implementation of cryptographic algorithms by software vendors, as well the coexistence of multiple implementations of the same algorithms. They eventually provide implementations that are more resource-efficient.

text: Low-end HW might not be able to perform strong cryptography (due to memory and/or CPU capacities for example); consider using Elliptic Curve Cryptography over RSA, especially for CPU- and memory-limited devices.

text: Choosing HW accelerated cryptography means that a reasonable assurance must be obtained on the quality of the HW implementation, since “bad cryptography” on HW will be leveraged on all the SW using these functions.

text: Regarding true and pseudo-random number:

text:  As a general rule, a true random number should be used for key generation, but may not be required for salts, initialization vectors etc., where a cryptographically secure pseudo-random number may be sufficient. One may argue that using a cryptographically secure software pseudorandom number generator is more secure than a badly implemented hardware “true random number generator.”  When using hardware claiming a “true random”, developers should consider using strong postprocessing functions. The functions used for that purpose are typically block encryption or hash functions.

text:  Some standard groups for Smart Home address this point by always requiring a true random, and compliance of this random to given test vectors.

text: More details on the different categories of random generators can be found in references from national cybersecurity agencies.

text: Vendors could consider HW-based cryptography as a criterion for HW procurement (Smart Home devices or network HW for cloud infrastructures). In this case, HW-based cryptography must be used according to the HW guidelines that will describe how to securely use the HW.

text: If needed, consider getting advice from security experts or your national cybersecurity agency.

text: Manage keys securely

text: As a general rule, cryptographic keys should be securely generated, distributed (or provisioned), used, stored, and deleted (including revocation).

text: Badly implemented key management can introduce vulnerabilities that are often exploited, even in Smart Home devices.

text: Smart Home introduces a few new specifics: Smart Home incorporates technologies coming from machineto-machine technologies without direct user interface (for example surveillance cameras). It has consequences in terms of key provisioning for at least two reasons:

text:  Devices without direct user interfaces are particularly vulnerable to attacks on a PKI (loss of certificates…). While users of a PC can easily delete or install certificates, such devices rely mostly on remote administration, and sometimes do not even allow end-users to perform such administration tasks. For this reason, Smart Home vendors should consider very carefully the revocation mechanisms associated with their devices, and the end-user means to easily fix issues of that kind.  Industry players introduced the notion of remote provisioning for mobile communication. While keys are loaded in SIM cards in protected environment, the “embedded UICCs” rely on remote subscription management systems to obtain key material. The protection of these exchanges is consequently critical and must be assessed accordingly by manufacturers and vendors. Should the keys be leaked, the user and the vendors could be at risk in many ways (loss of control over the device, eavesdropping, credential theft, cloning etc.). More generally, the notion of confidential key agreement must be considered in IoT in general, and Smart Home in particular.

text: As a general practice, Smart Home devices should leverage upon their user interfaces to mitigate the risks caused by key management constraints. Key management must be transparent to the user. It shall only be necessary for the first-time peering. For that purpose, it is important to provide user-friendly mechanisms

text: to ensure authentication. For example, a visual graphic interface can be used to authenticate devices, with a QRCode.

text: See good practices presented in Section 6 on the Integration of devices in the Home Area Network.

text: 5.2.4 User data protection

text: The user data protection includes:

text:  The notion of privacy/confidentiality.  The notion of integrity and authenticity (for example related to theft of loss of control over the devices).

text: For that purpose, it is important to define privacy/confidentiality protection measures before they are implemented in devices and services.

text: Identify personal data

text: The interpretation of privacy protection raises many issues, one of them being to successfully identify what can be considered a personal data. The definition according to the EU Data Protection Directive

text: includes data relating to an identified or identifiable person.

text: In the case of the Smart Home devices, however, it may be safe to assume that any data related to the user activity is somehow personal, since the location of this activity can be linked to an occupant of the user home. This last approach will have to be continued throughout the whole product or service lifecycle.

text: Metadata should be considered as personal data by default, since they are subject to the same threats.

text: Consider getting advice from your national data protection agency.

text: Implement transparency measures

text: The interactions with the user (which should not be limited to the Terms and conditions) enable to cover the legal transparency requirements

text: The service or device provider must communicate:  The provider’s name and address.

text:  What data is collected, in layman terms.  The purpose of processing, explaining notably why the processing is necessary for the performance, or why it is necessary for compliance with a legal obligation.  The recipients of the data.  How the user can: o Access all data processed about him. o Require the rectification, deletion or blocking of data that is incomplete, inaccurate or isn't being processed in compliance with the data protection rules.  And all other information required to ensure the processing is fair.

text: The service or device provider must require the consent of the user (or “data subject”).

text: On top of legal requirements, actors might also consider:

text:  Defining a strict opt-in policy.  Enabling rectification, deletion or blocking of data without a reason.  Ensuring data portability.

text: The design phase of the service or product, where the details of the processing have to be assessed with regards to the explicit and legitimate purposes. The actors must ensure that themselves and their subcontractors or suppliers:  Do not process user data more than needed.  Do not pursue an illegitimate purpose with regard to user data.

text: As a general rule, third party components integrated in the device or third party cloud services should not access unencrypted user data unless user agreement has been obtained. Access control or anonymity/pseudonymity measures gives assurance that user data is not accessed by these third parties.

text: Define access control, anonymity and unlinkability measures to enforce the protection of private data

text: These measures intend to protect confidentiality and integrity are typically:  Access control measures: o As a general rule, access to sensitive data should be controlled (see good practices on Identification, authentication, authorisation). o For web services and devices including virtualization, access control could be completed by data isolation (see good practices on Self-protection).  Anonymity measures:

text: The typical example is ensuring that the key used to browse the “customer database” is not the same as the key used to browse the “usage analytics database.” However the situation is more complicated in practice: in the case of Smart Home, for example, network locator is a critical factor of linkability and should be taken into account accordingly. Vendors should also be aware, that unlinkability can also:

text:  Cause trust issues and reduce attack mitigation capabilities (for example if a user cannot be notified that their device is compromised).  Cause a conflict with other legal requirements.

text: There is no one-size-fits-all good practice to balance unlinkability against other desired properties. The right balance must be defined during the design stage by examining the associated risks.

text: 5.2.5 Identification, authentication, authorisation

text: Applies to remote services, class 2 devices and higher

text: The objective is to perform strong authentication before granting access to sensitive functions or data.

text: Devices or users connecting to a server must be able to authenticate the server. Reciprocally, servers must be able to authenticate clients and users.

text: Mutual authentication consists in demonstrating cryptographically to both the client and the server that they are communicating with the expected party.

text: Mutual authentication is generally supported by Public Key Infrastructures (PKI) and certificates. The use of such infrastructure components is supported by protocols such as TLS. However using methods such as these does not grant a secure mutual authentication, unless:

text:  There is a certificate for both the server and the client.  Certificates are properly validated (ruling out, for example, the use of self-signed certificates).  Revocation lists are verified (alternatively, interrogations to an OCSP server).

text:  All services require this authentication step. Which also means that even private URLs accessible on a device must require authentication.  Certificate pinning is used.

text: As a side note, it must be noted that certificate pinning does not eliminate the need for certificate validation. For example, the pinned certificate can be an intermediate or root Certificate Authority (CA) – which means that the end certificate still has to be verified against the CAs.

text: Users should be authenticated by multi-factor authentication whenever possible, including for authentication to cloud services or mobile interfaces as well as local administration sessions of devices.

text: Several methods can be used for multi-factor authentication. As an example, the NIST provides a summary of these methods.

text: Implement access control measures to separate the privileges of different users as well as the privileges of different applications

text: The objective is to control access to sensitive functions or data.

text: Implementing privilege levels, rings or domains is a good practice. Some platforms implement such levels in hardware. If such functions are available, vendors are advised to use them. If not, operating systems already provide capacities to implement privilege control. At the firmware / software level, access control must be used to control access rights of both applications and individuals. In particular:

text:  For devices with an operating system, not all applications need to be root or be executed in kernel land.  Not all individuals need to have access user data stored in the device or associated services.

text: Other measures are required at a firmware or software/applicative level:

text:  User accounts must be unique and separated for both local and distant services.

text:  The device must distinguish between normal users and admin users. The latter only have access to configuration functions.

text: It is important to allow and encourage the use of strong passwords.

text: As it is regularly demonstrated, passwords are often a weak point, whether they are weak user passwords or weak default passwords for products internal services. Many devices use strong protection measures that are defeated by the lack of proper password management.

text: This concerns all possible uses of passwords: direct device interfaces such as JTAG, but also web, mobile or cloud interfaces. The usual measures are the following:

text:  Allow and encourage the use of strong passwords.  Require the user to change credentials (username, password) at their first login.  Do not use hard-coded or “default” passwords or shared passwords, for instance for remote support accounts.  Do not store/expose passwords in clear text or with weak protection. Adaptive one-way functions such as PBKDF2, scrypt or bcrypt should be preferred.  Use countermeasures against password guessing / account harvesting. Services must be protected against: o Horizontal guessing (testing a small number of usual passwords on a high number of user accounts). o Vertical guessing (testing a high number of passwords on a single user account). o This typically includes lock-out and delaying measures as well as high password strength / entropy and diversification of passwords across devices. This also includes countermeasures against account discovery or other means used to exploit password recovery functions.  Define options for password control. Typically, in the case of an administrator account, the default 99 100 option should require strong passwords by default.

text:  Password policies are eventually useless if the final user is not fully aware of the threats and good practices. Vendors and service providers should consider raising the awareness of their users whenever possible, for example to support the use of password managers. Examples of simple guidelines can be found in ENISA Basic security practices regarding passwords and online identities.

text: Applies to remote services, class 2 devices and higher Enforcing a secure session management policy also contributes to making sure that the authorized user is the one using a given session. Typically:

text:  Sensitive functions such as administration via web services should require re-authentication.  No data should be transmitted before authorization.  Strong (random) session handlers should be used to avoid replay.  The user must know at any time if, and why, they are logged on a particular service, meaning that no passive sign-up for third party services should be performed.

text: 5.2.6 Self-protection

text: Self-protection includes all measures taken to enhance the robustness of previously mentioned security functions. Developers should challenge every security function of their design, consider how they could be bypassed or weakened, and eventually implement self-protection measures. The main topics considered here are:

text:  Hardware self-protection: these measures aim at protecting the hardware against physical attacks or observation. They include tamper evidence or tamper resistance, and secure design measures.

text:  Software self-protection: software also contributes to protect existing security functions, typically by validating inputs and outputs, or by separating the capacities of the different software components (levels of trust, virtualization…).  Non-user data protection: data used to enforce the security functions should be protected. These measures intend to avoid storing internal keys as cleartext, or any other data that could be used to circumvent the service security.  Hardening: hardening consists in reducing the attack surface of the product or device. This includes removing unused services or interfaces (for instance remote shell access to the device, which should not be needed in production), as well as integrating malware protection.

text: Most of the self-protection measures must be considered from the early design phases. Only the hardening can be defined as an additional measure that can take place after the design and implementation phases.

text: Applies to remote services, high-capacity devices

text: Devices vendors should be aware of the following mechanisms in order to limit hardware and/or software tampering of their devices and services:

text:  Basic to moderate “tamper resistance” mechanisms, which will slow an attacker (this typically includes specific sealing methods for the casing, or the use of epoxy to protect components, or the entire board, disconnection of debug ports, integration of a Trusted Platform Module…).  Basic to moderate “tamper evidence” mechanisms, such as tamper-evident seals or labels, or even switches or sensors (light, power…) that will trigger a tamper response.  Basic to moderate “tamper response” mechanisms such as sending an alarm to a remote service, logging a security error or erasing sensitive data.

text: While they may not be recommended for every case, vendors should consider using them depending on the level of sensitivity of the assets stored on the device, or the intrinsic value of the device itself. In particular, even constrained devices could be able to implement some kind of tamper evidence, even if they are not able to implement resistance and response.

text: More details on anti-tamper technologies can be found at different sources, for example Black Hat or ICCC conferences.

text: Hardware design can be used to make the device harder to attack. In particular:

text:  Memory (including memory controller) can include measures such as: o Secure erase and wear levelling. o Direct memory access, Non executable memory, …

text:  Printed Circuit Board (PCB) design can contribute to security by including: o Blind and buried vias. o Buried bus lines. o Electronic fuses and similar techniques, for example to deactivate JTAG access (other uses can also be considered).  System on Chip (SoC) design can include some of the previous measures, and can also include: o Pin placement. o The implementation of “system level” features such as HW Virtualization, micro kernels, Secure boot, Trusted ExecutionEnvironments…

text: The ease of access to the components, as well as their removability, can also be considered during the design phases, even if it cannot be the primary physical protection measure.

text: Protect the software security functions with self-protection measures by reinforcing interfaces and strengthening the application separation at runtime

text: Apples to remote services, class 1 devices and higher

text: Software can contribute to self-protection measures for instance for robustness of interfaces against bad inputs. Secure implementation, thoroughly tested, will protect against common attack vectors such as:

text:  Buffer/heap overflows.  OWASP’s List of the Top Ten Web Vulnerabilities: o Injection flaws. o Broken authentication. o Cross-site scripting (XSS). o Insecure direct object references. o Security misconfiguration. o Sensitive data exposure. o Missing function-level access control. o Cross-site request forgery (CSRF). o Use of components with known vulnerabilities. o Invalidated redirects and forwards.

text: This includes robustness of network interfaces against buffer overflows or fuzzing.

text: Implement trust zones for the execution of applications (and/or ensuring segregation or execution protection), for example by whitelisting applications, or by using Trusted Execution Environments or Secure boot, or SW virtualization…

text: Provide a secure default configuration

text: The default configuration of devices and services should be secured.

text: The operation mode of the device (or service) should be the most secure one by default. A user might arguably want to disable a given security function, but this should be the consequence of a deliberate action from the user, and the user should be warned that this change reduces the security of the solution.

text: Providing a secure configuration by default means in practice that:

text:  A remote service will use HTTPS by default.  Setup wizard for devices should include the necessary steps to upload any security configuration data such as certificates.  Stronger password policies will be selected by default…

text: Encrypted storage is not only useful to protect user data, but also to protect data that is needed to enforce security on the device.

text: Internal data may be just as sensitive as user data, but are often not protected enough, leading for example, to situations where “hardcoded root credentials, API keys for Amazon Web Services, URLs never meant to be known to end-users, and manufacturing network configurations” can be found in cleartext on devices.

text: As a general rule, configuration data should be encrypted at rest and in transit.

text: Perform hardening on both HW and SW

text: Perform hardening to reduce the attack surface: remove unused services or interfaces, integrate dedicated security software, activate memory or control flow protections.

text: For devices that have a complete operating system, several measures can be considered to harden the device, such as ASLR, non-executable memory, process segregation or sandboxing.

text: Another measure is removing unused tools, services and libraries. Unnecessary services should not be present on the device (typically telnet must always be deactivated, but even SSH or FTP can be deactivated in many cases). This type of measures is also applicable at a network level: the device should not leave open ports, especially ports that could be exposed via plug-and-play protocols.

text: The default configuration of the device should be based upon the most secure parameters, and users should be warned if they have the possibility to roll back to less secure parameters. For example multifactor authentication should be the default configuration. Users should be warned if they want to configure the service to single-factor authentication.

text: Vendors should also consider integrating malware protection to their systems since the Smart Home ecosystem provides many possible ways for malware to enter a device (mobile, personal computer, device network interfaces…).

text: Eventually, vendors should consider deactivation or protection of the external interfaces for example:  Protecting the physical debug interfaces such as JTAG/ISP (by password and physical action), or physically deactivate the physical debug access.  Including mitigation to avoid exploitation of interfaces such as I2C/SPI buses or serial interfaces.  Suppressing the administration interfaces or limiting it to a local access.

text: More generally, vendors should consider their means of protection for:

text:  BootROM interface.  Firmware update interfaces.  Configuration and calibration interfaces.  Inter-processor IPC.  USB external interfaces.  Protection against DMA attacks.  No unnecessary external interfaces should be accessible from the exterior of the device.

text: Good practices for the integration of devices in the Home Area Network

text: Security of the devices and services is not sufficient in a dynamically connected environment. The Smart Home device is usually connected to a controlled network, typically the Home Area Network. This network can bring additional security features. We suggest to introduce “resilience” as “the network capacity to ensure security control over the devices it contains.”

text: As examples of such features, a HAN smart hub or gateway can provide resilience on the HAN by providing firewalling, authentication, or malware detection. In the same manner, a mobile network operator can provide resilience on the mobile network by providing authentication, encryption, or anti-spam.

text: This study distinguishes between three main categories of good practices related to this topic:  Devices in the HAN should provide minimum reliability, even if they are not completely secured.  There should be a mean to give trust levels to devices connected the HAN.  Additional network security measures should be provided on the HAN, for example by dedicated Smart Home gateways, ISPs set-top-boxes, or via service providers (such as anti-virus or firewall specialists).

text: 6.1 Minimum reliability

text: Applies to class 0 devices and higher

text: The typical examples are:

text:  In case of outage (power, network or simply the associated cloud services): o Provide the user with a notification o Provide smart fail-safe mechanism or standalone option (if an outage or denial of service happens, devices should be able to go offline, continue to provide their functionalities, and synchronize to remote services as soon as they become available again).  For network: use the diversity of available interfaces (including hardwired connections) or RF spectrum to maintain connection.  For power: use battery back-up and/or alternate charging options.

text: These methods are not exclusive and should all be regarded as good practices. Be careful however when providing interface redundancy, since it increases attack surface. Therefore, more interfaces will have to undergo a security assessment (see good practices on self-protection).

text: The hardware itself should be as reliable as possible. The strict requirements of safety-critical hardware cannot possibly apply to Smart Home, but it should be noted that even consumer-grade equipment comes with an estimation of the Mean Time Between Failures (MTBF) or the Annual Failure Rate (AFR). Be able

text: to monitor and/or advertise these notions should also be considered a good practice for reliability or availability.

text: In terms of security, the benefits of these availability and reliability measures are twofold:

text:  It provides a basis for robustness against jamming and denial of service attacks.  It gives confidence in security alerts: if a device does not behave correctly, it should be an indication of an attack, and not an accident. This is typically a requirement so that additional security controls can be performed on top of the device.

text: Software components of the Smart Home must handle data changes without failure, errors and improper functioning

text: Applies to class 0 devices and higher

text: Software reliability is more difficult to define and assess. This leads to assurance quality measures for which many standards and practices exist. While such measures could make sense in safety-critical software, the cost-to-benefit must be carefully balanced. These issues are out of scope of this study, which focuses on more basic good practices:

text:  The usage of standard frameworks or communication protocols.  The notification of users in case or errors, updates or possible compromising.  The implementation of event logging and security audit with forensic enablement in mind.

text: 6.2 Trust relationships

text: Using a trust infrastructure give assurance in heterogeneous environments where devices may enter or quit a given networks, and cannot necessarily be trusted by default. Smart Home is a good example of environments where trust is needed:

text:  between the devices; and  between the devices and remote services.

text: The former may be managed locally by a gateway, while the latter could be answered by dependable solutions such as:  A Public Key Infrastructure.  Mutual authentication schemes based on shared secrets.  Alternative schemes such as Identity-Based Cryptography (IBC) and Identity-Based Encryption (IBE).

text: All these solutions have limitations and vulnerabilities, and should be implemented with these issues in mind.

text: The following are some examples of key limitations and vulnerabilities:

text:  A PKI may be complex to administer and maintain, especially when used by a fleet of heterogeneous devices. Revocation mechanisms and multiplicity of authorities add complexity to the infrastructure. Since several possibilities exist, manufacturers and service providers need to understand the security implications of operating a PKI either directly or via a third-party provider.  Some devices in Smart Home use cases may not be able, for performance reasons, to perform public key cryptography, which is required for most all these schemes. Even a scheme based on pre-shared secrets might use public-key cryptography, for example to enable the renewal of preshared secrets, or their revocation if they have been compromised.  A trust infrastructure is notoriously easy to be implemented wrong, especially for non-specialists. This could lead to vulnerabilities in many devices, giving a false sense of security to their users. For example, even with a complex PKI, vendors are sometimes forced to define additional security measures such as certificate pinning or the use of pre-shared keys. 135 136  History shows that the lack of a proper user interface emphasizes PKI-related vulnerabilities.  Amongst alternative schemes, IBE/IBC schemes were the subject of several research activities in the recent years and claim a much simpler infrastructure than PKI. The practical gap between IBE/IBC and PKI, however, might be smaller than advertised. Eventually IBE might also come with equivalent limitations or vulnerabilities. We did not find evidences of applications of such schemes in Smart Home. However, some research projects are applying it to smart grids.

text: The variety of means to establish trust has already been studied by many industry actors, and existing good practices could be used by Smart Home.

text: Using a trust infrastructure requires skills. Vendors without previous security experience are advised to get third-party support.

text: Use secure pairing for devices

text: A strength of Smart Home, when compared to other IoT use cases, is the fact that the end user has a physical access to all the devices. For this reason, secure pairing should also be considered as an additional measure to enforce trust relationships.

text: For example in Wi-Fi networks, WPS pairing can be securely achieved by a physical action (WPS onebutton-connect) while the PIN-based WPS is vulnerable to brute-force attacks.

text: The devices and services made assumptions to ensure that the security requirements are sufficient.

text: Users should be encouraged to check at installation time whether these assumptions are valid as well as the limitations in the usage of the device. For example, a devices using ZigBee connectivity to transmit security alarms might not be able to communicate properly when deployed behind a very thick wall.

text: Users should be invited to check that the installation conditions in their home allows the operation of all security functions.

text: 6.3 Network security

text: A gateway can participate in securing Smart Home Environments from internal and external attacks at network level.

text: HAN network security is a useful additional measure to device security. It can mitigate some device vulnerabilities, typically to ensure that data leaks on the HAN cannot “leave the HAN”, and symmetrically that internet threats do not enter the HAN.

text: Similar functions exist in house devices today. This approach is a logical evolution of these functions:

text:  The strong protection of the home Wi-Fi network is an example, provided vulnerable functions such as PIN-based WPS are not used.  Additional network protection, such as firewall Intrusion Detection System (IDS) or Intrusion Prevention System (IPS) capacities may be available from ISPs, device vendors or other actors (for example in SaaS service such as PC antiviruses). Collecting these data at a central point (e.g. in the gateway) enables network operators to detect certain attack scenarios remotely.

text: This solution leverages on the fact that the HAN contains high-capacity devices that “can be exploited to boost up the security of low-capacity devices by running on their behalf energy-hungry and complex security mechanisms.”

text: These device could notably be able to act as trust systems or facility, particularly for energy-hungry and complex functions such as key management.

text: Network segregation can ensure security for devices and services that have no reason to interact with each other. For that purpose:

text:  Constrained devices, such as sensors, should not have direct communication outside the HAN. They could rely on the Smart Home gateway or even the ISP’s set-top-box to manage long-range connections. This is particularly true for Class 0 devices that have no capacity to manage their own security.  The same logic can be applied between local networks. If devices can use a HAN which is different from the home Wi-Fi, there is a possibility for the HAN gateway to act as a firewall more efficiently. The use of VLAN might also be considered to segregate traffic type.  Wireless connections to the HAN should be performed by secure pairing.

text: Beware that segregation of networks is not a silver bullet: even a Bluetooth interface can be accessed from a relatively long-range with an adequate antenna. For this reason, these network protection measures are only additional measures over device protection functions.

text: Good practices for the usage until end-of-life

text: This section describes the good practices related to the device once it has been installed by the end-user until its disposal. These good practices consist in three different sets:

text:  Security good practices for the protection of data exchanges with networks accessible to the device.  Operation and maintenance of the security of the device with regards to new vulnerabilities and during device management.  Control of user data on the device.

text: 7.1 Protection of data exchanges

text: The Smart Home device may be interconnected with several networks. In case of an attack on the device or programming error impacting the network, some separation rules must be followed in order to limit the propagation to other networks.

text: Ensure access rights

text: Users shall verify the authorisations given to devices and services for data access and data exchange. This is particularly true in case of an update where access rights may be modified without user’s consent.

text: For example, devices and services can display a comprehensive view of their communications with external devices and services, their requirement to use private data, etc.

text: Applies to class 0 devices and higher

text: Local networks should be separated whenever possible. Each of these networks should be protected by a dedicated gateway (either because they consist of two different networks, or because they consist of two different VLANs managed by a gateway). For example:  The home Wi-Fi network will be protected by the ISP set top box. This network might include for example entertainment equipment or NAS devices.  The Home Area Network will be protected by the Smart Home hub or gateway.  The users might create ad-hoc networks dedicated to some devices. For example a Bluetooth network can include smart lightbulbs and smart locks on the one side and smartphones or tablets, which have access to mobile network, on the other side. To prevent attacks from the smartphones or tablets to the ad-hoc network, users should be encouraged to secure their smartphones and tablets, typically by securely configuring them (password, official application stores only) and using dedicated security applications (anti-virus, protection suites).

text: Smart Home devices in each of these networks have no reason to access devices in the other networks. Even if it were the case, access should be managed by the dedicated gateways.

text: Most of Smart Home devices in these networks have also no reason to access the WAN directly, especially since the home is very likely to be connected to an ISP. For this reason, devices should access the WAN only through their dedicated hubs or gateways. This is a significant difference between Smart Home and other IoT contexts, where sensors can be expected to have a direct LPWAN access.

text: The Smart Home gateways or hubs must implement network protection measures, as described in Section 6.

text: Some Smart Home devices have a direct access to WAN or LPWAN, for example alarms and surveillance cameras. In this case, the WAN or LPWAN access should not be used to enter the HAN. For this reason, these devices should access local network only through a secure gateway or hub.

text: Applies to class 0 devices and higher

text: Comply with the requirements and recommendations of the AMI gateway if a Smart Meter is installed.

text: While the security functions of the smart meters or smart energy gateways are out of the scope of this study, in some architectures the gateway to the Advanced Metering Infrastructure is used as an interface to the Home Area Network. To ensure correct operation of the AMI, Smart Home vendors should:

text:  implement the protection required by the smart gateway, if any; and  prevent disruption of service, for example causing denial of service by using too much bandwidth.

text: 7.2 Operational security and maintenance

text: Following the good practices described so far shall significantly reduce the risk of having vulnerabilities found in the product, however this risk can never be avoided. Vendors shall not only pro-actively perform a survey for new vulnerability but also provide a secure and reliable device update mechanism to allow fixing vulnerabilities.

text: 7.2.1 Vulnerability survey

text: Perform vulnerability survey

text: Once a device is on the market, the vendor must perform a vulnerability survey and fix security flaws accordingly. The vulnerability survey should include developer findings, on-line researches, CERTs advisories, as well as input from customers and security researches. The end-user must be informed of the support period of the device and of the end of support for security fixes.

text: A policy for vulnerability handling and disclosure awareness should be defined. Bug bounty programs 150 151 can also provide an incentive to third-party researchers.

text: Known vulnerabilities must be patched. A patch may consist of a workaround if the developer did not yet provide a fix. When over-the-air updates are not available, a plan for product recalls shall be considered, so that vendors can implement the patch in the devices.

text: For online services supporting Smart Home devices, a rollback to a secure state must be possible.

text: Eventually, vulnerabilities impacting user data should be communicated as transparently as possible. The EU Opinion 03/2014 on Personal Data Breach Notification from the

text: Article 29

text: Working Party gives examples of such situations.

text: The devices and services made assumptions to ensure that the security requirements are sufficient. Vendors and users should be encouraged to check regularly that these assumptions are still valid. For example:

text:  Limitations in the usage of the device (for example, a given device might need ZigBee connectivity to transmit security alarms, implying that it will not be able to send alarms when deployed behind a very thick wall). Vendors could discover that, in the field, the signal requires even stricter conditions (even thinner walls, no interference…). They will need to send users an information so they can check is their installation is secure.  Assumed properties of the environment (for example, assuming that the certification authorities in the certificate store are all trusted and not compromised). Vendors should perform a survey to be able to remove a compromised CA from the certificate store.  Assumed properties of cryptographic properties (for example, assuming that a given algorithm and key size are sufficient for a given task). Vendors will need to check regularly this assumption, for example if a new cryptographic attack puts users at risk unless they use longer keys or change their cryptographic suites.

text: 7.2.2 Security updates

text: Protect the software update mechanism

text: Applies to class 1 devices and higher

text: Security updates provide protection against vulnerabilities found during the life of a device or application. However this comes at a cost, since support of this functionality also provides an entry point for an attacker. In particular vendors should:

text:  Provide automatic and timely security updates.  Protect the updates (typically via encryption and digital signature). The update files must not contain sensitive data. The signature must be verified before the update is applied.

text:  Protect the application of an update on the device. An attacker should not be able to trigger a firmware installation without an authorization.  Protect the security update interface against attacks.

text: 7.2.3 Remote interfaces protection

text: The ease of use of the user interface must contribute to help users perform correct administrative tasks. Such interfaces can be found for example on the device itself, on a web portal or through a mobile application.

text: User-friendliness helps maintaining a secure state on the device by:

text:  Giving more chance that simple actions such as firmware update or password changes are effectively performed by the user.  Providing an accurate description of the security status of the service, and explaining what actions can contribute to mitigate potential threats.

text: Vendors and service providers should also raise their users’ awareness about infected e-mails and hoaxes.

text: Protect remote monitoring interfaces

text: Protection of remote monitoring interfaces is crucial since they often provide a highly-privileged entry point into a device. This protection includes access control and authentication mechanisms, as described in good practices on Identification, authentication, authorisation.

text: 7.2.4 Security management system for support infrastructures

text: Regarding the requirements for remote infrastructures related to Smart Home, there is no specific needs in the Smart Home use case compared to usual cloud services or usual device support infrastructures.

text: For this reason, the main recommendations would consist of:

text:  Security management: As a general rule, implement an information security management system (ISMS) as described in the ISO 27001. ENISA recommendations apply.  Secure development: as a general rule, follow the recommendations issued by OWASP, especially (but not limited to) the following: o Top 10 project. o Testing project. o Web Testing Environment Project. o Application Security Verification Standard Project. o Software Assurance Maturity Model.  Security assessment: we recommend that service operators: o Ask for third-party audits on their infrastructures (such audits may be part of an ISO 27001 certification).

text: o Ask for third-party penetration testing of their services, including at least a network scan and if possible, manual penetration testing.

text: Regarding Cloud computing, service providers should consider certification following ENISA recommendations.

text: 7.3 Control of user data

text: Provide secure backup and/or deletion of the data stored/processed by the device (and by associated cloud services) during the operation and at end-of-life

text: The end-user must have a way to securely erase its private data collected by or stored on a Smart Home device.

text: More generally, a secure factory-reset of the firmware and configuration should be available on the device.

text: For client information in remote infrastructures such as cloud services, data sanitization must be in place.

text: For user data present on devices, secure deletion of encryption keys may provide enough protection, assuming that data is encrypted in conditions that guarantee long-term confidentiality (see good practices on Cryptography).

text: Metadata should be erased the same way as other sensitive data, since the same threat apply (see good practices on User data protection).

text: Recommendations

text: 8.1 All stakeholders should reach a consensus on minimum security requirements

text: This recommendation is mainly intended for vendors and service providers, national cybersecurity agencies, consumer groups, standardisation bodies and/or industry associations

text: This study identified several groups of good practices related to Smart Home Environments. For some of these topics, dedicated security standards or initiatives already exist.

text: It is important that all stakeholders involved reach a consensus on good practices in order to build a widely accepted set of requirements for Smart Home. By relying on national cybersecurity agencies and consumer groups on the one hand, and standard groups and industry associations on the other hand, the Industry can converge toward a unique set of minimum security requirements.

text: These minimum security requirements should target the whole ecosystem of a Smart Home: interconnected devices, services and networks. They could be tailored for IoT or specifically for Smart Home Environments and should target specific IoT security concerns, beyond the usual security requirements (for example related to web security).

text: The objective of this recommendation is also to clarify which Smart Home specific strengths can be leveraged upon to provide efficient security functions, in particular for devices related to health and safety and devices with low capacity (class 0 and class 1).

text: A consensus can also be a first step for industry associations and standards groups to build compliance tools, such as a testing guides. Industry associations and standard groups could therefore define requirements with compliance testing in mind.

text: 8.2 Industry actors should support security-driven business models

text: This recommendation is mainly intended for vendors, policy makers, industry groups and consumer associations

text: Smart Home, at least in its consumer-market part, is mainly cost-driven. As a consequence, functionalities usually has priority over security for both vendors and end-users. This leads to an increase of vulnerabilities, with increased security concerns that can have an impact on the Home and its inhabitants as it happened recently in the automotive domain.

text: It is recommended that security becomes a requirement for all products and services that have an impact on user’s life and safety.

text: For that purpose, vendors and policy makers should understand their users’ expectations of safety, security and privacy. They should propose a secure version of their products or even integrate security in their product by default.

text: Consumer associations should raise the issue and discuss with industry groups to provide requirements on “secure options”, and how “secure” and “non-secure” options should be advertised so as to provide a fair information to the consumer. An incentive could be to assess the costs of security against the costs of liabilities of an insecure product.

text: 8.3 All actors should contribute to raise security awareness

text: This recommendation is mainly intended for vendors, consumer associations and national cybersecurity agencies

text: Security awareness is especially needed since end-users integrate devices and services to control their Smart Home, with a potential impact on their life and safety.

text: Vendors’ awareness

text: IoT vendors shall keep track of vulnerabilities in other IoT products, especially in the context of Smart Home Environments. For that purpose, vendors can hire or train security experts to understand security vulnerabilities in IoT, as they can only get worse with a wider adoption of the products. It is also important to consider early warnings on security issues provided by users and researchers, as they contribute to reducing the attack surface on devices and services.

text: By raising the awareness level of IoT companies to security, product security will be improved and vendors will reduce the threats they face and associated reputation issues. It is particularly true for vendors with limited experience in security.

text: Users’ awareness

text: Users have a de facto responsibility on the security of their devices and services connected local networks, yet they may not be aware of that fact. Consumer associations and/or cybersecurity agencies can raise user awareness by providing user support and guidance on several topics such as:  How to choose a Smart Home device  How to operate a Smart Home device  How to control online services etc.

text: Vendors should also contribute to this awareness by explaining clearly how to properly configure their devices, the security properties available and the consequences of an insecure configuration.

text: In this context, vendors as well as consumer associations might contribute to establish user guidance (see for example Annex D: Example of topics for user awareness).

text: 8.4 Industry actors should develop security assessment methods or frameworks

text: This recommendation is intended for industry associations, the European Commission and its Member States,

text: national cybersecurity agencies, standardisation bodies

text: The security of IoT in Smart Home Environments depends on several constraints not covered by existing security assessment methods or framework. It is important to understand how Smart Home devices, regardless of the regulation, will not be able to resist cyber-attacks which can originate from inside or outside the Home.

text: For that purpose, industry associations, the European Commission and its Member States (for example through their national privacy agencies) should define rules to ensure the level of security of a given product. Such security assessment method could be targeted at manufacturers, vendors and/or end-users.

text: It is recommended that such security assessment method combines and adapts existing work such as:

text:  Whitelisting or certification of vendors.  Integration of multiple levels of assurance to counter attack with different impact  Defining the rules for security audit and testing (e.g. self-assessment, third party assessment, certification…)

text: It is also recommended to collaborate with CERTs or external third-party to demonstrate resistance to existing attacks using at minimum well-known/public vulnerabilities assessment as well as black-box vulnerability testing campaign or a code/configuration review. Enhanced security assessment could integrate product-specific vulnerability assessment as well as grey- or white-box vulnerability testing campaign and/or a fuzzing campaign .

text: Note that manufacturers and developers with limited experience in security are strongly encouraged to rely on:  Security researchers (academics) or private evaluation facilities, that have the skills to perform these tasks.  National cybersecurity agencies or industry associations, that are able to clarify the expected effort and methods for these tasks.

text: 8.5 Policy Makers should clarify the legal aspects of Smart Home Environments

text: This recommendation is intended for: policy makers from the European Commission and in its Member States

text: A compromised Smart Home component could have a severe impact in terms of security, privacy and safety in many cases (smart locks, thermostats, smoke or CO2 detectors…). Technical measures could address a good part of such risks. However, their adoption might be expensive and there is no clear incentive to naturally regulate vulnerable solution. Hence, it is important to define liabilities through policy.

text: For that purpose, Policy makers should clarify the liability issues related to Smart Homes by defining:

text:  The liability of industry players in cases of damages or injury, if a compromised device fails to meet its safety goal.  The liability of industry players whenever a private data breach occurs.

text: Moreover, the European Commission and Member States should clarify:  How long companies should be liable for fixing known vulnerabilities.  The liability of companies not disclosing, and not fixing, potential vulnerabilities.

text:  A legal framework for disclosure of vulnerabilities by academics or private-sector researchers knowing that: o Companies should be able to have enough time to fix vulnerabilities before a disclosure is made. o On the other hand, a company should not be able to prevent or limit the disclosure of a vulnerability (not being public does not prevent a vulnerability to be found and exploited by several actors). This should be a requirement especially when a company does not provide fixes or workarounds to mitigate the associated threat.

text: Note that liability could provide an incentive to implement security correctly, as it is already a part of the CE marking process (in case of damages or injuries). Yet, several risks and limitations that should be avoided to limit financial risks, unfair situations to smaller players, and the scope of application.

text: 8.6 Industry research and publicly-funded initiatives should integrate cyber security in R&D projects related to Smart Home and IoT

text: This recommendation is mainly intended for vendors, academics, and policy makers which fund research

text: While many good practices are already available for Smart Home vendors to implement security, some of them have limitations or could be improved.

text: The European Commission and its Member States (MS), research and development competent authorities in cooperation, the Academia and R&D sector should develop incentive to integrate cyber security in existing research programmes, such as FP7 and Horizon 2020.

text: Moreover, projects managers should:  Define which part of their project needs to consider cyber security.  Evaluate security requirements that shall cover identified cyber threats.  Explain to which extent their project integrates cyber security.

text: For research and development projects focusing purely on security, current research indicates new mechanisms that could provide additional protection (for example Anonymous signatures or 169 170 171 authentication, homomorphic encryption or secure multiparty computation.) These project should contribute to securing Smart Home Environments (for example, by defining trust relationships within heterogeneous home networks, by overcoming the issues of class 0 or class 1 constrained devices…)

text: Annex A: Additional details on Smart Home Environments

text: Communications

text: As presented in Figure 4, Smart Home devices include a very high number of communication means:

text:  Direct or short-range communication is used within the home  Long-range communication is used to access the remote services associated with the devices, and is also present due to the existing connectivity in the home.

text: A.1.1 Technologies

text: Smart Home devices typically have one or several interfaces to different ranges of communication. They can use direct communications with other devices (that may be Smart Home devices or personal computers, smartphones…), ad-hoc and multi-hop communications.

text: Short range communication on the Home Area Network

text: Short range communications include both low speed Personal Area Networks (PAN) using and high speed networks. They can implement wireless or wired connections.

text: Wireless protocols vary from standards such as 6LowPAN, Zigbee, Bluetooth or Wi-Fi, but also proprietary protocols such as Z-Wave or EnOcean.

text: Wired connections include Ethernet, Fiber optics, Powerline Communication or telephone wires.

text: Long range communication over a Wide Area Network:

text: For long-range communications and Internet connectivity, devices can rely on their own connectivity or use a gateway be it the Smart Home gateway or a smartphone.

text: WAN communications are possible at low speed through Low-Power Wide-Area Networks (LPWAN), with approaches such as LoRaWAN (often abbreviated into LoRA), Ultra Narrow Band (e.g. SigFox) and many others such as LTE-MTC, NWave…

text: High speed WAN communications may also be available using Internet through a gateway or a set-top-box, a direct 4G/LTE connectivity…

text: A.1.2 Protocols

text: On top of these communication technologies, devices implement several higher-level protocols, some of them being dedicated to IoT. For example, the following protocols are used in various contexts:  Messaging protocols with a many-to-many approach o Example: MQTT (adapted into MQTT-SN, for non TCP/IP protocols such as ZigBee).  Webservice protocols, or document transfer protocols, with a client-server approach o Example: HTTP for TCP/IP protocols. o Example: CoAP (initially built for UDP protocols).

text: A.1.3 Security

text: The usage of dedicated security mechanisms varies depending on the solution used. Several approaches are taken, from the transport to the applicative layer: o User authentication/authorization protocols such as Oauth / OpenID, XACML/SAML Single sign-on etc. o Communication protection protocols such as SSL/TLS over TCP/IP, or DTLS over UDP. o Usage of cryptographic algorithms to secure transport layer is found amongst many of the communication protocols.

text: Platforms

text: A Smart Home platform integrates a set of:  Hardware.  Operating System.  Additional software (e.g. communication stacks).  Related remote services (e.g. analytics, device management or provisioning).

text: While the platform includes all these elements, it has to be noted that in many cases there are different providers for these parts. Typically low cost devices can be built upon cheap Hardware, using one of the many open source OSes available (TinyOS, Contiki, FreeRTOS, Mantis OS, Nano-RK, LiteOS…).

text: The environment of the platform is:  The service infrastructures providing the remote services and their applications.  The networks (both the HAN and the WAN) and the objects attached to it:

text: o Objects attached to the HAN such as smartphones, tablets or PCs. o Other Smart Home platforms. o Other actors, for example web services, accessible through the WAN.

text: It has to be noted that devices may enable privileged pairings with any of these elements. For example:  A smart lock can be paired with the user’s smartphone.  A smart hub is intended to be paired with the other Smart Home devices.  A smart TV can be paired with third-party cloud services such as entertainment providers, or social networks.

text: Annex B: Mapping threats with good practices

text: The threats of the ENISA threat landscape are mapped to good practices in Table 2 in order to highlight specific countermeasures. The good practices are associated to the lifecycle of devices and services in Smart Home Environments.

text: Some threats were merged for readability reasons, and some threats were not mapped to good practices: this does not mean that the threats are not applicable to the Smart Home use cases, but only that these threats will have to be considered after a first set of good practices are already in place.

text: The Several good practices are generally not included in the table, because they are implicitly used by most of the security functions. These good practices are:

text:  Logs and audit measures must cover, and contribute to, all the security functions.  Cryptography is the basis of most security functions.  User should be notified whenever security is at risk.

text: However, in some cases they are included in the mapping hereafter, mostly when they are considered as the main security countermeasure to a given threat.

text: Legal Nefarious Activity/Abuse Eavesdropping / Interception / Hijacking Physical attacks Dependability and reliability

text: Disasters and outages

text: Unintentional damages (accidental)

text: Damage/Loss (IT Assets)

text: Failures / Malfunctions

text: Annex C: Checklist of good practices

text: Table 3 proposes a checklist of good practices and their application to remote services and devices classes. Stakeholders can use this table for example in their risk assessment to cross-check which good practices applicable to secure their devices and services.

text: The application of good practices to devices classes and remote services is denoted by the following icons:

text: 0+ 1+ 2+ GOOD PRACTICES FOR THE DEVELOPMENT OF SMART HOME DEVICES AND SERVICES APPLIES TO 1+ 1+ 1+ 0+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 2+ 2+ 1+ 2+ 1+ 1+ 1+ Good practices for the integration of devices in the Home Area Network APPLIES TO 0+ 1+ 1+ 1+ 1+ 1+ Good practices for the usage until end-of-life APPLIES TO 0+ 0+ 0+ 0+ 0+ 1+ 1+ 1+ 1+

text: Annex D: Example of topics for user awareness

text: This annex presents an example of possible actions to perform in order to:

text:  Choose a Smart Home device securely  Operate a Smart Home device securely  Use online services for Smart Home securely

text: Annex E: List of Acronyms

text: ENISA

text: European Union Agency for Network and Information Security Science and Technology Park of Crete (ITE) Vassilika Vouton, 700 13, Heraklion, Greece

text: Athens Office

text: 1 Vass. Sofias & Meg. Alexandrou Marousi 151 24, Athens, Greece

text: PO Box 1309, 710 01 Heraklion, Greece ISBN: 978-92-9204-141-0 doi:10.2824/360120 Tel: +30 28 14 40 9710 info@enisa.europa.eu www.enisa.europa.eu