Microsoft recommendations to improve security and resilience in the promitor 2.9.1 service #2551
Unanswered
sairinraychoudhury
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Everyone
Needed advice from community members. We have deployed promitor 2.9.1 using helm in Microsoft Azure Kubernetes Service (AKS). Also during an assessment of our platform towards improved security & resilience angle received below recommendations from Microsoft experts to be implemented.
Containers sharing sensitive host namespaces should be avoided
Least privileged Linux capabilities should be enforced for containers
Privileged containers should be avoided
Usage of host networking and ports should be restricted.
Usage of pod HostPath volume mounts should be restricted to a known list to restrict node access from compromised containers
The root access inside the service container should be avoided.
We are not sure if above actions when implemented will have an impact on promitor since we used default promitor configs which are in helm chart for promitor.
Could anyone from the community please help or guide us on below queries?
Have you tried implementing custom configs apart from default configs provided?
Do you have a view of the impact by any means if we go ahead and implement this?
Are there any other general recommendation towards achieving this?
Beta Was this translation helpful? Give feedback.
All reactions