Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We're experiencing authentication/authorization issues from IDSMC 2.0.1 and ACS 3.3. It worked fine until we upgraded from IDSMC 1.2.3 to 2.0.1. We've been through the release notes, and Employing ACS with IDSMC "Appendix C".ACS 3.3 simply reports "B...
We went back and tested it in our lab and got it working with Network Devices Groups and with individual devices and users. For some reason, we still have problems in our production implementation that we are trying to figure out. The error message ...
Ryan,Thanks!! 100% perfect!! Generated a new server cert. and then did the discovery with each sensor and now we're back in business having successfully tested S138 yesterday.Key were those two steps. Gen. new cert. and then sync up sensors with it. ...
Scott,any news on this; we've had a TAC case open for about a month now and so far no results. Is the course of action to upgrade to MC 2.01 right now?We are on MC 1.2.3 and can't do any upgrades; all our patches are currently. What happpened? Plea...
Jason, did you receive any tip from TAC on fixing this issue; we're having the same problem as well. I upgrades all our IDS devices to the latest patch and our MC version is 1.2.3 , VMS 2.2 with all updated patches installed. We can update our NIDS ...
We are having the exact same problem. But I think ours broke around S132 sig. update.Queries from IDSMC to the NIDS work but pushes to the NIDS for new sig. updates don't work. Security Monitor is fine. The IDSMC actually recognizes the new sig updat...
