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

Add "Rust" to Malware programming languages + allow Admins to add custom languages #1905

Closed
securitiz opened this issue Feb 19, 2022 · 3 comments
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

@securitiz
Copy link

Use case

The list of programming languages for Malware is limited

Current Workaround

n/a

Proposed Solution

Add rust + allow admins to add programming languages as necessary

Additional Information

If the feature request is approved, would you be willing to submit a PR?

Yes / No (Help can be provided if you need assistance submitting a PR)

@nor3th nor3th added the feature use for describing a new feature to develop label Feb 19, 2022
@guys1444
Copy link
Contributor

guys1444 commented Feb 25, 2022

Link or Image to this case ?, Thanks

do you mean as a new entity ?

@securitiz
Copy link
Author

Not as a new entity. I've attached a screenshot below. When updating a malware, you can specify what language it is written in, and rust is not in that list:

image

image

guys1444 added a commit to guys1444/opencti that referenced this issue Feb 26, 2022
Update the key of the Rust programming language with a description regarding to issue OpenCTI-Platform#1905 Add "Rust" to Malware programming languages + allow Admins to add custom languages.
@securitiz
Copy link
Author

This may be fixed by #1886 if it is applied to other parameters such as Threat Actor's "Resource Level", Malware's "Malware Types", and in this case Malware's "Architecture Execution Environment"

@SamuelHassine SamuelHassine added this to the Release 5.4.0 milestone May 5, 2022
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Sep 29, 2022
@SamuelHassine SamuelHassine removed this from the Release 5.4.0 milestone Sep 29, 2022
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

4 participants