Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 52,124
    • Issues 52,124
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,547
    • Merge requests 1,547
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #366456
Closed
Open
Issue created Jun 28, 2022 by Derek Ferguson@derekfergusonDeveloper

DAST Pre-scan verification implementation

As a part of configuring scans, users should be able to click a button to verify that:

  1. We can connect to the target site.
  2. If authentication is specified, we can authenticate to the target site.
  3. We are able to follow links and crawl up to 3 pages without errors.

This should be an optional step in any test config and shouldn't interfere with saving the test, even if the verification fails.

Proposal

See the design issue for the approved designs.

  1. Add a Pre-scan verification section to the on-demand test config screen.
  2. Add a drawer that contains the Pre-scan verification details.
    1. On the test config page
    2. On the On-demand index page
  3. Show that the verification process is running.
    1. In the drawer
    2. On the test config page
  4. Add alert to on-demand index page when pre-scan verification has finished.
  5. Add Pre-scan verification column to Scan Library tab on On-demand index page.
  6. Add option on Scan Library page to verify configuration.
  7. Show the results of the pre-scan verification in the drawer.
  • 📺 Walkthrough video (Note: Some aspects of the design proposal have changed)
  • 🕹 Prototype
  • 🎨 Figma

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited Jun 28, 2022 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Time tracking