Secure colocation in Australia: what sits behind the security claims?
When every provider on your shortlist says its colocation service is secure, where do you start? Ask what the evidence covers. A current certificate may apply to a different site, an audit may exclude a system you rely on, and a well-controlled entrance tells you little about who can open your cabinet. The detail is what makes the claims useful.
We’ll work through the documents to request, the access arrangements to understand and the questions to take on a site visit. You can use the same approach across your shortlist, including our own colocation services, to build a view of the controls that will protect your equipment and the responsibilities that remain with your team.
How to verify data centre security claims
To verify data centre security claims, review the provider’s certifications and audit reports, confirm their scope and validity, and assess the physical security, access controls and personnel procedures protecting your infrastructure.
Know what each piece of evidence can tell you
Start by separating a provider’s claim from independent assurance. A certificate records conformity within a defined scope. An audit or assurance report gives more detail about the system, testing and findings, depending on the engagement. Neither should be read without checking which entities, services and locations it covers.
Two providers can display the same logo and offer very different scopes of assurance. Ask for the supporting documents relevant to your service, under a non-disclosure agreement where needed. If a full report cannot be shared, discuss a redacted version, a controlled review or other suitable evidence. Record what remains unverified rather than assuming that either a logo or a refusal settles the question.
Read the scope before the logo
Check the entity, scope and date first, then look at any findings and customer responsibilities. These details tell you whether the evidence relates to your deployment. Our compliance and certifications overview can help you identify which documents to ask MDC for.
• The named entity. Match the certified or assessed organisation to the service provider and the legal entity in your agreement. If the names differ, ask the provider to explain the relationship and how your service falls within scope.
• The scope statement. Check the sites, services and processes covered. An assessment of corporate systems does not automatically cover the controls protecting your racks or the systems managing your service.
• The dates. Check certificate validity and the reporting or assessment period. Ask about relevant changes since the report, follow-up work and any evidence needed to bridge the period to your evaluation.
• The findings and responsibilities. For SOC reports, review exceptions, management responses and controls your organisation is expected to operate. Judge findings by their relevance and treatment, rather than simply counting them.
Colocation security certifications and standards explained
These schemes answer different questions. Choose the evidence that matches the risks and obligations of your deployment, and check the scope of each document rather than treating a longer list as proof of a stronger service.
| Assurance scheme | What it actually covers | What it does not tell you |
| ISO 27001 | Certification of an information security management system within a defined scope | Your own compliance or every site and service. Check the certificate scope and relevant applicability evidence |
| SOC 1 | An assurance report on controls relevant to user entities’ internal control over financial reporting | General security posture. It is a financial controls report, not a security one |
| SOC 2 | An assurance report against the trust services criteria included in the engagement | Automatic coverage of every criterion or service. Check scope, exceptions and customer controls; Type II assesses operation over a period |
| PCI DSS | Controls protecting cardholder data, including physical security requirements | That your own environment is compliant. The provider’s compliance supports yours. It does not confer it. |
| Uptime Institute Tier | Infrastructure resilience, with different awards for design, constructed facilities and operations | The effectiveness of physical or information security controls |
| PSPF and SCEC zoning | Applicable government physical security requirements and zone certification/accreditation | Approval of every site or space. Check the exact scope and authority |
| Hosting Certification Framework | Provider and facility certification for hosting government data, with Certified Strategic the highest level | System-level accreditation. It certifies the hosting provider, not your system |
| IRAP assessment | A security assessment of systems, cloud services, gateways or GovLink at SECRET and below | System certification, authorisation or complete control compliance. Review scope and findings |
Uptime Institute Tier certification concerns infrastructure resilience. Check whether the award covers design documents, the constructed facility or operations. Tier III addresses concurrent maintainability; Tier IV adds fault tolerance. Those distinctions help assess availability, but they do not establish physical or information security.
IRAP assessments examine security controls within a stated system scope. They are not provider or system certification, and an assessment does not by itself establish that every tested control is met. Request the scope, date, relevant classification and findings, including exclusions and actions still open.
Follow the access path to your equipment
Assess physical security from the perimeter through to the cabinet. Ask what each control does, who monitors it and how an exception is handled. Strong controls need to work together along the whole access path.
At the building, check surveillance coverage, low-light capability, authenticated entry and delivery controls. At the hall or cage, establish whether the space is shared or dedicated, whether a private room with slab-to-slab walls is available if required, and how access is authorised. At the rack, ask who holds access rights, how cabinets are locked and what logging is available. Have the provider demonstrate the controls it can safely show during a visit.
For government-related deployments, have your security adviser specify the physical zone and approval evidence needed. Request the scope for the actual room or hall, including relevant PSPF and SCEC requirements. Do not assume an approval applies equally across every site or space a provider operates.
Ask who will work on your equipment
Cameras and access systems matter, but you also need to understand the people authorised to use them. Ask how routine maintenance, urgent work and temporary access are approved. That tells you how the written security policy will affect day-to-day operations.
Establish which staff are directly employed and which are subcontracted, then ask how both groups are vetted and supervised. Where clearances are required, confirm the level, issuing authority and process for maintaining assurance of current status. For other roles, ask what screening applies. Check how access is changed or revoked when someone moves roles or leaves.
Apply those questions to remote hands services too. The work happens on your equipment, sometimes while your team is off site. Agree who may request a task, how the request is authenticated, which actions need approval and what record you receive afterwards.
Use the site visit to test your understanding
A site visit can help you understand how the documented controls work, although it cannot prove their effectiveness over time. Walk the approved visitor route and discuss tailgating prevention, delivery handling and out-of-hours access. Ask for a sanitised access-log example and talk through how an unexpected request from someone claiming to represent your organisation would be handled.
Ask what the provider has learned from incidents or near misses it can discuss, and how corrective actions are checked. Then ask who can authorise an exception to the access policy and how that decision is recorded. A provider may have legitimate confidentiality limits; what matters is whether you can obtain enough relevant assurance to assess the process.
Colocation security evidence checklist
Use the checklist to track the evidence received and any follow-up needed. If you’re still comparing the broader service, our data centre selection questions cover capacity, resilience and operational support alongside security.
• Every certificate, with the named entity, scope statement, sites covered and expiry date
• The underlying audit report or statement of applicability, under non-disclosure if required
• All exceptions and qualifications noted by auditors, with management responses
• Applicable physical security zone and approval evidence for the proposed space, including authority and date
• IRAP assessment report, scope, date and classification level, described as assessed
• Uptime Institute Tier level, and whether it covers design, the constructed facility, or both
• Number of authenticated access points between the public street and your rack
• Surveillance coverage, retention period, and who can review footage
• Loading dock and delivery control procedures
• Cage, private room and slab-to-slab suite options, with per-cabinet access logging
• Whether on-site engineers are directly employed or subcontracted
• Clearance levels held, the issuing authority, and how currency is monitored
• Vetting standard applied to remote hands staff specifically
• Access revocation process and its timeframe when staff depart
• Identity verification process for out-of-hours access requests
• The most recent incident or near miss, and what changed as a result
• Who can authorise an exception to the access policy, with a recent documented example
The aim is to know how your equipment will be protected and where you still have work to do. Bring the findings into the service design, access procedures and contract, including the network connections and support arrangements your environment depends on. A security review earns its value when those responsibilities are understood before the racks arrive.
Looking for a data centre partner that can support your infrastructure today and as your requirements evolve? Macquarie Data Centres provides secure, resilient and scalable data centre solutions for hyperscale, enterprise, government and cloud environments.
Contact us to discuss your requirements, learn more about our team, or request a tour to see our facilities firsthand.
Frequently asked questions
How do I verify a data centre is actually secure?
Review the assurance documents for the proposed service, then examine physical access, personnel vetting, incident handling and customer responsibilities. Use a site visit to clarify how controls work in practice. Record any gaps and resolve material ones before committing.
What security certifications should a colocation provider have?
Choose according to the workload. ISO/IEC 27001 concerns information security management; SOC reports provide scoped assurance; PCI DSS applies where payment-card requirements are relevant. Government and Defence work may add hosting, physical security and DISP requirements. Confirm the applicable combination and scope with your security team.
Is a Tier IV data centre more secure than Tier III?
Tier certification addresses infrastructure resilience rather than security. Tier IV adds fault tolerance to the concurrent-maintainability requirements of Tier III, but physical and information security need their own assessment. Match the resilience level to your service needs.
Can a colocation provider be IRAP certified?
IRAP is an assessment program, not system certification. Request the relevant assessment report or assurance material, including scope, date, findings and exclusions. Your organisation still needs to assess the service against its own requirements.
What should I ask about data centre staff?
Ask whether on-site engineers are directly employed or subcontracted, which security clearances they hold and who issued them, how clearance currency is monitored, what background checking applies to uncleared staff, and how access is revoked when someone leaves. Apply every one of those questions to remote hands staff as well, since that is physical access to your equipment.
Should I be able to see a provider’s audit reports?
Ask what assurance material can be shared under appropriate confidentiality. Access may be limited by security, contractual or report-distribution conditions. A redacted report, controlled review or other independent evidence may help. Make sure any alternative answers the questions you need resolved.