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

Promote or demote Intrusion sets and campaigns #9461

Open
sudesh0sudesh opened this issue Dec 25, 2024 · 1 comment
Open

Promote or demote Intrusion sets and campaigns #9461

sudesh0sudesh opened this issue Dec 25, 2024 · 1 comment
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team

Comments

@sudesh0sudesh
Copy link

Hello Team,

Can we have a button for intrusion sets and campaigns so that the users can promote a campaign to an intrusion set and demote intrusion set to a campaign if they think it is necessary?

Current Work Around.

Currently, it is more tedious as they have to create a campaign and attach it to the report or multiple reports and then delete the intrusion set or vice versa.

@sudesh0sudesh sudesh0sudesh added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Dec 25, 2024
@nino-filigran
Copy link

@sudesh0sudesh could you please elaborate on this and more specifically on:

  • how often does that occur that an intrusion set is created as a campaign and vice versa?
  • why does it occur?

For future reference we already have a ticket opened about this: #3571
For now, this is something we might plan to do, but on a limited set of entities (threat actor <-> intrusion set & malware <-> tool, hence the question to understand the real issue behind this request).

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