/
AutoCog: Measuring the Description-to-permission Fidelity i AutoCog: Measuring the Description-to-permission Fidelity i

AutoCog: Measuring the Description-to-permission Fidelity i - PowerPoint Presentation

karlyn-bohler
karlyn-bohler . @karlyn-bohler
Follow
396 views
Uploaded On 2016-06-15

AutoCog: Measuring the Description-to-permission Fidelity i - PPT Presentation

Zhengyang Qu 1 Vaibhav Rastogi 1 Xinyi Zhang 12 Yan Chen 1 Tiantian Zhu 3 and Zhong Chen 4 1 1 Northwestern University IL US 2 Fudan University Shanghai China ID: 363844

noun permission application description permission noun description application dpr autocog model semantic phrase system semantics set amp permissions relatedness

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "AutoCog: Measuring the Description-to-pe..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

AutoCog: Measuring the Description-to-permission Fidelity in Android Applications

Zhengyang Qu1, Vaibhav Rastogi1, Xinyi Zhang1,2, Yan Chen1, Tiantian Zhu3, and Zhong Chen4

1

1

Northwestern University, IL, US,

2

Fudan University, Shanghai, China,

3

Zhejiang University, Hangzhou, China,

4

Wind Mobile, Toronto, CanadaSlide2

Outline

Problem StatementApproach & DesignEvaluationConclusions2Slide3

Outline

Problem StatementApproach & DesignEvaluationConclusions3Slide4

Motivations

Android Permission SystemAccess control by permission systemFew users can understand security implications from requested permissions User expectation v.s. Application BehaviorUser expectation based on application descriptionPermission defines application behaviorAssess how well permission align with description4Slide5

Desired Systems

Application developersEnd users Requirements:Rich semantic informationIndependent of external resourceAutomation5Slide6

Challenge & Contributions

Inferring description semanticsSimilar meaning may be conveyed in a vast diversity of natural language text“friends”, “contact list”, “address book”Correlating description semantics with permission semanticsA number of functionalities described may map to the same permission“enable navigation”, “display map”, “find restaurant nearby”61. Leverage stat-of-the-art NLP techniques2. Design a learning-based algorithmSlide7

System Prototype

Available on Google Playhttps://play.google.com/store/apps/details?id=com.version1.autocog7Slide8

Outline

Problem StatementApproach & DesignDescription Semantics (DS) ModelDescription-to-Permission Relatedness (DPR) ModelEvaluationConclusion8Slide9

System Overview

9Slide10

System Overview

10Slide11

System Overview

11Slide12

Ontology modeling

Logical dependency between verb phrase and noun phrase<“scan”, “barcode”> for CAMERA, <“record”, “voice”> for RECORD_AUDIOLogical dependency between noun phrases <“scanner”, “barcode”>, <“note”, “voice”>Noun phrase with possessive<“your”, “camera”>, <“own”, “voice”>12Slide13

Description Semantics Model (Contribution 1)

Extract Abstract SemanticsExplicit Semantic Analysis (ESA)Computing the semantic relatedness of textsLeverage a big document corpus (Wikipedia) as the knowledge base and constructs a vector representationAdvantages:Rich semantic information, Quantitative representation of semantics13Slide14

Description-to-Permission

Relatedness (DPR) Model (Contribution 2)Learning-based methodInput: application permission, application descriptionOutput: <np-counterpart, noun phrase> correlated with each sensitive permission14Slide15

Samples in DPR Model

PermissionSemantic PatternsWRITE_EXTERNAL_STORAGE<delete, audio file>, <convert, file format>ACCESS_FINE_LOCATION<display, map>, <find, branch atm>, <your location>ACCESS_COARSE_LOCATION<set, gps navigation>, <remember, location>GET_ACCOUNTS<manage, account>, <integrate, facebook>RECEIVE_BOOT_COMPLETED<change, hd

paper>, <display, notification>CAMERA

<deposit, check>, <scanner, barcode>, <snap, photo>

READ_CONTACTS

<block,

text message

>, <beat, facebook friend>

RECORD_AUDIO

<send, voice message>,

<note, voice>

WRITE_SETTINGS

<set, ringtone>, <enable,

flight mode

>

WRITE_CONTACTS

<wipe, contact list>, <secure, text message>

READ_CALENDAR

<optimize, time>, <synchronize, calendar>

15Slide16

Learning Algorithm for DPR

S1: Grouping noun phrasesCreate semantic relatedness score matrix <“map”, [(“map”, 1.00), (“map view”, 0.96), (“interactive map”, 0.89), …]>S2: Selecting Noun Phrases Correlated with PermissionsNot biased to frequently occurring noun phrasesJointly consider conditional probabilities:P(perm | np) and P(np | perm)16Slide17

Learning Algorithm for DPR(cont’d)

S3: Pairing np-counterpart with Noun Phrase“Retrieve Running Apps permission is required because, if the user is not looking at the widget actively (for e.g. he might using another app like Google Maps)”17Slide18

Outline

Problem StatementApproach & DesignEvaluationConclusions18Slide19

Evaluation

Training set: 36,060 applicationsValidation set: 1,785 applications (150-200 for each permissions), 11 sensitive permissions19Slide20

Closely Related Work

Whyper, Pandita et al., USENIX Security 2013Leverages API documentation to generate a semantics modelAPIs are mapped to permissions using PScoutLimitationsLimited semantic information“Blow into the mic to extinguish the flame…” for RECORD_AUDIO permission not in API documentLack of associated APIsRECEIVE_BOOT_COMPLETED has no associated APIsLack of automation20Slide21

Accuracy Comparison

21SystemPrecision (%)Recall (%)F-score (%)Accuracy (%)AutoCog92.692.092.393.2Whyper85.5

66.574.8

79.9Slide22

Results

22Case Studies:AutoCog TP/ Whyper FN:“Filter by contact, in/out SMS”, “5 calendar views”AutoCog TN/Whyper FP“Saving event attendance status now works on Android 4.0”AutoCog FN/Whyper TP“Ability to navigate to a Contact if that Contact has address”AutoCog FP/Whyper TN“Set recording as ringtone”Latency: 4.5 s check an applicationSlide23

Conclusions

AutoCog is a system to measure the description-to-permission fidelityLearning-based algorithm to generate DPR model, better accuracy performance, ability to extend over other permissionsOngoing workOptimize the training algorithm to improve the scalabilitySimplify our semantics models23Slide24

AutoCog App

24Slide25

25

Thank you!http://list.cs.northwestern.edu/mobile/Questions?Slide26

NLP Module

Sentence boundary disambiguation (SBD)Description is split into sentences for subsequent sentence structure analysis (Stanford Parser)Grammatical structure analysisStanford Parser outputs typed dependencies and PoS tagging of each wordExtract pairs of noun phrase and np-counterpartRemove stopwords and named entities; Normalized by lowercasing and lemmatization26Slide27

Description-to-Permission Relatedness (DPR) Model (Contribution 2)

27Slide28

Decision

Extract all pairs of noun phrase and np-counterpartCondition:28Slide29

Deployment

29Slide30

DPR Model (cont’d)

Pairing np-counterpart with Noun PhraseTo explore the context and semantic dependenciesSP: total number of descriptions where the pair <nc, np’> is detected, the number of application requesting the permission is 30Slide31

Measurement Results

Another 45,811 applications, DPR model trained in accuracy evaluation31Negative correlation between the number of questionable permissions of one application by a specific developer with the total number of applications published by that developer:r = -0.405, p < 0.001Slide32

Backup

32Slide33

Back up

33