I noticed the spaces on the lines following the crypto keyword. Thats why I created the other 2 expressions. The other 2 expressions basically capture all of the lines between the 2 character sets that surround the ((.|\n)*). The | (pipe symbol) acts like a Boolean 'OR' and will match anything before or after it. So the before is a .(DOT) and the after is a line feed (\n) and it will capture anything until it reaches the last part of the expression...
It looks like the RegEx engine in NCM is basically not operable I can get these expressions to work in other RegEx engines just not the one in NCM. Did this get fixed in the latest Orion version? We are currently running 11.5.1.(no hot fixes) and our NCM is version 7.3.2....