Field notes on resilient infrastructure.
Practical perspectives on infrastructure, operations and the technology decisions that shape reliable, supportable environments.
A cyber baseline should follow the environment it protects
A single cyber checklist can miss the different risks carried by enterprise IT, cloud and operational technology. Effective security starts by scoping the environment, then applying and proving controls where they matter.
Read article→
Third-party access needs technical boundaries, not just contracts
Supplier and support access can become a persistent privileged pathway unless it is constrained, attributable and independently visible. Contracts define the relationship, but technical controls determine what can actually happen.
Read article→
Network segmentation decays unless you test the boundaries
Separate network zones can become connected by inherited firewall rules, vendor access and shared management systems. Segmentation needs maintained policies, understood dependencies and evidence that its boundaries still work.
Read article→
Emergency patching is an architecture requirement
Urgent security patching is not simply maintenance. Infrastructure must be designed and operated so high-risk changes can be made promptly, with understood dependencies, reliable recovery options and appropriate oversight.
Read article→
Outage communication needs its own operating plan
Technical recovery and stakeholder communication need to work in parallel during an outage. Clear ownership, verified updates and independent communication channels help organisations respond without distracting the people restoring the service.
Read article→
AI needs infrastructure evidence before autonomy
AI can accelerate infrastructure and security operations, but reliable recommendations depend on the asset, identity, monitoring and configuration evidence available underneath them.
Read article→
End-of-support dates are infrastructure deadlines
End-of-support dates are not just calendar reminders. Safe replacement depends on understanding business services, hidden dependencies and the evidence required to retire ageing platforms.
Read article→
Recovery readiness starts with a complete restore
A successful backup job does not prove that a business service can be restored. Recovery readiness depends on restoring data, applications, settings and dependencies to a usable state, then proving the result through testing.
Read article→
Isolating vital systems needs an operational plan
Network isolation can preserve critical operations during a disruption, but only when dependencies, authority, access and recovery steps have been designed and tested in advance.
Read article→
Cloud-first still needs operational ownership
Moving workloads to cloud platforms does not remove operational responsibility. This guidance explains the ownership, portability, cost, monitoring and recovery decisions that keep cloud services supportable over time.
Read article→
Internet-facing network devices need operational ownership
Routers, firewalls and VPN gateways are not set-and-forget appliances. This guidance explains the operating disciplines that keep edge devices supportable, observable and less exposed over time.
Read article→The dependency test: what would stop your business first?
When every system is labelled critical, resilience work becomes difficult to prioritise. A simple dependency test can expose where one failure is most likely to interrupt the business first.
Read article→Have an environment you need to talk through?
Independent, practical guidance for Brisbane, Gold Coast and South East Queensland organisations.
Discuss Your Environment