Top 10 2014-I8 Insufficient Security Configurability - Revision history

Craig Smith at 23:02, 1 December 2015

2015-12-01T23:02:44Z

Craig Smith at 00:12, 18 August 2015

2015-08-18T00:12:44Z

Craig Smith at 23:03, 9 February 2015

2015-02-09T23:03:52Z

Craig Smith at 22:44, 29 June 2014

2014-06-29T22:44:58Z

Craig Smith at 22:44, 29 June 2014

2014-06-29T22:44:00Z

Craig Smith at 22:41, 29 June 2014

2014-06-29T22:41:33Z

Craig Smith at 22:40, 29 June 2014

2014-06-29T22:40:35Z

Craig Smith at 22:36, 29 June 2014

2014-06-29T22:36:44Z

Craig Smith at 22:35, 29 June 2014

2014-06-29T22:35:57Z

Craig Smith at 22:33, 29 June 2014

2014-06-29T22:33:45Z

← Older revision		Revision as of 23:02, 1 December 2015
Line 1:		Line 1:
−	<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>	+	<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_2010:SummaryTableHeaderBeginTemplate\|year=2013\|language=en}}

← Older revision		Revision as of 00:12, 18 August 2015
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}}

@@ Line 22: / Line 22: @@
 {{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=Is My Security Configurability Sufficient?|position=firstLeft|year=2013|language=en}}
-The simplest way to determine if you have security configurability deficiencies is to manually inspect the administrative interface of the device for options to strengthen security such as forcing the creation of strong passwords, the ability to separate admin users from normal users and the ability to enable encryption for data at rest.
+Checking for Insufficient Security Configurability includes:
 {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Improve My Security Configurability?|position=right|year=2013|language=en}}
 Sufficient security configurability requires:
-# Ensuring the ability to separate normal users from administrative users.
+# Ensuring the ability to separate normal users from administrative users
-# Ensuring the ability to encrypt data at rest or in transit.
+# Ensuring the ability to encrypt data at rest or in transit
-# Ensuring the ability to force strong password policies.
+# Ensuring the ability to force strong password policies
 {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}}
 '''Scenario #1:''' No ability to enforce strong password policies.

← Older revision		Revision as of 22:44, 29 June 2014
Line 41:		Line 41:

	</span>{{Top_10_2010:ExampleEndTemplate}}		</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~~.	+	In the cases above, the attacker is able to use the lack of these controls to get access to user accounts with weak passwords or access data at rest which has protection.

@@ Line 25: / Line 25: @@
 {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Improve My Security Configurability?|position=right|year=2013|language=en}}
-Ensuring sufficient security configurability requires:
+Sufficient security configurability requires:
 # Ensuring the ability to separate normal users from administrative users.
 # Ensuring the ability to encrypt data at rest or in transit.
-# Ensuring the ability to force strong password policies
+# Ensuring the ability to force strong password policies.
 {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}}
 '''Scenario #1:''' No ability to enforce strong password policies.
 {{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;">
-Example
+Admins and users are allowed to create passwords for their accounts.
 </span>{{Top_10_2010:ExampleEndTemplate}}
 '''Scenario #2:''' No ability to enable encryption of data at rest.
 {{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;">
-Example
+Password or other sensitive data stored on the device may not be encrypted.
 </span>{{Top_10_2010:ExampleEndTemplate}}

@@ Line 2: / Line 2: @@
 {{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:SummaryTableTemplate|exploitability=2|prevalence=2|detectability=1|impact=2|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 device.
@@ Line 13: / Line 13: @@
 </td>
-      <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Insufficient security configurability could lead to compromise of the device whether intentional or accidental.
+      <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Insufficient security configurability could lead to compromise of the device whether intentional or accidental and/or data loss.
 </td>

@@ Line 2: / Line 2: @@
 {{Top_10_2010:SummaryTableHeaderBeginTemplate|year=2013|language=en}}
-{{Top_10:SummaryTableTemplate|exploitability=2|prevalence=2|detectability=2|impact=1|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 device.
@@ Line 10: / Line 10: @@
 </td>
-      <td colspan=2  {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Insufficient security configurability is present when users of the device have limited or no ability to alter its security controls. Insufficient security configurability is apparent when the web interface of the device has no options for creating granular user permissions or forcing the use of strong passwords. Manual review of the web interface and its available options will review these deficiencies.
+      <td colspan=2  {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Insufficient security configurability is present when users of the device have limited or no ability to alter its security controls. Insufficient security configurability is apparent when the web interface of the device has no options for creating granular user permissions or for example, forcing the use of strong passwords. Manual review of the web interface and its available options will reveal these deficiencies.
 </td>
@@ Line 16: / Line 16: @@
 </td>
-      <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Data could be stolen or modified and devices taken control of.  Could your users be harmed? Could your brand be harmed?
+      <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider the business impact if data can be stolen or modified and control over the device assumed. Could your customers be harmed?
 </td>

@@ Line 4: / Line 4: @@
 {{Top_10:SummaryTableTemplate|exploitability=1|prevalence=2|detectability=2|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 device, the cloud interface or the mobile application.
+      <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider anyone who has access to the device.
 </td>