Skip to content

Git Repository Import

  • Due to the compliance requirements, end-user code cannot be transferred into or out of the ReD Env without proper authorization
  • We leverage a static code analysis tool (CheckMarx One) to evaluate your code and ensure it is without vulnerabilities prior to being transferred into the production environment.

GitHub Setup Process

  • Are you using GitHub?

    • We can setup a webhook in your account to do the scanning.
    • We can setup a mirror of your repo into AWS CodeCommit that can be available in production.
    • Please send in a request ticket to regulated_data_environment@harvard.edu with the (1) Github account (2) Repository name

  • ReD Team will respond to request and you will need to allow ReD Team admin access to your GitHub repository to allow configuration of a webhook and GitHub Action

  • ReD Team will then configure the static code analysis tool as a webhook to your designated GitHub repository with GitHub Actions that will automatically start a new scan with each push/change to your repository
  • If the scanner identifies any vulnerabilities, you will be notified by email and you will have to review these vulnerabilities and remediate them before your code can be synced with AWS CodeCommit
    • You will be responsible for remediating any out of date packages by updating them to the latest version
    • If you are using open source code that can’t be modified or older versions of packages due to dependencies, you will need to have an exception approved by submitting an email to regulated_data_environment@harvard.edu.
    • The ReD Team is available at regulated_data_environment@harvard.edu to assist with any questions to the findings or remediation process
  • If the scanner results in no vulnerabilities, your code will automatically be synced to AWS CodeCommit for you to use within the ReD environment with standard Git commands
  • If you make changes to code within the ReD environment and want to sync it back to GitHub, you will need prior approval. There is no automated sync process from AWS CodeCommit to GitHub due to potential PII/PHI data concerns.
    • Your Data Manager/PI will need to review the code that you would like synced back to GitHub as part of the approval process.
    • The ReD Team will scan for PII/PHI, and make a copy available to you in the Sanitation zone.
    • Note: ReD Team is not be responsible for your PII/PHI data and cannot guarantee catching all cases

Warning: The manual review process does not guarantee a data breach will not occur. Please treat this process as you would for exporting results as in any other setting ensuring best practices are followed and data/code is treated securely.