# Hardening guideline for Ansible itself

**URL:** <https://forum.ansible.com/t/hardening-guideline-for-ansible-itself/24565>\
**Category:** Ansible Project\
**Created:** [May 24, 2017, 12:16pm UTC](https://forum.ansible.com/t/hardening-guideline-for-ansible-itself/24565 "2017-05-24T12:16:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pawel](https://avatars.discourse-cdn.com/v4/letter/p/ecae2f/32.png) [@Pawel](https://forum.ansible.com/u/Pawel)\
**Post date:** [May 24, 2017, 12:16pm UTC](https://forum.ansible.com/t/hardening-guideline-for-ansible-itself/24565/1 "2017-05-24T12:16:47Z")

</div>

Hi,

I’m looking for best practices describing how to harden Ansible installation itself. Unauthorized access to Ansible host can do a lot of harm to the organization especially if someone could get access to playbooks or keys used by Ansible. The question is how to protect Ansible installation and sensitive data repository.

Thanks for any suggestions  
regards  
Pawel