As an Organization Administrator, I need a functional overview of security risks with running legacy software in EAASI to understand what to upload and how to direct configuration efforts

[EG-tech]

Purpose
The precise security concerns regarding malware and exploitation of legacy software running in EAASI are not well or commonly understood among the user base. In order to set local policies, make configuration decisions in conjunction with my Configuration User team, and effectively advocate for EAASI usage and resources at my institution with IT support, leadership, etc., I need a functional overview of security risks associated running legacy software in EAASI's containerized architecture (particularly with running environments where live Internet access is enabled).

Gap Analysis
There is some generalization about the security concerns of accessing legacy malware in EAASI the FAQ section of the User Handbook, but no thorough break-down or documentation of EAASI architecture/containers vis-a-vis security risks.