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

[wiz]: Add a connector option to convert threat actor in intrusion-set #3435

Closed
romain-filigran opened this issue Feb 17, 2025 · 0 comments · Fixed by #3438
Closed

[wiz]: Add a connector option to convert threat actor in intrusion-set #3435

romain-filigran opened this issue Feb 17, 2025 · 0 comments · Fixed by #3438
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@romain-filigran
Copy link
Member

Use case

Wiz public Threat Landscape Feed (https://www.wiz.io/api/feed/cloud-threat-landscape/stix.json) models adversary information as STIX Threat Actor entities. To avoid duplication, add a connector option to convert these threat actors into intrusion-set entities.

@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 Feb 17, 2025
@romain-filigran romain-filigran added this to the Bugs backlog milestone Feb 17, 2025
@flavienSindou flavienSindou added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 18, 2025
maximus-debski pushed a commit to maximus-debski/connectors that referenced this issue Feb 26, 2025
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 solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants