diff --git a/content/docs/1.getting-started/05.api-scan/2.creating-a-collection.md b/content/docs/1.getting-started/05.api-scan/2.creating-a-collection.md index 46cd255..38435a0 100644 --- a/content/docs/1.getting-started/05.api-scan/2.creating-a-collection.md +++ b/content/docs/1.getting-started/05.api-scan/2.creating-a-collection.md @@ -34,7 +34,7 @@ Once your target is set up: ## Step 3: Select Your API Source Type -ZeroThreat offers many options for importing your API collection: +ZeroThreat offers multiple methods to create or import your API collection. In Step 3, choose any one method based on how your APIs are available, such as uploading an existing collection, importing from a cloud source, or recording API requests using ZeroThreat API Recorder. | Source Type | Description | | ---------------------- | ----------------------------------------------------------------------------- | @@ -131,7 +131,15 @@ If your APIs are managed in **MuleSoft Anypoint Platform**, you can connect Zero ::fiqure-img{source="/Images/image (385).png"} :: -2. **Set Up Integration** +2. **Required MuleSoft Scope** + + Before connecting MuleSoft with ZeroThreat, make sure your MuleSoft connected app has the required access scope.\ + In MuleSoft Anypoint Platform, go to **Access Management > Connected Apps**, open your connected app, then click **Add Scopes** and assign the **Exchange Viewer** scope. + + ::fiqure-img{source="/Images/image (506).png"} + :: + +3. **Set Up Integration** * Enter a **Connection Name**. * Provide your **Client ID** and **Client Secret** from your MuleSoft Anypoint account. * ZeroThreat will validate the credentials before proceeding. @@ -139,7 +147,7 @@ If your APIs are managed in **MuleSoft Anypoint Platform**, you can connect Zero ::fiqure-img{source="/Images/image (386).png"} :: -3. **Fetch APIs** +4. **Fetch APIs** * Once validated, ZeroThreat fetches your available organizations and API assets. * Choose the **Connection** (newly created or previously saved). @@ -295,6 +303,62 @@ Your Postman Cloud APIs will be added as a Collection in ZeroThreat. You can opt +#### ZeroThreat API Recorder + +ZeroThreat API Recorder lets you create an API collection by browsing your web application and capturing the API requests triggered during normal user actions. This is useful when you do not already have an API collection ready, when API inventory is missing, or when new APIs have been added and need to be discovered through frontend workflows. Instead of manually uploading a specification file, you can let ZeroThreat collect in-scope API requests as you interact with the application. + +**Prerequisite:** You must have the ZeroThreat Chrome Extension installed. + +
+ +Steps to create a collection using ZeroThreat API Recorder + +1. Click **ZeroThreat API Recorder**. + +::fiqure-img{source="/Images/image (501).png"} +:: + +2. Enter a **Collection Name** and the **Web Application URL**. + +::fiqure-img{source="/Images/image (502).png"} +:: + +The Web Application URL is the frontend application where the recorder will open. As you browse the application, ZeroThreat captures API requests that belong to the target scope. + +::hint{ style="background-color:#f7fcff; border:1px solid #07405a33; color:#1e6995;" icon="circle-info" iconClass="text-sky-600"} +###### If your frontend and APIs use the same domain or subdomain, you can use that application URL directly. + +###### If your frontend and APIs use different subdomains, create the ZeroThreat target using the API domain, then enter the frontend URL as the Web Application URL. + +###### For example, if your API is hosted on `api.example.com` and your frontend is hosted on `app.example.com`, create the target for `api.example.com` and enter `app.example.com` as the Web Application URL. The recorder will open the frontend, and API requests made to the target API domain will be collected. +:: + +::hint{ style="background-color:#fff4e6; color:#f97316; border:1px solid #f6d2b0;" icon="triangle-exclamation" iconClass="text-[#f97316]"} +###### **Note:** API requests outside the configured target scope will not be included in the collection. +:: + +3. Click **Open Extension to Record API Requests**. This opens the web application in a new tab and launches the ZeroThreat Chrome Extension on that page. +4. In the extension, click **Start Recording**. + +::fiqure-img{source="/Images/image (503).png"} +:: + +5. Browse the application and perform the user actions that trigger the APIs you want to include in the collection. +6. When you are done, click **Stop Recording** in the extension and click **Save** to store the API collection. + +::fiqure-img{source="/Images/image (504).png"} +:: + +7. Return to the ZeroThreat portal and click **Next**. + +::fiqure-img{source="/Images/image (505).png"} +:: + +The captured APIs will be added to the collection and can be used for scanning. + +
+ + ## Step 4: Review and Configure API Endpoints diff --git a/content/docs/2.manage-targets/4.target-configuration.md b/content/docs/2.manage-targets/4.target-configuration.md index 2c31281..0a7da9b 100644 --- a/content/docs/2.manage-targets/4.target-configuration.md +++ b/content/docs/2.manage-targets/4.target-configuration.md @@ -6,6 +6,20 @@ description: Target Configuration helps define how ZeroThreat should interact wi seo.description : Fine-tune your scan targets by configuring headers, authentication, and server options. Optimize each target setup for accurate and effective scanning. --- +## Accessing Target Configuration + +To open Target Configuration, go to the **Dashboard** and click **Targets.** + + ::fiqure-img{source="/Images/image (77).png"} + :: + +The Targets page lists all Web and API targets that you have. From here, click the target URL or the gear icon next to the target you want to configure. + + ::fiqure-img{source="/Images/image (507).png"} + :: + +This opens the Target Configuration drawer for that specific target, where you can manage scan behavior, scope, authentication-related settings, schedules, scan profiles, integrations, and other target-level options. + ## Configuration The Configuration section contains core settings that affect how the scanner runs against your target. diff --git a/content/docs/6.plans/01.zerothreat-plans.md b/content/docs/6.plans/01.zerothreat-plans.md index f22e607..9ddb5c0 100644 --- a/content/docs/6.plans/01.zerothreat-plans.md +++ b/content/docs/6.plans/01.zerothreat-plans.md @@ -13,7 +13,7 @@ description: ZeroThreat offers plans for individuals, security teams, enterprise ## Unified Plan Comparison -
+
PlanPricingHostsParallel ScansRe-TestsCI/CD IntegrationIssue Tracking IntegrationNotification IntegrationStatic IPProduction-Safe TestingAgentic AI PentestingComplex UI Flow Automation (Playwright)Custom Attack TemplatesWhite-Label ReportsCVE Based Attack Coverage (Scan Profile)Open Attack Coverage (Scan Profile)Popular CVE's (Scan Profile)Quick TestDelay Days for latest CVE's
Free Plan$0/month – 5 scans on signup with limited report view, then 1 scan/month with limited report viewUnlimited1 per hostNoNoNoNoNoNoYesNoNoNoPreviewPreviewNoNoNot Applicable
Professional Cloud$100/month for the first host, $75/month for each additional host up to 10. 20% off annual upfront payment1–101 per hostUnlimitedNoNoYesNoNoYesNoNoNoYesPreviewNoYes30
Professional Pay-Per-Scan$25 per scan. Minimum purchase: $125 for 5 creditsUnlimitedUsage-basedFree 1-week Re-RestNoNoNoNoNoYesNoNoNoPreviewPreviewYesNo30
Enterprise CloudContact Sales10+3 per hostUnlimitedYesYesYesYes – ExtraYesYesYesYes – Nuclei + Burp + Faster UpdatesYesYesYesNoYes0
Enterprise Pay-Per-ScanContact SalesUnlimitedUsage-basedFree 1-week Re-TestNoNoYesYes – ExtraNoYesNoYes – Nuclei + Burp + Faster UpdatesYesYesYesNoNo0
Enterprise On-PremContact SalesUnlimited2 per instanceUnlimitedYesYesYesNot ApplicableYesYesYesYes – Nuclei + Burp + Faster UpdatesYesYesYesNoYes0
diff --git a/main.css b/main.css index 2169c9b..937606a 100644 --- a/main.css +++ b/main.css @@ -411,3 +411,22 @@ table tr td:first-child { max-width: 220px; width: 220px; } + + .table_scroll::-webkit-scrollbar { + width: 5px; + height: 8px; +} + +.table_scroll::-webkit-scrollbar-track { + background: rgba(216, 214, 214, 0.658); + border-radius: 9999px; +} + +.table_scroll::-webkit-scrollbar-thumb { + background: rgba(161, 160, 160, 0.603); + border-radius: 9999px; +} + +.table_scroll::-webkit-scrollbar-thumb:hover { + background: rgba(140, 140, 140, 0.8); +} diff --git a/public/Images/image (501).png b/public/Images/image (501).png new file mode 100644 index 0000000..597f3f1 Binary files /dev/null and b/public/Images/image (501).png differ diff --git a/public/Images/image (502).png b/public/Images/image (502).png new file mode 100644 index 0000000..c5c1455 Binary files /dev/null and b/public/Images/image (502).png differ diff --git a/public/Images/image (503).png b/public/Images/image (503).png new file mode 100644 index 0000000..bbbed07 Binary files /dev/null and b/public/Images/image (503).png differ diff --git a/public/Images/image (504).png b/public/Images/image (504).png new file mode 100644 index 0000000..5bb5bb1 Binary files /dev/null and b/public/Images/image (504).png differ diff --git a/public/Images/image (505).png b/public/Images/image (505).png new file mode 100644 index 0000000..ce9912c Binary files /dev/null and b/public/Images/image (505).png differ diff --git a/public/Images/image (506).png b/public/Images/image (506).png new file mode 100644 index 0000000..e0d602e Binary files /dev/null and b/public/Images/image (506).png differ diff --git a/public/Images/image (507).png b/public/Images/image (507).png new file mode 100644 index 0000000..65fee22 Binary files /dev/null and b/public/Images/image (507).png differ diff --git a/public/Images/image copy.png b/public/Images/image copy.png deleted file mode 100644 index 1827e19..0000000 Binary files a/public/Images/image copy.png and /dev/null differ