> For the complete documentation index, see [llms.txt](https://docs.infraglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraglide.com/jane-ai-copilot/security-audits.md).

# Architecture Security Audits

InfraGlide exposes several security-related experiences. They are **not** one single scanner — some are deterministic rules on live inventory, others are Jane LLM reviews of the canvas or findings.

***

## 🛡️ Security Audit Experiences

### 1. Operations Security Page (`/operations/security`)

* Scans **live cloud inventory** — verifying live infrastructure configurations against security best practices.
* UI disclaimer: static checks on firewalls, public exposure, and resource encryption signals.

<figure><img src="/files/JhPSQAwSrgVkKPxntQHQ" alt="Operations Security Dashboard"><figcaption><p>Figure 1: Cloud Infrastructure Security Posture &#x26; Finding Audits</p></figcaption></figure>

### 2. Pre-deploy Canvas Posture Check

* Evaluates saved **pipeline components** before deploying.
* Highlights unencrypted storage buckets, overly permissive ingress rules (`0.0.0.0/0`), and missing logging parameters.

### 3. Ask Jane on Findings

* Click **Ask Jane** on any security finding card to request a detailed explanation and recommended remediation steps.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraglide.com/jane-ai-copilot/security-audits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.