> For the complete documentation index, see [llms.txt](https://bugrecon.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bugrecon.gitbook.io/docs/use-cases-and-scenarios.md).

# Use cases and scenarios

This section describes common workflows and scenarios that combine multiple BugRecon features for automated reconnaissance and rapid discovery.

***

## Automated sync → automated scans → async alerts

Keep your scope in sync with external bug bounty providers.

1. **Sync** - Programs and scope are fetched from the connected platform. New programs create projects; scope changes (added/removed domains) update your scopes.
2. **Automated scans** - New or updated domains can trigger scans automatically (subdomain, port, HTTP, vulnerability, etc.), depending on your [Automation](/docs/features-list/automation.md) configuration.
3. **Async alerts** - Results are sent to you asynchronously via notifications (e.g. Discord) so you stay informed without watching the interface.

This flow lets you react quickly when programs change and reduces manual steps.

***

## Real-time and 24/7 certificate creation detection → alerting

[CertStream](/docs/features-list/modules/certstream.md) monitors the Certificate Transparency (CT) log stream continuously. When a new SSL certificate is issued for a domain you monitor:

1. **Detection** - The new subdomain is detected in real time.
2. **Alerting** - You receive an immediate notification (e.g. Discord) with the detected subdomain.
3. **Optional follow-up** - With [Automation](/docs/features-list/automation.md) enabled (Premium/Enterprise), follow-up scans (subdomain, port, HTTP, vulns, etc.) can be queued automatically.

This scenario is useful for discovering new subdomains as soon as they are issued, often before other hunters.

***

## Scan cascade

When new subdomains appear (from a subdomain scan, [CertStream](/docs/features-list/modules/certstream.md), or [Integration](/docs/features-list/modules/integration.md) sync), BugRecon can automatically queue a chain of follow-up scans:

1. **Trigger** - New subdomains are discovered.
2. **Cascade** - Depending on your [Automation](/docs/features-list/automation.md) settings, the platform can automatically run: port scan → HTTP scan → vulnerability scan → leaks scan → URL scan → basic auth → screenshot → domain takeover → JavaScript scan.
3. **Wildcards** - Newly discovered wildcard domains can be added to CertStream monitoring for continuous coverage.
4. **Recursive discovery** - Subdomain scans can trigger further subdomain scans for recursive enumeration.

You configure which scan types run in cascade via **Settings → Automation**. This keeps your data fresh without manual intervention.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bugrecon.gitbook.io/docs/use-cases-and-scenarios.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.