You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,9 @@ Deploys two Lambda functions:
41
41
* Deploys an additional Jira lambda function and a Step function for orchestration, triggered by an EventBridge rule.
42
42
* Non-suppressed findings with severity above a threshold result in ticket creation and workflow status update from `NEW` to `NOTIFIED`.
43
43
***ProductName Filtering**: You can optionally filter which AWS product findings create Jira tickets using `jira_integration.include_product_names` (default = `[]`, meaning all products). For example, set to `["Security Hub"]` to create tickets only for Security Hub findings, or `["Inspector"]` for Inspector findings only. Common values: `"Security Hub"`, `"Inspector"`, `"GuardDuty"`, `"Macie"`. The filtering is implemented at the Step Function level for optimal performance.
44
-
* Auto-closing can be activated with `jira_integration.autoclose_enabled` (default = false). Using the issue number in the finding note, the function transitions issues using `jira_integration.autoclose_transition_name` and `jira_integration.autoclose_comment`. Criteria for being forwarded for automatic ticket closure are:
44
+
* Auto-closing can be activated with `jira_integration.autoclose_enabled` (default = false). Using the issue number in the finding note, the function transitions issues using `jira_integration.autoclose_transition_name` and `jira_integration.autoclose_comment`.
45
+
***Intermediate Transition**: Optionally specify `jira_integration.include_intermediate_transition` to transition the ticket through an intermediate status before closing it. This is useful for Jira workflows that require tickets to pass through specific statuses (e.g., "Review", "In Progress") before reaching the final closed state. If not specified, tickets are closed directly using `autoclose_transition_name`.
46
+
* Criteria for being forwarded for automatic ticket closure are:
45
47
* Workflow Status "RESOLVED"
46
48
* Workflow Status "NOTIFIED" and one of:
47
49
* Record State "ARCHIVED"
@@ -145,7 +147,7 @@ A lambda layer provides aws-lambda-powertools. To have these dependencies locall
| <aname="input_jira_eventbridge_iam_role_name"></a> [jira\_eventbridge\_iam\_role\_name](#input\_jira\_eventbridge\_iam\_role\_name)| The name of the role which will be assumed by EventBridge rules for Jira integration |`string`|`"SecurityHubFindingsManagerJiraEventBridge"`| no |
| <aname="input_jira_step_function_iam_role_name"></a> [jira\_step\_function\_iam\_role\_name](#input\_jira\_step\_function\_iam\_role\_name)| The name of the role which will be assumed by AWS Step Function for Jira integration |`string`|`"SecurityHubFindingsManagerJiraStepFunction"`| no |
150
152
| <aname="input_lambda_runtime"></a> [lambda\_runtime](#input\_lambda\_runtime)| The version of Python to use for the Lambda functions |`string`|`"python3.12"`| no |
151
153
| <aname="input_rules_filepath"></a> [rules\_filepath](#input\_rules\_filepath)| Pathname to the file that stores the manager rules |`string`|`""`| no |
0 commit comments