The Internet of Things (IoT) is the interconnection of physical devices, vehicles (also called “connected devices” and “smart devices”), buildings and other elements: integrated with electronics, software, sensors, actuators and network connectivity that enable these objects to collect and exchange data.3. Security Issues and Vulnerabilities “Yet as we connect more and more devices to the Internet, everything from the thermostat to the toilet to the front door itself can create a potential new opening for intruders electronic. » – MIT Technology Review, August 2013 • Usage data can reveal whether or not a person is present in the home • The automated home system can be hacked, allowing intruders to enter the home • Video feeds from Homes Allow Attackers to Access Private Information About Individuals3.1 IoT Security: Trends, Issues, and Challenges3.2 Security and Privacy Challenges for the Internet of Things3.3 Unique Challenges for Internet of Things Security IoT• IoT relies on microcontrollers with limited memory and computing power o This often makes it impractical to implement approaches designed for powerful computers o This in turn requires that limited IoT devices be hidden behind secure gateways. • Threats based on physical access to IoT devices. (SOC) incorporating hardware security support o Ecliptic curve cryptography with reduced computational requirements • Everything exposed to the Internet must be securely updateable • The user experience must be sufficiently good to avoid becoming a weak link in the chain • The need to keep up to date with security best practices... middle of paper ......tainers (software), Trusted Platform Module, hardware coprocessors, mapping secure memory and code execution encryption operations.Virtualization-based security agent: Hypervisors in a virtualized environment are widely used to transparently enforce security policies across enterprise and cloud applications in IT environments enterprise and cloud computing. Gateway-based security agent: When security cannot be added to an endpoint, as is the case for legacy systems, a gateway-based security agent or Bump-in-the-wire implementing The security agent function as a physically separate network node can be deployed to secure these types of endpoints and their communications. Because the security agent is not physically located on the same endpoint it is protecting, advanced security features such as Secure Boot Attestation or application whitelisting on that endpoint cannot be used. not be easily implemented..