What is a practical way GAS results can be connected to ongoing work items?

• A. Convert alerts into commits automatically without review.
• B. Archive alerts without action.
• C. Link GAS alerts to existing issues or create new issues in issue trackers via APIs or webhooks.
• D. Use GAS results only as read-only reports with no integration.

Answer: (C)

Connecting GAS results to ongoing work items by linking alerts to existing issues or creating new ones in your issue tracker via APIs or webhooks makes the findings actionable and trackable within the team's normal workflow. When a vulnerability or misconfiguration is detected, automatically creating or associating an issue provides a clear owner, priority, and remediation steps, and ties the security finding to the development work already being tracked. This approach preserves traceability from the alert through triage, assignment, remediation, and verification, and it enables seamless visibility in dashboards and sprint planning. Automating the process with APIs or webhooks reduces manual effort, avoids losing context, and ensures that security work is not forgotten or left as a standalone report. In contrast, converting alerts into commits without review, archiving alerts without action, or using results only as read-only reports fail to integrate the findings into the actual workflow where developers can address them.