This custom action needs to be added at step level in a job to register security scan resutls in ServiceNow instance.
- credentials (Devops integration token of a GitHub tool created in ServiceNow DevOps or username and password for a ServiceNow devops integration user)
- instance URL for your ServiceNow dev, test, prod, etc. environments
- tool_id of your GitHub tool created in ServiceNow DevOps
On GitHub, go in your organization settings or repository settings, click on the Secrets > Actions and create a new secret.
Create secrets called For token based authentication which is available from v3.0.0, create secrets called
SN_DEVOPS_INTEGRATION_TOKEN
required for token based authenticationSN_INSTANCE_URL
your ServiceNow instance URL, for example https://test.service-now.comSN_ORCHESTRATION_TOOL_ID
only the sys_id is required for the GitHub tool created in your ServiceNow instance
For basic authentication , create secrets called
SN_INSTANCE_URL
your ServiceNow instance URL, for example https://test.service-now.comSN_DEVOPS_USER
SN_DEVOPS_PASSWORD
SN_ORCHESTRATION_TOOL_ID
only the sys_id is required for the GitHub tool created in your ServiceNow instance
Step 3: Identify upstream job that must complete successfully before the job using this custom action will run
Use needs to configure the identified upstream job. See test.yml for usage.
ServiceNowSecurityScanResults:
# type of machine to run the job on
runs-on: ubuntu-latest
name: ServiceNow Security Scan Results
steps:
- name: ServiceNow DevOps Security Results
uses: ServiceNow/servicenow-devops-security-result@v3.1.0
with:
# DevOps Integration Token of GitHub tool created in ServiceNow instance for token based authentication.
devops-integration-token: ${{ secrets.SN_DEVOPS_INTEGRATION_TOKEN }}
# ServiceNow Instance URL
instance-url: ${{ secrets.SN_INSTANCE_URL }}
# Orchestration Tool Id
tool-id: ${{ secrets.SN_ORCHESTRATION_TOOL_ID }}
# GitHub Context
context-github: ${{ toJSON(github) }}
# Display Name of the Job
job-name: 'ServiceNow Security Scan Results'
security-result-attributes: '{"scanner": "Veracode", "applicationName": "", "buildVersion": "", "securityToolId": ""}'
# scanner: Scanning tool and is required e.g. Veracode.
# applicationName: Name of your Veracode application and is required. This attribute is applicable only for Veracode.
# buildVersion: Veracode Scan name / build version and is optional. This attribute is applicable only for Veracode.
# securityToolId: Security tool onboarded in ServiceNow (sys_id of the onboarded security tool) and is optional.
ServiceNowSecurityScanResults:
# type of machine to run the job on
runs-on: ubuntu-latest
name: ServiceNow Security Scan Results
steps:
- name: ServiceNow DevOps Security Results
uses: ServiceNow/servicenow-devops-security-result@v3.1.0
with:
# DevOps Integration Token of GitHub tool created in ServiceNow instance for token based authentication.
devops-integration-token: ${{ secrets.SN_DEVOPS_INTEGRATION_TOKEN }}
# ServiceNow Instance URL
instance-url: ${{ secrets.SN_INSTANCE_URL }}
# Orchestration Tool Id
tool-id: ${{ secrets.SN_ORCHESTRATION_TOOL_ID }}
# GitHub Context
context-github: ${{ toJSON(github) }}
# Display Name of the Job
job-name: 'ServiceNow Security Scan Results'
security-result-attributes: '{"scanner": "Checkmarx One", "projectName": "", "projectId": "", "scanId": "", "securityToolId": ""}'
# scanner: Scanning tool and is required e.g. Checkmarx One.
# projectName/projectId: Name/Id of your Checkmarx One project and is required. This attribute is applicable only for Checkmarx One.
# scanId: Checkmarx One scan id and is optional. This attribute is applicable only for Checkmarx One.
# securityToolId: Security tool onboarded in ServiceNow (sys_id of the onboarded security tool) and is optional.
ServiceNowSecurityScanResults:
# type of machine to run the job on
runs-on: ubuntu-latest
name: ServiceNow Security Scan Results
steps:
- name: ServiceNow DevOps Security Results
uses: ServiceNow/servicenow-devops-security-result@v3.1.0
with:
# DevOps Integration Token of GitHub tool created in ServiceNow instance for token based authentication.
devops-integration-token: ${{ secrets.SN_DEVOPS_INTEGRATION_TOKEN }}
# ServiceNow Instance URL
instance-url: ${{ secrets.SN_INSTANCE_URL }}
# Orchestration Tool Id
tool-id: ${{ secrets.SN_ORCHESTRATION_TOOL_ID }}
# GitHub Context
context-github: ${{ toJSON(github) }}
# Display Name of the Job
job-name: 'ServiceNow Security Scan Results'
security-result-attributes: '{"scanner": "Checkmarx SAST", "projectId": "", "securityToolId": ""}'
# scanner: Scanning tool and is required e.g. Checkmarx SAST.
# projectId: Id of your Checkmarx SAST project and is required. This attribute is applicable only for Checkmarx SAST.
# securityToolId: Security tool onboarded in ServiceNow (sys_id of the onboarded security tool) and is optional.
devops-integration-token: ${{ secrets.SN_DEVOPS_INTEGRATION_TOKEN }}
ServiceNowSecurityScanResults:
# type of machine to run the job on
runs-on: ubuntu-latest
name: ServiceNow Security Scan Results
steps:
- name: ServiceNow DevOps Security Results
uses: ServiceNow/servicenow-devops-security-result@v3.1.0
with:
# Devops Integration User Name
devops-integration-user-name: ${{ secrets.SN_DEVOPS_USER }}
# Devops Integration User Password
devops-integration-user-password: ${{ secrets.SN_DEVOPS_PASSWORD }}
# ServiceNow Instance URL
instance-url: ${{ secrets.SN_INSTANCE_URL }}
# Orchestration Tool Id
tool-id: ${{ secrets.SN_ORCHESTRATION_TOOL_ID }}
# GitHub Context
context-github: ${{ toJSON(github) }}
# Display Name of the Job
job-name: 'ServiceNow Security Scan Results'
security-result-attributes: '{"scanner": "Veracode", "applicationName": "", "buildVersion": "", "securityToolId": ""}'
# scanner: Scanning tool and is required e.g. Veracode.
# applicationName: Name of your Veracode application and is required. This attribute is applicable only for Veracode.
# buildVersion: Veracode Scan name / build version and is optional. This attribute is applicable only for Veracode.
# securityToolId: Security tool onboarded in ServiceNow (sys_id of the onboarded security tool) and is optional.
ServiceNowSecurityScanResults:
# type of machine to run the job on
runs-on: ubuntu-latest
name: ServiceNow Security Scan Results
steps:
- name: ServiceNow DevOps Security Results
uses: ServiceNow/servicenow-devops-security-result@v3.1.0
with:
# Devops Integration User Name
devops-integration-user-name: ${{ secrets.SN_DEVOPS_USER }}
# Devops Integration User Password
devops-integration-user-password: ${{ secrets.SN_DEVOPS_PASSWORD }}
# ServiceNow Instance URL
instance-url: ${{ secrets.SN_INSTANCE_URL }}
# Orchestration Tool Id
tool-id: ${{ secrets.SN_ORCHESTRATION_TOOL_ID }}
# GitHub Context
context-github: ${{ toJSON(github) }}
# Display Name of the Job
job-name: 'ServiceNow Security Scan Results'
security-result-attributes: '{"scanner": "Checkmarx One", "projectName": "", "projectId": "", "scanId": "", "securityToolId": ""}'
# scanner: Scanning tool and is required e.g. Checkmarx One.
# projectName/projectId: Name/Id of your Checkmarx One project and is required. This attribute is applicable only for Checkmarx One.
# scanId: Checkmarx One scan id and is optional. This attribute is applicable only for Checkmarx One.
# securityToolId: Security tool onboarded in ServiceNow (sys_id of the onboarded security tool) and is optional.
ServiceNowSecurityScanResults:
# type of machine to run the job on
runs-on: ubuntu-latest
name: ServiceNow Security Scan Results
steps:
- name: ServiceNow DevOps Security Results
uses: ServiceNow/servicenow-devops-security-result@v3.1.0
with:
# Devops Integration User Name
devops-integration-user-name: ${{ secrets.SN_DEVOPS_USER }}
# Devops Integration User Password
devops-integration-user-password: ${{ secrets.SN_DEVOPS_PASSWORD }}
# ServiceNow Instance URL
instance-url: ${{ secrets.SN_INSTANCE_URL }}
# Orchestration Tool Id
tool-id: ${{ secrets.SN_ORCHESTRATION_TOOL_ID }}
# GitHub Context
context-github: ${{ toJSON(github) }}
# Display Name of the Job
job-name: 'ServiceNow Security Scan Results'
security-result-attributes: '{"scanner": "Checkmarx SAST", "projectId": "", "securityToolId": ""}'
# scanner: Scanning tool and is required e.g. Checkmarx SAST.
# projectId: Id of your Checkmarx SAST project and is required. This attribute is applicable only for Checkmarx SAST.
# securityToolId: Security tool onboarded in ServiceNow (sys_id of the onboarded security tool) and is optional.
The values for secrets should be setup in Step 1. Secrets should be created in Step 2.
Optional DevOps Integration Token of GitHub tool created in ServiceNow instance for token based authentication.
Optional DevOps Integration Username to ServiceNow instance.
Optional DevOps Integration User Password to ServiceNow instance.
Required URL of ServiceNow instance to create change in ServiceNow.
Required Orchestration Tool Id for GitHub created in ServiceNow DevOps
Required Github context contains information about the workflow run details.
Required Security Result Attributes
{
"scanner": "", # Scanning tool and is required e.g. Veracode or Checkmarx One or Checkmarx SAST
"applicationName": "", # Name of your Veracode application and is required. This attribute is applicable only for Veracode.
"buildVersion": "", # Veracode Scan name / build version and is optional. This attribute is applicable only for Veracode.
"projectName": "", # Name of your Checkmarx One project and is required. This attribute is applicable only for Checkmarx One.
"projectId": "", # Id of your Checkmarx One / Checkmarx SAST project and is required. This attribute is applicable only for Checkmarx One and Checkmarx SAST.
"scanId": "", # Checkmarx One scan id and is optional. This attribute is applicable only for Checkmarx One.
"securityToolId": "" # Security tool onboarded in ServiceNow (sys_id of the onboarded security tool) and is optional.
}
No outputs produced.
ServiceNow customers may request support through the Now Support (HI) portal.
Initially, ServiceNow product management and engineering representatives will own governance of these integrations to ensure consistency with roadmap direction. In the longer term, we hope that contributors from customers and our community developers will help to guide prioritization and maintenance of these integrations. At that point, this governance model can be updated to reflect a broader pool of contributors and maintainers.