Proceedings of the 2016 ACM Workshop on Software PROtection 2016
DOI: 10.1145/2995306.2995316
|View full text |Cite
|
Sign up to set email alerts
|

The ASPIRE Framework for Software Protection

Abstract: In the ASPIRE research project, a software protection tool flow was designed and prototyped that targets native ARM Android code. This tool flow supports the deployment of a number of protections against man-at-the-end attacks. In this tutorial, an overview of the tool flow will be presented and attendants will participate to a hands-on demonstration. In addition, we will present an overview of the decision support systems developed in the project to facilitate the use of the protection tool flow.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2016
2016
2020
2020

Publication Types

Select...
2
2
1

Relationship

2
3

Authors

Journals

citations
Cited by 5 publications
(7 citation statements)
references
References 0 publications
0
7
0
Order By: Relevance
“…We do confirm, however, that all attacks considered as relevant in the scope of the ASPIRE project by both its academic and its industrial partners, are covered by our meta-model. From this discussion, and from the final validation report [43] of the ASPIRE project, we conclude that requirements R1-R6 are met with respect to the concepts and relations considered relevant in the scope of the ASPIRE project.…”
Section: Validation On Software Protection Tool Chainmentioning
confidence: 81%
See 1 more Smart Citation
“…We do confirm, however, that all attacks considered as relevant in the scope of the ASPIRE project by both its academic and its industrial partners, are covered by our meta-model. From this discussion, and from the final validation report [43] of the ASPIRE project, we conclude that requirements R1-R6 are met with respect to the concepts and relations considered relevant in the scope of the ASPIRE project.…”
Section: Validation On Software Protection Tool Chainmentioning
confidence: 81%
“…Security experts from the industrial partners determined the assets in the C code, as well as their security requirements. A pseudonomynous list of them can be found in Section 5 of the ASPIRE Validation Report [43]. The security experts, together with the developers of the ACTC, then also determined which configurations of protections have to be deployed on each asset to achieve sufficient protection against attacks on the assets.…”
Section: Validation Of Work Flow On Industrial Use Casesmentioning
confidence: 99%
“…Tigress [11] and ASPIRE framework [6] are source code level obfuscation tools published in academic research. These are source-to-source obfuscators that also contain controlflow obfuscation techniques.…”
Section: A Source-level Obfuscation Techniquesmentioning
confidence: 99%
“…This paper considers two locations for obfuscation techniques in software: at the source code level and the binary level-or both [6] 1 . When distributors need to disseminate source code of a piece of software, it is likely that source code, or source-level, obfuscation will be applied.…”
Section: Introductionmentioning
confidence: 99%
“…anti-debugging, which makes more difficult to perform dynamic analysis by attaching a trusted debugger, preventing attackers from using their own [2]; -algorithm hiding, a set of obfuscation techniques against the reverse engineering, protecting a code's confidentiality and understandability [3]; -call stack checks, which verifies the execution correctness by checking that functions are called in the right order [4]; -barrier slicing, which enforces the integrity of data and code areas by moving them to a trusted server where they will be executed [5]; -code guards, which are checks added in an application to detect and react to integrity breaches [6]; -code mobility, which protects application parts from reverse engineering and analysis by removing them from the application to be installed at run time when they need to be executed [7]; -data hiding, which involves altering the data structures and the functions' data flow for ensuring data confidentiality [8]; -remote attestation, which protects application integrity by forcing the application to periodically send integrity proofs to a verification server [9].…”
Section: Approachmentioning
confidence: 99%