> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/user-guides/security-audit.md).
# Security Audit
Security Audit provides password security strength reporting in your vault.
## Overview
The Security Audit screen gives the passwords stored in your vault an overall security score based on password strength. You can clearly view information about each record's password strength and reuse from this screen.
{% embed url="" %}
Security Audit
{% endembed %}
## Calculation of Security Score
The calculation of password strength and reuse is performed continuously from your vault across all platforms including Keeper Desktop, Web Vault, iOS and Android devices.
Security Audit
Keeper's password "strength" is a calculated score based on the complexity of the password, with a score rating between 0 and 100 according to the metrics below:
Very Weak: < 20\
Weak: 20-40\
Good: 40-60\
Strong: 60-80\
Very Strong: 80+
For more information on how Security Scores are calculated, visit the following page:
{% content-ref url="/spaces/-LO5CAzpxoaEquZJBpYz/pages/1rTSmBdFb1VN9Pmxn4xB" %}
[Security Audit Score Calculation](/enterprise-guide/security-audit/security-audit-score-calculation.md)
{% endcontent-ref %}
You can easily view a record that contains a high-risk password by clicking on it from the provided list. To resolve the risk, you will be directed to change the password at the record's website and then update the corresponding record in your vault.
Resolve a High-Risk Password
{% hint style="info" %}
Click [here](/user-guides/web-vault.md#changing-passwords-with-keeperfill) to learn how to easily change your passwords using Keeper's browser extension, KeeperFill.
{% endhint %}
---
# 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.keeper.io/user-guides/security-audit.md?ask=&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.
