Search16 Results

Describes the approved implementation pattern for using enterprise shared services to support workloads hosted within University-managed Azure environments.

Defines the minimum requirements for hosting HIPAA workloads in University-managed Azure environments.

Describes the approved implementation pattern for data protection, encryption, backup, recovery, retention, and data lifecycle management for workloads hosted within University-managed Azure environments.

Describes the approved implementation pattern for workload resiliency, operational continuity, backup, recovery, restoration, and service availability for workloads hosted within University-managed environments.

Describes the approved implementation pattern for monitoring, logging, alerting, and audit visibility for workloads hosted in University-managed environments.

Describes the approved implementation pattern for networking and connectivity for HIPAA workloads hosted in University-managed Azure environments.

Describes the approved implementation pattern for deploying and operating regulated workloads within University-managed Azure environments.

Describes the approved implementation pattern for authentication, authorization, privileged access, workload identities, identity governance, lifecycle management, and identity auditability across University-managed technology environments.

Defines requirements for the creation, classification, governance, ownership, operation, and lifecycle management of subscriptions within University-managed Azure environments. Azure subscriptions provide administrative, operational, financial, governance, and accountability boundaries and serve as the primary workload-isolation boundary when required by workload classification, risk, or approved architecture decisions.

Defines the requirements for protecting University data throughout its lifecycle, including classification, access protection, encryption, monitoring, retention, recovery, disposal, and governance.

The University of Arkansas will use subscription-level isolation as the primary boundary for regulated workloads hosted in Azure.

Workloads requiring HIPAA controls will be deployed into dedicated subscriptions governed through approved standards, architecture patterns, and policy assignments rather than sharing a common multi-tenant regulated environment.

The University of Arkansas will permit approved shared platform services to support HIPAA workloads when those services do not process, store, or expose protected health information (PHI).

Shared services may be consumed by regulated workloads when they satisfy approved security, governance, and operational requirements.

The University of Arkansas will use Azure Management Groups as the primary governance boundary for cloud environments.

Security, compliance, operational, and platform controls will be applied through Management Group inheritance rather than direct configuration of individual subscriptions whenever practical.

The University of Arkansas will use centralized enterprise identity services as the authoritative identity provider for Regulated data workloads hosted in Azure.

Authentication, authorization, privileged access, and workload identities will be managed through approved enterprise identity services and implemented through standardized identity patterns.

The University of Arkansas will use Azure Commercial as the hosting environment for regulated workloads, including HIPAA workloads, when required security, governance, and compliance controls can be implemented using approved architecture patterns and standards.

Azure Government will not be the default hosting environment. Exceptions may be evaluated when regulatory, contractual, or institutional requirements explicitly require a government cloud environment.