Reviewing your security log

You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you.

En este artículo

Accessing your security log

The security log lists all actions performed within the last 90 days.

En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en Configuración.
In the user settings sidebar, click Security log.

Searching your security log

El registro lista la siguiente información sobre cada acción:

En qué repositorio se realizó una acción
El usuario que realizó la acción
La acción que se realizó
En qué país se realizó la acción
La fecha y hora en que se produjo la acción

Nota que no puedes buscar entradas utilizando texto. Sin embargo, puedes construir consultas de búsqueda utilizando una variedad de filtros. Muchos operadores que se utilizan cuando se busca el registro por queries, tales como -, >, o <, empatan con el mismo formato que si se busca con GitHub. Para obtener más información, consulta la sección "Buscar en GitHub".

Búsqueda basada en la operación

Utiliza el calificador operation para limitar las acciones en tipos específicos de operaciones. Por ejemplo:

operation:access encuentra todos los eventos en donde se accedió a un recurso.
operation:authentication encuentra todos los eventos en donde se realizó un evento de autenticación.
operation:create encuentra todos los eventos en donde se creó un recurso.
operation:modify encuentra todos los eventos en donde se modificó un recurso existente.
operation:remove encuentra todos los eventos en donde se eliminó un recurso existente.
operation:restore encuentra todos los eventos en donde se restauró un recurso existente.
operation:transfer encuentra todos los eventos en donde se transfirió un recurso existente.

Búsqueda basada en el repositorio

Utiliza el calificador repo para limitar las acciones a un repositorio específico. Por ejemplo:

repo:my-org/our-repo encuentra todos los eventos que ocurrieron para el repositorio our-repo en la organización my-org.
repo:my-org/our-repo repo:my-org/another-repo encuentra todos los eventos que ocurrieron tanto para los repositorios our-repo como another-repo en la organización my-org.
-repo:my-org/not-this-repo excluye todos los eventos que ocurrieron para el repositorio not-this-repo en la organización my-org.

Nota que debes incluir el nombre de cuenta dentro del calificador repo; no funcionará si buscas únicamente repo:our-repo.

Búsqueda basada en el usuario

El calificador actor puede incluir eventos que se basen en quién realizó la acción. Por ejemplo:

actor:octocat encuentra todos los eventos realizados por octocat.
actor:octocat actor:hubot encuentra todos los eventos realizados tanto por octocat como por hubot.
-actor:hubot excluye todos los eventos realizados por hubot.

Ten en cuenta que solo puedes utilizar un nombre de usuario GitHub, no el nombre real de una persona.

Search based on the action performed

Category Name	Description
`account_recovery_token`	Contains all activities related to adding a recovery token.
`billing`	Contains all activities related to your billing information.
`marketplace_agreement_signature`	Contains all activities related to signing the Mercado GitHub Developer Agreement.
`marketplace_listing`	Contains all activities related to listing apps in Mercado GitHub.
`oauth_access`	Contains all activities related to App OAuths you've connected with.
`payment_method`	Contains all activities related to paying for your GitHub subscription.
`profile_picture`	Contains all activities related to your profile picture.
`project`	Contains all activities related to project boards.
`public_key`	Contains all activities related to your public SSH keys.
`repo`	Contains all activities related to the repositories you own.
`sponsors`	Contains all events related to Patrocinadores de GitHub and sponsor buttons (see "About Patrocinadores de GitHub" and "Displaying a sponsor button in your repository")
`two_factor_authentication`	Contains all activities related to two-factor authentication.
`user`	Contains all activities related to your account.

A description of the events within these categories is listed below.

The `account_recovery_token` category

Action	Description
confirm	Triggered when you successfully store a new token with a recovery provider.
recover	Triggered when you successfully redeem an account recovery token.
recover_error	Triggered when a token is used but GitHub is not able to validate it.

The `billing` category

Action	Description
change_billing_type	Triggered when you change how you pay for GitHub.
change_email	Triggered when you change your email address.

The `marketplace_agreement_signature` category

Action	Description
create	Triggered when you sign the Mercado GitHub Developer Agreement.

The `marketplace_listing` category

Action	Description
approve	Triggered when your listing is approved for inclusion in Mercado GitHub.
create	Triggered when you create a listing for your app in Mercado GitHub.
delist	Triggered when your listing is removed from Mercado GitHub.
redraft	Triggered when your listing is sent back to draft state.
reject	Triggered when your listing is not accepted for inclusion in Mercado GitHub.

The `oauth_access` category

Action	Description
create	Triggered when you grant access to an App OAuth.
destroy	Triggered when you revoke an App OAuth's access to your account.

The `payment_method` category

Action	Description
clear	Triggered when a payment method on file is removed.
create	Triggered when a new payment method is added, such as a new credit card or PayPal account.
update	Triggered when an existing payment method is updated.

The `profile_picture` category

Action	Description
update	Triggered when you set or update your profile picture.

The `project` category

Action	Description
`create`	Triggered when a project board is created.
`rename`	Triggered when a project board is renamed.
`update`	Triggered when a project board is updated.
`delete`	Triggered when a project board is deleted.
`link`	Triggered when a repository is linked to a project board.
`unlink`	Triggered when a repository is unlinked from a project board.
`project.access`	Triggered when a project board's visibility is changed.
`update_user_permission`	Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed.

The `public_key` category

Action	Description
create	Triggered when you add a new public SSH key to your GitHub account.
delete	Triggered when you remove a public SSH key to your GitHub account.

The `repo` category

