Built for public sector
Basalt's Porirua practice has been working public sector threat profiles long enough to know which controls actually move the dial — and which line items quietly waste budget. We bring that pattern recognition in week one.
If your public sector business sits in Porirua, the threat profile is ransomware, identity-driven attacks and supply chain compromise. Basalt's zero trust architecture practice is built around exactly that. Zero trust architecture rolled out around your real systems — not a vendor demo. Identity-first segmentation, device posture, application-aware proxying and continuous verification, sequenced so engineering teams keep shipping.
The public sector concentration around Porirua sees ransomware, identity-driven attacks and supply chain compromise. Our zero trust architecture work in Wellington 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 zero trust architecture to organisations across Porirua and the wider Wellington region (population ~60k). The public sector sectors that anchor the region face a distinct threat profile — ransomware, identity-driven attacks and supply chain compromise — 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.
Basalt's Porirua practice has been working public sector threat profiles long enough to know which controls actually move the dial — and which line items quietly waste budget. We bring that pattern recognition in week one.
Findings ship with control references against NZ Privacy Act 2020 and NZISM and remediation guidance written for the team that has to action it. Your board, your auditor, and your on-call engineer all get something they can use.
Basalt doesn't resell tooling. New Zealand public sector clients get an independent read on what's working, what isn't, and what's costing more than it should — not a thinly-veiled sales pipeline.
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 Porirua 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 Porirua and the wider Wellington 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 public sector sector concentration in Porirua drives a different threat model than a generic New Zealand engagement — ransomware, identity-driven attacks and supply chain compromise. 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