Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Playbook] Be able to use Vulnerability specific fields in playbook filters #7409

Open
romain-filigran opened this issue Jun 18, 2024 · 0 comments
Open

[Playbook] Be able to use Vulnerability specific fields in playbook filters #7409

romain-filigran opened this issue Jun 18, 2024 · 0 comments
Assignees
@Archidoit @ValentinBouzinFiligran @romain-filigran @Gwendoline-FAVRE-FELIX
Labels
feature use for describing a new feature to develop playbook Linked to automation engine
Milestone
Release 6.3.0

Comments

@romain-filigran
Copy link
Member

Use case

Use of vulnerability-specific fields to filter entities in playbooks.

Current Workaround

No workaround

Proposed Solution

Support of vulnerability specific fields in "match knowledge" component:

  • CVSS V3 properties
  • Future EPSS properties
  • Future KEV property
@romain-filigran romain-filigran added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels Jun 18, 2024
@romain-filigran romain-filigran modified the milestone: Release 6.3.0 Jun 18, 2024
@romain-filigran romain-filigran mentioned this issue Jun 18, 2024
Open
@romain-filigran romain-filigran changed the title Be able to use Vulnerability specific fields in playbook filters [Playbook] Be able to use Vulnerability specific fields in playbook filters Jun 18, 2024
@romain-filigran romain-filigran added this to the Release 6.3.0 milestone Jun 20, 2024
@romain-filigran romain-filigran self-assigned this Jun 20, 2024
@Jipegien Jipegien added the playbook Linked to automation engine label Jul 1, 2024
@Archidoit Archidoit self-assigned this Jul 3, 2024
@ValentinBouzinFiligran ValentinBouzinFiligran self-assigned this Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Archidoit Archidoit

@ValentinBouzinFiligran ValentinBouzinFiligran

@romain-filigran romain-filigran

@Gwendoline-FAVRE-FELIX Gwendoline-FAVRE-FELIX

Labels
feature use for describing a new feature to develop playbook Linked to automation engine
Projects
None yet
Milestone
Release 6.3.0
Development

No branches or pull requests
5 participants
@Archidoit @Jipegien @ValentinBouzinFiligran @romain-filigran @Gwendoline-FAVRE-FELIX