Slide 1

Blue ZoneContext Based Access ControlAndroid applicationPresented bySHYAM SUNDAR SVENKATESH SGAYATHRI KPRIYABHAARATHI RGuided byRAMESH P NAsst prof - Dept of CSE#Batch 8Blue ZoneAbstract Misuse of the data by malicious applications from our android device may result in privacy breaches and sensitive data leakage. The problem arises from the fact that Android users do not have control over the application capabilities once the applications have been granted the requested privileges upon installation. so that context based access control restrictions can be applied and executed. #Batch 8Blue Zone2Existing systemLacking of security for specific application services.Not effective for complete system wide process.All the services are disabled and enabled once and for all yet results in non usability of the required services Application must be deactivated and activated for each specific location.

#Batch 8Blue ZoneLimitationsDo not cover all the possible ways in which applications can access user data and device resources.

The User leakage of Their privacy.

not accurate enough to identify the location.#Batch 8Blue ZoneProposed systemContext-based access control (CBAC) mechanism for Android systems that allows smartphone users to set configuration policies users can set restricted privileges for device applications when using the device at work, and device applications may re-gain their original privileges when the device is used at home. This change in device privileges is automatically applied as soon as the user device matches a pre-defined context of a user-defined policy. #Batch 8Blue ZoneOvercoming the limitations in existing systemApplications should not be able to fake the location of the device.

Can develop securer and more acceptable applications for end users.

#Batch 8Blue ZoneSystem Architecture

#Batch 8Blue ZoneModules1. Context Provider

2. Access Controller

3. Policy Manager

4. Policy Executor

#Batch 8Blue Zone1. Context ProviderProviding content to applications. The context Provider is the interface between the provider and other applications. Together, providers and provider clients offer a consistent, standard interface to data that also handles inter-process communication and secure data access.

#Batch 8Blue Zone2. Access ControllerThe Access Controller controls the authorizations of applications and prevents unauthorized usage of device resources or services. The Access Controller complements this system with more control methods and specific fine-grained control permissions that better reflect the application capabilities and narrow down its accessibility to resources.

#Batch 8Blue Zone3.Policy ManagerThe Policy Manager (PM) represents the interface used to create policies, mainly assigning application restrictions to contexts. It mainly gives control to the user to configure which resources and services are accessible by applications at the given context provided by the Context Provider.

#Batch 8Blue Zone4. Policy ExecutorThe Policy Executor (PE) enforces device restrictions by comparing the devices context with the configured policies. Once an application requests access to a resource or service, the PE checks the user-configured restrictions set at the Policy Manager to either grant to deny access to the application request. #Batch 8Blue ZoneUse Case Diagram

#Batch 8Blue ZoneScreen Shots

#Batch 8Blue ZoneScreen Shots

#Batch 8Blue ZoneScreen Shots

#Batch 8Blue ZoneScreen Shots

#Batch 8Blue ZoneScreen Shots

#Batch 8Blue ZoneScreen Shots

#Batch 8Blue ZoneScreen Shots

#Batch 8Blue ZoneScreen Shots

#Batch 8Blue ZoneConclusionWe proposed a modified version of the Android OS supporting context-based access control policies. The restrictions specified in a policy are automatically applied as soon as the user device matches the pre-defined context associated with the policy. #Batch 8Blue ZoneThank you#Batch 8Blue Zone