MID server doesn't accept SNMPv3 credentials from CyberArk that do have a policy id other than SNMPv3 and SNMPv3PrivacyKeyDescriptionMID server doesn't accept SNMPv3 credentials from CyberArk that do have a policy id other than SNMPv3 and SNMPv3PrivacyKeySteps to Reproduce Create a new SNMPv3 Credential as per CyberArk vault configurationCreate a new MID SNMP Trap ListenerAssociate the credential from item 1 to item 2 aboveStart MID SNMP Trap listenerObserved warning that ignoring the SNMPv3 Credential 06/02/20 12:20:49 (039) ECCQueueMonitor.1 WARNING *** WARNING *** (70)SNMPTrapListener - SNMPTrapListener: (<credential>): Security name does not defined for credentials: <credential>,skeeping this record OR Create snmpv3 credential on discovery_credentials tableIn order to confirm the credential is correct discover an IP address which uses such credential while at the same time reviewing network traffic with wiresharkRecreate the credential, however this time as an external CyberArk credentialDiscover the same CI while at the same time reviewing network traffic with wireshark and compare the captures, instance credential vs external credentialWorkaroundSet CyberArk credential policy IDs to 'SNMPv3' and 'SNMPv3PrivacyKey' respectively.Related Problem: PRB1409851