{"id":18520,"date":"2021-07-08T01:04:53","date_gmt":"2021-07-07T21:04:53","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/18520\/"},"modified":"2022-05-05T11:03:46","modified_gmt":"2022-05-05T07:03:46","slug":"mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/18520\/","title":{"rendered":"Artificial intelligence in every smartphone"},"content":{"rendered":"

Here at Kaspersky, we\u2019ve been using AI in our mobile security solution<\/a> for some time now. At the recent Mobile World Congress in Barcelona, Viktor Chebyshev of our Global Research and Analysis Team (GReAT) talked about why \u2014 and what we\u2019ve achieved with the technology.<\/p>\n

A brief history of mobile malware evolution<\/h2>\n

First, a bit of background on the evolution of malicious apps for Android. The operating system appeared back in 2007, and the first Android smartphone, the HTC Dream, became available in 2008. Malware writers quickly got to know the new platform, and by 2009 the world saw the first malicious programs for Android<\/a>.<\/p>\n

True, there weren\u2019t many at first: Back in 2009, Kaspersky was detecting about three new Android threats a month, a number Chebyshev, armed with only a simple signature-based antivirus engine, could manage on his own.<\/p>\n

\"In<\/a>

In 2009, we detected three new samples of Android malware per month on average<\/p><\/div>\n

Very soon, however, the number of threats snowballed, and by 2010 our monthly detections of new Android malware had shot up to 20,000. The signature-based engine still managed, but far more time was spent on analyzing the malicious files.<\/p>\n

As the operating system\u2019s popularity soared, the amount of new Android malware swelled. In 2012, we were detecting an average of 467,515 samples per month, our team of mobile threat analysts had grown to four, and heuristic analysis<\/a> and statistical methods supplemented the signature-based engine \u2014 but that wasn\u2019t enough.<\/p>\n

Fttkit provides a striking example of how mobile threats have evolved. The creators of this Trojan dropper call it an \u201cautomated service to protect Android apps,\u201d but it actually helps fellow malware writers evade antivirus detection. It works by using obfuscation<\/a> to trick security solutions and then installing other malware, usually banking Trojans. We know of more than 360,000 unique versions of Fttkit,\u00a0and the figure continues to grow.<\/p>\n

AI for mobile security<\/h2>\n

To pick through that number of malware samples manually would require an ever-expanding team, and, more important, would take a lot of time (during which users could pick up new malware).<\/p>\n

That\u2019s where machine-learning technologies come in\u00a0and can save significant amounts of time and resources. However, such technologies are quite resource-intensive, meaning that doing all of the necessary work right on a user\u2019s device can reduce performance and battery life. To minimize the impact, we use a hybrid option, with the smartphone performing less-resource-intense operations and then sending data to the cloud for the heavy lifting. This model ensures reliable protection and quick responses to new threats with minimal impact on smartphone performance and battery life.<\/p>\n

Here\u2019s what we achieved by implementing machine learning in Kaspersky for Android<\/a>:<\/p>\n

The verdict delivered by the machine-learning technologies in our solution for Android\u00a0\u2014 DangerousObject.AndroidOS.GenericML\u00a0\u2014 is currently on the Top-3 list, accounting for 6.63% of all malware for this operating system detected by our products.<\/p>\n

\"This<\/a>

This verdict from our machine-learning technologies is among the three most common<\/p><\/div>\n

Most significantly, our mobile products detect around 33% of all new<\/em> Android threats using AI.<\/p>\n

This is made possible by a combination of factors. First, we have an extensive mobile threat database, which we have maintained since 2009. Second, our team of mobile threat researchers has unique expertise in the field. Third, we have a team of machine-learning experts who effectively integrate this technology into our products. All this combined helps our mobile security solutions<\/a> consistently top independent tests<\/a> in terms of both protection and performance.<\/p>\n\n","protected":false},"excerpt":{"rendered":"

We’ve been using machine learning in Kaspersky Internet Security for Android for years now. Here’s why \u2014 and what we’ve achieved.<\/p>\n","protected":false},"author":2706,"featured_media":18525,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[7,1226],"tags":[1481,105,1583,2804,1415,2467,320,527,2468],"class_list":{"0":"post-18520","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-products","8":"category-technology","9":"tag-ai","10":"tag-android","11":"tag-artificial-intelligence","12":"tag-kaspersky-for-android","13":"tag-machine-learning","14":"tag-ml","15":"tag-mobile-world-congress","16":"tag-mwc","17":"tag-mwc21"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/18520\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/23038\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/9248\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/24990\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/22998\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/22285\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/25606\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/25080\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/31010\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/9817\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/40526\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/17749\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/15030\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/27034\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/31196\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/27267\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/24079\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/29414\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/mwc21-artificial-intelligence-in-kaspersky-internet-security-for-android\/29206\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/android\/","name":"Android"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/18520","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2706"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=18520"}],"version-history":[{"count":2,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/18520\/revisions"}],"predecessor-version":[{"id":18524,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/18520\/revisions\/18524"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/18525"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=18520"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=18520"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=18520"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}