I presume you were thinking about foreach in compliance rules, this is to i.e. list all processes running then check if process of interest is running there as well. You could also check so you can get familiar more with compliance if you have not already:
regarding samples for complicated compliance I don't have any but maybe someone else can share this with you.
it's a loop construct. just like it is in nsh (for example). it iterates over a list.
so you can do like
foreach <output from an extended object>
if value1 as string = foo
value2 as string = blah
thnx bill & Davorin.
is there any documentation regarding this to explore more?
can u provide me any sample complicated compliance/customized compliance/use case to understand deeply?
1 of 1 people found this helpful
install the compliance content that ships w/ the product - DISA STIG, SOX, PCI, etc. there will be rules in there of varying complexity.
i'm not sure if documentation will help you here - these are basic logical constructs and what you use will determine on what you are trying to determine 'about' the part(s) you are operating on.