> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/developer-machines/malicious-files/findings.md).

# Findings

The **Findings** page lists every file flagged by a malicious-file detection rule across your enrolled devices.

To open it, select **Malicious Files** > **Findings** in the **Developer Machines** section of the left navigation.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2F1CEnYcgvxDYjXsBiGQEQ%2FScreenshot%202026-10-27%20at%2016.23.07.png?alt=media&amp;token=2599e4d8-b26d-4a0c-ac3c-43cf0ff0a0f0" alt=""><figcaption></figcaption></figure>

Findings are grouped into three tabs: **New**, **Resolved**, and **Suppressed**. A finding moves to **Resolved** or **Suppressed** when you resolve or suppress it, when it matches a [suppression rule](https://docs.stepsecurity.io/developer-machines/malicious-files/suppression-rules.md), or when you deactivate the detection rule that flagged it.

For each flagged file, StepSecurity shows:

* **File:** the name of the flagged file, for example `.cursorrules` or `index.js`
* **Device:** the device where the file was detected, with the device's user and operating system
* **Campaigns:** the attack campaign the matching detection rule is associated with, for example `miasma`
* **Confidence:** how confident the detection rule is that the file is malicious, for example `High` or `Medium`. Open the finding to see the full condition breakdown behind the confidence level.
* **Status:** the current status of the finding, for example `Active` or `Suppressed`
* **Reason:** shown on the **Suppressed** tab only. The reason selected when the finding was suppressed, for example `False positive`, followed by the comment if one was added

#### Filters and export

* **All confidence:** filter by detection confidence
* **All campaigns:** filter by the attack campaign a detection rule is associated with

Select **Export CSV** to download the findings as a Comma-Separated Values (CSV) file.

You can also search across devices and extensions using the global search box at the top of the console.

The **New Threats** indicator in the top navigation bar reflects newly detected items across the console, including newly flagged malicious files.

### Finding details

Selecting a flagged file opens a side panel with the full detection record for that file.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2F9905M8RZdt5PDmSF5lN3%2FScreenshot%202026-10-27%20at%2016.45.47.png?alt=media&amp;token=8ae84e89-f841-48ef-80c7-804ff6ce912c" alt=""><figcaption></figcaption></figure>

The panel header shows the file path and the rule that flagged it, followed by chips summarizing the detection: confidence (for example, `High`), status (for example, `Active`), and the associated campaign.

The details block includes:

* **Path:** the full path of the flagged file on the device
* **SHA-256:** the SHA-256 hash of the file, for correlation and threat-intel lookups
* **Rule:** the identifier of the detection rule that matched
* **Matched glob:** the file-path pattern the rule used to select candidate files
* **First seen** / **Last seen:** when the file was first detected on the device and when it was most recently observed

#### **Condition breakdown**

Below the details block, the **Condition breakdown** shows why the file was flagged. For each campaign the rule evaluates, it displays:

* The campaign name and an overall match indicator (for example, `Full match`)
* A description of what the rule is checking for
* The individual conditions that make up the rule, each showing whether it is **Required** and how it was evaluated (for example, `regex · matched`)

A rule can require multiple conditions to match before a file is flagged. This breakdown lets you confirm exactly which indicators were present, which is useful both for validating a detection and for triaging a lower-confidence match.

### Remediation

When a file is flagged, identify the affected device from the **Device** column and investigate the file in place. Confirmed-malicious files should be removed from the device, and any credentials accessible from that machine should be treated as potentially exposed and rotated.&#x20;

After remediation, rescan the device and confirm the file is no longer flagged on the **Findings** page.

### Resolving and suppressing findings

Select the actions menu (**⋮**) at the end of a finding's row to act on it:

* **Resolve:** marks the finding as resolved and moves it to the **Resolved** tab. Confirm the action and optionally add a comment. Use this after you have removed the file from the device.
* **Suppress:** moves this finding to the **Suppressed** tab. Use this for a single file you have reviewed and do not need to act on.
* **Create suppression rule:** opens the suppression rule form with this finding's detection rule and file path already filled in as conditions. The scope defaults to **All devices**; select **Only this finding's device** to limit the rule to the device the finding came from. See Suppression Rules.
* **Deactivate rule for all devices:** deactivates the detection rule that flagged this finding. Devices across your organization stop scanning for the rule, and its current findings move to **Suppressed**. Select a reason and optionally add a comment to confirm. See Deactivating and activating a rule.

When you suppress a finding or deactivate a rule from this menu, select one of these reasons and optionally add a comment:

| Reason             | Meaning                                   |
| ------------------ | ----------------------------------------- |
| **False positive** | The file is not malicious                 |
| **Not applicable** | The file is not relevant                  |
| **Accepted risk**  | The risk has been reviewed and accepted   |
| **Used in tests**  | The file is not in production code        |
| **Will fix later** | The issue will be addressed in the future |

{% hint style="info" %}
Choose the narrowest action that fits. **Suppress** affects one finding, a suppression rule affects only the findings that match its conditions on the devices in its scope, and deactivating a detection rule turns it off for every device.
{% endhint %}

If the machine cloned a repository from your GitHub organization, check [Findings](https://docs.stepsecurity.io/github/malicious-files/findings.md) in Malicious Files for GitHub to see whether the same file is present in the repository's branches, pull requests or tags.


---

# 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.stepsecurity.io/developer-machines/malicious-files/findings.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.
