Slides are attached, Q&A is listed below the video.
The first time I became aware of possible IoT issues was the "Ripple20" demonstration (TCP/IP) stack deep inside (never changing) parts of "unsuspicious" un-patchable hardware devices
Ripple 20 is just one example. you can look on recent discovered TLStorm and TLStrom 2.0 as well.
How is Check Point Protected loaded onto the firmware of the IoT device?
The device manufacturer must integrate our Nano Agent into the firmware of the device. It is not something an end user can integrate on their own.
Do you keep a list of the manufacturers that have decided to integrate Check Point Protect into their IoT devices?
The public ones are listed on our website.
What you are doing for camera should be possible for energy meter also. are the threat vectors similar? Are you doing this with any OEM of Energy Meters?
You are correct. We are having conversations with manufacturers of Energy meters at this moment and we will start a POC with one of them very soon.
You say we identify the attack no matter where it happens, does this include BlueTooth?
We are looking for specific known malicious techniques and tactics which should also apply to Bluetooth as well, if the device has it,
In the latest R81 revisions for CKP customers are you looking to implement default IoT policy rules so IoT objects can have this threat prevention policy applied once they have been added as network objects?
What you're describing is different functionality than we discussed here today. That said, we are working on this sort of functionality separately.
Are you able to provide a vendor integration roadmap?
Contact us and we can explain the process for integrating our Nano Agent.
If you buy a CP certified protected IOT device from a vendor and you already have a CP manager is it possible to get the logs from the device?
Theoretically, yes, but it is up to the device manufacturer to provide that.
How does the Armis integration figure into this discussion?
Armis integration is related to network protection, which was not discussed as part of this session.
