From 4a2dba27fe51ee38e08da050c036e15b2f1b2467 Mon Sep 17 00:00:00 2001 From: pasant9 Date: Wed, 30 Oct 2024 11:53:59 +0530 Subject: [PATCH] Add allow list to expose Developer portal --- ...curity-guidelines-for-production-deployment.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/en/docs/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment.md b/en/docs/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment.md index 3a8f27f7ca..3ec01184fc 100644 --- a/en/docs/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment.md +++ b/en/docs/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment.md @@ -812,12 +812,25 @@ This section provides a list of security guidelines for configuring the network

Note:

It is recommended to use an allowlisting approach when allowing access to resources in your product from the DMZ level.

+

For the API-M Developer Portal, exposing the following paths would be sufficient:

+ + - ## Configure client authentication Client authentication is used to identify the application or the client that is making the request.