![]() Now I know part of this is correct because not only is it connecting the with AIM server, but I am getting a consistent error in the APPAudit.log: Username: tenableDomain: ĬyberArk Account Details Name: -tenable ![]() I will go down through the options as I added them: Only then did I attempt to work with Tenable.sc, and created a "Windows CyberArk Vault Credential". I immediately did a CPM reconcile on the tenable user account to validate that it was in sync with the local Windows AD. ![]() To this safe I have granted the PROV_hostname user, the "nessus" application user AND the domain user "tenable" access to the safe to be able to pull paswords. I have created a domain user account with the name of "tenable" and placed that account within a newly created safe titled TenableSC. This followed the same procedure used for the other applications. I have defined the name "nessus" as my application, and identified the Tenable.sc server as the application source. ![]() I already have 4 applications configured within AIM and pulling passwords successfully, so I am going to consider #1 and #2 completed. wadageek, thank you for such an ordered list, but I need to comment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |