Copilot audit events for policy changes do not say which policy changed #213377
Replies: 2 comments 3 replies
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
Thanks for the detailed write-up. I'm not GitHub staff, so I can't say whether the omission is intended, but I can add a +1 and a few practical points. +1 on the gap An audit event that records who changed a Copilot policy and when, but not which policy or what value, doesn't meet the need that the roadmap item describes. For SOC 2 and ISO evidence, auditors usually want the object, the old value and the new value. Your comparison with the other Copilot events is a strong argument: Workarounds in the meantime (not a replacement for the fix)
What would help the team act on this
Posting the same request on the roadmap item you reference (github/roadmap#822), if it is still open for comments, would put it where the product owners are watching. I've added a 👍 here. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
Body
What I expected
Copilot settings changes should be auditable end to end. github/roadmap#822 shipped with the goal that admins can "review updates and changes to their Copilot settings through the audit log."
What happens
The events
copilot.cfb_enterprise_settings_changedandcopilot.cfb_org_settings_changedcarry only common fields: action, actor, timestamp, owner. They don't include the policy name or the previous/current value, so an audit trail (including audit log streaming to Splunk/Datadog) can show that a change happened and who made it, but not what changed.Why it matters
For change-management evidence (SOC 2, ISO) and for alerting on specific policy changes, "who/when" isn't sufficient. Today we have to reconcile the event against current Copilot settings manually, or ask the actor what they changed.
Not consistent with other Copilot events
copilot.cfb_seat_management_changedreturns new_value/old_value, andcopilot.enterprise_enablement_changedreturns current_value/previous_value. So the detail exists elsewhere in the same family of events.Ask
The event reference lists no additional fields for these two actions:
https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise
All reactions