UNA's public-facing digital infrastructure supports enrollment, student communications, and federal accessibility compliance. It is managed by Web Services, operating within IT, without a formal continuity framework, shared documentation repository, or automated failsafes for several critical functions.
This plan identifies the specific gaps, names the shared risks that span both teams, and proposes a practical mitigation framework. The goal is to open a structured conversation with IT before a gap becomes an incident.
Current operational ownership mapped below. Several Tier 1 systems involve both Web Services and IT — continuity is a shared concern, not a departmental one.
| Tier | System | Platform / Host | Operational Owner |
|---|---|---|---|
| Tier 1 | una.edu (main site) | Cascade CMS — Hannon Hill | Beacon + Web Services |
| Tier 1 | apps.una.edu | WordPress — American Cloud | Web Services |
| Tier 1 | SSL certs (una.edu) | — | CIO |
| Tier 1 | DNS (una.edu) | — | CIO / IT |
| Tier 1 | Banner API integration | IT-managed endpoint | ERP (endpoint) + Web Services (consumer) |
| Tier 1 | Slate integration | — | Enrollment Management |
| Tier 2 | WCAG compliance monitoring | — | Web Services |
| Tier 3 | Vendor / agency relationships | Beacon, Hannon Hill, American Cloud | Web Services |
SSL certificates for una.edu are generated manually by the CIO. No automated renewal, no advance alerting, no documented coverage procedure if the CIO is unavailable at renewal time. A missed renewal triggers browser security warnings across all UNA domains — a high-visibility failure at any point in the enrollment cycle.
Operational documentation for Web Services systems is actively being developed but remains incomplete. Architecture decisions, configurations, and procedural knowledge are not yet fully documented in an institutionally-accessible form. Credentials are managed in 1Password with a shared vault and shared email, ensuring system access is not tied to any single team member — though the structure has not been formally aligned with an IT-wide credential standard.
Several Tier 1 systems have split ownership within IT — Web Services manages the consumer side, while the Banner API endpoint is maintained by a separate IT function — with no documented protocol for what happens when either side is unavailable. The Banner API endpoint is IT-managed; Web Services consumes it. If the endpoint changes or fails, there is no established escalation path or named point of contact.