topic Re: Firepower 4125 - how to resolve NESSUS plugin ID 57582 in Network Security

Firepower 4125 - how to resolve NESSUS plugin ID 57582

robert-l-swafford2-ctr — Sat, 09 Aug 2025 06:54:46 GMT

Our current ACAS scans are showing plugin 57582, SSL Self-Signed Certificate on Firepower 4125 with FTD devices.

The Firepower 4125 is running version 7.4.2.2

I am asking if there is a correct method to resolve plugin 57582. It my understand the FXOS, FMC and FTP software versions are the newest we can apply to these devices. Any detailed support on how to resolve this issue on this model device will be greatly appreciated.

Re: Firepower 4125 - how to resolve NESSUS plugin ID 57582

Mark Elsen — Sat, 09 Aug 2025 10:51:52 GMT

- @robert-l-swafford2-ctr If you are confronted with a security issue on the particular platform and you are using latest software , then contact TAC. Or report the problem to PSIRT (product security issue response team) : psirt@cisco.com

Re: Firepower 4125 - how to resolve NESSUS plugin ID 57582

MHM Cisco World — Sat, 09 Aug 2025 10:57:13 GMT

can you share screenshot
FCM > device > cert > cert status

MHM

Re: Firepower 4125 - how to resolve NESSUS plugin ID 57582

robert-l-swafford2-ctr — Sat, 09 Aug 2025 11:16:08 GMT

This is what I see MHM Cisco World.

These devices are Firepower 4125. We did generate and put certificates directly on the chassis manager IP in the past.

Re: Firepower 4125 - how to resolve NESSUS plugin ID 57582

MHM Cisco World — Sat, 09 Aug 2025 11:41:33 GMT

> show ssl-certificate

> show crypto ca certificates

check cert in above show, subject name and issuer is cisco

if that what you see it default self-singed cisco cert add to FTD

MHM

Re: Firepower 4125 - how to resolve NESSUS plugin ID 57582

Marvin Rhoads — Mon, 11 Aug 2025 04:39:07 GMT

There are potentially multiple certificates in use on a given Firepower device:

1. An SSL VPN certificate for that service. Per your FMC screen shot, there are no such certificates in your case.

2. The certificate for Firepower Chassis Manager. This would be added and configured via the FCM UI or, optionally, via FXOS.

3. The sftunnel certificate used to secure communications between the device and its managing FMC.

Please provide more details of the certificate you are seeing and we can give better guidance regarding how (or if) it can be mitigated.

Re: Firepower 4125 - how to resolve NESSUS plugin ID 57582

robert-l-swafford2-ctr — Wed, 17 Sep 2025 07:43:42 GMT

I want to thank each of your for the support. The open findings have been resolved and I appreciate this forum for the support.