As user, I want to Find assessed risks

[olivierlemee]

https://www.notion.so/cybnity/40-5eefc1a4251147fd8b6d19aad353eaa8

Search cybersecurity risks that are assessed (e.g in progress, finalized and consistents, reviewed) with consideration of threats, vulnerabilities, likelihoods and impacts analysis performed given a realistic visibility for their management (e.g identification of control measures to implement) regarding existent assets, and/or future (e.g projects in progress). This scope consider the processes initialized and/or finalized of risks identication, assessment, analysis.

REQ_FCT_53: https://www.notion.so/cybnity/Find-assessed-risks-97090742f19e475d83c4a3b9cadbb5d4?pvs=4

[olivierlemee]

required behaviour specified at https://www.notion.so/cybnity/Find-assessed-risks-97090742f19e475d83c4a3b9cadbb5d4?pvs=4

RMF template specified at https://www.notion.so/cybnity/FCT_73_NIST-4c39f0929d724b4fb25954fdf9a1d052?pvs=4

[olivierlemee]

PROCESS TEMPLATE AREA in security-activity-orchestration project Coded:

• ActivityState, CompletionState, Attribute, ITemplate, IWorkflowCommandHandler, Process, Step, ProcessBuilder
• unit tests

To do:

• [x] IdentifiableAggregate, AggregateRoot
• [x] Step coding
• [x] Process coding
• [x] update the mermaid doc in source code diagram according to the developed

[olivierlemee]

• [x] test sample of assembled RMF template instantiation serving as template configuration, including step's sub-processed

• [x] cucumber test of XML template read (multiple language auto-selection), instantiation via builder and buildDirector validated

• [x] XML template files defining a RMF full process including all sub-steps and NIST standard descriptions

  • [x] english version
  • [x] french version

• [x] coding of NIST RMF events published/intercepted by the staging model and steps as outcomes of sub-processes (subtasks)

[olivierlemee]

To continue to do:

from XMLProcessProcessBuilder class defining handlers in template (defineCommandsHandling(Process instance) method) from Step class defining handler according to the supported events (initializeAutomaticActivationEventsHandling() method)

• [ ] coding of default/common Process handle which intercept standard command events (application of strategy design pattern regarding behaviour of handling and managed events) relative to Process attributes change requests (e.g description)
• [ ] coding of default/common Step handler (ChainCommandHandler) which intercept comment events (application of strategy design pattern regarding behaviour of handling and managed events) relative to Step attributes change requests (e.g properties)
• [ ] ConcreteCommandHandler method to finalize regarding events (application of strategy design pattern regarding behaviour of handling and managed events) regarding implementation of ChainCommandHandler
• [ ] coding of generic event (outcomes) interception by the command handler