The Canary destination lets you to synchronise the scarlet source addresses into your ignore lists, which means you can avoid any false-positives from the normal scarlet scanning.
Canary uses a Domain Hash and Auth Token as credentials. To obtain them, follow these steps:
The Confluence destination is a great place to document your attack surface. Everything is timestamped, and the version history settings within Confluence make it easy to track changes over time.
Confluence uses an API User and API Token as credentials. To obtain them, first create a new user with minimal access privileges (this will be the API User), then follow these steps:
The Confluence URI can be obtained by creating a new page for the attack surface data, and then browsing to it. The URI will look a bit like:
which can be converted to an API URI like:
If your firewall technology supports dynamic rules (most do) then create a rule that limits the source to dispatcher.scarlet.ae
The Discord destination is rate-limited, so only really good for moderate usage. When being rate limited, messages can also be discarded or displayed in an unexpected order, which might be confusing. To help avoid this, we'd recommend separating the different event classes into different channels (sending the asset events to one channel, and the general scarlet events to another).
Discord uses a Webhook as credentials. To create one, follow these steps:
The Elasticsearch destination is good for all types of events and all levels of volume. Everything is timestamped, and the Elastic Common Schema (ECS) standard that we use is well supported by third-party tools and scripts.
Elasticsearch uses an API ID and API key as credentials. To create them, follow these steps:
If your firewall technology supports dynamic rules (most do) then create a rule that limits the source to dispatcher.scarlet.ae
The Qualys destination is a great place to send your attack surface data. scarlet will synchronise all your assets and virtual hosts into Qualys, and update any asset descriptions to make them clear and easy to identify.
Qualys uses an API User and API Password as credentials. To create them, follow these steps:
The Qualys URI can be obtained by selecting Help, then About. The API host is in the Security Operations Center (SOC) section of the page, and this should be converted into a standard URI, which will look something like:
The Sentinel destination is good for all types of events and all levels of volume. Everything is timestamped, and the Elastic Common Schema (ECS) standard that we use is well supported by third-party tools and scripts.
Sentinel uses a Webhook as credentials. To create one, follow these steps:
The Slack destination is rate-limited, so only really good for moderate usage. When being rate limited, messages can also be discarded or displayed in an unexpected order, which might be confusing. To help avoid this, we'd recommend separating the different event classes into different channels (sending the asset events to one channel, and the general scarlet events to another).
Slack uses a Webhook as credentials. To create one, follow these steps:
The Splunk destination is good for all types of events and all levels of volume. Everything is timestamped, and the Elastic Common Schema (ECS) standard that we use is well supported by third-party tools and scripts.
Splunk uses an HEC token as credentials. To create one, follow these steps:
If your firewall technology supports dynamic rules (most do) then create a rule that limits the source to dispatcher.scarlet.ae
The Teams destination is rate-limited, so only really good for moderate usage. When being rate limited, messages can also be discarded or displayed in an unexpected order, which might be confusing. To help avoid this, we'd recommend separating the different event classes into different channels (sending the asset events to one channel, and the general scarlet events to another).
Teams uses a Webhook as credentials. To create one, follow these steps: