Guillaume "B.B." Van Hemmen
f454a1d1ee
Changed the restart policy condition from "on-failure" to "any" to ensure the container restarts on any circumstance. Removed the maximum attempts and window restrictions to allow continuous attempts without limitation. |
||
|---|---|---|
| .env.dist | ||
| .gitignore | ||
| docker-compose.yml | ||
| README.md | ||
MobSF
Introduction
Mobile Security Framework (MobSF) is an automated, all-in-one mobile application (Android/iOS/Windows) pen-testing, malware analysis, and security assessment framework capable of performing static and dynamic analysis.
Table of Contents
Prerequisites
- Docker: Make sure Docker is installed and running on your system.
- Docker Compose: Docker Compose is required to orchestrate the container setup.
- Traefik Deployment:
- Deployed Traefik standalone or
- Deployed Traefik Authelia.
Installation
- Clone the repository:
git clone https://git.van-hemmen.com/GuillaumeHemmen-DockerCompose-Infra/mobsf.git
cd mobsf
- Copy the environment variable template:
cp .env.dist .env
- Customize the
.envfile as necessary for your environment.
Note: You must define a basic authentication in MOBSF_BASIC_AUTH to protect your instance of MobSF.
Usage
Start the MobSF service with Docker Compose:
docker compose up -d
Access MobSF by navigating to https://<MOBSF_FQDN> in your web browser. You will need to authenticate using the basic auth setup in your .env file.
Post-launch
MobSF uses a fixed UID for the files persisted. To have the volume approach work, you must change the ownership of the data inside the volume as follows:
docker run --rm -v mobsf_data:/vol alpine sh -c "chown --recursive 9901:9901 /vol"
Note: The default volume name is assumed to be mobsf_data. Please adapt your command if it is different.