> As of April 2026, the Security Log Request process has changed. Customer Support can now fulfill log requests using [this process](https://internal.gitlab.com/handbook/support/workflows/security-logs-runbook/).
Users often ask for access to GitLab.com logs, typically, due to [IP blocks](/handbook/support/workflows/ip-blocks), a possible security issue, or for internal auditing purposes.
Always include a link to the log as an internal note, with additional information if needed.
If the customer request matches one of the templates defined in the [internal runbook](https://internal.gitlab.com/handbook/support/workflows/security-logs-runbook/), Customer Support can fulfill the log request directly by following the process outlined there.
If the request does not match an available template, we can provide generic summary information such as the below.
- Information found in the [Audit Events Features](https://docs.gitlab.com/administration/audit_event_reports/)
- Information about who has accessed the account/projects that the customers owns. This can include:
@@ -53,6 +58,7 @@ We can provide the following information:
- range of timestamp of occurrence
- project path
- Provide the above excluding a known list. For example, number of IP addresses not originating from a user's "work office".
- Ensure you add the Zendesk ticket tag: `customer_log_requests` for reporting and audit purposes.
### What we cannot provide without a SIRT escalation
