Skip to content

feat: add JWT OAuth capability for ServiceNow integration, to address customer PFRs; fix: status of Incidents/Security Incidents in ServiceNow to remain as-is if no mapping exist, instead of defaulting to a particular 'In Progress' or 'Analysis' #230

feat: add JWT OAuth capability for ServiceNow integration, to address customer PFRs; fix: status of Incidents/Security Incidents in ServiceNow to remain as-is if no mapping exist, instead of defaulting to a particular 'In Progress' or 'Analysis'

feat: add JWT OAuth capability for ServiceNow integration, to address customer PFRs; fix: status of Incidents/Security Incidents in ServiceNow to remain as-is if no mapping exist, instead of defaulting to a particular 'In Progress' or 'Analysis' #230

Triggered via pull request November 26, 2025 02:15
@nshalabhnshalabh
synchronize #47
nshalabh:main
Status Failure
Total duration 4m 14s
Artifacts 2

security-and-tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
cdk-nag
Process completed with exit code 1.
security-scan
Unexpected input(s) 'grype-version', valid inputs are ['path', 'file', 'image', 'registry-username', 'registry-password', 'format', 'github-token', 'artifact-name', 'output-file', 'syft-version', 'dependency-snapshot', 'upload-artifact', 'upload-artifact-retention', 'upload-release-assets', 'config']

Artifacts

Produced during runtime
Name Size Digest
sample-aws-security-incident-response-integrations-security-scan-2.spdx.json
2.44 KB
sha256:d7f0fdd0bbf8fd7885d4d2cf0b83d5f1adea4e112d277227820bc66effa3cf53
sample-aws-security-incident-response-integrations-security-scan.spdx.json
2.44 KB
sha256:53696b615a9af2c63fa562719df43f548c65b380914f000195f816dc054d7fe5