Senior-led delivery
Every Greymouth engagement is led by a senior consultant — no junior pipelines, no resold capacity. New Zealand clients deal directly with the operators doing the work.
Greymouth, New Zealand
AI Red Teaming in Greymouth.
AI Red Teaming for New Zealand organisations operating in and around Greymouth. Adversarial testing for production LLM and AI systems — prompt injection, jailbreaks, training-data leakage, agentic tool abuse and model manipulation tested against your real deployments.
Over 200 distinct jailbreak techniques in our active library — across Basalt operations in the past 12 months.
THREAT VECTOR
Threats facing Greymouth mining.
The mining, fishing concentration around Greymouth sees OT/SCADA on remote sites, satellite-link interception and contractor identity sprawl. Our ai red teaming work in West Coast 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 NZ Privacy Act 2020 and NZISM, with GCSB / NCSC NZ guidance cited where it changes the remediation priority. Board reporting follows the CERT NZ Critical Controls expectation set.
LOCAL CONTEXT
Local context.
Basalt delivers ai red teaming to organisations across Greymouth and the wider West Coast region (population ~14k). The mining, fishing sectors that anchor the region face a distinct threat profile — OT/SCADA on remote sites, satellite-link interception and contractor identity sprawl — and our engagements are scoped to that, not a generic playbook. Reporting maps cleanly to the NZ Privacy Act 2020 and NZISM that New Zealand boards already use, with regulator context (GCSB / NCSC NZ) called out where it changes a remediation priority.
RATIONALE
Why Basalt for ai red teaming in Greymouth.
Mapped to New Zealand context
Findings and roadmaps reference the regulatory environment your business actually operates in — NZ Privacy Act 2020 and NZISM. Board-level reporting follows the CERT NZ Critical Controls 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.
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 New Zealand 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 Greymouth?
Most Greymouth engagements scope inside one week and start within two. Retainer clients can trigger work the same day. We do not pipeline New Zealand clients through junior teams — a senior consultant scopes and runs the work end-to-end.
Do you do ai red teaming on-site in Greymouth or remote?
Both. Sensitive work — classified-adjacent environments, live incident response, OT walkthroughs — gets on-site time in Greymouth and the wider West Coast region. Routine assessments and detection engineering run remote with a tight feedback loop.
How does Basalt map findings to New Zealand regulators?
Every finding ships with a control reference against the NZ Privacy Act 2020 and NZISM so your compliance team is not re-mapping our report. Where GCSB / NCSC NZ guidance exists for the specific finding, we cite it inline. Board-level reporting follows the CERT NZ Critical Controls expectation set.
What makes ai red teaming in Greymouth different from a generic engagement?
The mining sector concentration in Greymouth drives a different threat model than a generic New Zealand engagement — OT/SCADA on remote sites, satellite-link interception and contractor identity sprawl. 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 Greymouth.
Cyber Security Consulting in Greymouth
Strategic cyber security consulting
Penetration Testing in Greymouth
CREST-aligned penetration testing
Code Security Audit in Greymouth
Source code review and SAST/DAST integration
Identity Threat Detection & Response in Greymouth
ITDR for identity-driven attacks
OTHER DEPLOYMENTS
AI Red Teaming in other New Zealand cities.
AI Red Teaming in AucklandAI Red Teaming in WellingtonAI Red Teaming in ChristchurchAI Red Teaming in HamiltonAI Red Teaming in TaurangaAI Red Teaming in NapierAI Red Teaming in DunedinAI Red Teaming in Palmerston NorthAI Red Teaming in NelsonAI Red Teaming in RotoruaAI Red Teaming in New PlymouthAI Red Teaming in Whangarei