54 lines
1.2 KiB
Markdown
54 lines
1.2 KiB
Markdown
# Lab TRB-3: Mobile Security Inspection
|
|
|
|
Domain:
|
|
- 3.0 Software Troubleshooting
|
|
|
|
Works on:
|
|
- Android
|
|
- iOS
|
|
|
|
## Goal
|
|
|
|
Inspect mobile security signals without installing or removing apps.
|
|
|
|
## Part 1: App Source Review
|
|
|
|
Pick three installed apps and record:
|
|
- App name:
|
|
- Source or store if visible:
|
|
- Developer name if visible:
|
|
- Permissions that seem sensitive:
|
|
|
|
## Part 2: Device Controls
|
|
|
|
Record:
|
|
- OS update status:
|
|
- Unknown sources or sideloading status if visible:
|
|
- Developer mode status if visible:
|
|
- VPN status:
|
|
- Device management profile or MDM status if visible:
|
|
|
|
## Part 3: Data and Battery Signals
|
|
|
|
Record:
|
|
- Highest mobile data user:
|
|
- Highest battery user:
|
|
- Any app you do not recognize:
|
|
- Any unexpected ads, redirects, or warnings:
|
|
|
|
## Part 4: Scenario Practice
|
|
|
|
Choose the risk:
|
|
|
|
1. User installed a bank app from a link in a text message.
|
|
2. Phone shows ads when no browser is open.
|
|
3. Device is jailbroken.
|
|
4. A weather app uses large amounts of background data.
|
|
5. Fake virus warnings appear repeatedly.
|
|
|
|
## What You Should Learn
|
|
|
|
- Mobile compromise often looks like odd app behavior, ads, or data usage.
|
|
- Rooting, jailbreaking, sideloading, and unofficial stores raise risk.
|
|
- Managed devices should follow organization policy and MDM procedures.
|
|
|