Wiz, implemented and run by the people who fix what it finds
Wiz connects to your cloud accounts through their own APIs and, without installing anything on a workload, builds a graph of everything that runs there and how it connects: configuration, vulnerabilities, identities, exposure and data. Kode-1 is a Wiz partner in Australia and the APAC region. We assess with it, deploy it, tune it to your estate, and run the remediation program that turns its findings into a shorter list.
What Wiz does
Wiz is a cloud-native application protection platform, usually shortened to CNAPP. It reads your cloud through API connectors rather than agents, so a full picture of the estate arrives without a rollout, and it covers what agents miss: containers and Kubernetes, serverless, managed services and appliances, as well as virtual machines. Everything lands on one graph, where a misconfiguration, a vulnerability, an over-permissioned identity, an exposed endpoint and sensitive data appear as one attack path, ranked by whether an attacker could walk it. It covers posture, vulnerabilities, identity, data, containers, infrastructure code, compliance, runtime protection through a lightweight sensor, and the AI running in your cloud.
Where it earns its place
Wiz suits estates that look like these.
Several clouds, one question
Accounts and subscriptions across more than one provider, and a board that wants a single answer about exposure.
A backlog nobody can rank
Thousands of findings from posture and vulnerability tools, sorted by generic severity, with no way to say which matter.
Identity sprawl
Roles, service accounts and keys accumulated over years, most with far more reach than the workload needs.
Containers and Kubernetes at scale
Clusters and images that agent-based scanning never saw properly, rebuilt several times a day by the pipeline.
Fixes that belong to developers
Platform and product teams own the infrastructure code, and security findings need to reach them in their own tools.
Continuous compliance evidence
An auditor or regulator who expects controls evidenced on demand, not assembled into a spreadsheet each quarter.
What Kode-1 adds
Assess
- The Cloud Risk Assessment run on Wiz, connected read-only to your accounts, so the register is built from your estate rather than from interviews
- The graph read by people who have remediated cloud estates, so the priority list reflects your business and not only the platform's scoring
- A board-ready summary of exposure, in the shape the frameworks you answer to expect
Deploy
- Connectors across every account and provider, with projects and role-based views so each team sees its own estate
- Policy baselines tuned to your workloads, so the findings are signal rather than noise
- Integration with the ticketing, chat and security tooling your teams already live in
Operate
- A remediation program with owners and a weekly rhythm, started while the assessment is still running
- Ongoing tuning as the estate and the threats change, and guardrails in the pipeline so fixed things stay fixed
- Managed operation under agreed service levels if you would rather we ran it with you
License
- Licensing through Kode-1 or directly with the vendor, whichever suits your procurement
- Sizing against the estate you actually have, and right-sizing as it changes
- One accountable partner for the platform and the program, rather than a reseller and a consultancy who each point at the other
How we deploy it
Six steps, in this order.
- 01
Connect
Read-only connectors to every account, subscription and project, and the first full inventory.
- 02
Baseline
Policies fitted to your workloads and frameworks, and the initial findings triaged with the teams who own the resources.
- 03
Prioritise
The graph read for real attack paths, and a short list leadership can fund and teams can finish.
- 04
Route
Each finding sent to the owning team with the fix written for them, in the tools they already use.
- 05
Guardrail
Infrastructure code scanned before deployment, so the same misconfiguration cannot come back.
- 06
Report
Exposure and progress reported on a rhythm a board, an auditor or an insurer will accept as evidence.
Who it suits, and who it does not
Wiz suits an organisation with a real cloud footprint: several accounts, more than one team deploying, containers or Kubernetes in the mix, and a regulator, auditor or board asking for evidence. The larger and more varied the estate, the more the graph is worth. It is less compelling for a single small account running a handful of virtual machines, where the provider's native tooling and a disciplined review may be enough, and we will say so rather than sell a platform into a problem that does not need one. The same applies where the constraint is people rather than visibility: a platform that produces a better list does not fix a team with nobody to work it, which is why we pair the deployment with the remediation program rather than leaving you with a console.
A chosen partner, and still independent advice
Our solution pages name no vendor. The advice answers to your outcome, and the tooling test we publish applies to every platform, including this one. We chose Wiz because it passes that test, and because being close to the product sharpens what we can tell you about it. Where it is the right fit we will say so, deploy it, and stand behind the result. Where it is not, you will hear that first.
Wiz Cloud, Wiz Code and Wiz Defend
Each card names the problems that product answers, and links to the page on this site that describes the problem without naming a platform.
Wiz Cloud
The agentless core: inventory across every account and provider, and a graph that joins configuration, vulnerabilities, identities, exposure and data into attack paths.
- An estate across several clouds that no single console can enumerate
- Thousands of findings ranked by generic severity, with no way to say which fifty matter
- Identities and service accounts with far more reach than the workload needs
- Sensitive data in buckets, databases and snapshots that nobody has mapped to who can reach it
- Compliance evidence assembled by hand each quarter
Wiz Code
Security from the repository to the running cloud: code, infrastructure templates, container images and the pipelines that build them.
- Misconfigurations that reach production because nobody checked the infrastructure code before it was applied
- Secrets and credentials committed to repositories and baked into images
- A cloud finding with no owner, because nothing traced it back to the code and the team that produced it
- Developers who get security findings in a security tool rather than in the pull request
Wiz Defend
Detection and response for the cloud: runtime signals and cloud logs correlated on the same graph, so an alert arrives with the context an investigator needs.
- A security operations team that sees cloud alerts without knowing what the workload holds or can reach
- Runtime threats in containers and virtual machines that posture scanning alone cannot see
- Investigations that take days because the signal, the asset and the identity live in different tools
- Incident playbooks written for the data centre and never rehearsed against a cloud breach
Start with a conversation
Choose how you want to begin. A partner replies within one business day.
Before you enquire
No. It connects to your cloud accounts through their APIs and builds the inventory from there. A lightweight sensor is available for runtime protection on the workloads where you want it, and we deploy it selectively rather than everywhere.
The major public clouds, and the Kubernetes, container and serverless services running on them. If your estate spans more than one provider, that is where it is strongest. Tell us what you run and we will confirm coverage against it in the demo.
Either. Some organisations prefer one accountable partner for the platform and the program; others have procurement arrangements with the vendor already. We size the licence against your estate either way, and our advice on the platform does not change with where the invoice comes from.
Often, and not always. Provider tooling is good at its own platform and blind between platforms and between categories. If you run one provider with a small, stable estate, it may be enough, and we will tell you so. If you run several, or a large container estate, or need one view of risk that joins configuration, identity, exposure and data, this is the gap it fills.
Yes. Submit the RFI, RFP or RFQ through the form, we reply with where to send the documents, and we respond within the timeframe your process sets, with licensing, implementation and managed-service pricing in one proposal, a reference architecture for your estate, and answers written by the engineers who would do the work.
Yes. Managed operation covers tuning, triage, the remediation rhythm and reporting, under agreed service levels. You can start with the assessment and deployment, run the program with us, and decide later whether to keep it in-house or leave it with us.
The cloud security page describes the problem and the six things that have to be true, whatever tooling you choose. This page is about one platform we bring when it fits. Start there if you are still deciding whether the problem applies to you; start here if you are already evaluating this platform or have chosen it.