Reviewing the audit log for your organization

Accessing the audit log

The audit log lists actions performed within the last 90 days. Only owners can access an organization's audit log.

1. In the top right corner of GitHub Enterprise, click your profile photo, then click Your profile.
   
2. On the left side of your profile page, under "Organizations", click the icon for your organization.
   
3. Under your organization name, click Settings.
   
4. In the Settings sidebar, click Audit log.
   

Searching the audit log

The log lists the following information about each action:

• Which repository an action was performed in
• The user that performed the action
• The action that was performed
• Which country the action took place in
• The date and time the action occurred

Note that you cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as -, >, or <, match the same format as searching across GitHub Enterprise. For more information, see "Searching on GitHub."

Search based on repository

Use the repo qualifier to limit actions to a specific repository. For example:

• repo:my-org/our-repo finds all events that occurred for the our-repo repository in the my-org organization.
• repo:my-org/our-repo repo:my-org/another-repo finds all events that occurred for both the our-repo and another-repo repositories in the my-org organization.
• -repo:my-org/not-this-repo excludes all events that occurred for the not-this-repo repository in the my-org organization.

Note that you must include the account name within the repo qualifier; searching for just repo:our-repo will not work.

Search based on the user

The actor qualifier can scope events based on who performed the action. For example:

• actor:octocat finds all events performed by octocat.
• actor:octocat actor:hubot finds all events performed by both octocat and hubot.
• -actor:hubot excludes all events performed by hubot.

Note that you can only use a GitHub Enterprise username, not an individual's real name.

Search based on the action performed

To search for specific events, use the action qualifier in your query. Actions listed in the audit log are grouped within the following categories:

You can search for specific sets of actions using these terms. For example:

• action:team finds all events grouped within the team category.
• -action:hook excludes all events in the webhook category.

Each category has a set of associated events that you can filter on. For example:

• action:team.create finds all events where a team was created.
• -action:hook.events_changed excludes all events where the events on a webhook have been altered.

This list describes the available categories and associated events:

• The discussion_post category
• The discussion_post_reply category
• The hook category
• The integration_installation_request category
• The issue category
• The org category
• The oauth_application category
• The profile_picture category
• The project category
• The protected_branch category
• The repo category
• The repository_vulnerability_alert category
• The team category
• The team_discussions category

The discussion_post category

The discussion_post_reply category

The hook category

The integration_installation_request category

The issue category

The org category

The oauth_application category

The profile_picture category

The project category

The protected_branch category

The repo category

The repository_vulnerability_alert category

The team category

The team_discussions category

Search based on time of action

Use the created qualifier to filter actions in the audit log based on when they occurred. Date formatting must follow the ISO8601 standard, which is YYYY-MM-DD (year-month-day). You can also add optional time information THH:MM:SS+00:00 after the date, to search by the hour, minute, and second. That's T, followed by HH:MM:SS (hour-minutes-seconds), and a UTC offset (+00:00).

Dates support greater than, less than, and range qualifiers. For example:

• created:2014-07-08 finds all events that occurred on July 8th, 2014.
• created:>=2014-07-08 finds all events that occurred on or after July 8th, 2014.
• created:<=2014-07-08 finds all events that occurred on or before July 8th, 2014.
• created:2014-07-01..2014-07-31 finds all events that occurred in the month of July 2014.

The audit log contains data for the past 90 days, but you can use the created qualifier to search for events earlier than that.

Search based on location

Using the qualifier country, you can filter actions in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example:

• country:de finds all events that occurred in Germany.
• country:Mexico finds all events that occurred in Mexico.
• country:"United States" all finds events that occurred in the United States.

Using the Audit log API

To ensure a secure IP and maintain compliance for your organization, you can use the Audit log API to keep copies of your audit log data and monitor:

• Access to your organization or repository settings.
• Changes in permissions.
• Added or removed users in an organization, repository, or team.
• Users being promoted to admin.
• Changes to permissions of a GitHub App.

The GraphQL response can include data for up to 90 to 120 days.

For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "GraphQL API Audit Log."

Further reading

• "Keeping your organization secure"