Defender errors when running against DLP policies with \. And \T syntax

[ahuynhMITRE]

🐛 Summary

What's wrong? Please be specific.

An agency has noted that when running the Invoke-Scuba command the PowerShell failed with no results. Attached below are the errors in the PowerShell terminal and were not specific to DLP however through additional investigation and testing two of the DLP compliance policies (attached) contained the following syntax “.” and “\T” causing the error. Once the two policies were removed/renamed the script ran successfully.

To reproduce

Steps to reproduce the behavior:

1. Create DLP compliance policies including the syntax included in the attachments and linked above
2. Run ScubaGear

Expected behavior

Expectation: ScubaGear to run and capture the DLP compliant policies for the defender product

Any helpful log output or screenshots

PowerShell Error:

Syntax from Provider Export:

[schrolla]

This looks like another occurrence of escaping causing issues in the JSON. I think we need a more comprehensive solution to escaping to prevent the more general case than what was done in #822. Ideally, creating a general purpose method for escaping, passing all strings thru it, and holding that. It should handle general presence of backslashes, unicode codes, and other control characters.