> For the complete documentation index, see [llms.txt](https://doc.threatreaper.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.threatreaper.ai/user-guide/what-is-lockthreat.md).

# 📖 What is LockThreat?

LockThreat is an AI security and governance platform. The console is organised around a security lifecycle, which is also how the left sidebar is grouped.

| **Sidebar section** | **Module**   | **Purpose**                                                                      |
| ------------------- | ------------ | -------------------------------------------------------------------------------- |
| **(top)**           | Dashboard    | Executive overview across modules                                                |
| DISCOVER            | AI-Discover  | Inventory AI models, endpoints and shadow AI across cloud, network and endpoints |
| PROBE               | AI-Probe     | Red-team and scan code, model files and live AI endpoints                        |
| PROTECT             | AI-Firewall  | Real-time guardrails for prompts and LLM outputs, driven by policies             |
| PROTECT             | AI-Agents    | Autonomous allow / block / challenge / escalate decisions with trust scoring     |
| PROTECT             | AI-Guard     | Protected chat wrappers and browser plugin management                            |
| PROTECT             | AI-MCP       | Model Context Protocol security (limited availability)                           |
| GOVERNANCE          | AI-Align     | Map your controls to AI regulations and frameworks                               |
| GOVERNANCE          | AI-Explain   | Explain why a decision or finding was produced                                   |
| OPTIMIZE            | AI-Analytics | Model usage, cost, budgets and rate limits                                       |
| **(bottom)**        | Settings     | Administration (visible only when your role allows it)                           |

You only see the modules that your organisation has licensed, that are enabled for your current project, and that your role has permission to view. If a module is missing from your sidebar, ask your administrator.

## Key concepts

* **Organisation** — your company account. Billing, licensing and credits are held at this level.
* **Tenant / Project** — a workspace inside the organisation (for example, one per business unit or region). Almost everything you create (scans, policies, logs) belongs to the project that is active when you create it. The project name appears in the top bar.
* **Role** — a named set of permissions you hold within a project.
* **Policy** — a set of guardrails and the action to take for each. Policies are attached to AI-Firewall projects.
* **Guardrail** — a single detector, such as Prompt Injection, PII or Toxicity.
* **Credits** — a per-module balance consumed when you run certain operations (see Credits).


---

# 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://doc.threatreaper.ai/user-guide/what-is-lockthreat.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.