Add comprehensive security scanning workflows for Java agent#127
Closed
Add comprehensive security scanning workflows for Java agent#127
Conversation
This commit implements complete security scanning for aws-xray-java-agent: - CodeQL analysis for Java code security scanning with security-extended queries - Runs on PR/push and weekly schedule - Adapted for Java agent multi-module Gradle project structure - Scans published Maven artifacts from Maven Central twice daily - Monitors agent and plugin modules separately - Detects new vulnerabilities in existing published artifacts - Focuses on HIGH/CRITICAL severity issues requiring immediate action - Generates actionable summary reports with error handling - Special focus on key dependencies: X-Ray SDK Core and OpenTelemetry Java Agent - Comprehensive coverage: source code, dependencies, published Maven artifacts - Java-focused: OWASP Dependency Check, SpotBugs, FindSecBugs - Agent-specific: Multi-module scanning, OpenTelemetry integration awareness - Security-focused: commit hashes, proper permissions, categorized results - Production-ready: scans actual published artifacts from Maven Central - Robust: proper timeouts, error handling, and job dependencies - Actionable: clear reporting and GitHub Security tab integration Addresses the critical security gap where aws-xray-java-agent had no automated security scanning despite being critical infrastructure used in production.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit implements complete security scanning for aws-xray-java-agent:
CodeQL analysis for Java code security scanning with security-extended queries
Runs on PR/push and weekly schedule
Adapted for Java agent multi-module Gradle project structure
Scans published Maven artifacts from Maven Central twice daily
Monitors agent and plugin modules separately
Detects new vulnerabilities in existing published artifacts
Focuses on HIGH/CRITICAL severity issues requiring immediate action
Generates actionable summary reports with error handling
Special focus on key dependencies: X-Ray SDK Core and OpenTelemetry Java Agent
Comprehensive coverage: source code, dependencies, published Maven artifacts
Java-focused: OWASP Dependency Check, SpotBugs, FindSecBugs
Agent-specific: Multi-module scanning, OpenTelemetry integration awareness
Security-focused: commit hashes, proper permissions, categorized results
Production-ready: scans actual published artifacts from Maven Central
Robust: proper timeouts, error handling, and job dependencies
Actionable: clear reporting and GitHub Security tab integration
Addresses the critical security gap where aws-xray-java-agent had no automated security scanning despite being critical infrastructure used in production.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.