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-I6 Insecure Cloud Interface"
Craig Smith (talk | contribs) |
Craig Smith (talk | contribs) |
||
| Line 26: | Line 26: | ||
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Secure My Cloud Interface?|position=right|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Secure My Cloud Interface?|position=right|year=2013|language=en}} | ||
A secure cloud interface requires: | A secure cloud interface requires: | ||
| − | # Default passwords and ideally default usernames to be changed during initial setup | + | # Default passwords and ideally default usernames to be changed during initial setup |
| − | # Ensuring user accounts can not be enumerated using functionality such as password reset mechanisms | + | # Ensuring user accounts can not be enumerated using functionality such as password reset mechanisms |
| − | # Ensuring account lockout after an appropriate number of tries | + | # Ensuring account lockout after an appropriate number of tries |
| − | # Ensuring the cloud-based web interface is not susceptible to XSS, SQLi or CSRF | + | # Ensuring the cloud-based web interface is not susceptible to XSS, SQLi or CSRF |
| − | # Ensuring credentials are not exposed | + | # Ensuring credentials are not exposed over the internet |
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}} | ||
Revision as of 21:55, 5 February 2015
| 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 internet. | Attacker uses multiple vectors such as insufficient authentication, lack of transport encryption and account enumeration to access data or controls via the cloud website. Attack will most likely come from the internet. | An insecure cloud interface is present when easy to guess credentials are used or account enumeration is possible. Insecure cloud interfaces are easy to discover by simply reviewing the connection to the cloud interface and identifying if SSL is in use or by using the password reset mechanism to identify valid accounts which can lead to account enumeration. | An insecure cloud interface could lead to compromise of user data and control over the device. | Consider the business impact of an insecure cloud interface. Data could be stolen or modified and control over devices assumed. Could your customers be harmed? Could your brand be harmed? | |
|
Is My Cloud Interface Secure?
The easiest way to determine if your cloud interface is secure is by reviewing areas such as account enumeration, account lockout and whether credentials or other sensitive data are exposed while connected to the cloud interface. |
How Do I Secure My Cloud Interface?
A secure cloud interface requires:
|
|
Example Attack Scenarios
Scenario #1: Password reset indicates whether account is valid. Password Reset "That account does not exist." Scenario #2: Username and password are poorly protected when transmitted over the network. Authorization: Basic S2ZjSDFzYkF4ZzoxMjM0NTY3 In the cases above, the attacker is able to either determine a valid user account or is able to capture the credentials as they cross the network and decode them since the credentials are only protected using Base64 Encoding.
|
References
OWASP External |
