CINXE.COM

Mobile security - Wikipedia

<!DOCTYPE html> <html class="client-nojs vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-sticky-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-enabled skin-theme-clientpref-day vector-toc-available" lang="en" dir="ltr"> <head> <meta charset="UTF-8"> <title>Mobile security - Wikipedia</title> <script>(function(){var className="client-js vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-sticky-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-enabled skin-theme-clientpref-day vector-toc-available";var cookie=document.cookie.match(/(?:^|; )enwikimwclientpreferences=([^;]+)/);if(cookie){cookie[1].split('%2C').forEach(function(pref){className=className.replace(new RegExp('(^| )'+pref.replace(/-clientpref-\w+$|[^\w-]+/g,'')+'-clientpref-\\w+( |$)'),'$1'+pref+'$2');});}document.documentElement.className=className;}());RLCONF={"wgBreakFrames":false,"wgSeparatorTransformTable":["",""],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy", "wgMonthNames":["","January","February","March","April","May","June","July","August","September","October","November","December"],"wgRequestId":"f4e66e7e-eeac-446f-999d-56bcf44498b4","wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"Mobile_security","wgTitle":"Mobile security","wgCurRevisionId":1255553561,"wgRevisionId":1255553561,"wgArticleId":30500317,"wgIsArticle":true,"wgIsRedirect":false,"wgAction":"view","wgUserName":null,"wgUserGroups":["*"],"wgCategories":["Articles with short description","Short description is different from Wikidata","All articles with unsourced statements","Articles with unsourced statements from October 2023","Articles needing additional references from October 2023","All articles needing additional references","All articles with vague or ambiguous time","Vague or ambiguous time from March 2023","Wikipedia articles needing clarification from October 2023","Articles with unsourced statements from March 2023", "All articles with specifically marked weasel-worded phrases","Articles with specifically marked weasel-worded phrases from March 2023","All articles with failed verification","Articles with failed verification from October 2023","Articles needing additional references from November 2022","Articles with unsourced statements from February 2017","Articles with unsourced statements from April 2012","All articles with incomplete citations","Articles with incomplete citations from March 2023","CS1 French-language sources (fr)","Mobile security"],"wgPageViewLanguage":"en","wgPageContentLanguage":"en","wgPageContentModel":"wikitext","wgRelevantPageName":"Mobile_security","wgRelevantArticleId":30500317,"wgIsProbablyEditable":true,"wgRelevantPageIsProbablyEditable":true,"wgRestrictionEdit":[],"wgRestrictionMove":[],"wgNoticeProject":"wikipedia","wgCiteReferencePreviewsActive":false,"wgFlaggedRevsParams":{"tags":{"status":{"levels":1}}},"wgMediaViewerOnClick":true,"wgMediaViewerEnabledByDefault" :true,"wgPopupsFlags":0,"wgVisualEditor":{"pageLanguageCode":"en","pageLanguageDir":"ltr","pageVariantFallbacks":"en"},"wgMFDisplayWikibaseDescriptions":{"search":true,"watchlist":true,"tagline":false,"nearby":true},"wgWMESchemaEditAttemptStepOversample":false,"wgWMEPageLength":90000,"wgRelatedArticlesCompat":[],"wgCentralAuthMobileDomain":false,"wgEditSubmitButtonLabelPublish":true,"wgULSPosition":"interlanguage","wgULSisCompactLinksEnabled":false,"wgVector2022LanguageInHeader":true,"wgULSisLanguageSelectorEmpty":false,"wgWikibaseItemId":"Q3268325","wgCheckUserClientHintsHeadersJsApi":["brands","architecture","bitness","fullVersionList","mobile","model","platform","platformVersion"],"GEHomepageSuggestedEditsEnableTopics":true,"wgGETopicsMatchModeEnabled":false,"wgGEStructuredTaskRejectionReasonTextInputEnabled":false,"wgGELevelingUpEnabledForUser":false};RLSTATE={"ext.globalCssJs.user.styles":"ready","site.styles":"ready","user.styles":"ready","ext.globalCssJs.user":"ready","user": "ready","user.options":"loading","ext.cite.styles":"ready","ext.pygments":"ready","skins.vector.search.codex.styles":"ready","skins.vector.styles":"ready","skins.vector.icons":"ready","jquery.makeCollapsible.styles":"ready","ext.wikimediamessages.styles":"ready","ext.visualEditor.desktopArticleTarget.noscript":"ready","ext.uls.interlanguage":"ready","wikibase.client.init":"ready","ext.wikimediaBadges":"ready"};RLPAGEMODULES=["ext.cite.ux-enhancements","ext.pygments.view","mediawiki.page.media","ext.scribunto.logs","site","mediawiki.page.ready","jquery.makeCollapsible","mediawiki.toc","skins.vector.js","ext.centralNotice.geoIP","ext.centralNotice.startUp","ext.gadget.ReferenceTooltips","ext.gadget.switcher","ext.urlShortener.toolbar","ext.centralauth.centralautologin","mmv.bootstrap","ext.popups","ext.visualEditor.desktopArticleTarget.init","ext.visualEditor.targetLoader","ext.echo.centralauth","ext.eventLogging","ext.wikimediaEvents","ext.navigationTiming","ext.uls.interface", "ext.cx.eventlogging.campaigns","ext.cx.uls.quick.actions","wikibase.client.vector-2022","ext.checkUser.clientHints","ext.quicksurveys.init","ext.growthExperiments.SuggestedEditSession","wikibase.sidebar.tracking"];</script> <script>(RLQ=window.RLQ||[]).push(function(){mw.loader.impl(function(){return["user.options@12s5i",function($,jQuery,require,module){mw.user.tokens.set({"patrolToken":"+\\","watchToken":"+\\","csrfToken":"+\\"}); }];});});</script> <link rel="stylesheet" href="/w/load.php?lang=en&amp;modules=ext.cite.styles%7Cext.pygments%2CwikimediaBadges%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediamessages.styles%7Cjquery.makeCollapsible.styles%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles%7Cwikibase.client.init&amp;only=styles&amp;skin=vector-2022"> <script async="" src="/w/load.php?lang=en&amp;modules=startup&amp;only=scripts&amp;raw=1&amp;skin=vector-2022"></script> <meta name="ResourceLoaderDynamicStyles" content=""> <link rel="stylesheet" href="/w/load.php?lang=en&amp;modules=site.styles&amp;only=styles&amp;skin=vector-2022"> <meta name="generator" content="MediaWiki 1.44.0-wmf.4"> <meta name="referrer" content="origin"> <meta name="referrer" content="origin-when-cross-origin"> <meta name="robots" content="max-image-preview:standard"> <meta name="format-detection" content="telephone=no"> <meta name="viewport" content="width=1120"> <meta property="og:title" content="Mobile security - Wikipedia"> <meta property="og:type" content="website"> <link rel="preconnect" href="//upload.wikimedia.org"> <link rel="alternate" media="only screen and (max-width: 640px)" href="//en.m.wikipedia.org/wiki/Mobile_security"> <link rel="alternate" type="application/x-wiki" title="Edit this page" href="/w/index.php?title=Mobile_security&amp;action=edit"> <link rel="apple-touch-icon" href="/static/apple-touch/wikipedia.png"> <link rel="icon" href="/static/favicon/wikipedia.ico"> <link rel="search" type="application/opensearchdescription+xml" href="/w/rest.php/v1/search" title="Wikipedia (en)"> <link rel="EditURI" type="application/rsd+xml" href="//en.wikipedia.org/w/api.php?action=rsd"> <link rel="canonical" href="https://en.wikipedia.org/wiki/Mobile_security"> <link rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en"> <link rel="alternate" type="application/atom+xml" title="Wikipedia Atom feed" href="/w/index.php?title=Special:RecentChanges&amp;feed=atom"> <link rel="dns-prefetch" href="//meta.wikimedia.org" /> <link rel="dns-prefetch" href="//login.wikimedia.org"> </head> <body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject mw-editable page-Mobile_security rootpage-Mobile_security skin-vector-2022 action-view"><a class="mw-jump-link" href="#bodyContent">Jump to content</a> <div class="vector-header-container"> <header class="vector-header mw-header"> <div class="vector-header-start"> <nav class="vector-main-menu-landmark" aria-label="Site"> <div id="vector-main-menu-dropdown" class="vector-dropdown vector-main-menu-dropdown vector-button-flush-left vector-button-flush-right" > <input type="checkbox" id="vector-main-menu-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-main-menu-dropdown" class="vector-dropdown-checkbox " aria-label="Main menu" > <label id="vector-main-menu-dropdown-label" for="vector-main-menu-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-menu mw-ui-icon-wikimedia-menu"></span> <span class="vector-dropdown-label-text">Main menu</span> </label> <div class="vector-dropdown-content"> <div id="vector-main-menu-unpinned-container" class="vector-unpinned-container"> <div id="vector-main-menu" class="vector-main-menu vector-pinnable-element"> <div class="vector-pinnable-header vector-main-menu-pinnable-header vector-pinnable-header-unpinned" data-feature-name="main-menu-pinned" data-pinnable-element-id="vector-main-menu" data-pinned-container-id="vector-main-menu-pinned-container" data-unpinned-container-id="vector-main-menu-unpinned-container" > <div class="vector-pinnable-header-label">Main menu</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-main-menu.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-main-menu.unpin">hide</button> </div> <div id="p-navigation" class="vector-menu mw-portlet mw-portlet-navigation" > <div class="vector-menu-heading"> Navigation </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="n-mainpage-description" class="mw-list-item"><a href="/wiki/Main_Page" title="Visit the main page [z]" accesskey="z"><span>Main page</span></a></li><li id="n-contents" class="mw-list-item"><a href="/wiki/Wikipedia:Contents" title="Guides to browsing Wikipedia"><span>Contents</span></a></li><li id="n-currentevents" class="mw-list-item"><a href="/wiki/Portal:Current_events" title="Articles related to current events"><span>Current events</span></a></li><li id="n-randompage" class="mw-list-item"><a href="/wiki/Special:Random" title="Visit a randomly selected article [x]" accesskey="x"><span>Random article</span></a></li><li id="n-aboutsite" class="mw-list-item"><a href="/wiki/Wikipedia:About" title="Learn about Wikipedia and how it works"><span>About Wikipedia</span></a></li><li id="n-contactpage" class="mw-list-item"><a href="//en.wikipedia.org/wiki/Wikipedia:Contact_us" title="How to contact Wikipedia"><span>Contact us</span></a></li> </ul> </div> </div> <div id="p-interaction" class="vector-menu mw-portlet mw-portlet-interaction" > <div class="vector-menu-heading"> Contribute </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="n-help" class="mw-list-item"><a href="/wiki/Help:Contents" title="Guidance on how to use and edit Wikipedia"><span>Help</span></a></li><li id="n-introduction" class="mw-list-item"><a href="/wiki/Help:Introduction" title="Learn how to edit Wikipedia"><span>Learn to edit</span></a></li><li id="n-portal" class="mw-list-item"><a href="/wiki/Wikipedia:Community_portal" title="The hub for editors"><span>Community portal</span></a></li><li id="n-recentchanges" class="mw-list-item"><a href="/wiki/Special:RecentChanges" title="A list of recent changes to Wikipedia [r]" accesskey="r"><span>Recent changes</span></a></li><li id="n-upload" class="mw-list-item"><a href="/wiki/Wikipedia:File_upload_wizard" title="Add images or other media for use on Wikipedia"><span>Upload file</span></a></li> </ul> </div> </div> </div> </div> </div> </div> </nav> <a href="/wiki/Main_Page" class="mw-logo"> <img class="mw-logo-icon" src="/static/images/icons/wikipedia.png" alt="" aria-hidden="true" height="50" width="50"> <span class="mw-logo-container skin-invert"> <img class="mw-logo-wordmark" alt="Wikipedia" src="/static/images/mobile/copyright/wikipedia-wordmark-en.svg" style="width: 7.5em; height: 1.125em;"> <img class="mw-logo-tagline" alt="The Free Encyclopedia" src="/static/images/mobile/copyright/wikipedia-tagline-en.svg" width="117" height="13" style="width: 7.3125em; height: 0.8125em;"> </span> </a> </div> <div class="vector-header-end"> <div id="p-search" role="search" class="vector-search-box-vue vector-search-box-collapses vector-search-box-show-thumbnail vector-search-box-auto-expand-width vector-search-box"> <a href="/wiki/Special:Search" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only search-toggle" title="Search Wikipedia [f]" accesskey="f"><span class="vector-icon mw-ui-icon-search mw-ui-icon-wikimedia-search"></span> <span>Search</span> </a> <div class="vector-typeahead-search-container"> <div class="cdx-typeahead-search cdx-typeahead-search--show-thumbnail cdx-typeahead-search--auto-expand-width"> <form action="/w/index.php" id="searchform" class="cdx-search-input cdx-search-input--has-end-button"> <div id="simpleSearch" class="cdx-search-input__input-wrapper" data-search-loc="header-moved"> <div class="cdx-text-input cdx-text-input--has-start-icon"> <input class="cdx-text-input__input" type="search" name="search" placeholder="Search Wikipedia" aria-label="Search Wikipedia" autocapitalize="sentences" title="Search Wikipedia [f]" accesskey="f" id="searchInput" > <span class="cdx-text-input__icon cdx-text-input__start-icon"></span> </div> <input type="hidden" name="title" value="Special:Search"> </div> <button class="cdx-button cdx-search-input__end-button">Search</button> </form> </div> </div> </div> <nav class="vector-user-links vector-user-links-wide" aria-label="Personal tools"> <div class="vector-user-links-main"> <div id="p-vector-user-menu-preferences" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <div id="p-vector-user-menu-userpage" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <nav class="vector-appearance-landmark" aria-label="Appearance"> <div id="vector-appearance-dropdown" class="vector-dropdown " title="Change the appearance of the page&#039;s font size, width, and color" > <input type="checkbox" id="vector-appearance-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-appearance-dropdown" class="vector-dropdown-checkbox " aria-label="Appearance" > <label id="vector-appearance-dropdown-label" for="vector-appearance-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-appearance mw-ui-icon-wikimedia-appearance"></span> <span class="vector-dropdown-label-text">Appearance</span> </label> <div class="vector-dropdown-content"> <div id="vector-appearance-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <div id="p-vector-user-menu-notifications" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <div id="p-vector-user-menu-overflow" class="vector-menu mw-portlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-sitesupport-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="https://donate.wikimedia.org/wiki/Special:FundraiserRedirector?utm_source=donate&amp;utm_medium=sidebar&amp;utm_campaign=C13_en.wikipedia.org&amp;uselang=en" class=""><span>Donate</span></a> </li> <li id="pt-createaccount-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="/w/index.php?title=Special:CreateAccount&amp;returnto=Mobile+security" title="You are encouraged to create an account and log in; however, it is not mandatory" class=""><span>Create account</span></a> </li> <li id="pt-login-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="/w/index.php?title=Special:UserLogin&amp;returnto=Mobile+security" title="You&#039;re encouraged to log in; however, it&#039;s not mandatory. [o]" accesskey="o" class=""><span>Log in</span></a> </li> </ul> </div> </div> </div> <div id="vector-user-links-dropdown" class="vector-dropdown vector-user-menu vector-button-flush-right vector-user-menu-logged-out" title="Log in and more options" > <input type="checkbox" id="vector-user-links-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-user-links-dropdown" class="vector-dropdown-checkbox " aria-label="Personal tools" > <label id="vector-user-links-dropdown-label" for="vector-user-links-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-ellipsis mw-ui-icon-wikimedia-ellipsis"></span> <span class="vector-dropdown-label-text">Personal tools</span> </label> <div class="vector-dropdown-content"> <div id="p-personal" class="vector-menu mw-portlet mw-portlet-personal user-links-collapsible-item" title="User menu" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-sitesupport" class="user-links-collapsible-item mw-list-item"><a href="https://donate.wikimedia.org/wiki/Special:FundraiserRedirector?utm_source=donate&amp;utm_medium=sidebar&amp;utm_campaign=C13_en.wikipedia.org&amp;uselang=en"><span>Donate</span></a></li><li id="pt-createaccount" class="user-links-collapsible-item mw-list-item"><a href="/w/index.php?title=Special:CreateAccount&amp;returnto=Mobile+security" title="You are encouraged to create an account and log in; however, it is not mandatory"><span class="vector-icon mw-ui-icon-userAdd mw-ui-icon-wikimedia-userAdd"></span> <span>Create account</span></a></li><li id="pt-login" class="user-links-collapsible-item mw-list-item"><a href="/w/index.php?title=Special:UserLogin&amp;returnto=Mobile+security" title="You&#039;re encouraged to log in; however, it&#039;s not mandatory. [o]" accesskey="o"><span class="vector-icon mw-ui-icon-logIn mw-ui-icon-wikimedia-logIn"></span> <span>Log in</span></a></li> </ul> </div> </div> <div id="p-user-menu-anon-editor" class="vector-menu mw-portlet mw-portlet-user-menu-anon-editor" > <div class="vector-menu-heading"> Pages for logged out editors <a href="/wiki/Help:Introduction" aria-label="Learn more about editing"><span>learn more</span></a> </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-anoncontribs" class="mw-list-item"><a href="/wiki/Special:MyContributions" title="A list of edits made from this IP address [y]" accesskey="y"><span>Contributions</span></a></li><li id="pt-anontalk" class="mw-list-item"><a href="/wiki/Special:MyTalk" title="Discussion about edits from this IP address [n]" accesskey="n"><span>Talk</span></a></li> </ul> </div> </div> </div> </div> </nav> </div> </header> </div> <div class="mw-page-container"> <div class="mw-page-container-inner"> <div class="vector-sitenotice-container"> <div id="siteNotice"><!-- CentralNotice --></div> </div> <div class="vector-column-start"> <div class="vector-main-menu-container"> <div id="mw-navigation"> <nav id="mw-panel" class="vector-main-menu-landmark" aria-label="Site"> <div id="vector-main-menu-pinned-container" class="vector-pinned-container"> </div> </nav> </div> </div> <div class="vector-sticky-pinned-container"> <nav id="mw-panel-toc" aria-label="Contents" data-event-name="ui.sidebar-toc" class="mw-table-of-contents-container vector-toc-landmark"> <div id="vector-toc-pinned-container" class="vector-pinned-container"> <div id="vector-toc" class="vector-toc vector-pinnable-element"> <div class="vector-pinnable-header vector-toc-pinnable-header vector-pinnable-header-pinned" data-feature-name="toc-pinned" data-pinnable-element-id="vector-toc" > <h2 class="vector-pinnable-header-label">Contents</h2> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-toc.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-toc.unpin">hide</button> </div> <ul class="vector-toc-contents" id="mw-panel-toc-list"> <li id="toc-mw-content-text" class="vector-toc-list-item vector-toc-level-1"> <a href="#" class="vector-toc-link"> <div class="vector-toc-text">(Top)</div> </a> </li> <li id="toc-Challenges_of_smartphone_mobile_security" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Challenges_of_smartphone_mobile_security"> <div class="vector-toc-text"> <span class="vector-toc-numb">1</span> <span>Challenges of smartphone mobile security</span> </div> </a> <button aria-controls="toc-Challenges_of_smartphone_mobile_security-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle Challenges of smartphone mobile security subsection</span> </button> <ul id="toc-Challenges_of_smartphone_mobile_security-sublist" class="vector-toc-list"> <li id="toc-Threats" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Threats"> <div class="vector-toc-text"> <span class="vector-toc-numb">1.1</span> <span>Threats</span> </div> </a> <ul id="toc-Threats-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Consequences" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Consequences"> <div class="vector-toc-text"> <span class="vector-toc-numb">1.2</span> <span>Consequences</span> </div> </a> <ul id="toc-Consequences-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Attacks_based_on_communication" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Attacks_based_on_communication"> <div class="vector-toc-text"> <span class="vector-toc-numb">2</span> <span>Attacks based on communication</span> </div> </a> <button aria-controls="toc-Attacks_based_on_communication-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle Attacks based on communication subsection</span> </button> <ul id="toc-Attacks_based_on_communication-sublist" class="vector-toc-list"> <li id="toc-Attacks_based_on_SMS_and_MMS" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Attacks_based_on_SMS_and_MMS"> <div class="vector-toc-text"> <span class="vector-toc-numb">2.1</span> <span>Attacks based on SMS and MMS</span> </div> </a> <ul id="toc-Attacks_based_on_SMS_and_MMS-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Attacks_based_on_communication_networks" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Attacks_based_on_communication_networks"> <div class="vector-toc-text"> <span class="vector-toc-numb">2.2</span> <span>Attacks based on communication networks</span> </div> </a> <ul id="toc-Attacks_based_on_communication_networks-sublist" class="vector-toc-list"> <li id="toc-GSM_networks" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#GSM_networks"> <div class="vector-toc-text"> <span class="vector-toc-numb">2.2.1</span> <span>GSM networks</span> </div> </a> <ul id="toc-GSM_networks-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Wi-Fi" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Wi-Fi"> <div class="vector-toc-text"> <span class="vector-toc-numb">2.2.2</span> <span>Wi-Fi</span> </div> </a> <ul id="toc-Wi-Fi-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Bluetooth" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Bluetooth"> <div class="vector-toc-text"> <span class="vector-toc-numb">2.2.3</span> <span>Bluetooth</span> </div> </a> <ul id="toc-Bluetooth-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> </ul> </li> <li id="toc-Attacks_based_on_vulnerabilities_in_software_applications" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Attacks_based_on_vulnerabilities_in_software_applications"> <div class="vector-toc-text"> <span class="vector-toc-numb">3</span> <span>Attacks based on vulnerabilities in software applications</span> </div> </a> <button aria-controls="toc-Attacks_based_on_vulnerabilities_in_software_applications-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle Attacks based on vulnerabilities in software applications subsection</span> </button> <ul id="toc-Attacks_based_on_vulnerabilities_in_software_applications-sublist" class="vector-toc-list"> <li id="toc-Web_browser" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Web_browser"> <div class="vector-toc-text"> <span class="vector-toc-numb">3.1</span> <span>Web browser</span> </div> </a> <ul id="toc-Web_browser-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Operating_system" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Operating_system"> <div class="vector-toc-text"> <span class="vector-toc-numb">3.2</span> <span>Operating system</span> </div> </a> <ul id="toc-Operating_system-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Attacks_based_on_hardware_vulnerabilities" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Attacks_based_on_hardware_vulnerabilities"> <div class="vector-toc-text"> <span class="vector-toc-numb">4</span> <span>Attacks based on hardware vulnerabilities</span> </div> </a> <button aria-controls="toc-Attacks_based_on_hardware_vulnerabilities-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle Attacks based on hardware vulnerabilities subsection</span> </button> <ul id="toc-Attacks_based_on_hardware_vulnerabilities-sublist" class="vector-toc-list"> <li id="toc-Electromagnetic_waveforms" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Electromagnetic_waveforms"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.1</span> <span>Electromagnetic waveforms</span> </div> </a> <ul id="toc-Electromagnetic_waveforms-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Juice_jacking" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Juice_jacking"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.2</span> <span>Juice jacking</span> </div> </a> <ul id="toc-Juice_jacking-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Jailbreaking_and_rooting" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Jailbreaking_and_rooting"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.3</span> <span>Jailbreaking and rooting</span> </div> </a> <ul id="toc-Jailbreaking_and_rooting-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Password_cracking" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Password_cracking"> <div class="vector-toc-text"> <span class="vector-toc-numb">5</span> <span>Password cracking</span> </div> </a> <ul id="toc-Password_cracking-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Malicious_software_(malware)" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Malicious_software_(malware)"> <div class="vector-toc-text"> <span class="vector-toc-numb">6</span> <span>Malicious software (malware)</span> </div> </a> <button aria-controls="toc-Malicious_software_(malware)-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle Malicious software (malware) subsection</span> </button> <ul id="toc-Malicious_software_(malware)-sublist" class="vector-toc-list"> <li id="toc-Problematic_common_apps_and_pre-installed_software" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Problematic_common_apps_and_pre-installed_software"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.1</span> <span>Problematic common apps and pre-installed software</span> </div> </a> <ul id="toc-Problematic_common_apps_and_pre-installed_software-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Malware_attacks" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Malware_attacks"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.2</span> <span>Malware attacks</span> </div> </a> <ul id="toc-Malware_attacks-sublist" class="vector-toc-list"> <li id="toc-Infection" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Infection"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.2.1</span> <span>Infection</span> </div> </a> <ul id="toc-Infection-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Spread_to_other_systems" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Spread_to_other_systems"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.2.2</span> <span>Spread to other systems</span> </div> </a> <ul id="toc-Spread_to_other_systems-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Examples" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Examples"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.3</span> <span>Examples</span> </div> </a> <ul id="toc-Examples-sublist" class="vector-toc-list"> <li id="toc-Viruses_and_Trojans" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Viruses_and_Trojans"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.3.1</span> <span>Viruses and Trojans</span> </div> </a> <ul id="toc-Viruses_and_Trojans-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Ransomware" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Ransomware"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.3.2</span> <span>Ransomware</span> </div> </a> <ul id="toc-Ransomware-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Spyware" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Spyware"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.3.3</span> <span>Spyware</span> </div> </a> <ul id="toc-Spyware-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Portability_of_malware_across_platforms" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Portability_of_malware_across_platforms"> <div class="vector-toc-text"> <span class="vector-toc-numb">6.4</span> <span>Portability of malware across platforms</span> </div> </a> <ul id="toc-Portability_of_malware_across_platforms-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Countermeasures" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Countermeasures"> <div class="vector-toc-text"> <span class="vector-toc-numb">7</span> <span>Countermeasures</span> </div> </a> <button aria-controls="toc-Countermeasures-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle Countermeasures subsection</span> </button> <ul id="toc-Countermeasures-sublist" class="vector-toc-list"> <li id="toc-Security_in_operating_systems" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Security_in_operating_systems"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.1</span> <span>Security in operating systems</span> </div> </a> <ul id="toc-Security_in_operating_systems-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Security_software" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Security_software"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.2</span> <span>Security software</span> </div> </a> <ul id="toc-Security_software-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Resource_monitoring_in_the_smartphone" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Resource_monitoring_in_the_smartphone"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.3</span> <span>Resource monitoring in the smartphone</span> </div> </a> <ul id="toc-Resource_monitoring_in_the_smartphone-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Network_surveillance" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Network_surveillance"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.4</span> <span>Network surveillance</span> </div> </a> <ul id="toc-Network_surveillance-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Manufacturer_surveillance" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Manufacturer_surveillance"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.5</span> <span>Manufacturer surveillance</span> </div> </a> <ul id="toc-Manufacturer_surveillance-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-User_awareness" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#User_awareness"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.6</span> <span>User awareness</span> </div> </a> <ul id="toc-User_awareness-sublist" class="vector-toc-list"> <li id="toc-Enable_Android_Device_Encryption" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Enable_Android_Device_Encryption"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.6.1</span> <span>Enable Android Device Encryption</span> </div> </a> <ul id="toc-Enable_Android_Device_Encryption-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Centralized_storage" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Centralized_storage"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.7</span> <span>Centralized storage</span> </div> </a> <ul id="toc-Centralized_storage-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Limitations" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Limitations"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.8</span> <span>Limitations</span> </div> </a> <ul id="toc-Limitations-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Next_generation_of_mobile_security" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Next_generation_of_mobile_security"> <div class="vector-toc-text"> <span class="vector-toc-numb">7.9</span> <span>Next generation of mobile security</span> </div> </a> <ul id="toc-Next_generation_of_mobile_security-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-See_also" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#See_also"> <div class="vector-toc-text"> <span class="vector-toc-numb">8</span> <span>See also</span> </div> </a> <ul id="toc-See_also-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Notes" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Notes"> <div class="vector-toc-text"> <span class="vector-toc-numb">9</span> <span>Notes</span> </div> </a> <ul id="toc-Notes-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-References" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#References"> <div class="vector-toc-text"> <span class="vector-toc-numb">10</span> <span>References</span> </div> </a> <button aria-controls="toc-References-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle References subsection</span> </button> <ul id="toc-References-sublist" class="vector-toc-list"> <li id="toc-Books" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Books"> <div class="vector-toc-text"> <span class="vector-toc-numb">10.1</span> <span>Books</span> </div> </a> <ul id="toc-Books-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Articles" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Articles"> <div class="vector-toc-text"> <span class="vector-toc-numb">10.2</span> <span>Articles</span> </div> </a> <ul id="toc-Articles-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Websites" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Websites"> <div class="vector-toc-text"> <span class="vector-toc-numb">10.3</span> <span>Websites</span> </div> </a> <ul id="toc-Websites-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Further_reading" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Further_reading"> <div class="vector-toc-text"> <span class="vector-toc-numb">11</span> <span>Further reading</span> </div> </a> <ul id="toc-Further_reading-sublist" class="vector-toc-list"> </ul> </li> </ul> </div> </div> </nav> </div> </div> <div class="mw-content-container"> <main id="content" class="mw-body"> <header class="mw-body-header vector-page-titlebar"> <nav aria-label="Contents" class="vector-toc-landmark"> <div id="vector-page-titlebar-toc" class="vector-dropdown vector-page-titlebar-toc vector-button-flush-left" > <input type="checkbox" id="vector-page-titlebar-toc-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-page-titlebar-toc" class="vector-dropdown-checkbox " aria-label="Toggle the table of contents" > <label id="vector-page-titlebar-toc-label" for="vector-page-titlebar-toc-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-listBullet mw-ui-icon-wikimedia-listBullet"></span> <span class="vector-dropdown-label-text">Toggle the table of contents</span> </label> <div class="vector-dropdown-content"> <div id="vector-page-titlebar-toc-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <h1 id="firstHeading" class="firstHeading mw-first-heading"><span class="mw-page-title-main">Mobile security</span></h1> <div id="p-lang-btn" class="vector-dropdown mw-portlet mw-portlet-lang" > <input type="checkbox" id="p-lang-btn-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-p-lang-btn" class="vector-dropdown-checkbox mw-interlanguage-selector" aria-label="Go to an article in another language. Available in 15 languages" > <label id="p-lang-btn-label" for="p-lang-btn-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--action-progressive mw-portlet-lang-heading-15" aria-hidden="true" ><span class="vector-icon mw-ui-icon-language-progressive mw-ui-icon-wikimedia-language-progressive"></span> <span class="vector-dropdown-label-text">15 languages</span> </label> <div class="vector-dropdown-content"> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li class="interlanguage-link interwiki-ar mw-list-item"><a href="https://ar.wikipedia.org/wiki/%D8%A3%D9%85%D9%86_%D8%A7%D9%84%D9%87%D8%A7%D8%AA%D9%81_%D8%A7%D9%84%D9%85%D8%AD%D9%85%D9%88%D9%84" title="أمن الهاتف المحمول – Arabic" lang="ar" hreflang="ar" data-title="أمن الهاتف المحمول" data-language-autonym="العربية" data-language-local-name="Arabic" class="interlanguage-link-target"><span>العربية</span></a></li><li class="interlanguage-link interwiki-bg mw-list-item"><a href="https://bg.wikipedia.org/wiki/%D0%A1%D0%B8%D0%B3%D1%83%D1%80%D0%BD%D0%BE%D1%81%D1%82_%D0%BD%D0%B0_%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D0%BD%D0%B8%D1%82%D0%B5_%D1%82%D0%B5%D0%BB%D0%B5%D1%84%D0%BE%D0%BD%D0%B8" title="Сигурност на мобилните телефони – Bulgarian" lang="bg" hreflang="bg" data-title="Сигурност на мобилните телефони" data-language-autonym="Български" data-language-local-name="Bulgarian" class="interlanguage-link-target"><span>Български</span></a></li><li class="interlanguage-link interwiki-ca mw-list-item"><a href="https://ca.wikipedia.org/wiki/Seguretat_en_la_telefonia_m%C3%B2bil" title="Seguretat en la telefonia mòbil – Catalan" lang="ca" hreflang="ca" data-title="Seguretat en la telefonia mòbil" data-language-autonym="Català" data-language-local-name="Catalan" class="interlanguage-link-target"><span>Català</span></a></li><li class="interlanguage-link interwiki-de mw-list-item"><a href="https://de.wikipedia.org/wiki/Kryptohandy" title="Kryptohandy – German" lang="de" hreflang="de" data-title="Kryptohandy" data-language-autonym="Deutsch" data-language-local-name="German" class="interlanguage-link-target"><span>Deutsch</span></a></li><li class="interlanguage-link interwiki-es mw-list-item"><a href="https://es.wikipedia.org/wiki/Seguridad_en_telefon%C3%ADa_m%C3%B3vil" title="Seguridad en telefonía móvil – Spanish" lang="es" hreflang="es" data-title="Seguridad en telefonía móvil" data-language-autonym="Español" data-language-local-name="Spanish" class="interlanguage-link-target"><span>Español</span></a></li><li class="interlanguage-link interwiki-fa mw-list-item"><a href="https://fa.wikipedia.org/wiki/%D8%A7%D9%85%D9%86%DB%8C%D8%AA_%D9%85%D9%88%D8%A8%D8%A7%DB%8C%D9%84" title="امنیت موبایل – Persian" lang="fa" hreflang="fa" data-title="امنیت موبایل" data-language-autonym="فارسی" data-language-local-name="Persian" class="interlanguage-link-target"><span>فارسی</span></a></li><li class="interlanguage-link interwiki-fr mw-list-item"><a href="https://fr.wikipedia.org/wiki/S%C3%A9curit%C3%A9_logicielle_des_smartphones" title="Sécurité logicielle des smartphones – French" lang="fr" hreflang="fr" data-title="Sécurité logicielle des smartphones" data-language-autonym="Français" data-language-local-name="French" class="interlanguage-link-target"><span>Français</span></a></li><li class="interlanguage-link interwiki-ko mw-list-item"><a href="https://ko.wikipedia.org/wiki/%EB%AA%A8%EB%B0%94%EC%9D%BC_%EB%B3%B4%EC%95%88" title="모바일 보안 – Korean" lang="ko" hreflang="ko" data-title="모바일 보안" data-language-autonym="한국어" data-language-local-name="Korean" class="interlanguage-link-target"><span>한국어</span></a></li><li class="interlanguage-link interwiki-ks mw-list-item"><a href="https://ks.wikipedia.org/wiki/%D9%85%D9%88%D8%A8%D8%A7%D8%A6%D9%84_%D8%B3%DB%8C%DA%A9%D9%88%D8%B1%D9%B9%DB%8C" title="موبائل سیکورٹی – Kashmiri" lang="ks" hreflang="ks" data-title="موبائل سیکورٹی" data-language-autonym="कॉशुर / کٲشُر" data-language-local-name="Kashmiri" class="interlanguage-link-target"><span>कॉशुर / کٲشُر</span></a></li><li class="interlanguage-link interwiki-ml mw-list-item"><a href="https://ml.wikipedia.org/wiki/%E0%B4%AE%E0%B5%8A%E0%B4%AC%E0%B5%88%E0%B5%BD_%E0%B4%B8%E0%B5%81%E0%B4%B0%E0%B4%95%E0%B5%8D%E0%B4%B7" title="മൊബൈൽ സുരക്ഷ – Malayalam" lang="ml" hreflang="ml" data-title="മൊബൈൽ സുരക്ഷ" data-language-autonym="മലയാളം" data-language-local-name="Malayalam" class="interlanguage-link-target"><span>മലയാളം</span></a></li><li class="interlanguage-link interwiki-ru mw-list-item"><a href="https://ru.wikipedia.org/wiki/%D0%A2%D0%B5%D1%85%D0%BD%D0%BE%D0%BB%D0%BE%D0%B3%D0%B8%D0%B8_%D0%B7%D0%B0%D1%89%D0%B8%D1%82%D1%8B_%D1%82%D0%B5%D0%BB%D0%B5%D1%84%D0%BE%D0%BD%D0%BD%D1%8B%D1%85_%D0%BF%D0%B5%D1%80%D0%B5%D0%B3%D0%BE%D0%B2%D0%BE%D1%80%D0%BE%D0%B2" title="Технологии защиты телефонных переговоров – Russian" lang="ru" hreflang="ru" data-title="Технологии защиты телефонных переговоров" data-language-autonym="Русский" data-language-local-name="Russian" class="interlanguage-link-target"><span>Русский</span></a></li><li class="interlanguage-link interwiki-th mw-list-item"><a href="https://th.wikipedia.org/wiki/%E0%B8%84%E0%B8%A7%E0%B8%B2%E0%B8%A1%E0%B8%A1%E0%B8%B1%E0%B9%88%E0%B8%99%E0%B8%84%E0%B8%87%E0%B8%82%E0%B8%AD%E0%B8%87%E0%B8%AD%E0%B8%B8%E0%B8%9B%E0%B8%81%E0%B8%A3%E0%B8%93%E0%B9%8C%E0%B9%80%E0%B8%84%E0%B8%A5%E0%B8%B7%E0%B9%88%E0%B8%AD%E0%B8%99%E0%B8%97%E0%B8%B5%E0%B9%88" title="ความมั่นคงของอุปกรณ์เคลื่อนที่ – Thai" lang="th" hreflang="th" data-title="ความมั่นคงของอุปกรณ์เคลื่อนที่" data-language-autonym="ไทย" data-language-local-name="Thai" class="interlanguage-link-target"><span>ไทย</span></a></li><li class="interlanguage-link interwiki-tr mw-list-item"><a href="https://tr.wikipedia.org/wiki/Mobil_g%C3%BCvenlik" title="Mobil güvenlik – Turkish" lang="tr" hreflang="tr" data-title="Mobil güvenlik" data-language-autonym="Türkçe" data-language-local-name="Turkish" class="interlanguage-link-target"><span>Türkçe</span></a></li><li class="interlanguage-link interwiki-zh-yue mw-list-item"><a href="https://zh-yue.wikipedia.org/wiki/%E6%B5%81%E5%8B%95%E9%9B%BB%E8%A9%B1%E4%BF%9D%E5%AE%89" title="流動電話保安 – Cantonese" lang="yue" hreflang="yue" data-title="流動電話保安" data-language-autonym="粵語" data-language-local-name="Cantonese" class="interlanguage-link-target"><span>粵語</span></a></li><li class="interlanguage-link interwiki-zh mw-list-item"><a href="https://zh.wikipedia.org/wiki/%E7%A7%BB%E5%8B%95%E5%AE%89%E5%85%A8" title="移動安全 – Chinese" lang="zh" hreflang="zh" data-title="移動安全" data-language-autonym="中文" data-language-local-name="Chinese" class="interlanguage-link-target"><span>中文</span></a></li> </ul> <div class="after-portlet after-portlet-lang"><span class="wb-langlinks-edit wb-langlinks-link"><a href="https://www.wikidata.org/wiki/Special:EntityPage/Q3268325#sitelinks-wikipedia" title="Edit interlanguage links" class="wbc-editpage">Edit links</a></span></div> </div> </div> </div> </header> <div class="vector-page-toolbar"> <div class="vector-page-toolbar-container"> <div id="left-navigation"> <nav aria-label="Namespaces"> <div id="p-associated-pages" class="vector-menu vector-menu-tabs mw-portlet mw-portlet-associated-pages" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-nstab-main" class="selected vector-tab-noicon mw-list-item"><a href="/wiki/Mobile_security" title="View the content page [c]" accesskey="c"><span>Article</span></a></li><li id="ca-talk" class="vector-tab-noicon mw-list-item"><a href="/wiki/Talk:Mobile_security" rel="discussion" title="Discuss improvements to the content page [t]" accesskey="t"><span>Talk</span></a></li> </ul> </div> </div> <div id="vector-variants-dropdown" class="vector-dropdown emptyPortlet" > <input type="checkbox" id="vector-variants-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-variants-dropdown" class="vector-dropdown-checkbox " aria-label="Change language variant" > <label id="vector-variants-dropdown-label" for="vector-variants-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet" aria-hidden="true" ><span class="vector-dropdown-label-text">English</span> </label> <div class="vector-dropdown-content"> <div id="p-variants" class="vector-menu mw-portlet mw-portlet-variants emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> </div> </div> </nav> </div> <div id="right-navigation" class="vector-collapsible"> <nav aria-label="Views"> <div id="p-views" class="vector-menu vector-menu-tabs mw-portlet mw-portlet-views" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-view" class="selected vector-tab-noicon mw-list-item"><a href="/wiki/Mobile_security"><span>Read</span></a></li><li id="ca-edit" class="vector-tab-noicon mw-list-item"><a href="/w/index.php?title=Mobile_security&amp;action=edit" title="Edit this page [e]" accesskey="e"><span>Edit</span></a></li><li id="ca-history" class="vector-tab-noicon mw-list-item"><a href="/w/index.php?title=Mobile_security&amp;action=history" title="Past revisions of this page [h]" accesskey="h"><span>View history</span></a></li> </ul> </div> </div> </nav> <nav class="vector-page-tools-landmark" aria-label="Page tools"> <div id="vector-page-tools-dropdown" class="vector-dropdown vector-page-tools-dropdown" > <input type="checkbox" id="vector-page-tools-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-page-tools-dropdown" class="vector-dropdown-checkbox " aria-label="Tools" > <label id="vector-page-tools-dropdown-label" for="vector-page-tools-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet" aria-hidden="true" ><span class="vector-dropdown-label-text">Tools</span> </label> <div class="vector-dropdown-content"> <div id="vector-page-tools-unpinned-container" class="vector-unpinned-container"> <div id="vector-page-tools" class="vector-page-tools vector-pinnable-element"> <div class="vector-pinnable-header vector-page-tools-pinnable-header vector-pinnable-header-unpinned" data-feature-name="page-tools-pinned" data-pinnable-element-id="vector-page-tools" data-pinned-container-id="vector-page-tools-pinned-container" data-unpinned-container-id="vector-page-tools-unpinned-container" > <div class="vector-pinnable-header-label">Tools</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-page-tools.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-page-tools.unpin">hide</button> </div> <div id="p-cactions" class="vector-menu mw-portlet mw-portlet-cactions emptyPortlet vector-has-collapsible-items" title="More options" > <div class="vector-menu-heading"> Actions </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-more-view" class="selected vector-more-collapsible-item mw-list-item"><a href="/wiki/Mobile_security"><span>Read</span></a></li><li id="ca-more-edit" class="vector-more-collapsible-item mw-list-item"><a href="/w/index.php?title=Mobile_security&amp;action=edit" title="Edit this page [e]" accesskey="e"><span>Edit</span></a></li><li id="ca-more-history" class="vector-more-collapsible-item mw-list-item"><a href="/w/index.php?title=Mobile_security&amp;action=history"><span>View history</span></a></li> </ul> </div> </div> <div id="p-tb" class="vector-menu mw-portlet mw-portlet-tb" > <div class="vector-menu-heading"> General </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="t-whatlinkshere" class="mw-list-item"><a href="/wiki/Special:WhatLinksHere/Mobile_security" title="List of all English Wikipedia pages containing links to this page [j]" accesskey="j"><span>What links here</span></a></li><li id="t-recentchangeslinked" class="mw-list-item"><a href="/wiki/Special:RecentChangesLinked/Mobile_security" rel="nofollow" title="Recent changes in pages linked from this page [k]" accesskey="k"><span>Related changes</span></a></li><li id="t-upload" class="mw-list-item"><a href="/wiki/Wikipedia:File_Upload_Wizard" title="Upload files [u]" accesskey="u"><span>Upload file</span></a></li><li id="t-specialpages" class="mw-list-item"><a href="/wiki/Special:SpecialPages" title="A list of all special pages [q]" accesskey="q"><span>Special pages</span></a></li><li id="t-permalink" class="mw-list-item"><a href="/w/index.php?title=Mobile_security&amp;oldid=1255553561" title="Permanent link to this revision of this page"><span>Permanent link</span></a></li><li id="t-info" class="mw-list-item"><a href="/w/index.php?title=Mobile_security&amp;action=info" title="More information about this page"><span>Page information</span></a></li><li id="t-cite" class="mw-list-item"><a href="/w/index.php?title=Special:CiteThisPage&amp;page=Mobile_security&amp;id=1255553561&amp;wpFormIdentifier=titleform" title="Information on how to cite this page"><span>Cite this page</span></a></li><li id="t-urlshortener" class="mw-list-item"><a href="/w/index.php?title=Special:UrlShortener&amp;url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FMobile_security"><span>Get shortened URL</span></a></li><li id="t-urlshortener-qrcode" class="mw-list-item"><a href="/w/index.php?title=Special:QrCode&amp;url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FMobile_security"><span>Download QR code</span></a></li> </ul> </div> </div> <div id="p-coll-print_export" class="vector-menu mw-portlet mw-portlet-coll-print_export" > <div class="vector-menu-heading"> Print/export </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="coll-download-as-rl" class="mw-list-item"><a href="/w/index.php?title=Special:DownloadAsPdf&amp;page=Mobile_security&amp;action=show-download-screen" title="Download this page as a PDF file"><span>Download as PDF</span></a></li><li id="t-print" class="mw-list-item"><a href="/w/index.php?title=Mobile_security&amp;printable=yes" title="Printable version of this page [p]" accesskey="p"><span>Printable version</span></a></li> </ul> </div> </div> <div id="p-wikibase-otherprojects" class="vector-menu mw-portlet mw-portlet-wikibase-otherprojects" > <div class="vector-menu-heading"> In other projects </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li class="wb-otherproject-link wb-otherproject-commons mw-list-item"><a href="https://commons.wikimedia.org/wiki/Category:Mobile_security" hreflang="en"><span>Wikimedia Commons</span></a></li><li id="t-wikibase" class="wb-otherproject-link wb-otherproject-wikibase-dataitem mw-list-item"><a href="https://www.wikidata.org/wiki/Special:EntityPage/Q3268325" title="Structured data on this page hosted by Wikidata [g]" accesskey="g"><span>Wikidata item</span></a></li> </ul> </div> </div> </div> </div> </div> </div> </nav> </div> </div> </div> <div class="vector-column-end"> <div class="vector-sticky-pinned-container"> <nav class="vector-page-tools-landmark" aria-label="Page tools"> <div id="vector-page-tools-pinned-container" class="vector-pinned-container"> </div> </nav> <nav class="vector-appearance-landmark" aria-label="Appearance"> <div id="vector-appearance-pinned-container" class="vector-pinned-container"> <div id="vector-appearance" class="vector-appearance vector-pinnable-element"> <div class="vector-pinnable-header vector-appearance-pinnable-header vector-pinnable-header-pinned" data-feature-name="appearance-pinned" data-pinnable-element-id="vector-appearance" data-pinned-container-id="vector-appearance-pinned-container" data-unpinned-container-id="vector-appearance-unpinned-container" > <div class="vector-pinnable-header-label">Appearance</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-appearance.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-appearance.unpin">hide</button> </div> </div> </div> </nav> </div> </div> <div id="bodyContent" class="vector-body" aria-labelledby="firstHeading" data-mw-ve-target-container> <div class="vector-body-before-content"> <div class="mw-indicators"> </div> <div id="siteSub" class="noprint">From Wikipedia, the free encyclopedia</div> </div> <div id="contentSub"><div id="mw-content-subtitle"></div></div> <div id="mw-content-text" class="mw-body-content"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><div class="shortdescription nomobile noexcerpt noprint searchaux" style="display:none">Security risk and prevention for mobile devices</div> <style data-mw-deduplicate="TemplateStyles:r1236090951">.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}</style><div role="note" class="hatnote navigation-not-searchable">This article is about security threats to mobile devices. For using mobile devices for secure system access, see <a href="/wiki/Computer_security#Hardware_protection_mechanisms" title="Computer security">Computer security §&#160;Hardware protection mechanisms</a>.</div> <p><b>Mobile security</b>, or <b>mobile device security</b>, is the protection of <a href="/wiki/Smartphone" title="Smartphone">smartphones</a>, tablets, and <a href="/wiki/Laptop" title="Laptop">laptops</a> from threats associated with <a href="/wiki/Wireless_computing" class="mw-redirect" title="Wireless computing">wireless computing</a>.<sup id="cite_ref-:2_1-0" class="reference"><a href="#cite_note-:2-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup> It has become increasingly important in <a href="/wiki/Mobile_computing" title="Mobile computing">mobile computing</a>. The <a href="/wiki/Information_security" title="Information security">security</a> of personal and business information now stored on <a href="/wiki/Smartphones" class="mw-redirect" title="Smartphones">smartphones</a> is of particular concern.<sup id="cite_ref-FOOTNOTEFurnell200913CHAPTER_1:_GETTING_MOBILE_2-0" class="reference"><a href="#cite_note-FOOTNOTEFurnell200913CHAPTER_1:_GETTING_MOBILE-2"><span class="cite-bracket">&#91;</span>2<span class="cite-bracket">&#93;</span></a></sup> </p><p>Increasingly, users and businesses use smartphones not only to communicate, but also to plan and organize their work and private life. Within companies, these technologies are causing profound changes in the organization of <a href="/wiki/Information_systems" class="mw-redirect" title="Information systems">information systems</a> and have therefore become the source of new risks. Indeed, smartphones collect and compile an increasing amount of sensitive information to which access must be controlled to protect the <a href="/wiki/Information_privacy" title="Information privacy">privacy</a> of the <a href="/wiki/User_(computing)" title="User (computing)">user</a> and the <a href="/wiki/Intellectual_property" title="Intellectual property">intellectual property</a> of the company. </p><p>The majority of attacks are aimed at smartphones.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="Not supported by the details, and not according to some sources. (October 2023)">citation needed</span></a></i>&#93;</sup> These attacks take advantage of vulnerabilities discovered in smartphones that can result from different modes of communication, including <a href="/wiki/SMS" title="SMS">Short Message Service</a> (SMS, text messaging), <a href="/wiki/Multimedia_Messaging_Service" title="Multimedia Messaging Service">Multimedia Messaging Service</a> (MMS), <a href="/wiki/Wi-Fi" title="Wi-Fi">wireless connections</a>, <a href="/wiki/Bluetooth" title="Bluetooth">Bluetooth</a>, and <a href="/wiki/GSM" title="GSM">GSM</a>, the de facto international standard for mobile communications. Smartphone operating systems or browsers are another weakness. Some <a href="/wiki/Malware" title="Malware">malware</a> makes use of the common user's limited knowledge. Only 2.1% of users reported having first-hand contact with <a href="/wiki/Mobile_malware" title="Mobile malware">mobile malware</a>, according to a 2008 McAfee study, which found that 11.6% of users had heard of someone else being harmed by the problem. Yet, it is predicted that this number will rise.<sup id="cite_ref-abiresearch.com_3-0" class="reference"><a href="#cite_note-abiresearch.com-3"><span class="cite-bracket">&#91;</span>3<span class="cite-bracket">&#93;</span></a></sup> </p><p>Security <a href="/wiki/Countermeasure_(computer)" title="Countermeasure (computer)">countermeasures</a> are being developed and applied to smartphones, from security best practices in software to the dissemination of information to end users. Countermeasures can be implemented at all levels, including <a href="/wiki/Operating_system" title="Operating system">operating system</a> development, software design, and user behavior modifications. </p> <meta property="mw:PageProp/toc" /> <div class="mw-heading mw-heading2"><h2 id="Challenges_of_smartphone_mobile_security">Challenges of smartphone mobile security</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=1" title="Edit section: Challenges of smartphone mobile security"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <div class="mw-heading mw-heading3"><h3 id="Threats">Threats</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=2" title="Edit section: Threats"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <style data-mw-deduplicate="TemplateStyles:r1251242444">.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}</style><table class="box-More_citations_needed plainlinks metadata ambox ambox-content ambox-Refimprove" role="presentation"><tbody><tr><td class="mbox-image"><div class="mbox-image-div"><span typeof="mw:File"><a href="/wiki/File:Question_book-new.svg" class="mw-file-description"><img alt="" src="//upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/50px-Question_book-new.svg.png" decoding="async" width="50" height="39" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/75px-Question_book-new.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/100px-Question_book-new.svg.png 2x" data-file-width="512" data-file-height="399" /></a></span></div></td><td class="mbox-text"><div class="mbox-text-span">This section <b>needs additional citations for <a href="/wiki/Wikipedia:Verifiability" title="Wikipedia:Verifiability">verification</a></b>.<span class="hide-when-compact"> Please help <a href="/wiki/Special:EditPage/Mobile_security" title="Special:EditPage/Mobile security">improve this article</a> by <a href="/wiki/Help:Referencing_for_beginners" title="Help:Referencing for beginners">adding citations to reliable sources</a>&#32;in this section. Unsourced material may be challenged and removed.<br /><small><span class="plainlinks"><i>Find sources:</i>&#160;<a rel="nofollow" class="external text" href="https://www.google.com/search?as_eq=wikipedia&amp;q=%22Mobile+security%22">"Mobile security"</a>&#160;–&#160;<a rel="nofollow" class="external text" href="https://www.google.com/search?tbm=nws&amp;q=%22Mobile+security%22+-wikipedia&amp;tbs=ar:1">news</a>&#160;<b>·</b> <a rel="nofollow" class="external text" href="https://www.google.com/search?&amp;q=%22Mobile+security%22&amp;tbs=bkt:s&amp;tbm=bks">newspapers</a>&#160;<b>·</b> <a rel="nofollow" class="external text" href="https://www.google.com/search?tbs=bks:1&amp;q=%22Mobile+security%22+-wikipedia">books</a>&#160;<b>·</b> <a rel="nofollow" class="external text" href="https://scholar.google.com/scholar?q=%22Mobile+security%22">scholar</a>&#160;<b>·</b> <a rel="nofollow" class="external text" href="https://www.jstor.org/action/doBasicSearch?Query=%22Mobile+security%22&amp;acc=on&amp;wc=on">JSTOR</a></span></small></span> <span class="date-container"><i>(<span class="date">October 2023</span>)</i></span><span class="hide-when-compact"><i> (<small><a href="/wiki/Help:Maintenance_template_removal" title="Help:Maintenance template removal">Learn how and when to remove this message</a></small>)</i></span></div></td></tr></tbody></table> <p>A smartphone user is exposed to various threats when they use their phone. In just the last two quarters of 2012, the number of unique mobile threats grew by 261%, according to <a href="/w/index.php?title=ABI_Research&amp;action=edit&amp;redlink=1" class="new" title="ABI Research (page does not exist)">ABI Research</a>.<sup id="cite_ref-abiresearch.com_3-1" class="reference"><a href="#cite_note-abiresearch.com-3"><span class="cite-bracket">&#91;</span>3<span class="cite-bracket">&#93;</span></a></sup> These threats can disrupt the operation of the smartphone and transmit or modify user data. Applications must guarantee privacy and integrity of the information they handle. In addition, since some apps could themselves be malware, their functionality and activities should be limited (for example, restricting the apps from accessing location information via the <a href="/wiki/Global_Positioning_System" title="Global Positioning System">Global Positioning System</a> (GPS), blocking access to the user's address book, preventing the transmission of data on the network, or sending SMS messages that are billed to the user).<sup id="cite_ref-:2_1-1" class="reference"><a href="#cite_note-:2-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup> Malicious apps can also be <a href="/wiki/Installation_(computer_programs)" title="Installation (computer programs)">installed</a> without the owners' permission or knowledge. </p><p><a href="/wiki/Vulnerability_(computing)" class="mw-redirect" title="Vulnerability (computing)">Vulnerability</a> in mobile devices refers to aspects of system security that are susceptible to attacks. A vulnerability occurs when there is system weakness, an attacker has access to the weakness, and the attacker has competency to exploit the weakness.<sup id="cite_ref-:2_1-2" class="reference"><a href="#cite_note-:2-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup> </p><p>Potential attackers began looking for vulnerabilities when Apple's <a href="/wiki/IPhone" title="IPhone">iPhone</a> and the first <a href="/wiki/Android_(operating_system)" title="Android (operating system)">Android</a> devices came onto the market. Since the introduction of apps (particularly mobile banking apps), which are vital targets for hackers, <a href="/wiki/Malware" title="Malware">malware</a> has been rampant. The Department of Homeland Security's <a href="/wiki/Computer_security" title="Computer security">cybersecurity</a> department claims that the number of vulnerable points in smartphone operating systems has increased.<sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Manual_of_Style/Dates_and_numbers#Chronological_items" title="Wikipedia:Manual of Style/Dates and numbers"><span title="Quantify and date the claim &quot;increased&quot;. What year? During what timeframe? From what old amount to what new amount? (March 2023)">when?</span></a></i>&#93;</sup> As mobile phones are connected to utilities and appliances, <a href="/wiki/Hacker" title="Hacker">hackers</a>, <a href="/wiki/Cybercrime" title="Cybercrime">cybercriminals</a>, and even intelligence officials have access to these devices.<sup id="cite_ref-:0_4-0" class="reference"><a href="#cite_note-:0-4"><span class="cite-bracket">&#91;</span>4<span class="cite-bracket">&#93;</span></a></sup> </p><p>Starting in 2011, it became increasingly popular to let employees use their own devices for work-related purposes. The Crowd Research Partners study, published in 2017, reports that during 2017, most businesses that mandated the use of mobile devices were subjected to malware attacks and breaches. It has become common for rogue applications to be installed on user devices without the user's permission. They breach privacy, which hinders the effectiveness of the devices.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (October 2023)">citation needed</span></a></i>&#93;</sup><sup class="noprint Inline-Template" style="margin-left:0.1em; white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Please_clarify" title="Wikipedia:Please clarify"><span title="It&#39;s unclear what this paragraph is meant to convey. It seems to consist of sentences conveying different messages with no coherence. (October 2023)">clarification needed</span></a></i>&#93;</sup> </p><p>Since the recent rise of mobile attacks, hackers have increasingly targeted smartphones through credential theft and snooping. The number of attacks targeting smartphones and other devices has risen by 50 percent.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (March 2023)">citation needed</span></a></i>&#93;</sup> According to the study,<sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Avoid_weasel_words" class="mw-redirect" title="Wikipedia:Avoid weasel words"><span title="The material near this tag possibly uses too vague attribution or weasel words. (March 2023)">which?</span></a></i>&#93;</sup> <a href="/wiki/Mobile_banking" title="Mobile banking">mobile banking</a> applications are responsible for the increase in attacks. </p><p>Malware—such as <a href="/wiki/Ransomware" title="Ransomware">ransomware</a>, <a href="/wiki/Computer_worm" title="Computer worm">worms</a>, <a href="/wiki/Botnet" title="Botnet">botnets</a>, <a href="/wiki/Trojan_horse_(computing)" title="Trojan horse (computing)">Trojans</a>, and <a href="/wiki/Virus_(computer)" class="mw-redirect" title="Virus (computer)">viruses</a>—have been developed to exploit vulnerabilities in mobile devices. Malware is distributed by attackers so they can gain access to private information or digitally harm a user. For example, should malware breach a user's banking service, it may be able to access their transaction information, their rights to <a href="/wiki/Login" title="Login">log in</a>, and their money. Some malware is developed with anti-detection techniques to avoid detection. Attackers who use malware can avoid detection by hiding <a href="/wiki/Intrusion_detection_system" title="Intrusion detection system">malicious code</a>. </p><p>Trojan-droppers can also avoid detection of malware. Despite the fact that the malware inside a device does not change, the dropper generates new <a href="/wiki/Hash_function" title="Hash function">hashes</a> each time. Additionally, droppers can also create a multitude of files, which can lead to the creation of viruses. Android mobile devices are prone to Trojan-droppers. The banking Trojans also enable attacks on the banking applications on the phone, which leads to the theft of data for use in stealing money and funds.<sup class="noprint Inline-Template" style="margin-left:0.1em; white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Please_clarify" title="Wikipedia:Please clarify"><span title="The previous sentences should be clarified: 1) is &#39;generating hashes&#39; the same thing of having polymorphic code? 2) are &#39;multitude of files&#39; mean having legitimate files mixed-in with trojan files? 3) why are Android devices &quot;more prone&quot; to Trojan-dropper in comparison with other malwares / devices (October 2023)">clarification needed</span></a></i>&#93;</sup> </p><p><a href="/wiki/IOS_jailbreaking" title="IOS jailbreaking">Jailbreaks</a> for <a href="/wiki/IOS" title="IOS">iOS</a> devices work by disabling the signing of codes on iPhones so that applications not downloaded from the App Store can be operated. In this way, all the protection layers offered by iOS are disrupted, exposing the device to malware. These outside applications don't run in a <a href="/wiki/Sandbox_(computer_security)" title="Sandbox (computer security)">sandbox</a>, which exposes potential security problems. Some attack vectors change the mobile devices' configuration settings by installing malicious credentials and <a href="/wiki/Virtual_private_network" title="Virtual private network">virtual private networks</a> (VPNs) to direct information to malicious systems. In addition, <a href="/wiki/Spyware" title="Spyware">spyware</a> can be installed on mobile devices in order to track an individual. </p><p>Triade malware comes pre-installed on some mobile devices. In addition to Haddad, there is Lotoor, which exploits vulnerabilities in the system to repackage legitimate applications.<sup id="cite_ref-:4_5-0" class="reference"><a href="#cite_note-:4-5"><span class="cite-bracket">&#91;</span>5<span class="cite-bracket">&#93;</span></a></sup> The devices are also vulnerable due to spyware and leaky behaviors through applications. Mobile devices are also effective conveyance systems for malware threats, breaches of information, and thefts. </p><p>Wi-Fi interference technologies can also attack mobile devices through potentially insecure networks. By compromising the network, hackers are able to gain access to key data. Devices connected to public networks are at risk of attacks. A VPN, on the other hand, can be used to secure networks. As soon as a system is threatened, an active VPN will operate. There are also social engineering techniques, such as <a href="/wiki/Phishing" title="Phishing">phishing</a>, in which unsuspecting victims are sent links to lead them to malicious websites. The attackers can then hack into the victim's device and copy all of its information. </p><p>Some mobile device attacks can be prevented. For example, containerization allows the creation of a hardware infrastructure that separates business data from other data. Additionally, network protection detects malicious traffic and rogue access points. Data security is also ensured through authentication.<sup id="cite_ref-:2_1-3" class="reference"><a href="#cite_note-:2-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup> </p><p>There are a number of threats to mobile devices, including annoyance, stealing money, invading privacy, propagation, and malicious tools.<sup id="cite_ref-Leavitt2011_6-0" class="reference"><a href="#cite_note-Leavitt2011-6"><span class="cite-bracket">&#91;</span>6<span class="cite-bracket">&#93;</span></a></sup> There are three prime targets for attackers:<sup id="cite_ref-FOOTNOTEBishop2004_7-0" class="reference"><a href="#cite_note-FOOTNOTEBishop2004-7"><span class="cite-bracket">&#91;</span>7<span class="cite-bracket">&#93;</span></a></sup> </p> <ol><li>Data – Smartphones are devices for data management and may contain sensitive data like <a href="/wiki/Credit_card" title="Credit card">credit card</a> numbers, authentication information, private information, activity logs (calendar, call logs).</li> <li>Identity – Smartphones are highly customizable, so the device or its contents can easily be associated with a specific person.</li> <li>Availability – Attacking a smartphone can limit or deprive a user's access to it.</li></ol> <p>Attacks on mobile security systems include: </p> <ul><li><a href="/wiki/Botnet" title="Botnet">Botnets</a> – Attackers infect multiple machines with malware that victims generally acquire via e-mail attachments or from compromised applications or websites. The malware then gives hackers remote control of "zombie" devices, which can then be instructed to perform harmful acts.<sup id="cite_ref-Leavitt2011_6-1" class="reference"><a href="#cite_note-Leavitt2011-6"><span class="cite-bracket">&#91;</span>6<span class="cite-bracket">&#93;</span></a></sup></li> <li>Malicious applications – Hackers upload malicious programs or games to third-party smartphone application marketplaces. The programs steal personal information and open backdoor communication channels to install additional applications and cause other problems.<sup id="cite_ref-Leavitt2011_6-2" class="reference"><a href="#cite_note-Leavitt2011-6"><span class="cite-bracket">&#91;</span>6<span class="cite-bracket">&#93;</span></a></sup></li> <li>Malicious links on social networks – An effective way to spread malware where hackers can place Trojans, spyware, and backdoors.<sup id="cite_ref-Leavitt2011_6-3" class="reference"><a href="#cite_note-Leavitt2011-6"><span class="cite-bracket">&#91;</span>6<span class="cite-bracket">&#93;</span></a></sup></li> <li><a href="/wiki/Spyware" title="Spyware">Spyware</a> – Hackers use this to hijack phones, allowing them to hear calls, see text messages and e-mails, and <a href="/wiki/Mobile_phone_tracking" title="Mobile phone tracking">track a user's location</a> through GPS updates.<sup id="cite_ref-Leavitt2011_6-4" class="reference"><a href="#cite_note-Leavitt2011-6"><span class="cite-bracket">&#91;</span>6<span class="cite-bracket">&#93;</span></a></sup></li></ul> <p>The source of these attacks are the same actors found in the non-mobile computing space:<sup id="cite_ref-FOOTNOTEBishop2004_7-1" class="reference"><a href="#cite_note-FOOTNOTEBishop2004-7"><span class="cite-bracket">&#91;</span>7<span class="cite-bracket">&#93;</span></a></sup> </p> <ul><li>Professionals, whether commercial or military, who focus on the three targets mentioned above. They steal sensitive data from the general public, as well as undertake industrial <a href="/wiki/Espionage" title="Espionage">espionage</a>. They will also use the identity of those attacked to achieve other attacks.</li> <li>Thieves who want to gain income through data or identities they have stolen. The thieves will attack many people to increase their potential income.</li> <li><a href="/wiki/Black_hat_(computer_security)" title="Black hat (computer security)">Black hat hackers</a> who specifically attack availability.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">&#91;</span>8<span class="cite-bracket">&#93;</span></a></sup><sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Verifiability" title="Wikipedia:Verifiability"><span title="The article doesn&#39;t describe availability attack. (October 2023)">failed verification</span></a></i>&#93;</sup> Their goal is to develop <a href="/wiki/Computer_virus" title="Computer virus">viruses</a>, and cause damage to the device.<sup id="cite_ref-:6_9-0" class="reference"><a href="#cite_note-:6-9"><span class="cite-bracket">&#91;</span>9<span class="cite-bracket">&#93;</span></a></sup><sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Verifiability" title="Wikipedia:Verifiability"><span title="This document doesn&#39;t describe black-hatter as someone who specifically creates computer viruses or tries to cause damage. (October 2023)">failed verification</span></a></i>&#93;</sup> In some cases, hackers have an interest in stealing data on devices.</li> <li><a href="/wiki/Grey_hat" title="Grey hat">Grey hat hackers</a> who reveal vulnerabilities.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">&#91;</span>10<span class="cite-bracket">&#93;</span></a></sup> Their goal is to expose vulnerabilities of the device.<sup id="cite_ref-:5_11-0" class="reference"><a href="#cite_note-:5-11"><span class="cite-bracket">&#91;</span>11<span class="cite-bracket">&#93;</span></a></sup> <a href="/wiki/Grey_hat" title="Grey hat">Grey hat</a> hackers do not intend on damaging the device or stealing data. <sup id="cite_ref-FOOTNOTEBilton2010_12-0" class="reference"><a href="#cite_note-FOOTNOTEBilton2010-12"><span class="cite-bracket">&#91;</span>12<span class="cite-bracket">&#93;</span></a></sup></li></ul> <div class="mw-heading mw-heading3"><h3 id="Consequences">Consequences</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=3" title="Edit section: Consequences"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>When a smartphone is infected by an attacker, the attacker can attempt several things: </p> <ul><li>The attacker can manipulate the smartphone as a <a href="/wiki/Zombie_(computer_science)" class="mw-redirect" title="Zombie (computer science)">zombie machine</a>: a machine with which the attacker can communicate and send commands which will be used to send unsolicited messages (<a href="/wiki/Email_spam" title="Email spam">spam</a>) via SMS or email.<sup id="cite_ref-FOOTNOTEGuoWangZhu20043_13-0" class="reference"><a href="#cite_note-FOOTNOTEGuoWangZhu20043-13"><span class="cite-bracket">&#91;</span>13<span class="cite-bracket">&#93;</span></a></sup></li> <li>The attacker can easily force the smartphone to make phone calls. For example, one can use the <a href="/wiki/API" title="API">API</a> (library that contains the basic functions not present in the smartphone) PhoneMakeCall by <a href="/wiki/Microsoft" title="Microsoft">Microsoft</a>, which collects telephone numbers from any source (such as <a href="/wiki/Yellow_pages" title="Yellow pages">yellow pages</a>) and then calls them.<sup id="cite_ref-FOOTNOTEGuoWangZhu20043_13-1" class="reference"><a href="#cite_note-FOOTNOTEGuoWangZhu20043-13"><span class="cite-bracket">&#91;</span>13<span class="cite-bracket">&#93;</span></a></sup> The attacker can use this method to call paid services, resulting in charges to the smartphone owner. Dangerously, the smartphone could call and disrupt <a href="/wiki/Emergency_service" title="Emergency service">emergency services</a>.<sup id="cite_ref-FOOTNOTEGuoWangZhu20043_13-2" class="reference"><a href="#cite_note-FOOTNOTEGuoWangZhu20043-13"><span class="cite-bracket">&#91;</span>13<span class="cite-bracket">&#93;</span></a></sup></li> <li>A compromised smartphone can record conversations between the user and others and send them to a third party.<sup id="cite_ref-FOOTNOTEGuoWangZhu20043_13-3" class="reference"><a href="#cite_note-FOOTNOTEGuoWangZhu20043-13"><span class="cite-bracket">&#91;</span>13<span class="cite-bracket">&#93;</span></a></sup> This can cause user privacy and industrial security problems.</li> <li>An attacker can also steal a user's identity, usurp their identity (with a copy of the user's <a href="/wiki/Subscriber_Identity_Module" class="mw-redirect" title="Subscriber Identity Module">SIM</a> card or even the telephone itself), and thus impersonate the owner. This raises security concerns in countries where smartphones can be used to place orders, view bank accounts, or are used as an identity card.<sup id="cite_ref-FOOTNOTEGuoWangZhu20043_13-4" class="reference"><a href="#cite_note-FOOTNOTEGuoWangZhu20043-13"><span class="cite-bracket">&#91;</span>13<span class="cite-bracket">&#93;</span></a></sup></li> <li>The attacker can reduce the usability of the smartphone, by discharging the battery.<sup id="cite_ref-FOOTNOTEDagonMartinStarder200412_14-0" class="reference"><a href="#cite_note-FOOTNOTEDagonMartinStarder200412-14"><span class="cite-bracket">&#91;</span>14<span class="cite-bracket">&#93;</span></a></sup> For example, they can launch an application that will run continuously on the smartphone processor, requiring a lot of energy and draining the battery. Frank Stajano and Ross Anderson first described this form of attack, calling it an attack of "battery exhaustion" or "sleep deprivation torture".<sup id="cite_ref-FOOTNOTEDixonMishra20103_15-0" class="reference"><a href="#cite_note-FOOTNOTEDixonMishra20103-15"><span class="cite-bracket">&#91;</span>15<span class="cite-bracket">&#93;</span></a></sup></li> <li>The attacker can make the smartphone unusable.<sup id="cite_ref-FOOTNOTETöyssyHelenius2006113_16-0" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup> This attack can delete the boot scripts, resulting in a phone without a functioning <a href="/wiki/Mobile_operating_system" title="Mobile operating system">operating system</a>; modify certain files to make it unusable, such as a script that launches at startup that forces the smartphone to restart; or embed a startup application that will empty the battery.<sup id="cite_ref-FOOTNOTEDixonMishra20103_15-1" class="reference"><a href="#cite_note-FOOTNOTEDixonMishra20103-15"><span class="cite-bracket">&#91;</span>15<span class="cite-bracket">&#93;</span></a></sup></li> <li>The attacker can remove the user's data, whether personal (photos, music, videos) or professional (contacts, calendars, notes).<sup id="cite_ref-FOOTNOTETöyssyHelenius2006113_16-1" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup></li></ul> <div class="mw-heading mw-heading2"><h2 id="Attacks_based_on_communication">Attacks based on communication</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=4" title="Edit section: Attacks based on communication"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <div class="mw-heading mw-heading3"><h3 id="Attacks_based_on_SMS_and_MMS">Attacks based on SMS and MMS</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=5" title="Edit section: Attacks based on SMS and MMS"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Some attacks derive from flaws in the management of <a href="/wiki/SMS" title="SMS">Short Message Service</a> (SMS) and <a href="/wiki/Multimedia_Messaging_Service" title="Multimedia Messaging Service">Multimedia Messaging Service</a> (MMS). </p><p>Some mobile phone models have problems in managing <a href="/wiki/Binary-coded_decimal" title="Binary-coded decimal">binary</a> SMS messages. By sending an ill-formed block, it is possible to cause the phone to restart, leading to the denial-of-service attacks. If a user with a <a href="/wiki/Siemens_S55" title="Siemens S55">Siemens S55</a> received a text message containing a <a href="/wiki/Chinese_characters" title="Chinese characters">Chinese character</a>, it would lead to a denial of service.<sup id="cite_ref-FOOTNOTESiemens20101_17-0" class="reference"><a href="#cite_note-FOOTNOTESiemens20101-17"><span class="cite-bracket">&#91;</span>17<span class="cite-bracket">&#93;</span></a></sup> In another case, while the standard requires that the maximum size of a Nokia Mail address is 32 characters, some <a href="/wiki/Nokia" title="Nokia">Nokia</a> phones did not verify this standard, so if a user enters an email address over 32 characters, that leads to complete dysfunction of the e-mail handler and puts it out of commission. This attack is called "curse of silence". A study on the safety of the SMS infrastructure revealed that SMS messages sent from the <a href="/wiki/Internet" title="Internet">Internet</a> can be used to perform a <a href="/wiki/Ddos#Distributed_attack" class="mw-redirect" title="Ddos">distributed denial of service</a> (DDoS) attack against the <a href="/wiki/Mobile_telephony" title="Mobile telephony">mobile telecommunications</a> infrastructure of a big city. The attack exploits the delays in the delivery of messages to overload the network. </p><p>Another potential attack could begin with a phone that sends an MMS to other phones, with an attachment. This attachment is infected with a virus. Upon receipt of the MMS, the user can choose to open the attachment. If it is opened, the phone is infected, and the virus sends an MMS with an infected attachment to all the contacts in the address book. There is a real-world example of this attack: the virus <a href="/wiki/Commwarrior_(computer_virus)" class="mw-redirect" title="Commwarrior (computer virus)">Commwarrior</a><sup id="cite_ref-FOOTNOTETöyssyHelenius2006113_16-2" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup> sends MMS messages (including an infected file) to all recipients in a mobile phone's address book. If a recipient installs the infected file, the virus repeats, sending messages to recipients taken from the new address book. </p> <div class="mw-heading mw-heading3"><h3 id="Attacks_based_on_communication_networks">Attacks based on communication networks</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=6" title="Edit section: Attacks based on communication networks"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <div class="mw-heading mw-heading4"><h4 id="GSM_networks">GSM networks</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=7" title="Edit section: GSM networks"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>The attacker may try to break the <a href="/wiki/Encryption" title="Encryption">encryption</a> of a <a href="/wiki/GSM" title="GSM">GSM mobile network</a>. The network encryption algorithms belong to the family of algorithms called <a href="/wiki/A5/1" title="A5/1">A5</a>. Due to the policy of <a href="/wiki/Security_through_obscurity" title="Security through obscurity">security through obscurity</a>, it has not been possible to openly test the robustness of these algorithms. There were originally two variants of the algorithm: <a href="/wiki/A5/1" title="A5/1">A5/1</a> and <a href="/wiki/A5/2" title="A5/2">A5/2</a> (stream ciphers), where the former was designed to be relatively strong, and the latter was purposely designed to be weak to allow easy <a href="/wiki/Cryptanalysis" title="Cryptanalysis">cryptanalysis</a> and eavesdropping. <a href="/wiki/ETSI" class="mw-redirect" title="ETSI">ETSI</a> forced some countries (typically outside Europe) to use A5/2. Since the encryption algorithm was made public, it was proved to be breakable: A5/2 could be broken on the fly, and A5/1 in about 6 hours.<sup id="cite_ref-FOOTNOTEGendrullis2008266_18-0" class="reference"><a href="#cite_note-FOOTNOTEGendrullis2008266-18"><span class="cite-bracket">&#91;</span>18<span class="cite-bracket">&#93;</span></a></sup> In July 2007, the <a href="/wiki/3GPP" title="3GPP">3GPP</a> approved a change request to prohibit the implementation of A5/2 in any new mobile phones, decommissioning the algorithm; it is no longer implemented in mobile phones. </p><p>Stronger public algorithms have been added to the GSM standard: the A5/3 and A5/4 (<a href="/wiki/Block_cipher" title="Block cipher">Block ciphers</a>), otherwise known as <a href="/wiki/KASUMI" title="KASUMI">KASUMI or UEA1</a><sup id="cite_ref-FOOTNOTEEuropean_Telecommunications_Standards_Institute20111_19-0" class="reference"><a href="#cite_note-FOOTNOTEEuropean_Telecommunications_Standards_Institute20111-19"><span class="cite-bracket">&#91;</span>19<span class="cite-bracket">&#93;</span></a></sup> published by ETSI. If the network does not support A5/1, or any other A5 algorithm implemented by the phone, then the base station can specify A5/0 which is the null algorithm, whereby the radio traffic is sent unencrypted. Even if mobile phones are able to use <a href="/wiki/3G" title="3G">3G</a> or <a href="/wiki/4G" title="4G">4G</a> (which have much stronger encryption than 2G GSM), the base station can downgrade the radio communication to 2G GSM and specify A5/0 (no encryption).<sup id="cite_ref-FOOTNOTEJøsangMiralabéDallot2015_20-0" class="reference"><a href="#cite_note-FOOTNOTEJøsangMiralabéDallot2015-20"><span class="cite-bracket">&#91;</span>20<span class="cite-bracket">&#93;</span></a></sup> This is the basis for eavesdropping attacks on mobile radio networks using a fake base station commonly called an <a href="/wiki/IMSI_catcher" class="mw-redirect" title="IMSI catcher">IMSI catcher</a>. </p><p>In addition, tracing of mobile terminals is difficult since each time the mobile terminal is accessing or being accessed by the network, a new temporary identity (TMSI) is allocated to the mobile terminal. The TMSI is used as the identity of the mobile terminal the next time it accesses the network. The TMSI is sent to the mobile terminal in encrypted messages.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (October 2023)">citation needed</span></a></i>&#93;</sup> </p><p>Once the encryption algorithm of GSM is broken, the attacker can intercept all unencrypted communications made by the victim's smartphone. </p> <div class="mw-heading mw-heading4"><h4 id="Wi-Fi">Wi-Fi</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=8" title="Edit section: Wi-Fi"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">See also: <a href="/wiki/Wi-Fi#Network_security" title="Wi-Fi">Wi-Fi §&#160;Network_security</a></div> <figure class="mw-halign-right" typeof="mw:File/Thumb"><a href="/wiki/File:EvilTwinWireless_en.jpg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/4/4a/EvilTwinWireless_en.jpg/350px-EvilTwinWireless_en.jpg" decoding="async" width="350" height="248" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/4/4a/EvilTwinWireless_en.jpg/525px-EvilTwinWireless_en.jpg 1.5x, //upload.wikimedia.org/wikipedia/commons/4/4a/EvilTwinWireless_en.jpg 2x" data-file-width="550" data-file-height="389" /></a><figcaption> Access Point spoofing</figcaption></figure> <p>An attacker can try to eavesdrop on Wi-Fi communications to derive information (e.g., username, password). This type of attack is not unique to smartphones, but they are very vulnerable to these attacks because often Wi-Fi is their only means of communication and access the internet. The security of wireless networks (<a href="/wiki/Wireless_LAN" title="Wireless LAN">WLAN</a>) is thus an important subject. </p><p>Initially, wireless networks were secured by <a href="/wiki/Wired_Equivalent_Privacy" title="Wired Equivalent Privacy">WEP</a> keys. The weakness of WEP is its short encryption key, which is the same for all connected clients. In addition, several reductions in the search space of the keys have been found by researchers. Now, most wireless networks are protected by the <a href="/wiki/Wi-Fi_Protected_Access" title="Wi-Fi Protected Access">WPA</a> security protocol. WPA is based on the <a href="/wiki/Temporal_Key_Integrity_Protocol" title="Temporal Key Integrity Protocol">Temporal Key Integrity Protocol</a> (TKIP), which was designed to allow migration from WEP to WPA on the equipment already deployed. The major improvements in security are the <a href="/wiki/Dynamic_encryption" title="Dynamic encryption">dynamic encryption</a> keys. For small networks, the WPA uses a "<a href="/wiki/Pre-shared_key" title="Pre-shared key">pre-shared key</a>" which is based on a shared key. Encryption can be vulnerable if the length of the shared key is short. With limited opportunities for input (i.e., only the numeric keypad), mobile phone users might define short encryption keys that contain only numbers. This increases the likelihood that an attacker succeeds with a brute-force attack. The successor to WPA, called <a href="/wiki/IEEE_802.11i-2004" title="IEEE 802.11i-2004">WPA2</a>, is supposed to be safe enough to withstand a brute force attack. </p><p>The ability to access free and fast Wi-Fi gives a business an edge over those who do not. Free Wi-Fi is usually provided by organizations such as airports, coffee shops, and restaurants for a number of reasons, including encouraging customers to spend more time and money on the premises, and helping users stay productive.<sup id="cite_ref-:2_1-4" class="reference"><a href="#cite_note-:2-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup> Another reason is enhancing customer tracking: many restaurants and coffee shops compile data about their customers so they can target advertisements directly to their devices.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (March 2023)">citation needed</span></a></i>&#93;</sup> This means that customers know what services the facility provides. Generally, individuals filter business premises based on Internet connections as another reason to gain a competitive edge. Network security is the responsibility of the organizations, as unsecured Wi-Fi networks are prone to numerous risks. The man-in-the-middle attack entails the interception and modification of data between parties. Additionally, malware can be distributed via the free Wi-Fi network and hackers can exploit software vulnerabilities to smuggle malware onto connected devices. It is also possible to eavesdrop and sniff Wi-Fi signals using special software and devices, capturing login credentials and hijacking accounts.<sup id="cite_ref-:6_9-1" class="reference"><a href="#cite_note-:6-9"><span class="cite-bracket">&#91;</span>9<span class="cite-bracket">&#93;</span></a></sup> </p><p>As with GSM, if the attacker succeeds in breaking the identification key, both the phone and the entire network it is connected to become exposed to attacks. </p><p>Many smartphones remember wireless LANs they have previously connected to, allowing users to not have to re-identify with each connection. However, an attacker could create a Wi-Fi access point twin with the same parameters and characteristics as a real network. By automatically connecting to the fraudulent network, a smartphone becomes susceptible to the attacker, who can intercept any unencrypted data.<sup id="cite_ref-Gittleson_2014_y120_21-0" class="reference"><a href="#cite_note-Gittleson_2014_y120-21"><span class="cite-bracket">&#91;</span>21<span class="cite-bracket">&#93;</span></a></sup> </p><p>Lasco is a worm that initially infects a remote device using the <a href="/wiki/SIS_(file_format)" title="SIS (file format)">SIS file format</a>,<sup id="cite_ref-FOOTNOTETöyssyHelenius200627_22-0" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius200627-22"><span class="cite-bracket">&#91;</span>22<span class="cite-bracket">&#93;</span></a></sup> a type of script file that can be executed by the system without user interaction. The smartphone thus believes the file to come from a trusted source and downloads it, infecting the machine.<sup id="cite_ref-FOOTNOTETöyssyHelenius200627_22-1" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius200627-22"><span class="cite-bracket">&#91;</span>22<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading4"><h4 id="Bluetooth">Bluetooth</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=9" title="Edit section: Bluetooth"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/Bluetooth#Security" title="Bluetooth">Bluetooth §&#160;Security</a></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">See also: <a href="/wiki/Bluesnarfing" title="Bluesnarfing">Bluesnarfing</a> and <a href="/wiki/Bluebugging" title="Bluebugging">Bluebugging</a></div> <p>Security issues related to Bluetooth on mobile devices have been studied and have shown numerous problems on different phones. One easy to exploit <a href="/wiki/Vulnerability_(computing)" class="mw-redirect" title="Vulnerability (computing)">vulnerability</a> is that unregistered services do not require authentication, and vulnerable applications have a <a href="/wiki/Virtual_COM_port" title="Virtual COM port">virtual serial port</a> used to control the phone. An attacker only needed to connect to the port to take full control of the device.<sup id="cite_ref-FOOTNOTEMulliner2006113_23-0" class="reference"><a href="#cite_note-FOOTNOTEMulliner2006113-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup> </p><p>In another example, an attacker sends a file via Bluetooth to a phone within range with Bluetooth in discovery mode. If the recipient accepts, a virus is transmitted. An example of this is a worm called Cabir.<sup id="cite_ref-FOOTNOTETöyssyHelenius2006113_16-3" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup> The worm searches for nearby phones with Bluetooth in discoverable mode and sends itself to the target device. The user must accept the incoming file and install the program, after which the worm infects the machine. </p> <div class="mw-heading mw-heading2"><h2 id="Attacks_based_on_vulnerabilities_in_software_applications">Attacks based on vulnerabilities in software applications</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=10" title="Edit section: Attacks based on vulnerabilities in software applications"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Other attacks are based on flaws in the OS or applications on the phone. </p> <div class="mw-heading mw-heading3"><h3 id="Web_browser">Web browser</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=11" title="Edit section: Web browser"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">See also: <a href="/wiki/Browser_security" title="Browser security">Browser security</a></div> <p>The <a href="/wiki/Mobile_web_browser" class="mw-redirect" title="Mobile web browser">mobile web browser</a> is an emerging attack vector for mobile devices. Just as common Web browsers, mobile web browsers are extended from pure web navigation with widgets and plug-ins or are completely native mobile browsers. </p><p><a href="/wiki/IOS_jailbreaking" title="IOS jailbreaking">Jailbreaking</a> the iPhone with firmware 1.1.1 was based entirely on vulnerabilities on the web browser.<sup id="cite_ref-FOOTNOTEDunhamAbu_NimehBecher2008225_24-0" class="reference"><a href="#cite_note-FOOTNOTEDunhamAbu_NimehBecher2008225-24"><span class="cite-bracket">&#91;</span>24<span class="cite-bracket">&#93;</span></a></sup> In this case, there was a vulnerability based on a <a href="/wiki/Stack_based_buffer_overflow" class="mw-redirect" title="Stack based buffer overflow">stack-based buffer overflow</a> in a library used by the web browser (<a href="/wiki/LibTIFF" title="LibTIFF">LibTIFF</a>). A similar vulnerability in the web browser for Android was discovered in October 2008.<sup id="cite_ref-:7_25-0" class="reference"><a href="#cite_note-:7-25"><span class="cite-bracket">&#91;</span>25<span class="cite-bracket">&#93;</span></a></sup> Like the iPhone vulnerability, it was due to an obsolete and vulnerable <a href="/wiki/Library_(computing)" title="Library (computing)">library</a>, but significantly differed in that Android's sandboxing architecture limited the effects of this vulnerability to the Web browser process. </p><p>Smartphones are also victims of classic Web <a href="/wiki/Piracy" title="Piracy">piracy</a> such as phishing, malicious websites, and background-running software. The big difference is that smartphones do not yet have strong <a href="/wiki/Antivirus_software" title="Antivirus software">antivirus software</a> available.<sup id="cite_ref-:3_26-0" class="reference"><a href="#cite_note-:3-26"><span class="cite-bracket">&#91;</span>26<span class="cite-bracket">&#93;</span></a></sup><sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Verifiability" title="Wikipedia:Verifiability"><span title="The article barely supports / does not directly support these two statements at all. (October 2023)">failed verification</span></a></i>&#93;</sup> </p><p>The Internet offers numerous interactive features that ensure a higher engagement rate, capture more and relevant data, and increase brand loyalty. Blogs, forums, social networks, and <a href="/wiki/Wiki" title="Wiki">wikis</a> are some of the most common interactive websites. Due to the tremendous growth of the Internet, there has been a rapid rise in the number of security breaches experienced by individuals and businesses. </p><p>Mobile browser users can balance usage and caution in several ways,<sup id="cite_ref-Usenix_27-0" class="reference"><a href="#cite_note-Usenix-27"><span class="cite-bracket">&#91;</span>27<span class="cite-bracket">&#93;</span></a></sup> such as reviewing computer security regularly, using secure and secret passwords, and correcting, upgrading, and replacing the necessary features. Installation of <a href="/wiki/Antivirus_software" title="Antivirus software">antivirus</a> and anti-spyware programs is the most effective way of protecting the computer, as they offer protection against malware, spyware, and viruses. Additionally, they use <a href="/wiki/Firewall_(computing)" title="Firewall (computing)">firewalls</a>, which are typically installed between trusted networks or devices and the Internet. By acting as a web server, the firewall prevents external users from accessing the internal computer system.<sup id="cite_ref-:8_28-0" class="reference"><a href="#cite_note-:8-28"><span class="cite-bracket">&#91;</span>28<span class="cite-bracket">&#93;</span></a></sup><sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Verifiability" title="Wikipedia:Verifiability"><span title="Source doesn&#39;t mention any of the prevention techniques found here. (October 2023)">failed verification</span></a></i>&#93;</sup> </p> <div class="mw-heading mw-heading3"><h3 id="Operating_system">Operating system</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=12" title="Edit section: Operating system"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">See also: <a href="/wiki/Operating_system#Security" title="Operating system">Operating system §&#160;Security</a></div> <p>Sometimes it is possible to overcome the security safeguards by modifying the <a href="/wiki/Mobile_operating_system" title="Mobile operating system">operating system</a> (OS) itself, such as the manipulation of <a href="/wiki/Firmware" title="Firmware">firmware</a> and malicious signature certificates. These attacks are difficult. </p><p>In 2004, vulnerabilities in <a href="/wiki/Virtual_machine" title="Virtual machine">virtual machines</a> running on certain devices were revealed. It was possible to bypass the <a href="/wiki/Bytecode" title="Bytecode">bytecode</a> verifier and access the native underlying operating system.<sup id="cite_ref-abiresearch.com_3-2" class="reference"><a href="#cite_note-abiresearch.com-3"><span class="cite-bracket">&#91;</span>3<span class="cite-bracket">&#93;</span></a></sup> The results of this research were not published in detail. The firmware security of Nokia's <a href="/wiki/Symbian" title="Symbian">Symbian</a> Platform Security Architecture (PSA) is based on a central configuration file called SWIPolicy. In 2008, it was possible to manipulate the Nokia firmware before it was installed. In fact, some downloadable versions of this file were human-readable, so it was possible to modify and change the image of the firmware. <sup id="cite_ref-FOOTNOTEBecher200965_29-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200965-29"><span class="cite-bracket">&#91;</span>29<span class="cite-bracket">&#93;</span></a></sup> This vulnerability was solved by an update from Nokia. </p><p>In theory, smartphones have an advantage over hard drives since the OS files are in <a href="/wiki/Read-only_memory" title="Read-only memory">read-only memory</a> (ROM) and cannot be changed by malware. However, in some systems it was possible to circumvent this: in the <a href="/wiki/Symbian_OS" class="mw-redirect" title="Symbian OS">Symbian OS</a>, it was possible to overwrite a file with a file of the same name.<sup id="cite_ref-FOOTNOTEBecher200965_29-1" class="reference"><a href="#cite_note-FOOTNOTEBecher200965-29"><span class="cite-bracket">&#91;</span>29<span class="cite-bracket">&#93;</span></a></sup> On the Windows OS, it was possible to change a pointer from a general configuration file to an editable file. </p><p>When an application is installed, the <a href="/wiki/Code_signing" title="Code signing">signing</a> of this application is verified by a series of <a href="/wiki/Public_key_certificate" title="Public key certificate">certificates</a>. One can create a valid <a href="/wiki/Digital_signature" title="Digital signature">signature</a> without using a valid certificate and add it to the list.<sup id="cite_ref-FOOTNOTEBecher200966_30-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200966-30"><span class="cite-bracket">&#91;</span>30<span class="cite-bracket">&#93;</span></a></sup> In the Symbian OS, all certificates are in the directory <code class="mw-highlight mw-highlight-lang-text mw-content-ltr" style="" dir="ltr">c:\resource\swicertstore\dat</code>. With firmware changes explained above, it is very easy to insert a seemingly valid but malicious certificate. </p><p><a href="/wiki/Android_(operating_system)" title="Android (operating system)">Android</a> is the OS that has been attacked the most, because it has the largest userbase. A cybersecurity company<sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Avoid_weasel_words" class="mw-redirect" title="Wikipedia:Avoid weasel words"><span title="The material near this tag possibly uses too vague attribution or weasel words. (March 2023)">which?</span></a></i>&#93;</sup> reported to have blocked about 18 million attacks in 2016.<sup id="cite_ref-31" class="reference"><a href="#cite_note-31"><span class="cite-bracket">&#91;</span>31<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading2"><h2 id="Attacks_based_on_hardware_vulnerabilities">Attacks based on hardware vulnerabilities</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=13" title="Edit section: Attacks based on hardware vulnerabilities"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <div class="mw-heading mw-heading3"><h3 id="Electromagnetic_waveforms">Electromagnetic waveforms</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=14" title="Edit section: Electromagnetic waveforms"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>In 2015, researchers at the French government agency <i><a href="/wiki/Agence_nationale_de_la_s%C3%A9curit%C3%A9_des_syst%C3%A8mes_d%27information" title="Agence nationale de la sécurité des systèmes d&#39;information">Agence nationale de la sécurité des systèmes d'information</a></i> (ANSSI, <abbr style="font-size:85%" title="literal translation">lit.</abbr><span style="white-space: nowrap;">&#8201;</span><span class="gloss-quot">'</span><span class="gloss-text">French National Agency for the Security of Information Systems</span><span class="gloss-quot">'</span>) demonstrated the capability to trigger the voice interface of certain smartphones remotely by using "specific <a href="/wiki/Electromagnetism" title="Electromagnetism">electromagnetic</a> waveforms".<sup id="cite_ref-:0_4-1" class="reference"><a href="#cite_note-:0-4"><span class="cite-bracket">&#91;</span>4<span class="cite-bracket">&#93;</span></a></sup> The exploit took advantage of antenna-properties of headphone wires while plugged into the audio-output jacks of the vulnerable smartphones and effectively spoofed audio input to inject commands via the audio interface.<sup id="cite_ref-:0_4-2" class="reference"><a href="#cite_note-:0-4"><span class="cite-bracket">&#91;</span>4<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading3"><h3 id="Juice_jacking">Juice jacking</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=15" title="Edit section: Juice jacking"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">See also: <a href="/wiki/Juice_jacking" title="Juice jacking">Juice jacking</a></div> <p>Juice jacking is a physical or hardware vulnerability specific to mobile platforms. Utilizing the dual purpose of the USB charge port, many devices have been susceptible to having data exfiltrated from, or malware installed onto, a mobile device by utilizing malicious charging <a href="/wiki/Kiosk_software" title="Kiosk software">kiosks</a> set up in public places or hidden in normal charge adapters. </p> <div class="mw-heading mw-heading3"><h3 id="Jailbreaking_and_rooting">Jailbreaking and rooting</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=16" title="Edit section: Jailbreaking and rooting"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Jailbreaking is also a physical access vulnerability, in which a mobile device user hacks into device to unlock it, exploiting weaknesses in the operating system. Mobile device users take control of their own device by jailbreaking it, allowing them to customize the interface by installing applications, change <a href="/wiki/Settings_(Windows)" title="Settings (Windows)">system settings</a> that are not allowed on the devices, tweak OS processes, and run uncertified programs. This openness exposes the device to a variety of malicious attacks which can compromise private data.<sup id="cite_ref-:4_5-1" class="reference"><a href="#cite_note-:4-5"><span class="cite-bracket">&#91;</span>5<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading2"><h2 id="Password_cracking">Password cracking</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=17" title="Edit section: Password cracking"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>In 2010, researchers from the University of Pennsylvania investigated the possibility of <a href="/wiki/Password_cracking" title="Password cracking">cracking a device's password</a> through a <a href="/wiki/Smudge_attack" title="Smudge attack">smudge attack</a> (literally imaging the finger smudges on the screen to discern the user's password).<sup id="cite_ref-Usenix_27-1" class="reference"><a href="#cite_note-Usenix-27"><span class="cite-bracket">&#91;</span>27<span class="cite-bracket">&#93;</span></a></sup> The researchers were able to discern the device password up to 68% of the time under certain conditions.<sup id="cite_ref-Usenix_27-2" class="reference"><a href="#cite_note-Usenix-27"><span class="cite-bracket">&#91;</span>27<span class="cite-bracket">&#93;</span></a></sup> Outsiders may perform over-the-shoulder surveillance on victims, such as watching specific keystrokes or pattern gestures, to unlock device password or passcode. </p> <div class="mw-heading mw-heading2"><h2 id="Malicious_software_(malware)"><span id="Malicious_software_.28malware.29"></span>Malicious software (malware)</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=18" title="Edit section: Malicious software (malware)"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/Mobile_malware" title="Mobile malware">Mobile malware</a></div><figure class="mw-halign-right" typeof="mw:File/Thumb"><a href="/wiki/File:Graphiquemalware_en.jpg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/6/6b/Graphiquemalware_en.jpg/450px-Graphiquemalware_en.jpg" decoding="async" width="450" height="258" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/6/6b/Graphiquemalware_en.jpg 1.5x" data-file-width="550" data-file-height="315" /></a><figcaption>Malware types based on number of infected smartphones (2009)<sup id="cite_ref-FOOTNOTESchmidtSchmidtBatyukClausen2009a3_32-0" class="reference"><a href="#cite_note-FOOTNOTESchmidtSchmidtBatyukClausen2009a3-32"><span class="cite-bracket">&#91;</span>32<span class="cite-bracket">&#93;</span></a></sup></figcaption></figure><p>As smartphones are a permanent point of access to the Internet (they are often turned on), they can be compromised with malware as easily as computers. A <a href="/wiki/Malware" title="Malware">malware</a> is a computer program that aims to harm the system in which it resides. </p><p><a href="/wiki/Trojan_horse_(computing)" title="Trojan horse (computing)">Trojans</a>, <a href="/wiki/Computer_worm" title="Computer worm">worms</a> and <a href="/wiki/Mobile_virus" class="mw-redirect" title="Mobile virus">viruses</a> are all considered malware. A Trojan is a program on a device that allows external users to connect discreetly. A worm is a program that reproduces on multiple computers across a network. A virus is a malicious software designed to spread to other computers by inserting itself into legitimate programs and running programs in parallel. </p><p>Malware is far less numerous and serious to smartphones as it is to computers. Nonetheless, recent studies show that the evolution of malware in smartphones have rocketed in the last few years posing a threat to analysis and detection.<sup id="cite_ref-:7_25-1" class="reference"><a href="#cite_note-:7-25"><span class="cite-bracket">&#91;</span>25<span class="cite-bracket">&#93;</span></a></sup> In 2017, mobile malware variants increased by 54%.<sup id="cite_ref-33" class="reference"><a href="#cite_note-33"><span class="cite-bracket">&#91;</span>33<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading3"><h3 id="Problematic_common_apps_and_pre-installed_software">Problematic common apps and pre-installed software</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=19" title="Edit section: Problematic common apps and pre-installed software"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Various common apps installed by millions can intrude on privacy, even if they were installed from a trusted software distribution service like the <a href="/wiki/Google_Play_Store" class="mw-redirect" title="Google Play Store">Google Play Store</a>. For example, in 2022 it was shown that the popular app <a href="/wiki/TikTok" title="TikTok">TikTok</a> collects a lot of data and is required to make it available to the <a href="/wiki/Chinese_Communist_Party" title="Chinese Communist Party">Chinese Communist Party</a> (CCP) due to a national security law. This includes personal information on millions of Americans. </p><p>The firmware and "stock software" preinstalled on devices – and updated with preinstalled software – can also have undesired components or privacy-intruding default configurations or substantial security vulnerabilities. In 2019, <a href="/w/index.php?title=Kryptowire&amp;action=edit&amp;redlink=1" class="new" title="Kryptowire (page does not exist)">Kryptowire</a> identified Android devices with malicious firmware that collected and transmitted sensitive data without users' consent. </p><p>Analysis of data traffic by popular smartphones running variants of Android found substantial by-default data collection and sharing with no opt-out by <a href="/wiki/Pre-installed_software" title="Pre-installed software">pre-installed software</a>.<sup id="cite_ref-34" class="reference"><a href="#cite_note-34"><span class="cite-bracket">&#91;</span>34<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-35" class="reference"><a href="#cite_note-35"><span class="cite-bracket">&#91;</span>35<span class="cite-bracket">&#93;</span></a></sup> This issue also can't be addressed by conventional security patches. Outgoing Internet traffic can be analyzed with <a href="/wiki/Packet_analyzer" title="Packet analyzer">packet analyzers</a> and with firewall apps like the <a href="/w/index.php?title=NetGuard&amp;action=edit&amp;redlink=1" class="new" title="NetGuard (page does not exist)">NetGuard</a> firewall app for Android that allows reading blocked traffic logs.<sup id="cite_ref-36" class="reference"><a href="#cite_note-36"><span class="cite-bracket">&#91;</span>36<span class="cite-bracket">&#93;</span></a></sup><sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs additional references to reliable sources. (November 2022)">additional citation(s) needed</span></a></i>&#93;</sup> </p> <div class="mw-heading mw-heading3"><h3 id="Malware_attacks">Malware attacks</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=20" title="Edit section: Malware attacks"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Typically, an attack on a smartphone made by malware takes place in three phases: the infection of a host, the accomplishment of its goal, and the spread of the malware to other systems. Malware often uses the resources offered by infected smartphones. It will use the output devices such as Bluetooth or <a href="/wiki/Infrared" title="Infrared">infrared</a>, but it may also use the address book or email address of the person to infect the user's acquaintances. The malware exploits the trust that is given to data sent by an acquaintance. </p> <div class="mw-heading mw-heading4"><h4 id="Infection">Infection</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=21" title="Edit section: Infection"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Infection is the method used by malware to gain access to the smartphone; it may exploit an internal vulnerability or rely on the gullibility of the user. Infections are classified into four classes according to their degree of user interaction:<sup id="cite_ref-FOOTNOTEBecher200987_37-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200987-37"><span class="cite-bracket">&#91;</span>37<span class="cite-bracket">&#93;</span></a></sup> </p> <ol><li>Explicit permission – The most benign interaction is to ask the user if it is allowed to infect the machine, clearly indicating its potential malicious behavior. This is typical behavior of a <a href="/wiki/Proof_of_concept#Security" title="Proof of concept">proof of concept</a> malware.</li> <li>Implied permission – This infection is based on the fact that the user has a habit of installing software. Most Trojans try to seduce the user into installing attractive applications (like games or useful applications) that actually contain malware.</li> <li>Common interaction – This infection is related to a common behavior, such as opening an MMS or email.</li> <li>No interaction – The device is infected without the user taking action. This class of infection is the most dangerous, as it is both unapproved and automatic.</li></ol> <p><b>Accomplishment of its goal</b> </p><p>Once the malware has infected a phone, it will also seek to accomplish its goal, which is usually one of the following:<sup id="cite_ref-FOOTNOTEBecher200988_38-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200988-38"><span class="cite-bracket">&#91;</span>38<span class="cite-bracket">&#93;</span></a></sup> </p> <ul><li>Monetary damages – The attacker can steal user data and either sell them to the same user or sell to a third party.</li> <li>Data or device damage – Malware can partially damage the device or delete or modify data on the device.</li> <li>Concealed damage – The two aforementioned types of damage are detectable, but the malware can also leave a <a href="/wiki/Backdoor_(computing)" title="Backdoor (computing)">backdoor</a> for future attacks or even conduct <a href="/wiki/Telephone_tapping" class="mw-redirect" title="Telephone tapping">wiretaps</a>.</li></ul> <div class="mw-heading mw-heading4"><h4 id="Spread_to_other_systems">Spread to other systems</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=22" title="Edit section: Spread to other systems"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Once the malware has infected a smartphone, it aims to spread to a new host.<sup id="cite_ref-FOOTNOTEMickensNoble20051_39-0" class="reference"><a href="#cite_note-FOOTNOTEMickensNoble20051-39"><span class="cite-bracket">&#91;</span>39<span class="cite-bracket">&#93;</span></a></sup> This usually occurs to proximate devices via Wi-Fi, Bluetooth, or infrared; or to remote networks via telephone calls, SMS, or emails. </p> <figure typeof="mw:File/Thumb"><a href="/wiki/File:MalwareEffect.png" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/a/a6/MalwareEffect.png/500px-MalwareEffect.png" decoding="async" width="500" height="340" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/a/a6/MalwareEffect.png/750px-MalwareEffect.png 1.5x, //upload.wikimedia.org/wikipedia/commons/a/a6/MalwareEffect.png 2x" data-file-width="888" data-file-height="604" /></a><figcaption> Diagram (in French) which ranks common smartphone malware behaviors by frequency.<sup id="cite_ref-FOOTNOTESchmidtSchmidtBatyukClausen2009a3_32-1" class="reference"><a href="#cite_note-FOOTNOTESchmidtSchmidtBatyukClausen2009a3-32"><span class="cite-bracket">&#91;</span>32<span class="cite-bracket">&#93;</span></a></sup> At least 50 malware varieties exhibit no negative behavior, except their ability to spread.<sup id="cite_ref-FOOTNOTESchmidtSchmidtBatyukClausen2009a3_32-2" class="reference"><a href="#cite_note-FOOTNOTESchmidtSchmidtBatyukClausen2009a3-32"><span class="cite-bracket">&#91;</span>32<span class="cite-bracket">&#93;</span></a></sup></figcaption></figure> <div class="mw-heading mw-heading3"><h3 id="Examples">Examples</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=23" title="Edit section: Examples"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <div class="mw-heading mw-heading4"><h4 id="Viruses_and_Trojans">Viruses and Trojans</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=24" title="Edit section: Viruses and Trojans"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/Mobile_virus" class="mw-redirect" title="Mobile virus">Mobile virus</a></div> <ul><li><a href="/wiki/Cabir_(computer_worm)" title="Cabir (computer worm)">Cabir</a> (also known as Caribe, SybmOS/Cabir, Symbian/Cabir, and EPOC.cabir) is the name of a computer worm developed in 2004, designed to infect mobile phones running <a href="/wiki/Symbian_OS" class="mw-redirect" title="Symbian OS">Symbian OS</a>. It is believed to have been the first computer worm able to infect mobile phones.</li> <li><a href="/wiki/Commwarrior-A" class="mw-redirect" title="Commwarrior-A">Commwarrior</a>, created on March 7, 2005, was the first worm able to infect many machines from MMS.<sup id="cite_ref-FOOTNOTETöyssyHelenius2006113_16-4" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup> It is sent as COMMWARRIOR.ZIP containing the file COMMWARRIOR.SIS. When this file is executed, Commwarrior attempts to connect to nearby devices by Bluetooth or infrared under a random name. It then attempts to send MMS message to the contacts in the smartphone with different header messages for each person, who receive the MMS and often open them without further verification.</li> <li>Phage was the first <a href="/wiki/Palm_OS" title="Palm OS">Palm OS</a> virus discovered.<sup id="cite_ref-FOOTNOTETöyssyHelenius2006113_16-5" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup> It transfers to the Palm from a PC via <a href="/wiki/Synchronization" title="Synchronization">synchronization</a>. It infects all applications in the smartphone and embeds its own code to function without the user and the system detecting it. From the system's perspective, all the applications behave as expected.</li> <li>RedBrowser is a Trojan based on <a href="/wiki/Java_(programming_language)" title="Java (programming language)">Java</a>.<sup id="cite_ref-FOOTNOTETöyssyHelenius2006113_16-6" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup> The Trojan masquerades as a program called "RedBrowser" which allows the user to visit WAP sites without a WAP connection. During application installation, the user sees a request on their phone that the application needs permission to send messages. If the user accepts, RedBrowser can send SMS to paid call centers. This program uses the smartphone's connection to social networks (e.g., <a href="/wiki/Facebook" title="Facebook">Facebook</a>, <a href="/wiki/Twitter" title="Twitter">Twitter</a>) to get the contact information for the user's acquaintances (provided the required permissions have been given) and will send them messages.</li> <li>WinCE.PmCryptic.A is a malicious software on Windows Mobile which aims to earn money for its authors. It uses the infestation of memory cards that are inserted in the smartphone to spread more effectively. <sup id="cite_ref-FOOTNOTERaboin2009272_40-0" class="reference"><a href="#cite_note-FOOTNOTERaboin2009272-40"><span class="cite-bracket">&#91;</span>40<span class="cite-bracket">&#93;</span></a></sup></li> <li>CardTrap is a virus that is available on different types of smartphones, which aims to deactivate the system and third-party applications. It works by replacing the files used to start the smartphone and applications to prevent them from executing.<sup id="cite_ref-FOOTNOTETöyssyHelenius2006114_41-0" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006114-41"><span class="cite-bracket">&#91;</span>41<span class="cite-bracket">&#93;</span></a></sup> There are different variants of this virus such as Cardtrap.A for SymbOS devices. It also infects the memory card with malware capable of infecting <a href="/wiki/Windows" class="mw-redirect" title="Windows">Windows</a>.</li> <li><a href="/wiki/Ghost_Push" title="Ghost Push">Ghost Push</a> is malicious software on Android OS which automatically <a href="/wiki/Rooting_(Android)" title="Rooting (Android)">roots</a> the Android device and installs malicious applications directly to system partition. It then unroots the device to prevent users from removing the threat by master reset (the threat can be removed only by reflashing). It cripples the system resources, executes quickly, and is hard to detect.</li></ul> <div class="mw-heading mw-heading4"><h4 id="Ransomware">Ransomware</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=25" title="Edit section: Ransomware"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Mobile ransomware is a type of malware that locks users out of their mobile devices in a pay-to-unlock-your-device ploy. It has significantly grown as a threat category since 2014.<sup id="cite_ref-42" class="reference"><a href="#cite_note-42"><span class="cite-bracket">&#91;</span>42<span class="cite-bracket">&#93;</span></a></sup> Mobile users are often less security-conscious – particularly as it pertains to scrutinizing applications and web links – and trust the mobile device's native protection capability. </p><p>Mobile ransomware poses a significant threat to businesses reliant on instant access and availability of their proprietary information and contacts. The likelihood of a traveling businessman paying a ransom to unlock their device is significantly higher since they are at a disadvantage given inconveniences such as timeliness and less direct access to IT staff. Recent ransomware attacks have caused many Internet-connected devices to not work and are costly for companies to recover from. </p> <div class="mw-heading mw-heading4"><h4 id="Spyware">Spyware</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=26" title="Edit section: Spyware"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/Spyware" title="Spyware">Spyware</a></div> <ul><li><a href="/wiki/Pegasus_(spyware)" title="Pegasus (spyware)">Pegasus</a> – In 2021, journalists and researchers reported the discovery of spyware developed and distributed by a private company which can and has been used to infect both iOS and Android smartphones often – partly via use of <a href="/wiki/Zero-day_(computing)" class="mw-redirect" title="Zero-day (computing)">0-day exploits</a> – without the need for any user-interaction or significant clues to the user. The spyware is then used to exfiltrate data, track user locations, capture film through its camera, and activate the microphone at any time.<sup id="cite_ref-43" class="reference"><a href="#cite_note-43"><span class="cite-bracket">&#91;</span>43<span class="cite-bracket">&#93;</span></a></sup></li> <li>Flexispy is a Symbian application that can be considered a Trojan. The program sends all information received and sent from the smartphone to a Flexispy server. It was originally created to protect children and spy on adulterous spouses.<sup id="cite_ref-FOOTNOTETöyssyHelenius2006113_16-7" class="reference"><a href="#cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-:8_28-1" class="reference"><a href="#cite_note-:8-28"><span class="cite-bracket">&#91;</span>28<span class="cite-bracket">&#93;</span></a></sup></li></ul> <div class="mw-heading mw-heading3"><h3 id="Portability_of_malware_across_platforms">Portability of malware across platforms</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=27" title="Edit section: Portability of malware across platforms"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Attackers can make their malware target multiple platforms. Some malware attacks operating systems but is able to spread across different systems. </p><p>To begin with, malware can use runtime environments like <a href="/wiki/Java_virtual_machine" title="Java virtual machine">Java virtual machine</a> or the <a href="/wiki/.NET_Framework" title=".NET Framework">.NET Framework</a>. They can also use other libraries present in many operating systems.<sup id="cite_ref-FOOTNOTEBecher200991-94_44-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200991-94-44"><span class="cite-bracket">&#91;</span>44<span class="cite-bracket">&#93;</span></a></sup> Some malware carries several executable files in order to run in multiple environments, utilizing these during the propagation process. In practice, this type of malware requires a connection between the two operating systems to use as an attack vector. Memory cards can be used for this purpose, or synchronization software can be used to propagate the virus. </p> <div class="mw-heading mw-heading2"><h2 id="Countermeasures">Countermeasures</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=28" title="Edit section: Countermeasures"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Mobile security is divided into different categories, as methods do not all act at the same level and are designed to prevent different threats. These methods range from the management of security by the operating system (protecting the system from corruption by an application) to the behavioral education of the user (preventing the installation of a suspicious software). </p> <div class="mw-heading mw-heading3"><h3 id="Security_in_operating_systems">Security in operating systems</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=29" title="Edit section: Security in operating systems"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>The first layer of security in a smartphone is the <a href="/wiki/Mobile_operating_system" title="Mobile operating system">operating system</a>. Beyond needing to handle the usual roles (e.g., <a href="/wiki/Resource_management" title="Resource management">resource management</a>, scheduling processes) on the device, it must also establish the protocols for introducing external applications and data without introducing risk.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (February 2017)">citation needed</span></a></i>&#93;</sup> </p><p>A central paradigm in mobile operating systems is the idea of a <a href="/wiki/Sandbox_(computer_security)" title="Sandbox (computer security)">sandbox</a>. Since smartphones are currently designed to accommodate many applications, they must have mechanisms to ensure these applications are safe for the phone itself, for other applications and data on the system, and for the user. If a malicious program reaches a mobile device, the vulnerable area presented by the system must be as small as possible. Sandboxing extends this idea to compartmentalize different processes, preventing them from interacting and damaging each other. Based on the history of operating systems, sandboxing has different implementations. For example, where <a href="/wiki/IOS" title="IOS">iOS</a> will focus on limiting access to its public API for applications from the App Store by default, Managed Open In allows you to restrict which apps can access which types of data. Android bases its sandboxing on its legacy of <a href="/wiki/Linux" title="Linux">Linux</a> and <a href="/wiki/TrustedBSD" class="mw-redirect" title="TrustedBSD">TrustedBSD</a>. </p><p>The following points highlight mechanisms implemented in operating systems, especially Android. </p> <dl><dt>Rootkit detectors</dt> <dd>The intrusion of a <a href="/wiki/Rootkit" title="Rootkit">rootkit</a> in the system is a great danger in the same way as on a computer. It is important to prevent such intrusions, and to be able to detect them as often as possible. Indeed, there is concern that with this type of malicious program, an attacker could partially or completely bypass the device security, or acquire administrator rights. If this happens, nothing prevents the attacker from studying or disabling the safety features that were circumvented, deploying the applications they want, or disseminating a method of intrusion by a rootkit to a wider audience.<sup id="cite_ref-FOOTNOTEBecher200912_45-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200912-45"><span class="cite-bracket">&#91;</span>45<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel20085-6_46-0" class="reference"><a href="#cite_note-FOOTNOTESchmidtSchmidtClausenYüksel20085-6-46"><span class="cite-bracket">&#91;</span>46<span class="cite-bracket">&#93;</span></a></sup></dd> <dd>An example of a defense mechanism against this is the <a href="/wiki/Chain_of_trust" title="Chain of trust">chain of trust</a> (such as in iOS). This mechanism relies on signatures from applications required to start the operating system, and a certificate signed by the manufacturer (Apple). In the event that the signature checks are inconclusive, the device detects this and stops the boot-up.<sup id="cite_ref-FOOTNOTEHalbronnSigwald20105-6_47-0" class="reference"><a href="#cite_note-FOOTNOTEHalbronnSigwald20105-6-47"><span class="cite-bracket">&#91;</span>47<span class="cite-bracket">&#93;</span></a></sup> If the operating system is compromised due to jailbreaking, rootkit detection may not work if it is disabled by the jailbreak method or software is loaded after jailbreak disables Rootkit Detection.</dd></dl> <dl><dt>Process isolation</dt> <dd>Android uses mechanisms of user process isolation inherited from Linux. Each application has a user associated with it, and a tuple (<a href="/wiki/User_Login" class="mw-redirect" title="User Login">UID</a>, <a href="/wiki/Group_identifier" title="Group identifier">GID</a>). This approach serves as a sandbox: while applications can be malicious, they cannot get out of the sandbox reserved for them by their identifiers, and thus cannot interfere with the proper functioning of the system. For example, since it is impossible for a process to end the process of another user, an application can thus not stop the execution of another application.<sup id="cite_ref-FOOTNOTEBecher200912_45-1" class="reference"><a href="#cite_note-FOOTNOTEBecher200912-45"><span class="cite-bracket">&#91;</span>45<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTERuff2011127_48-0" class="reference"><a href="#cite_note-FOOTNOTERuff2011127-48"><span class="cite-bracket">&#91;</span>48<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEHogbenDekker201050_49-0" class="reference"><a href="#cite_note-FOOTNOTEHogbenDekker201050-49"><span class="cite-bracket">&#91;</span>49<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel200850_50-0" class="reference"><a href="#cite_note-FOOTNOTESchmidtSchmidtClausenYüksel200850-50"><span class="cite-bracket">&#91;</span>50<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEShabtaiFledelKanonovElovici200910_51-0" class="reference"><a href="#cite_note-FOOTNOTEShabtaiFledelKanonovElovici200910-51"><span class="cite-bracket">&#91;</span>51<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>File permissions</dt> <dd>From the legacy of Linux, <a href="/wiki/Filesystem_permissions" class="mw-redirect" title="Filesystem permissions">filesystem permissions</a> mechanisms also help with sandboxing. Permissions prevent a process from editing any files it wants. It is therefore not possible to freely corrupt files necessary for the operation of another application or system. Furthermore, in Android there is the method of locking memory permissions. It is not possible to change the permissions of files installed on the SD card from the phone, and consequently it is impossible to install applications.<sup id="cite_ref-FOOTNOTEBecher200931_52-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200931-52"><span class="cite-bracket">&#91;</span>52<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel20083_53-0" class="reference"><a href="#cite_note-FOOTNOTESchmidtSchmidtClausenYüksel20083-53"><span class="cite-bracket">&#91;</span>53<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEShabtaiFledelKanonovElovici20097-8_54-0" class="reference"><a href="#cite_note-FOOTNOTEShabtaiFledelKanonovElovici20097-8-54"><span class="cite-bracket">&#91;</span>54<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Memory protection</dt> <dd>In the same way as on a computer, memory protection prevents <a href="/wiki/Privilege_escalation" title="Privilege escalation">privilege escalation</a>. This could occur if a process managed to reach an area allocated to other processes, where it could write in the memory of a process with rights superior to its own (with 'root' in the worst case) and perform actions beyond its permissions. It would suffice to insert function calls are authorized by the privileges of the malicious application.<sup id="cite_ref-FOOTNOTEShabtaiFledelKanonovElovici200910_51-1" class="reference"><a href="#cite_note-FOOTNOTEShabtaiFledelKanonovElovici200910-51"><span class="cite-bracket">&#91;</span>51<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Development through runtime environments</dt> <dd>Software is often developed in high-level languages, which can control what is being done by a running program. For example, <a href="/wiki/Java_virtual_machine" title="Java virtual machine">Java virtual machines</a> continuously monitor the actions of the execution threads they manage, monitor and assign resources, and prevent malicious actions. Buffer overflows can be prevented by these controls.<sup id="cite_ref-FOOTNOTEPandya200815_55-0" class="reference"><a href="#cite_note-FOOTNOTEPandya200815-55"><span class="cite-bracket">&#91;</span>55<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEBecher200922_56-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200922-56"><span class="cite-bracket">&#91;</span>56<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEShabtaiFledelKanonovElovici200910_51-2" class="reference"><a href="#cite_note-FOOTNOTEShabtaiFledelKanonovElovici200910-51"><span class="cite-bracket">&#91;</span>51<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <div class="mw-heading mw-heading3"><h3 id="Security_software">Security software</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=30" title="Edit section: Security software"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Above the operating system security, there is a layer of security software. This layer is composed of individual components to strengthen various vulnerabilities: prevent malware, intrusions, the identification of a user as a human, and user authentication. It contains software components that have learned from their experience with computer security; however, on smartphones, this software must deal with greater constraints (see <a href="#Limitations">limitations</a>). </p> <dl><dt>Antivirus and firewall</dt> <dd>An antivirus software can be deployed on a device to verify that it is not infected by a known threat, usually by signature detection software that detects malicious executable files. A mobile antivirus product would scan files and compare them against a database of known mobile malware code signatures.<sup id="cite_ref-Leavitt2011_6-5" class="reference"><a href="#cite_note-Leavitt2011-6"><span class="cite-bracket">&#91;</span>6<span class="cite-bracket">&#93;</span></a></sup></dd> <dd>A firewall, meanwhile, can watch over the existing traffic on the network and ensure that a malicious application does not seek to communicate through it. It may equally verify that an installed application does not seek to establish suspicious communication, which may prevent an intrusion attempt.<sup id="cite_ref-FOOTNOTEBecherFreilingHoffmannHolz201196_57-0" class="reference"><a href="#cite_note-FOOTNOTEBecherFreilingHoffmannHolz201196-57"><span class="cite-bracket">&#91;</span>57<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEBecher2009128_58-0" class="reference"><a href="#cite_note-FOOTNOTEBecher2009128-58"><span class="cite-bracket">&#91;</span>58<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEBecher2009140_59-0" class="reference"><a href="#cite_note-FOOTNOTEBecher2009140-59"><span class="cite-bracket">&#91;</span>59<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel20085-6_46-1" class="reference"><a href="#cite_note-FOOTNOTESchmidtSchmidtClausenYüksel20085-6-46"><span class="cite-bracket">&#91;</span>46<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Visual notifications</dt> <dd>In order to make the user aware of any abnormal actions, such as a call they did not initiate, one can link some functions to a visual notification that is impossible to circumvent. For example, when a call is triggered, the called number should always be displayed. Thus, if a call is triggered by a malicious application, the user can see, and take appropriate action.</dd></dl> <dl><dt>Turing test</dt> <dd>It is important to confirm certain actions by a user decision. The <a href="/wiki/Turing_test" title="Turing test">Turing test</a> is used to distinguish between a human and a virtual user, often in the form of a <a href="/wiki/CAPTCHA" title="CAPTCHA">CAPTCHA</a>.</dd></dl> <dl><dt>Biometric identification</dt> <dd>Another method to use is <a href="/wiki/Biometrics" title="Biometrics">biometrics</a>,<sup id="cite_ref-FOOTNOTEThirumathyamDerawi20101_60-0" class="reference"><a href="#cite_note-FOOTNOTEThirumathyamDerawi20101-60"><span class="cite-bracket">&#91;</span>60<span class="cite-bracket">&#93;</span></a></sup> a technique of identifying a person by means of their morphology (e.g., by <a href="/wiki/Facial_recognition_system" title="Facial recognition system">recognition of the face</a> or eye) or their behavior (e.g., their <a href="/wiki/Handwritten_biometric_recognition" title="Handwritten biometric recognition">signature or way of writing</a>). One advantage of using biometric security is that users can avoid having to remember a password or other secret combination to authenticate and prevent malicious users from accessing their devices. In a system with strong biometric security, only the primary user can access the smartphone.</dd></dl> <div class="mw-heading mw-heading3"><h3 id="Resource_monitoring_in_the_smartphone">Resource monitoring in the smartphone</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=31" title="Edit section: Resource monitoring in the smartphone"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Should a malicious application pass the security barriers, it can take the actions for which it was designed. However, this activity can be sometimes detected by monitoring the various resources used on the phone. Depending on the goals of the malware, the consequences of infection are not always the same; all malicious applications are not intended to harm the devices on which they are deployed.<sup id="cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel20087-12_61-0" class="reference"><a href="#cite_note-FOOTNOTESchmidtSchmidtClausenYüksel20087-12-61"><span class="cite-bracket">&#91;</span>61<span class="cite-bracket">&#93;</span></a></sup> </p><p>The following resources are only indications and do not provide certainty about the legitimacy of the activity of an application. However, these criteria can help target suspicious applications, especially if several criteria are combined. </p> <dl><dt>Battery</dt> <dd>Some malware is aimed at exhausting the energy resources of the phone. Monitoring the energy consumption of the phone can be a way to detect certain malware applications.<sup id="cite_ref-FOOTNOTEBecher200912_45-2" class="reference"><a href="#cite_note-FOOTNOTEBecher200912-45"><span class="cite-bracket">&#91;</span>45<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Memory usage</dt> <dd>Memory usage is inherent in any application. However, if one finds that an unnecessary or unexpected proportion of memory is used by an application, it may be flagged as suspicious.</dd></dl> <dl><dt>Network traffic</dt> <dd>As part of normal operation on a smartphone, many applications are bound to connect via the network. However, an application using a lot of bandwidth can be strongly suspected of attempting to communicate a lot of information and disseminate data to many other devices. This observation only allows a suspicion, because some legitimate applications can be very resource-intensive in terms of network communications, the best example being <a href="/wiki/Streaming_video" class="mw-redirect" title="Streaming video">streaming video</a>.</dd></dl> <dl><dt>Services</dt> <dd>One can monitor the activity of various services of a smartphone. During certain moments, some services should not be active, and if one is detected, the application should be suspected. For example, the sending of an SMS when the user is filming video: this communication does not make sense and is suspicious; malware may attempt to send SMS while its activity is masked.<sup id="cite_ref-FOOTNOTEBecher2009126_62-0" class="reference"><a href="#cite_note-FOOTNOTEBecher2009126-62"><span class="cite-bracket">&#91;</span>62<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <div class="mw-heading mw-heading3"><h3 id="Network_surveillance">Network surveillance</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=32" title="Edit section: Network surveillance"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p><a href="/wiki/Network_traffic" title="Network traffic">Network traffic</a> exchanged by phones can be monitored. One can place safeguards in network routing points in order to detect abnormal behavior. As the mobile's use of network protocols is much more constrained than that of a computer, expected network data streams can be predicted (e.g., the protocol for sending an SMS), which permits detection of anomalies in mobile networks.<sup id="cite_ref-FOOTNOTEMalik201628_63-0" class="reference"><a href="#cite_note-FOOTNOTEMalik201628-63"><span class="cite-bracket">&#91;</span>63<span class="cite-bracket">&#93;</span></a></sup> </p> <dl><dt>Spam filters</dt> <dd>Similar to email exchanges, <a href="/wiki/Spamming" title="Spamming">spam</a> can be detected through means of mobile communications (SMS, MMS). It is therefore possible to detect and minimize this kind of attempt by filters deployed on network infrastructure that is relaying these messages.</dd></dl> <dl><dt>Encryption of stored or transmitted information</dt> <dd>Because it is always possible that data exchanged can be intercepted, communications and information storage rely on encryption to prevent a malicious entity from using any data obtained during communications. However, this poses the problem of key exchange for encryption algorithms, which requires a secure channel.</dd></dl> <dl><dt>Telecom <a href="/wiki/Network_monitoring" title="Network monitoring">network monitoring</a></dt> <dd>The networks for SMS and MMS exhibit predictable behavior, and there is not as much liberty compared with what one can do with protocols such as <a href="/wiki/Transmission_Control_Protocol" title="Transmission Control Protocol">TCP</a> or UDP. This implies that one cannot predict the flow of data from common web protocols; a protocol might generate very little traffic by consulting simple pages (rarely) or generate heavy traffic by using video streaming. On the other hand, messages exchanged via mobile phone have a framework and a specific model, and the user does not, in a normal case, have the freedom to intervene in the details of these communications. Therefore, if an abnormality is found in the flux of network data in the mobile networks, the potential threat can be quickly detected.</dd></dl> <div class="mw-heading mw-heading3"><h3 id="Manufacturer_surveillance">Manufacturer surveillance</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=33" title="Edit section: Manufacturer surveillance"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>In the production and distribution chain for mobile devices, manufacturers are responsibility for ensuring that devices are delivered in a basic configuration without vulnerabilities. Most users are not experts and many of them are not aware of the existence of security vulnerabilities, so the device configuration as provided by manufacturers will be retained by many users. Some smartphone manufacturers add <a href="/wiki/Titan_M2" class="mw-redirect" title="Titan M2">Titan M2s</a> (a security hardware chip) to increase mobile security.<sup id="cite_ref-64" class="reference"><a href="#cite_note-64"><span class="cite-bracket">&#91;</span>64<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-65" class="reference"><a href="#cite_note-65"><span class="cite-bracket">&#91;</span>65<span class="cite-bracket">&#93;</span></a></sup> </p> <dl><dt>Remove debug mode</dt> <dd>Phones are sometimes set in a debug mode during manufacturing, but this mode must be disabled before the phone is sold. This mode allows access to features not intended for routine use by a user. Due to the speed of development and production, distractions occur, and some devices are sold in debug mode. This kind of deployment exposes mobile devices to exploits that utilize this oversight.<sup id="cite_ref-FOOTNOTEBecherFreilingHoffmannHolz2011101_66-0" class="reference"><a href="#cite_note-FOOTNOTEBecherFreilingHoffmannHolz2011101-66"><span class="cite-bracket">&#91;</span>66<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTERuff201111_67-0" class="reference"><a href="#cite_note-FOOTNOTERuff201111-67"><span class="cite-bracket">&#91;</span>67<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Default settings</dt> <dd>When a smartphone is sold, its default settings must be correct, and not leave security gaps. The default configuration is not always changed, so a good initial setup is essential for users. There are, for example, default configurations that are vulnerable to denial-of-service attacks.<sup id="cite_ref-FOOTNOTEBecher200912_45-3" class="reference"><a href="#cite_note-FOOTNOTEBecher200912-45"><span class="cite-bracket">&#91;</span>45<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEHogbenDekker201045_68-0" class="reference"><a href="#cite_note-FOOTNOTEHogbenDekker201045-68"><span class="cite-bracket">&#91;</span>68<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Security audit of apps</dt> <dd>App stores have emerged alongside smartphones. Both users and providers are tasked with examining the immense volume of apps available, from different points of view (e.g., security, content). Security audits should be particularly cautious, because if a fault is not detected, the application can spread very quickly within a few days, and infect a significant number of devices.<sup id="cite_ref-FOOTNOTEBecher200912_45-4" class="reference"><a href="#cite_note-FOOTNOTEBecher200912-45"><span class="cite-bracket">&#91;</span>45<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Detect suspicious applications demanding rights</dt> <dd>When installing applications, it is good to warn the user against sets of permissions that, grouped together, seem potentially dangerous, or at least suspicious. Frameworks like such as Kirin, on Android, attempt to detect and prohibit certain sets of permissions.<sup id="cite_ref-FOOTNOTEBecher200913_69-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200913-69"><span class="cite-bracket">&#91;</span>69<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Revocation procedures</dt> <dd>First developed for Android, a process known as 'remote revocation' can remotely and globally uninstall an application from any device that has it. This means the spread of a malicious application that evaded security checks can be immediately stopped when the threat is discovered.<sup id="cite_ref-FOOTNOTEBecher200934_70-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200934-70"><span class="cite-bracket">&#91;</span>70<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTERuff20117_71-0" class="reference"><a href="#cite_note-FOOTNOTERuff20117-71"><span class="cite-bracket">&#91;</span>71<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Avoid heavily customized systems</dt> <dd>Manufacturers are tempted to overlay custom layers on existing operating systems, with the dual purpose of offering customized options and disabling or charging for certain features. This has the dual effect of risking the introduction of new bugs in the system, coupled with an incentive for users to modify the systems to circumvent the manufacturer's restrictions. These systems are rarely as stable and reliable as the original and may suffer from phishing attempts or other exploits.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (April 2012)">citation needed</span></a></i>&#93;</sup></dd></dl> <dl><dt>Improve software patch processes</dt> <dd>New versions of various software components of a smartphone, including operating systems, are regularly published. These 'patches' correct flaws over time. Nevertheless, manufacturers often do not deploy these updates to their devices in a timely fashion, and sometimes not at all. Thus, vulnerabilities can persist when they could be corrected; while they exist and are generally known, they are easily exploitable.<sup id="cite_ref-FOOTNOTEBecher200913_69-1" class="reference"><a href="#cite_note-FOOTNOTEBecher200913-69"><span class="cite-bracket">&#91;</span>69<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <div class="mw-heading mw-heading3"><h3 id="User_awareness">User awareness</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=34" title="Edit section: User awareness"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>The user has a large responsibility in the cycle of security. This can be as simple as using a password, or as detailed as precisely controlling which permissions are granted to applications. This precaution is especially important if the user is an employee of a company who stores business data on the device. </p><p>Much malicious behavior is allowed by user carelessness. Smartphone users were found to ignore security messages during application installation, especially during application selection and checking application reputation, reviews, security, and agreement messages.<sup id="cite_ref-72" class="reference"><a href="#cite_note-72"><span class="cite-bracket">&#91;</span>72<span class="cite-bracket">&#93;</span></a></sup> A recent survey by <a href="/wiki/Internet_security" title="Internet security">internet security</a> experts BullGuard showed a lack of insight concerning the rising number of malicious threats affecting mobile phones, with 53% of users claiming that they are unaware of security software for smartphones. A further 21% argued that such protection was unnecessary, and 42% admitted it hadn't crossed their mind ("Using APA," 2011).<sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citing_sources#What_information_to_include" title="Wikipedia:Citing sources"><span title="A complete citation is needed. (March 2023)">full citation needed</span></a></i>&#93;</sup> These statistics show that consumers are not concerned about security risks because they believe it is not a serious problem. However, in truth, smartphones are effectively handheld computers and are just as vulnerable. </p><p>The following are precautions that a user can take to manage security on a smartphone: </p> <dl><dt>Be skeptical</dt> <dd>A user should not believe everything that may be presented, as some information may be wrong, misleading, phishing, or attempting to distribute a malicious application. It is therefore advisable to check an application's reputation before buying or installing it.<sup id="cite_ref-FOOTNOTEHogbenDekker201046-48_73-0" class="reference"><a href="#cite_note-FOOTNOTEHogbenDekker201046-48-73"><span class="cite-bracket">&#91;</span>73<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Permissions given to applications</dt> <dd>The mass distribution of applications necessitates different permissions mechanisms for each operating system. It is necessary to clarify these permissions mechanisms to users, as they differ between systems and can be confusing. In addition, it is rarely feasible (or possible) to modify large sets of permissions requested by an application. However, this can be a source of risk because a user can grant an application excessive rights beyond what is necessary. For example, a note-taking application does not require access to the geolocation service to function. During installation, the user must consider an application's privileges and should not accept the installation if the requested rights are inconsistent.<sup id="cite_ref-FOOTNOTERuff20117-8_74-0" class="reference"><a href="#cite_note-FOOTNOTERuff20117-8-74"><span class="cite-bracket">&#91;</span>74<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEHogbenDekker201045_68-1" class="reference"><a href="#cite_note-FOOTNOTEHogbenDekker201045-68"><span class="cite-bracket">&#91;</span>68<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEShabtaiFledelKanonovElovici20098-9_75-0" class="reference"><a href="#cite_note-FOOTNOTEShabtaiFledelKanonovElovici20098-9-75"><span class="cite-bracket">&#91;</span>75<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <dl><dt>Be careful</dt> <dd>A user's phone can be protected through simple gestures and precautions, such as locking the smartphone when it is not in use, not leaving the device unattended, not blindly trusting applications, not storing sensitive data, or encrypting sensitive data that cannot be separated from the device.<sup id="cite_ref-FOOTNOTEHogbenDekker201043_76-0" class="reference"><a href="#cite_note-FOOTNOTEHogbenDekker201043-76"><span class="cite-bracket">&#91;</span>76<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-FOOTNOTEHogbenDekker201047_77-0" class="reference"><a href="#cite_note-FOOTNOTEHogbenDekker201047-77"><span class="cite-bracket">&#91;</span>77<span class="cite-bracket">&#93;</span></a></sup></dd> <dt>Disconnect unused peripheral devices</dt> <dd>According to <i>NIST Guidelines for Managing the Security of Mobile Devices 2013</i>, it is recommended to "Restrict user and application access to hardware, such as the digital camera, GPS, Bluetooth interface, USB interface, and removable storage". This can include removing permissions and configurations for unused peripheral devices.</dd></dl> <div class="mw-heading mw-heading4"><h4 id="Enable_Android_Device_Encryption">Enable Android Device Encryption</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=35" title="Edit section: Enable Android Device Encryption"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <dl><dd>The latest Android<sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Manual_of_Style/Dates_and_numbers#Chronological_items" title="Wikipedia:Manual of Style/Dates and numbers"><span title="The time period mentioned near this tag is ambiguous. (March 2023)">as of?</span></a></i>&#93;</sup> smartphones come with a built-in encryption setting for securing all the information saved on your device. This makes it difficult for a hacker to extract and decipher the information in case your device is compromised. It can be accessed via: <i>Settings → Security → Encrypt Phone + Encrypt SD Card.</i></dd></dl> <dl><dt>Ensure data</dt> <dd>Smartphones have significant memory capacity and can carry several gigabytes of data. The user must be careful about what data it carries and whether they should be protected (such as files containing bank information or business data). The user must have the prudence to avoid the transmission of sensitive data on a smartphone, which can be easily stolen. Furthermore, when a user gets rid of a device, they must be sure to remove all personal data first.<sup id="cite_ref-FOOTNOTEHogbenDekker201043-45_78-0" class="reference"><a href="#cite_note-FOOTNOTEHogbenDekker201043-45-78"><span class="cite-bracket">&#91;</span>78<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <p>These precautions reduce the ability for people or malicious applications to exploit a user's smartphone. If users are careful, many attacks can be defeated, especially phishing and applications seeking only to obtain rights on a device. </p> <div class="mw-heading mw-heading3"><h3 id="Centralized_storage">Centralized storage</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=36" title="Edit section: Centralized storage"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>One form of mobile protection allows companies to control the delivery and storage of text messages, by hosting the messages on a company server, rather than on the sender or receiver's phone. When certain conditions are met, such as an expiration date, the messages are deleted.<sup id="cite_ref-79" class="reference"><a href="#cite_note-79"><span class="cite-bracket">&#91;</span>79<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading3"><h3 id="Limitations">Limitations</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=37" title="Edit section: Limitations"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>The security mechanisms mentioned in this article are to a large extent inherited from knowledge and experience with computer security. The elements composing the two device types are similar, and there are common measures that can be used, such as antivirus software and firewalls. However, the implementation of these solutions is not necessarily possible (or is at least highly constrained) within a mobile device. The reason for this difference is the technical resources available to computers and mobile devices: even though the computing power of smartphones is becoming faster, they have other limitations: </p> <ul><li><b>Single-task system</b> – Some operating systems, including some still commonly used, are single-tasking. Only the foreground task is executed. It is difficult to introduce applications such as antivirus and firewall on such systems, because they cannot perform their monitoring while the user is operating the device, when monitoring is most needed.</li> <li><b>Energy autonomy</b> – A critical limitation for smartphones is energy autonomy. It is important that security mechanisms not consume too much battery resources, which could dramatically undermine the smartphone's autonomy and usage.</li> <li><b>Network</b> – Directly related to battery life, network utilization should not be too high. From the point of view of energy consumption, network utilization is one of the most expensive resources. Nonetheless, some calculations may need to be relocated to remote servers in order to preserve the battery. This balance can make implementation of certain intensive computation mechanisms a delicate situation.<sup id="cite_ref-FOOTNOTEBecher200940_80-0" class="reference"><a href="#cite_note-FOOTNOTEBecher200940-80"><span class="cite-bracket">&#91;</span>80<span class="cite-bracket">&#93;</span></a></sup></li></ul> <p>Furthermore, it is common that even if updates exist, or can be developed, they are not always deployed. For example, a user may not be aware of operating system updates; or a user may discover known vulnerabilities that are not corrected until the end of a long development cycle, which allows time to exploit the loopholes.<sup id="cite_ref-FOOTNOTERuff201111_67-1" class="reference"><a href="#cite_note-FOOTNOTERuff201111-67"><span class="cite-bracket">&#91;</span>67<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading3"><h3 id="Next_generation_of_mobile_security">Next generation of mobile security</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=38" title="Edit section: Next generation of mobile security"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>The following mobile environments are expected to make up future security frameworks: </p> <dl><dt>Rich operating system</dt> <dd>This category will contain traditional mobile operating systems like Android, iOS, Symbian OS, or Windows Phone. They will provide the traditional functionality and security of an OS to the applications.</dd></dl> <dl><dt>Secure Operating System (Secure OS)</dt> <dd>This category features a secure kernel which will run in parallel with a fully featured Rich OS, on the same processor core. It will include drivers for the Rich OS ("normal world") to communicate with the secure kernel ("secure world"). The trusted infrastructure could include interfaces like the display or keypad to regions of PCI-E address space and memories.</dd></dl> <dl><dt>Trusted Execution Environment (TEE)</dt> <dd>This environment will be made up of hardware and software. It helps control of access rights and houses sensitive applications, which need to be isolated from the Rich OS. It effectively acts as a firewall between the "normal world" and "secure world".</dd></dl> <dl><dt>Secure Element (SE)</dt> <dd>The SE consists of tamper-resistant hardware and associated software or separate isolated hardware. It can provide high levels of security and work in tandem with the TEE. The SE will be mandatory for hosting proximity payment applications or official electronic signatures. SE may connect, disconnect, block peripheral devices, and operate separate set of hardware.</dd></dl> <dl><dt>Security Applications (SA)</dt> <dd>Numerous security applications are available on app stores, providing protection from viruses and performing vulnerability assessment.<sup id="cite_ref-FOOTNOTEGupta2016461_81-0" class="reference"><a href="#cite_note-FOOTNOTEGupta2016461-81"><span class="cite-bracket">&#91;</span>81<span class="cite-bracket">&#93;</span></a></sup></dd></dl> <div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=39" title="Edit section: See also"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <ul><li><a href="/wiki/Browser_security" title="Browser security">Browser security</a></li> <li><a href="/wiki/Computer_security" title="Computer security">Computer security</a></li> <li><a href="/wiki/Information_security" title="Information security">Information security</a></li> <li><a href="/wiki/Mobile_Malware" class="mw-redirect" title="Mobile Malware">Mobile Malware</a></li> <li><a href="/wiki/Phone_hacking" title="Phone hacking">Phone hacking</a></li> <li><a href="/wiki/Telephone_tapping" class="mw-redirect" title="Telephone tapping">Telephone tapping</a></li> <li><a href="/wiki/Wireless_Public_Key_Infrastructure" title="Wireless Public Key Infrastructure">Wireless Public Key Infrastructure</a> (WPKI)</li> <li><a href="/wiki/Wireless_security" title="Wireless security">Wireless security</a></li> <li><a href="/wiki/Defense_strategy_(computing)" title="Defense strategy (computing)">Defense strategy (computing)</a></li> <li><span class="plainlinks"><a class="external text" href="https://en.wikipedia.org/w/index.php?title=Special:Search&amp;search=deepcat%3A%22Computer+security+exploits%22+deepcat%3A%22Mobile+security%22&amp;ns0=1&amp;fulltext=Search">Exploits of mobile security</a></span></li></ul> <div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=40" title="Edit section: Notes"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <style data-mw-deduplicate="TemplateStyles:r1239543626">.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}</style><div class="reflist reflist-columns references-column-width" style="column-width: 32em;"> <ol class="references"> <li id="cite_note-:2-1"><span class="mw-cite-backlink">^ <a href="#cite_ref-:2_1-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:2_1-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-:2_1-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-:2_1-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-:2_1-4"><sup><i><b>e</b></i></sup></a></span> <span class="reference-text"><style data-mw-deduplicate="TemplateStyles:r1238218222">.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("//upload.wikimedia.org/wikipedia/commons/6/65/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("//upload.wikimedia.org/wikipedia/commons/d/d6/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("//upload.wikimedia.org/wikipedia/commons/a/aa/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("//upload.wikimedia.org/wikipedia/commons/4/4c/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://whatis.techtarget.com/definition/mobile-security">"What is mobile security (wireless security)? - Definition from WhatIs.com"</a>. <i>WhatIs.com</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2020-12-05</span></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=WhatIs.com&amp;rft.atitle=What+is+mobile+security+%28wireless+security%29%3F+-+Definition+from+WhatIs.com&amp;rft_id=https%3A%2F%2Fwhatis.techtarget.com%2Fdefinition%2Fmobile-security&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEFurnell200913CHAPTER_1:_GETTING_MOBILE-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEFurnell200913CHAPTER_1:_GETTING_MOBILE_2-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFFurnell2009">Furnell 2009</a>, p.&#160;13, CHAPTER 1: GETTING MOBILE.</span> </li> <li id="cite_note-abiresearch.com-3"><span class="mw-cite-backlink">^ <a href="#cite_ref-abiresearch.com_3-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-abiresearch.com_3-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-abiresearch.com_3-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.abiresearch.com/press/byod-and-increased-malware-threats-help-driving-bi/">"BYOD and Increased Malware Threats Help Driving Billion Dollar Mobile Security Services Market in 2013"</a>. <i>ABI Research</i>. 2013-03-29<span class="reference-accessdate">. Retrieved <span class="nowrap">2018-11-11</span></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=ABI+Research&amp;rft.atitle=BYOD+and+Increased+Malware+Threats+Help+Driving+Billion+Dollar+Mobile+Security+Services+Market+in+2013&amp;rft.date=2013-03-29&amp;rft_id=https%3A%2F%2Fwww.abiresearch.com%2Fpress%2Fbyod-and-increased-malware-threats-help-driving-bi%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-:0-4"><span class="mw-cite-backlink">^ <a href="#cite_ref-:0_4-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:0_4-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-:0_4-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFKasmiLopes_Esteves2015" class="citation journal cs1">Kasmi C, Lopes Esteves J (13 August 2015). "IEMI Threats for Information Security: Remote Command Injection on Modern Smartphones". <i><a href="/wiki/IEEE_Transactions_on_Electromagnetic_Compatibility" title="IEEE Transactions on Electromagnetic Compatibility">IEEE Transactions on Electromagnetic Compatibility</a></i>. <b>57</b> (6): 1752–1755. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTEMC.2015.2463089">10.1109/TEMC.2015.2463089</a>. <a href="/wiki/S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a>&#160;<a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:34494009">34494009</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=IEEE+Transactions+on+Electromagnetic+Compatibility&amp;rft.atitle=IEMI+Threats+for+Information+Security%3A+Remote+Command+Injection+on+Modern+Smartphones&amp;rft.volume=57&amp;rft.issue=6&amp;rft.pages=1752-1755&amp;rft.date=2015-08-13&amp;rft_id=info%3Adoi%2F10.1109%2FTEMC.2015.2463089&amp;rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A34494009%23id-name%3DS2CID&amp;rft.aulast=Kasmi&amp;rft.aufirst=C&amp;rft.au=Lopes+Esteves%2C+J&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span> <ul><li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFAndy_Greenberg2015" class="citation magazine cs1">Andy Greenberg (14 October 2015). <a rel="nofollow" class="external text" href="https://www.wired.com/2015/10/this-radio-trick-silently-hacks-siri-from-16-feet-away/">"Hackers Can Silently Control Siri From 16 Feet Away"</a>. <i>Wired</i>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Wired&amp;rft.atitle=Hackers+Can+Silently+Control+Siri+From+16+Feet+Away&amp;rft.date=2015-10-14&amp;rft.au=Andy+Greenberg&amp;rft_id=https%3A%2F%2Fwww.wired.com%2F2015%2F10%2Fthis-radio-trick-silently-hacks-siri-from-16-feet-away%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li></ul> </span></li> <li id="cite_note-:4-5"><span class="mw-cite-backlink">^ <a href="#cite_ref-:4_5-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:4_5-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMichael_SW_LeeIan_Soon2017" class="citation journal cs1">Michael SW Lee; Ian Soon (2017-06-13). "Taking a bite out of Apple: Jailbreaking and the confluence of brand loyalty, consumer resistance and the co-creation of value". <i>Journal of Product &amp; Brand Management</i>. <b>26</b> (4): 351–364. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1108%2FJPBM-11-2015-1045">10.1108/JPBM-11-2015-1045</a>. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1061-0421">1061-0421</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Journal+of+Product+%26+Brand+Management&amp;rft.atitle=Taking+a+bite+out+of+Apple%3A+Jailbreaking+and+the+confluence+of+brand+loyalty%2C+consumer+resistance+and+the+co-creation+of+value&amp;rft.volume=26&amp;rft.issue=4&amp;rft.pages=351-364&amp;rft.date=2017-06-13&amp;rft_id=info%3Adoi%2F10.1108%2FJPBM-11-2015-1045&amp;rft.issn=1061-0421&amp;rft.au=Michael+SW+Lee&amp;rft.au=Ian+Soon&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-Leavitt2011-6"><span class="mw-cite-backlink">^ <a href="#cite_ref-Leavitt2011_6-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Leavitt2011_6-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Leavitt2011_6-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-Leavitt2011_6-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-Leavitt2011_6-4"><sup><i><b>e</b></i></sup></a> <a href="#cite_ref-Leavitt2011_6-5"><sup><i><b>f</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFLeavitt2011" class="citation journal cs1">Leavitt, Neal (2011). "Mobile Security: Finally a Serious Problem?". <i>Computer</i>. <b>44</b> (6): 11–14. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FMC.2011.184">10.1109/MC.2011.184</a>. <a href="/wiki/S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a>&#160;<a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:19895938">19895938</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Computer&amp;rft.atitle=Mobile+Security%3A+Finally+a+Serious+Problem%3F&amp;rft.volume=44&amp;rft.issue=6&amp;rft.pages=11-14&amp;rft.date=2011&amp;rft_id=info%3Adoi%2F10.1109%2FMC.2011.184&amp;rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A19895938%23id-name%3DS2CID&amp;rft.aulast=Leavitt&amp;rft.aufirst=Neal&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEBishop2004-7"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEBishop2004_7-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEBishop2004_7-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFBishop2004">Bishop 2004</a>.</span> </li> <li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFOlson2013" class="citation web cs1">Olson, Parmy (26 August 2013). <a rel="nofollow" class="external text" href="http://edition.cnn.com/2013/08/26/opinion/olson-mobile-hackers/index.html">"Your smartphone is hackers' next big target"</a>. CNN<span class="reference-accessdate">. Retrieved <span class="nowrap">August 26,</span> 2013</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=Your+smartphone+is+hackers%27+next+big+target&amp;rft.pub=CNN&amp;rft.date=2013-08-26&amp;rft.aulast=Olson&amp;rft.aufirst=Parmy&amp;rft_id=http%3A%2F%2Fedition.cnn.com%2F2013%2F08%2F26%2Fopinion%2Folson-mobile-hackers%2Findex.html&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-:6-9"><span class="mw-cite-backlink">^ <a href="#cite_ref-:6_9-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:6_9-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20121117002355/http://www.gov.mu/portal/sites/cert/files/Guide%20on%20Protection%20Against%20Hacking.pdf">"Guide on Protection Against Hacking"</a> <span class="cs1-format">(PDF)</span>. Mauritius National Computer Board. Archived from <a rel="nofollow" class="external text" href="http://www.gov.mu/portal/sites/cert/files/Guide%20on%20Protection%20Against%20Hacking.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2012-11-17.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=Guide+on+Protection+Against+Hacking&amp;rft.pub=Mauritius+National+Computer+Board&amp;rft_id=http%3A%2F%2Fwww.gov.mu%2Fportal%2Fsites%2Fcert%2Ffiles%2FGuide%2520on%2520Protection%2520Against%2520Hacking.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFLemos" class="citation web cs1">Lemos, Robert. <a rel="nofollow" class="external text" href="http://news.cnet.com/2009-1001_3-958129.html">"New laws make hacking a black-and-white choice"</a>. CNET News.com<span class="reference-accessdate">. Retrieved <span class="nowrap">September 23,</span> 2002</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=New+laws+make+hacking+a+black-and-white+choice&amp;rft.pub=CNET+News.com&amp;rft.aulast=Lemos&amp;rft.aufirst=Robert&amp;rft_id=http%3A%2F%2Fnews.cnet.com%2F2009-1001_3-958129.html&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-:5-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-:5_11-0">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMcCaney2012" class="citation web cs1">McCaney, Kevin (7 May 2012). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210126103931/https://gcn.com/articles/2012/05/07/the-unknowns-hack-nasa-air-force-harvard.aspx">"<span class="cs1-kern-left"></span>'Unknowns' hack NASA, Air Force, saying 'We're here to help'<span class="cs1-kern-right"></span>"</a>. Archived from <a rel="nofollow" class="external text" href="http://gcn.com/articles/2012/05/07/the-unknowns-hack-nasa-air-force-harvard.aspx">the original</a> on 2021-01-26<span class="reference-accessdate">. Retrieved <span class="nowrap">May 7,</span> 2012</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=%27Unknowns%27+hack+NASA%2C+Air+Force%2C+saying+%27We%27re+here+to+help%27&amp;rft.date=2012-05-07&amp;rft.aulast=McCaney&amp;rft.aufirst=Kevin&amp;rft_id=http%3A%2F%2Fgcn.com%2Farticles%2F2012%2F05%2F07%2Fthe-unknowns-hack-nasa-air-force-harvard.aspx&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEBilton2010-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBilton2010_12-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBilton2010">Bilton 2010</a>.</span> </li> <li id="cite_note-FOOTNOTEGuoWangZhu20043-13"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEGuoWangZhu20043_13-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEGuoWangZhu20043_13-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-FOOTNOTEGuoWangZhu20043_13-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-FOOTNOTEGuoWangZhu20043_13-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-FOOTNOTEGuoWangZhu20043_13-4"><sup><i><b>e</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFGuoWangZhu2004">Guo, Wang &amp; Zhu 2004</a>, p.&#160;3.</span> </li> <li id="cite_note-FOOTNOTEDagonMartinStarder200412-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEDagonMartinStarder200412_14-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFDagonMartinStarder2004">Dagon, Martin &amp; Starder 2004</a>, p.&#160;12.</span> </li> <li id="cite_note-FOOTNOTEDixonMishra20103-15"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEDixonMishra20103_15-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEDixonMishra20103_15-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFDixonMishra2010">Dixon &amp; Mishra 2010</a>, p.&#160;3.</span> </li> <li id="cite_note-FOOTNOTETöyssyHelenius2006113-16"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTETöyssyHelenius2006113_16-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTETöyssyHelenius2006113_16-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-FOOTNOTETöyssyHelenius2006113_16-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-FOOTNOTETöyssyHelenius2006113_16-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-FOOTNOTETöyssyHelenius2006113_16-4"><sup><i><b>e</b></i></sup></a> <a href="#cite_ref-FOOTNOTETöyssyHelenius2006113_16-5"><sup><i><b>f</b></i></sup></a> <a href="#cite_ref-FOOTNOTETöyssyHelenius2006113_16-6"><sup><i><b>g</b></i></sup></a> <a href="#cite_ref-FOOTNOTETöyssyHelenius2006113_16-7"><sup><i><b>h</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFTöyssyHelenius2006">Töyssy &amp; Helenius 2006</a>, p.&#160;113.</span> </li> <li id="cite_note-FOOTNOTESiemens20101-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTESiemens20101_17-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFSiemens2010">Siemens 2010</a>, p.&#160;1.</span> </li> <li id="cite_note-FOOTNOTEGendrullis2008266-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEGendrullis2008266_18-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFGendrullis2008">Gendrullis 2008</a>, p.&#160;266.</span> </li> <li id="cite_note-FOOTNOTEEuropean_Telecommunications_Standards_Institute20111-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEEuropean_Telecommunications_Standards_Institute20111_19-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFEuropean_Telecommunications_Standards_Institute2011">European Telecommunications Standards Institute 2011</a>, p.&#160;1.</span> </li> <li id="cite_note-FOOTNOTEJøsangMiralabéDallot2015-20"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEJøsangMiralabéDallot2015_20-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFJøsangMiralabéDallot2015">Jøsang, Miralabé &amp; Dallot 2015</a>.</span> </li> <li id="cite_note-Gittleson_2014_y120-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-Gittleson_2014_y120_21-0">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFGittleson2014" class="citation web cs1">Gittleson, Kim (2014-03-28). <a rel="nofollow" class="external text" href="https://www.bbc.co.uk/news/technology-26762198">"Data-stealing Snoopy drone unveiled at Black Hat"</a>. <i>BBC News</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2023-10-27</span></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=BBC+News&amp;rft.atitle=Data-stealing+Snoopy+drone+unveiled+at+Black+Hat&amp;rft.date=2014-03-28&amp;rft.aulast=Gittleson&amp;rft.aufirst=Kim&amp;rft_id=https%3A%2F%2Fwww.bbc.co.uk%2Fnews%2Ftechnology-26762198&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTETöyssyHelenius200627-22"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTETöyssyHelenius200627_22-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTETöyssyHelenius200627_22-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFTöyssyHelenius2006">Töyssy &amp; Helenius 2006</a>, p.&#160;27.</span> </li> <li id="cite_note-FOOTNOTEMulliner2006113-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEMulliner2006113_23-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFMulliner2006">Mulliner 2006</a>, p.&#160;113.</span> </li> <li id="cite_note-FOOTNOTEDunhamAbu_NimehBecher2008225-24"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEDunhamAbu_NimehBecher2008225_24-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFDunhamAbu_NimehBecher2008">Dunham, Abu Nimeh &amp; Becher 2008</a>, p.&#160;225.</span> </li> <li id="cite_note-:7-25"><span class="mw-cite-backlink">^ <a href="#cite_ref-:7_25-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:7_25-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSuarez-TangilJuan_E._TapiadorPedro_Peris-LopezArturo_Ribagorda2014" class="citation journal cs1">Suarez-Tangil, Guillermo; Juan E. Tapiador; Pedro Peris-Lopez; Arturo Ribagorda (2014). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171031165855/http://www.seg.inf.uc3m.es/~guillermo-suarez-tangil/papers/2013cst-ieee.pdf">"Evolution, Detection and Analysis of Malware in Smart Devices"</a> <span class="cs1-format">(PDF)</span>. <i>IEEE Communications Surveys &amp; Tutorials</i>. <b>16</b> (2): 961–987. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FSURV.2013.101613.00077">10.1109/SURV.2013.101613.00077</a>. <a href="/wiki/S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a>&#160;<a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:5627271">5627271</a>. Archived from <a rel="nofollow" class="external text" href="http://www.seg.inf.uc3m.es/~guillermo-suarez-tangil/papers/2013cst-ieee.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2017-10-31<span class="reference-accessdate">. Retrieved <span class="nowrap">2013-11-11</span></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=IEEE+Communications+Surveys+%26+Tutorials&amp;rft.atitle=Evolution%2C+Detection+and+Analysis+of+Malware+in+Smart+Devices&amp;rft.volume=16&amp;rft.issue=2&amp;rft.pages=961-987&amp;rft.date=2014&amp;rft_id=info%3Adoi%2F10.1109%2FSURV.2013.101613.00077&amp;rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A5627271%23id-name%3DS2CID&amp;rft.aulast=Suarez-Tangil&amp;rft.aufirst=Guillermo&amp;rft.au=Juan+E.+Tapiador&amp;rft.au=Pedro+Peris-Lopez&amp;rft.au=Arturo+Ribagorda&amp;rft_id=http%3A%2F%2Fwww.seg.inf.uc3m.es%2F~guillermo-suarez-tangil%2Fpapers%2F2013cst-ieee.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-:3-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-:3_26-0">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFNg" class="citation web cs1">Ng, Alfred. <a rel="nofollow" class="external text" href="https://www.cnet.com/news/your-smartphones-are-getting-more-valuable-for-hackers/">"Your smartphones are getting more valuable for hackers"</a>. <i>CNET</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2021-03-04</span></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=CNET&amp;rft.atitle=Your+smartphones+are+getting+more+valuable+for+hackers&amp;rft.aulast=Ng&amp;rft.aufirst=Alfred&amp;rft_id=https%3A%2F%2Fwww.cnet.com%2Fnews%2Fyour-smartphones-are-getting-more-valuable-for-hackers%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-Usenix-27"><span class="mw-cite-backlink">^ <a href="#cite_ref-Usenix_27-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Usenix_27-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Usenix_27-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFAvivGibsonMossopBlaze" class="citation conference cs1">Aviv, Adam J.; Gibson, Katherine; Mossop, Evan; Blaze, Matt; Smith, Jonathan M. <a rel="nofollow" class="external text" href="http://static.usenix.org/events/woot10/tech/full_papers/Aviv.pdf"><i>Smudge Attacks on Smartphone Touch Screens</i></a> <span class="cs1-format">(PDF)</span>. <a rel="nofollow" class="external text" href="http://static.usenix.org/events/woot10/">4th USENIX Workshop on Offensive Technologies</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Smudge+Attacks+on+Smartphone+Touch+Screens&amp;rft.aulast=Aviv&amp;rft.aufirst=Adam+J.&amp;rft.au=Gibson%2C+Katherine&amp;rft.au=Mossop%2C+Evan&amp;rft.au=Blaze%2C+Matt&amp;rft.au=Smith%2C+Jonathan+M.&amp;rft_id=http%3A%2F%2Fstatic.usenix.org%2Fevents%2Fwoot10%2Ftech%2Ffull_papers%2FAviv.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-:8-28"><span class="mw-cite-backlink">^ <a href="#cite_ref-:8_28-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:8_28-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFHamilton2018" class="citation news cs1">Hamilton, Keegan (July 11, 2018). <a rel="nofollow" class="external text" href="https://news.vice.com/en_us/article/zmkv3y/el-chapos-lawyers-want-to-suppress-evidence-from-spyware-used-to-catch-cheating-spouses">"El Chapo's lawyers want to suppress evidence from spyware used to catch cheating spouses"</a>. <a href="/wiki/Vice_Media" title="Vice Media">Vice Media</a>. <q>The Thailand-based FlexiSPY bills itself as "the world's most powerful monitoring software," and the company's website lists prospective buyers as concerned parents who want to spy on their kids and companies interested in snooping on their employees. But the app has also been dubbed "stalkerware" because it was initially marketed to jealous spouses paranoid about infidelity.</q></cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.atitle=El+Chapo%27s+lawyers+want+to+suppress+evidence+from+spyware+used+to+catch+cheating+spouses&amp;rft.date=2018-07-11&amp;rft.aulast=Hamilton&amp;rft.aufirst=Keegan&amp;rft_id=https%3A%2F%2Fnews.vice.com%2Fen_us%2Farticle%2Fzmkv3y%2Fel-chapos-lawyers-want-to-suppress-evidence-from-spyware-used-to-catch-cheating-spouses&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEBecher200965-29"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEBecher200965_29-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEBecher200965_29-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;65.</span> </li> <li id="cite_note-FOOTNOTEBecher200966-30"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher200966_30-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;66.</span> </li> <li id="cite_note-31"><span class="mw-cite-backlink"><b><a href="#cite_ref-31">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFDiogenes2019" class="citation book cs1">Diogenes, Yuri (2019). <a rel="nofollow" class="external text" href="https://www.worldcat.org/oclc/1139764053"><i>Cybersecurity - Attack and Defense Strategies - Second Edition</i></a>. Erdal Ozkaya, Safari Books Online (2nd&#160;ed.). Packt. p.&#160;163. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-83882-779-3" title="Special:BookSources/978-1-83882-779-3"><bdi>978-1-83882-779-3</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/1139764053">1139764053</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Cybersecurity+-+Attack+and+Defense+Strategies+-+Second+Edition&amp;rft.pages=163&amp;rft.edition=2nd&amp;rft.pub=Packt&amp;rft.date=2019&amp;rft_id=info%3Aoclcnum%2F1139764053&amp;rft.isbn=978-1-83882-779-3&amp;rft.aulast=Diogenes&amp;rft.aufirst=Yuri&amp;rft_id=https%3A%2F%2Fwww.worldcat.org%2Foclc%2F1139764053&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTESchmidtSchmidtBatyukClausen2009a3-32"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTESchmidtSchmidtBatyukClausen2009a3_32-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTESchmidtSchmidtBatyukClausen2009a3_32-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-FOOTNOTESchmidtSchmidtBatyukClausen2009a3_32-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFSchmidtSchmidtBatyukClausen2009a">Schmidt et al. 2009a</a>, p.&#160;3.</span> </li> <li id="cite_note-33"><span class="mw-cite-backlink"><b><a href="#cite_ref-33">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20211009121610/http://images.mktgassets.symantec.com/Web/Symantec/%7B3a70beb8-c55d-4516-98ed-1d0818a42661%7D_ISTR23_Main-FINAL-APR10.pdf?aid=elq_">"Eloqua - Error Information"</a> <span class="cs1-format">(PDF)</span>. Archived from <a rel="nofollow" class="external text" href="http://images.mktgassets.symantec.com/Web/Symantec/%7B3a70beb8-c55d-4516-98ed-1d0818a42661%7D_ISTR23_Main-FINAL-APR10.pdf?aid=elq_">the original</a> <span class="cs1-format">(PDF)</span> on 2021-10-09.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=Eloqua+-+Error+Information&amp;rft_id=http%3A%2F%2Fimages.mktgassets.symantec.com%2FWeb%2FSymantec%2F%257B3a70beb8-c55d-4516-98ed-1d0818a42661%257D_ISTR23_Main-FINAL-APR10.pdf%3Faid%3Delq_&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-34"><span class="mw-cite-backlink"><b><a href="#cite_ref-34">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://techxplore.com/news/2021-10-reveals-scale-data-sharing-android-mobile.html">"Study reveals scale of data-sharing from Android mobile phones"</a>. <i><a href="/wiki/Trinity_College_Dublin" title="Trinity College Dublin">Trinity College Dublin</a></i><span class="reference-accessdate">. Retrieved <span class="nowrap">16 November</span> 2021</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Trinity+College+Dublin&amp;rft.atitle=Study+reveals+scale+of+data-sharing+from+Android+mobile+phones&amp;rft_id=https%3A%2F%2Ftechxplore.com%2Fnews%2F2021-10-reveals-scale-data-sharing-android-mobile.html&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-35"><span class="mw-cite-backlink"><b><a href="#cite_ref-35">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFLiuPatrasLeith2021" class="citation web cs1">Liu, Haoyu; Patras, Paul; Leith, Douglas J. (6 October 2021). <a rel="nofollow" class="external text" href="https://www.scss.tcd.ie/Doug.Leith/Android_privacy_report.pdf">"Android Mobile OS Snooping By Samsung, Xiaomi, Huawei and Realme Handsets"</a> <span class="cs1-format">(PDF)</span><span class="reference-accessdate">. Retrieved <span class="nowrap">16 November</span> 2021</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=Android+Mobile+OS+Snooping+By+Samsung%2C+Xiaomi%2C+Huawei+and+Realme+Handsets&amp;rft.date=2021-10-06&amp;rft.aulast=Liu&amp;rft.aufirst=Haoyu&amp;rft.au=Patras%2C+Paul&amp;rft.au=Leith%2C+Douglas+J.&amp;rft_id=https%3A%2F%2Fwww.scss.tcd.ie%2FDoug.Leith%2FAndroid_privacy_report.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-36"><span class="mw-cite-backlink"><b><a href="#cite_ref-36">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://github.com/M66B/NetGuard/blob/master/FAQ.md">"NetGuard FAQ"</a>. <i><a href="/wiki/GitHub" title="GitHub">GitHub</a></i>. 4 November 2022<span class="reference-accessdate">. Retrieved <span class="nowrap">4 November</span> 2022</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=GitHub&amp;rft.atitle=NetGuard+FAQ&amp;rft.date=2022-11-04&amp;rft_id=https%3A%2F%2Fgithub.com%2FM66B%2FNetGuard%2Fblob%2Fmaster%2FFAQ.md&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEBecher200987-37"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher200987_37-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;87.</span> </li> <li id="cite_note-FOOTNOTEBecher200988-38"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher200988_38-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;88.</span> </li> <li id="cite_note-FOOTNOTEMickensNoble20051-39"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEMickensNoble20051_39-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFMickensNoble2005">Mickens &amp; Noble 2005</a>, p.&#160;1.</span> </li> <li id="cite_note-FOOTNOTERaboin2009272-40"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTERaboin2009272_40-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFRaboin2009">Raboin 2009</a>, p.&#160;272.</span> </li> <li id="cite_note-FOOTNOTETöyssyHelenius2006114-41"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTETöyssyHelenius2006114_41-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFTöyssyHelenius2006">Töyssy &amp; Helenius 2006</a>, p.&#160;114.</span> </li> <li id="cite_note-42"><span class="mw-cite-backlink"><b><a href="#cite_ref-42">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFHaas2015" class="citation thesis cs1">Haas, Peter D. (2015). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160224021536/http://gradworks.umi.com/15/86/1586729.html"><i>Ransomware goes mobile: An analysis of the threats posed by emerging methods</i></a> (Thesis). Utica College. Archived from <a rel="nofollow" class="external text" href="http://gradworks.umi.com/15/86/1586729.html">the original</a> on 2016-02-24.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&amp;rft.title=Ransomware+goes+mobile%3A+An+analysis+of+the+threats+posed+by+emerging+methods&amp;rft.inst=Utica+College&amp;rft.date=2015&amp;rft.aulast=Haas&amp;rft.aufirst=Peter+D.&amp;rft_id=http%3A%2F%2Fgradworks.umi.com%2F15%2F86%2F1586729.html&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-43"><span class="mw-cite-backlink"><b><a href="#cite_ref-43">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://www.theguardian.com/news/2021/jul/18/what-is-pegasus-spyware-and-how-does-it-hack-phones">"What is Pegasus spyware and how does it hack phones?"</a>. <i>The Guardian</i>. 18 July 2021<span class="reference-accessdate">. Retrieved <span class="nowrap">13 August</span> 2021</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=The+Guardian&amp;rft.atitle=What+is+Pegasus+spyware+and+how+does+it+hack+phones%3F&amp;rft.date=2021-07-18&amp;rft_id=https%3A%2F%2Fwww.theguardian.com%2Fnews%2F2021%2Fjul%2F18%2Fwhat-is-pegasus-spyware-and-how-does-it-hack-phones&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEBecher200991-94-44"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher200991-94_44-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;91-94.</span> </li> <li id="cite_note-FOOTNOTEBecher200912-45"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEBecher200912_45-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEBecher200912_45-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-FOOTNOTEBecher200912_45-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-FOOTNOTEBecher200912_45-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-FOOTNOTEBecher200912_45-4"><sup><i><b>e</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;12.</span> </li> <li id="cite_note-FOOTNOTESchmidtSchmidtClausenYüksel20085-6-46"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel20085-6_46-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel20085-6_46-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFSchmidtSchmidtClausenYüksel2008">Schmidt et al. 2008</a>, p.&#160;5-6.</span> </li> <li id="cite_note-FOOTNOTEHalbronnSigwald20105-6-47"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEHalbronnSigwald20105-6_47-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFHalbronnSigwald2010">Halbronn &amp; Sigwald 2010</a>, p.&#160;5-6.</span> </li> <li id="cite_note-FOOTNOTERuff2011127-48"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTERuff2011127_48-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFRuff2011">Ruff 2011</a>, p.&#160;127.</span> </li> <li id="cite_note-FOOTNOTEHogbenDekker201050-49"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEHogbenDekker201050_49-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFHogbenDekker2010">Hogben &amp; Dekker 2010</a>, p.&#160;50.</span> </li> <li id="cite_note-FOOTNOTESchmidtSchmidtClausenYüksel200850-50"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel200850_50-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFSchmidtSchmidtClausenYüksel2008">Schmidt et al. 2008</a>, p.&#160;50.</span> </li> <li id="cite_note-FOOTNOTEShabtaiFledelKanonovElovici200910-51"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEShabtaiFledelKanonovElovici200910_51-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEShabtaiFledelKanonovElovici200910_51-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-FOOTNOTEShabtaiFledelKanonovElovici200910_51-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFShabtaiFledelKanonovElovici2009">Shabtai et al. 2009</a>, p.&#160;10.</span> </li> <li id="cite_note-FOOTNOTEBecher200931-52"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher200931_52-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;31.</span> </li> <li id="cite_note-FOOTNOTESchmidtSchmidtClausenYüksel20083-53"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel20083_53-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFSchmidtSchmidtClausenYüksel2008">Schmidt et al. 2008</a>, p.&#160;3.</span> </li> <li id="cite_note-FOOTNOTEShabtaiFledelKanonovElovici20097-8-54"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEShabtaiFledelKanonovElovici20097-8_54-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFShabtaiFledelKanonovElovici2009">Shabtai et al. 2009</a>, p.&#160;7-8.</span> </li> <li id="cite_note-FOOTNOTEPandya200815-55"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEPandya200815_55-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFPandya2008">Pandya 2008</a>, p.&#160;15.</span> </li> <li id="cite_note-FOOTNOTEBecher200922-56"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher200922_56-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;22.</span> </li> <li id="cite_note-FOOTNOTEBecherFreilingHoffmannHolz201196-57"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecherFreilingHoffmannHolz201196_57-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecherFreilingHoffmannHolz2011">Becher et al. 2011</a>, p.&#160;96.</span> </li> <li id="cite_note-FOOTNOTEBecher2009128-58"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher2009128_58-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;128.</span> </li> <li id="cite_note-FOOTNOTEBecher2009140-59"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher2009140_59-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;140.</span> </li> <li id="cite_note-FOOTNOTEThirumathyamDerawi20101-60"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEThirumathyamDerawi20101_60-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFThirumathyamDerawi2010">Thirumathyam &amp; Derawi 2010</a>, p.&#160;1.</span> </li> <li id="cite_note-FOOTNOTESchmidtSchmidtClausenYüksel20087-12-61"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTESchmidtSchmidtClausenYüksel20087-12_61-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFSchmidtSchmidtClausenYüksel2008">Schmidt et al. 2008</a>, p.&#160;7-12.</span> </li> <li id="cite_note-FOOTNOTEBecher2009126-62"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher2009126_62-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;126.</span> </li> <li id="cite_note-FOOTNOTEMalik201628-63"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEMalik201628_63-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFMalik2016">Malik 2016</a>, p.&#160;28.</span> </li> <li id="cite_note-64"><span class="mw-cite-backlink"><b><a href="#cite_ref-64">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFVaughan-Nichols" class="citation news cs1">Vaughan-Nichols, Steven J. <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/google-tensor-chip-for-pixel-6-everything-we-know-so-far/">"Google Tensor chip: Everything we know so far"</a>. <i>ZDNet</i>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=ZDNet&amp;rft.atitle=Google+Tensor+chip%3A+Everything+we+know+so+far&amp;rft.aulast=Vaughan-Nichols&amp;rft.aufirst=Steven+J.&amp;rft_id=https%3A%2F%2Fwww.zdnet.com%2Farticle%2Fgoogle-tensor-chip-for-pixel-6-everything-we-know-so-far%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-65"><span class="mw-cite-backlink"><b><a href="#cite_ref-65">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation magazine cs1"><a rel="nofollow" class="external text" href="https://www.wired.com/story/google-titan-m-security-chip-pixel-3/">"The Titan M Chip Powers Up Pixel 3 Security"</a>. <i>Wired</i>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Wired&amp;rft.atitle=The+Titan+M+Chip+Powers+Up+Pixel+3+Security&amp;rft_id=https%3A%2F%2Fwww.wired.com%2Fstory%2Fgoogle-titan-m-security-chip-pixel-3%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEBecherFreilingHoffmannHolz2011101-66"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecherFreilingHoffmannHolz2011101_66-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecherFreilingHoffmannHolz2011">Becher et al. 2011</a>, p.&#160;101.</span> </li> <li id="cite_note-FOOTNOTERuff201111-67"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTERuff201111_67-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTERuff201111_67-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFRuff2011">Ruff 2011</a>, p.&#160;11.</span> </li> <li id="cite_note-FOOTNOTEHogbenDekker201045-68"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEHogbenDekker201045_68-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEHogbenDekker201045_68-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFHogbenDekker2010">Hogben &amp; Dekker 2010</a>, p.&#160;45.</span> </li> <li id="cite_note-FOOTNOTEBecher200913-69"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEBecher200913_69-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEBecher200913_69-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;13.</span> </li> <li id="cite_note-FOOTNOTEBecher200934-70"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher200934_70-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;34.</span> </li> <li id="cite_note-FOOTNOTERuff20117-71"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTERuff20117_71-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFRuff2011">Ruff 2011</a>, p.&#160;7.</span> </li> <li id="cite_note-72"><span class="mw-cite-backlink"><b><a href="#cite_ref-72">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMylonasKastaniaGritzalis2013" class="citation journal cs1">Mylonas, Alexios; Kastania, Anastasia; Gritzalis, Dimitris (2013). "Delegate the smartphone user? Security awareness in smartphone platforms". <i>Computers &amp; Security</i>. <b>34</b>: 47–66. <a href="/wiki/CiteSeerX_(identifier)" class="mw-redirect" title="CiteSeerX (identifier)">CiteSeerX</a>&#160;<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.717.4352">10.1.1.717.4352</a></span>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.cose.2012.11.004">10.1016/j.cose.2012.11.004</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Computers+%26+Security&amp;rft.atitle=Delegate+the+smartphone+user%3F+Security+awareness+in+smartphone+platforms&amp;rft.volume=34&amp;rft.pages=47-66&amp;rft.date=2013&amp;rft_id=https%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fsummary%3Fdoi%3D10.1.1.717.4352%23id-name%3DCiteSeerX&amp;rft_id=info%3Adoi%2F10.1016%2Fj.cose.2012.11.004&amp;rft.aulast=Mylonas&amp;rft.aufirst=Alexios&amp;rft.au=Kastania%2C+Anastasia&amp;rft.au=Gritzalis%2C+Dimitris&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEHogbenDekker201046-48-73"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEHogbenDekker201046-48_73-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFHogbenDekker2010">Hogben &amp; Dekker 2010</a>, p.&#160;46-48.</span> </li> <li id="cite_note-FOOTNOTERuff20117-8-74"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTERuff20117-8_74-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFRuff2011">Ruff 2011</a>, p.&#160;7-8.</span> </li> <li id="cite_note-FOOTNOTEShabtaiFledelKanonovElovici20098-9-75"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEShabtaiFledelKanonovElovici20098-9_75-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFShabtaiFledelKanonovElovici2009">Shabtai et al. 2009</a>, p.&#160;8-9.</span> </li> <li id="cite_note-FOOTNOTEHogbenDekker201043-76"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEHogbenDekker201043_76-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFHogbenDekker2010">Hogben &amp; Dekker 2010</a>, p.&#160;43.</span> </li> <li id="cite_note-FOOTNOTEHogbenDekker201047-77"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEHogbenDekker201047_77-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFHogbenDekker2010">Hogben &amp; Dekker 2010</a>, p.&#160;47.</span> </li> <li id="cite_note-FOOTNOTEHogbenDekker201043-45-78"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEHogbenDekker201043-45_78-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFHogbenDekker2010">Hogben &amp; Dekker 2010</a>, p.&#160;43-45.</span> </li> <li id="cite_note-79"><span class="mw-cite-backlink"><b><a href="#cite_ref-79">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCharlie_Sorrel2010" class="citation magazine cs1">Charlie Sorrel (2010-03-01). <a rel="nofollow" class="external text" href="https://www.wired.com/gadgetlab/2010/03/tigertext-deletes-text-messages-from-receivers-phone/">"TigerText Deletes Text Messages From Receiver's Phone"</a>. <i><a href="/wiki/Wired_(magazine)" title="Wired (magazine)">Wired</a></i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100826025202/http://www.wired.com/gadgetlab/2010/03/tigertext-deletes-text-messages-from-receivers-phone">Archived</a> from the original on 2010-08-26<span class="reference-accessdate">. Retrieved <span class="nowrap">2010-03-02</span></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Wired&amp;rft.atitle=TigerText+Deletes+Text+Messages+From+Receiver%27s+Phone&amp;rft.date=2010-03-01&amp;rft.au=Charlie+Sorrel&amp;rft_id=https%3A%2F%2Fwww.wired.com%2Fgadgetlab%2F2010%2F03%2Ftigertext-deletes-text-messages-from-receivers-phone%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></span> </li> <li id="cite_note-FOOTNOTEBecher200940-80"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEBecher200940_80-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFBecher2009">Becher 2009</a>, p.&#160;40.</span> </li> <li id="cite_note-FOOTNOTEGupta2016461-81"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEGupta2016461_81-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFGupta2016">Gupta 2016</a>, p.&#160;461.</span> </li> </ol></div> <div class="mw-heading mw-heading2"><h2 id="References">References</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=41" title="Edit section: References"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <div class="mw-heading mw-heading3"><h3 id="Books">Books</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=42" title="Edit section: Books"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <style data-mw-deduplicate="TemplateStyles:r1239549316">.mw-parser-output .refbegin{margin-bottom:0.5em}.mw-parser-output .refbegin-hanging-indents>ul{margin-left:0}.mw-parser-output .refbegin-hanging-indents>ul>li{margin-left:0;padding-left:3.2em;text-indent:-3.2em}.mw-parser-output .refbegin-hanging-indents ul,.mw-parser-output .refbegin-hanging-indents ul li{list-style:none}@media(max-width:720px){.mw-parser-output .refbegin-hanging-indents>ul>li{padding-left:1.6em;text-indent:-1.6em}}.mw-parser-output .refbegin-columns{margin-top:0.3em}.mw-parser-output .refbegin-columns ul{margin-top:0}.mw-parser-output .refbegin-columns li{page-break-inside:avoid;break-inside:avoid-column}@media screen{.mw-parser-output .refbegin{font-size:90%}}</style><div class="refbegin" style=""> <ul><li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBishop2004" class="citation book cs1">Bishop, Matt (2004). <i>Introduction to Computer Security</i>. Addison Wesley Professional. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-0-321-24744-5" title="Special:BookSources/978-0-321-24744-5"><bdi>978-0-321-24744-5</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Introduction+to+Computer+Security&amp;rft.pub=Addison+Wesley+Professional&amp;rft.date=2004&amp;rft.isbn=978-0-321-24744-5&amp;rft.aulast=Bishop&amp;rft.aufirst=Matt&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFDunhamAbu_NimehBecher2008" class="citation book cs1">Dunham, Ken; Abu Nimeh, Saeed; Becher, Michael (2008). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=Nd1RcGWMKnEC"><i>Mobile Malware Attack and Defense</i></a>. Syngress Media. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-59749-298-0" title="Special:BookSources/978-1-59749-298-0"><bdi>978-1-59749-298-0</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Mobile+Malware+Attack+and+Defense&amp;rft.pub=Syngress+Media&amp;rft.date=2008&amp;rft.isbn=978-1-59749-298-0&amp;rft.aulast=Dunham&amp;rft.aufirst=Ken&amp;rft.au=Abu+Nimeh%2C+Saeed&amp;rft.au=Becher%2C+Michael&amp;rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3DNd1RcGWMKnEC&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFFurnell2009" class="citation book cs1">Furnell, Steven (2009). <i>Mobile Security</i>. Itgp. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-84928-021-1" title="Special:BookSources/978-1-84928-021-1"><bdi>978-1-84928-021-1</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Mobile+Security&amp;rft.pub=Itgp&amp;rft.date=2009&amp;rft.isbn=978-1-84928-021-1&amp;rft.aulast=Furnell&amp;rft.aufirst=Steven&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFRogers2013" class="citation book cs1">Rogers, David (2013). <i>Mobile Security: A Guide for Users</i>. Copper Horse Solutions Limited. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-291-53309-5" title="Special:BookSources/978-1-291-53309-5"><bdi>978-1-291-53309-5</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Mobile+Security%3A+A+Guide+for+Users&amp;rft.pub=Copper+Horse+Solutions+Limited&amp;rft.date=2013&amp;rft.isbn=978-1-291-53309-5&amp;rft.aulast=Rogers&amp;rft.aufirst=David&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li></ul> </div> <div class="mw-heading mw-heading3"><h3 id="Articles">Articles</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=43" title="Edit section: Articles"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239549316"><div class="refbegin" style=""> <ul><li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBecher2009" class="citation thesis cs1">Becher, Michael (2009). <a rel="nofollow" class="external text" href="https://ub-madoc.bib.uni-mannheim.de/2998/1/dissertation_becher.pdf"><i>Security of Smartphones at the Dawn of Their Ubiquitousness</i></a> <span class="cs1-format">(PDF)</span> (Dissertation). Mannheim University.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&amp;rft.title=Security+of+Smartphones+at+the+Dawn+of+Their+Ubiquitousness&amp;rft.inst=Mannheim+University&amp;rft.date=2009&amp;rft.aulast=Becher&amp;rft.aufirst=Michael&amp;rft_id=https%3A%2F%2Fub-madoc.bib.uni-mannheim.de%2F2998%2F1%2Fdissertation_becher.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBecherFreilingHoffmannHolz2011" class="citation conference cs1">Becher, Michael; Freiling, Felix C.; Hoffmann, Johannes; Holz, Thorsten; Uellenbeck, Sebastian; Wolf, Christopher (May 2011). <a rel="nofollow" class="external text" href="http://www.ieee-security.org/TC/SP2011/PAPERS/2011/paper007.pdf"><i>Mobile Security Catching Up? Revealing the Nuts and Bolts of the Security of Mobile Devices</i></a> <span class="cs1-format">(PDF)</span>. 2011 IEEE Symposium on Security and Privacy. pp.&#160;96–111. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FSP.2011.29">10.1109/SP.2011.29</a>. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-4577-0147-4" title="Special:BookSources/978-1-4577-0147-4"><bdi>978-1-4577-0147-4</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Mobile+Security+Catching+Up%3F+Revealing+the+Nuts+and+Bolts+of+the+Security+of+Mobile+Devices&amp;rft.pages=96-111&amp;rft.date=2011-05&amp;rft_id=info%3Adoi%2F10.1109%2FSP.2011.29&amp;rft.isbn=978-1-4577-0147-4&amp;rft.aulast=Becher&amp;rft.aufirst=Michael&amp;rft.au=Freiling%2C+Felix+C.&amp;rft.au=Hoffmann%2C+Johannes&amp;rft.au=Holz%2C+Thorsten&amp;rft.au=Uellenbeck%2C+Sebastian&amp;rft.au=Wolf%2C+Christopher&amp;rft_id=http%3A%2F%2Fwww.ieee-security.org%2FTC%2FSP2011%2FPAPERS%2F2011%2Fpaper007.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBilton2010" class="citation news cs1">Bilton, Nick (26 July 2010). <a rel="nofollow" class="external text" href="https://www.nytimes.com/2010/07/26/technology/26security.html">"Hackers With Enigmatic Motives Vex Companies"</a>. <i>The New York Times</i>. p.&#160;5.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=The+New+York+Times&amp;rft.atitle=Hackers+With+Enigmatic+Motives+Vex+Companies&amp;rft.pages=5&amp;rft.date=2010-07-26&amp;rft.aulast=Bilton&amp;rft.aufirst=Nick&amp;rft_id=https%3A%2F%2Fwww.nytimes.com%2F2010%2F07%2F26%2Ftechnology%2F26security.html&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCaiChenWuZhang2015" class="citation thesis cs1">Cai, Fangda; Chen, Hao; Wu, Yuanyi; Zhang, Yuan (2015). <a rel="nofollow" class="external text" href="http://web.cs.ucdavis.edu/~hchen/paper/most2015.pdf"><i>AppCracker: Widespread Vulnerabilities in Userand Session Authentication in Mobile Apps</i></a> <span class="cs1-format">(PDF)</span> (Dissertation). University of California, Davis.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&amp;rft.title=AppCracker%3A+Widespread+Vulnerabilities+in+Userand+Session+Authentication+in+Mobile+Apps&amp;rft.inst=University+of+California%2C+Davis&amp;rft.date=2015&amp;rft.aulast=Cai&amp;rft.aufirst=Fangda&amp;rft.au=Chen%2C+Hao&amp;rft.au=Wu%2C+Yuanyi&amp;rft.au=Zhang%2C+Yuan&amp;rft_id=http%3A%2F%2Fweb.cs.ucdavis.edu%2F~hchen%2Fpaper%2Fmost2015.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCrussellGiblerChen2012" class="citation thesis cs1">Crussell, Johnathan; Gibler, Clint; Chen, Hao (2012). <a rel="nofollow" class="external text" href="http://web.cs.ucdavis.edu/~hchen/paper/esorics2012.pdf"><i>Attack of the Clones: Detecting Cloned Applications on Android Markets</i></a> <span class="cs1-format">(PDF)</span> (Dissertation). University of California, Davis.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&amp;rft.title=Attack+of+the+Clones%3A+Detecting+Cloned+Applications+on+Android+Markets&amp;rft.inst=University+of+California%2C+Davis&amp;rft.date=2012&amp;rft.aulast=Crussell&amp;rft.aufirst=Johnathan&amp;rft.au=Gibler%2C+Clint&amp;rft.au=Chen%2C+Hao&amp;rft_id=http%3A%2F%2Fweb.cs.ucdavis.edu%2F~hchen%2Fpaper%2Fesorics2012.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFDagonMartinStarder2004" class="citation journal cs1">Dagon, David; Martin, Tom; Starder, Thad (October–December 2004). "Mobile Phones as Computing Devices: The Viruses are Coming!". <i>IEEE Pervasive Computing</i>. <b>3</b> (4): 11. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FMPRV.2004.21">10.1109/MPRV.2004.21</a>. <a href="/wiki/S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a>&#160;<a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:14224399">14224399</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=IEEE+Pervasive+Computing&amp;rft.atitle=Mobile+Phones+as+Computing+Devices%3A+The+Viruses+are+Coming%21&amp;rft.volume=3&amp;rft.issue=4&amp;rft.pages=11&amp;rft.date=2004-10%2F2004-12&amp;rft_id=info%3Adoi%2F10.1109%2FMPRV.2004.21&amp;rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A14224399%23id-name%3DS2CID&amp;rft.aulast=Dagon&amp;rft.aufirst=David&amp;rft.au=Martin%2C+Tom&amp;rft.au=Starder%2C+Thad&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFDixonMishra2010" class="citation conference cs1">Dixon, Bryan; Mishra, Shivakant (June–July 2010). <a rel="nofollow" class="external text" href="http://wraits10.di.fc.ul.pt/paper%2012.pdf"><i>On and Rootkit and Malware Detection in Smartphones</i></a> <span class="cs1-format">(PDF)</span>. 2010 International Conference on Dependable Systems and Networks Workshops (DSN-W). <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-4244-7728-9" title="Special:BookSources/978-1-4244-7728-9"><bdi>978-1-4244-7728-9</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=On+and+Rootkit+and+Malware+Detection+in+Smartphones&amp;rft.date=2010-06%2F2010-07&amp;rft.isbn=978-1-4244-7728-9&amp;rft.aulast=Dixon&amp;rft.aufirst=Bryan&amp;rft.au=Mishra%2C+Shivakant&amp;rft_id=http%3A%2F%2Fwraits10.di.fc.ul.pt%2Fpaper%252012.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFGendrullis2008" class="citation conference cs1">Gendrullis, Timo (November 2008). <a rel="nofollow" class="external text" href="http://citeseerx.ist.psu.edu/viewdoc/versions?doi=10.1.1.182.2029"><i>A real-world attack breaking A5/1 within hours</i></a>. Proceedings of CHES '08. Springer. pp.&#160;266–282. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.1007%2F978-3-540-85053-3_17">10.1007/978-3-540-85053-3_17</a></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=A+real-world+attack+breaking+A5%2F1+within+hours&amp;rft.pages=266-282&amp;rft.pub=Springer&amp;rft.date=2008-11&amp;rft_id=info%3Adoi%2F10.1007%2F978-3-540-85053-3_17&amp;rft.aulast=Gendrullis&amp;rft.aufirst=Timo&amp;rft_id=http%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fversions%3Fdoi%3D10.1.1.182.2029&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFGupta2016" class="citation conference cs1">Gupta, Sugandha (2016). <i>Vulnebdroid: Automated Vulnerability Score Calculator for Android Applications</i>. International Symposium on Security in Computing and Communication. Springer. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2F978-981-10-2738-3_40">10.1007/978-981-10-2738-3_40</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Vulnebdroid%3A+Automated+Vulnerability+Score+Calculator+for+Android+Applications&amp;rft.pub=Springer&amp;rft.date=2016&amp;rft_id=info%3Adoi%2F10.1007%2F978-981-10-2738-3_40&amp;rft.aulast=Gupta&amp;rft.aufirst=Sugandha&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFGuoWangZhu2004" class="citation conference cs1">Guo, Chuanxiong; Wang, Helen; Zhu, Wenwu (November 2004). <a rel="nofollow" class="external text" href="http://conferences.sigcomm.org/hotnets/2004/HotNets-III%20Proceedings/guo.pdf"><i>Smart-Phone Attacks and Defenses</i></a> <span class="cs1-format">(PDF)</span>. ACM SIGCOMM HotNets. Association for Computing Machinery, Inc<span class="reference-accessdate">. Retrieved <span class="nowrap">March 31,</span> 2012</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Smart-Phone+Attacks+and+Defenses&amp;rft.pub=Association+for+Computing+Machinery%2C+Inc.&amp;rft.date=2004-11&amp;rft.aulast=Guo&amp;rft.aufirst=Chuanxiong&amp;rft.au=Wang%2C+Helen&amp;rft.au=Zhu%2C+Wenwu&amp;rft_id=http%3A%2F%2Fconferences.sigcomm.org%2Fhotnets%2F2004%2FHotNets-III%2520Proceedings%2Fguo.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFHalbronnSigwald2010" class="citation conference cs1">Halbronn, Cedric; Sigwald, John (2010). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130202043634/http://esec-lab.sogeti.com/dotclear/public/publications/10-hitbkl-iphone.pdf"><i>Vulnerabilities &amp; iPhone Security Model</i></a> <span class="cs1-format">(PDF)</span>. HITB SecConf 2010. Archived from <a rel="nofollow" class="external text" href="http://esec-lab.sogeti.com/dotclear/public/publications/10-hitbkl-iphone.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2013-02-02<span class="reference-accessdate">. Retrieved <span class="nowrap">2012-04-21</span></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Vulnerabilities+%26+iPhone+Security+Model&amp;rft.date=2010&amp;rft.aulast=Halbronn&amp;rft.aufirst=Cedric&amp;rft.au=Sigwald%2C+John&amp;rft_id=http%3A%2F%2Fesec-lab.sogeti.com%2Fdotclear%2Fpublic%2Fpublications%2F10-hitbkl-iphone.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFHogbenDekker2010" class="citation web cs1">Hogben, Giles; Dekker, Marnix (December 2010). <a rel="nofollow" class="external text" href="https://www.enisa.europa.eu/activities/identity-and-trust/risks-and-data-breaches/smartphones-information-security-risks-opportunities-and-recommendations-for-users/at_download/fullReport">"Smartphones: Information security Risks, Opportunities and Recommendations for users"</a>. <i>ENISA</i>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=ENISA&amp;rft.atitle=Smartphones%3A+Information+security+Risks%2C+Opportunities+and+Recommendations+for+users&amp;rft.date=2010-12&amp;rft.aulast=Hogben&amp;rft.aufirst=Giles&amp;rft.au=Dekker%2C+Marnix&amp;rft_id=https%3A%2F%2Fwww.enisa.europa.eu%2Factivities%2Fidentity-and-trust%2Frisks-and-data-breaches%2Fsmartphones-information-security-risks-opportunities-and-recommendations-for-users%2Fat_download%2FfullReport&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFJøsangMiralabéDallot2015" class="citation journal cs1">Jøsang, Audun; Miralabé, Laurent; Dallot, Léonard (2015). <a rel="nofollow" class="external text" href="http://folk.uio.no/josang/papers/JMD2015-JIW.pdf">"Vulnerability by Design in Mobile Network Security"</a> <span class="cs1-format">(PDF)</span>. <i>Journal of Information Warfare (JIF)</i>. <b>14</b> (4). <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1445-3347">1445-3347</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Journal+of+Information+Warfare+%28JIF%29&amp;rft.atitle=Vulnerability+by+Design+in+Mobile+Network+Security&amp;rft.volume=14&amp;rft.issue=4&amp;rft.date=2015&amp;rft.issn=1445-3347&amp;rft.aulast=J%C3%B8sang&amp;rft.aufirst=Audun&amp;rft.au=Miralab%C3%A9%2C+Laurent&amp;rft.au=Dallot%2C+L%C3%A9onard&amp;rft_id=http%3A%2F%2Ffolk.uio.no%2Fjosang%2Fpapers%2FJMD2015-JIW.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMalik2016" class="citation conference cs1">Malik, Jyoti (2016). <a rel="nofollow" class="external text" href="http://dl.acm.org/citation.cfm?id=2940348"><i>CREDROID: Android malware detection by network traffic analysis</i></a>. Proceedings of the 1st ACM Workshop on Privacy-Aware Mobile Computing. Association for Computing Machinery, Inc. pp.&#160;28–36. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2940343.2940348">10.1145/2940343.2940348</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=CREDROID%3A+Android+malware+detection+by+network+traffic+analysis&amp;rft.pages=28-36&amp;rft.pub=Association+for+Computing+Machinery%2C+Inc.&amp;rft.date=2016&amp;rft_id=info%3Adoi%2F10.1145%2F2940343.2940348&amp;rft.aulast=Malik&amp;rft.aufirst=Jyoti&amp;rft_id=http%3A%2F%2Fdl.acm.org%2Fcitation.cfm%3Fid%3D2940348&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMickensNoble2005" class="citation conference cs1">Mickens, James W.; Noble, Brian D. (2005). <a rel="nofollow" class="external text" href="http://dl.acm.org/citation.cfm?id=1080806"><i>Modeling epidemic spreading in mobile environments</i></a>. WiSe '05 Proceedings of the 4th ACM workshop on Wireless security. Association for Computing Machinery, Inc. pp.&#160;77–86. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F1080793.1080806">10.1145/1080793.1080806</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Modeling+epidemic+spreading+in+mobile+environments&amp;rft.pages=77-86&amp;rft.pub=Association+for+Computing+Machinery%2C+Inc.&amp;rft.date=2005&amp;rft_id=info%3Adoi%2F10.1145%2F1080793.1080806&amp;rft.aulast=Mickens&amp;rft.aufirst=James+W.&amp;rft.au=Noble%2C+Brian+D.&amp;rft_id=http%3A%2F%2Fdl.acm.org%2Fcitation.cfm%3Fid%3D1080806&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMulliner2006" class="citation thesis cs1">Mulliner, Collin Richard (2006). <a rel="nofollow" class="external text" href="http://mulliner.org/mobilesecurity/2006_mulliner_MSThesis.pdf"><i>Security of Smart Phones</i></a> <span class="cs1-format">(PDF)</span> (M.Sc. thesis). University of California, Santa Barbara.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&amp;rft.title=Security+of+Smart+Phones&amp;rft.degree=M.Sc.&amp;rft.inst=University+of+California%2C+Santa+Barbara&amp;rft.date=2006&amp;rft.aulast=Mulliner&amp;rft.aufirst=Collin+Richard&amp;rft_id=http%3A%2F%2Fmulliner.org%2Fmobilesecurity%2F2006_mulliner_MSThesis.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFPandya2008" class="citation thesis cs1">Pandya, Vaibhav Ranchhoddas (2008). <a rel="nofollow" class="external text" href="http://www.cs.sjsu.edu/faculty/stamp/students/pandya_vaibhav.pdf"><i>Iphone Security Analysis</i></a> <span class="cs1-format">(PDF)</span> (Thesis). San Jose State University.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&amp;rft.title=Iphone+Security+Analysis&amp;rft.inst=San+Jose+State+University&amp;rft.date=2008&amp;rft.aulast=Pandya&amp;rft.aufirst=Vaibhav+Ranchhoddas&amp;rft_id=http%3A%2F%2Fwww.cs.sjsu.edu%2Ffaculty%2Fstamp%2Fstudents%2Fpandya_vaibhav.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFRaboin2009" class="citation conference cs1 cs1-prop-foreign-lang-source">Raboin, Romain (December 2009). <a rel="nofollow" class="external text" href="http://actes.sstic.org/SSTIC09/La_securite_des_smartphones/SSTIC09-article-R-Raboin-La_securite_des_smartphones.pdf"><i>La sécurité des smartphones</i></a> <span class="cs1-format">(PDF)</span>. <a rel="nofollow" class="external text" href="http://actes.sstic.org/SSTIC09/">Symposium sur la sécurité des technologies de l'information et des communications 2009. SSTIC09</a> (in French).</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=La+s%C3%A9curit%C3%A9+des+smartphones&amp;rft.date=2009-12&amp;rft.aulast=Raboin&amp;rft.aufirst=Romain&amp;rft_id=http%3A%2F%2Factes.sstic.org%2FSSTIC09%2FLa_securite_des_smartphones%2FSSTIC09-article-R-Raboin-La_securite_des_smartphones.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFRacicMaChen2006" class="citation thesis cs1">Racic, Radmilo; Ma, Denys; Chen, Hao (2006). <a rel="nofollow" class="external text" href="http://web.cs.ucdavis.edu/~hchen/paper/securecomm2006.pdf"><i>Exploiting MMS Vulnerabilities to Stealthily Exhaust Mobile Phone's Battery</i></a> <span class="cs1-format">(PDF)</span> (Dissertation). University of California, Davis.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&amp;rft.title=Exploiting+MMS+Vulnerabilities+to+Stealthily+Exhaust+Mobile+Phone%27s+Battery&amp;rft.inst=University+of+California%2C+Davis&amp;rft.date=2006&amp;rft.aulast=Racic&amp;rft.aufirst=Radmilo&amp;rft.au=Ma%2C+Denys&amp;rft.au=Chen%2C+Hao&amp;rft_id=http%3A%2F%2Fweb.cs.ucdavis.edu%2F~hchen%2Fpaper%2Fsecurecomm2006.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFRothPolakRieffel2008" class="citation conference cs1">Roth, Volker; Polak, Wolfgang; Rieffel, Eleanor (2008). <a rel="nofollow" class="external text" href="http://dl.acm.org/citation.cfm?id=1352533.1352569&amp;coll=DL&amp;dl=ACM&amp;CFID=72991384&amp;CFTOKEN=79396606"><i>Simple and Effective Defense Against Evil Twin Access Points</i></a>. ACM SIGCOMM HotNets. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F1352533.1352569">10.1145/1352533.1352569</a>. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-59593-814-5" title="Special:BookSources/978-1-59593-814-5"><bdi>978-1-59593-814-5</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Simple+and+Effective+Defense+Against+Evil+Twin+Access+Points&amp;rft.date=2008&amp;rft_id=info%3Adoi%2F10.1145%2F1352533.1352569&amp;rft.isbn=978-1-59593-814-5&amp;rft.aulast=Roth&amp;rft.aufirst=Volker&amp;rft.au=Polak%2C+Wolfgang&amp;rft.au=Rieffel%2C+Eleanor&amp;rft_id=http%3A%2F%2Fdl.acm.org%2Fcitation.cfm%3Fid%3D1352533.1352569%26coll%3DDL%26dl%3DACM%26CFID%3D72991384%26CFTOKEN%3D79396606&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFRuff2011" class="citation conference cs1 cs1-prop-foreign-lang-source">Ruff, Nicolas (2011). <a rel="nofollow" class="external text" href="https://www.sstic.org/media/SSTIC2011/SSTIC-actes/Securite_Android/SSTIC2011-Article-Securite_Android-ruff.pdf"><i>Sécurité du système Android</i></a> <span class="cs1-format">(PDF)</span>. <a rel="nofollow" class="external text" href="https://www.sstic.org/2011/programme/">Symposium sur la sécurité des technologies de l'information et des communications 2011. SSTIC11</a> (in French).</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=S%C3%A9curit%C3%A9+du+syst%C3%A8me+Android&amp;rft.date=2011&amp;rft.aulast=Ruff&amp;rft.aufirst=Nicolas&amp;rft_id=https%3A%2F%2Fwww.sstic.org%2Fmedia%2FSSTIC2011%2FSSTIC-actes%2FSecurite_Android%2FSSTIC2011-Article-Securite_Android-ruff.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFRuggieroFoote2011" class="citation thesis cs1">Ruggiero, Paul; Foote, Jon (2011). <a rel="nofollow" class="external text" href="https://www.us-cert.gov/sites/default/files/publications/cyber_threats-to_mobile_phones.pdf"><i>Cyber Threats to Mobile Phones</i></a> <span class="cs1-format">(PDF)</span> (thesis). US-CERT.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&amp;rft.title=Cyber+Threats+to+Mobile+Phones&amp;rft.inst=US-CERT&amp;rft.date=2011&amp;rft.aulast=Ruggiero&amp;rft.aufirst=Paul&amp;rft.au=Foote%2C+Jon&amp;rft_id=https%3A%2F%2Fwww.us-cert.gov%2Fsites%2Fdefault%2Ffiles%2Fpublications%2Fcyber_threats-to_mobile_phones.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSchmidtSchmidtClausenYüksel2008" class="citation conference cs1">Schmidt, Aubrey-Derrick; Schmidt, Hans-Gunther; Clausen, Jan; Yüksel, Kamer Ali; Kiraz, Osman; Camtepe, Ahmet; Albayrak, Sahin (October 2008). <a rel="nofollow" class="external text" href="http://www.dai-labor.de/fileadmin/Files/Publikationen/Buchdatei/lk2008-android_security.pdf"><i>Enhancing Security of Linux-based Android Devices</i></a> <span class="cs1-format">(PDF)</span>. Proceedings of 15th International Linux Kongress.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Enhancing+Security+of+Linux-based+Android+Devices&amp;rft.date=2008-10&amp;rft.aulast=Schmidt&amp;rft.aufirst=Aubrey-Derrick&amp;rft.au=Schmidt%2C+Hans-Gunther&amp;rft.au=Clausen%2C+Jan&amp;rft.au=Y%C3%BCksel%2C+Kamer+Ali&amp;rft.au=Kiraz%2C+Osman&amp;rft.au=Camtepe%2C+Ahmet&amp;rft.au=Albayrak%2C+Sahin&amp;rft_id=http%3A%2F%2Fwww.dai-labor.de%2Ffileadmin%2FFiles%2FPublikationen%2FBuchdatei%2Flk2008-android_security.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSchmidtSchmidtBatyukClausen2009a" class="citation conference cs1">Schmidt, Aubrey-Derrick; Schmidt, Hans-Gunther; Batyuk, Leonid; Clausen, Jan Hendrik; Camtepe, Seyit Ahmet; Albayrak, Sahin (April 2009a). <a rel="nofollow" class="external text" href="http://dai-labor.de/fileadmin/files/publications/326600420_android_mw.pdf"><i>Smartphone Malware Evolution Revisited: Android Next Target?</i></a> <span class="cs1-format">(PDF)</span>. 4th International Conference on Malicious and Unwanted Software (MALWARE). <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-4244-5786-1" title="Special:BookSources/978-1-4244-5786-1"><bdi>978-1-4244-5786-1</bdi></a><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-11-30</span></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Smartphone+Malware+Evolution+Revisited%3A+Android+Next+Target%3F&amp;rft.date=2009-04&amp;rft.isbn=978-1-4244-5786-1&amp;rft.aulast=Schmidt&amp;rft.aufirst=Aubrey-Derrick&amp;rft.au=Schmidt%2C+Hans-Gunther&amp;rft.au=Batyuk%2C+Leonid&amp;rft.au=Clausen%2C+Jan+Hendrik&amp;rft.au=Camtepe%2C+Seyit+Ahmet&amp;rft.au=Albayrak%2C+Sahin&amp;rft_id=http%3A%2F%2Fdai-labor.de%2Ffileadmin%2Ffiles%2Fpublications%2F326600420_android_mw.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFShabtaiFledelKanonovElovici2009" class="citation arxiv cs1">Shabtai, Asaf; Fledel, Yuval; Kanonov, Uri; Elovici, Yuval; Dolev, Shlomi (2009). "Google Android: A State-of-the-Art Review of Security Mechanisms". <a href="/wiki/ArXiv_(identifier)" class="mw-redirect" title="ArXiv (identifier)">arXiv</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://arxiv.org/abs/0912.5101v1">0912.5101v1</a></span> [<a rel="nofollow" class="external text" href="https://arxiv.org/archive/cs.CR">cs.CR</a>].</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=preprint&amp;rft.jtitle=arXiv&amp;rft.atitle=Google+Android%3A+A+State-of-the-Art+Review+of+Security+Mechanisms&amp;rft.date=2009&amp;rft_id=info%3Aarxiv%2F0912.5101v1&amp;rft.aulast=Shabtai&amp;rft.aufirst=Asaf&amp;rft.au=Fledel%2C+Yuval&amp;rft.au=Kanonov%2C+Uri&amp;rft.au=Elovici%2C+Yuval&amp;rft.au=Dolev%2C+Shlomi&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFThirumathyamDerawi2010" class="citation conference cs1">Thirumathyam, Rubathas; Derawi, Mohammad O. (2010). <a rel="nofollow" class="external text" href="https://archive.today/20130212202928/http://orbit.dtu.dk/getResource?recordId=265507&amp;objectId=1&amp;versionId=1"><i>Biometric Template Data Protection in Mobile Device Using Environment XML-database</i></a>. 2010 2nd International Workshop on Security and Communication Networks (IWSCN). <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-4244-6938-3" title="Special:BookSources/978-1-4244-6938-3"><bdi>978-1-4244-6938-3</bdi></a>. Archived from <a rel="nofollow" class="external text" href="http://orbit.dtu.dk/getResource?recordId=265507&amp;objectId=1&amp;versionId=1">the original</a> on 2013-02-12.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Biometric+Template+Data+Protection+in+Mobile+Device+Using+Environment+XML-database&amp;rft.date=2010&amp;rft.isbn=978-1-4244-6938-3&amp;rft.aulast=Thirumathyam&amp;rft.aufirst=Rubathas&amp;rft.au=Derawi%2C+Mohammad+O.&amp;rft_id=http%3A%2F%2Forbit.dtu.dk%2FgetResource%3FrecordId%3D265507%26objectId%3D1%26versionId%3D1&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFTöyssyHelenius2006" class="citation journal cs1">Töyssy, Sampo; Helenius, Marko (2006). "About malicious software in smartphones". <i>Journal in Computer Virology</i>. <b>2</b> (2): 109–119. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2Fs11416-006-0022-0">10.1007/s11416-006-0022-0</a>. <a href="/wiki/S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a>&#160;<a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:9760466">9760466</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Journal+in+Computer+Virology&amp;rft.atitle=About+malicious+software+in+smartphones&amp;rft.volume=2&amp;rft.issue=2&amp;rft.pages=109-119&amp;rft.date=2006&amp;rft_id=info%3Adoi%2F10.1007%2Fs11416-006-0022-0&amp;rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A9760466%23id-name%3DS2CID&amp;rft.aulast=T%C3%B6yssy&amp;rft.aufirst=Sampo&amp;rft.au=Helenius%2C+Marko&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li></ul> <div class="mw-heading mw-heading3"><h3 id="Websites">Websites</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=44" title="Edit section: Websites"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <ul><li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFEuropean_Telecommunications_Standards_Institute2011" class="citation web cs1">European Telecommunications Standards Institute (2011). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120512035904/http://www.etsi.org/WebSite/OurServices/Algorithms/3gppalgorithms.aspx">"3GPP Confidentiality and Integrity Algorithms &amp; UEA1 UIA1"</a>. Archived from <a rel="nofollow" class="external text" href="http://www.etsi.org/WebSite/OurServices/Algorithms/3gppalgorithms.aspx">the original</a> on 12 May 2012.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=3GPP+Confidentiality+and+Integrity+Algorithms+%26+UEA1+UIA1&amp;rft.date=2011&amp;rft.au=European+Telecommunications+Standards+Institute&amp;rft_id=http%3A%2F%2Fwww.etsi.org%2FWebSite%2FOurServices%2FAlgorithms%2F3gppalgorithms.aspx&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSiemens2010" class="citation web cs1">Siemens (2010). <a rel="nofollow" class="external text" href="http://www.securityfocus.com/bid/7004/">"Series M Siemens SMS DoS Vulnerability"</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=Series+M+Siemens+SMS+DoS+Vulnerability&amp;rft.date=2010&amp;rft.au=Siemens&amp;rft_id=http%3A%2F%2Fwww.securityfocus.com%2Fbid%2F7004%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li></ul> </div> <div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Mobile_security&amp;action=edit&amp;section=45" title="Edit section: Further reading"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239549316"><div class="refbegin" style=""> <ul><li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1 cs1-prop-foreign-lang-source"><a rel="nofollow" class="external text" href="http://www.cigref.fr/cigref_publications/RapportsContainer/Parus2010/Securisation_de_la_mobilit%C3%A9_2010_CIGREF.pdf">"Sécurisation de la mobilité"</a> <span class="cs1-format">(PDF)</span>. <i>CIGREF</i> (in French). October 2010.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=CIGREF&amp;rft.atitle=S%C3%A9curisation+de+la+mobilit%C3%A9&amp;rft.date=2010-10&amp;rft_id=http%3A%2F%2Fwww.cigref.fr%2Fcigref_publications%2FRapportsContainer%2FParus2010%2FSecurisation_de_la_mobilit%25C3%25A9_2010_CIGREF.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFChong2007" class="citation conference cs1">Chong, Wei Hoo (November 2007). <a rel="nofollow" class="external text" href="http://lutpii.students-blog.undip.ac.id/files/2010/09/iDEN-Smartphone-Embedded-Software-Testing.pdf"><i>iDEN Smartphone Embedded Software Testing</i></a> <span class="cs1-format">(PDF)</span>. Fourth International Conference on Information Technology, 2007. ITNG '07. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FITNG.2007.103">10.1109/ITNG.2007.103</a>. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-0-7695-2776-5" title="Special:BookSources/978-0-7695-2776-5"><bdi>978-0-7695-2776-5</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=iDEN+Smartphone+Embedded+Software+Testing&amp;rft.date=2007-11&amp;rft_id=info%3Adoi%2F10.1109%2FITNG.2007.103&amp;rft.isbn=978-0-7695-2776-5&amp;rft.aulast=Chong&amp;rft.aufirst=Wei+Hoo&amp;rft_id=http%3A%2F%2Flutpii.students-blog.undip.ac.id%2Ffiles%2F2010%2F09%2FiDEN-Smartphone-Embedded-Software-Testing.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFJansen,_WayneScarfone,_Karen2008" class="citation journal cs1">Jansen, Wayne; Scarfone, Karen (October 2008). <a rel="nofollow" class="external text" href="http://csrc.nist.gov/publications/nistpubs/800-124/SP800-124.pdf">"Guidelines on Cell Phone and PDA Security: Recommendations of the National Institute of Standards and Technology"</a> <span class="cs1-format">(PDF)</span>. <i>National Institute of Standards and Technology</i>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.6028%2FNIST.SP.800-124">10.6028/NIST.SP.800-124</a></span><span class="reference-accessdate">. Retrieved <span class="nowrap">April 21,</span> 2012</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=National+Institute+of+Standards+and+Technology&amp;rft.atitle=Guidelines+on+Cell+Phone+and+PDA+Security%3A+Recommendations+of+the+National+Institute+of+Standards+and+Technology&amp;rft.date=2008-10&amp;rft_id=info%3Adoi%2F10.6028%2FNIST.SP.800-124&amp;rft.au=Jansen%2C+Wayne&amp;rft.au=Scarfone%2C+Karen&amp;rft_id=http%3A%2F%2Fcsrc.nist.gov%2Fpublications%2Fnistpubs%2F800-124%2FSP800-124.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMurugiah_P._SouppayaScarfone,_Karen2013" class="citation journal cs1">Murugiah P. Souppaya; Scarfone, Karen (June 21, 2013). <a rel="nofollow" class="external text" href="https://www.nist.gov/publications/guidelines-managing-security-mobile-devices-enterprise">"Guidelines for Managing the Security of Mobile Devices in the Enterprisewebsite=National Institute of Standards and Technology"</a>. <i>NIST</i>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.6028%2FNIST.SP.800-124r1">10.6028/NIST.SP.800-124r1</a></span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=NIST&amp;rft.atitle=Guidelines+for+Managing+the+Security+of+Mobile+Devices+in+the+Enterprisewebsite%3DNational+Institute+of+Standards+and+Technology&amp;rft.date=2013-06-21&amp;rft_id=info%3Adoi%2F10.6028%2FNIST.SP.800-124r1&amp;rft.au=Murugiah+P.+Souppaya&amp;rft.au=Scarfone%2C+Karen&amp;rft_id=https%3A%2F%2Fwww.nist.gov%2Fpublications%2Fguidelines-managing-security-mobile-devices-enterprise&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFLeeSuhJeongMo2008" class="citation conference cs1">Lee, Sung-Min; Suh, Sang-bum; Jeong, Bokdeuk; Mo, Sangdok (January 2008). <i>A Multi-Layer Mandatory Access Control Mechanism for Mobile Devices Based on Virtualization</i>. 5th IEEE Consumer Communications and Networking Conference, 2008. CCNC 2008. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2Fccnc08.2007.63">10.1109/ccnc08.2007.63</a>. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-4244-1456-7" title="Special:BookSources/978-1-4244-1456-7"><bdi>978-1-4244-1456-7</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=A+Multi-Layer+Mandatory+Access+Control+Mechanism+for+Mobile+Devices+Based+on+Virtualization&amp;rft.date=2008-01&amp;rft_id=info%3Adoi%2F10.1109%2Fccnc08.2007.63&amp;rft.isbn=978-1-4244-1456-7&amp;rft.aulast=Lee&amp;rft.aufirst=Sung-Min&amp;rft.au=Suh%2C+Sang-bum&amp;rft.au=Jeong%2C+Bokdeuk&amp;rft.au=Mo%2C+Sangdok&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFLiYangWu2010" class="citation conference cs1">Li, Feng; Yang, Yinying; Wu, Jie (March 2010). <a rel="nofollow" class="external text" href="http://www.cs.ucr.edu/~michalis/COURSES/240-10/papers/cpmc.pdf"><i>CPMC: An Efficient Proximity Malware Coping Scheme in Smartphone-based Mobile Networks</i></a> <span class="cs1-format">(PDF)</span>. INFOCOM, 2010 Proceedings IEEE. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FINFCOM.2010.5462113">10.1109/INFCOM.2010.5462113</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=CPMC%3A+An+Efficient+Proximity+Malware+Coping+Scheme+in+Smartphone-based+Mobile+Networks&amp;rft.date=2010-03&amp;rft_id=info%3Adoi%2F10.1109%2FINFCOM.2010.5462113&amp;rft.aulast=Li&amp;rft.aufirst=Feng&amp;rft.au=Yang%2C+Yinying&amp;rft.au=Wu%2C+Jie&amp;rft_id=http%3A%2F%2Fwww.cs.ucr.edu%2F~michalis%2FCOURSES%2F240-10%2Fpapers%2Fcpmc.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFNiYangBaiChampion2009" class="citation conference cs1">Ni, Xudong; Yang, Zhimin; Bai, Xiaole; Champion, Adam C.; Xuan, Dong (October 2009). <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/xpl/conhome/5312767/proceeding"><i>Distribute: Differentiated User Access Control on Smartphones</i></a>. 6th IEEE International Conference on Mobile Adhoc and Periodic Sensor Systems, 2009. MASS '09. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-4244-5113-5" title="Special:BookSources/978-1-4244-5113-5"><bdi>978-1-4244-5113-5</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=Distribute%3A+Differentiated+User+Access+Control+on+Smartphones&amp;rft.date=2009-10&amp;rft.isbn=978-1-4244-5113-5&amp;rft.aulast=Ni&amp;rft.aufirst=Xudong&amp;rft.au=Yang%2C+Zhimin&amp;rft.au=Bai%2C+Xiaole&amp;rft.au=Champion%2C+Adam+C.&amp;rft.au=Xuan%2C+Dong&amp;rft_id=https%3A%2F%2Fieeexplore.ieee.org%2Fxpl%2Fconhome%2F5312767%2Fproceeding&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFOngtangMcLaughlinEnckMcdaniel2009" class="citation conference cs1">Ongtang, Machigar; McLaughlin, Stephen; Enck, William; Mcdaniel, Patrick (December 2009). <a rel="nofollow" class="external text" href="http://www.patrickmcdaniel.org/pubs/acsac09a.pdf"><i>Semantically Rich Application-Centric Security in Android</i></a> <span class="cs1-format">(PDF)</span>. Annual Computer Security Applications Conference, 2009. ACSAC '09. <i>Annual Computer Security Applications Conference (Acsac)</i>. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1063-9527">1063-9527</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=conference&amp;rft.jtitle=Annual+Computer+Security+Applications+Conference+%28Acsac%29&amp;rft.atitle=Semantically+Rich+Application-Centric+Security+in+Android&amp;rft.date=2009-12&amp;rft.issn=1063-9527&amp;rft.aulast=Ongtang&amp;rft.aufirst=Machigar&amp;rft.au=McLaughlin%2C+Stephen&amp;rft.au=Enck%2C+William&amp;rft.au=Mcdaniel%2C+Patrick&amp;rft_id=http%3A%2F%2Fwww.patrickmcdaniel.org%2Fpubs%2Facsac09a.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSchmidtByeSchmidtClausen2009b" class="citation conference cs1">Schmidt, Aubrey-Derrick; Bye, Rainer; Schmidt, Hans-Gunther; Clausen, Jan; Kiraz, Osman; Yüksel, Kamer A.; Camtepe, Seyit A.; Albayrak, Sahin (2009b). <a rel="nofollow" class="external text" href="http://www.dai-labor.de/fileadmin/files/publications/android.pdf"><i>Static Analysis of Executables for Collaborative Malware Detection on Android</i></a> <span class="cs1-format">(PDF)</span>. IEEE International Conference Communications, 2009. ICC '09. <i>Communications, 2009. Icc '09. IEEE International Conference on</i>. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1938-1883">1938-1883</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=conference&amp;rft.jtitle=Communications%2C+2009.+Icc+%2709.+IEEE+International+Conference+on&amp;rft.atitle=Static+Analysis+of+Executables+for+Collaborative+Malware+Detection+on+Android&amp;rft.date=2009&amp;rft.issn=1938-1883&amp;rft.aulast=Schmidt&amp;rft.aufirst=Aubrey-Derrick&amp;rft.au=Bye%2C+Rainer&amp;rft.au=Schmidt%2C+Hans-Gunther&amp;rft.au=Clausen%2C+Jan&amp;rft.au=Kiraz%2C+Osman&amp;rft.au=Y%C3%BCksel%2C+Kamer+A.&amp;rft.au=Camtepe%2C+Seyit+A.&amp;rft.au=Albayrak%2C+Sahin&amp;rft_id=http%3A%2F%2Fwww.dai-labor.de%2Ffileadmin%2Ffiles%2Fpublications%2Fandroid.pdf&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li> <li><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFYangZhouJiaZhang2010" class="citation conference cs1">Yang, Feng; Zhou, Xuehai; Jia, Gangyong; Zhang, Qiyuan (2010). <i>A Non-cooperative Game Approach for Intrusion Detection Systems in Smartphone systems</i>. 8th Annual Communication Networks and Services Research Conference. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FCNSR.2010.24">10.1109/CNSR.2010.24</a>. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-1-4244-6248-3" title="Special:BookSources/978-1-4244-6248-3"><bdi>978-1-4244-6248-3</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=conference&amp;rft.btitle=A+Non-cooperative+Game+Approach+for+Intrusion+Detection+Systems+in+Smartphone+systems&amp;rft.date=2010&amp;rft_id=info%3Adoi%2F10.1109%2FCNSR.2010.24&amp;rft.isbn=978-1-4244-6248-3&amp;rft.aulast=Yang&amp;rft.aufirst=Feng&amp;rft.au=Zhou%2C+Xuehai&amp;rft.au=Jia%2C+Gangyong&amp;rft.au=Zhang%2C+Qiyuan&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AMobile+security" class="Z3988"></span></li></ul> </div> <div class="navbox-styles"><style data-mw-deduplicate="TemplateStyles:r1129693374">.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}</style><style data-mw-deduplicate="TemplateStyles:r1236075235">.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}</style></div><div role="navigation" class="navbox" aria-labelledby="Information_security" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="3"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><style data-mw-deduplicate="TemplateStyles:r1239400231">.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}</style><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Information_security" title="Template:Information security"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Information_security" title="Template talk:Information security"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Information_security" title="Special:EditPage/Template:Information security"><abbr title="Edit this template">e</abbr></a></li></ul></div><div id="Information_security" style="font-size:114%;margin:0 4em"><a href="/wiki/Information_security" title="Information security">Information security</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related security categories</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Computer_security" title="Computer security">Computer security</a></li> <li><a href="/wiki/Automotive_security" title="Automotive security">Automotive security</a></li> <li><a href="/wiki/Cybercrime" title="Cybercrime">Cybercrime</a> <ul><li><a href="/wiki/Cybersex_trafficking" title="Cybersex trafficking">Cybersex trafficking</a></li> <li><a href="/wiki/Computer_fraud" title="Computer fraud">Computer fraud</a></li></ul></li> <li><a href="/wiki/Cybergeddon" title="Cybergeddon">Cybergeddon</a></li> <li><a href="/wiki/Cyberterrorism" title="Cyberterrorism">Cyberterrorism</a></li> <li><a href="/wiki/Cyberwarfare" title="Cyberwarfare">Cyberwarfare</a></li> <li><a href="/wiki/Electromagnetic_warfare" class="mw-redirect" title="Electromagnetic warfare">Electromagnetic warfare</a></li> <li><a href="/wiki/Information_warfare" title="Information warfare">Information warfare</a></li> <li><a href="/wiki/Internet_security" title="Internet security">Internet security</a></li> <li><a class="mw-selflink selflink">Mobile security</a></li> <li><a href="/wiki/Network_security" title="Network security">Network security</a></li> <li><a href="/wiki/Copy_protection" title="Copy protection">Copy protection</a></li> <li><a href="/wiki/Digital_rights_management" title="Digital rights management">Digital rights management</a></li></ul> </div></td><td class="noviewer navbox-image" rowspan="3" style="width:1px;padding:0 0 0 2px"><div><figure class="mw-halign-center" typeof="mw:File"><a href="/wiki/File:CIAJMK1209-en.svg" class="mw-file-description" title="vectorial version"><img alt="vectorial version" src="//upload.wikimedia.org/wikipedia/commons/thumb/c/c5/CIAJMK1209-en.svg/150px-CIAJMK1209-en.svg.png" decoding="async" width="150" height="150" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/c/c5/CIAJMK1209-en.svg/225px-CIAJMK1209-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/c/c5/CIAJMK1209-en.svg/300px-CIAJMK1209-en.svg.png 2x" data-file-width="496" data-file-height="496" /></a><figcaption>vectorial version</figcaption></figure></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Threat_(computer)" class="mw-redirect" title="Threat (computer)">Threats</a></th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Adware" title="Adware">Adware</a></li> <li><a href="/wiki/Advanced_persistent_threat" title="Advanced persistent threat">Advanced persistent threat</a></li> <li><a href="/wiki/Arbitrary_code_execution" title="Arbitrary code execution">Arbitrary code execution</a></li> <li><a href="/wiki/Backdoor_(computing)" title="Backdoor (computing)">Backdoors</a></li> <li>Bombs <ul><li><a href="/wiki/Fork_bomb" title="Fork bomb">Fork</a></li> <li><a href="/wiki/Logic_bomb" title="Logic bomb">Logic</a></li> <li><a href="/wiki/Time_bomb_(software)" title="Time bomb (software)">Time</a></li> <li><a href="/wiki/Zip_bomb" title="Zip bomb">Zip</a></li></ul></li> <li><a href="/wiki/Hardware_backdoor" title="Hardware backdoor">Hardware backdoors</a></li> <li><a href="/wiki/Code_injection" title="Code injection">Code injection</a></li> <li><a href="/wiki/Crimeware" title="Crimeware">Crimeware</a></li> <li><a href="/wiki/Cross-site_scripting" title="Cross-site scripting">Cross-site scripting</a></li> <li><a href="/wiki/Cross-site_leaks" title="Cross-site leaks">Cross-site leaks</a></li> <li><a href="/wiki/DOM_clobbering" title="DOM clobbering">DOM clobbering</a></li> <li><a href="/wiki/History_sniffing" title="History sniffing">History sniffing</a></li> <li><a href="/wiki/Cryptojacking" title="Cryptojacking">Cryptojacking</a></li> <li><a href="/wiki/Botnet" title="Botnet">Botnets</a></li> <li><a href="/wiki/Data_breach" title="Data breach">Data breach</a></li> <li><a href="/wiki/Drive-by_download" title="Drive-by download">Drive-by download</a></li> <li><a href="/wiki/Browser_Helper_Object" title="Browser Helper Object">Browser Helper Objects</a></li> <li><a href="/wiki/Computer_virus" title="Computer virus">Viruses</a></li> <li><a href="/wiki/Data_scraping" title="Data scraping">Data scraping</a></li> <li><a href="/wiki/Denial-of-service_attack" title="Denial-of-service attack">Denial-of-service attack</a></li> <li><a href="/wiki/Eavesdropping" title="Eavesdropping">Eavesdropping</a></li> <li><a href="/wiki/Email_fraud" title="Email fraud">Email fraud</a></li> <li><a href="/wiki/Email_spoofing" title="Email spoofing">Email spoofing</a></li> <li><a href="/wiki/Exploit_(computer_security)" title="Exploit (computer security)">Exploits</a></li> <li><a href="/wiki/Dialer#Fraudulent_dialer" title="Dialer">Fraudulent dialers</a></li> <li><a href="/wiki/Hacktivism" title="Hacktivism">Hacktivism</a></li> <li><a href="/wiki/Infostealer" title="Infostealer">Infostealer</a></li> <li><a href="/wiki/Insecure_direct_object_reference" title="Insecure direct object reference">Insecure direct object reference</a></li> <li><a href="/wiki/Keystroke_logging" title="Keystroke logging">Keystroke loggers</a></li> <li><a href="/wiki/Malware" title="Malware">Malware</a></li> <li><a href="/wiki/Payload_(computing)" title="Payload (computing)">Payload</a></li> <li><a href="/wiki/Phishing" title="Phishing">Phishing</a> <ul><li><a href="/wiki/Voice_phishing" title="Voice phishing">Voice</a></li></ul></li> <li><a href="/wiki/Polymorphic_engine" title="Polymorphic engine">Polymorphic engine</a></li> <li><a href="/wiki/Privilege_escalation" title="Privilege escalation">Privilege escalation</a></li> <li><a href="/wiki/Ransomware" title="Ransomware">Ransomware</a></li> <li><a href="/wiki/Rootkit" title="Rootkit">Rootkits</a></li> <li><a href="/wiki/Scareware" title="Scareware">Scareware</a></li> <li><a href="/wiki/Shellcode" title="Shellcode">Shellcode</a></li> <li><a href="/wiki/Spamming" title="Spamming">Spamming</a></li> <li><a href="/wiki/Social_engineering_(security)" title="Social engineering (security)">Social engineering</a></li> <li><a href="/wiki/Spyware" title="Spyware">Spyware</a></li> <li><a href="/wiki/Software_bug" title="Software bug">Software bugs</a></li> <li><a href="/wiki/Trojan_horse_(computing)" title="Trojan horse (computing)">Trojan horses</a></li> <li><a href="/wiki/Hardware_Trojan" title="Hardware Trojan">Hardware Trojans</a></li> <li><a href="/wiki/Remote_access_trojan" class="mw-redirect" title="Remote access trojan">Remote access trojans</a></li> <li><a href="/wiki/Vulnerability_(computing)" class="mw-redirect" title="Vulnerability (computing)">Vulnerability</a></li> <li><a href="/wiki/Web_shell" title="Web shell">Web shells</a></li> <li><a href="/wiki/Wiper_(malware)" title="Wiper (malware)">Wiper</a></li> <li><a href="/wiki/Computer_worm" title="Computer worm">Worms</a></li> <li><a href="/wiki/SQL_injection" title="SQL injection">SQL injection</a></li> <li><a href="/wiki/Rogue_security_software" title="Rogue security software">Rogue security software</a></li> <li><a href="/wiki/Zombie_(computing)" title="Zombie (computing)">Zombie</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Defenses</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Application_security" title="Application security">Application security</a> <ul><li><a href="/wiki/Secure_coding" title="Secure coding">Secure coding</a></li> <li>Secure by default</li> <li><a href="/wiki/Secure_by_design" title="Secure by design">Secure by design</a> <ul><li><a href="/wiki/Misuse_case" title="Misuse case">Misuse case</a></li></ul></li></ul></li> <li><a href="/wiki/Computer_access_control" title="Computer access control">Computer access control</a> <ul><li><a href="/wiki/Authentication" title="Authentication">Authentication</a> <ul><li><a href="/wiki/Multi-factor_authentication" title="Multi-factor authentication">Multi-factor authentication</a></li></ul></li> <li><a href="/wiki/Authorization" title="Authorization">Authorization</a></li></ul></li> <li><a href="/wiki/Computer_security_software" title="Computer security software">Computer security software</a> <ul><li><a href="/wiki/Antivirus_software" title="Antivirus software">Antivirus software</a></li> <li><a href="/wiki/Security-focused_operating_system" title="Security-focused operating system">Security-focused operating system</a></li></ul></li> <li><a href="/wiki/Data-centric_security" title="Data-centric security">Data-centric security</a></li> <li><a href="/wiki/Code_obfuscation" class="mw-redirect" title="Code obfuscation">Obfuscation (software)</a></li> <li><a href="/wiki/Data_masking" title="Data masking">Data masking</a></li> <li><a href="/wiki/Encryption" title="Encryption">Encryption</a></li> <li><a href="/wiki/Firewall_(computing)" title="Firewall (computing)">Firewall</a></li> <li><a href="/wiki/Intrusion_detection_system" title="Intrusion detection system">Intrusion detection system</a> <ul><li><a href="/wiki/Host-based_intrusion_detection_system" title="Host-based intrusion detection system">Host-based intrusion detection system</a> (HIDS)</li> <li><a href="/wiki/Anomaly_detection" title="Anomaly detection">Anomaly detection</a></li></ul></li> <li><a href="/wiki/Information_security_management" title="Information security management">Information security management</a> <ul><li><a href="/wiki/Information_risk_management" class="mw-redirect" title="Information risk management">Information risk management</a></li> <li><a href="/wiki/Security_information_and_event_management" title="Security information and event management">Security information and event management</a> (SIEM)</li></ul></li> <li><a href="/wiki/Runtime_application_self-protection" title="Runtime application self-protection">Runtime application self-protection</a></li> <li><a href="/wiki/Site_isolation" title="Site isolation">Site isolation</a></li></ul> </div></td></tr></tbody></table></div> <div class="navbox-styles"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236075235"></div><div role="navigation" class="navbox" aria-labelledby="Mobile_phones" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239400231"><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Mobile_phones" title="Template:Mobile phones"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Mobile_phones" title="Template talk:Mobile phones"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Mobile_phones" title="Special:EditPage/Template:Mobile phones"><abbr title="Edit this template">e</abbr></a></li></ul></div><div id="Mobile_phones" style="font-size:114%;margin:0 4em"><a href="/wiki/Mobile_phone" title="Mobile phone">Mobile phones</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Cellular_network" title="Cellular network">Mobile<br />networks</a>,<br />protocols</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><td colspan="2" class="navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Channel_capacity" title="Channel capacity">Channel capacity</a></li> <li><a href="/wiki/Cellular_frequencies" title="Cellular frequencies">Frequencies</a></li> <li><a href="/wiki/Multi-band_device" title="Multi-band device">Multi-band</a></li> <li><a href="/wiki/Mobile_phone_operator" title="Mobile phone operator">Network operator</a> <ul><li><a href="/wiki/List_of_mobile_network_operators" title="List of mobile network operators">list</a></li></ul></li> <li><a href="/wiki/Roaming" title="Roaming">Roaming</a></li> <li><a href="/wiki/Mobile_phone_signal" title="Mobile phone signal">Signal</a></li> <li><a href="/wiki/SIM_card" title="SIM card">SIM card</a> <ul><li><a href="/wiki/Dual_SIM" title="Dual SIM">dual SIM</a></li> <li><a href="/wiki/ESIM" title="ESIM">eSIM</a></li> <li><a href="/wiki/SIM_lock" title="SIM lock">SIM lock</a></li></ul></li> <li><a href="/wiki/Comparison_of_mobile_phone_standards" title="Comparison of mobile phone standards">Standards comparison</a></li> <li><a href="/wiki/Tethering" title="Tethering">Tethering</a></li> <li><a href="/wiki/Mobile_VoIP" title="Mobile VoIP">VoIP</a></li> <li><a href="/wiki/Wireless_Application_Protocol" title="Wireless Application Protocol">WAP</a></li> <li><a href="/wiki/XHTML_Mobile_Profile" title="XHTML Mobile Profile">XHTML-MP</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/List_of_mobile_phone_generations" class="mw-redirect" title="List of mobile phone generations">Generations</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><b>Analogue</b>:</li> <li><a href="/wiki/Mobile_radio_telephone" title="Mobile radio telephone">0G</a></li> <li><a href="/wiki/1G" title="1G">1G</a></li> <li><b>Digital</b>:</li> <li><a href="/wiki/2G" title="2G">2G</a></li> <li><a href="/wiki/3G" title="3G">3G</a> <ul><li><a href="/wiki/3G_adoption" title="3G adoption">adoption</a></li></ul></li> <li><a href="/wiki/High_Speed_Packet_Access" title="High Speed Packet Access">3.5G</a></li> <li><a href="/wiki/4G" title="4G">4G</a></li> <li><a href="/wiki/LTE_Advanced_Pro" class="mw-redirect" title="LTE Advanced Pro">4.5G</a></li> <li><a href="/wiki/5G" title="5G">5G</a></li> <li><a href="/wiki/6G" title="6G">6G</a></li></ul> </div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">General<br />operation</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Mobile_phone_feature" title="Mobile phone feature">Features</a></li> <li><a href="/wiki/GSM" title="GSM">GSM</a> <ul><li><a href="/wiki/GSM_services" title="GSM services">services</a></li></ul></li> <li><a href="/wiki/History_of_mobile_phones" title="History of mobile phones">History</a></li> <li><a href="/wiki/Mobile_operating_system" title="Mobile operating system">Operating system</a></li> <li><a class="mw-selflink selflink">Security</a> <ul><li><a href="/wiki/Phone_cloning" title="Phone cloning">phone cloning</a></li></ul></li> <li><a href="/wiki/Mobile_telephony" title="Mobile telephony">Telephony</a> <ul><li><a href="/wiki/Airplane_mode" title="Airplane mode">airplane mode</a></li></ul></li> <li><a href="/wiki/Text_messaging" title="Text messaging">Text messaging</a> <ul><li><a href="/wiki/Short_Message_Service" class="mw-redirect" title="Short Message Service">SMS</a></li> <li><a href="/wiki/Multimedia_Messaging_Service" title="Multimedia Messaging Service">MMS</a></li> <li><a href="/wiki/Rich_Communication_Services" title="Rich Communication Services">RCS</a></li></ul></li> <li><a href="/wiki/Mobile_phone_spam" title="Mobile phone spam">Spam</a></li> <li><a href="/wiki/Mobile_phone_tracking" title="Mobile phone tracking">Tracking</a></li> <li><a href="/wiki/Mobile_web" title="Mobile web">Web browsing</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Mobile_device" title="Mobile device">Mobile<br />devices</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><td colspan="2" class="navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><b><a href="/wiki/Category:Mobile_phone_manufacturers" title="Category:Mobile phone manufacturers">Manufacturers</a></b></li> <li><a href="/wiki/List_of_3D-enabled_mobile_phones" title="List of 3D-enabled mobile phones">3D phone</a></li> <li><a href="/wiki/Camera_phone" title="Camera phone">Camera phone</a></li> <li><a href="/wiki/Car_phone" title="Car phone">Car phone</a></li> <li><a href="/wiki/Feature_phone" title="Feature phone">Feature phone</a></li> <li><a href="/wiki/Projector_phone" title="Projector phone">Projector phone</a></li> <li><a href="/wiki/Satellite_phone" title="Satellite phone">Satellite phone</a></li> <li><a href="/wiki/Smartphone" title="Smartphone">Smartphone</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Form_factor_(mobile_phones)" title="Form factor (mobile phones)">Form factors</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Form_factor_(mobile_phones)#Bar" title="Form factor (mobile phones)">Bar</a></li> <li><a href="/wiki/Clamshell_design" title="Clamshell design">Flip</a></li> <li><a href="/wiki/Phablet" title="Phablet">Phablet</a></li> <li><a href="/wiki/Form_factor_(mobile_phones)#Slider" title="Form factor (mobile phones)">Slider</a></li> <li><a href="/wiki/Form_factor_(mobile_phones)#Slate" title="Form factor (mobile phones)">Slate</a></li> <li><a href="/wiki/Smartwatch" title="Smartwatch">Smartwatch</a></li> <li><a href="/wiki/Foldable_smartphone" title="Foldable smartphone">Fold</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Comparison_of_smartphones" title="Comparison of smartphones">Smartphones</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Android_(operating_system)" title="Android (operating system)">Android devices</a> <ul><li><a href="/wiki/Rooting_(Android)" title="Rooting (Android)">rooting</a></li></ul></li> <li><a href="/wiki/BlackBerry_10#Devices" title="BlackBerry 10">BlackBerry 10</a></li> <li><a href="/wiki/IPhone" title="IPhone">iPhone</a> <ul><li><a href="/wiki/IOS_jailbreaking" title="IOS jailbreaking">iOS jailbreaking</a></li></ul></li> <li><a href="/wiki/List_of_open-source_mobile_phones" title="List of open-source mobile phones">Open-source mobile phones</a></li> <li><a href="/wiki/Comparison_of_Symbian_devices" title="Comparison of Symbian devices">Symbian devices</a></li> <li><a href="/wiki/List_of_Windows_phones" title="List of Windows phones">Windows Phone devices</a></li></ul> </div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Mobile<br />specific<br /><a href="/wiki/Software" title="Software">software</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Mobile_app" title="Mobile app">Apps</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Mobile_app_development" title="Mobile app development">Development</a></li> <li><a href="/wiki/List_of_mobile_app_distribution_platforms" title="List of mobile app distribution platforms">Distribution</a></li> <li><a href="/wiki/Mobile_application_management" title="Mobile application management">Management</a></li> <li><a href="/wiki/Mobile_cloud_computing" title="Mobile cloud computing">Cloud computing</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Mobile_commerce" title="Mobile commerce">Commerce</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Mobile_banking" title="Mobile banking">Banking</a></li> <li><a href="/wiki/Mobile_marketing" title="Mobile marketing">Marketing</a> <ul><li><a href="/wiki/Mobile_advertising" title="Mobile advertising">advertising</a></li> <li><a href="/wiki/Mobile_campaign" title="Mobile campaign">campaigns</a></li></ul></li> <li><a href="/wiki/Mobile_payment" title="Mobile payment">Payments</a> <ul><li><a href="/wiki/Contactless_payment" title="Contactless payment">contactless</a></li> <li><a href="/wiki/Mobile_donating" title="Mobile donating">donating</a></li></ul></li> <li><a href="/wiki/Mobile_ticketing" title="Mobile ticketing">Ticketing</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Mobile_content" title="Mobile content">Content</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Mobile_blogging" title="Mobile blogging">Blogging</a></li> <li><a href="/wiki/Push_email" title="Push email">Email</a></li> <li><a href="/wiki/Mobile_gambling" title="Mobile gambling">Gambling</a></li> <li><a href="/wiki/Mobile_game" title="Mobile game">Gaming</a></li> <li><a href="/wiki/MHealth" title="MHealth">Health</a></li> <li><a href="/wiki/Instant_messaging" title="Instant messaging">Instant messaging</a></li> <li><a href="/wiki/M-learning" title="M-learning">Learning</a></li> <li><a href="/wiki/Mobile_music" title="Mobile music">Music</a></li> <li><a href="/wiki/Mobile_news" title="Mobile news">News</a></li> <li><a href="/w/index.php?title=Mobile_search&amp;action=edit&amp;redlink=1" class="new" title="Mobile search (page does not exist)">Search</a> <ul><li><a href="/wiki/Mobile_local_search" title="Mobile local search">local</a></li></ul></li> <li><a href="/wiki/Mobile_social_network" title="Mobile social network">Social</a> <ul><li><a href="/wiki/Mobile_social_address_book" title="Mobile social address book">address book</a></li></ul></li> <li><a href="/wiki/Mobile_television" title="Mobile television">Television</a></li></ul> </div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Category:Mobile_phone_culture" title="Category:Mobile phone culture">Culture</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Box_breaker" title="Box breaker">Box breaking</a></li> <li><a href="/wiki/Mobile_phone_charm" title="Mobile phone charm">Charms</a></li> <li><a href="/wiki/Mobile_comic" title="Mobile comic">Comics</a></li> <li><a href="/wiki/Mobile_dating" title="Mobile dating">Dating</a></li> <li><a href="/wiki/Japanese_mobile_phone_culture" title="Japanese mobile phone culture">Japanese culture</a></li> <li><a href="/wiki/Cell_phone_novel" title="Cell phone novel">Novels</a></li> <li><a href="/wiki/Ringtone" title="Ringtone">Ringtones</a> <ul><li><a href="/wiki/Silent_mode" title="Silent mode">silent mode</a></li></ul></li> <li><a href="/wiki/Selfie" title="Selfie">Selfie</a></li> <li><a href="/wiki/SMS_language" title="SMS language">Txt-spk</a></li> <li><a href="/wiki/Wallpaper_(computing)" title="Wallpaper (computing)">Wallpaper</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Environment<br />and health</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/De_Quervain_syndrome" title="De Quervain syndrome">BlackBerry thumb</a></li> <li><a href="/wiki/Mobile_phones_and_driving_safety" title="Mobile phones and driving safety">Driving safety</a></li> <li><a href="/wiki/Electronic_waste" title="Electronic waste">Electronic waste</a></li> <li><a href="/wiki/Common_external_power_supply" title="Common external power supply">External power supply</a></li> <li><a href="/wiki/Digital_media_use_and_mental_health" title="Digital media use and mental health">Mental health from overuse</a></li> <li><a href="/wiki/Phantom_vibration_syndrome" title="Phantom vibration syndrome">Phantom vibration syndrome</a></li> <li><a href="/wiki/Wireless_device_radiation_and_health" title="Wireless device radiation and health">Radiation and health</a></li> <li><a href="/wiki/Mobile_phone_recycling" title="Mobile phone recycling">Recycling</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Law" title="Law">Law</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Carrier_IQ" title="Carrier IQ">Carrier IQ</a></li> <li><a href="/wiki/Legality_of_recording_by_civilians" title="Legality of recording by civilians">Legality of recording by civilians</a></li> <li><a href="/wiki/Mobile_phones_in_prison" title="Mobile phones in prison">Mobile phones in prison</a></li> <li><a href="/wiki/Photography_and_the_law" title="Photography and the law">Photography and the law</a></li> <li><a href="/wiki/Telephone_tapping" class="mw-redirect" title="Telephone tapping">Telephone tapping</a></li> <li><a href="/wiki/Texting_while_driving" title="Texting while driving">Texting while driving</a></li> <li><a href="/wiki/Restrictions_on_cell_phone_use_while_driving_in_the_United_States" title="Restrictions on cell phone use while driving in the United States">USA use restrictions while driving</a></li></ul> </div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div> <ul><li><span class="nowrap"><span class="noviewer" typeof="mw:File"><span><img alt="" src="//upload.wikimedia.org/wikipedia/commons/thumb/4/4e/Telecom-icon.svg/28px-Telecom-icon.svg.png" decoding="async" width="28" height="28" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/4/4e/Telecom-icon.svg/42px-Telecom-icon.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/4/4e/Telecom-icon.svg/56px-Telecom-icon.svg.png 2x" data-file-width="500" data-file-height="500" /></span></span> </span><a href="/wiki/Portal:Telecommunication" title="Portal:Telecommunication">Telecommunication&#32;portal</a></li> <li><span class="nowrap"><span class="noviewer" typeof="mw:File"><span><img alt="telephone icon" src="//upload.wikimedia.org/wikipedia/commons/thumb/b/b8/Telephone_icon_blue_gradient.svg/28px-Telephone_icon_blue_gradient.svg.png" decoding="async" width="28" height="28" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/b/b8/Telephone_icon_blue_gradient.svg/42px-Telephone_icon_blue_gradient.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/b/b8/Telephone_icon_blue_gradient.svg/56px-Telephone_icon_blue_gradient.svg.png 2x" data-file-width="722" data-file-height="722" /></span></span> </span><a href="/wiki/Portal:Telephones" title="Portal:Telephones">Telephones&#32;portal</a></li> <li><span class="noviewer" typeof="mw:File"><span title="Category"><img alt="" src="//upload.wikimedia.org/wikipedia/en/thumb/9/96/Symbol_category_class.svg/16px-Symbol_category_class.svg.png" decoding="async" width="16" height="16" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/en/thumb/9/96/Symbol_category_class.svg/23px-Symbol_category_class.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/9/96/Symbol_category_class.svg/31px-Symbol_category_class.svg.png 2x" data-file-width="180" data-file-height="185" /></span></span>&#160;<a href="/wiki/Category:Mobile_telecommunications" title="Category:Mobile telecommunications">Category</a></li></ul> </div></td></tr></tbody></table></div> <div class="navbox-styles"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236075235"></div><div role="navigation" class="navbox" aria-labelledby="Malware_topics" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239400231"><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Malware" title="Template:Malware"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Malware" title="Template talk:Malware"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Malware" title="Special:EditPage/Template:Malware"><abbr title="Edit this template">e</abbr></a></li></ul></div><div id="Malware_topics" style="font-size:114%;margin:0 4em"><a href="/wiki/Malware" title="Malware">Malware</a> topics</div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Infectious malware</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Comparison_of_computer_viruses" title="Comparison of computer viruses">Comparison of computer viruses</a></li> <li><a href="/wiki/Computer_virus" title="Computer virus">Computer virus</a></li> <li><a href="/wiki/Computer_worm" title="Computer worm">Computer worm</a></li> <li><a href="/wiki/List_of_computer_worms" title="List of computer worms">List of computer worms</a></li> <li><a href="/wiki/Timeline_of_computer_viruses_and_worms" title="Timeline of computer viruses and worms">Timeline of computer viruses and worms</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Concealment</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Backdoor_(computing)" title="Backdoor (computing)">Backdoor</a></li> <li><a href="/wiki/Clickjacking" title="Clickjacking">Clickjacking</a></li> <li><a href="/wiki/Man-in-the-browser" title="Man-in-the-browser">Man-in-the-browser</a></li> <li><a href="/wiki/Man-in-the-middle_attack" title="Man-in-the-middle attack">Man-in-the-middle</a></li> <li><a href="/wiki/Rootkit" title="Rootkit">Rootkit</a></li> <li><a href="/wiki/Trojan_horse_(computing)" title="Trojan horse (computing)">Trojan horse</a></li> <li><a href="/wiki/Zombie_(computing)" title="Zombie (computing)">Zombie computer</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Malware for profit</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Adware" title="Adware">Adware</a></li> <li><a href="/wiki/Botnet" title="Botnet">Botnet</a></li> <li><a href="/wiki/Crimeware" title="Crimeware">Crimeware</a></li> <li><a href="/wiki/Fleeceware" title="Fleeceware">Fleeceware</a></li> <li><a href="/wiki/Form_grabbing" title="Form grabbing">Form grabbing</a></li> <li><a href="/wiki/Dialer#Fraudulent_dialer" title="Dialer">Fraudulent dialer</a></li> <li><a href="/wiki/Infostealer" title="Infostealer">Infostealer</a></li> <li><a href="/wiki/Keystroke_logging" title="Keystroke logging">Keystroke logging</a></li> <li><a href="/wiki/Internet_bot#Malicious_purposes" title="Internet bot">Malbot</a></li> <li><a href="/wiki/Privacy-invasive_software" title="Privacy-invasive software">Privacy-invasive software</a></li> <li><a href="/wiki/Ransomware" title="Ransomware">Ransomware</a></li> <li><a href="/wiki/Rogue_security_software" title="Rogue security software">Rogue security software</a></li> <li><a href="/wiki/Scareware" title="Scareware">Scareware</a></li> <li><a href="/wiki/Spyware" title="Spyware">Spyware</a></li> <li><a href="/wiki/Web_threat" title="Web threat">Web threats</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">By operating system</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Category:Android_(operating_system)_malware" title="Category:Android (operating system) malware">Android malware</a></li> <li><a href="/wiki/Category:Classic_Mac_OS_viruses" title="Category:Classic Mac OS viruses">Classic Mac OS viruses</a></li> <li><a href="/wiki/Category:IOS_malware" title="Category:IOS malware">iOS malware</a></li> <li><a href="/wiki/Linux_malware" title="Linux malware">Linux malware</a></li> <li><a href="/wiki/Category:MacOS_malware" title="Category:MacOS malware">MacOS malware</a></li> <li><a href="/wiki/Macro_virus" title="Macro virus">Macro virus</a></li> <li><a href="/wiki/Mobile_malware" title="Mobile malware">Mobile malware</a></li> <li><a href="/wiki/Palm_OS_viruses" title="Palm OS viruses">Palm OS viruses</a></li> <li><a href="/wiki/HyperCard_viruses" class="mw-redirect" title="HyperCard viruses">HyperCard viruses</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Protection</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Anti-keylogger" title="Anti-keylogger">Anti-keylogger</a></li> <li><a href="/wiki/Antivirus_software" title="Antivirus software">Antivirus software</a></li> <li><a href="/wiki/Browser_security" title="Browser security">Browser security</a></li> <li><a href="/wiki/Data_loss_prevention_software" title="Data loss prevention software">Data loss prevention software</a></li> <li><a href="/wiki/Defensive_computing" title="Defensive computing">Defensive computing</a></li> <li><a href="/wiki/Firewall_(computing)" title="Firewall (computing)">Firewall</a></li> <li><a href="/wiki/Internet_security" title="Internet security">Internet security</a></li> <li><a href="/wiki/Intrusion_detection_system" title="Intrusion detection system">Intrusion detection system</a></li> <li><a class="mw-selflink selflink">Mobile security</a></li> <li><a href="/wiki/Network_security" title="Network security">Network security</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Countermeasures</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Computer_and_network_surveillance" title="Computer and network surveillance">Computer and network surveillance</a></li> <li><a href="/wiki/Honeypot_(computing)" title="Honeypot (computing)">Honeypot</a></li> <li><a href="/wiki/Operation:_Bot_Roast" title="Operation: Bot Roast">Operation: Bot Roast</a></li></ul> </div></td></tr></tbody></table></div> <!-- NewPP limit report Parsed by mw‐web.codfw.main‐6b7f745dd4‐s4j4b Cached time: 20241125140339 Cache expiry: 2592000 Reduced expiry: false Complications: [vary‐revision‐sha1, show‐toc] CPU time usage: 1.350 seconds Real time usage: 1.565 seconds Preprocessor visited node count: 12387/1000000 Post‐expand include size: 266659/2097152 bytes Template argument size: 18847/2097152 bytes Highest expansion depth: 12/100 Expensive parser function count: 26/500 Unstrip recursion depth: 1/20 Unstrip post‐expand size: 259271/5000000 bytes Lua time usage: 0.848/10.000 seconds Lua memory usage: 8390284/52428800 bytes Number of Wikibase entities loaded: 0/400 --> <!-- Transclusion expansion time report (%,ms,calls,template) 100.00% 1349.392 1 -total 19.99% 269.685 1 Template:Reflist 17.91% 241.689 83 Template:Sfn 12.61% 170.193 17 Template:Fix 11.85% 159.850 15 Template:Cite_web 8.47% 114.339 6 Template:Navbox 8.39% 113.255 7 Template:Citation_needed 8.30% 111.945 22 Template:Cite_conference 6.88% 92.807 30 Template:Category_handler 6.47% 87.272 1 Template:Computer_security --> <!-- Saved in parser cache with key enwiki:pcache:idhash:30500317-0!canonical and timestamp 20241125140339 and revision id 1255553561. Rendering was triggered because: page-view --> </div><!--esi <esi:include src="/esitest-fa8a495983347898/content" /> --><noscript><img src="https://login.wikimedia.org/wiki/Special:CentralAutoLogin/start?type=1x1" alt="" width="1" height="1" style="border: none; position: absolute;"></noscript> <div class="printfooter" data-nosnippet="">Retrieved from "<a dir="ltr" href="https://en.wikipedia.org/w/index.php?title=Mobile_security&amp;oldid=1255553561">https://en.wikipedia.org/w/index.php?title=Mobile_security&amp;oldid=1255553561</a>"</div></div> <div id="catlinks" class="catlinks" data-mw="interface"><div id="mw-normal-catlinks" class="mw-normal-catlinks"><a href="/wiki/Help:Category" title="Help:Category">Category</a>: <ul><li><a href="/wiki/Category:Mobile_security" title="Category:Mobile security">Mobile security</a></li></ul></div><div id="mw-hidden-catlinks" class="mw-hidden-catlinks mw-hidden-cats-hidden">Hidden categories: <ul><li><a href="/wiki/Category:Articles_with_short_description" title="Category:Articles with short description">Articles with short description</a></li><li><a href="/wiki/Category:Short_description_is_different_from_Wikidata" title="Category:Short description is different from Wikidata">Short description is different from Wikidata</a></li><li><a href="/wiki/Category:All_articles_with_unsourced_statements" title="Category:All articles with unsourced statements">All articles with unsourced statements</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_October_2023" title="Category:Articles with unsourced statements from October 2023">Articles with unsourced statements from October 2023</a></li><li><a href="/wiki/Category:Articles_needing_additional_references_from_October_2023" title="Category:Articles needing additional references from October 2023">Articles needing additional references from October 2023</a></li><li><a href="/wiki/Category:All_articles_needing_additional_references" title="Category:All articles needing additional references">All articles needing additional references</a></li><li><a href="/wiki/Category:All_articles_with_vague_or_ambiguous_time" title="Category:All articles with vague or ambiguous time">All articles with vague or ambiguous time</a></li><li><a href="/wiki/Category:Vague_or_ambiguous_time_from_March_2023" title="Category:Vague or ambiguous time from March 2023">Vague or ambiguous time from March 2023</a></li><li><a href="/wiki/Category:Wikipedia_articles_needing_clarification_from_October_2023" title="Category:Wikipedia articles needing clarification from October 2023">Wikipedia articles needing clarification from October 2023</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_March_2023" title="Category:Articles with unsourced statements from March 2023">Articles with unsourced statements from March 2023</a></li><li><a href="/wiki/Category:All_articles_with_specifically_marked_weasel-worded_phrases" title="Category:All articles with specifically marked weasel-worded phrases">All articles with specifically marked weasel-worded phrases</a></li><li><a href="/wiki/Category:Articles_with_specifically_marked_weasel-worded_phrases_from_March_2023" title="Category:Articles with specifically marked weasel-worded phrases from March 2023">Articles with specifically marked weasel-worded phrases from March 2023</a></li><li><a href="/wiki/Category:All_articles_with_failed_verification" title="Category:All articles with failed verification">All articles with failed verification</a></li><li><a href="/wiki/Category:Articles_with_failed_verification_from_October_2023" title="Category:Articles with failed verification from October 2023">Articles with failed verification from October 2023</a></li><li><a href="/wiki/Category:Articles_needing_additional_references_from_November_2022" title="Category:Articles needing additional references from November 2022">Articles needing additional references from November 2022</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_February_2017" title="Category:Articles with unsourced statements from February 2017">Articles with unsourced statements from February 2017</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_April_2012" title="Category:Articles with unsourced statements from April 2012">Articles with unsourced statements from April 2012</a></li><li><a href="/wiki/Category:All_articles_with_incomplete_citations" title="Category:All articles with incomplete citations">All articles with incomplete citations</a></li><li><a href="/wiki/Category:Articles_with_incomplete_citations_from_March_2023" title="Category:Articles with incomplete citations from March 2023">Articles with incomplete citations from March 2023</a></li><li><a href="/wiki/Category:CS1_French-language_sources_(fr)" title="Category:CS1 French-language sources (fr)">CS1 French-language sources (fr)</a></li></ul></div></div> </div> </main> </div> <div class="mw-footer-container"> <footer id="footer" class="mw-footer" > <ul id="footer-info"> <li id="footer-info-lastmod"> This page was last edited on 5 November 2024, at 14:47<span class="anonymous-show">&#160;(UTC)</span>.</li> <li id="footer-info-copyright">Text is available under the <a href="/wiki/Wikipedia:Text_of_the_Creative_Commons_Attribution-ShareAlike_4.0_International_License" title="Wikipedia:Text of the Creative Commons Attribution-ShareAlike 4.0 International License">Creative Commons Attribution-ShareAlike 4.0 License</a>; additional terms may apply. By using this site, you agree to the <a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use" class="extiw" title="foundation:Special:MyLanguage/Policy:Terms of Use">Terms of Use</a> and <a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy" class="extiw" title="foundation:Special:MyLanguage/Policy:Privacy policy">Privacy Policy</a>. Wikipedia® is a registered trademark of the <a rel="nofollow" class="external text" href="https://wikimediafoundation.org/">Wikimedia Foundation, Inc.</a>, a non-profit organization.</li> </ul> <ul id="footer-places"> <li id="footer-places-privacy"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy">Privacy policy</a></li> <li id="footer-places-about"><a href="/wiki/Wikipedia:About">About Wikipedia</a></li> <li id="footer-places-disclaimers"><a href="/wiki/Wikipedia:General_disclaimer">Disclaimers</a></li> <li id="footer-places-contact"><a href="//en.wikipedia.org/wiki/Wikipedia:Contact_us">Contact Wikipedia</a></li> <li id="footer-places-wm-codeofconduct"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Universal_Code_of_Conduct">Code of Conduct</a></li> <li id="footer-places-developers"><a href="https://developer.wikimedia.org">Developers</a></li> <li id="footer-places-statslink"><a href="https://stats.wikimedia.org/#/en.wikipedia.org">Statistics</a></li> <li id="footer-places-cookiestatement"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Cookie_statement">Cookie statement</a></li> <li id="footer-places-mobileview"><a href="//en.m.wikipedia.org/w/index.php?title=Mobile_security&amp;mobileaction=toggle_view_mobile" class="noprint stopMobileRedirectToggle">Mobile view</a></li> </ul> <ul id="footer-icons" class="noprint"> <li id="footer-copyrightico"><a href="https://wikimediafoundation.org/" class="cdx-button cdx-button--fake-button cdx-button--size-large cdx-button--fake-button--enabled"><img src="/static/images/footer/wikimedia-button.svg" width="84" height="29" alt="Wikimedia Foundation" loading="lazy"></a></li> <li id="footer-poweredbyico"><a href="https://www.mediawiki.org/" class="cdx-button cdx-button--fake-button cdx-button--size-large cdx-button--fake-button--enabled"><img src="/w/resources/assets/poweredby_mediawiki.svg" alt="Powered by MediaWiki" width="88" height="31" loading="lazy"></a></li> </ul> </footer> </div> </div> </div> <div class="vector-settings" id="p-dock-bottom"> <ul></ul> </div><script>(RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgHostname":"mw-web.codfw.main-5cd4cd96d5-xb5z6","wgBackendResponseTime":191,"wgPageParseReport":{"limitreport":{"cputime":"1.350","walltime":"1.565","ppvisitednodes":{"value":12387,"limit":1000000},"postexpandincludesize":{"value":266659,"limit":2097152},"templateargumentsize":{"value":18847,"limit":2097152},"expansiondepth":{"value":12,"limit":100},"expensivefunctioncount":{"value":26,"limit":500},"unstrip-depth":{"value":1,"limit":20},"unstrip-size":{"value":259271,"limit":5000000},"entityaccesscount":{"value":0,"limit":400},"timingprofile":["100.00% 1349.392 1 -total"," 19.99% 269.685 1 Template:Reflist"," 17.91% 241.689 83 Template:Sfn"," 12.61% 170.193 17 Template:Fix"," 11.85% 159.850 15 Template:Cite_web"," 8.47% 114.339 6 Template:Navbox"," 8.39% 113.255 7 Template:Citation_needed"," 8.30% 111.945 22 Template:Cite_conference"," 6.88% 92.807 30 Template:Category_handler"," 6.47% 87.272 1 Template:Computer_security"]},"scribunto":{"limitreport-timeusage":{"value":"0.848","limit":"10.000"},"limitreport-memusage":{"value":8390284,"limit":52428800},"limitreport-logs":"anchor_id_list = table#1 {\n [\"CITEREFAndy_Greenberg2015\"] = 1,\n [\"CITEREFAvivGibsonMossopBlaze\"] = 1,\n [\"CITEREFBecher2009\"] = 1,\n [\"CITEREFBecherFreilingHoffmannHolz2011\"] = 1,\n [\"CITEREFBilton2010\"] = 1,\n [\"CITEREFBishop2004\"] = 1,\n [\"CITEREFCaiChenWuZhang2015\"] = 1,\n [\"CITEREFCharlie_Sorrel2010\"] = 1,\n [\"CITEREFChong2007\"] = 1,\n [\"CITEREFCrussellGiblerChen2012\"] = 1,\n [\"CITEREFDagonMartinStarder2004\"] = 1,\n [\"CITEREFDiogenes2019\"] = 1,\n [\"CITEREFDixonMishra2010\"] = 1,\n [\"CITEREFDunhamAbu_NimehBecher2008\"] = 1,\n [\"CITEREFEuropean_Telecommunications_Standards_Institute2011\"] = 1,\n [\"CITEREFFurnell2009\"] = 1,\n [\"CITEREFGendrullis2008\"] = 1,\n [\"CITEREFGittleson2014\"] = 1,\n [\"CITEREFGuoWangZhu2004\"] = 1,\n [\"CITEREFGupta2016\"] = 1,\n [\"CITEREFHaas2015\"] = 1,\n [\"CITEREFHalbronnSigwald2010\"] = 1,\n [\"CITEREFHamilton2018\"] = 1,\n [\"CITEREFHogbenDekker2010\"] = 1,\n [\"CITEREFJansen,_WayneScarfone,_Karen2008\"] = 1,\n [\"CITEREFJøsangMiralabéDallot2015\"] = 1,\n [\"CITEREFKasmiLopes_Esteves2015\"] = 1,\n [\"CITEREFLeavitt2011\"] = 1,\n [\"CITEREFLeeSuhJeongMo2008\"] = 1,\n [\"CITEREFLemos\"] = 1,\n [\"CITEREFLiYangWu2010\"] = 1,\n [\"CITEREFLiuPatrasLeith2021\"] = 1,\n [\"CITEREFMalik2016\"] = 1,\n [\"CITEREFMcCaney2012\"] = 1,\n [\"CITEREFMichael_SW_LeeIan_Soon2017\"] = 1,\n [\"CITEREFMickensNoble2005\"] = 1,\n [\"CITEREFMulliner2006\"] = 1,\n [\"CITEREFMurugiah_P._SouppayaScarfone,_Karen2013\"] = 1,\n [\"CITEREFMylonasKastaniaGritzalis2013\"] = 1,\n [\"CITEREFNg\"] = 1,\n [\"CITEREFNiYangBaiChampion2009\"] = 1,\n [\"CITEREFOlson2013\"] = 1,\n [\"CITEREFOngtangMcLaughlinEnckMcdaniel2009\"] = 1,\n [\"CITEREFPandya2008\"] = 1,\n [\"CITEREFRaboin2009\"] = 1,\n [\"CITEREFRacicMaChen2006\"] = 1,\n [\"CITEREFRogers2013\"] = 1,\n [\"CITEREFRothPolakRieffel2008\"] = 1,\n [\"CITEREFRuff2011\"] = 1,\n [\"CITEREFRuggieroFoote2011\"] = 1,\n [\"CITEREFSchmidtByeSchmidtClausen2009b\"] = 1,\n [\"CITEREFSchmidtSchmidtBatyukClausen2009a\"] = 1,\n [\"CITEREFSchmidtSchmidtClausenYüksel2008\"] = 1,\n [\"CITEREFShabtaiFledelKanonovElovici2009\"] = 1,\n [\"CITEREFSiemens2010\"] = 1,\n [\"CITEREFSuarez-TangilJuan_E._TapiadorPedro_Peris-LopezArturo_Ribagorda2014\"] = 1,\n [\"CITEREFThirumathyamDerawi2010\"] = 1,\n [\"CITEREFTöyssyHelenius2006\"] = 1,\n [\"CITEREFVaughan-Nichols\"] = 1,\n [\"CITEREFYangZhouJiaZhang2010\"] = 1,\n}\ntemplate_list = table#1 {\n [\"About\"] = 1,\n [\"Additional citation needed\"] = 1,\n [\"As of when?\"] = 1,\n [\"Citation needed\"] = 7,\n [\"Cite arXiv\"] = 1,\n [\"Cite book\"] = 5,\n [\"Cite conference\"] = 22,\n [\"Cite journal\"] = 10,\n [\"Cite magazine\"] = 3,\n [\"Cite news\"] = 5,\n [\"Cite thesis\"] = 8,\n [\"Cite web\"] = 15,\n [\"Clarify\"] = 2,\n [\"Code\"] = 1,\n [\"Computer security\"] = 1,\n [\"Failed verification\"] = 4,\n [\"Full citation needed\"] = 1,\n [\"Lit\"] = 1,\n [\"Main\"] = 4,\n [\"Malware\"] = 1,\n [\"Mobile phones\"] = 1,\n [\"More citations needed\"] = 1,\n [\"Refbegin\"] = 3,\n [\"Refend\"] = 3,\n [\"Reflist\"] = 1,\n [\"Search link\"] = 1,\n [\"See also\"] = 5,\n [\"Sfn\"] = 83,\n [\"Short description\"] = 1,\n [\"Since when?\"] = 1,\n [\"Which\"] = 1,\n [\"Which?\"] = 1,\n}\narticle_whitelist = table#1 {\n}\ntable#1 {\n [\"size\"] = \"small\",\n}\ntable#1 {\n [\"size\"] = \"small\",\n}\n"},"cachereport":{"origin":"mw-web.codfw.main-6b7f745dd4-s4j4b","timestamp":"20241125140339","ttl":2592000,"transientcontent":false}}});});</script> <script type="application/ld+json">{"@context":"https:\/\/schema.org","@type":"Article","name":"Mobile security","url":"https:\/\/en.wikipedia.org\/wiki\/Mobile_security","sameAs":"http:\/\/www.wikidata.org\/entity\/Q3268325","mainEntity":"http:\/\/www.wikidata.org\/entity\/Q3268325","author":{"@type":"Organization","name":"Contributors to Wikimedia projects"},"publisher":{"@type":"Organization","name":"Wikimedia Foundation, Inc.","logo":{"@type":"ImageObject","url":"https:\/\/www.wikimedia.org\/static\/images\/wmf-hor-googpub.png"}},"datePublished":"2011-01-16T23:47:01Z","dateModified":"2024-11-05T14:47:12Z","headline":"safeguards and best practices against security attacks or exploits that target software vulnerabilities in mobile devices"}</script> </body> </html>

Pages: 1 2 3 4 5 6 7 8 9 10