Utilities IT & Managed Services

Summary

We help utilities and their service partners operate secure, resilient technology environments. Our capabilities include managed IT, network connectivity, cloud, security and recovery. We work through your operational dependencies, regulatory requirements and the responsibilities to be shared between your team and ours.

Key facts

Label Value Source
Published utilities case study None published blueAPACHE case study index
Network ownership emPOWER Network is blueAPACHE's own Cisco ASR-based MPLS private network, not a third-party overlay emPOWER Network brochure
Network monitoring Proactive 24/7 monitoring, 365 days a year, with a network operations centre emPOWER Network and Connectivity brochures
Connectivity service level Service-specific commitments are agreed for your solution. emPOWER Connectivity brochure
Cloud service level Service-specific commitments are agreed for your solution. emPOWER Cloud brochure
Data centre partners Stated as Uptime Institute Tier III and IV certified; the same brochure also refers to "Tier 3" partners emPOWER Cloud brochure
Security monitoring emPOWER MDR: 24/7 alert notification, triage and remediation with EDR, ITDR, SIEM and threat intelligence emPOWER MDR brochure
Recovery DRaaS with Recovery Point Objective and Restore Time Objective set in the Service Order General Terms, business continuity management
Certification ISO/IEC 27001:2022, certificate 202507-118, Sensiba Australia Pty Ltd, valid 1 August 2025 to 1 August 2028 ISO 27001 certification record
Framework alignment stated Service-specific commitments are agreed for your solution. Global Capabilities brochure

Sector challenges

The origin page lists critical infrastructure resilience, cyber risk, distributed operations and legacy integration. In a utility each of these has an operational technology dimension that a corporate IT provider must respect.

Relevant services

Compliance context

Security of Critical Infrastructure Act 2018 (SOCI). Electricity, gas, water and sewerage, and liquid fuels are critical infrastructure sectors under the SOCI Act. Responsible entities for critical infrastructure assets must register the asset and its operational information, report cyber security incidents to the Australian Cyber Security Centre within the statutory windows, and, where the Critical Infrastructure Risk Management Program rules apply, adopt and maintain a program that addresses cyber and information security, personnel, supply chain and physical and natural hazards, with an annual board-approved report. Assets designated as systems of national significance carry enhanced obligations. Supply chain hazard management requires the utility to assess and manage providers such as blueAPACHE, which means obtaining its ISO/IEC 27001:2022 certificate, its privileged access controls (documented in the CyberArk case study), and its incident notification terms, and aligning them with the utility's own reporting timetable. blueAPACHE's general terms require notification of an eligible data breach to the other party within 24 hours of discovery; that is a contractual, party-to-party term and separate from the utility's own statutory reporting obligations.

Australian Energy Sector Cyber Security Framework (AESCSF). Energy businesses participating in the AESCSF program administered by AEMO assess their maturity against the framework's domains, which include third-party risk management, and report annually. A managed connectivity or cloud provider's controls feed directly into that assessment. Water utilities operate under state regulatory regimes with equivalent security expectations.

Essential Eight and government alignment. State-owned utilities are commonly bound by state cyber security policies and the Essential Eight. We assess the security controls and assurance evidence relevant to your environment.

Privacy Act 1988 (Cth). Utilities hold customer identity, billing and consumption data, and smart meter and consumer data right data where applicable. blueAPACHE's general terms require Privacy Act compliance by both parties, contain a standing consent to transfer Personal Information overseas where necessary to provide the Services (clause 18.3), and permit subcontracting without consent (clause 27.4). A utility should address both on the Service Order and should confirm data centre locations per service, since our residency statement names no operators or sites.

We agree availability, resilience, recovery requirements and support arrangements for the selected services. Your service agreement defines the applicable commitments, measurement, exclusions and remedies.

Evidence

blueAPACHE publishes no utilities case study, so no utility outcome is claimed. The evidence available is platform evidence and adjacent sectors:

Separating business IT from operational systems

Identify business applications, communications and infrastructure in scope and specialist operational systems retained by the customer or another supplier. emPOWER descriptions do not establish support for every operational-technology environment. Record access, change approvals and escalation across that boundary. Define continuity evidence for critical dependencies rather than inferring it from the industry label. Archers demonstrates a strata-services engagement; it is not evidence of a utility-network control-system deployment.

