You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For my use case with ARX, I'd like to be able to output the final attacker model results as part of the output PDF (File => Create Certificate).
Describe the solution you'd like
Just having the values in the output certificate would be very helpful, as that would mean that one file would have all the information, rather than need to screenshot the attacker models page separately.
Describe alternatives you've considered
I'm not really sure what other ways it can be added in, but the main alternative is just what we are already doing - screenshotting the values separately.
The text was updated successfully, but these errors were encountered:
Thanks for suggesting this. The certificate is currently quite limited in the amount of information it contains. The main reason is that a lot of the risk and utility measures provided by ARX can be quite computationally demanding to calculate. Hence, to extend the certificate with additional information would probably require (1) a rewrite to generate the certificate in a background thread and (2) a dialog where users can select the information that they want to have included.
This requires some work and we are not able to implement this at the moment due to a lack of resources. I will leave the issue open for others to take up or for us to come back to it when we have time.
Is your feature request related to a problem? Please describe.
For my use case with ARX, I'd like to be able to output the final attacker model results as part of the output PDF (File => Create Certificate).
Describe the solution you'd like
Just having the values in the output certificate would be very helpful, as that would mean that one file would have all the information, rather than need to screenshot the attacker models page separately.
Describe alternatives you've considered
I'm not really sure what other ways it can be added in, but the main alternative is just what we are already doing - screenshotting the values separately.
The text was updated successfully, but these errors were encountered: