I've sent an email off to the Signature Update team and they will have to correct this in the next CSPM update.
In the meantime can you try to use the 3.0(4)S23 entry?
If this works, then use the 3.0(4)S23 entry as a workaround until CSPM can be updated with the correct entry. There should be no functional difference in what CSPM can configure between 3.0(4)S23 and 3.0(5)S23.
NOTE: Originally S23 was going to be released as a 3.0(4)S23, but then other bug fixes, and ssh were added requiring us to increaes the number to 3.0(5)S23.
I had the same problem with a different version but I resolved it by installing the CSPM update first, using the Signature Update Wizard (not selecting any version on the first screen - click next - check on "Load CSPM Sensor Signature Update File" - browse for the "html" folder of your extracted update).
Then run the update ont he IDSM.
Now run the Signature Update Wizard again. At this time the correct version should populate. Highlight it and click "Query Sensor".
I have had a similar problem with what you just described before however, this is not the same. This one is a direct result of the signature not being in the data file. I have selected 3.0(4)S23 IDSM in the CSPM for the time being (as suggested) and will wait for the next release.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :