Use when acquire and analyze mobile device data using Cellebrite UFED
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill performing-mobile-device-forensics-with-cellebrite --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Performing Mobile Device Forensics With Cellebrite?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-performing-mobile-device-forensics-with-cellebrite)More formats (shields.io, HTML) on the badges page.
---
name: performing-mobile-device-forensics-with-cellebrite
description: Use when acquire and analyze mobile device data using Cellebrite UFED
and open-source tools to extract communications, location data, and application
artifacts. Use when working with performing mobile device forensics with cellebrite.
domain: cybersecurity
tags:
- forensics
- mobile-forensics
- cellebrite
- smartphone-analysis
- ios-forensics
- android-forensics
subdomain: digital-forensics
version: '1.0'
author: oyi77
license: Apache-2.0
nist_csf:
- RS.AN-01
- RS.AN-03
- DE.AE-02
- RS.MA-01
category: cybersecurity
---
# Performing Mobile Device Forensics With Cellebrite
## Overview
Cybersecurity skill for performing mobile device forensics with cellebrite. Follows industry best practices and security standards.
## When to Use
**Trigger phrases:**
- "performing mobile device forensics with cellebrite"
- "Acquire and analyze mobile device data using Cellebrite UFED and open-source too"
- When extracting evidence from smartphones or tablets during an investigation
- For recovering deleted messages, call logs, and location data from mobile devices
- During investigations involving communications via messaging apps
- When analyzing mobile application data for evidence of criminal activity
- For corporate investigations involving employee mobile device misuse
## When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
## Prerequisites
- Cellebrite UFED Touch/4PC or UFED Physical Analyzer (licensed)
- Alternative open-source tools: ALEAPP, iLEAPP, MEAT, libimobiledevice
- Appropriate cables and adapters for target device
- Faraday bag to isolate the device from network signals
- Legal authorization (warrant, consent, or corporate policy)
- Knowledge of iOS and Android file system structures
## Workflow
```python
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
```
1. **Plan Operations** — Define objectives, scope, and success criteria for mobile device forensics operations.
2. **Prepare Environment** — Set up tools, access, and data sources required for mobile device forensics.
3. **Execute Core Workflow** — Use cellebrite to perform mobile device forensics operations following established procedures.
4. **Validate Results** — Verify that results meet quality standards and objectives.
5. **Report Findings** — Document results, observations, and recommendations.
6. **Follow Up** — Track remediation actions and verify fixes where applicable.
## Tools
- **cellebrite** — Primary tool for this skill
- **Analysis Platform** — Data processing and visualization
- **Collaboration Tools** — Team coordination and knowledge sharing
## Process
1. **Reconnaissance** — Gather target information, identify attack surface, enumerate services
1. **Analysis/Exploitation** — Execute the technique, analyze results, document findings
1. **Reporting** — Document IOCs, write findings, provide remediation recommendations
## Verification
- [ ] All mobile device forensics procedures executed completely and documented
- [ ] Findings validated against multiple data sources
- [ ] False positives identified and filtered
- [ ] Results documented with evidence and timestamps
- [ ] Recommendations provided with risk-based prioritization
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |
| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!