---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# System properties for Webhooks

# System properties for Webhooks {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The system properties for webhooks are explained below.  
{#tisc-sysprops-retry__table_zp1_pbb_2cc__entry__4}

| Property Name | Description | Type | Value |
|-|-|-|-|
| sn_sec_tisc.webhook_ignore_threat_score_reapply | Ignore webhook events triggered by threat score recalculate history. | True/False | True |
| sn_sec_tisc.webhook_max_event_batch_size | Maximum number of events to send as part of one webhook request. The batch size will be limited to 2000 even if a higher value is set in this property. | Integer | 1000 |
| sn_sec_tisc.webhook_retry_count | Number of times a failed request should be retried before marking it as error and moving on to next batch of events. The retry count will be limited to 10 even if a higher number is set in this property. | Integer | 5 |
| sn_sec_tisc.webhook_retry_interval | Number of seconds to wait before re-attempting a failed batch. This will exponentially increase based on the retry count. For example, if retry_count is 3 and retry_interval is 30, retries are fired after 30, 60, and 120s. The initial retry interval will be limited to 300 seconds even if a higher value is set in this property. | Integer | 30 |
[ ]

{#tisc-sysprops-retry__table_zp1_pbb_2cc}
**Related tasks**   

* [Configure webhooks](https://servicenow-prod.fluidtopics.net/ODuCo7qCJ~3zNx9~~KEtjw "Configure a webhook to subscribe to events in Threat Intelligence Security Center.")
* [Webhook Triggers](https://servicenow-prod.fluidtopics.net/O8ndwLPQgmk0ujEwJZfzbg "Webhook triggers are used to filter the threat intelligence entities that needs to be tracked for any event changes such as Create, Update, and Delete.")