Compliance Reports and RegEx Doc? Also, RegEx/Compliance rule matching for network devices?

Just search for regular expression cheat sheet and find one that you like, they're all pretty good.  

Many STIG compliance rules don't "anchor" enough stuff, which means defining where the search starts, like at a beginning of a line, and where it ends, like at EOL.   A simple string match, instead of a regular expression match, cannot anchor at all really, it just looks for the text on a line.

Common regex anchors include the "^", also known as carat or some call it a "ref", which can anchor things at the beginning of a line, and the "$" which anchors things to the end of a line.  However, I've notice in SW that "$" tends to work great when you are testing a rule, but not when you implement it.  Others have said this might be specific to config types, such as Cisco.   If "$" doesn't work, use "\r" instead, which works for me really well most times (when not testing that is!)...

So, to do a good check for a switchport on vlan 1, you would do a regex search for "^switchport access vlan 1\r".

Of course on some devices, with this being the "default", it wouldn't actually show up in the config.   In which case you might need to look for a switchport that doesn't have anything set at all.   ie: something that isn't a trunk, but doesn't have a "switchport access" command on it.

Thank you for this response! I would've responded sooner but THWACK is god awful slow during core hours and I've been quite busy on SolarWinds as it is. I will definitely test using the carat and "\r" for these types of instances, but oddly enough, I've tried many characters to isolate VLAN 1. It turns out that the apostrophe on both sides of "1" actually did the trick while making the string type RegEx. SolarWinds is such a frustrating app to work with, I'm sure you can sympathize lol.