-
Notifications
You must be signed in to change notification settings - Fork 341
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 - Non-zero exits codes DeTT&CT CLI #46
Comments
I have the same problem. I haven't been able to get the YAML convert.
Sample YAML file:
|
Hi @SanWieb Thank you for this input! We have something related to this on our backlog and I've incorporated your request to that. Right now it has a low priority given other items that we are working on. Regards, |
Hi @arashnikoo Do you still have issues with that YAML? When using latest DeTT&CT version with all the packages from requirements.txt and using python 3.8, I don't get any error based on your given YAML file. Regards, |
Hi @rubinatorz I have the latest DeTT&CT, all the packages from requirements.txt are the latest, and using the python 3.8, still unable to convert the given YAML to file json. Traceback (most recent call last): Output for python3 dettect.py generic -ds
|
Hi @cpaul82 it seems that both errors are the same. On both code lines the data source from the MITRE data is split based on the colon. In every data source there's a colon to split the data source and data component:
We case the ATT&CK STIX data in the cache directory, and I think this local cache file is corrupt or outdated. Can you please try to remove the cache folder and try the command again? |
Hi @rubinatorz I'm having a similar error: I've made sure the packages installed are the same versions listed in requirements.txt, as you mentioned above, but the error persists. Any help would be appreciated |
Hi!
I would like to automate the generation of ATT&CK Layers with DeTT&CT via GIT actions. Detecting if the generation succeeds would be much easier if the DeTT&CT CLI exits with a non-zero code after failure.
Especially for the health check of the yaml files, but also for example when a yaml does not exists.
Is this an idea or was it a deliberate choice to have only zero exit codes?
Alternative is to check the output of the DeTT&CT CLI with a second script and base the exit code on the output, however this would be not very easy and clean.
The text was updated successfully, but these errors were encountered: