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

Feature Request: Specify relationship_type for attribute/event tags through the API/PyMISP #9483

Closed
1 task done
crym opened this issue Jan 10, 2024 · 0 comments
Closed
1 task done
Labels
needs triage This issue has been automatically labelled and needs further triage T: feature request Type: feature request. This issue is requesting a new feature

Comments

@crym
Copy link

crym commented Jan 10, 2024

Is your feature request related to a problem? Please describe.

I would like to be able to specify the relationship_type on event/attribute tags through the API/PyMISP

Describe the solution you'd like

Added as a optional parameter to https://pymisp.readthedocs.io/en/latest/modules.html#pymisp.PyMISP.tag (in a similar way as the parameter 'local').

For the API:
https://misp.nfcert.org/api/openapi#operation/tagEvent
https://misp.nfcert.org/api/openapi#operation/tagAttribute

Describe alternatives you've considered

Current option is doing it locally in PyMISP:
First first fetch the event and then:

tag = event.add_tag("sometag")
tag.relationship_type = "some-relationship"
misp.update_event(event)

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@crym crym added needs triage This issue has been automatically labelled and needs further triage T: feature request Type: feature request. This issue is requesting a new feature labels Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue has been automatically labelled and needs further triage T: feature request Type: feature request. This issue is requesting a new feature
Projects
None yet
Development

No branches or pull requests

1 participant