Remediation Actions
Trigger remediation actions for risky findings directly from dashboards and query details.
Overview
Remediation actions enable you to take immediate action on risky findings identified by Veza queries and dashboards. When a query or dashboard includes findings with a risk level, you can create tickets or send messages through integrated systems to initiate remediation workflows.
Veza integrates with Jira, ServiceNow, and Slack so you can create tickets or post messages for findings that need attention.
When to use remediation
Use remediation when you need to act on specific findings. For example, after reviewing a dashboard and spotting a risk that needs attention. Common scenarios include:
Escalating critical findings: A dashboard shows service accounts with excessive permissions. Click Remediate to create a Jira ticket assigned to the team responsible for that service.
Coordinating across teams: A query identifies users with stale access to a sensitive database. Share the finding via Slack so the responsible team can investigate.
Creating an audit trail: A compliance review reveals misconfigured storage buckets. Create a ServiceNow incident to document the finding and track remediation through your ITSM workflow.
Remediation creates a one-time ticket or message for a specific finding. For ongoing monitoring that triggers automatically when conditions change, use Rules and Alerts instead.
How it works
When you click Remediate on a dashboard or query, Veza opens a modal where you choose a channel and configure the notification:
Select a channel: Choose Jira, ServiceNow, or Slack from the Remediate dropdown.
Choose Veza Actions: Pick one or more configured Veza Actions as the delivery destination. Each selected action creates a separate ticket or message.
Add context: Optionally add notes, and (for Jira) assign a team member.
Preview and submit: Review the live preview of the ticket or message content, then click Create.
After submission, Veza polls the notification status and displays a toast notification confirming success or reporting any errors.
Each remediation notification includes a title (the query or dashboard name), a direct link to the source in Veza, and any notes you added. The message body uses a standard format that varies by channel. See the channel-specific guides below for details and examples.
Remediation notifications use a fixed message format. Unlike alert email templates, the body structure of remediation tickets and messages cannot be customized. You can control the title, notes, and delivery destination, but not the overall message layout.
Private queries and public dashboards: When a dashboard is made public, any private queries on the dashboard are automatically excluded. Users viewing a public dashboard will not see tiles for queries they do not have access to. There is no "not found" or empty state for those tiles. Dashboard-level remediation references the dashboard name and link, not individual query results. For dashboards shared across teams, queries that require integrations outside the recipient team's scope are also hidden from that team's view.
Remediation channels
Remediation supports three notification channels. See each guide for a full end-to-end walkthrough:
Jira
Jira ticket with finding details and link
Select Veza Action(s), assign team member, add notes
ServiceNow
ServiceNow incident with finding details and link
Select Veza Action(s), add notes
Slack
Message posted to configured Slack channel (not individuals)
Select Veza Action(s), add notes
Available channels depend on which Veza Actions are configured in Integrations > Veza Actions. If no actions are configured for a channel type, that option will not appear in the Remediate dropdown.
Prerequisites
Before using remediation actions, ensure:
At least one Veza Action is configured for a supported channel (Jira, ServiceNow, or Slack)
The query or dashboard includes findings with a risk level other than "None"
Your account has the required remediation permissions
Required permissions
Remediation requires both view and create permissions for the target type:
Query
assessment_query:remediate:view, assessment_query:remediate:create
Dashboard
assessment_reports:remediate:view, assessment_reports:remediate:create
If you do not see the Remediate button, contact your Veza administrator to verify your role includes these permissions.
The Remediate button only appears for queries and dashboards with risky findings. If no findings have a risk level, the button will not appear regardless of permissions.
Troubleshooting
Remediate button is not visible
Query or dashboard has no risky findings
The button only appears when at least one finding has a risk level other than "None". Add a risk level to the query or choose a different query.
Missing permissions
Your role must include assessment_query:remediate:view and assessment_query:remediate:create (for queries) or the equivalent assessment_reports permissions (for dashboards). Contact your Veza administrator.
No channels available in dropdown
No Veza Actions configured
Configure at least one Jira, ServiceNow, or Slack Veza Action in Integrations > Veza Actions.
Notification failed or errored
After submitting a remediation, Veza displays a toast notification with the result. Possible statuses:
Success
The ticket was created or the message was sent.
Failed
The target system rejected the request. Verify the Veza Action configuration and credentials.
Error
An unexpected error occurred. Check the Veza Action connection and retry.
If a notification fails, verify the Veza Action is still valid by testing it from Integrations > Veza Actions.
See also
Jira Veza Action (setup and example notifications)
ServiceNow Veza Action (setup and example notifications)
Slack Veza Action (setup and example messages)
Last updated
Was this helpful?