View source for Top 10 2014-I2 Insufficient Authentication/Authorization

<center>[https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project#tab=Top_10_IoT_Vulnerabilities__282014_29 Back To The Internet of Things Top 10]</center>

{{Top_10_2010:SummaryTableHeaderBeginTemplate|year=2013|language=en}}
{{Top_10:SummaryTableTemplate|exploitability=2|prevalence=2|detectability=1|impact=1|year=2013|language=en}}
{{Top_10_2010:SummaryTableHeaderEndTemplate|year=2013}}
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider anyone who has access to the web interface, mobile interface or cloud interface including internal and external users.

</td>
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Attacker uses weak passwords, insecure password recovery mechanisms, poorly protected credentials or lack of granular access control to access a particular interface. Attack could come from external or internal users.

</td>
     <td colspan=2  {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Authentication may not be sufficient when weak passwords are used or are poorly protected. Insufficient authentication/authorization is prevalent as it is assumed that interfaces will only be exposed to users on internal networks and not to external users on other networks. Deficiencies are often found to be present across all interfaces. Many Issues with authentication/authorization are easy to discover when examining the interface manually and can also be discovered via automated testing.

</td>
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Insufficient authentication/authorization can result in data loss or corruption, lack of accountability, or denial of access and can lead to complete compromise of the device and/or user accounts.

</td>
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider the business impact of compromised user accounts and possibly devices. All data could be stolen, modified, or deleted.  Could your customers be harmed?

</td>
{{Top_10_2010:SummaryTableEndTemplate|year=2013}}

{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=Is My Authentication/Authorization Sufficient?|position=firstLeft|year=2013|language=en}}

Checking for Insufficient Authentication includes:
* Attempting to use simple passwords such as "1234" is a fast and easy way to determine if the password policy is sufficient across all interfaces
* Reviewing network traffic to determine if credentials are being transmitted in clear text
* Reviewing requirements around password controls such as password complexity, password history check, password expiration and forced password reset for new users
* Reviewing whether re-authentication is required for sensitive features

Checking for Insufficient Authorization includes:
* Reviewing the various interfaces to determine whether the interfaces allow for separation of roles. For example, all features will be accessible to administrators, but users will have a more limited set of features available.
* Reviewing access controls and testing for privilege escalation

{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Make My Authentication/Authorization Better?|position=right|year=2013|language=en}}
Sufficient authentication/authorization requires:
# Ensuring that the strong passwords are required
# Ensuring granular access control is in place when necessary
# Ensuring credentials are properly protected
# Implement two factor authentication where possible
# Ensuring that password recovery mechanisms are secure
# Ensuring re-authentication is required for sensitive features
# Ensuring options are available for configuring password controls
# Ensuring credential can be revoked
# The app authentication is required
# The device authentication is required
# The server authentication is required
# Manage authenicated user id(credential info.) and the user's device id, the user's app id mapping table in the authentication server
# Ensuring that the authentication token/session key issuing to client is always different
# Ensuring that the user id, app id, device id is universally unique

Please review the following tabs for more detail based on whether you are a [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Manufacturers Manufacturer], [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Developers Developer] or [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Consumers Consumer]
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}}
'''Scenario #1:''' The interface only requires simple passwords.

{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;">
Username = Bob; Password = 1234

</span>{{Top_10_2010:ExampleEndTemplate}}
'''Scenario #2:''' Username and password are poorly protected when transmitted over the network.
{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;">
Authorization: Basic YWRtaW46MTIzNA==

</span>{{Top_10_2010:ExampleEndTemplate}}
In the cases above, the attacker is able to either easily guess the password or is able to capture the credentials as they cross the network and decode it since the credentials are only protected using Base64 Encoding.


{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=references|position=right|risk=1|year=2013|language=en}}
{{Top_10_2010:SubSubsectionOWASPReferencesTemplate}}

[https://www.owasp.org/index.php/Top_10_2013-A2-Broken_Authentication_and_Session_Management Top 10 2013-A2-Broken Authentication and Session Management]
{{Top_10_2010:SubSubsectionExternalReferencesTemplate}}