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

alienvault connector : always insert URL of the pulse as an external reference #55

Closed
Fred-certeu opened this issue Mar 9, 2020 · 1 comment
Assignees
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)

Comments

@Fred-certeu
Copy link

Fred-certeu commented Mar 9, 2020

Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.

Problem to Solve

When importing a pulse in the form of a report, the alienvault connector creates an external reference when the orginal alienvault pulse provides an URL under in the field REFERENCE.
However, some alienvault pulses do not populate this REFERENCE field. In this case, no external reference is created in the opencti report and it is impossible, from OpenCTI, to find the origin of the information.

Current Workaround

{ Please describe how you currently solve or work around this problem, given OpenCTI's limitation. }

Proposed Solution

When importing a pulse from alienvault, the connector should always add the URL of the alienvault as an external reference
(in addition to any existing URL provided under REFERENCE in the pulse).

Additional Information

{ Any additional information, including logs or screenshots if you have any. }

@maertv
Copy link
Contributor

maertv commented Mar 24, 2020

The URL of the pulse is added to external references. Closing the issue.

@maertv maertv closed this as completed Mar 24, 2020
@maertv maertv added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 24, 2020
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

No branches or pull requests

3 participants