Skip to main content
QMSQMS
QMS
  • Welcome to your QMS
  • Quality Manual
  • Procedures
    • GP-001 Control of documents
    • GP-002 Quality planning
    • GP-003 Audits
    • GP-004 Vigilance system
    • GP-005 Human Resources and Training
    • GP-006 Non-conformity, Corrective and Preventive actions
    • GP-007 Post-market surveillance
    • GP-009 Sales
    • GP-010 Purchases and suppliers evaluation
    • GP-011 Provision of service
    • GP-012 Design, redesign and development
    • GP-013 Risk management
    • GP-014 Feedback and complaints
    • GP-015 Clinical evaluation
    • GP-016 Traceability and identification
    • GP-017 Technical assistance service
    • GP-018 Infrastructure and facilities
      • Templates
      • Specific procedures
        • SP-018-001 Remote infrastructure control access policy
        • SP-018-002 AWS console-managed resources procedure
    • GP-019 Non-product software validation
    • GP-020 QMS Data analysis
    • GP-021 Communications
    • GP-022 Document translation
    • GP-023 Change control management
    • GP-024 Predetermined Change Control Plan
    • GP-025 Usability and Human Factors Engineering
    • GP-027 Corporate Governance
    • GP-028 AI Development
    • GP-029 Software Delivery and Commissioning
    • GP-030 Cyber Security Management
    • GP-050 Data Protection
    • GP-051 Security violations
    • GP-052 Data Privacy Impact Assessment (DPIA)
    • GP-100 Business Continuity (BCP) and Disaster Recovery plans (DRP)
    • GP-101 Information security
    • GP-200 Remote Data Acquisition in Clinical Investigations
    • GP-026 Market-specific product requirements
    • GP-110 Esquema Nacional de Seguridad
  • Records
  • Legit.Health Plus Version 1.1.0.0
  • Legit.Health Plus Version 1.1.0.1
  • Legit.Health Utilities
  • Licenses and accreditations
  • Applicable Standards and Regulations
  • Pricing
  • Public tenders
  • Procedures
  • GP-018 Infrastructure and facilities
  • Specific procedures
  • SP-018-001 Remote infrastructure control access policy

SP-018-001 Remote infrastructure control access policy

Procedure flowchart​

Purpose​

This procedure defines the process for granting remote access to AWS resources that are accessed directly (e.g. EC2 instances), as opposed to resources managed through the AWS console.

Scope​

This procedure applies to all team members who require remote access to AWS resources.

Responsibilities​

JD-001​

  • To approve the granting of remote access permissions to team members.

JD-005​

  • To ensure that the process of granting access follows the methodology established in this procedure.

JD-007​

  • To perform the technical operations described in this procedure and record the corresponding evidence.

Inputs​

  • Team member's full name.
  • Team member's IP address.

Outputs​

  • An updated AWS security group granting remote access to the user.
  • The credentials generated for allowing remote access.

Development​

The process for granting remote access to an AWS resource must follow these steps:

  1. Request the team member's IP address and full name.

  2. Check whether an AWS security group already exists for the user. If not, create a new one. The security group name must be the user's full name converted to lowercase, with spaces replaced by hyphens and accents removed. For example, "Gerardo Fernández Moreno" becomes gerardo-fernandez-moreno.

  3. Configure the security group with at least the following inbound rule:

    PortIPDescription
    22XXX.XXX.XXX.XXX (user's IP)User's location

  4. Attach the security group to the target resource.

  5. Create a user account inside the resource, following the same naming convention as the security group.

  6. Configure authentication credentials:

    • If the resource accepts SSH connections: Generate a PEM key pair for the user (if one does not already exist) and add the public key to /home/{username}/.ssh/authorized_keys. See the AWS documentation for detailed instructions.
    • If the resource does not accept SSH connections: Create a user with a password and share the credentials with the team member through Passbolt.

Document signature meaning​

  • Author: JD-004 María Diez and/or JD-007 Gerardo Fernández
  • Review: JD-005 Mr. Alfonso Medela
  • Approval: JD-001 Ms. Andy Aguilar

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 Design & Development Manager, JD-004 Quality Manager & PRRC
  • Approver: JD-001 General Manager
ㅤ

Previous
Specific procedures
Next
SP-018-002 AWS console-managed resources procedure
  • Procedure flowchart
  • Purpose
  • Scope
  • Responsibilities
    • JD-001
    • JD-005
    • JD-007
  • Inputs
  • Outputs
  • Development
  • Document signature meaning
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.)