Learn how you can securely manage users with the latest ships for GitHub Enterprise.
Over the past few weeks, we have released several new features to help our GitHub Enterprise customers secure and manage users at an enterprise level. Learn how you can securely manage users with GitHub Enterprise’s latest ships!
Enterprise owners can now prevent organization owners from inviting outside collaborators to repositories in their enterprise. In the “Repository outside collaborators” policy dropdown, we’ve included an additional option labeled “Enterprise admins only.” This option limits the ability to invite outside collaborators strictly to enterprise administrators.
Read our GitHub Changelog and documentation to learn more about repository management policies.
Another new feature now available in public beta is that enterprise owners have the ability to revoke pending member invitations. To view pending members and revoke a pending invitation, navigate to the “Pending invitations” page within your enterprise account.
Learn more about this feature via our Changelog and documentation.
Now in public beta, GitHub Enterprise account owners can view actor IP addresses in the audit log for events associated with their private repositories. In this case, an actor is defined as a user that initiates an event within GitHub Enterprise. Disclosing actor IP addresses within audit logs is a long-awaited feature for our Enterprise customers, because it enables them to meet their security and compliance needs. IP addresses are only shared if an Enterprise member takes action against their GitHub Enterprise-owned asset, such as a private repository, project board, issue, or GitHub Action within the enterprise organization. We do not report when someone pushes code to a public repository or a GitHub Enterprise member pushes code to private repositories that are not part of their enterprise’s organization.
GitHub Advanced Security customers can now view Dependabot alerts at the enterprise level. This new UI capability in public beta displays a repository-centric view of application security risks, an alert-centric view of all secret scanning, and Dependabot alerts. We plan to include alert-centric views for code scanning in the near future!
Read our Changelog and documentation to learn more about security overview.
GitHub Advanced Security customers can also conduct dry runs for custom secret scanning patterns. Conducting dry runs allows admins to understand a pattern’s impact across the entire enterprise and hone in on the pattern before publishing and generating alerts.
Check out our Changelog and our documentation for more information
To learn more about how to keep your organization secure, check out our docs on managing and reviewing security settings.
Start your free trial for 30 days and increase your team’s collaboration. $21 per user/month after trial expires.
Curious about other plans?
In March, we experienced two incidents that resulted in degraded performance across GitHub services.
This blog post is an in-depth walkthrough on how we perform security research leveraging GitHub features, including code scanning, CodeQL, and Codespaces.
In this post, I’ll look at CVE-2023-6241, a vulnerability in the Arm Mali GPU that allows a malicious app to gain arbitrary kernel code execution and root on an Android phone. I’ll show how this vulnerability can be exploited even when Memory Tagging Extension (MTE), a powerful mitigation, is enabled on the device.
Rizel Scarlett 
