New ISO27k domotics security standard

ISO/IEC 27403 "Cybersecurity – IoT security and privacy – Guidelines for IoT-domotics" was published at the very end of last month.

“Domotics” is a neologism for smart homes.

This new standard covers the cybersecurity and privacy aspects of thing-to-thing interactions (e.g. home hubs and entertainment subsystems) as well as human-to-thing plus thing-to-sensors/actuators that physically interact with the home (e.g. smart door locks and thermostats) and networking both within the home (e.g. WiFi, Bluetooth) and beyond (e.g. fibre or wireless broadband).

The standard is aimed squarely at guiding the designers, manufacturers and security or privacy assessors of IoT domotics, as oppoed to retail customers and users. It provides examples of information risks that should (in theory at least) have been identified, evaluated and addressed by IoT suppliers baking-in suitable security controls to protect their valued customers' interests. In reality, how much security and privacy do you really expect from cheap and shoddy things in such a highly competitive and short-term-focused market?

Consumers who are as smart as their IoT things may be intrigued and concerned by the security and privacy implications of the streams of information now flowing freely around their homes and vehicles.

Furthermore, things are also increasingly invading our workplaces, not least because we wage-slaves are wearing or carrying them in through the front door every morning. Who doesn't have a smartphone or watch these days? Some of us may even be 'concealing' them internally: smart implants are both a thing and things.


Before those information streams become rivers and we find ourselves plunging headlong into the seething white water rapids in a flimsy inflatable, take a moment to ponder the information risk, security and privacy challenges ahead ... and hopefully plot a relatively safe route around the semi-submerged boulders and whirlpools.

The standard is sold through the national standard bodies, or direct from ISO and IEC.

Popular posts from this blog

Pragmatic ISMS implementation guide (FREE!)

Image
Early this morning ( very  early!) I remotely attended an ISO/IEC JTC 1/SC 27/WG 1 editing meeting in London discussing the planned revision of ISO/IEC 27003:2017 . Overall, the meeting was very productive in that we got through a  long  list of expert comments on the preliminary draft standard, debated the objectives of the project and the standard and reached consensus on most points. In summary: 27003 is to be revised to align with the current 2022 releases of ISO/IEC 27001 , 27002 and 27005 : These changes are  mostly  minor aside from the new section 6.3 on ISMS changes.
Read more

Two dozen information risks that ISO forgot

Image
Selecting the wrong controls - controls that are inappropriate, ineffective, too costly, impracticable, fragile, unnecessary, counterproductive or whatever, often as a result of blind faith in fads and fashions of the day and FOMO e.g. MFA, AI, cyber Failing to select the right controls - controls that are ideal for the particular situation, both now and in perpetuity, for whatever reason - mostly ignorance and prejudice Selecting and implementing controls at the wrong time or in the wrong way (where 'wrong' includes ineffective, inappropriate, sub-optimal e.g. bolting on controls rather than designing and building them in) Inept and inaccurate identification, analysis and quantification of risk, including reliance on p oor quality (incomplete, inaccurate, out of date, misleading, unreliable ...) information about actual risks, particularly subtle and emerging risks plus those involving deliberate concealment and misdirection e.g. fraud, misinformation, disinformation, propagan
Read more

ISMS internal audit priorities

Image
A thread on the ISO27k Forum sparked my imagination over coffee this morning. Hope had previously asked for assistance with an ISO/IEC 27001:2022 audit plan.  Bhushan offered a lengthy and generally sound response explaining how to use a spreadsheet with tabs to plan and record the audit work performed on 100% of the main body clauses and 50% of the 93 Annex A controls, day-by-day. That's OK ... except it wasn't entirely clear that he was interpreting and elaborating on the standard's actual requirements. ISO/IEC 27001 does not explicitly require, for example, that (as Bhushan stated) "ALL the management system clauses from 4 to 10 AND their sub-clauses need to be listed and audited" in an ISMS internal audit, although evidently he interprets it in that way. In clause 9.2.1, the standard states a requirement for internal audits to provide information on whether the ISMS conforms to the organization’s own requirements for the ISMS plus the requirements of the stan
Read more