Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • #214120
Closed
Open
Issue created Apr 10, 2020 by Derek Ferguson@derekfergusonDeveloper5 of 5 checklist items completed5/5 checklist items

Disable the DAST spider and provide list of urls to scan

Problem to solve

Users sometimes want to scan only a specific set of URLs, instead of having the scan spider their entire app. This would allow for more targeted, quicker scans of the application when they know the branch being scanned only applies to specific areas of the app.

Implementation plan

  • Create a multi-page website fixture
  • Implement Passive Scan !284
  • Implement Active Scan !293
  • Change DAST_URLS to DAST_PATHS. DAST_PATHS should only not include the host and should work with the DAST_WEBSITE to make the full URL. This will allow users to use review apps without having to reset the DAST_URLS in a before_script. !300
  • Add documentation !41727 (merged)

Intended users

  • Delaney (Development Team Lead)
  • Sasha (Software Developer)
  • Sam (Security Analyst)
  • Simone (Software Engineer in Test)

Further details

Proposal

Assuming that this is supported by ZAP, I believe that we should do two things to support this feature:

  1. Add an environment variable to disable spidering
  2. Support multiple URLs (comma-delimited) in the DAST_WEBSITE environment variable.
  3. or a text file with urls

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited Sep 16, 2020 by Craig Smith
Assignee
Assign to
Time tracking