Action	Description
access	Triggered when you a repository you own is switched from "private" to "public" (or vice versa).
add_member	Triggered when a GitHub user is invited to have collaboration access to a repository.
add_topic	Triggered when a repository owner adds a topic to a repository.
archived	Triggered when a repository owner archives a repository.
create	Triggered when a new repository is created.
destroy	Triggered when a repository is deleted.
disable	Triggered when a repository is disabled (e.g., for insufficient funds).
enable	Triggered when a repository is re-enabled.
remove_member	Triggered when a GitHub user is removed from a repository as a collaborator.
remove_topic	Triggered when a repository owner removes a topic from a repository.
rename	Triggered when a repository is renamed.
transfer	Triggered when a repository is transferred.
transfer_start	Triggered when a repository transfer is about to occur.
unarchived	Triggered when a repository owner unarchives a repository.

The `sponsors` category

Action	Description
repo_funding_link_button_toggle	Triggered when you enable or disable a sponsor button in your repository (see "Displaying a sponsor button in your repository")
repo_funding_links_file_action	Triggered when you change the FUNDING file in your repository (see "Displaying a sponsor button in your repository")
sponsor_sponsorship_cancel	Triggered when you cancel a sponsorship (see "Downgrading a sponsorship")
sponsor_sponsorship_create	Triggered when you sponsor a developer (see "Sponsoring an open source contributor")
sponsor_sponsorship_preference_change	Triggered when you change whether you receive email updates from a sponsored developer (see "Managing your sponsorship")
sponsor_sponsorship_tier_change	Triggered when you upgrade or downgrade your sponsorship (see "Upgrading a sponsorship" and "Downgrading a sponsorship")
sponsored_developer_approve	Triggered when your Patrocinadores de GitHub account is approved (see "Setting up Patrocinadores de GitHub for your user account")
sponsored_developer_create	Triggered when your Patrocinadores de GitHub account is created (see "Setting up Patrocinadores de GitHub for your user account")
sponsored_developer_profile_update	Triggered when you edit your sponsored developer profile (see "Editing your profile details for Patrocinadores de GitHub")
sponsored_developer_request_approval	Triggered when you submit your application for Patrocinadores de GitHub for approval (see "Setting up Patrocinadores de GitHub for your user account")
sponsored_developer_tier_description_update	Triggered when you change the description for a sponsorship tier (see "Changing your sponsorship tiers")
sponsored_developer_update_newsletter_send	Triggered when you send an email update to your sponsors (see "Contacting your sponsors")
waitlist_invite_sponsored_developer	Triggered when you are invited to join Patrocinadores de GitHub from the waitlist (see "Setting up Patrocinadores de GitHub for your user account")
waitlist_join	Triggered when you join the waitlist to become a sponsored developer (see "Setting up Patrocinadores de GitHub for your user account")

The `successor_invitation` category

Action	Description
accept	Triggered when you accept a succession invitation (see "Maintaining ownership continuity of your user account's repositories")
cancel	Triggered when you cancel a succession invitation (see "Maintaining ownership continuity of your user account's repositories")
create	Triggered when you create a succession invitation (see "Maintaining ownership continuity of your user account's repositories")
decline	Triggered when you decline a succession invitation (see "Maintaining ownership continuity of your user account's repositories")
revoke	Triggered when you revoke a succession invitation (see "Maintaining ownership continuity of your user account's repositories")

The `two_factor_authentication` category

Action	Description
enabled	Triggered when two-factor authentication is enabled.
disabled	Triggered when two-factor authentication is disabled.

The `user` category

Action	Description
add_email	Triggered when you add a new email address.
create	Triggered when you create a new user account.
remove_email	Triggered when you remove an email address.
rename	Triggered when you rename your account.
change_password	Triggered when you change your password.
forgot_password	Triggered when you ask for a password reset.
login	Triggered when you log in to GitHub.
failed_login	Triggered when you failed to log in successfully.
two_factor_requested	Triggered when GitHub asks you for your two-factor authentication code.
show_private_contributions_count	Triggered when you publicize private contributions on your profile.
hide_private_contributions_count	Triggered when you hide private contributions on your profile.
report_content	Triggered when you report an issue or pull request, or a comment on an issue, pull request, or commit.

The `user_status` category

Action	Description
update	Triggered when you set or change the status on your profile. For more information, see "Setting a status."
destroy	Triggered when you clear the status on your profile.

Exporting your security log

Puedes exportar el registro como datos JSON o como un archivo con valores separados por comas (V).

Botón de exportar

Para filtrar los resultados en tu exportación, busca utilizando uno o más de los calificadores antes de recurrir al menú desplegable Export.

Qualifier	Valor de ejemplo
`Acción`	team.create
`actor (actor)`	octocat
`usuario`	codertocat
`org`	octo-org
`repo`	octo-org/documentation
`created`	2019-06-01

Después de que exportes el registro como JSON o CSV, verás las siguientes claves y valores en el archivo resultante.

Clave	Valor de ejemplo
`Acción`	team.create
`actor (actor)`	octocat
`usuario`	codertocat
`org`	octo-org
`repo`	octo-org/documentation
`created_at (creado en)`	1429548104000 (Los registros horarios muestran la hora desde Epoch con milisegundos).
`data.hook_id`	245
`data.events`	["issues", "issue_comment", "pull_request", "pull_request_review_comment"]
`data.events_were`	["push", "pull_request", "issues"]
`data.target_login`	octocat
`data.old_user`	hubot
`data.team`	octo-org/engineering