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.

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

Broken attack patterns matrix everywhere #5841

Closed
SamuelHassine opened this issue Feb 6, 2024 · 2 comments
Closed

Broken attack patterns matrix everywhere #5841

SamuelHassine opened this issue Feb 6, 2024 · 2 comments
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@SamuelHassine
Copy link
Member

Description

  1. This issue leads multiple screens to not work correctly.
  2. Do a query like:
query {
  attackPatterns(first: 5000) {
    edges {
      node {
        id
      }
    }
  }
}

Result is:

image

Only 500 first are returned.

@SamuelHassine SamuelHassine added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 6, 2024
@Jipegien Jipegien added critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Feb 7, 2024
@Goumies Goumies self-assigned this Feb 8, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.0 milestone Feb 8, 2024
@SamuelHassine SamuelHassine reopened this Feb 10, 2024
@SamuelHassine SamuelHassine changed the title Broken attack patterns matrix everywhere - request for 5000 entities will return only 500 Broken attack patterns matrix everywhere Feb 10, 2024
@richard-julien
Copy link
Member

This is expected behavior. If the attackPatterns ask for 5000 elements we need to rework the screen or create a specific API

@Jipegien
Copy link
Member

This current behaviour is not good enough. We need to fix this for the next major release. We are currently not consistent in our displaying of matrices and this is a major CTI use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

4 participants