> For the complete documentation index, see [llms.txt](https://chunhthanhde.gitbook.io/google-learning-programs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chunhthanhde.gitbook.io/google-learning-programs/google-it-support-professional-certificate/course-5-it-security-defense-against-the-digital-dark-arts/module-3-authentication-authorization-accounting/1.authentication/1.best-practices-for-authentication.md).

# Best Practices for Authentication 🔐

## **Understanding Authentication** 🔍

* **Identification**: Describing an entity uniquely (e.g., email address).
* **Authentication**: Proving the identity (e.g., password associated with the email).

Authentication and authorization are distinct:

* **Authentication (AuthN)**: Verifying who you are.
* **Authorization (AuthZ)**: Determining what resources you can access.

## **Password Strength** 🛡️

* **Weak Password Example**: `ponies`
  * Short and simple, easily compromised by brute force or dictionary attacks.
* **Strong Password Characteristics**:
  * Longer length, complexity, including numbers, uppercase letters, and special characters.

## **Security vs. Usability Trade-Off** ⚖️

* **Strong Passwords**: Complex and harder to remember.
* **Usable Passwords**: Easier to remember but less secure.

Finding a balance is crucial. For instance, transforming a memorable phrase into a complex password (e.g., `1L1k3P0n!3s`) enhances security while remaining relatively easy to remember.

## **Good Password Practices** ✔️

* **Password Policies**:
  * Enforce length, complexity, and avoid dictionary words.
  * Avoid writing down or sharing passwords.
  * Prevent password reuse across accounts.
* **Password Rotation**:
  * Rotate passwords periodically, but avoid overly frequent changes to prevent poor security practices, like writing passwords down.

## **Summary** 📋

Effective authentication requires a balance between security and usability. Strong passwords are essential but must be manageable for users. Implementing robust password policies and practices can safeguard against unauthorized access and maintain system integrity.

By understanding and applying these principles, you can ensure robust security while accommodating practical usability needs. 🌐🔒


---

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

```
GET https://chunhthanhde.gitbook.io/google-learning-programs/google-it-support-professional-certificate/course-5-it-security-defense-against-the-digital-dark-arts/module-3-authentication-authorization-accounting/1.authentication/1.best-practices-for-authentication.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.