Senior-led delivery
Every Blenheim engagement is led by a senior consultant — no junior pipelines, no resold capacity. New Zealand clients deal directly with the operators doing the work.
New Zealand wine teams in Blenheim pick Basalt for compliance consulting because the work is scoped to their actual threat model, not a generic checklist. Compliance work that does not bury your engineering team — ISO 27001, SOC 2, Essential Eight and NIST CSF mapped to controls you actually run, not parallel paperwork.
The wine concentration around Blenheim sees POS skimming, e-commerce account takeover and shipment-fraud during peak season. Our compliance consulting work in Marlborough is scoped against this real threat profile, not a generic checklist.
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.
Basalt delivers compliance consulting to organisations across Blenheim and the wider Marlborough region (population ~32k). The wine sectors that anchor the region face a distinct threat profile — POS skimming, e-commerce account takeover and shipment-fraud during peak season — 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.
Every Blenheim engagement is led by a senior consultant — no junior pipelines, no resold capacity. New Zealand clients deal directly with the operators doing the work.
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.
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.
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.
Most Blenheim 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.
Both. Sensitive work — classified-adjacent environments, live incident response, OT walkthroughs — gets on-site time in Blenheim and the wider Marlborough region. Routine assessments and detection engineering run remote with a tight feedback loop.
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.
The wine sector concentration in Blenheim drives a different threat model than a generic New Zealand engagement — POS skimming, e-commerce account takeover and shipment-fraud during peak season. Our scoping reflects that, and so does the test library we bring to the work.
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.
Strategic cyber security consulting
Adversarial testing for LLMs and AI systems
CREST-aligned penetration testing
Source code review and SAST/DAST integration