> 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/runtime-defense/incident-types/altered-binary.md).

# Altered binary

An altered binary incident indicates that a binary that during image scanning was found with different metadata than what is specified by its package was executed. This binary might have been maliciously replaced or altered.

## Investigation

The following incident shows that the process *python2.7* was launched, but it seems to be altered or corrupted.

<figure><img src="https://991698089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjkReOE2QgjHPl2bpbcR3%2Fuploads%2Fgit-blob-8228d28fb9c756897ca0f94f5fbffde46d80364f%2Faltered_binary_incident.png?alt=media" alt="altered binary incident"><figcaption></figcaption></figure>

Your investigation should focus on locating the source of the affected image.

If the image was pulled from a remote repository, you should confirm the image hash is as expected given the repository image metadata. You should make sure the image repository and the author are valid.

If the image was built locally, you must examine the build process. Inspect your supply chain to understand if any binary from signed sources (such as a package manager) is changed or modified throughout the build.

## Mitigation

A full mitigation strategy for this incident begins by resolving the issues that allowed to pull or build an image including an altered binary.

Ensure that compliance benchmarks are appropriately applied to the affected images and containers. Use [Trusted Images](/admin-guide/compliance/trusted-images.md), to avoid image pulls from untrusted sources.

For additional protection, Enable the *block* action in the applicable compliance check to take action when altered binaries are found in an image during a scan.

<figure><img src="https://991698089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjkReOE2QgjHPl2bpbcR3%2Fuploads%2Fgit-blob-78c2765bbc4dcb853bbfb9ba0d19d771caf5ffc9%2Faltered_binary_compliance_check.png?alt=media" alt="altered binary compliance check"><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.prismacloud.io/admin-guide/runtime-defense/incident-types/altered-binary.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.