diff --git a/.github/SECURITY.md b/.github/SECURITY.md
index affc77b..074fb74 100644
--- a/.github/SECURITY.md
+++ b/.github/SECURITY.md
@@ -2,6 +2,25 @@
 
 The Docling team and community take security bugs seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
 
+## Supported Versions
+
+The latest versions of Docling are supported.
+
+### Security
+
+- Participation in the [OpenSSF Best Practices Badge Program](https://bestpractices.coreinfrastructure.org/en/projects/10101) for Free/Libre and FLOSS projects to ensure that we follow current best practices for quality and security
+- Use of [HTTPS](https://en.wikipedia.org/wiki/HTTPS) for network communication
+- Use of secure protocols for network communication (through the use of HTTPS)
+- Up-to-date support for TLS/SSL (through the use of [OpenSSL](https://www.openssl.org/))
+- Performance of TLS certificate verification by default before sending HTTP headers with private information (through the use of OpenSSL and HTTPS)
+- Distribution of the software via cryptographically signed releases (on the [PyPI](https://pypi.org/), [Quay.io](https://quay.io/organization/docling-project/) and [GHCR.io](https://github.com/orgs/docling-project/packages) package repositories)
+- Use of [GitHub](https://github.com/) Issues for vulnerability reporting and tracking
+
+### Analysis
+
+- Use of [Ruff](https://docs.astral.sh/ruff/), [Mypy](https://mypy.readthedocs.io/) and [Pytest](https://docs.pytest.org/en/7.2.x/) for Python code linting (static and dynamic analysers) on pull requests and builds
+- Use of GitHub Issues for bug reporting and tracking
+
 ## Reporting a Vulnerability
 
 If you think you've identified a security issue in an Docling project repository, please DO NOT report the issue publicly via the GitHub issue tracker, etc.
@@ -10,7 +29,7 @@ Instead, send an email with as many details as possible to [deepsearch-core@zuri
 
 Please do not create a public issue.
 
-## Security Vulnerability Response
+### Security Vulnerability Response
 
 Each report is acknowledged and analyzed by the core maintainers within 3 working days.