> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Security

> What Sazabi finds in your logs and repositories on the security side, what it needs from you, and where to set it up.

Sazabi looks for security problems and files each one as an [issue](https://docs.sazabi.com/detect/issues.md) with the Security type, so it reaches your inbox, your channels, and your coding agent like any other problem. It looks in:

* **Your logs.** Sazabi reads the logs you send for attacks, unusual account activity, and secrets written where they don't belong.

- **Your code.** Sazabi scans your connected repositories for vulnerabilities and files each confirmed finding as an issue.

Sazabi reports what it finds. It doesn't block traffic or change your systems.

## What it needs

* **For findings in logs:** the logs your applications, cloud platform, and security tools already produce. Sazabi can only report what your logs contain, so a login route that logs nothing can't show a credential spray.
* **For vulnerabilities in code:** a repository connected to the project under **Git repositories** in [**Settings > Code**](https://app.sazabi.com/settings/code-search).

## Set it up

**Step 1**

### Send your logs

Hand setup to your coding agent or run one command. See [Quickstart](https://docs.sazabi.com/get-started/quickstart.md). To add more of your stack, see [Send data](https://docs.sazabi.com/send-data.md).

**Step 2**

### Connect your security sources

Add the tools that record who did what, such as AWS CloudTrail, Okta, or GitHub Audit Log. Browse the **Security and identity** group in [Integrations](https://docs.sazabi.com/catalogs/integrations.md). On Kubernetes, see [Send Kubernetes audit logs](https://docs.sazabi.com/send-data/kubernetes-audit-logs.md).

**Step 3**

### Route security issues to your team

Add a delivery rule with the condition **Type is one of** **Security**, or run `npx -y @sazabi/cli@latest notifications delivery-rules create --notification-type issue_triggered --destination slack_channel:C0SEC --type security`, with your own channel ID. See [Route notifications](https://docs.sazabi.com/triage/notifications.md#delivery-rules).

To see what Sazabi has found so far, run `npx -y @sazabi/cli@latest issues list --type security --status open`, or open **Issues** in the web app and filter by type.

## Go deeper

* [Detect threats in your logs](https://docs.sazabi.com/detect/security.md): what the log detections catch, what they read, and how to steer them.

- [Security review](https://docs.sazabi.com/detect/security-review.md): how Sazabi scans connected repositories and files confirmed vulnerabilities.
- [Send Kubernetes audit logs](https://docs.sazabi.com/send-data/kubernetes-audit-logs.md): see who exec'd into pods, read secrets, or changed RBAC.
- [Route notifications](https://docs.sazabi.com/triage/notifications.md): send security issues to the right channel or on-call tool.
- [Issues](https://docs.sazabi.com/detect/issues.md): types, categories, and what you can do with any issue.

Looking for how Sazabi protects your data? See [Trust](https://docs.sazabi.com/trust.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.