> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/investigate-and-respond-to-threats/threat-intel-management/indicator-investigation/expire-an-indicator.md). # Expire an indicator Expire indicators from the CLI or UI in Cortex XSOAR 8.10 On-prem. Indicators can have the Expiration Status field set to **Active** or **Expired**. When indicators expire, they still exist in Cortex XSOAR, meaning they are still displayed and you can still search for them. You may want to expire an indicator to filter out less relevant alerts, allowing analysts to focus on active threats. Expiring IoCs that are no longer relevant helps ensure that security systems remain focused on current threats. You can set up expiration in the indicator type, integration feed, or in a script. For more information, see [Configure indicator expiration](/cortex-xsoar-8-on-prem/8.10/investigate-and-respond-to-threats/threat-intel-management/indicator-configuration/configure-indicator-expiration.md). When you manually expire an indicator, this overrides indicator extraction rules set in scripts, indicator types, and feeds. You can expire indicators using the following methods: * In the indicator layout by clicking **Expire indicator**. You need a TIM license to access the indicator layout. * Use the **`expireIndicators`** command to change the expiration status to **Expired** for one or more indicators. This command accepts a comma-separated list of indicator values and supports multiple indicator types. For example, you can set the expiration status for an IP address, domain, and file hash: `!expireIndicators value=1.1.1.1,safeurl.com,45356A9DB614ED7161A3B9192E2F318D0AB5AD10`. * Use the `!setIndicator` or for multiple indicators use the `!setIndicators` command to reset the indicators' expiration value. The value can also be set to **`Never`**, so that the indicators never expire. For example, **`!setIndicators indicatorsValues=watson.com expiration=Never`**. --- # 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/investigate-and-respond-to-threats/threat-intel-management/indicator-investigation/expire-an-indicator.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.