AI workloads and quantum risk: are Essential Eight controls keeping up?

TL;DR: AI systems and quantum computing are reshaping Australia’s security baseline, exposing gaps in visibility, patch discipline, privileged access, and cryptographic resilience while making the Essential Eight a practical framework for controlling dynamic workloads and legacy encryption dependencies, according to Forescout. The security problem is not AI or quantum alone, but governance that still assumes stable assets and durable cipher trust.

Editorial analysis by NHI Mgmt Group, based on content published by Forescout: “Securing AI & Quantum: The Essential Eight Way”.

Key questions

Q: How should security teams govern AI workloads across multiple cloud providers?

A: They should treat each AI workload as a governed identity with one owner, one approved purpose, and one revocation path.

Q: Why do overprivileged service accounts increase AI model risk?

A: Because AI systems often depend on non-human identities to reach data, tools and monitoring paths, overprivileged accounts can become a direct route to model theft, data exposure or workflow manipulation.

Q: What breaks when organisations assume today’s encryption will stay safe for years?

A: Long-term confidentiality breaks when organisations rely on algorithms and protocols that may be weakened before the data expires.

Practitioner guidance

• Establish continuous AI asset discovery Track GPU clusters, inference services, model endpoints, and experimental testbeds as governed assets the moment they appear on the network.
• Constrain execution on AI workloads Apply application control and runtime policy so only approved code, containers, and model-serving components can execute in AI environments.
• Review machine identity scope for AI services Map service accounts, tokens, and API credentials used by model pipelines and inference services, then remove unnecessary privilege and cross-environment reuse.

Bottom line: AI workloads create a governance problem because they are dynamic, opaque, and often tied to machine identities that outlive the runtime they serve.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →