How Wiz Uses Service Ownership to Make Security Findings Actionable
Summary
Wiz describes using its Service Catalog to group cloud risks by service, assign owners, and automate routing and remediation—reducing duplicate findings and helping security and engineering teams coordinate.
Key points
- Wiz synced existing service ownership mappings from code repositories into its Service Catalog using an internal tool and the Wiz API.
- The team improved inconsistent tagging, clarified service ownership separately from alert recipients, and automated updates.
- Service tags help route security issues to dedicated Slack channels and connect them with owners and on-call assignments.
- Service Issues consolidate related risks across environments and deployments into a single remediation object, reducing duplicate alerts and focusing teams on root causes.
- Wiz plans to add service and service-issue context to Wiz Workflows and strengthen reminder and escalation processes.
- The article recommends making reliable service tagging, clear ownership, and automation foundational to using a service catalog for security.
Article Details
- Topic
- Using service ownership and Wiz Service Catalog to organize security findings, route issues to responsible teams, and improve remediation.
People
Vendors
Products
SlackWe also used the same internal concepts for engineering operational alerts to create dedicated Slack channels for security issues. Service tags are attached to services so automation rules could route issues to theWiz Service CatalogThat is what made Service Catalog so compelling for our team here at Wiz.Wiz Workflowsservices for security use cases, for example we’ll be releasing services and service issue context to Wiz Workflows this month to make it easier to orchestrate responses and remediation.