Documentation
  • 🍻Intro
    • Why API Security is Critical?
    • Pynt at a Glance
    • Who Should Use Pynt?
  • πŸ‘©β€πŸ’»API Security Testing
    • Security Testing Overview
    • Prerequisites for Running Pynt Scans
    • How to Install Pynt CLI
    • How to install Pynt Binary (Linux only)
    • Pynt CLI Modes
      • πŸ”΅Pynt Command CLI Mode
      • πŸ”΅Pynt Listen CLI Mode
    • Pynt Security Tests Coverage
      • Business Logic Tests
      • Injection Tests
      • Authentication Bypass Tests
      • Mass Assignment Tests
      • Server-Side Request Forgery Tests
      • Stack Trace In Response
      • Lack of Resources and Rate Limiting
      • File Path Manipulation
      • GraphQL Introspection Vulnerability
      • GraphQL Alias Overloading
      • LLM APIs Vulnerabilities
      • Insecure Transport Scheme
      • Basic Authentication
      • HTTP Desynchronization (Desync) Attack
    • Sensitive Data Exposure Detection
    • Pynt Scans Troubleshooting
      • Pynt CLI Troubleshooting
      • Pynt for Postman Troubleshooting
        • Troubleshoot Pynt Container not Running Error
        • Troubleshoot Empty API Key Error
        • Troubleshoot Unauthorized API Key Error
        • Troubleshoot Collection Not Found Error
        • Troubleshoot Non-Unique Collection Name Error
        • Troubleshoot Empty Collection Identifier Error
        • Troubleshoot Unreachable Target Error
        • Troubleshoot Target Responds with Errors Error
        • Troubleshoot Unresolved Target Domain Error
        • Troubleshoot Unresolved Variable Error
        • Troubleshoot TLS Handshake Fail Error
        • Troubleshoot Few Requests Error
        • Troubleshoot One User Only Error
        • Troubleshoot Failed Assertions Error
    • How To
      • How to Run Business Logic Tests with Pynt
      • How to associate a Pynt scan to an Application in Pynt Dashboard
      • How to tag a scan in Pynt
    • Benchmarks
      • Pynt vs OWASP crAPI
  • 🀲Security Testing Integrations
    • 🟠Pynt with API Testing Tools
      • πŸ”˜Pynt for Postman
        • Fork Pynt Collection
        • Run Pynt Container
        • Run Pynt in Postman
        • View Scan Results in Postman
      • πŸ”˜Pynt for Insomnia
      • πŸ”˜Pynt for ReadyAPI
    • 🟠Pynt with API Testing CLIs
      • πŸ”˜Pynt for Newman (Postman CLI)
      • πŸ”˜Pynt for TestRunner (ReadyAPI CLI)
    • 🟠Pynt with Testing Frameworks
      • πŸ”˜Pynt for .NET (xUnit)
      • πŸ”˜Pynt for Selenium
      • πŸ”˜Pynt for Rest Assured
      • πŸ”˜Pynt for Jest
      • πŸ”˜Pynt for pytest
      • πŸ”˜Pynt for Go
      • πŸ”˜Pynt for JMeter
    • 🟠Pynt on CI/CD
      • ❗How to get Pynt ID for CI/CD Authentication
      • πŸ”˜Pynt for GitHub Actions
      • πŸ”˜Pynt for Azure DevOps Pipelines
      • πŸ”˜Pynt for GitLab
      • πŸ”˜Pynt for Jenkins
    • 🟠Pynt with Burp Suite
    • 🟠Pynt with Browsers
      • πŸ”˜Pynt for Firefox Browser
    • 🟠Live Traffic Connectors
      • πŸ”˜eBPF
        • πŸ”˜Key Components
      • πŸ”˜Traffic Mirroring
    • 🟠Advanced Pynt Examples
      • πŸ”˜Pynt as a Standalone Container
      • πŸ”˜Pynt with Prerecorded Har Files
      • πŸ”˜Pynt with cURL
  • 🈸Applications View
    • Application View Overview
    • Manage Applications
      • Add Application
      • Delete Application
      • Rename Application
    • Manage Sources for API Discovery
      • Add Source
      • Delete Source
      • View Source Info
      • Source Categories
        • API Documentation
          • Swagger
          • Postman Collection
        • API Gateways
          • AWS API Gateway
          • Azure API Gateway
          • Kong API Gateway
          • GCP API Gateway
          • Gravitee API Gateway
        • Testing (API Security Scans)
        • Live Traffic
          • Data Collection with eBPF
          • ALB Traffic Capture with AWS Traffic Mirroring
        • Code Repository
    • Application Dashboard
    • Generate Pentest Report
  • πŸ“šAPI Catalog
    • API Catalog Overview
    • Navigate API Catalog
      • Filtering API Catalog by Application
      • API Catalog Customization
      • API Related Info
      • APIs at Risk
    • Manage API Source Gaps
      • New APIs
      • Untested APIs
      • Shadow APIs
      • Undocumented APIs
    • View Detailed Endpoint Info
  • βͺScan History
    • Scan History Overview
    • Navigate Scan History
      • Associating Scans with Specific Application
      • Filtering by Application
      • Scan Related Info
      • Scan History Customization
    • View Detailed Scan Info
    • Associate Vulnerabilities to Tickets with JIRA
  • Account Management
    • Single Sign-On (SSO)
      • Setting up Okta
      • Setting up Entra ID
Powered by GitBook
On this page
  1. Scan History
  2. Navigate Scan History

Scan Related Info

Explore security-related API information in Pynt's scan history for informed decisions and efficient management.

Access detailed scan-related information in Pynt to gain a comprehensive understanding of your API security assessments. Pynt provides in-depth details for each scan, including fields such as scan date, duration, risk scores, vulnerabilities detected, and specific endpoints tested. This detailed overview allows you to thoroughly analyze each scan’s results, understand the security posture of your APIs, and track the progress of remediation efforts.

By reviewing the scan fields, you can identify patterns, prioritize vulnerabilities based on their severity, and ensure that your security measures are effective and up-to-date. Pynt’s scan-related info helps you maintain a clear and organized record of your security assessments, empowering you to make informed decisions and take targeted actions to protect your APIs.

Each entry in the 'Scan History' View provides comprehensive details about the security scans:

  1. Timestamp: The date and time when the scan occurred.

  2. User: Identifies the user who initiated the security scan.

  3. Integration: Specifies the integration or tool used for conducting the scan.

  4. Functional Test Name: Indicates the name of the functional test associated with the security scan.

  5. Scan Duration: Displays the time taken for the scan to complete.

  6. Status: Reflects the outcome of the security scan, whether it was successful or encountered issues.

  7. Application: Identifies the application associated with the scan.

  8. Endpoints Num.: The total number of endpoints tested during the scan.

  9. Errors Num.: Indicates the number of errors detected in the API endpoints.

  10. Warnings Num.: Specifies the number of warnings identified during the security scan.

  11. Report: Allows to view and download the comprehensive report associated with the scan.

PreviousFiltering by ApplicationNextScan History Customization

Last updated 8 months ago

βͺ