Skip to main content
In Flarehawk, an asset represents a single domain you want to monitor. Each asset has its own ingest endpoint, its own ingest token, its own detection tier, and its own event retention setting. When you add a new domain to Flarehawk, you are creating an asset and then connecting an upstream security tool — see Integrations — to deliver events to that asset’s endpoint.

​
What an asset contains

Every asset in Flarehawk tracks the following:

​
The ingest endpoint

Each asset has a dedicated ingest endpoint built from its asset ID:
When you connect a source through an integration, Flarehawk provisions delivery to these endpoints automatically. The asset ID in the URL path routes incoming events to the correct asset, and the ingest token (sent as a header) authenticates each delivery.
Keep your ingest token secret. Anyone with the token and your asset ID can push data to your asset. If you suspect a token has been compromised, rotate it from Settings → Connections in the dashboard.

​
Multiple assets per organization

Your organization can have multiple assets — one per domain you want to monitor. Each asset is fully independent:
  • Alerts, logs, and analytics are scoped to the individual asset
  • Detection tier and retention can differ between assets
  • You can pause or disable one asset without affecting others
This design lets you apply different monitoring strategies to different domains. For example, you might run your production API on the Complete tier for maximum coverage, while a low-traffic staging domain runs on the Basic tier.
Use the asset name field to make it clear which environment an asset represents (e.g., api-production vs api-staging), especially if you have multiple zones under the same organization.

​
Source connection

Flarehawk tracks the status of each upstream source connected to an asset. On the Getting Started page, the dashboard walks you through the integration-specific setup so you can connect a source without copying values manually. See Integrations for the list of supported sources and their delivery modes. Once events start flowing, the asset’s status updates to confirm that ingestion is working. You can see the last ingest time and total event count for each asset from the asset list.

​
Asset verification

When you add an asset, Flarehawk may ask you to verify ownership of the domain. Verification confirms that the asset identifier matches a domain you control, preventing accidental cross-tenant data delivery.
Deleting an asset removes the asset configuration and invalidates its ingest tokens immediately. Existing alerts and events associated with the asset are also removed. This action cannot be undone. Disconnect or stop your upstream source first to avoid delivery errors after deletion.
Yes. The asset name is a display label only and does not affect the ingest endpoint or token. Renaming an asset does not require any changes to your upstream source configuration.
Yes. Asset access is governed by your organization’s membership. All members of your organization can view and manage assets based on their role.