> For the complete documentation index, see [llms.txt](https://docs.scanner.dev/scanner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/beta-features/jupyter-notebooks/scanner-notebooks-on-github.md).

# Scanner Notebooks on GitHub

The [**scanner-notebooks**](https://github.com/scanner-inc/scanner-notebooks) GitHub repository contains a wide range of Jupyter notebooks tailored for security use cases.

These notebooks are designed to help users quickly get started with analyzing various security log sources and leverage powerful visualizations.

Each notebook is crafted for real-world use cases, making it easier for security teams to detect, investigate, and respond to potential threats efficiently.

Use cases highlighted in these notebooks will soon include:

* Visualizing network graphs of role assumption for privilege escalation
* Unusual API activity
* Suspicious cross-account activity
* Access from unauthorized or risky locations
* Failed security controls changes
* Compromised user credentials
* And more...

The notebooks will soon cover common log sources, such as:

* AWS CloudTrail, VPC flow
* Cloudflare HTTP, WAF, DNS
* Crowdstrike FDR
* Windows Sysmon
* Okta System
* GitHub Audit
* And more...

You can start using these notebooks by cloning the [**scanner-notebooks**](https://github.com/scanner-inc/scanner-notebooks) repository on GitHub and using them in a local Jupyter environment like **JupyterLab Desktop**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/beta-features/jupyter-notebooks/scanner-notebooks-on-github.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
