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

Risk treatment plan exporter should have asset populations #181

Open
mike1813 opened this issue Jun 18, 2024 · 3 comments
Open

Risk treatment plan exporter should have asset populations #181

mike1813 opened this issue Jun 18, 2024 · 3 comments
Assignees
Labels
bug Something isn't working DS2 Internal Project.

Comments

@mike1813
Copy link
Member

In the version tagged as v3.6.0-test, the web U/I supports extraction of a risk treatment plan. This provides a list of system model asset classes, each displayed with its type, a brief description, and its population level, followed by a table listing its potential (mis)behaviours. This table cites threats that cause each misbehaviour, and control strategies that block those threats.

There is an option to 'Export' the risk treatment plan as a offline HTML document. In the web U/I, the correct population levels are shown for each asset class, but in the 'exported' version, they are not. Instead, we get a population level 'Very Many', which is the highest level in the domain model population scale, highest population level for the relevant asset. This is 'greyed out', so it may be a default, suggesting that the problem may be that population levels are actually missing in the exported version.

The attached test case reproduces the error using domain model v6a5-1-2.

small-uncontrolled asserted.nq.gz

@mike1813 mike1813 added the bug Something isn't working label Jun 18, 2024
@kenmeacham kenmeacham assigned dgc and unassigned kenmeacham Dec 17, 2024
@kenmeacham
Copy link
Contributor

Assigned to @dgc, as related to reporting work. Not sure if this is required, depending on what happens with the reports generally.

@mike1813
Copy link
Member Author

mike1813 commented Jan 9, 2025

Reviewed by @mike1813 : this probably should be addressed because we know ongoing research projects do need enhanced reports. The code affected is fairly new, and was originally intended to meet some of those needs, so it seems likely this flaw will affect at least some current research activities.

@sdm2d11
Copy link

sdm2d11 commented Feb 12, 2025

@druimalban and @kenmeacham to discuss how to fix (or better avoid) this in the new version of the report export.
Suggestions from Mike is that it might be a problem of including it in the actual exported file rather than in retrieving the information from the Knowledge Base.

Close the issue when the new reporting function is available, provided it does not show up there.

@dgc : in your handover discuss this issue with @druimalban if you have done anything (actually or planned).

@sdm2d11 sdm2d11 added the DS2 Internal Project. label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working DS2 Internal Project.
Projects
None yet
Development

No branches or pull requests

4 participants