Use of Applicability Fixlet

Hi Guys,

I was creating Custom SCM checks for a platform which does not have OOB CIS checks available.

I created a new site of a random OS using SCM Checklist Wizard and after creating the site, I started creating checks via SCM Wizard.

After checks were created, I tried fetching the compliance report (after running the environment scan and testing all the checks) and I got this error:

I think this is because of the applicability fixlet not being relevant on these 4 endpoints, but I might be wrong. I have changed the relevance of the applicability fixlet. I’ll try fetching the reports again when the data is imported (Not allowed to import manually) and check.

Might there be any other reason for this failure?

I'm not sure whether there are other reasons for the issue, but not having an Applicability Fixlet, or it not being relevant, is definitely one cause for this.

The Applicability Fixlet(s) are what make a computer relevant to a checklist, or to some part of a checklist. Even within a checklist site, a computer might be applicable to some portions of the checklist based on installed software or configured services...applicability checks allow things like "not failing ten checks for Office configuration, on a machine that doesn't have Office installed to begin with".

You must create these using the wizards, there is metadata on the fixlets that match up checks to the applicability for those checks.

It's been a while since I looked at this and I think there are a few different wizards that could be used, can you tell me which wizards you're using to build the checklist? Is it an XCCDF import or copy of existing checklist or something else?

Hi Jason,

I used the first one to create the site, and the second one to create the checks. when I created the site, the applicability fixlet was already a part of it

image