Feature: Logging and Monitoring of Authentication Activity

[brian-burton]

Description

This issue is to add a BDD feature (in compliance-test-kit/BDD-and-TDD/features) for Feature: Logging and Monitoring of Authentication Activity.

The workshop comment was:

Logging and Monitoring : linked to Observability The authentication system should provide detailed logs of authentication events, allowing for monitoring and analysis of user access patterns, potential security breaches, and compliance reporting.

This issue does not link to a decision.

[peeterko2]

The Notifications have in the Event header attributes for source, reportingSystem and relatedParty (TMF630 Part 1). In my view we should more strictly define how these attributes are used in the ODA context:

e.g. Resource Order Management (component A) create a Resource in Resource Inventory (component B) because of a Resource Order entered by a staff member (C)

ResourceCreateEvent with

• reportingSystem= B
• dource= A
• relatedParty= role: initiator, id: C

When Notifications are made mandatory including the rules as described above there should be sufficient data generated to enable this analysis.