As a quick test, can you Add some of these failing servers into BSA with their FQDN. Run your Discover and Compliance jobs against those servers and see if that makes any difference.
the syntax in the users.local is not correct - * will not work - you can do:
i would fix that and re-run.
I think you misread his text, he said:
users.local setting is set to BLAdmins:* rw,map=administrator
That syntax is correct.
oh yeah - there should be some KAs on the ssl_connect issue...
Justin I would recommend doing a search for "SSL_connect" and see if you can find a similar problem to what you are encountering. I would also open a Helpdesk ticket for additional support.
Did this get resolved?
If so, please can you update the discussion thread with details so that is can be marked as answered.
Thanks & Regards,
Jim (Forum Manager/Facilitator)
Hello Bill -
For a newbie to BL and compliance in general -
Can you point to to a KB article on what is DISA compliance?
"Compliance" is a term that gets tossed around a lot and has different meanings to different people. In general it means, is your server compliant? Has it been hardened to a certain security standard?
There are many server industry security standards; CIS, DISA, HIPAA, PCI, SOX, etc. DISA is the security standard followed by the government and military. You can find a list of DISA STIGs here:
In BSA you can take any industry standard and create a Component Template that can do analysis and remediation automatically. This is a powerful feature of BSA.
I created some DISA STIGs earlier this year and they were added as user contrib content here:
We also supply out of the box Compliance Templates (that you can download and install) for different standards, but they are not up to date. But you can use them as a guideline to update them to the latest version.
Most of these policies have been nicely updated in 8.5-8.7.