> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/configure/customize-terminal-output.md).

# Customize terminal output

Prisma Cloud lets you create rules that block access to resources or block the deployment of non-compliant containers.

For example, you might create a rule that blocks the deployment of any image that has critical severity vulnerabilities. By default, when you try to run non-compliant image, Prisma Cloud returns a terse response:

```
# docker -H :9998 --tls run -ti morello/docker-whale
docker: Error response from daemon: [Prisma Cloud] operation blocked by policy: (test-compliance), host has 19 compliance issues.
```

To help the operator better understand how to handle a blocked action, you can enhance Prisma Cloud’s default response by

* Appending a custom message to the default message. For example, you could tell operators where to go to open a ticket.
* Configuring Prisma Cloud to return an itemized list of compliance issues rather than just a summary. This way, the operator does not need to contact the security team to determine which issues are preventing deployment. They are explicitly listed in the response.

Enhanced terminal output is available for rules created under:

* **Defend > Vulnerabilities > Policy**
* **Defend > Compliance > Policy**
* **Defend > Access** (Kubernetes access control rules)

## Specify a Custom Message

You can create custom rules to audit your Kubernetes cluster and alert when a rule is violated. Refer to the [Kubernetes auditing](/admin-guide/audit/kubernetes-auditing.md) documentation.

## Output itemized list of compliance issues

You can configure vulnerability and compliance rules to return a detailed list of issues when Prisma Cloud blocks a deployment.

In this procedure, you create a vulnerability rule that prevents the deployment of any image that contains any type of vulnerable package.

Although this procedure is specific to vulnerability rules, the process for compliance rules is the same.

1. Open Console.
2. Create a new vulnerability rule (**Defend > Vulnerabilities > Policy**) or compliance rule (**Defend > Compliance > Policy**).
3. In the new rule dialog, enter the following information:
   1. Enter a rule name.
   2. Specify conditions that trigger a block action.

      For example, for the **Image contains vulnerable OS packages** condition in a vulnerability rule, set the **Action** to **Block** and set the **Severity** threshold to **Low**.
   3. Set **Terminal output verbosity for blocked requests** to **Detailed**.
   4. Click **Save**.
4. Test your setup by deploying an image with vulnerabilities.

   On a host protected by Prisma Cloud, run an image with vulnerabilities.

   ```console
   $ docker run --rm -it ubuntu:14.04 sh
   docker: Error response from daemon: [Prisma Cloud] Image operation blocked by policy: (sdf), has 44 vulnerabilities, [low:25 medium:19].
   Image          ID       CVE             Package   Version             Severity   Status
   =====          ==       ===             =======   =======             ========   ======
   ubuntu:14.04   4333f1   CVE-2017-2518   sqlite3   3.8.2-1ubuntu2.1    medium     deferred
   ubuntu:14.04   4333f1   CVE-2017-6512   perl      5.18.2-2ubuntu1.1   medium     needed
     .
     .
     .
   ```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/admin-guide/configure/customize-terminal-output.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.