Navigating the High-Assurance Cloud for the Commonwealth
The Australian Federal Government is currently witnessing a significant migration trend: the move toward the ServiceNow Protected Platform (SPP). As a CMA, I am frequently asked why this is necessary and how to manage the transition. SPP isn't just a different URL; it is a high-assurance environment specifically engineered to meet the IRAP requirements at the PROTECTED level.
Why SPP? The Value Proposition
The SPP offers a "pre-hardened" environment. ServiceNow manages the underlying infrastructure, data centres, and personnel clearances (NV1) required to host sensitive government data. This allows agencies to "inherit" a large portion of their security controls, drastically reducing the time and cost required to achieve an ATO (Authority to Operate).
Architectural Challenges of a "Protected" Migration
Leading a team of CTAs through an SPP migration involves several strategic considerations:
- Data Sovereignty: We must ensure all data—including backups and logs—remains on Australian soil. SPP is purpose-built for this, but architects must still be careful with third-party integrations that might "leak" data to non-protected endpoints.
- "Out-of-the-Box" (OOTB) Rigour: In a Protected environment, every line of custom code is a potential vulnerability. The recommended approach is "Configuration over Customisation." By staying close to OOTB functionality, we ensure the instance remains performant, upgradable, and easier to re-accredit during annual security reviews.
- Secure Integration Patterns: One of the biggest hurdles is how a PROTECTED instance interacts with legacy, "Unclassified" systems. We architect these using secure MID Servers and Integration Hub spokes that utilise certificate-based authentication and encrypted payloads.
The Architect’s Role in Migration
Moving to SPP requires a shift in how we think about platform management. We discussed several "Success Pillars" with our CTA team:
- Sovereignty and Residency: SPP ensures that data remains on-shore and is managed by NV1-cleared personnel, fulfilling a core Commonwealth requirement.
- Standardization vs. Customization: To maintain the integrity of a Protected environment, architects must be ruthless about staying "Out-of-the-Box." High levels of customization increase the risk profile and complicate the ongoing security accreditation.
- Interoperability: How does a PROTECTED instance talk to a non-protected system? Designing secure integration patterns (using the Integration Hub and secure MID Servers) is a primary responsibility for today's CMA.
By moving to SPP, agencies are making a strategic investment. They are moving away from the burden of managing "technical debt" and security infrastructure, allowing their internal teams to focus on digital workflows that improve the lives of Australian citizens.
1 Comment
