From 6ecba780075e75d7f662369a4a76cc12af441ecb Mon Sep 17 00:00:00 2001 From: Dorian Date: Fri, 4 Jun 2021 11:14:49 -0700 Subject: [PATCH 1/2] Added use cases --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index a82c2ba..5c91c5e 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,12 @@ Execute Instance Scans and get progress and results of runs. +# Use Case +1. Scoped Applications + a. If you have a scoped application linked to source control, you can configure Github Actions to trigger when a commit is added from ServiceNow. You would either set it up to just trigger on the scoped application using `appScopeSysIds`or after you have manually run a set of suites on the scoped application, you can utilize the `comboSysId` +2. Triggered remotely through Github APIs + b. Another way to utilize this when you don't have code linked to source control, would be to create business rules and REST messages (or flows and rest steps) to trigger the scans. The example that comes to mind is if you want to trigger this without writing code on the target instance. If that is the case, you are going to run into issues around IP listing and having the checks / suite sys_ids known. Although it is possible, it seems overkill for this use case because you could just trigger this through internal ServiceNow APIs + # Usage ## Step 1: Prepare values for setting up your variables for Actions - credentials (username and password for a service account) From 3055769af0d1b3fcea8fb12ddb1642a8562855e9 Mon Sep 17 00:00:00 2001 From: Dorian Date: Fri, 4 Jun 2021 11:15:29 -0700 Subject: [PATCH 2/2] formatting use cases --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5c91c5e..a52a33d 100644 --- a/README.md +++ b/README.md @@ -4,9 +4,12 @@ Execute Instance Scans and get progress and results of runs. # Use Case 1. Scoped Applications - a. If you have a scoped application linked to source control, you can configure Github Actions to trigger when a commit is added from ServiceNow. You would either set it up to just trigger on the scoped application using `appScopeSysIds`or after you have manually run a set of suites on the scoped application, you can utilize the `comboSysId` + + - If you have a scoped application linked to source control, you can configure Github Actions to trigger when a commit is added from ServiceNow. You would either set it up to just trigger on the scoped application using `appScopeSysIds`or after you have manually run a set of suites on the scoped application, you can utilize the `comboSysId` + 2. Triggered remotely through Github APIs - b. Another way to utilize this when you don't have code linked to source control, would be to create business rules and REST messages (or flows and rest steps) to trigger the scans. The example that comes to mind is if you want to trigger this without writing code on the target instance. If that is the case, you are going to run into issues around IP listing and having the checks / suite sys_ids known. Although it is possible, it seems overkill for this use case because you could just trigger this through internal ServiceNow APIs + + - Another way to utilize this when you don't have code linked to source control, would be to create business rules and REST messages (or flows and rest steps) to trigger the scans. The example that comes to mind is if you want to trigger this without writing code on the target instance. If that is the case, you are going to run into issues around IP listing and having the checks / suite sys_ids known. Although it is possible, it seems overkill for this use case because you could just trigger this through internal ServiceNow APIs # Usage ## Step 1: Prepare values for setting up your variables for Actions