Introduction
As mobile health (mHealth) applications become central to remote patient monitoring and chronic disease management, they handle an increasing volume of Electronic Patient Health Information (ePHI). In the United States, the Health Insurance Portability and Accountability Act (HIPAA) mandates strict technical safeguards for this data. However, a significant gap often exists between regulatory compliance claims and the technical reality of local data storage. This study performs a digital forensic "autopsy" on popular Android medical applications to evaluate their effectiveness in protecting sensitive user data.
Methodology
The researchers conducted a controlled forensic experiment using a five-stage workflow:
- Environment Setup: A Samsung Galaxy S4 running Android 5.0 was utilized for its compatibility with physical extraction tools.
- Data Generation: Three major medical app suites—iHealth MyVitals, iHealth Gluco-Smart, and Withings Health Mate—were installed. Researchers generated realistic test data using six medical devices over a five-day period.
- Forensic Imaging: A bit-for-bit physical image of the smartphone's internal memory was created using MSAB XRY (v7.7).
- Artifact Analysis: The images were analyzed using XAMN and AccessData FTK to locate SQLite databases and XML configuration files.
- Validation: Recovered digital artifacts were cross-referenced against manual logs of the measurements taken during the trial.
Forensic Analysis and Findings
The investigation revealed that two out of the three tested application suites stored Protected Health Information (PHI) in unencrypted plaintext, potentially violating HIPAA regulations and exposing users to identity theft or medical profiling.
The Plaintext Pitfall
The iHealth MyVitals and Withings Health Mate applications stored sensitive medical readings—including systolic/diastolic blood pressure, pulse rates, and oxygen levels—in SQLite databases without encryption.
As shown in the recovered database artifacts, medical measurements such as blood oxygen saturation (Result) and pulse rate (PR) are clearly visible. This lack of encryption means that any actor with physical access to the device or root-level malware could easily extract a patient's medical history.
Security Credential Leakage
Perhaps the most critical vulnerability discovered was the storage of authentication credentials. The iHealth MyVitals app stored the user’s plaintext password and session tokens within an XML file (sp_user_region_host_info.xml).
This "Master Key" leak represents a catastrophic security failure. By recovering the plaintext password (e.g., "MedExp2018") and active session tokens, an attacker could bypass local device security and compromise the user's entire cloud-based medical profile.
Discussion and Compliance Gap
The study highlights a significant compliance gap. While all three manufacturers claim HIPAA compliance on their websites, the forensic evidence demonstrates a failure to implement the required technical safeguards for data at rest. Only the iHealth Gluco-Smart app successfully encrypted its local databases, making it the only app in the study to truly align with HIPAA’s Security Rule.
Beyond medical stats, the apps leaked "lifestyle" metadata, such as environmental conditions (humidity, lighting) recorded by smart scales. Such data can be used to construct invasive behavioral profiles of users.
Conclusion and Future Work
The research underscores the urgent need for more rigorous oversight of mHealth applications. While modern Android versions have improved default encryption, app-level database security remains a developer responsibility. Future research will expand this forensic analysis to iOS platforms and a broader range of IoT medical devices to determine if these security blind spots persist in the modern mobile ecosystem.
Summary updated