enterprise-cmcs/Security Hub Visibility

Syncs AWS Security Hub findings with Jira issues

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
jira-base-uriURI of the target Jira API endpointno
jira-usernameJira username that will be the reporter of issues created when syncingyes
jira-tokenJira token corresponding to the jira-username input with permission to manage issues for the target Jira projectyes
jira-project-keyJira project key where issues will be createdyes
jira-ignore-statusesComma-separated list of Jira issue statuses that will be ignore when syncingno
jira-assigneethe assignee accountId to assign the Jira ticket tono
jira-transition-mapJSON string of Jira statuses and transition pairs to traverse when closing an issue e.g "To Do:Start Progress, In Progress:Done"no
jira-custom-fieldsJSON string of Jira custom field keys/values, e.g. { "customfield_14117": "example-value" }
jira-watchersComma separated list of Emails for Atlassion Jira and User EUA IDs for Enterprise Jira no""
jira-add-labelsComma separated list of labels to add in newly created tickets""
aws-regionTarget AWS region for Security Hub findingsno
aws-severitiesComma-separated list of Security Hub finding severities to syncno
auto-closea boolean to support auto closing for issueno
dry-run-test-dataa boolean to support dry run of tickets creationno
jira-link-id-on-creationthe new created issue will be linked to this link idno
jira-link-type-on-creationthis defines the relation of the new issue with feature issue specified and default value for this is 'Relates'no
jira-link-direction-on-creationthis variable is to specify the direction of linked issue either inward or outwardno
jira-link-id-on-closurethe closed issue will be linked to this link idno
jira-link-type-on-closurethis defines the relation of the closed issue with feature issue specified and default value for this is 'Relates'no
jira-link-direction-on-closurethis variable is to specify the direction of linked issue either inward or outwardno
include-all-productsa boolean to enable findings from other productsno
skip-productscomma separated list of product names for those the findings should be skippedno
jira-duedate-fieldThe Jira field ID to use for setting the due date (e.g., duedate, customfield_xxxxx). Defaults to duedate.no""
due-date-criticalNumber of days within which a Jira issue should be due for critical findingsno15
due-date-highNumber of days within which a Jira issue should be due for high findingsno30
due-date-moderateNumber of days within which a Jira issue should be due for moderate findingsno90
due-date-lowNumber of days within which a Jira issue should be due for low findingsno365
jira-labels-configThis variable is to specify stringified labels configno
jira-consolidate-ticketsTrue/False value to enable/disable the consolidation of ticketsno
test-findings-dataJSON string of findings listno
jira-api-versionJira API version to use (v2 or v3). v3 uses ADF format for descriptions/comments, v2 uses plain text.no2
namedescription
updatesList of urls of created issues
totalcount of updates
createdcount of created issues
closedcount of closed issues
create-issue-errorscount of errors encountered during Jira issue creation
link-issue-errors-on-creationcount of errors encountered during Jira issue linking on creation
link-issue-errors-on-closurecount of errors encountered during Jira issue linking on closure
jqlthe jql query for new updates