Issue/Help with "Extend CVE lookup to multiple CVEs instead of one as Threat Vault API limit is hit"

Open
#1,078 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
api, security

Research direction

Start by locating the CVE lookup API documentation and the Threat Vault API call described in the issue. Determine whether batch requests are supported, what request limit is appropriate, and how coverage for large CVE sets should work; the issue is done when multiple CVEs can be queried within a documented limit.

Written by the indexing model from the issue text.

Description

documentation

Documentation link

Describe the problem

CVE lookups are used by Threat Team, Professional Services, Customer Success Team and by customer. Current option of limiting the API to only single lookup of CVEs is limiting the functionality. It should atleast allow batch operaition like sending lookup queries for 100 CVEs or what engineering seems right number. I have customer who has reached out to me requesting coverage request for 5000+ cves and wants to know PA supports it.

Suggested fix

Kindly modify the API call for CVE to include batch operation so that multiple CVE's could be requested.

Dominant language
MDX
Stars
78
Forks
88
Avg merge
5d 17h
Merged PRs (30d)
18

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PaloAltoNetworks/pan.dev

All issues in PaloAltoNetworks/pan.dev

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.