Over 200 distinct jailbreak techniques in our active library — across Basalt operations in the past 12 months.
THREAT VECTOR
Threats facing Kelvin Grove Urban Village tech.
The tech, creative, research concentration around Kelvin Grove Urban Village sees CI/CD supply chain compromise, OAuth token theft and AI/LLM prompt injection at scale. Our ai red teaming work in QLD / Brisbane knowledge precinct is scoped against this real threat profile, not a generic checklist.
Common pains
- LLM features shipped without an attacker’s perspective
- No process for testing prompt injection or jailbreaks
- Agents wired to tools and data with no abuse modelling
ENGAGEMENT
How we engage.
- Adversarial test suite covering OWASP LLM Top 10
- Prompt injection and jailbreak findings with reproductions
- Tool-use and agent abuse path analysis
- Hardening recommendations and CI guardrails
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 ai red teaming to organisations across Kelvin Grove Urban Village and the wider QLD / Brisbane knowledge precinct region (population ~10k). The tech, creative, research sectors that anchor the region face a distinct threat profile — CI/CD supply chain compromise, OAuth token theft and AI/LLM prompt injection at scale — 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 ai red teaming in Kelvin Grove Urban Village.
Decision-first scoping
Before a single test runs, we agree the decision the output will change — invest, divest, accept, fix. Kelvin Grove Urban Village engagements without a named decision-maker don't get past scoping. That discipline keeps work focused.
Regulator-ready output
Every finding is tagged against ASD Essential Eight and SOCI Act controls with ACSC guidance cited where it shifts a remediation priority. Your compliance team stops re-mapping our reports.
Continuous, not one-shot
AI Red Teaming doesn't end at the report. Basalt's Kelvin Grove Urban Village clients run retainer reviews on a quarterly cadence so the security posture compounds rather than drifting back six months after the engagement.
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 ai red teaming engagement in Kelvin Grove Urban Village?
Most Kelvin Grove Urban Village 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 ai red teaming on-site in Kelvin Grove Urban Village or remote?
Both. Sensitive work — classified-adjacent environments, live incident response, OT walkthroughs — gets on-site time in Kelvin Grove Urban Village and the wider QLD / Brisbane knowledge precinct 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 ai red teaming in Kelvin Grove Urban Village different from a generic engagement?
The tech sector concentration in Kelvin Grove Urban Village drives a different threat model than a generic Australian engagement — CI/CD supply chain compromise, OAuth token theft and AI/LLM prompt injection at scale. 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 Kelvin Grove Urban Village.
Cyber Security Consulting in Kelvin Grove Urban Village
Strategic cyber security consulting
Explore →
Penetration Testing in Kelvin Grove Urban Village
CREST-aligned penetration testing
Explore →
Code Security Audit in Kelvin Grove Urban Village
Source code review and SAST/DAST integration
Explore →
Identity Threat Detection & Response in Kelvin Grove Urban Village
ITDR for identity-driven attacks
Explore →
OTHER DEPLOYMENTS
AI Red Teaming in other Australia cities.