2022-06-15 07:51:47 +00:00
|
|
|
---
|
|
|
|
|
title: "Security"
|
|
|
|
|
description: "An overview introduction into Authelia's security features."
|
|
|
|
|
lead: "An overview introduction into Authelia's security features."
|
2022-06-28 05:27:14 +00:00
|
|
|
date: 2022-06-15T17:51:47+10:00
|
2022-06-15 07:51:47 +00:00
|
|
|
draft: false
|
|
|
|
|
images: []
|
|
|
|
|
menu:
|
|
|
|
|
overview:
|
|
|
|
|
parent: "security"
|
|
|
|
|
weight: 410
|
|
|
|
|
toc: false
|
|
|
|
|
aliases:
|
|
|
|
|
- /docs/security/
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
The __Authelia__ team takes security very seriously. Because __Authelia__ is intended as a security product a lot of
|
|
|
|
|
decisions are made with security being the priority. This section discusses these decisions as well as considerations
|
|
|
|
|
users should make when implementing __Authelia__.
|
|
|
|
|
|
|
|
|
|
## Coordinated vulnerability disclosure
|
|
|
|
|
|
|
|
|
|
__Authelia__ follows the [coordinated vulnerability disclosure](https://en.wikipedia.org/wiki/Coordinated_vulnerability_disclosure)
|
|
|
|
|
model when dealing with security vulnerabilities. This was previously known as responsible disclosure. We strongly
|
|
|
|
|
urge anyone reporting vulnerabilities to __Authelia__ or any other project to follow this model as it is considered
|
|
|
|
|
as a best practice by many in the security industry.
|