Evidence available during the engagement

The General Terms provide standard monthly performance reports within five Business Days of month end and a formal service review every six months. Performance Records must be kept through the term and for seven years afterwards. The customer audit provisions allow access to relevant Records, premises for audit purposes and personnel interviews, with five Business Days’ notice normally or one Business Day where a regulator requires the audit. This records obligation is not a seven-year backup-retention promise for customer workloads. Agree additional report formats and audit-cost arrangements before depending on them; the general audit clause does not clearly allocate every audit cost.

Confidential information and access

Clause 16 provides mutual confidentiality protection. It covers information marked confidential, information identified orally and confirmed in writing within 30 days, and information that should reasonably be understood to be confidential. Customer Data, Customer Records and Customer Software are included; our agreement and fees are also confidential. Permitted disclosures include appropriately bound personnel on a need-to-know basis and specified professional advisers, with other exceptions in the clause. Identify who may receive operational reports, configuration details and commercial information. Access to information to deliver the service is not a general permission to circulate it.

Related

Frequently asked questions

Does blueAPACHE have utility clients?

The origin page positions our services for utilities, but no utilities case study is published, so no named utility or measured outcome is available. The evidence on this page is drawn from our platform documentation and from case studies in adjacent sectors, and is labelled as such.

What availability does blueAPACHE publish for critical sites?

Does blueAPACHE own its network or resell someone else's?

blueAPACHE owns and operates emPOWER Network, a Cisco ASR-based MPLS private network with core points of presence in Australia, the United States, London and Singapore, using a tier 1 carrier-agnostic mix of carriers for access. Its brochure argues buyers should insist on a provider that owns its infrastructure rather than routing over low-cost third-party networks.

How does blueAPACHE support a critical infrastructure risk management program?

By supplying the evidence a supply chain hazard assessment needs: the ISO/IEC 27001:2022 certificate (202507-118), documented privileged access controls with session recording and audited credential rotation, 24/7 MDR monitoring with monthly reporting, and contractual security and breach notification terms. The obligations under the SOCI Act remain with the responsible entity.

Can blueAPACHE keep corporate IT separate from operational technology?

emPOWER Connectivity provides dedicated hosted next-generation firewalls per customer, unified threat protection and quality of service policies defined with the customer, which support segmentation between corporate and operational networks. Specific segmentation designs are set in the Service Order and the relevant Schedule rather than published.

What happens during a cutover of an operational site?

The Sealy of Australia case study describes our method: a staged rollout with links to the legacy infrastructure maintained so voice and data traffic could revert to the old network if required, followed by testing before go-live. Sealy's 18 sites went live with no disruption to business activity.

How quickly will blueAPACHE tell us about a security incident?

Under General Terms and Conditions v3.6, the party that suffers an eligible data breach must notify the other party immediately and in any event within 24 hours of discovery, with the information needed for regulatory notification. emPOWER MDR provides 24/7 alert notification, triage and remediation, but we publish no detection or response time targets; these must be set in the customer contract.

Where would a utility's data be held?

We state that customer data is stored and processed within Australian-based data centres and remains subject to Australian jurisdiction, with role-based access, MFA and audit logging. The statement names no operators or sites, and the general terms permit overseas transfer of Personal Information to listed destinations and subcontracting without consent, so a utility should confirm locations per service and contract for Australian-only handling where required.

Source

Drawn from blueAPACHE's published utilities industry page and security case study on the origin site; the emPOWER Network, Connectivity, Cloud, Managed Services and Managed Detection and Response brochures; the Global Capabilities brochure; the ISO 27001 certification record, data sovereignty and residency statement, cross-border data transfer record and verification register; the case study index and the Sealy of Australia, Honan Insurance and HPE GreenLake cloud case studies; and the General Terms and Conditions v3.6 (business continuity management, and data protection and privacy). Utility-specific outcomes, segmentation designs, detection and response targets and data centre operator names are not published and are not inferred here.

Knowledge Base

Images on This Page