Architecture and design principles - Revision history

Vinaykbansal: /* Mobile Security */

2011-05-17T09:54:44Z

‎Mobile Security

Vinaykbansal at 09:26, 15 May 2011

2011-05-15T09:26:35Z

Vinaykbansal at 15:48, 14 May 2011

2011-05-14T15:48:15Z

Vinaykbansal at 15:46, 14 May 2011

2011-05-14T15:46:51Z

Giles Hogben at 14:26, 10 May 2011

2011-05-10T14:26:17Z

Giles Hogben at 12:54, 10 May 2011

2011-05-10T12:54:42Z

Giles Hogben at 12:49, 10 May 2011

2011-05-10T12:49:32Z

Giles Hogben at 12:42, 10 May 2011

2011-05-10T12:42:27Z

Giles Hogben at 12:33, 10 May 2011

2011-05-10T12:33:45Z

Giles Hogben at 12:32, 10 May 2011

2011-05-10T12:32:38Z

@@ Line 5: / Line 5: @@
 =='''Mobile Security'''==
 *1. Threats, Risks and Vulnerabilities (Risks)
-*2. Design Principles (As part of the Controls)
+*2. Design Principles (As part of the Controls) - Added here [https://www.owasp.org/index.php/Projects/OWASP_Mobile_Security_Project_-_Top_Ten_Mobile_Controls#Top_10_mobile_controls_and_design_principles]
 *3. Architectural Patterns  (New)
 *4. Secure Mobile Development/Coding Guidelines

@@ Line 4: / Line 4: @@
 =='''Mobile Security'''==
-*1. Threats, Risks and Vulnerabilities
+*1. Threats, Risks and Vulnerabilities (Risks)
-*2. Design Principles
+*2. Design Principles (As part of the Controls)
-*3. Architectural Patterns
+*3. Architectural Patterns  (New)
 *4. Secure Mobile Development/Coding Guidelines

@@ Line 7: / Line 7: @@
 *2. Design Principles
 *3. Architectural Patterns
-*4. Secure Mobile Development Guidelines
+*4. Secure Mobile Development/Coding Guidelines
 ==1. Top Risks/Vulnerabilities==

@@ Line 1: / Line 1: @@
 The following is a merge of ENISA, OWASP and Veracode top 10. Note that there is a mixture of threats and vulnerabilities here - we should decide whether to use risks (threats with impact on assets which occur with probability) and vulnerabilities (system flaws which increase the probability of a threat occurring). I have cut those risks/vulnerabilities which cannot be addressed in any way by developers.  We should decide whether to include recommendations in the style of "code of practice"- e.g. activity monitoring should only be used in circumstances xyz... (feel free to restructure)
-==Top Risks/Vulnerabilities==
+My recommendation would be to separate out the design principles from the Risks/Vulnerabilities.
 * Unsafe sensitive data storage

@@ Line 40: / Line 40: @@
 * Financial malware attacks The smartphone is infected with malware specifically designed for stealing credit card numbers, online banking credentials or subverting online banking or ecommerce transactions.
 * Network congestion 	Network resource overload due to smartphone usage leading to network unavailability for the end-user.
 * Unauthorized network connectivity (exfiltration or command & control)
 * UI Impersonation
@@ Line 51: / Line 52: @@
 ** Don't allow SSL downgrade.
 ** Don't trust network infrastructure
 * Client-side injection
 * Client-side DOS
 * Malicious third-party code
 * Client-side buffer overflow
 * Failure to properly handle inbound SMS messages
@@ Line 59: / Line 62: @@
 * Failure to properly handle outbound SMS messages
 * Failure to disable insecure platform features in application (caching of keystrokes, screen data)

@@ Line 36: / Line 36: @@
 * Surveillance attacks: An attacker keeps a specific user under surveillance through the target user’s smartphone.
 * Diallerware attacks: An attacker steals money from the user by means of malware that makes hidden use of premium SMS services or numbers.
 * Financial malware attacks The smartphone is infected with malware specifically designed for stealing credit card numbers, online banking credentials or subverting online banking or ecommerce transactions.
@@ Line 42: / Line 43: @@
 * UI Impersonation
 * System modification (rootkit, APN proxy config)
 * Logic or Time bomb (including runtime interpreter)
 * Unsafe sensitive data transmission
 * Hardcoded password/keys
 * Lack of data protection in transit
 * Client-side injection
 * Client-side DOS
@@ Line 51: / Line 56: @@
 * Client-side buffer overflow
 * Failure to properly handle inbound SMS messages
 * Failure to properly handle outbound SMS messages
 * Failure to disable insecure platform features in application (caching of keystrokes, screen data)

@@ Line 4: / Line 4: @@
 * Unsafe sensitive data storage
-** Consider the whole data lifecycle in writing your application
+** Consider the whole data lifecycle in writing your application (collection over the wire, temporary storage, caching, backup, deletion etc...)
 ** Automatically delete data which is not required (how to know when it's not required?).
 ** Securely delete data using standard shredding techniques.
 ** Store a minimum of data on the client side device.
-** Securely wipe removable media
+** Securely wipe removable media.
 ** Be aware of caches and temporary storage as a possible leakage channel.
 ** Implement key and password storage best practice.
-** Figure out what data needs to be protected most and what doesn't.
+** In the design phase analyse what data needs to be protected most and what doesn't and apply controls at appropriate places.
 * Unintentional disclosure of data: The smartphone user unintentionally discloses data on the smartphone.
@@ Line 17: / Line 17: @@
 ** Use non-persistent identifiers wherever possible - e.g. do not use the EMEI number as an identifier unless there is a good reason to do so.
 ** Apply techniques for the detection of covert channels - e.g. covert flow trees to discover information which may flow through shared resources such as file systems, resource use etc...
-** Carefully control any data which is stored in public stores such as address book, media gallery etc...
+** Carefully control what data which is stored in public stores such as address book, media gallery etc... including metadata.
 ** Obtain user explicit user consent according to best practice (see implementation guidelines) for collection of personal data.
@@ Line 33: / Line 33: @@
 * Network Spoofing Attacks: An attacker deploys a rogue network access point (WiFi or GSM) and users connect to it. The attacker subsequently intercepts (or tampers with) the user communication to carry out further attacks such as phishing.
-** Use the GSM encryption flags to detect and signal downgrade attacks.
+** Use the GSM encryption-on indicator to detect and signal downgrade attacks.
 * Surveillance attacks: An attacker keeps a specific user under surveillance through the target user’s smartphone.

@@ Line 3: / Line 3: @@
 ==Top Risks/Vulnerabilities==
-# Unsafe sensitive data storage
+* Unsafe sensitive data storage
 ** Consider the whole data lifecycle in writing your application
 ** Automatically delete data which is not required (how to know when it's not required?).
@@ Line 13: / Line 13: @@
 ** Figure out what data needs to be protected most and what doesn't.
-# Unintentional disclosure of data: The smartphone user unintentionally discloses data on the smartphone.
+* Unintentional disclosure of data: The smartphone user unintentionally discloses data on the smartphone.
-## Apply the principle of minimal disclosure - only collect and disclose data which is required for the application (how to know what this is?)
+** Apply the principle of minimal disclosure - only collect and disclose data which is required for the application (how to know what this is?)
-## Apply techniques for the detection of covert channels - e.g. covert flow trees to discover information which may flow through shared resources such as file systems, resource use etc...
+** Apply techniques for the detection of covert channels - e.g. covert flow trees to discover information which may flow through shared resources such as file systems, resource use etc...
-# Attacks on decommissioned smartphones: The smartphone is decommissioned improperly allowing an attacker access to the data on the device.
+* Attacks on decommissioned smartphones: The smartphone is decommissioned improperly allowing an attacker access to the data on the device.
-# Phishing attacks: An attacker collects user credentials (such as passwords and credit card numbers) by means of fake apps or (SMS, email) messages that seem genuine.
+* Phishing attacks: An attacker collects user credentials (such as passwords and credit card numbers) by means of fake apps or (SMS, email) messages that seem genuine.
-# Spyware:  Spyware covers untargeted collection of personal information as opposed to targeted surveillance.
+* Spyware:  Spyware covers untargeted collection of personal information as opposed to targeted surveillance.
-# Network Spoofing Attacks: An attacker deploys a rogue network access point (WiFi or GSM) and users connect to it. The attacker subsequently intercepts (or tampers with) the user communication to carry out further attacks such as phishing.
+* Network Spoofing Attacks: An attacker deploys a rogue network access point (WiFi or GSM) and users connect to it. The attacker subsequently intercepts (or tampers with) the user communication to carry out further attacks such as phishing.
-# Surveillance attacks: An attacker keeps a specific user under surveillance through the target user’s smartphone.
+* Surveillance attacks: An attacker keeps a specific user under surveillance through the target user’s smartphone.
-# Diallerware attacks: An attacker steals money from the user by means of malware that makes hidden use of premium SMS services or numbers.
+* Diallerware attacks: An attacker steals money from the user by means of malware that makes hidden use of premium SMS services or numbers.
-# Financial malware attacks The smartphone is infected with malware specifically designed for stealing credit card numbers, online banking credentials or subverting online banking or ecommerce transactions.
+* Financial malware attacks The smartphone is infected with malware specifically designed for stealing credit card numbers, online banking credentials or subverting online banking or ecommerce transactions.
-# Network congestion 	Network resource overload due to smartphone usage leading to network unavailability for the end-user.
+* Network congestion 	Network resource overload due to smartphone usage leading to network unavailability for the end-user.
-# Unauthorized network connectivity (exfiltration or command & control)
+* Unauthorized network connectivity (exfiltration or command & control)
-# UI Impersonation
+* UI Impersonation
-# System modification (rootkit, APN proxy config)
+* System modification (rootkit, APN proxy config)
-# Logic or Time bomb (including runtime interpreter)
+* Logic or Time bomb (including runtime interpreter)
-# Unsafe sensitive data transmission
+* Unsafe sensitive data transmission
-# Hardcoded password/keys
+* Hardcoded password/keys
-# Lack of data protection in transit
+* Lack of data protection in transit
-# Client-side injection
+* Client-side injection
-# Client-side DOS
+* Client-side DOS
-# Malicious third-party code
+* Malicious third-party code
-# Client-side buffer overflow
+* Client-side buffer overflow
-# Failure to properly handle inbound SMS messages
+* Failure to properly handle inbound SMS messages
-# Failure to properly handle outbound SMS messages
+* Failure to properly handle outbound SMS messages
-# Failure to disable insecure platform features in application (caching of keystrokes, screen data)
+* Failure to disable insecure platform features in application (caching of keystrokes, screen data)