A suite of encryption tools for use with Flowcode
Posted: Mon Aug 24, 2020 5:14 pm
I direct this request primarily to the Matrix team, to ask if Matrix would consider creating suite of encryption tools for use with Flowcode. The purpose is to provide secure communications for IOT and other types of interconnected projects.
Secure communication has already become a fundamental design requirement for any new IOT product development in the commercial world and there is a similar need developing within the hobby and maker fields. The use of external connections via WiFi or Ethernet inevitably exposes the connection and the associated network(s) to the risk of cyber-attack and all its potential consequences.
Apart from its obvious educational value, Flowcode is positioned as a tool to assist with the rapid development of embedded applications and SCADA systems and to have a range of secure communication components with in-built encryption based on peered reviewed, open source protocols continues to fit with this ethos.
In fact, I would argue that without it, the future potential of Flowcode could be artificially capped. By this I mean that the compelling need to incorporate secure communications is likely to drive engineering to use other programming languages that support more readily, the porting of open source encryption libraries.
To address this, I was thinking that Matrix could offer;
a) A suite of communication components with inbuilt encryption based on open source peer reviewed protocols for use in a future version of Flowcode.
b) An informative application guide – Effective secure communications requires the implementation of a range of procedural mitigation measures in addition to the hardware/firmware.
c) A related training module – There is definitely a need to educate our young future engineers in the art of implementing secure communications, as it is now and will continue to be a key requirement for all new ‘interconnected’ product development.
Matrix will likely need to draft in specialist resources to deliver these items and such the Matrix products will need to be additional ‘purchased’ options that enhance the standard Flowcode package. These features will also need periodic review and update, but I suspect those using Flowcode for education and the development of commercial use code, will welcome and embrace these options.
I am aware of the thread linked below, but recognising that designing secure communications is way beyond the capability of the average Flowcode user and indeed Matrix’s target audience, you really need to offer a robust 'turn key' solution.
viewtopic.php?f=65&t=18641&p=100568&hil ... on#p100568
I therefore ask if Matrix can seriously consider creating a sustainable business model able to deliver the above.
To help Matrix get an idea of the potential interest, I also ask forum users to indicate their support or otherwise, for the need of Flowcode to offer a ‘secure communications’ option.
Kind regards
Martin
Secure communication has already become a fundamental design requirement for any new IOT product development in the commercial world and there is a similar need developing within the hobby and maker fields. The use of external connections via WiFi or Ethernet inevitably exposes the connection and the associated network(s) to the risk of cyber-attack and all its potential consequences.
Apart from its obvious educational value, Flowcode is positioned as a tool to assist with the rapid development of embedded applications and SCADA systems and to have a range of secure communication components with in-built encryption based on peered reviewed, open source protocols continues to fit with this ethos.
In fact, I would argue that without it, the future potential of Flowcode could be artificially capped. By this I mean that the compelling need to incorporate secure communications is likely to drive engineering to use other programming languages that support more readily, the porting of open source encryption libraries.
To address this, I was thinking that Matrix could offer;
a) A suite of communication components with inbuilt encryption based on open source peer reviewed protocols for use in a future version of Flowcode.
b) An informative application guide – Effective secure communications requires the implementation of a range of procedural mitigation measures in addition to the hardware/firmware.
c) A related training module – There is definitely a need to educate our young future engineers in the art of implementing secure communications, as it is now and will continue to be a key requirement for all new ‘interconnected’ product development.
Matrix will likely need to draft in specialist resources to deliver these items and such the Matrix products will need to be additional ‘purchased’ options that enhance the standard Flowcode package. These features will also need periodic review and update, but I suspect those using Flowcode for education and the development of commercial use code, will welcome and embrace these options.
I am aware of the thread linked below, but recognising that designing secure communications is way beyond the capability of the average Flowcode user and indeed Matrix’s target audience, you really need to offer a robust 'turn key' solution.
viewtopic.php?f=65&t=18641&p=100568&hil ... on#p100568
I therefore ask if Matrix can seriously consider creating a sustainable business model able to deliver the above.
To help Matrix get an idea of the potential interest, I also ask forum users to indicate their support or otherwise, for the need of Flowcode to offer a ‘secure communications’ option.
Kind regards
Martin