Fn microsoft security graph 1.1.1

[lmahoney1]

Description

duplicate of PR #67 I made 67 with my other github account, I am supposed to be using this github account going forward.

Changed the variable the CTS uses to determine if a result from urlscan.io is malicious or not.

Motivation and Context

Fixes #66

How Has This Been Tested?

Submitted the url mentioned in the issue and the CTS returns a hit.

Checklist:

• [x] I have added a Signed-off-by
• [x] Either no new documentation is required by this change, OR I added new documentation
• [x] Either no new tests are required by this change, OR I added new tests
• [x] I have run pep8 and pylint. I have cleaned up all valid errors and warnings in code I have added or modified. These tools may generate false positives. Don't be worried about ignoring some errors or warnings. The goal is clean, consistent, and readable code.

Signed-off-by: Liam Mahoney lmahoney@oshkoshcorp.com

[annmarien]

Hi Liam

We have added scope in the 1.2.0 release of fn_microsoft_security_graph now on he App Exchange. Thanks for your input.