Not run DPOD service as root user with service account privilege managment

As indicated in the security assessment conducted by our bank client's Pentest team, a vulnerability known as the "Over-Privileged Server Service Account Principal" has been detected, which poses a significant risk to the client organization's security posture and regulatory compliance. Some of DPOD services currently operate with root user privileges(https://montier.atlassian.net/wiki/spaces/DPOD011900/pages/15800010210/Operating+System+Users). While this configuration may have been necessary for certain historical reasons, it has now come under scrutiny due to its implications for security and compliance. This over-privileged state increases the attack surface and makes it easier for malicious actors to compromise the system, potentially leading to unauthorized access, data breaches, and other security incidents. Furthermore, it violates the company's compliance requirements, thereby exposing the client to legal and financial risks. To address this critical security and compliance concern, I propose the following feature enhancement: Service Account Privilege Management that implement a comprehensive review and adjustment of service account privileges for all DPOD services. This entails:
   Identifying services currently running with root user privileges.
   Restricting and aligning the privileges of these services to the minimum necessary to perform their designated tasks.
   Implementing a strict principle of least privilege (PoLP) across the board to ensure that services only have access to the resources they require.
By implementing these actions, we can reduce the risk posed by over-privileged service accounts and ensure compliance with company policies.