docs(lighthouse): update lighthouse architecture docs (#9576)

Co-authored-by: Chandrapal Badshah <12944530+Chan9390@users.noreply.github.com>
Co-authored-by: Rubén De la Torre Vico <ruben@prowler.com>
Co-authored-by: Andoni Alonso <14891798+andoniaf@users.noreply.github.com>
This commit is contained in:
Chandrapal Badshah
2026-01-12 17:18:58 +08:00
committed by GitHub
parent 05466cff22
commit 6c01151d78
12 changed files with 448 additions and 244 deletions
@@ -22,7 +22,7 @@ For Lighthouse AI to work properly, models **must** support all of the following
- **Text input**: Ability to receive text prompts.
- **Text output**: Ability to generate text responses.
- **Tool calling**: Ability to invoke tools and functions.
- **Tool calling**: Ability to invoke tools and functions to retrieve data from Prowler.
If any of these capabilities are missing, the model will not be compatible with Lighthouse AI.
@@ -8,24 +8,33 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
Prowler Lighthouse AI integrates Large Language Models (LLMs) with Prowler security findings data.
Here's what's happening behind the scenes:
Behind the scenes, Lighthouse AI works as follows:
- Lighthouse AI runs as a [Langchain agent](https://docs.langchain.com/oss/javascript/langchain/agents) in NextJS
- The agent connects to the configured LLM provider to understand the prompt and decide what data is needed
- The agent accesses Prowler data through [Prowler MCP](https://docs.prowler.com/getting-started/products/prowler-mcp), which exposes tools from multiple sources, including:
- Prowler Hub
- Prowler Docs
- Prowler App
- Instead of calling every tool directly, the agent uses two meta-tools:
- `describe_tool` to retrieve a tool schema and parameter requirements.
- `execute_tool` to run the selected tool with the required input.
- Based on the user's query and the data necessary to answer it, Lighthouse agent will invoke necessary Prowler MCP tools using `discover_tool` and `execute_tool`
- The system uses a multi-agent architecture built with [LanggraphJS](https://github.com/langchain-ai/langgraphjs) for LLM logic and [Vercel AI SDK UI](https://sdk.vercel.ai/docs/ai-sdk-ui/overview) for frontend chatbot.
- It uses a ["supervisor" architecture](https://langchain-ai.lang.chat/langgraphjs/tutorials/multi_agent/agent_supervisor/) that interacts with different agents for specialized tasks. For example, `findings_agent` can analyze detected security findings, while `overview_agent` provides a summary of connected cloud accounts.
- The system connects to the configured LLM provider to understand user's query, fetches the right data, and responds to the query.
<Note>
Lighthouse AI supports multiple LLM providers including OpenAI, Amazon Bedrock, and OpenAI-compatible services. For configuration details, see [Using Multiple LLM Providers with Lighthouse](/user-guide/tutorials/prowler-app-lighthouse-multi-llm).
</Note>
- The supervisor agent is the main contact point. It is what users interact with directly from the chat interface. It coordinates with other agents to answer users' questions comprehensively.
<img src="/images/prowler-app/lighthouse-architecture.png" alt="Lighthouse AI Architecture" />
<img className="block dark:hidden" src="/images/lighthouse-architecture-light.png" alt="Prowler Lighthouse Architecture" />
<img className="hidden dark:block" src="/images/lighthouse-architecture-dark.png" alt="Prowler Lighthouse Architecture" />
<Note>
All agents can only read relevant security data. They cannot modify your data or access sensitive information like configured secrets or tenant details.
Lighthouse AI can only read relevant security data. It cannot modify data or access sensitive information such as configured secrets or tenant details.
</Note>
## Set up
## Set Up
Getting started with Prowler Lighthouse AI is easy:
@@ -43,11 +52,11 @@ For detailed configuration instructions for each provider, see [Using Multiple L
### Adding Business Context
The optional business context field lets you provide additional information to help Lighthouse AI understand your environment and priorities, including:
The optional business context field lets teams provide additional information to help Lighthouse AI understand environment priorities, including:
- Your organization's cloud security goals
- Organization cloud security goals
- Information about account owners or responsible teams
- Compliance requirements for your organization
- Compliance requirements
- Current security initiatives or focus areas
Better context leads to more relevant responses and prioritization that aligns with your needs.