Skip to main content
Sazabi looks for security problems and files each one as an issue 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.

Set it up

1

Send your logs

Hand setup to your coding agent or run one command. See Quickstart. To add more of your stack, see Send data.
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. On Kubernetes, see Send Kubernetes audit logs.
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.
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

Looking for how Sazabi protects your data? See Trust.