Table: wiz_project - Query Wiz Projects using SQL
Wiz is a cloud security platform that identifies the most critical risks and enables quick remediation by using a new scanner-less approach. It scans the entire environment to build a graph-based inventory and then applies cloud-native analysis to prioritize risks. Wiz supports multi-cloud environments and provides a holistic view of risks across Azure, AWS, GCP, and Kubernetes.
Table Usage Guide
The wiz_project
table provides insights into Projects within the Wiz platform. As a Security Engineer, explore project-specific details through this table, including ID, name, and creation time. Utilize it to uncover information about projects, such as their unique identifiers and the time they were created, which can aid in managing and securing your cloud environment.
Examples
Basic info
Gain insights into your project's structure by understanding the distribution of business units, the number of repositories, cloud accounts, and Kubernetes clusters, along with their respective security scores. This is useful to assess the overall security posture and resource allocation within your project.
select name, business_unit, security_score as security_score_in_percentage, repository_count, cloud_account_count, kubernetes_cluster_countfrom wiz_project;
select name, business_unit, security_score as security_score_in_percentage, repository_count, cloud_account_count, kubernetes_cluster_countfrom wiz_project;
Get count of critical issues per project
This query helps identify the number of critical issues per project, providing a clear overview of project health and potential areas of concern. This can be beneficial in prioritizing resources and remediation efforts.
with critical_issues as ( select id, severity, p ->> 'id' as project from wiz_issue, jsonb_array_elements(projects) as p where severity = 'CRITICAL')select p.name as project, count(c.id)from wiz_project as p left join critical_issues as c on p.id = c.projectgroup by p.name;
with critical_issues as ( select id, severity, json_extract(p.value, '$.id') as project from wiz_issue, json_each(projects) as p where severity = 'CRITICAL')select p.name as project, count(c.id)from wiz_project as p left join critical_issues as c on p.id = c.projectgroup by p.name;
Get the owner details of each project
Explore which projects are owned by which users to better understand project responsibility distribution. This can assist in identifying the point of contact for each project, facilitating smoother communication and project management.
select p.name, p.slug, u.name as user_name, u.email as user_emailfrom wiz_project as p left join jsonb_array_elements(project_owners) as o on true left join wiz_user as u on u.id = o ->> 'id';
select p.name, p.slug, u.name as user_name, u.email as user_emailfrom wiz_project as p, json_each(p.project_owners) as o left join wiz_user as u on u.id = json_extract(o.value, '$.id');
List archived projects
Explore which projects have been archived, allowing you to assess elements like the associated business unit, security score, and linked resources such as repositories, cloud accounts, and Kubernetes clusters. This can be useful in understanding the scope and impact of archived projects within your organization.
select name, business_unit, security_score as security_score_in_percentage, repository_count, cloud_account_count, kubernetes_cluster_countfrom wiz_projectwhere archived;
select name, business_unit, security_score as security_score_in_percentage, repository_count, cloud_account_count, kubernetes_cluster_countfrom wiz_projectwhere archived = 1;
Schema for wiz_project
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form, e.g. connection_name. | |
archived | boolean | If true, the project was archived. | |
business_unit | text | The project business unit. | |
cloud_account_count | bigint | The count of cloud account associated with the project. | |
cloud_organization_count | bigint | The count of cloud organizations associated with the project. | |
description | text | A human-readable description of the project. | |
entity_count | bigint | The count of the entity. | |
id | text | = | A unique identifier of the project. |
identifiers | jsonb | A list of project identifiers. | |
kubernetes_cluster_count | bigint | The count of Kubernetes cluster created within the project. | |
name | text | The name of the project. | |
profile_completion | bigint | The profile completion percentage of the project. | |
project_owners | jsonb | A list of project owners. | |
repository_count | bigint | The count of the repository. | |
resource_tag_links | text | A list of resource tags. | |
risk_profile | text | Specifies the project risk-profile. | |
security_score | bigint | Security score is based on the number of successful assessments that ran on this project out of the total assessments. | |
slug | text | The project slug. | |
team_member_count | bigint | The count of the project team member. | |
technology_count | bigint | The count of the technology. | |
workload_count | bigint | The count of the workload. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- wiz
You can pass the configuration to the command with the --config
argument:
steampipe_export_wiz --config '<your_config>' wiz_project