Sudo banner validation

---
title: Sudo banner validation
description: Sudo banner validation flags missing sudo permissions on managed devices so you know when the DEX agent's capabilities are limited.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/digital-end-user-experience-dex/sudo-banner-validation.html
release: australia
product: Digital End-User Experience \(DEX\)
classification: digital-end-user-experience-dex
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [DEX advanced configuration, Configure, Digital End-User Experience, IT Operations Management]
---

# Sudo banner validation

Sudo banner validation flags missing sudo permissions on managed devices so you know when the DEX agent's capabilities are limited.

The DEX agent requires specific sudo permissions to perform actions such as restarting services \(`restart_service`\) or removing files \(`rm`\). The agent flags missing required permissions.

As a DEX administrator, you can control the sudo banner configuration for macOS. For example, if your organization does not use Jamf, add that command to the exclusion list. In this case, the banner does not appear on the device page for excluded commands.

**Note:** Updating the exclusion list doesn't change configured sudo permissions on the end-user device.

-   **[Configure sudo banner exclusion list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/digital-end-user-experience-dex/configure-sudo-banner-exclusion-list.md)**  
Add the appropriate commands to the sudo banner exclusion list so the system doesn't flag them.

**Parent Topic:**[DEX advanced configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/digital-end-user-experience-dex/dex-advanced-configuration.md)