As far as I know, there is no such configuration to manage the domain (link to populate specific domain data only into CDP).
There were cases where a secret should not be shared publicly. meaning someone can view any secrets stored within the application. In these cases, you’ll need to explore ways to hide the secrets. The best way is to create an
orchestration/middleware/proxy layer to hide the secret. This could be built in the form of a
server-side application or
Serverless application (such as
Azure Functions or
AWS Lambda) to handle the
Client Secret to protect it from malicious users. For an example of the proper way to handle this, Create a .Net Core application to handle the secret information and facilitate requests between the SPA application (rendering host) and the CDP tenant.
What to do if someone gains access?
If someone has gained access to your protected secrets for Sitecore CDP/Personalize, you should notify
Sitecore support immediately and request a reset of your API Token. Once the reset has been completed, you’ll need to update all of your sources of ingestion/management of your tenant. But be careful during this process, to restrict access to only those that need it, and ensure you are not publicly making any secret information public.
Reference: Sitecore CDP/Personalize: Security Considerations when working with the APIs