{"id":8656,"date":"2020-06-23T07:56:56","date_gmt":"2020-06-23T07:56:56","guid":{"rendered":"https:\/\/www.experfy.com\/blog\/?p=8656"},"modified":"2023-12-04T09:07:41","modified_gmt":"2023-12-04T09:07:41","slug":"security-of-iot-devices-ways-to-protect-yourself-part-2","status":"publish","type":"post","link":"https:\/\/www.experfy.com\/blog\/iot\/security-of-iot-devices-ways-to-protect-yourself-part-2\/","title":{"rendered":"Security of IoT Devices: Ways to Protect Yourself. Part 2"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

It\u2019s never late to become safe. As technology penetrates our lives and business deeper and more profound each day, so do risks associated with adopting hi-tech innovations. The Internet of Things (IoT) encomapses a wide range of smart devices, but they are not as intelligent as we would like them to be when it comes to cybersecurity. Check out what we\u2019ve got to say on this issue.<\/em><\/strong><\/p>\n\n\n\n

In our previous articles (they are here<\/a> and here<\/a> if you haven\u2019t read them yet) we covered some general issues of IoT device security and what measure should be taken to secure them, including blockchain and certification. Moreover, we compiled a general overview of actions each party involved in implementing IoT projects can take for a safer IoT world. Now let\u2019s study it in more detail.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Everybody Counts<\/strong><\/h2>\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

We may roughly single out the following main characters in the game called \u201cYour IoT Project\u201d \u2014 manufacturers\/integrators of IoT devices, IoT solution\/software developers, IoT solution deployment specialists and IoT solution operators (users). Of course, this list may be expanded but we wouldn\u2019t be able to cover each and every aspect so we tried to focus on the most crucial ones. What can you do to secure Your IoT devices? Let the game begin!<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Compliance with the minimum requirements for equipment<\/strong><\/em><\/h3>\n\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

It is best if equipment contains a minimum amount of components necessary for its functioning, and nothing more. For example, you should add USB ports only if they are needed for the device to operate. Additional components open up new spots and pathways for attacks on the device and it\u2019s obvious that we should minimize such chances.<\/p>\n\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

\n

Protection of equipment against unlawful modifications<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

You\u2019d better develop procedures to identify opportunities for unlawful physical alterations, such as a loose device cover or removal of a device component. These signals pointing out to illegal penetration into the system can be sent in a data stream to the cloud, thus warning operators of these events.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Development of the solution based on secure equipment<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

If your budget allows, you can introduce additional security features, such as secure encrypted storage, or boot functions based on a Trusted Platform Module (TPM). These features enhance security on IoT devices and help protect the entire IoT infrastructure.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Secure updates<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n\n

It is inevitable but firmware will be updated throughout the operational life of the device. The development of secure update methods and the cryptographic reliability of firmware releases will ensure the safety of devices during and after the update.<\/p>\n\n\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Safe software development method<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

When developing protected software, you need to carefully consider how to secure IoT devices at all stages \u2014 from creating the project to its implementation, testing and deployment. The method you finally choose determines platforms, languages \u200b\u200band tools you\u2019ll be utilizing. The secure application development lifecycle provides a step-by-step procedure to create secure software.<\/p>\n\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

\n

Caution with open-source software<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

This type of software accelerates the solution development process in general. However, if you opt out for this variant, you should take into account the level of community engagement in relation to each such component. If the community is active, it guarantees adequate software support and troubleshooting. Vice versa, if you use a project based on open-source software characterized by low activity and little notice, you will most likely experience lack of support, with problems left unidentified.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Caution with integration<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Many vulnerabilities in the software protection system can be found at the border crossing between APIs and libraries. The functionality that is of no importance for the current deployment may still be available at the API level. To ensure the security of the entire system, be sure to check that all interfaces of integrated components are free from vulnerabilities and weak spots.<\/p>\n\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Secure equipment deployment<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The situation may be that you\u2019ll need to deploy your IoT devices in insecure locations, such as public spaces or locations with no monitoring. In this case, you should enable the utmost protection of deployed equipment from illegal modifications. If your equipment has USB or other ports, make sure they are securely covered, since they can be used as entry points for cyberattacks as well as physical alterations.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Secure authentication keys<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

In the process of deployment, each device requires device identifiers and associated authentication keys that are usually created by the cloud service. These keys should be stored in a physically secure location even after the deployment is over. A malicious device can use any compromised key to disguise itself as a device currently in operation.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

\n

System updates<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

Your OS and all device drivers must be updated to the latest version. For example, Microsoft automatically updates Windows 10 (Internet of Things or other SKUs) if the corresponding option is on. This may be the best way to secure IoT devices. Consistent upgrading of other operating systems, such as Linux, also helps protect them from malicious attacks.<\/p>\n\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

\n

Protection against malicious activity<\/strong><\/em><\/h3>\n\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

If possible, install the latest anti-virus and anti-malware programs into the operating system of each device. This will help eliminate most of the external threats. Most modern OSs provide users with the opportunity to take timely and adequate measures and potential risks long before it even arises.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

\n\n

Frequent audit<\/strong><\/em><\/h3>\n\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

To respond to security issues, you should first and foremost carry out an audit of the IoT infrastructure for security incidents. Most operating systems have built-in event logging. They should be reviewed on a frequent basis to ensure there are no security breaches. Audit data can be transmitted as a separate telemetry data stream to the cloud service for further analysis.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

\n

Physical protection of the IoT<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

The easiest security attacks on the IoT infrastructure occur through physical access to devices. It is of paramount importance to protect USB ports and other physically accessible components from malicious attacks. One of the key factors in detecting breaches is maintaining physical access logs, e. g. when using USB ports.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

\n

Protection of cloud credentials<\/strong><\/em><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

Cloud authentication credentials used to configure and operate an IoT project are probably the easiest way to access an IoT system. To ensure the functioning of IoT device security solutions, you should change your password on a recurrent basis and avoid using credentials on public computers.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

\n

On a final note<\/strong><\/h2>\n\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n\n

Functional capabilities of all those different IoT devices vary drastically. Some devices may be represented by computers with standard desktop operating systems, while on some devices a very simplified operating system can be installed. The above safety recommendations may apply to these devices all at once or to some of them only, depending on the degree of complexity. We would strongly recommend to apply additional deployment and security recommendations provided by the device manufacturer (if any).<\/p>\n\n\n\n

Some legacy and limited devices may not be designed for IoT deployment. They may not be able to encrypt data, connect to the Internet, or provide advanced audit tools. To ensure the security required when connecting such devices to the Internet, field gateways should be used when compiling data from legacy devices. The field gateway provides secure authentication, negotiation of encrypted sessions, receiving commands from the cloud, and other security features.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

It\u2019s never late to become safe. As technology penetrates our lives and business deeper and more profound each day, so do risks associated with adopting hi-tech innovations. The Internet of Things (IoT) encomapses a wide range of smart devices, but they are not as intelligent as we would like them to be when it comes to cybersecurity. Check out what we\u2019ve got to say on this issue.<\/p>\n","protected":false},"author":687,"featured_media":8657,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[195],"tags":[127,287],"ppma_author":[3479],"class_list":["post-8656","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-iot","tag-cybersecurity","tag-iot"],"authors":[{"term_id":3479,"user_id":687,"is_guest":0,"slug":"denis-novikov","display_name":"Denis Novikov","avatar_url":"https:\/\/www.experfy.com\/blog\/wp-content\/uploads\/2020\/04\/medium_33a1908b-a1b9-4f02-907d-66acf1825947-150x150.jpg","user_url":"https:\/\/www.qulix.com\/","last_name":"Novikov","first_name":"Denis","job_title":"","description":"Denis Novikov is Deputy Director of Business Development at Qulix Systems<\/a>. A representative of the StandFore FS intellectual banking platform, he is a strategy development consultant for Digital Banking products and an expert in the field of software development and implementation for financial organizations."}],"_links":{"self":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/8656","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/users\/687"}],"replies":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/comments?post=8656"}],"version-history":[{"count":7,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/8656\/revisions"}],"predecessor-version":[{"id":34618,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/8656\/revisions\/34618"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/media\/8657"}],"wp:attachment":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/media?parent=8656"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/categories?post=8656"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/tags?post=8656"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=8656"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}