VScanner's Knowledge Base
  • Welcome to VScanner Documentation
  • VScanner API
    • Introduction
      • Classification
    • Authentication
    • Vulnerability Scanner
      • Scans
        • Explorer Preferences
          • Features
        • Website Vulnerability Preferences
          • Features
        • Scan API Preferences
          • Features
        • Subdomain Finder
    • PDF Report Generation
  • FAQ (Frequently Asked Questions)
    • Account & Subscription
      • Can I change my subscription at any time?
      • Can I delete my account at any time?
      • Which payment methods does VScanner accept?
    • Scans & Reports
      • Can I export the scan result to PDF?
      • I fixed the vulnerabilities found on the last scan, how do I run a new one?
      • How often can I run a scan?
      • How long will it take for a scan to complete?
      • What is a target on VScanner?
      • How to scan a website on VScanner?
      • How does VScanner work?
    • Web Security Vulnerabilities
      • How to protect from cyber attacks?
      • List of OWASP TOP 10 vulnerabilities for 2021-2022
      • What are the most common vulnerabilities on websites?
      • How to fix - Broken Access Control
      • How to fix - Extension Vulnerabilities
      • How to fix - Plugin Vulnerabilities
      • How to fix - CMS Vulnerability
      • How to fix - Weak HTTPS Configurations
      • How to fix - Invalid HTTPS Certificates
      • How to fix - Session Failure
      • How to fix - Validation Failure
      • How to fix - Authorization Failure
      • How to fix - Weak Authentication
      • How to fix - Sensitive Data Exposure
      • How to fix - Cross-Site Request Forgery (CSRF)
      • How to fix - Local File Injection (LFI)
      • How to fix - Remote File Injection (RFI)
      • How to fix - Cross-Site Scripting (XSS)
      • How to fix - Command Injection
      • How to fix - SQL Injection
Powered by GitBook
On this page
  • scan_type
  • Authentication
  • API Definition
  • Some common validations
  1. VScanner API
  2. Vulnerability Scanner
  3. Scans

Scan API Preferences

Scan jobs can be configured with the optional "preferences" object. If no "preferences" object is passed to a scanning job the default parameters are used.

scan_type

Parameter type: string

To perform the explorer scan, send the scan type parameter with the value api . Check the checks performed here: Features

Allowed parameters

full

default

lite

api

The API scan is designed to perform vulnerability checks and collect relevant information through the API specification itself. In other words, to perform the API scan you need to provide the specification of your API.

{
    "url": "https://api.example.com",
    "preferences": {
        "scan_type" : "api",
        "api_definition": "https://api.example.com/api/schema",
    }
}

Example of expected response in cases of successful request:

{
    "enqueued_scan_id": "1f7dffb6-28fb-11f0-80c4-e6cba48c97bd"
}

Authentication

API Scan with Customizable Authentication

We provide authentication for API cans by providing a request field for HTTP headers. This means that you can provide the request header expected by your API.

With this feature, you can send an internal JSON request detailing exactly how your API receives, authenticates and validates the requests that will be sent.

{
    "url": "https://api.example.com",
    "preferences": {
        "scan_type" : "api",
        "api_definition": "https://api.example.com/api/schema",
        "api_header":{"x-apikey_example": "d1ue09-uecquq-q2iv-q2i-0q20qv-q0oq2"}
    }
}

Note that the key x-apikey_example was used in the example but is not limited to. In other words, you can use any names from your API regardless of which or how many keys/values ​​you need.

API Definition

We accept API definition files in:

  • JSON

  • YML/YAML

  • XML

The API types we are able to scan are:

  • OpenAPI

  • SOAP

Some common validations

When the required API definition field is missing, we currently return this message:

{
    "detail": "Something went wrong when starting your scan"
}

When the API definition does not match as expected, for ease we return the original error like this:

{
    "detail": "The type and/or format values of the api definition field 'api_definition' are invalid. Please submit a correct api definition."
}
PreviousFeaturesNextFeatures

Last updated 4 days ago