The first day of the DEMO conference here saw a range of clever applications that drew the occasional hoots of appreciation, laughter for presentation and polite applause for functionality. There wasn’t much to indicate the company had anything but another mobile security solution as CEO Sujit Jain explained how the company’s Maverick Secure Mobile software can help protect a phone that’s been stolen. Once a thief swaps out a phone’s SIM card (define), the application works in the background to notify the owner of the change by sending an alert to a pre-designated alternate number — a second phone you own, or one belonging to a friend, colleague or family member.<\/p>\n","protected":false},"excerpt":{"rendered":"
If the software detects that your phone’s SIM card has been altered, it will notify your reporting contact phone, sending them a log of calls and messaging activity made on the phone.<\/p>\n
By sending a “Hang” command to your stolen phone, a loud alarm goes off repeatedly. The only way to make it stop — short of smashing the phone — is to remove the battery.<\/p>\n
But that is only short-term relief, as Jain happily explained, since the alarm will resume blaring the moment the battery is replaced. “We’ll have support for Blackberry and Windows Mobile devices in the next four to six weeks,” Jain later told InternetNews.com.<\/p>\n
Jain said the company is negotiating with carriers and other potential partners and expects to have information on rates and availability in the U.S. shortly.<\/p>\n
According to Maverick’s Web site, another feature of the software, called “Spy Call”, will let the owner call the stolen device from the reporting phone.<\/p>\n
http:\/\/www.internetnews.com\/mobility\/article.php\/3770266\/An+Alarming+Development+at+Tech+Conference.htm<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-869","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/869","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=869"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/869\/revisions"}],"predecessor-version":[{"id":3356,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/869\/revisions\/3356"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=869"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=869"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=869"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}