This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:iot-reloaded:cybersecurity_issues_and_threats_in_iot_systems [2024/10/16 11:59] – pczekalski | en:iot-reloaded:cybersecurity_issues_and_threats_in_iot_systems [2024/12/10 21:50] (current) – pczekalski | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== IoT Attack Vectors ====== | ====== IoT Attack Vectors ====== | ||
| + | In this section, we discuss the concept of IoT attack vectors, attack surfaces, and threat vectors to clarify the difference between these cybersecurity terms, which are often used interchangeably. We discuss some IoT attack vectors that should be considered when designing cybersecurity strategies for IoT networks and systems. We also discuss some strategies that can be used to eliminate or mitigate the risk posed by IoT attack vectors. | ||
| + | |||
| + | ===== IoT attack vector, attack surface, and threat vector ===== | ||
| + | IoT attack vectors are the various methods that cybercriminals can use to access IoT devices to launch cyberattacks on the IoT infrastructure or other information system infrastructure of an organisation or the Internet as a whole. They provide a means for cybercriminals to exploit security vulnerabilities to compromise sensitive data's confidentiality, | ||
| + | |||
| + | The number of attack vectors keeps growing as cybercriminals develop numerous simple and sophisticated methods to exploit unresolved security vulnerabilities and zero-day abilities on computer systems and networks. In this way, there is no single solution to mitigate the risk posed by the growing number of attack vectors in classical computer systems and networks. As the number of IoT devices connected to the Internet increases, the number of IoT-related attack vectors also increases, requiring the development of a holistic cybersecurity strategy that handles the traditional attack vectors (e.g., malware, viruses, email attachments, | ||
| + | |||
| + | To defend IoT networks and systems, it is crucial to understand the various ways a cybercriminal can use to gain unauthorised access to IoT networks and systems. The term threat vector is often used interchangeably with attack vector. An IoT threat vector is the number of potential ways or methods cybercriminals can use to compromise the confidentiality, | ||
| + | |||
| + | An IoT attack surface is the number of attack vectors that cybercriminals can use to manipulate an IoT network or system to compromise data confidentiality, | ||
| + | |||
| + | ===== Some IoT attack vectors ===== | ||
| + | To eliminate IoT attack vectors, it is essential to understand the nature of some of them and their sources and then develop comprehensive security strategies to deal with them. This section will discuss IoT attack vectors from the perception layer to the application layer. Some of the IoT attack vectors or ways in which cybercriminals can gain illegal access to IoT networks and systems (to compromise data security or launch further attacks) include the following: | ||
| + | * **Compromised user or device credentials**: | ||
| + | * **Weak cryptographic algorithms**: | ||
| + | * **Open communication ports**: Cybercriminals can exploit unsecured and unnecessarily open ports (virtual entry points into a device that associates network traffic with a given application or process) to gain access to the device. Every necessarily open and unsecured port is a threat vector that cybercriminals can exploit to attack IoT devices, servers, and applications. | ||
| + | * **Misconfigurations**: | ||
| + | * **Firmware vulnerabilities**: | ||
| + | * **Zero-day vulnerabilities**: | ||
| + | * **Cross-site scripting (XSS)**: A browser-based attack vector can inject or insert malicious code within a browser-based application designed for users to access IoT services. For many IoT applications, | ||
| + | * **SQL injection**: | ||
| + | * **Distributed Denial of Service (DDoS) attacks**: This type of attack vector involves the use of bots to infect IoT devices and then create a botnet (network of bots) that can be controlled to overwhelm IoT gateways, services, data centres, and web applications with a massive amount of traffic or requests. This attack aims to cause the IoT gateways, services, data centres, and web applications to crash, depriving the users of accessing IoT services. The attacker takes over many IoT devices, creates a botnet, and redirects traffic from their devices to IoT gateways, services, data centres, and web applications to disrupt IoT services. | ||
| + | * **Session hijacking**: | ||
| + | * **Malware infection**: | ||
| + | * **Phishing**: | ||
| + | * **Brute-force attack**: This is another attack vector aimed at compromising the authentication credentials and encryption keys to gain unauthorised access to IoT data. It could be done using a trial-and-error method to guess the password or encryption key to gain unauthorised access to IoT networks, systems, and data. If the password and the encryption key are not strong enough, the attacker can illegally gain access to IoT devices. Using default passwords and weak encryption schemes in IoT devices makes them susceptible to these attacks. | ||
| + | * **Physical attacks**: This type of attack vector involves the adversary' | ||
| + | * **Insider attack**: It is also essential to consider the fact that legitimate users or employees could decide to leak sensitive IoT data to external entities, compromising the confidentiality of the data. An insider may also delete sensitive data intentionally or unintentionally. This attack vector should be considered when designing a cybersecurity strategy for IoT networks and systems. | ||
| + | * **Exploitation of supply chain vulnerability**: | ||
| + | |||
| + | The attack vectors discussed above could be grouped into two categories: passive and active. Passive attack vector exploits allow attackers to gain unauthorised access to IoT networks and systems without intruding or interfering with their operation. Examples of these attack vectors include phishing and other social engineering-based attack vectors. On the other hand, active attack vector exploits interfere with the operation of the IoT network and system. Examples of this category of attack vector include DDoD attacks, brute-force attacks, malware attacks, etc. | ||
| + | |||
| + | |||
| + | ===== Strategies to defend against well-known IoT attack vector exploits ===== | ||
| + | To address common attack vectors, it is vital to understand the nature of the attack vector exploits, including passive and active ones. Most attack vector exploits share some common characteristics, | ||
| + | * The attackers first identify targets that they intend to go after. | ||
| + | * The attackers use social engineering strategies, malware, phishing, and vulnerability scanning tools to scan the targeted victim' | ||
| + | * The attackers set out to identical a set of attack vectors that they intend to exploit and then search for the tools required to carry out the attack vector exploits. | ||
| + | * Attackers gain unauthorised access to IoT systems, steal sensitive data, install malware, and sometimes escalate the attack by using compromised devices to carry out further attacks to compromise other system resources. | ||
| + | * The attack tries to clean their tracks to remain undetected. They also steal valuable data or use computing and communication resources. | ||
| + | |||
| + | |||
| + | Identifying and deploying practical security tools and policies to deal with IoT attack vectors is essential. These security tools and policies should be designed to eliminate or reduce the risk from IoT attack vectors from the IoT perception layer to the application layers. Some of the strategies that can be designed to defend IoT networks and systems against well-known IoT attack vectors include the following: | ||
| + | * **Create secure authentication policies**: Replace default passwords with strong passwords. Encourage the use of password managers to ensure that login credentials are strong and resilient to brute-force attacks. | ||
| + | * **Implementation of strong energy-efficient cryptographic schemes**: The IoT data stored in IoT devices, computing devices, network devices, and databases should be encrypted or transformed to a format that is unintelligible to unauthorised entities. Data should be encrypted before being transported over communication networks. | ||
| + | * **Secure communication ports**: All communication ports should be secured, and unused ports should be closed to prevent exploitation. | ||
| + | * **Identify and resolve vulnerabilities**: | ||
| + | * **Enforce the policy of least resistance**: | ||
| + | * **All IoT devices in the network should be identifiable**: | ||
| + | * **Adoption of secure software development methods**: The code should be well-tested and reviewed to ensure that security vulnerabilities can be identified and resolved. We should also ensure that the libraries used to implement the device firmware are secured and well-tested. When programming IoT devices, copying already-written code from the Internet should be minimised to ensure it does not introduce security vulnerabilities. | ||
| + | * **Continual monitoring of IoT devices**: Maintaining an up-to-date inventory of all connected devices and monitoring the activities within IoT devices and other systems. Automated tools should be used to discover all connected devices and continuously scan them to identify and address vulnerabilities. | ||
| + | * **Regular security update and patching**: Although managing and installing security updates and patching security gaps for thousands of devices can be challenging, | ||
| + | * **Decommission unused IoT devices**: Unused IoT devices should be removed from the IoT network. If any IoT device is not being used, it may not be regularly updated or adequately secured, which poses a risk to the IoT network and systems. Thus, any used IoT device and any other hard or software system not being used should be removed from the IoT network. | ||
| + | * **Implement centralised management for IoT devices**: Managing IoT devices, network traffic and data flow from a single point facilitates the detection of malicious events and swiftly addresses them. It also promotes the implementation of integrated cybersecurity systems that enforce the implementation of security controls throughout the network. | ||
| + | * **Isolate IoT devices from critical system resources and data**: By isolating IoT devices from essential system and data resources, we ensure that even if the IoT network is compromised, | ||
| + | * **Use updated antimalware software**: Ensure that antimalware software is up to date to guarantee that it can protect against the latest malware. | ||
| + | * **Deploy attack detection and response tools**: Deploy automated attack detection and response tools that can detect and stop cyberattacks as soon as they are launched. AI and machine learning tools should be leveraged to design automated attack prevention, detection and response tools for IoT. | ||
| + | * **Regular and effective employee training**: Employees should be well-trained to handle cybersecurity tools and detect social engineering and phishing attacks designed to trick them into leaking sensitive information. | ||
| + | * **Ensuring supply chain security**: Third-party hardware and software tools should be well-secured to prevent the introduction of security vulnerabilities that attackers can exploit. Also, ensure that third-party software is regularly updated on time. | ||
| + | * **Zero-trust security approach**: Apply the Zero Trust (ZT) security framework to ensure that all users, whether in or outside the organisation' | ||
| + | * **System-based security approach**: The IoT security landscape is very complex and is constantly changing, requiring the integration of security tools, security policies, people, and diverse types of information and cyber-physical systems. The best way to manage the complex and dynamic interaction of complex components that constitute the IoT infrastructure is to use a system-based approach. Concepts from the growing fields of systems thinking, systems dynamics, and software engineering can be borrowed to model and design robust and secure cybersecurity systems for IoT networks and systems. | ||
| + | |||
| + | |||