{'fraction_non_alphanumeric': 0.013157894736842105, 'fraction_numerical': 0.0008223684210526315, 'mean_word_length': 5.614130434782608, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Mandatory Enforcement of Geofenced Security in Android

Android applications are today driving most of the aspects of business. But corresponding threats of information breach through a malware or naive users are also increasing many folds. It becomes extremely difficult for any organisation to allow employees to seamlessly use android based smartphones within office premises while keeping the related threats at bay. Situation is even more difficult for an organisation related to finance, defence, medicine, reasearch etc., where employees handle sensitive and confidential data. Usually, these threats are ignored else employers try to impose various physical restrictions which incur huge costs and inconvenience. In this regard, this paper proposes a novel scheme to enforce constraints on android based smartphones to mitigate above threats. It provides kernel level restriction on existing Android applications from accessing various smartphone resources whenever host device enters a predefined geographical boundary of an enterprise. This is achieved by dynamic security policies in SEAndroid. It utilises Android source from AOSP ported on Google Pixel2 XL device to demonstrate nuances of practicality.