Skip to main content
QMSQMS
QMS
  • Welcome to your QMS
  • Quality Manual
  • Procedures
  • Records
  • Legit.Health Plus Version 1.1.0.0
    • Index of Technical Documentation or Product File
    • Summary of Technical Documentation (STED)
    • Description and specifications
    • R-TF-001-007 Declaration of conformity
    • GSPR
    • Artificial Intelligence
    • Clinical
    • Cybersecurity
      • R-TF-024-001 Software Bills Of Materials
      • R-TF-024-002 Cyber Security Risk Management Plan
      • R-TF-024-003 Cyber Security Risk Matrix
      • R-TF-024-004 Security Risk Assessment Report
      • R-TF-025-005 Security Risk Testing Report
      • T-024-006 Threat Model Document
      • T-024-007 Cybersecurity Post-Market Surveillance Plan
      • T-024-009 Security Architecture Document
    • Design and development
    • Design History File
    • IFU and label
    • Post-Market Surveillance
    • Quality control
    • Risk Management
    • Usability and Human Factors Engineering
  • Legit.Health Plus Version 1.1.0.1
  • Licenses and accreditations
  • Applicable Standards and Regulations
  • Public tenders
  • Legit.Health Plus Version 1.1.0.0
  • Cybersecurity
  • R-TF-025-005 Security Risk Testing Report

R-TF-025-005 Security Risk Testing Report

Instructions

Provide a link to the security risk testing report, which should have the following sections:

  • Introduction: This section sets the stage by providing background information and defining the boundaries of the analysis.
  • Methodology: This outlines the approach taken for the analysis, including the tools used.
  • Synthesis: This section presents a summary of the findings, including the results of penetration tests, a breakdown of vulnerabilities found, and a table detailing these vulnerabilities.
  • Description of the report: This section likely elaborates on the vulnerabilities identified and provides recommendations for remediation.
  • Static Analysis: This part focuses on the security analysis of the Android application itself and its source code without executing it.
  • Dynamic Analysis: This section covers the analysis of the application and its environment while it is running, looking at the Android application attack surface, process filesystem, process memory, and DICOM manipulation.
  • Attacks on models: This suggests an analysis or testing of security related to data models, potentially machine learning models, within the system.
  • Penetration test results: This section likely provides detailed results from the penetration testing, specifically mentioning a vulnerable dependency (DCMTK) and Android app code obfuscation.

Signature meaning

The signatures for the approval process of this document can be found in the verified commits at the repository for the QMS. As a reference, the team members who are expected to participate in this document and their roles in the approval process, as defined in Annex I Responsibility Matrix of the GP-001, are:

  • Author: Team members involved
  • Reviewer: JD-003, JD-004
  • Approver: JD-001
Previous
R-TF-024-004 Security Risk Assessment Report
Next
T-024-006 Threat Model Document
All the information contained in this QMS is confidential. The recipient agrees not to transmit or reproduce the information, neither by himself nor by third parties, through whichever means, without obtaining the prior written permission of Legit.Health (AI LABS GROUP S.L.)