Built for energy
Basalt's Brisbane practice has been working energy threat profiles long enough to know which controls actually move the dial — and which line items quietly waste budget. We bring that pattern recognition in week one.
Brisbane, Australia
Application Security in Brisbane.
Application security program build-out delivered for energy teams in Brisbane, Australia. Application security programs built around your engineering org — threat modelling, secure-by-default libraries, AppSec champions and CI/CD guardrails that ship.
3x throughput on security reviews after paved-road rollout — across Basalt operations in the past 12 months.
THREAT VECTOR
Threats facing Brisbane energy.
The energy, mining, tech concentration around Brisbane sees OT/ICS intrusion, ransomware against billing systems and ENISA-style intrusion sets. Our application security work in QLD is scoped against this real threat profile, not a generic checklist.
Common pains
- Security review as the engineering bottleneck
- No threat models for new services
- Pen tests as the only feedback loop
ENGAGEMENT
How we engage.
- AppSec program design with maturity model
- Threat modelling templates and training
- Paved-road secure defaults for your stack
- AppSec champions enablement curriculum
Reporting
Every finding ships with a control reference against ASD Essential Eight and SOCI Act, with ACSC guidance cited where it changes the remediation priority. Board reporting follows the APRA CPS 234 expectation set.
LOCAL CONTEXT
Local context.
Basalt delivers application security to organisations across Brisbane and the wider QLD region (population ~2.6M). The energy, mining, tech sectors that anchor the region face a distinct threat profile — OT/ICS intrusion, ransomware against billing systems and ENISA-style intrusion sets — and our engagements are scoped to that, not a generic playbook. Reporting maps cleanly to the ASD Essential Eight and SOCI Act that Australian boards already use, with regulator context (ACSC) called out where it changes a remediation priority.
RATIONALE
Why Basalt for application security in Brisbane.
Reporting that lands
Findings ship with control references against ASD Essential Eight and SOCI Act and remediation guidance written for the team that has to action it. Your board, your auditor, and your on-call engineer all get something they can use.
No vendor bias
Basalt doesn't resell tooling. Australian energy clients get an independent read on what's working, what isn't, and what's costing more than it should — not a thinly-veiled sales pipeline.
2026 THREAT LANDSCAPE
What we test for.
- Agentic AI tool-abuse and indirect prompt injection at scale
- MCP server and AI-tool supply chain compromise
- Post-quantum cryptographic readiness (NIST PQC migration)
- Identity-first attack chains across federated SaaS
- Open-source software supply chain (post-xz, post-tj-actions)
Cyber security in Australia can't be done with last year's threat models. The Basalt practice runs against current attacker tradecraft — agentic AI abuse, MCP and AI-tool supply chain, post-quantum readiness — alongside the legacy infrastructure work that still keeps most organisations awake at night.
FAQ
Frequently asked questions.
How fast can Basalt start a application security engagement in Brisbane?
Most Brisbane engagements scope inside one week and start within two. Retainer clients can trigger work the same day. We do not pipeline Australian clients through junior teams — a senior consultant scopes and runs the work end-to-end.
Do you do application security on-site in Brisbane or remote?
Both. Sensitive work — classified-adjacent environments, live incident response, OT walkthroughs — gets on-site time in Brisbane and the wider QLD region. Routine assessments and detection engineering run remote with a tight feedback loop.
How does Basalt map findings to Australian regulators?
Every finding ships with a control reference against the ASD Essential Eight and SOCI Act so your compliance team is not re-mapping our report. Where ACSC guidance exists for the specific finding, we cite it inline. Board-level reporting follows the APRA CPS 234 expectation set.
What makes application security in Brisbane different from a generic engagement?
The energy sector concentration in Brisbane drives a different threat model than a generic Australian engagement — OT/ICS intrusion, ransomware against billing systems and ENISA-style intrusion sets. Our scoping reflects that, and so does the test library we bring to the work.
Is Basalt set up for AI-era threats, not just legacy infrastructure?
Yes — this is core to how we work. Basalt actively researches and tests against agentic AI tool-abuse and indirect prompt injection at scale, MCP server and AI-tool supply chain compromise and identity-first attack chains across federated SaaS. Most regional providers haven't mapped these attack paths; we run them in production against client systems with explicit scope.
RELATED OPERATIONS
Other operations in Brisbane.
Cyber Security Consulting in Brisbane
Strategic cyber security consulting
AI Red Teaming in Brisbane
Adversarial testing for LLMs and AI systems
Penetration Testing in Brisbane
CREST-aligned penetration testing
Code Security Audit in Brisbane
Source code review and SAST/DAST integration
OTHER DEPLOYMENTS
Application Security in other Australia cities.
Application Security in SydneyApplication Security in MelbourneApplication Security in PerthApplication Security in AdelaideApplication Security in Gold CoastApplication Security in NewcastleApplication Security in CanberraApplication Security in WollongongApplication Security in HobartApplication Security in GeelongApplication Security in TownsvilleApplication Security in Cairns