Decision-first scoping
Before a single test runs, we agree the decision the output will change — invest, divest, accept, fix. Dunedin engagements without a named decision-maker don't get past scoping. That discipline keeps work focused.
Dunedin, New Zealand
Penetration Testing in Dunedin.
Penetration Testing in Dunedin — built for the education sector that drives the region. CREST-aligned penetration testing for web apps, APIs, internal networks and cloud environments — findings ranked by exploitability, not just CVSS.
Median time-to-first-finding under 6 hours — across Basalt operations in the past 12 months.
THREAT VECTOR
Threats facing Dunedin education.
The education, biotech concentration around Dunedin sees ransomware targeting student records, OAuth abuse in Google Workspace and grant-fraud phishing. Our penetration testing work in Otago is scoped against this real threat profile, not a generic checklist.
Common pains
- Audit-driven testing that misses real attack chains
- Findings without business context or fix guidance
- Retesting that takes weeks to schedule
ENGAGEMENT
How we engage.
- Scoped engagement plan with rules of engagement
- Findings prioritised by exploitability and blast radius
- Executive summary suitable for the board and regulators
- Free retest of fixes within 90 days
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 penetration testing to organisations across Dunedin and the wider Otago region (population ~135k). The education, biotech sectors that anchor the region face a distinct threat profile — ransomware targeting student records, OAuth abuse in Google Workspace and grant-fraud phishing — 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 penetration testing in Dunedin.
Regulator-ready output
Every finding is tagged against NZ Privacy Act 2020 and NZISM controls with GCSB / NCSC NZ guidance cited where it shifts a remediation priority. Your compliance team stops re-mapping our reports.
Continuous, not one-shot
Penetration Testing doesn't end at the report. Basalt's Dunedin 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 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 penetration testing engagement in Dunedin?
Most Dunedin 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 penetration testing on-site in Dunedin or remote?
Both. Sensitive work — classified-adjacent environments, live incident response, OT walkthroughs — gets on-site time in Dunedin and the wider Otago 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 penetration testing in Dunedin different from a generic engagement?
The education sector concentration in Dunedin drives a different threat model than a generic New Zealand engagement — ransomware targeting student records, OAuth abuse in Google Workspace and grant-fraud phishing. 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 Dunedin.
Cyber Security Consulting in Dunedin
Strategic cyber security consulting
AI Red Teaming in Dunedin
Adversarial testing for LLMs and AI systems
Code Security Audit in Dunedin
Source code review and SAST/DAST integration
Identity Threat Detection & Response in Dunedin
ITDR for identity-driven attacks
OTHER DEPLOYMENTS
Penetration Testing in other New Zealand cities.
Penetration Testing in AucklandPenetration Testing in WellingtonPenetration Testing in ChristchurchPenetration Testing in HamiltonPenetration Testing in TaurangaPenetration Testing in NapierPenetration Testing in Palmerston NorthPenetration Testing in NelsonPenetration Testing in RotoruaPenetration Testing in New PlymouthPenetration Testing in WhangareiPenetration Testing in Invercargill