[Feature Request]: Update secure by default parameter description

Azure / ResourceModules

This repository includes a CI platform for and collection of mature and curated Bicep modules. The platform supports both ARM and Bicep and can be leveraged using GitHub actions as well as Azure DevOps pipelines.

https://aka.ms/carml

MIT License

725 stars 459 forks source link

[Feature Request]: Update secure by default parameter description #1703

Open eriqua opened 2 years ago

eriqua commented 2 years ago

Description

Whenever we mention that a particular parameter value should be set/enabled "for security reasons" we should probably mention in the description which rules we are following or which security baseline we aim to comply with. E.g., NIST 800

This issue is about

proposing and agreeing on a proper sentence to cover the above
update the relevant parameter descriptions throughout the modules
regenerate module readme files

rahalan commented 1 year ago

Team needs to decide what the actual quote should be saying and where it needs to sit.

rahalan commented 1 year ago

See #2176

rahalan commented 1 year ago

Will be discussed in a dedicated meeting

rahalan commented 1 year ago

Team will wait for the PSRule implementation #2149