Critical infrastructure resilience depends on how information moves
Critical infrastructure organisations rarely operate alone. Keeping essential services running depends on networks of contractors, technology providers, engineering specialists and government partners.
Across those relationships, sensitive information moves constantly. Maintenance teams need asset records. Engineers exchange technical drawings. Suppliers review project requirements. External specialists contribute to incident response plans.
This exchange is essential to operations. It also deserves greater attention in conversations about cyber resilience.
The Australian Signals Directorate’s (ASD) latest critical infrastructure factsheet highlights the risks created by increasingly interconnected systems, operational technology and supply chains. It urges organisations to adopt an “assumed breach” mindset, strengthen third-party risk management and prepare for disruption.
For infrastructure leaders, this raises a practical question: how well do you understand the information that moves beyond your organisation?
The information surrounding an asset matters
An infrastructure asset’s sensitivity extends to the documents that describe how it operates.
Engineering drawings can reveal system configurations. Maintenance records may identify weaknesses. Response plans can expose dependencies, escalation pathways and recovery procedures.
Individually, these documents serve legitimate business purposes. Together, they can build a detailed picture of an organisation’s operations.
Protecting that information requires visibility across its lifecycle: where it is held, who receives it, how it is used and whether access remains appropriate as circumstances change.
A document shared for a short engagement may remain accessible long after the work finishes. A supplier’s personnel may change without the operator being notified. Copies may accumulate across inboxes, shared drives and collaboration platforms.
These everyday situations deserve the same deliberate attention as the initial decision to share.
An assumed breach mindset changes the questions
ASD’s advice to assume a breach encourages organisations to examine the consequences of compromised systems or accounts, alongside their efforts to prevent an incident.
For external information sharing, that means looking closely at the scope of access.
If a contractor’s account were compromised, what could an attacker see? Would access be limited to the current engagement? Could the account download sensitive technical material? How quickly could the operator identify and remove that access?
The answers depend on decisions made well before an incident occurs.
Access should have a clear purpose and owner. Permissions should reflect the work being performed. Reviews should account for changes in roles, contracts and project stages.
These practices require coordination between operational teams, procurement, information management and cyber security. Each holds part of the picture; effective governance depends on bringing those perspectives together.
Supplier assurance needs to extend into everyday work
Assessing a supplier before an engagement is valuable. Understanding how information will be exchanged throughout that relationship is equally necessary.
Where will documents be shared? Who can invite additional participants? What happens when a subcontractor becomes involved? Who is responsible for closing access when the work ends?
Under operational pressure, people need a practical way to collaborate. If approved processes are difficult to use, workarounds become more likely.
Secure sharing therefore needs to fit the way teams deliver services. Clear responsibilities, usable tools and proportionate controls help make the approved approach a workable part of daily operations.
Visibility supports a more informed response
ASD identifies best practice event logging as another priority for critical infrastructure organisations.
When sensitive information is shared externally, activity records help establish what happened. Teams may need to understand which documents were accessed, whether files were downloaded and when permissions changed.
That evidence can support investigations and help determine the scope of a response. It can also reveal routine governance issues, such as access that has remained open unnecessarily.
Collecting records is only part of the task. Organisations also need to know who reviews them, how long they are retained and how they contribute to wider incident response processes.
Resilience planning must account for access to information
The factsheet calls on organisations to prepare for the capability to isolate and operate critical systems and networks for three months, and to prove they can restore vital assets while sustaining critical services.
Information access belongs in those discussions.
During a disruption, teams may urgently need approved procedures, asset documentation or recovery plans. External specialists may need to assist while normal communication channels are restricted.
Organisations should test how those exchanges would work, including dependencies on connectivity, identity services and cloud platforms. They also need suitable alternatives where normal access cannot be maintained.
A plan is more useful when the people expected to execute it have tested whether they can obtain the information they need.
A practical opportunity to strengthen resilience
ASD’s advice provides a timely reason to review how sensitive information moves across organisational boundaries.
Leaders can start with a single important supplier workflow: identify the information involved, follow where it goes, review who can access it and establish what evidence is available.
Platforms such as Objective Connect can support this work through controlled external collaboration, granular permissions and activity records. Their value depends on clear ownership, appropriate configuration and consistent operating practices.
For critical infrastructure organisations, confidence in information sharing comes from being able to explain why access exists, demonstrate how it is governed and respond when circumstances change.
The next resilience review should include a simple question: do we have the same confidence in how our sensitive information is shared as we do in the systems that hold it?