Enterprise admin controls expand for user management and security
GitHub Enterprise has rolled out several updates aimed at giving administrators finer-grained control over user access and a clearer view of security activity across their organization. The new features, released over the past few weeks, span invitation management, audit logging, and application security oversight.
Restrict outside collaborator invitations
Enterprise owners can now limit who is allowed to invite outside collaborators to repositories. A new option in the “Repository outside collaborators” policy dropdown, labeled Enterprise admins only, restricts this capability strictly to enterprise administrators. Previously, organization owners had more latitude in issuing these invitations. The policy is enforced via the enterprise’s repository management settings.
Revoke pending member invitations
In public beta, enterprise owners can now revoke pending member invitations. The capability is accessible from the “Pending invitations” page within the enterprise account, where admins can view outstanding invites and withdraw them as needed.
Audit log now includes actor IP addresses
Enterprise account owners can now view actor IP addresses in their audit log, a feature now in public beta. An actor is defined as a user who initiates an event within GitHub Enterprise. IP addresses are disclosed only when an enterprise member takes action on an asset owned by the enterprise, such as a private repository, project board, issue, or GitHub Action within the enterprise organization.
Notably, IP addresses are not reported when someone pushes code to a public repository, or when an enterprise member pushes code to private repositories that fall outside the enterprise’s organization.
Enterprise-wide security overview for Dependabot
GitHub Advanced Security customers can now view Dependabot alerts across the entire enterprise, a UI capability now in public beta. The new security overview provides a repository-centric view of application security risks, as well as an alert-centric view covering all secret scanning and Dependabot alerts. Alert-centric views for code scanning are planned for the near future.
Dry runs for custom secret scanning patterns
Admins on GitHub Advanced Security can also test custom secret scanning patterns before deploying them. Dry runs let administrators assess a pattern’s impact across the enterprise and refine the pattern before it is published and generates alerts.
