You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by da...@apache.org on 2025/11/26 10:13:27 UTC
(cloudstack-www) branch staging-site updated: add ‘external integrations' (#386)
This is an automated email from the ASF dual-hosted git repository.
dahn pushed a commit to branch staging-site
in repository https://gitbox.apache.org/repos/asf/cloudstack-www.git
The following commit(s) were added to refs/heads/staging-site by this push:
new 405660cd2 add ‘external integrations' (#386)
405660cd2 is described below
commit 405660cd290b2b28354460f3adf1f19091aef035
Author: dahn <da...@shapeblue.com>
AuthorDate: Wed Nov 26 11:13:21 2025 +0100
add ‘external integrations' (#386)
---
src/pages/security.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/pages/security.md b/src/pages/security.md
index 8cb9d829b..7e10e892d 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 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