Parameters with the type securestring and secureObject are designed to pass sensitive data to the resources being
deployed. Secure parameters cannot be accessed after the deployment is completed: they can neither be logged nor used as an output.
When used in nested deployments, however, it is possible to embed secure parameters in such a way they can be visible afterward.
What is the potential impact?
If the nested deployment contains a secure parameter in this way, then the value of this parameter may be readable in the deployment history. This
can lead to important credentials being leaked to unauthorized accounts.
