Skip to content

OWASP MSTG Compliance Checklist — PPP Mobile App ​

Target assurance level: MASVS Level 2 (medical data application)

Scanner: mobsfscan — integrated into the weekly security-scan.yml GitHub Actions workflow.

Last baseline: 2026-03-04


How the CI Gate Works ​

SeverityCI Behaviour
High / ERRORBlocks the workflow (exit 1) — mirrors the existing Semgrep gate
Warning / MediumCreates or updates a GitHub issue automatically (label: security:mobile-mstg)
InfoLogged in the step summary; no action taken

Running Locally ​

bash
pip install mobsfscan
mobsfscan mobile/ppp
# JSON output:
mobsfscan --json -o results.json mobile/ppp

MASVS Baseline Status ​

The following table maps each MASVS category to the current compliance status of the PPP mobile app. Items marked Automated are checked by mobsfscan on every weekly security scan. Items marked Manual require periodic human review.

MASVS-STORAGE — Data Storage ​

#RequirementStatusDetectionNotes
MSTG-STORAGE-1App does not store sensitive data in system logsPending reviewAutomatedmobsfscan checks for console.log / NSLog with tokens
MSTG-STORAGE-2No sensitive data stored in backupsPartialManualiOS UIFileSharingEnabled: true in app.config.js exposes documents to iTunes file sharing
MSTG-STORAGE-3App does not write sensitive data to application logsPending reviewAutomatedCovered by MSTG-STORAGE-1 scan rule
MSTG-STORAGE-5Keyboard cache disabled for sensitive inputsPending reviewManualNot yet audited
MSTG-STORAGE-7No sensitive data in screenshots/snapshotsPending reviewManualNo FLAG_SECURE (Android) or snapshot protection (iOS)
MSTG-STORAGE-12PII minimised in local storageGapManualMMKV stores accessToken + user object unencrypted; see SECURITY.md

MASVS-CRYPTO — Cryptography ​

#RequirementStatusDetectionNotes
MSTG-CRYPTO-1No hardcoded cryptographic keysPassAutomatedmobsfscan rule; no keys found in source
MSTG-CRYPTO-3App uses proven cryptographic primitivesPassManualTLS via AWS Lambda; MMKV supports AES-256 (not yet enabled)
MSTG-CRYPTO-6No weak random number generators for securityPending reviewAutomatedmobsfscan checks for Math.random() in security contexts

MASVS-AUTH — Authentication ​

#RequirementStatusDetectionNotes
MSTG-AUTH-1Authentication enforced at backendPassManualCognito JWT validated by tRPC middleware
MSTG-AUTH-2Session management handled server-sidePartialManualCognito manages sessions; no refresh token flow on mobile
MSTG-AUTH-8Biometric authentication (if used) is not event-bound onlyN/AManualBiometric auth not yet implemented

MASVS-NETWORK — Network Communication ​

#RequirementStatusDetectionNotes
MSTG-NETWORK-1All network traffic encrypted (TLS)PassAutomatedLambda Function URL enforces HTTPS
MSTG-NETWORK-2TLS settings follow best practicesPassAutomatedAWS-managed TLS 1.2+
MSTG-NETWORK-3Certificate pinning implementedPassAutomatedwithCertificatePinning plugin configured in app.config.js
MSTG-NETWORK-4App does not trust custom CAsPending reviewAutomatedmobsfscan checks for network security config issues

MASVS-PLATFORM — Platform Interaction ​

#RequirementStatusDetectionNotes
MSTG-PLATFORM-1App requests minimum necessary permissionsGapManualACCESS_BACKGROUND_LOCATION, WRITE_EXTERNAL_STORAGE may be over-scoped
MSTG-PLATFORM-2Input from external sources validatedPassManualtRPC + Zod validates all API inputs server-side
MSTG-PLATFORM-3App does not export sensitive functionality via IPCPending reviewAutomatedmobsfscan checks exported components
MSTG-PLATFORM-5JavaScript disabled in WebViews unless necessaryGapManualWebView has javaScriptEnabled: true for Cognito auth
MSTG-PLATFORM-6WebView configured to allow minimum protocol handlersPending reviewManualNo originWhitelist restriction on auth WebView

MASVS-CODE — Code Quality ​

#RequirementStatusDetectionNotes
MSTG-CODE-1App signed with valid certificatePassManualEAS Build handles signing
MSTG-CODE-2App built in release modePassManualEAS production profile uses release mode
MSTG-CODE-3Debug symbols removed from releasePending reviewManualExpo managed workflow; needs verification
MSTG-CODE-4No debugging code or verbose loggingPending reviewAutomatedmobsfscan checks for debug patterns
MSTG-CODE-9Obfuscation applied (L2)GapManualNo Hermes bytecode obfuscation configured

MASVS-RESILIENCE — Anti-Tampering (Level 2) ​

#RequirementStatusDetectionNotes
MSTG-RESILIENCE-1Jailbreak/root detectionGapManualNot implemented; see SECURITY.md
MSTG-RESILIENCE-2App detects and responds to debuggerGapManualNot implemented
MSTG-RESILIENCE-3App detects and responds to tamperingGapManualNot implemented
MSTG-RESILIENCE-5App detects and responds to emulatorGapManualNot implemented

Expected Baseline Findings ​

The following findings are expected on the initial mobsfscan run and represent known gaps documented in docs/site/mobile/security.md. These will be triaged and resolved through dedicated GitHub issues.

Expected FindingSeverityMSTG IDTracking
MMKV storage without encryption keyHighMSTG-STORAGE-12Documented in SECURITY.md
UIFileSharingEnabled: true in iOS configWarningMSTG-STORAGE-2app.config.js
JavaScript enabled in WebViewWarningMSTG-PLATFORM-5Required for Cognito auth flow
Background location permissionWarningMSTG-PLATFORM-1Required for hospital proximity
console.log statements in sourceInfoMSTG-STORAGE-1Normal for development; stripped in production
No jailbreak/root detectionN/A (manual)MSTG-RESILIENCE-1Documented in SECURITY.md

Maintaining This Checklist ​

  1. Weekly scan — the security-scan.yml workflow runs mobsfscan every Monday at 06:00 UTC
  2. New findings — medium-severity findings auto-create GitHub issues with security:mobile-mstg label
  3. Resolving findings — when a finding is fixed, the next clean scan auto-closes the issue
  4. Manual review — items marked "Manual" should be reviewed quarterly or before each production release
  5. Updating this doc — when a gap is resolved, update the Status column and add the PR reference

Internal documentation — org members only