{"resourceId":"utah-rai-redtail-faq-no-sensitive-data-allocation-only-access","versions":[{"version":"external-ecba71cc96628c69ba45225f1fc2e223ce842decc5f401620a8438a55ce3da15","resource":{"id":"utah-rai-redtail-faq-no-sensitive-data-allocation-only-access","title":"University of Utah Redtail FAQ: open system that does not currently support sensitive data, HIPAA or NIST 800-series controls; access only through challenge or allocation, six-month projects, no preemptible queue","organization":"University of Utah One-U Responsible AI Initiative","sector":"Higher education (research computing)","geography":"Utah, United States","publishedAt":"unknown (undated FAQ, retrieved 2026-10-08)","publicationDate":null,"eventDate":"2026-10-06","sourceName":"One-U Responsible AI Initiative","sourceLabel":"Operator program FAQ","sourceUrl":"https://rai.utah.edu/opportunities/redtail-challenge/redtail-faq/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["data-security","governance-procurement","operating-model"],"finding":"The program FAQ states Redtail 'is an open system and does not currently support sensitive data or compliance requirements, such as HIPAA or NIST 800-series controls', directing such projects to other CHPC resources. Access comes only through the challenge call or a regular allocation process beginning fall 2026; general open access is not contemplated and there is no preemptible queue. Selected projects get system and storage access for up to six months; longer storage carries a per-TB cost. CHPC is working on an inference-service blueprint for local model API access. The challenge offers no financial assistance.","sledRelevance":"Why now: at the Oct 6 launch, speakers promoted Redtail for clinical trial matching, cancer research and state government use. The operator's own terms say regulated and sensitive data are out of scope today. Agencies and health researchers elsewhere considering shared state AI factories should expect the same gap between launch messaging and data authorization.","evidence":"Opened and read the full FAQ page. Undated; content references the July 8 webinar and fall 2026 allocations. Operator documentation, not an audit.","architectureImplications":"Regulated workloads need a separate enclave or a different CHPC resource; inference API access depends on a blueprint still in development.","governanceImplications":"Allocation is proposal-based with six-month terms, so state agencies would compete with research projects and need a sponsor process.","securityPrivacyImplications":"No HIPAA or NIST 800-series support today means PHI or controlled unclassified data cannot be placed on Redtail as described.","caveats":"Undated FAQ written for the initial challenge call; terms may change as full operations begin in late fall 2026. Classified here as independent-reporting following the archive's treatment of the companion CHPC page, though it is the operator's own document.","streamIds":["nvidia"],"roles":{"sales":"The FAQ is the reality check on Redtail's launch messaging: no sensitive data, no HIPAA or NIST controls, access only by proposal. For state health and agency customers that changes the conversation from using the state AI factory to asking what it would take to add a compliant enclave. We can offer a data-classification and enclave-requirements assessment. We should not imply Redtail can host patient or regulated agency data today.","engineering":"Technically, Redtail as described is an open research system: proposal-based allocations, six-month terms, scratch storage and no preemptible queue. Fit is AI-ready research with non-sensitive data. Prerequisites for regulated use would be an enclave with HIPAA or NIST 800-series controls. Constraints are data class, term limits and an unfinished inference API. Proof of value: map each candidate workload's data class to Redtail's terms before proposing it.","delivery":"Delivery teams supporting agencies or health researchers need a data-classification gate before any Redtail proposal. CHPC owns access decisions; institutional data stewards own classification. Checkpoints are classification review, proposal submission and six-month renewal. Proposed acceptance: no regulated data placed on Redtail, and each project has a documented data class. Risk: users acting on launch-day messaging and moving sensitive data onto an open system."},"roleDetails":{"sales":{"customerProblem":"Agencies and health researchers may expect to use a state AI factory for regulated data that its current terms exclude.","stakeholders":["State health or agency data officers","Research compliance office","CHPC / research computing leadership","Privacy officer"],"discoveryQuestions":["What data class would your Redtail workload use?","Do you need HIPAA or NIST 800-series controls?","Can your project fit a six-month allocation?"],"valueHypothesis":"Clarifying data terms early can redirect regulated work to compliant resources and identify demand for a future enclave (interpretation).","potentialEngagement":"A data-classification and enclave-requirements assessment for workloads proposed for shared state AI compute.","unsupportedClaims":["Redtail can host PHI or regulated agency data today","Open, on-demand access","Free long-term storage"]},"engineering":{"fit":"Fits AI-ready research and education projects with non-sensitive data and defined six-month goals.","architectureIntegration":"Proposal-based allocation on an open HPC system with scratch storage; inference-service blueprint in development.","prerequisites":["Non-sensitive data","Approved challenge or allocation proposal","Plan for storage beyond six months"],"constraints":["No HIPAA or NIST 800-series support","No preemptible or guest queue","Six-month allocation terms","Inference API not yet available"],"security":"Treat Redtail as an open system; keep sensitive data on CHPC's protected environments.","proofOfValue":["Map candidate workloads to data class before proposing","Confirm storage and egress plan for project end"]},"delivery":{"work":"Add a data-classification gate and allocation-term planning to any Redtail project onboarding.","dependencies":["CHPC allocation process","Institutional data stewards","Protected-environment alternatives"],"ownership":"CHPC owns access; institutional data stewards own classification decisions.","skillsAdoption":"Researchers need guidance on data classes and allocation proposals.","governanceCheckpoints":["Data classification review","Proposal approval","Six-month renewal or close-out"],"acceptanceCriteria":["Every project has a documented data class (proposed)","No regulated data on Redtail (proposed)"],"risks":["Sensitive data placed on an open system","Projects stranded at six-month term end"]}},"retrievedAt":"2026-10-08T03:00:16Z","enrichedAt":"2026-10-08T03:09:35Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Undergraduates can join teams but not lead proposals; graduate students need a faculty mentor.","procurementImplications":"States planning shared AI factories should budget a compliant enclave from the start if agencies or health research are target users.","operatingModelImplications":"Allocation by proposal makes the operator a gatekeeper; agencies need a sponsor route into a research-oriented process.","sourceVerification":{"openedUrl":"https://rai.utah.edu/opportunities/redtail-challenge/redtail-faq/","referenceExcerpt":"Redtail is an open system and does not currently support sensitive data or compliance requirements, such as HIPAA or NIST 800-series controls.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}