Code Quality: Lack of Logging throughout codebase

[DinikaKC]

Description

There is minimal to no logging for security-related actions. This absence makes it difficult to trace unauthorized access attempts or to audit actions taken by the application. If this is being handled elsewhere already, please specify as I'm new to this

Concerned code

WindowsSecurityService.cs
AccessControlEntry.cs
StorageSecurityService.cs

Gains

• eg. A better readability.
• eg. Uncoupling concepts X and Y.
• eg. Clarifying the responsibility of class C.

Requirements

• eg. Using a specific design pattern.
• eg. Separating Interface I into three new interfaces I1, I2 and I3.
• eg. Regrouping the duplicated process into a new helper.

Comments

No response

[yaira2]

Can you clarify what you mean by logging?