Establish requirements for forensic logging, auditing

[godfreykutumela]

Goal:

As a OSS developer

`I want to have a full view of all the requirements related to forensic logging, auditing

so that I can design an end to end solution which addresses all through a design change

Acceptance Criteria:

• TBD

Complexity: Medium > Our platform is unique so we need to search deeper for this to ensure that nothing is missed in the process

Uncertainty: Low > It is archiveable

---

Tasks:

• TBD [ @? ]

Pull Requests:

• TBD

Follow-up:

• N/A

Dependencies:

• N/A

Accountability:

• Owner: @MichaelJBRichards
• QA/Review: @godfreykutumela

[mccleanla]

Hi there Would advise this team connect to the existing workstreams already talking about this... Pedro running sessions, Adrian and Michael engaged, me from product requirements needs. 2 workstreams: feature baseline + business process needs. Lesley-Ann

…

Sent from my iPhone

On 12 Feb 2021, at 12:29, Godfrey Kutumela ***@***.***> wrote:  Goal: As a OSS developer `I want to have a full view of all the requirements related to logging, audit and forensic so that I can design an end to end solution which addresses all through a design change Acceptance Criteria: TBD Complexity: Medium > Our platform is unique so we need to search deeper for this to ensure that nothing is missed in the process Uncertainty: Low > It is archiveable Tasks: TBD [ @? ] Done Acceptance Criteria pass Designs are up-to date Unit Tests pass Integration Tests pass Code Style & Coverage meets standards Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config. TBD Pull Requests: TBD Follow-up: N/A Dependencies: N/A Accountability: Owner: @godfreykutumela QA/Review: @godfreykutumela — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[godfreykutumela]

Noted will do @lavaughan

[rasputtintin]

@godfreykutumela please see updated story

[godfreykutumela]

Hi @MichaelJBRichards can you please have a look at this one from a business requirement perspective.

[godfreykutumela]

The logging, audit and forensic requirements will be defined as part of the Domain-Driven Development Sessions and brought here as input for further analysis and the output as input in the architecture review and redesign work. Please note @pedrosousabarreto and help track this in the problem/Solution space.

[godfreykutumela]

We will receive this from the feature baseline and business processes workstream.

[godfreykutumela]

Merged into the reference architecture