1 / 37

Company : Deutsche Telekom Academic advisor : Yuval Elovici

Company : Deutsche Telekom Academic advisor : Yuval Elovici Technical advisor : Assaf Shabtai Project Team : Limor Segev Eran Frieman Carmel Karni . Remote backup and recovery service for Android device owners. Motivation. Part of Deutsche Telekom project:

suchin
Télécharger la présentation

Company : Deutsche Telekom Academic advisor : Yuval Elovici

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Company: Deutsche Telekom Academic advisor: Yuval Elovici Technical advisor : Assaf Shabtai Project Team: Limor Segev Eran Frieman Carmel Karni Remote backup and recovery service for Android device owners

  2. Motivation. • Part of Deutsche Telekom project: • Backup and restore users’ Android terminals • Remote monitoring and offline analysis of Android application • Remote monitoring and offline analysis of Android application

  3. Problem Domain • An Android OS could be attacked by hackers: • Open platform • Users will access the Internet intensively • Everyone can develop applications for Android

  4. Problem Domain Cont. • Successful attack on Androids may: • Expose private information • Prevent T-Mobile customers from using T- Mobile services • Flood T-Mobile’s customer service infrastructure and personnel. • No easy way exists to “fix” mobile devices and especially Android.

  5. Scope and Purpose. • Backup and restore users’ Android terminals: • Develop a platform that will backup Android terminals and restore “last good snapshot” on demand. • Backup of customers installed applications. • Backup of applications must always be on a remote server.

  6. Current Situation • Backup is possible for: • Documents • Media files • Not for Application files

  7. The Solution • Backup Application files on remote server • Manage DB at server + Allow Security operations • Enable restoration of phone last stable status

  8. System Architecture 1. Downloading and installing a new application 2. System’s agent send the new application files (apk) to the external server 3. Sending the new application files (apk) to the storage server with additional information to enable restoring users’ systems 4. Backed-up application apk apk apk apk apk apk apk Internet Customer’s Android device Server Storage 5. Threat detection system checks files and alerts the server about threats

  9. System Architecture 3. Sending an alert to the user apk apk apk apk apk Storage Internet Customer’s Android device Server 2. Sending analysis result: “malicious application” • Threat detection system checks apks with status “UNCHECKED”

  10. System Architecture apk apk apk apk apk apk Internet Storage Server NetShield Analysis Server

  11. System Architecture Cont. • The system includes 4 major components: • Agent • Server (which runs a threat detection system) • Data Base • Remote Desktop Client for reports

  12. Main Functional Requirements Agent:

  13. Main Functional Requirements Server + Agent Management:

  14. Main Functional Requirements Management: Deployment and Installation: Agent Software Installation

  15. Main Functional Requirements System View:

  16. Non-Functional Requirements • Speed, Capacity & Throughput • Ninety five percent of all backup transaction will be • completed within 10 seconds. • The agent will use up to 20% of the CPU. • Reliability • support data recovery, including transmission-error detection • and correction. • Portability • client side is dedicated to the Android OS.

  17. Non-Functional Requirements • Usability • Extremely user-friendly. • Does not require constant maintenance by the user. • Possibility to configure most of the system operations to be done automatically • Safety & Security • The information sent between the server and the agents will be encrypted. • Availability • The server will be active at all times, waiting for agents requests or notifications from the Threats Detection System.

  18. High level use cases view of the system

  19. Use case: Install and Register

  20. Use case: Install and Register

  21. Use case: Login

  22. Use case: Login

  23. Use case: Intercept Install Event

  24. Use case: Intercept Install Event

  25. Use case: Backup Application

  26. Use case: Backup Application

  27. Use case: Hand-set Recovery

  28. Use case: Hand-set Recovery

  29. Use case: Handle Android malware detection

  30. Use case: Handle Android malware detection

  31. Use case: Manager Login

  32. Use case: Manager Login

  33. Use case: Produce Reports

  34. Use case: Produce Reports

  35. System Constraints • Platform constraints • Eclipse IDE • SE project constraints • If a device will be unavailable we will have to work on an emulator. • If there will be no threat detection program we will build a simulation of one.

  36. Risks • The system that we are developing require root permissions of the Android OS, which are not granted naturally. • The solution: There are known methods that will allow us to get Root Privileges.

  37. The End

More Related