Australian government hosting certification and procurement
Match each government hosting service to its required assurance level, actual sites and certification evidence. Prepare a provider assessment pack and check the registration pause before committing to a bid or launch date.
Home Affairs says new registration and supplementary assessment registration have been paused since 3 November 2025 while the framework is reformed. The normal formal assessment averages three to six months. Use the current notice to decide what can start.
Reviewed
Inside this guide
4 steps · 4 templates
Who it applies to
Data centre and cloud providers supplying hosting directly to Australian Government customers, and government procurement and assurance teams. Assess the specific facility, enclave or service named in the procurement.
What you’ll produce
A signed service and tier decision, an assessment evidence pack or register verification, and a calendar for maintaining certification.
Verify the tier and exact certified scope before relying on a supplier’s claim. For a new or expanded scope, get confirmation from Home Affairs and agree the procurement conditions with the agency.
Confirm the applicable edition, sites, products or service boundary and the certification route. Budget for assessment, changes needed to pass, and maintaining certification.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
Australia Hosting Certification Framework kickoff brief
Business reason and required outcome [Contract, obligation or approval]
Scope and exclusions [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones [Date, source and owner]
Executive sponsor and authorized signer [Names]
Project lead and backup [Names]
First workstream Set the required tier and exact service scope · Agency risk owner + procurement lead + provider architect [Name and due date]
People, effort and external costs [Estimate, owner and contingency]
Evidence folder and reviewer access [Location, access owner and review date]
Decisions and blockers [Item, options, owner and decision date]
First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START
How this works in practice
Two questions to check scope
Which proposed data centre, enclave or cloud service will hold or process each part of the workload?
Can the agency match the supplier’s certification ID and tier to the service named in the final contract?
Worked scenario
A fictional agency plans to procure a cloud service with separate production and recovery locations. It verifies both against the proposed certification scope. A supplier offers a new recovery location, so the agency records a decision on that location before contract signature.
Check critical infrastructure obligations where the service or operator falls within scope.
FROM THE SOURCE
Cases and numbers
Home Affairs · timing and registration
3 to 6 monthsPublished average for the formal assessment stage
The normal assessment averages three to six months
That estimate is for formal assessment. The current notice pauses registration for prospective providers and supplementary assessments from 3 November 2025 until the reforms are complete.
What to check Separate readiness work from the registration, assessment and award dependencies in the schedule.
The register lists BNE2 under Certified Strategic Facility and ADL1 and SYD1 under Certified Strategic Enclave. Each listing refers to the named locations and scope.
What to check Match the tier, location and coverage with the proposed contract, including backup and recovery services.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Set the required tier and exact service scope
Who Agency risk owner + procurement lead + provider architectWhen At sourcing or before a provider submits an assessment scope
Record data sensitivity, required tier and the service, operating entity, sites, recovery arrangements and delivery subcontractors. Separate facilities and enclaves from cloud service scope. Resolve eligibility and the current registration status with the programme.
What to produce
HCF service and certification scope decisionDecision memo
Gather first
Agency data classification and risk decision
Provider service description
Site and recovery map
HCF framework and current reform notice
How to prepare it
List each workload and the sites and services that support it, including backup and recovery. Identify the contracting provider and subcontractors responsible for relevant work.
Record the government customer’s required tier, the reason for that tier and whether each service has supporting certification evidence. Confirm current registration status for any service that needs assessment.
Ask the agency risk and procurement owners to sign the required scope and record the decision on any missing evidence.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional scope row
The production service and recovery enclave are separate lines. The agency requests the certification scope for each before the tender conditions are finalised.
Fictional decision
The agency requires Strategic certification for the workload and records which proposed locations the bidder must verify.
Check before handing it over
The required tier and every location or service are tied to a written risk decision and named owner.
Give the approved scope to procurement and the provider’s certification lead.
Who Provider certification lead + legal + site and cloud operatorsWhen During readiness and before any assessment submission
Use the official readiness guide to map evidence for ownership, control, site boundaries, operations and supply chain. Complete the current assessment pack when provided and prepare for requests, workshops or inspection.
What to produce
HCF provider assessment evidence packSpreadsheet
Gather first
Signed proposed scope
Home Affairs readiness guide
Ownership and leadership records
Site and service evidence
Supply chain records
How to prepare it
Record each applicable evidence request, responsible person, document version and location. Mark which records cover the whole facility or only one enclave or cloud service.
Collect approved governance and operating evidence. Review any gaps with legal and operations and schedule a site walkthrough or demonstration where requested.
Prepare the current assessment pack when provided by Home Affairs. Track submitted versions, written requests, corrective actions and the evidence required to close each request.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional evidence row
The site owner submits the approved enclave plan and inspection evidence. The certification lead identifies the perimeter covered and confirms the evidence publication date.
Fictional follow-up
The assessor asks about a subcontractor. Procurement attaches the current contract record and the accountable owner signs the response.
Check before handing it over
An assessor can trace each applicable requirement to current, correctly scoped evidence or an assigned open action.
Send the reviewed pack through the authorised channel when registration and assessment proceed.
Verify certification before relying on it in procurement
Who Procurement + agency assurance + provider account ownerWhen Before award, renewal or a change to the proposed service
Request the applicable certification ID and verify the legal entity, tier and service scope against Home Affairs evidence. Compare the proposed contract and delivery map. Escalate unresolved differences and document any conditions on award.
What to produce
HCF procurement scope verificationSpreadsheet
Gather first
Agency tier and scope decision
Provider certification ID and certificate evidence
Official register
Final proposal and contract schedules
How to prepare it
Create one row per contracted site, enclave or service and list the provider, required tier and exact supplied scope. Record the certification ID and source where available.
Compare the supplier evidence and official register. Check that each required location, backup service and delivery party is covered. Record and resolve naming, scope and tier discrepancies with the provider and Home Affairs.
Record the date, evidence, reviewer, current disposition and any award or change conditions. Retain source records for renewal and service changes.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional scope difference
The provider supplies an ID for a listed production enclave. Procurement records separate evidence needed for the proposed recovery site before award.
Fictional verification row
The scope owner matches the service and certification evidence to the signed contract schedule and attaches the review date and supporting records.
Check before handing it over
Each requirement can be traced to the contracted service and equivalent certified scope or an explicit unresolved decision.
Send the approved verification to the procurement delegate and service owner.
Maintain the certification evidence and report changes
Who Provider compliance lead + change owner + authorised signatoryWhen During certification and before implementing a relevant change
Assign ownership for the annual declaration, biannual contract reporting and applicable relevant change notices. Use the deed and current instructions for actual submission dates, evidence and notification channels.
What to produce
HCF maintenance and change registerSpreadsheet
Gather first
Executed deed
Certification IDs and scope
Current reporting forms
Government contract inventory
Planned ownership, operating and service changes
How to prepare it
List the reporting obligations, covered services, signatories and due dates. Reconcile the annual declaration and biannual contract reports against the current deed and instructions.
Assess planned changes to ownership, personnel, subcontractors, property or service operations for applicable notice and approval requirements. Record the decision owner and deadline.
Save each submitted version, receipt, regulator response and applicable change decision. Close the entry once the service inventory and supporting documentation are updated.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional reporting row
The reporting owner reconciles government contracts to their certified scope before the next contract form is signed and submitted.
Fictional change row
A proposed operating change goes to the compliance lead, who checks the deed and records the notification decision and evidence before rollout.
Check before handing it over
Every reporting and change action has a named owner, the correct scope and evidence of completion or an open due date.
Share the register with compliance, procurement, service owners and the authorised signatory.