Takedown Services
By streamlining the takedown request process for threat exposures such as malicious domains, code repository leaks, social media threats, and more, Flare significantly reduces the risks associated with threat actors exploiting these vectors in attacks against your business or customers.
Certain Flare packages and add-ons include a number of takedowns requests per year.
- Malicious Look-Alike Domains
- Reasons: Phishing, Attack Infrastructure
- Paste Sites (i.e., pastebin)
- Reasons: Leaked credentials, personally identifiable information (PII)
- Source Code (i.e., GitHub)
- Reasons: Leaked secrets, personal information, defamatory content, bullying, verbal abuse
- Cloud Infrastructure Buckets (i.e., AWS S3, Azure Blob Storage)
- Reasons: Leaked secrets, personally identifiable information (PII), malicious content
- Social Media (i.e., Meta properties, LinkedIn, X)
- Reasons: Impersonation, fraud, scam, other terms of use violations
You can initiate a takedown request for identified threat exposures in two ways:
- Within the Flare Application: Use the request takedown option from a related look-alike domain, source code, paste site, or cloud bucket Flare event card within the app. After clicking "request takedown," you will be taken to a form to provide further details about the request (Figure 1)
- Via Email Communication: For social media threat exposures, you can communicate with a Flare Customer Success Manager. Flare will provide a similar form for you to fill in and start the takedown process. For social media threats, you must identify and report them to us via Email, as the Flare platform does not detect these exposures automatically.
Once the forms are completed with the takedown request details, you will receive an email and/or in-app confirmation, including a ticket tracking link and status updates. Flare conducts the takedown request process, which varies by use case. If additional information is required, you will be notified via email. After processing, a takedown confirmation is provided via email and/or within the app, indicating whether the request was successful or unsuccessful.
It is important to note that submission does not guarantee success, as outcomes depend on the request's nature and third-party cooperation. Generally, the more obviously malicious the threat exposure or the more clearly it violates third-party terms of service, the higher the likelihood of a successful takedown.
