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

Missing TTPs in the DISARM matrix #9691

Open
yassine-ouaamou opened this issue Jan 23, 2025 · 3 comments
Open

Missing TTPs in the DISARM matrix #9691

yassine-ouaamou opened this issue Jan 23, 2025 · 3 comments
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team

Comments

@yassine-ouaamou
Copy link
Member

Description

Although they exist in the platform as Attack patterns, some TTPs are not findable from the Matrix

Reproducible Steps

For example, in Testing the TTP T0023.001 - Reframe context exists but can't be reached from the Matrix view within an incident

Steps to create the smallest reproducible scenario:

  1. Go to an incident
  2. Go to Knowledge -> Attack Patterns
  3. Select the "Disarm" framework
  4. Search for Reframe context

Expected Output

Actual Output

Can't find it.
FYI, I can only see its parent: Distort Facts

Additional information

Screenshots (optional)

@yassine-ouaamou yassine-ouaamou added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 23, 2025
@nino-filigran
Copy link

I don't think it's a bug, but rather, this third level is not shown in the matrix, hence the fact that you cannot find it. I however understand that not finding it makes it difficult to create a relation between lets say an intrusion & this TTP, since you have to go in the parent TTP, find the child TTP that you need, go in the child TTP, go in the knowledge view & then create the needed relation.

@nino-filigran nino-filigran added feature use for describing a new feature to develop and removed bug use for describing something not working as expected labels Jan 24, 2025
@nino-filigran
Copy link

Therefore, the requirement is that we should add a way to visualise the3rd level of child within the matrix.

@yassine-ouaamou
Copy link
Member Author

Indeed @nino-filigran. Do you want me to change the title of the issue to correspond more to a feature rather than a bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
Projects
None yet
Development

No branches or pull requests

2 participants