> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/hardening-and-security-suggestions-for-spinnaker.md).

# Hardening and Security Suggestions for Spinnaker

Customers may find that there is a need to secure their instances depending on their company best practices. This will vary from customer to customer depending on their overall infrastructure design and the exposure for their Spinnaker environment. The following are some articles to review that can provide some insight and help from our Armory Engineers on some best practices to look at when securing their environment

* [CVE Reports for Spinnaker](https://support.armory.io/support?id=kb_article_view\&sysparm_article=KB0010414) \* [Least Privilege Access Considerations with FIAT](https://support.armory.io/support?id=kb_article_view\&sysparm_article=KB0010281)\* [Github Security Considerations for Dinghy](https://support.armory.io/support?id=kb_article_view\&sysparm_article=KB0010284)\* [Hardening Spinnaker to Protect Against SPEL Misuse with AWS Metadata](https://support.armory.io/support?id=kb_article\&sysparm_article=KB0010526)