From c7c65fec38ea851c3a8cdf43758525f9037cb8e1 Mon Sep 17 00:00:00 2001 From: dahn Date: Tue, 18 Nov 2025 11:36:27 +0100 Subject: [PATCH 1/3] =?UTF-8?q?add=20=E2=80=98external=20integrations'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- src/pages/security.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/pages/security.md b/src/pages/security.md index 8cb9d829b8..35bda96fac 100644 --- a/src/pages/security.md +++ b/src/pages/security.md @@ -23,6 +23,7 @@ In addition to that, it is your own responsibility, as an operator to - protect against DoS and brute-force attacks. - provide full fledged monitoring. Though some facilities are provided, putting appropriate monitoring remains the ultimate responsibility of the operator. - ensure the security and integrity, including safeguarding them against unauthorized external access of critical cloud resources. These include, but are not limited to OS level access to Hosts, Management Servers, SystemVMs and routers. +- make sure `external integrations` are save to use. That all said, the project will work with any one on improving the secure use of the software it provides, with any 3rd party integration From c1337c2a55cf92141fbda0f14b8efbe3671959e2 Mon Sep 17 00:00:00 2001 From: dahn Date: Tue, 18 Nov 2025 12:44:17 +0100 Subject: [PATCH 2/3] Update src/pages/security.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- src/pages/security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/security.md b/src/pages/security.md index 35bda96fac..3c3dad13c6 100644 --- a/src/pages/security.md +++ b/src/pages/security.md @@ -23,7 +23,7 @@ In addition to that, it is your own responsibility, as an operator to - protect against DoS and brute-force attacks. - provide full fledged monitoring. Though some facilities are provided, putting appropriate monitoring remains the ultimate responsibility of the operator. - ensure the security and integrity, including safeguarding them against unauthorized external access of critical cloud resources. These include, but are not limited to OS level access to Hosts, Management Servers, SystemVMs and routers. -- make sure `external integrations` are save to use. +- make sure `external integrations` are safe to use. That all said, the project will work with any one on improving the secure use of the software it provides, with any 3rd party integration From 9214ba7c661e9864bd7461d129be4f038d21d231 Mon Sep 17 00:00:00 2001 From: dahn Date: Wed, 26 Nov 2025 11:06:24 +0100 Subject: [PATCH 3/3] Apply suggestion from @DaanHoogland --- src/pages/security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/security.md b/src/pages/security.md index 3c3dad13c6..7e10e892d3 100644 --- a/src/pages/security.md +++ b/src/pages/security.md @@ -23,7 +23,7 @@ In addition to that, it is your own responsibility, as an operator to - protect against DoS and brute-force attacks. - provide full fledged monitoring. Though some facilities are provided, putting appropriate monitoring remains the ultimate responsibility of the operator. - ensure the security and integrity, including safeguarding them against unauthorized external access of critical cloud resources. These include, but are not limited to OS level access to Hosts, Management Servers, SystemVMs and routers. -- make sure `external integrations` are safe to use. +- make sure scripts and executables added as custom integrations in the extensions framework, are safe to use. That all said, the project will work with any one on improving the secure use of the software it provides, with any 3rd party integration