gsadmin/sencho
1
0
Fork 0
mirror of https://github.com/Studio-Saelix/sencho.git synced 2026-08-27 18:57:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: align Community and Admiral assurance positioning (#1632)

Browse Source 
Reframe docs, OpenAPI registries copy, and License trial/expiry helpers
so Community is the full AGPLv3 product and Admiral leads with current
assurance (Hardened Build, Recovery Vault, support, governance).
Mesh, Secrets, and Host Console stay limited-availability without
Admiral sales framing.
This commit is contained in:
Anso
2026-07-14 19:44:28 -04:00
committed by GitHub
parent 678c198faa
commit 8096799e49
20 changed files with 168 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/deploy-enforcement.mdx
+1 -1
View File
@@ -7,7 +7,7 @@ description: "Block deploys that violate a scan policy before docker compose up
Deploy enforcement is the pre-flight half of Sencho's vulnerability workflow. When a [scan policy](/features/vulnerability-scanning#scan-policies) with **Block on deploy** enabled matches a stack, Sencho scans every image referenced by the stack's compose file before starting any container. A policy gates on exploitation risk: a known-exploited CVE (CISA KEV), a fixable Critical/High finding, or a raw severity threshold. If any image matches an enabled condition, the deploy is rejected and the stack never starts. Detection always continues post-deploy and on a schedule, so images that develop new vulnerabilities after the initial deploy still surface through alerts.
<Note>
Deploy enforcement and scan policies require an **Admiral** license.
Deploy enforcement and scan policies are available on every tier.
</Note>
## Configuring a block policy