Parameters with the type securestring and secureObject are designed to pass sensitive data to the resources being
deployed. Unlike other data types, they cannot be accessed after the deployment is completed. They can neither be logged nor used as an output.
Secure parameters can be assigned a default value which will be used if the parameter is not supplied. This default value is not protected and is
stored in cleartext in the deployment history.
What is the potential impact?
If the default value contains a secret, it will be disclosed to all accounts that have read access to the deployment history.
