---
title: Event log and security debug
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

## Event log

The **Event log** application is a place in the administration interface, where events and activities of the system are recorded. From the security point of view, the events logged into the event log are mainly:

- Authentication attempts - both successful and failed.
- All bad requests - which includes attempts for SQL injections and other various hacking efforts.

You can find more information about event log settings in the [Working with the system event log](https://docs.kentico.com/k8/developing-websites/troubleshooting-websites/working-with-the-system-event-log.md) topic.

## Security debug

The security debug is a part of the debugging interface in Kentico. It allows you to view user security checks performed by the system. Information stored in this section include:

- IsGlobalAdministrator, IsEditor, IsInRole, IsInSite, IsCultureAllowed checks,
- URL hash validation,
- redirects to the AccessDenied page - for missing permissions and UI elements.

You can find the security debug interface in the **Debug** application on the **Security** tab.

![Security debug](https://docs.kentico.com/docsassets/k8/event-log-and-security-debug/Security_debug.png "Security debug")

### Enabling the security debug functionality

If you cannot see the security page, you have to enable the security debug first in **Settings -> System -> Debug** by selecting the option **Enable security debug**.