To add a further complication to our setup, we want this to be as automated a process as possible. In this example, the app id is - substitute this for the app you want to audit. The user should only be involved in the process to open and interact with the desired app. This allows the auditor, who has a degree of technical proficiency, to be separate from the user, who may have special access to app functionality (such as logging in with their credentials). We will assume there is a third party auditor involved in the setup, who we want to be able to remotely access the device and issue commands. The user should not have to issue any commands themselves to do this. In the setup phase, the intention is to allow the user to launch an app in a way that its traffic can be intercepted. Where there isn’t sufficient documentation available, we’ve gone into further detail and provided screenshots. We breeze through some of the steps below for the sake of brevity, but almost all are well-documented elsewhere.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |