> For the complete documentation index, see [llms.txt](https://help.cloudstoragesec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cloudstoragesec.com/console-overview/see-whats-infected/malware-history.md).
# Malware History
For users that want to get a visual understanding of how malware has been found over time, you can use the Malware History report to track historic malware findings.
Malware History Dashboard
You can expand a specific identity and view more information around how often it was found. At this time, this report pulls data from the last 30 days of enabling it and will show information from that point onwards.
Times a malware was found in history
We also leverage [Amazon Bedrock](/how-it-works/integrations/amazon-bedrock.md) to interpret the malware finding to provide a human-readable summary and description of the malware found. As a result, Amazon Bedrock must be enabled for this feature.
Amazon BedRock analysis of a Malware found
---
# 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://help.cloudstoragesec.com/console-overview/see-whats-infected/malware-history.md?ask=&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.
