Github Audit log feedbacks

[jtan-brex]

Select Topic Area

Product Feedback

Body

Would like to share some feedback about github audit logs, also curious to hear community's takes on this as well.

Stemmed from the recent NPM supply chain compromise, it'd be great if github audit logs include below information

1. Git push events to include pushed branch name
2. Workflow logs: ability to have more Workflow hosted runner logs - today we could download specific workflow logs ad-hoc instead of fetched via audit logs. would be useful to have egress DNS requests for example.

Thanks!
Jiawei

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[alireza-iranpour85]

This is excellent, timely feedback, especially considering the recent focus on supply chain security following the NPM compromise. These enhancements would be a massive step forward for enterprise security and incident response.

I completely agree with your two points, and I'd love to emphasize why they are so critical for security teams and compliance:

---

1. Audit Logs for Git Push Events (Including Branch Name)

This is absolutely crucial. Currently, the lack of branch-level detail in the audit log for a git push creates a significant blind spot during security investigations.

Current Gap | Required Security Enhancement -- | -- Audit Log: User X pushed code to repository Y. | Audit Log MUST include: User X pushed to branch Z in repository Y.

Why this matters: When an incident requires rollback or isolation, knowing exactly which branch was targeted is essential for triage and containment. Without the branch name, security teams are forced to manually sift through Git history or rely on verbose third-party logs, which significantly delays the response time—a critical failure point in high-stakes incidents.

---

2. Deeper Workflow Logs (Especially Egress Monitoring)

The ability to proactively monitor and audit hosted runner behavior is non-negotiable for modern CI/CD security. Relying on ad-hoc download of run logs is too slow and inefficient for compliance and security monitoring.

Your suggestion about Egress DNS Requests is a perfect example of the telemetry we need.

The Threat Scenario: A compromised or malicious workflow step could attempt to exfiltrate secrets or proprietary data by connecting to an external C2 (Command and Control) server.

• If we have Egress DNS/Network Logs: We can immediately detect anomalous network calls from the runner and automatically flag them as a potential compromise, cutting off the attack before data leaves the system.

• Without these logs in the audit trail: The malicious activity is completely invisible until after the fact, making detection a reactive exercise rather than a proactive one.

---

Summary and Call to Action

These aren't just quality-of-life improvements; they are fundamental security and compliance requirements that would significantly strengthen GitHub's posture for enterprise customers.

I strongly encourage others to Upvote this suggestion and add any other specific use cases where the current lack of detail in audit logs has hindered your security investigations!

Thanks for bringing this important topic up, Jiawei!