What cloud and integration capabilities are covered in ProjectDiscovery Documentation?

ProjectDiscovery's documentation covers cloud account monitoring, team integrations, a REST API for custom workflows, and enterprise security configuration. According to the documentation index, the cloud platform connects to AWS, GCP, Cloudflare, and Azure accounts for security vulnerability monitoring, integrates with existing ticketing and alerting tools, and supports enterprise controls such as SAML SSO, IP whitelisting, and custom headers.

Cloud Monitoring: Supported Providers

The documentation states that Cloud Monitoring lets you connect and monitor accounts from four providers:

• AWS
• GCP
• Cloudflare
• Azure

The stated purpose is to surface security vulnerabilities in those connected accounts. The page does not detail which specific services within each provider are covered, what permissions are required, or how findings are reported, so treat the provider list as the confirmed scope and verify deeper configuration details in the relevant documentation sections.

Team Integrations

The documentation describes integrations with "your existing ticketing and alerting tools." This means the platform is designed to push findings into the workflow tools your team already uses rather than requiring a separate notification channel.

The index page does not name specific ticketing or alerting products, so if you need to confirm whether a particular tool is supported, check the integration documentation directly rather than assuming coverage.

API Integration

A REST API is documented for building and automating custom security workflows. This is the path to take when the built-in integrations don't match your process — for example, if you need to trigger scans from an internal system, pull results into a custom dashboard, or chain ProjectDiscovery actions into a larger pipeline.

The documentation describes the API as "comprehensive," but the index page itself doesn't list endpoints, authentication methods, or rate limits. Those details live in the API reference.

Enterprise Security Setup

For organizations, the documentation lists configuration options including:

• SAML SSO — single sign-on for team access
• IP whitelisting — restricting access by network origin
• Custom headers — additional request-level controls

These are grouped under enterprise security setup, alongside the note that the platform is intended to scale security operations with automation.

How the Pieces Fit Together

The documentation also points to related areas: advanced exposure discovery for mapping internet-exposed assets, custom vulnerability templates for detection at scale, and a vulnerability feed for trending exploits. These sit alongside the cloud and integration capabilities rather than replacing them.

What to Check Before Committing

The index page confirms capability areas but not implementation specifics. Before adopting any of these, confirm:

1. Which services within each cloud provider are monitored — the provider list is confirmed, the service-level coverage is not.
2. Which ticketing and alerting tools have native integrations — the category is confirmed, the product list is not.
3. API authentication and limits — needed before building automation against it.
4. Enterprise feature availability — SAML SSO and IP whitelisting may be tied to specific plan tiers; the documentation index does not state pricing or plan requirements.

If your goal is simply to understand what the platform covers, the four areas above are the answer. If your goal is to implement one of them, go to that section's dedicated documentation for the configuration steps.