# Weak Password Policy

## Overview

This will be seen time and time again. A simple example is if you compromise an account using the password **Winter2024!.** This password is 11 characters, includes upper/lower case characters, numbers and a special character but regardless it is still a **weak password** due to how common it is.

**Deny Lists** can be created to enforced to strengthen a password policy by blocking dictionary words, common words or phrases and passwords that have already been breached. 

Sometimes the organizations password policy could be floating out there in documents somewhere on the internet. You could register for an account and see the password policy on signup. You could even just ask them so you can help them improve upon it

## Example

<figure><img src="/files/5erl3O4PBrt8hcgJVq3F" alt=""><figcaption><p>Weak password policy example</p></figcaption></figure>

<figure><img src="/files/PiCwgiHPMa3jxNvAmm7G" alt=""><figcaption><p>Remediation recommendation</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://pnpt.adot8.com/external-pentest-playbook/common-pentest-findings/weak-password-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.