Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Edge Computing Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Chapter 6: Edge Security and Privacy
(section)
Page
Discussion
British English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Upload file
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== IIOT (INDUSTRIAL IOT) IN MANUFACTURING=== The production floor of a manufacturing company has integrated an IIoT system that is edge- based. Sensors associated with the machinery connect to edge gateways that track the health of the equipment for predictive maintenance. One extreme incident involved the main assembly robot producing inaccurate sensor readings that were altered, driving the robot to malfunction and claim weeks of expensive downtime on production. This revealed the insertion of an unauthorized device, a small single-board computer that was disguised as a sensor node and which fed erroneous data back to the control system. ====CHALLENGES:==== Even though it was optimized for efficiency, the factory edge network didn't include a device authentication protocol; attackers could access new sensors without the need for tight controls. Ensuring up time and keeping operational was prioritized often at the expense of timely application of security updates. Moreover, the presence of devices from many vendors further complicated efforts to establish consistent security standards, and production engineers received little training in cybersecurity best practices. ====SOLUTIONS IMPLEMENTED==== To solve these problems, stringent onboarding procedures were put in place: each sensor or controller must now present a digital certificate signed by the organization before being allowed onto the network. Any unknown device attempting to gain access is rejected and notification alerts are immediately sent out to ensure the remedying of bogus sensors does not take place in future. Additionally, they created a blockchain ledger to monitor device identities and to log any configuration changes over time. Every new addition or firmware update triggers a blockchain transaction being recorded to guarantee the creation of an immutable audit trail that can be reviewed by IT as well as OT (operational technology) teams increasing trust and accountability between departments. They segmented their network by listener and gateway: your sensors only talk to local gateway, and then your gateway only talks to central controls understanding that if any one part is breached there are limitations to how much of your network is attacked. More importantly, they rolled out an AI-powered detection system that monitored sensor readings for abnormalities. For known rogue sensors where outputs were statistically different from expected machine behavior; it is likely that ML models would have picked up on this irregularity early enough to allow for preemptive safety shutters before doing damage.In addition, maintenance processes were revised to ensure that scheduled downtimes were regular intervals of time explicitly dedicated towards security (for example, patching software vulnerabilities and routine equipment calibration checks). Training of staff on basic cyber hygiene such as ensuring that a USB drive or laptop was validated before connecting it into the organization edge networks have reduced the threat of the organization network being infected by malware. ====OUTCOME==== Then after enhancements made at this facility had enabled quick identification of anomalies; The next, an internal attempt by someone trying to connect using unauthorized monitoring tools was quickly detected and blocked ensuring nothing could affect operations in our pursuit against cyber-physical threats going forward. This includes how to properly secure our edges given their unique properties tightly coupled with how data generation happens right at the host itself which underlines an edge rather than left assume by further maintaining data access principles and protocols as logs have significantly aided audits of compliance as well being fitted into our own investigation processes during incidents reducing times taken before identifying potential problems where an immutable changelog was adapted into the process itself. Key Takeaways β Smart cities & IIOT factories share common challenges yet demonstrate needs for customized solutions & technologies but also show similar trends including segmentation, authentication continuous supervision Reacting quickly overcoming new challenges through advanced technology tools - Artificial Intelligence& Blockchain technologies just to name a few.
Summary:
Please note that all contributions to Edge Computing Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Edge Computing Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)