Canberra, Australia

Code Security Audit in Canberra.

Code Security Audit for Australian organisations operating in and around Canberra. Manual and tooled code review across your highest-risk repos — secrets, auth, injection, deserialisation and supply-chain risk, with CI integration that keeps findings from coming back.

85% of findings ship with a working patch suggestion — across Basalt operations in the past 12 months.

Threats facing Canberra government.

The government, defence concentration around Canberra sees state-aligned intrusion sets, supply chain compromise and credential phishing targeting cleared staff. Our code security audit work in ACT is scoped against this real threat profile, not a generic checklist.

Common pains

  • Tools that report thousands of low-quality findings
  • No clear ownership for fixing vulnerabilities in code
  • Supply-chain risk in third-party dependencies

How we engage.

  • Manual review of high-risk code paths
  • SAST + SCA integrated into CI with quality gates
  • Threat model per service or repository
  • Developer-grade fix guidance with sample patches

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.

Basalt delivers code security audit to organisations across Canberra and the wider ACT region (population ~470k). The government, defence sectors that anchor the region face a distinct threat profile — state-aligned intrusion sets, supply chain compromise and credential phishing targeting cleared staff — 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.

Why Basalt for code security audit in Canberra.

Senior-led delivery

Every Canberra engagement is led by a senior consultant — no junior pipelines, no resold capacity. Australian clients deal directly with the operators doing the work.

Mapped to Australia context

Findings and roadmaps reference the regulatory environment your business actually operates in — ASD Essential Eight and SOCI Act. Board-level reporting follows the APRA CPS 234 expectation set, so what we deliver lands without translation.

On the frontier

We actively research and test agentic AI tool-abuse and indirect prompt injection at scale, MCP server and AI-tool supply chain compromise and post-quantum cryptographic readiness (NIST PQC migration) — attack paths most regional providers still haven't mapped. Forward-thinking cyber defence, not last year's playbook.

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.

Frequently asked questions.

How fast can Basalt start a code security audit engagement in Canberra?

Most Canberra 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 code security audit on-site in Canberra or remote?

Both. Sensitive work — classified-adjacent environments, live incident response, OT walkthroughs — gets on-site time in Canberra and the wider ACT 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 code security audit in Canberra different from a generic engagement?

The government sector concentration in Canberra drives a different threat model than a generic Australian engagement — state-aligned intrusion sets, supply chain compromise and credential phishing targeting cleared staff. 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.

Other operations in Canberra.

Cyber Security Consulting in Canberra

Strategic cyber security consulting

Explore →

AI Red Teaming in Canberra

Adversarial testing for LLMs and AI systems

Explore →

Penetration Testing in Canberra

CREST-aligned penetration testing

Explore →

Identity Threat Detection & Response in Canberra

ITDR for identity-driven attacks

Explore →

Code Security Audit in other Australia cities.

Worth a conversation?Even if Basalt isn't the right partner, the call leaves you with a clearer read on what code security audit should look like for a government team in Australia.

Book the call