This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Top 10 2014-I4 Lack of Transport Encryption"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
−
<center>[https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=OWASP_Internet_of_Things_Top_10_for_2014 Back To The Internet of Things Top 10]</center>
+
<center>[https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project#tab=Top_IoT_Vulnerabilities Back To The Internet of Things Top 10]</center>
  
 
{{Top_10_2010:SummaryTableHeaderBeginTemplate|year=2013|language=en}}
 
{{Top_10_2010:SummaryTableHeaderBeginTemplate|year=2013|language=en}}

Revision as of 00:11, 18 August 2015

Back To The Internet of Things Top 10
Threat Agents Attack Vectors Security Weakness Technical Impacts Business Impacts
Application Specific Exploitability
AVERAGE		 Prevalence
COMMON		 Detectability
EASY		 Impact
SEVERE		 Application / Business Specific
Consider anyone who has access to the network the device is connected to, including external and internal users. Attacker uses the lack of transport encryption to view data being passed over the network. Attack could come from external or internal users. Lack of transport encryption allows data to be viewed as it travels over local networks or the internet. Lack of transport encryption is prevalent on local networks as it is easy to assume that local network traffic will not be widely visible, however in the case of a local wireless network, misconfiguration of that wireless network can make traffic visible to anyone within range of that wireless network. Many Issues with transport encryption are easy to discover simply by viewing network traffic and searching for readable data. Automated tools can also look for proper implementation of common transport encryption such as SSL and TLS. Lack of transport encryption can result in data loss and depending on the data exposed, could lead to complete compromise of the device or user accounts. Consider the business impact of exposed data as it travels across various networks. Data could be stolen or modified. Could your users be harmed by having their data exposed?
Do I Use Transport Encryption?

Checking for Lack of Transport Encryption includes:

  • Reviewing network traffic of the device, its mobile application and any cloud connections to determine if any information is passed in clear text
  • Reviewing the use of SSL or TLS to ensure it is up to date and properly implemented
  • Reviewing the use of any encryption protocols to ensure they are recommended and accepted
How Do I Use Transport Encryption?

Sufficient transport encryption requires:

  1. Ensuring data is encrypted using protocols such as SSL and TLS while transiting networks.
  2. Ensuring other industry standard encryption techniques are utilized to protect data during transport if SSL or TLS are not available.
  3. Ensuring only accepted encryption standards are used and avoid using proprietary encryption protocols

Please review the following tabs for more detail based on whether you are a Manufacturer, Developer or Consumer

Example Attack Scenarios

Scenario #1: The cloud interface uses only HTTP.

http://www.xyzcloudsite.com

Scenario #2: Username and password are transmitted in the clear over the network.

http://www.xyzcloud.com/login.php?userid=3&password=1234

In the cases above, the attacker has the ability to view sensitive data in the clear due to lack of transport encryption.


References

OWASP

Top 10 2013-A6-Sensitive Data Exposure

External
Retrieved from "https://wiki.owasp.org/index.php?title=Top_10_2014-I4_Lack_of_Transport_Encryption&oldid=199163"